2.2.16-gentoo-r3 Kernel Panic on boot [SOLVED]

EEPS · Last edited by EEPS on Mon Apr 24, 2006 4:34 am; edited 1 time in total

I just upgraded to the new gentoo-sources kernel and now it won't boot. It says something like "VFS: Cannot open root device" and "Please append a correct "root=" boot option" then it has a kernel panic and says unable to mount root fs on uknown-block(0,0). I had a very similar problem before, but that was due to not having my SATA drivers built into my kernel. This time I triple and quadruple checked to make sure they were getting built in (not module), and they are. I have SiS 5513 chipset and it is definently checked in my kernel config. One thing I noticed is that some modules are being built under driver/scsi called sata_sis.ko and sata_sx4.ko, and I don't know why they are as I have nothing under scsi that says to be built as a module. In the grub console, I can clearly see hd0 is the correct drive since I can cat out files on it in the grub terminal, and my devices.map is this:

skoalman · n00b Joined: 16 Oct 2004 Posts: 2 Location: Chicago, IL

i was having the same kernel panic problem. I have Silicon Image 3112 SATA controller and
had to have this chip supported in 2 places in the device driver section of my kernel config.
Under SCSI device support-->SCSI low level drivers-->Serial ATA (SATA) support i had to
select the option for my SATA controller and under ATA/ATAPI/MFM/RLL support i had to select
Silicon Image chipset support.

When i only had support for my SATA controller under SCSI low level drivers i kept getting a
kernel panic. After i added support for my SATA controller under ATA/ATAPI/MFM/RLL the kernel
booted fine.

EEPS · Posted: Mon Apr 24, 2006 4:34 am Post subject:

Ahhhh yes, that was it. I completely forgot about that. That was what was being built as a module. I built it in the kernel and it worked perfectly. Thaks a lot, just watch me be back here next kernel release with the same stupid question! :oops: