Re: Kernel panic on boot with kernel 2.6.10 (SATA SiL 3112A issue maybe)
Andro,
I was actually troubleshooting this same issue and replied because able
to figure out that I needed to change my /dev/hdX to /dev/sdX. I
remember trying to do that in the 2.6.9 kernel to no avail, getting the
same error as with the sata_sil module not loading. Perhaps we have
different SATA controllers.
mine via lspci:
0000:01:0b.0 RAID bus controller: Silicon Image, Inc. (formerly CMD
Technology Inc) SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev
02)
what controller are you running?
Also, sometime ago I added sata_sil to /etc/mkinitrd/modules but it
never worked for me. Perhaps when you upgrade a kernel it uses this
file to make the initrd.img and thus included that module? I don't have
time right now to take it out and try to break the system but maybe
that's why mine is working.
act:/etc/mkinitrd# cat modules
# /etc/mkinitrd/modules: Kernel modules to load for initrd.
#
# This file should contain the names of kernel modules and their
# arguments
# (if any) that are needed to mount the root file system, one per line.
# Comments begin with a `#', and everything on the line after them are
# ignored.
#
# You must run mkinitrd(8) to effect this change.
#
# Examples:
#
# ext2
# wd io=0x300
scsi_mod
sd_mod
libata
sata_sil
ext3
On Mon, Feb 28, 2005 at 12:56:12PM +0200, Andrey Andreev wrote:
> Anthony Tippett wrote:
> >For me this issue raised after the 2.6.7 kernels. I saw somewhere they
> >changed how SATA drives were stored in /dev and made them scsi devices
> >(sda, sdX...) instead of IDE (hda...)
>
> Yep, I had figured that one out (see my initial post).
>
> >My kernel root resided on /dev/hde2, so I tried telling grub to look for
> >it on /dev/sda2 ( I had no other scsi drives). However, there was still
> >an issue because the SATA_SIL module wasn't being loaded by initrd. I
> >think it was left out of the kernel src
>
> Yep, I moved the root, but as SATA_SIL was not loading I still could not
> boot. (see thread with matt zagrabelny) SATA_SIL was in source and was
> compiled, but was not loaded by the initrd.
>
> >Anyways, I finally got 2.6.10 to work by just changing the kernel root
> >in grub to /dev/sda2 instead of /dev/hde2. The best way to do this is
> >by letting the grub menu come up on boot up and pressing the "e" key to
> >edit the boot line. If it works, you can then edit the menu.lst and
> >change the kopt (in my case "kopt=root=/dev/sda2 ro") and then change
> >the 2.6.10+ kernel lines also.
> >
> >title Debian GNU/Linux, kernel 2.6.10-1-k7
> >root (hd0,1)
> >kernel /boot/vmlinuz-2.6.10-1-k7 root=/dev/sda2 ro
> >initrd /boot/initrd.img-2.6.10-1-k7
> >savedefault
> >boot
>
> Yep, I did that and it still did not work (see same thread).
>
> >I guess my point is that you don't have to add the sata_sil module to
> >initrd anymore as I thought I saw it in a kernel changelog as a bug and
> >it's been fixed.
>
> I had to edit initrd - sata_sil.ko was present in the initrd image, but
> loadmodules did not try to load it. It is peculiar if it does that for
> you. Any idea why that might be different? I have the exact same version
> of the kernel.
>
> Regards,
>
> Andro
>
> --
> Andrey Andreev
> University of Helsinki
> Dept. of Computer Science
--
Anthony Tippett - Sports-IT - 425-443-3152
Reply to: