Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Installing Gentoo
  • Search

kernel panic/unable to mount root on ...

Having problems with the Gentoo Handbook? If you're still working your way through it, or just need some info before you start your install, this is the place. All other questions go elsewhere.
Post Reply
Advanced search
16 posts • Page 1 of 1
Author
Message
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

kernel panic/unable to mount root on ...

  • Quote

Post by f41t3r » Wed Feb 02, 2005 6:03 pm

1st boot after installation:

Code: Select all

VFS: Cannot open root device "303" or 03:03
Please append correct "root=" boot option
Kernel panic: Unable to mount root fs on 03:03
lilo.conf:

Code: Select all

boot=/dev/hda
prompt
timeout=50
default=gentoo
vga=771
image=/boot/kernel-2.4.28-gentoo-r5
label=gentoo
root=/dev/hda3
other=/dev/hda1
label=windoza
my hdd:

Code: Select all

/dev/hda1 vfat - winda
/dev/hda2 ext2 active - /boot
/dev/hda3 ext3 - gentoo
/dev/hda4 - swap
I didn't use genkernel. Any body can help ?
Last edited by f41t3r on Thu Feb 03, 2005 12:41 am, edited 1 time in total.
"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
imadcow1
n00b
n00b
User avatar
Posts: 42
Joined: Tue Feb 17, 2004 3:26 am
Location: Cullman, Alabama
Contact:
Contact imadcow1
Website

  • Quote

Post by imadcow1 » Wed Feb 02, 2005 6:26 pm

I had a similar issue with grub and a 120gb drive. I added "hda=remap" to the boot options and that made it work.

I had to add that because western digital installed software on the drive in the same area that the bootloader is installed and it caused things to break.
www.madcowworld.com -- Your Link for Nothing
Top
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

  • Quote

Post by f41t3r » Wed Feb 02, 2005 8:23 pm

ok, now i have

Code: Select all

boot=/dev/hda
prompt
timeout=50
default=gentoo
vga=771
image=/boot/kernel-2.4.28-gentoo-r5
label=gentoo
root=/dev/hda3
append="hda=remap"
other=/dev/hda1
label=windoza


and unfortunately it still isn't working - the same error message
p.s. yup i have wd too
"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Wed Feb 02, 2005 8:40 pm

Be sure to statically include the root fs and your hd controller drivers in the kernel.

bye,
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

  • Quote

Post by f41t3r » Wed Feb 02, 2005 9:09 pm

i think 2 it's realated with some kernel options, but i must avow i don't know really where to search it ...
"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

  • Quote

Post by f41t3r » Thu Feb 03, 2005 12:32 am

few minutes ago i had recompile the kernel

for now there is only one line of error: Kernel Panic: Unable to mount root on 03:03

these are some parts from .config file maybe it will help you to find the bug :), thx anyway.

Code: Select all


#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_HAS_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_F00F_WORKS_OK=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_EDD=y
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
CONFIG_MATH_EMULATION=y
CONFIG_MTRR=y
CONFIG_SMP=y
CONFIG_NR_CPUS=32
CONFIG_X86_NUMA=y
CONFIG_X86_NUMAQ=y
CONFIG_X86_CLUSTERED_APIC=y
CONFIG_MULTIQUAD=y
CONFIG_X86_SUMMIT=y
CONFIG_X86_CLUSTERED_APIC=y
CONFIG_HAVE_DEC_LOCK=y

#
# General setup
#
CONFIG_NET=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_ISA=y
CONFIG_PCI_NAMES=y
CONFIG_EISA=y
CONFIG_MCA=y
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=y
CONFIG_CARDBUS=y
# CONFIG_TCIC is not set
# CONFIG_I82092 is not set
# CONFIG_I82365 is not set


[...]

#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=m
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=0
CONFIG_MTD_PARTITIONS=m
CONFIG_MTD_CONCAT=m
CONFIG_MTD_REDBOOT_PARTS=m
CONFIG_MTD_CMDLINE_PARTS=m
CONFIG_MTD_CHAR=m
CONFIG_MTD_BLOCK=m
# CONFIG_MTD_BLOCK_RO is not set
CONFIG_FTL=m
CONFIG_NFTL=m
CONFIG_NFTL_RW=y

#
# RAM/ROM/Flash chip drivers
#
# CONFIG_MTD_CFI is not set
# CONFIG_MTD_JEDECPROBE is not set
# CONFIG_MTD_GEN_PROBE is not set
# CONFIG_MTD_CFI_INTELEXT is not set
# CONFIG_MTD_CFI_AMDSTD is not set
# CONFIG_MTD_CFI_STAA is not set
# CONFIG_MTD_RAM is not set
# CONFIG_MTD_ROM is not set
# CONFIG_MTD_ABSENT is not set
# CONFIG_MTD_OBSOLETE_CHIPS is not set
# CONFIG_MTD_AMDSTD is not set
# CONFIG_MTD_SHARP is not set
# CONFIG_MTD_JEDEC is not set

[..]


#
# Self-contained MTD device drivers
#
# CONFIG_MTD_PMC551 is not set
# CONFIG_MTD_SLRAM is not set
CONFIG_MTD_MTDRAM=m
CONFIG_MTDRAM_TOTAL_SIZE=4096
CONFIG_MTDRAM_ERASE_SIZE=128
# CONFIG_MTD_BLKMTD is not set
# CONFIG_MTD_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
# CONFIG_MTD_DOC2001 is not set
# CONFIG_MTD_DOCPROBE is not set

[...]

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
CONFIG_BLK_DEV_PS2=m
CONFIG_BLK_DEV_XD=y
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
CONFIG_PARIDE_PT=m
CONFIG_PARIDE_PG=m
CONFIG_PARIDE_ATEN=m
# CONFIG_PARIDE_BPCK is not set
# CONFIG_PARIDE_BPCK6 is not set
# CONFIG_PARIDE_COMM is not set
# CONFIG_PARIDE_DSTR is not set
# CONFIG_PARIDE_FIT2 is not set
# CONFIG_PARIDE_FIT3 is not set
# CONFIG_PARIDE_EPAT is not set
# CONFIG_PARIDE_EPIA is not set
# CONFIG_PARIDE_FRIQ is not set
# CONFIG_PARIDE_FRPW is not set
# CONFIG_PARIDE_KBIC is not set
# CONFIG_PARIDE_KTTI is not set
# CONFIG_PARIDE_ON20 is not set
# CONFIG_PARIDE_ON26 is not set
CONFIG_BLK_CPQ_DA=m
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_CISS_MONITOR_THREAD is not set
CONFIG_BLK_DEV_DAC960=m
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_SX8=m
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_BLK_STATS=y

[...]

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_HD_IDE=y
CONFIG_BLK_DEV_HD=y
CONFIG_BLK_DEV_IDE_SATA=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_IDEDISK_STROKE=y
CONFIG_BLK_DEV_IDECS=y
CONFIG_BLK_DEV_DELKIN=m
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_IDE_TASK_IOCTL=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_OFFBOARD=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_PCI_WIP=y
# CONFIG_BLK_DEV_ADMA100 is not set
CONFIG_BLK_DEV_AEC62XX=m
CONFIG_BLK_DEV_ALI15X3=m
# CONFIG_WDC_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=m
# CONFIG_AMD74XX_OVERRIDE is not set
CONFIG_BLK_DEV_ATIIXP=m
CONFIG_BLK_DEV_CMD64X=y
CONFIG_BLK_DEV_TRIFLEX=m
CONFIG_BLK_DEV_CY82C693=m
CONFIG_BLK_DEV_CS5530=m
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
CONFIG_BLK_DEV_PIIX=m
CONFIG_BLK_DEV_NS87415=m
CONFIG_BLK_DEV_OPTI621=m
CONFIG_BLK_DEV_PDC202XX_OLD=m
# CONFIG_PDC202XX_BURST is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_PDC202XX_FORCE is not set
CONFIG_BLK_DEV_RZ1000=m
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_BLK_DEV_ATARAID=m
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_MEDLEY is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set

[...]

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SERIAL_EXTENDED=y
# CONFIG_SERIAL_MANY_PORTS is not set
# CONFIG_SERIAL_SHARE_IRQ is not set
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_ESPSERIAL is not set
# CONFIG_MOXA_INTELLIO is not set
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_SYNCLINKMP is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
CONFIG_STALDRV=y
# CONFIG_STALLION is not set
# CONFIG_ISTALLION is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
# CONFIG_PRINTER is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

[...]

#
# File systems
#
CONFIG_QUOTA=y
CONFIG_QFMT_V2=m
CONFIG_AUTOFS_FS=m
CONFIG_AUTOFS4_FS=y
CONFIG_REISERFS_FS=m
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
CONFIG_ADFS_FS=y
CONFIG_ADFS_FS_RW=y
CONFIG_AFFS_FS=m
CONFIG_HFS_FS=m
CONFIG_HFSPLUS_FS=m
CONFIG_BEFS_FS=m
# CONFIG_BEFS_DEBUG is not set
CONFIG_BFS_FS=y
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_JBD_DEBUG=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_UMSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_EFS_FS=m
CONFIG_JFFS_FS=m
CONFIG_JFFS_FS_VERBOSE=0
CONFIG_JFFS_PROC_FS=y
CONFIG_JFFS2_FS=m
CONFIG_JFFS2_FS_DEBUG=0
CONFIG_CRAMFS=m
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_JFS_FS=y
CONFIG_JFS_DEBUG=y
CONFIG_JFS_STATISTICS=y
CONFIG_MINIX_FS=m
CONFIG_VXFS_FS=m
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
CONFIG_HPFS_FS=y
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
CONFIG_DEVFS_DEBUG=y
CONFIG_DEVPTS_FS=y
CONFIG_QNX4FS_FS=m
# CONFIG_QNX4FS_RW is not set
CONFIG_ROMFS_FS=m
CONFIG_EXT2_FS=m
CONFIG_SYSV_FS=m
CONFIG_UDF_FS=m
# CONFIG_UDF_RW is not set
CONFIG_UFS_FS=m
# CONFIG_UFS_FS_WRITE is not set
CONFIG_XFS_FS=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_RT=y
CONFIG_XFS_TRACE=y
CONFIG_XFS_DEBUG=y

[...]

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_BSD_DISKLABEL=y
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
CONFIG_UNIXWARE_DISKLABEL=y
CONFIG_LDM_PARTITION=y
CONFIG_LDM_DEBUG=y
CONFIG_SGI_PARTITION=y
# CONFIG_ULTRIX_PARTITION is not set
CONFIG_SUN_PARTITION=y
# CONFIG_EFI_PARTITION is not set
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

[...]

"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Thu Feb 03, 2005 1:27 pm

Please report also your root filesystem and your hd controller chipset :)
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

  • Quote

Post by f41t3r » Thu Feb 03, 2005 2:31 pm

root fs is ext3; hd controller chipset ? where can i find information about it ?
"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Thu Feb 03, 2005 7:02 pm

I think on the installation manual of your motherboard, or on Google, by typing the name/model of it.
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
f41t3r
n00b
n00b
User avatar
Posts: 12
Joined: Wed Feb 02, 2005 5:58 pm
Location: Poland
Contact:
Contact f41t3r
Website

  • Quote

Post by f41t3r » Thu Feb 03, 2005 7:46 pm

ok, i've found this information about chipset in the motherboard manual:

Chipset:

VIA KT400 North bridge
ViA VT8235 South Bridge
-Dual channel Ultra DMA 33/66/100/133 master mode EIDE controller
"Try to realise the truth - there is no spoon, then you see, that's not the spoon that bends, it is only yourself" - spoon kid
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Sun Feb 06, 2005 7:06 pm

So, it seems that you have all the needed support included. So the only solution that comes to my mind is to add the option "read-only" to the linux section :?

Try to see here
http://www.netadmintools.com/html/5lilo.conf.man.html
if there are information useful to you..
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
rouben
Apprentice
Apprentice
User avatar
Posts: 159
Joined: Mon Feb 07, 2005 3:16 am
Location: Thornhill, ON, Canada
Contact:
Contact rouben
Website

  • Quote

Post by rouben » Mon Feb 07, 2005 3:24 am

I am having the same issue, except with reiserfs, and my IDE chipset is nVidia nForce. I am trying this out on a Compaq Presario R3310 laptop (maybe you know of some quirks with that model :?:).

The funny thing is that a 2.4 kernel with an identical configuration boots fine. It's just the 2.6. kernels that I am having problems with... :(

After Googling for a while I noticed that a lot of people have had this issue on a variety of distributions, from Fedora to Debian. So far the only two solutions I've seen were:
  • Make sure the IDE chipset and filesystem support is compiled in
  • Use an initrd image and let it do the mounting of the root fs
I have tried both, many times, under different conditions... I'll watch this thread with hopes that something interesting will come up.

Thanks in advance!
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Mon Feb 07, 2005 7:18 pm

rouben: try to post here your boot loader config file. If you use "LiLo", have you tried to use Grub? If yes, did you find the same problems? (this is useful also for f41t3r)
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
rouben
Apprentice
Apprentice
User avatar
Posts: 159
Joined: Mon Feb 07, 2005 3:16 am
Location: Thornhill, ON, Canada
Contact:
Contact rouben
Website

  • Quote

Post by rouben » Tue Feb 08, 2005 8:09 am

active wrote:rouben: try to post here your boot loader config file. If you use "LiLo", have you tried to use Grub? If yes, did you find the same problems? (this is useful also for f41t3r)
I'm using Grub, I stopped using LILO a while ago. ;)

My grub.conf is pretty simple:

Code: Select all

title Gentoo 2.6
kernel (hd0,4)/boot/kernel-2.6 root=/dev/hda5

title Gentoo 2.4
kernel (hd0,4)/boot/kernel-2.4 root=/dev/hda5
I didn't use genkernel, and I'm positive that I have both my IDE chipset and filesystem drivers built into the kernel (I doublecked this ad nauseum, I even built a kernel will all the IDE and filesystem options built-in, not as modules, but to no avail). After all, 2.4 kernels with identical configs are able to boot just fine using identical lilo configs.

At first I thought this is related to the fact that I have a single partition for everything (i.e. no separate /boot partition), or perhaps because I used reiserfs rather than ext2 or ext3. However, after researching this a bit, I noticed quite a few people having exactly the same issue with ext2, ext3 and reiser... 8O

Actually, just now, I notices something interesting that has a direct connection to my (and perhaps everyone else's) problem. The following line in my kernel output, just after the IDE chipset lines, right after the hda geometry output:

/dev/ide/host0/bus0/target0/lun0: unknown partition table

That would definitely explain the error I've been getting, now wouldn't it? ;) I never noticed this line before, in part because I never tried to boot the kernel in a high-res framebuffer mode and this line zipped by too fast for me to see. I am curious, f41t3r, do you notice anything similar to this in your kernel output, when you try to boot?

I'm using the latest 2.6 gentoo-dev-sources, by the way. I've tried some older releases too.
Top
active
Apprentice
Apprentice
User avatar
Posts: 228
Joined: Mon Jun 23, 2003 9:32 pm
Location: Something not a structure or union
Contact:
Contact active
Website

  • Quote

Post by active » Tue Feb 08, 2005 3:23 pm

rouben it's quite strange.
First of all try to add to:

Code: Select all

title Gentoo 2.6
kernel (hd0,4)/boot/kernel-2.6 root=/dev/hda5
this:

Code: Select all

title Gentoo 2.6
root (hd0,4)
kernel (hd0,4)/boot/kernel-2.6 root=/dev/hda5 
If the error persists, it could be:
1) an IDE + devfs problem
2) an ugly conversion from 2.4 to 2.6 kernel branches
In this case it could be useful also to emerge the linux26-headers, and try recompiling devfs. I think you should find out a guide on how to migrate from 2.4 to 2.6 on gentoo related docs.
GIT d- s:+>: a-- C+++ UBS+++ P++ L+++
E--- W+ N+ w M- PS+(++) PE PGP+ !t
X++ tv+ b++ D+ G e h! r++ x*
Top
rouben
Apprentice
Apprentice
User avatar
Posts: 159
Joined: Mon Feb 07, 2005 3:16 am
Location: Thornhill, ON, Canada
Contact:
Contact rouben
Website

  • Quote

Post by rouben » Tue Feb 08, 2005 7:09 pm

Thanks for the tip. :) Actually, I think my partition table is hosed. First of all, the computer was pre-installed with Windows XP Home (and I heard some rumours of weird partitioning artifacts on such systems). Secondly, I used PartitionMagic 8 to do a non-destructive resize in order to allocate some space for Gentoo, and ever since I kept getting odd behaviour out of both GRUB and the NTLDR (Windows' boot loader). When I examined the partition table in fdisk, I got an error message saying that the MBR and at least one of the boot records was invalid... anyway, what I am trying to say is that probably PartitionMagic did something nasty.

I'm using QTPartEd/PartEd next time. :)
Top
Post Reply

16 posts • Page 1 of 1

Return to “Installing Gentoo”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic