Bug#293569: Add megaraid to /etc/mkinitrd/modules doesn't work out
On Tue, Feb 08, 2005 at 11:07:04AM -0200, Martin Alain Kretschek wrote:
> I've tried to add megaraid to /etc/mkinitrd/modules but still doesn't work out
> I've modified the /etc/mkinitrd/modules as sugested by Horms...
> ~# cat /etc/mkinitrd/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
> Then I've installed the kernel-package for 686-smp (I used my
> machine's mirror (apt-move generated) to avoid new dowload, I've
> checkeout and this is the last kernel-image package available):
> ~# dpkg -i /mirrors/debian/pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb
> Selecting previously deselected package kernel-image-2.6.8-2-686-smp.
> (Reading database ... 23224 files and directories currently installed.)
> Unpacking kernel-image-2.6.8-2-686-smp (from
> .../kernel-image-2.6.8-2-686-smp_2.6.8-13_i386.deb) ...
> Setting up kernel-image-2.6.8-2-686-smp (2.6.8-13) ...
> /usr/sbin/mkinitrd: add_modules_dep_2_5: modprobe failed
> FATAL: Module megaraid2 not found.
> WARNING: This failure MAY indicate that your kernel will not boot!
> but it can also be triggered by needed modules being compiled into
> the kernel.
> Searching for GRUB installation directory ... found: /boot/grub .
> Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst .
> Searching for splash image... none found, skipping...
> Found kernel: /vmlinuz-2.6.8-2-686-smp
> Found kernel: /vmlinuz-2.4.27-2-686-smp
> Updating /boot/grub/menu.lst ... done
> So I've checked out mkinitrd works as expected:
> ~# mount /boot/initrd.img-2.6.8-2-686-smp /mnt/ -o ro,loop
> ~# cat /mnt/loadmodules
> modprobe -k megaraid
> modprobe -k vesafb > /dev/null 2>&1
> modprobe -k fbcon 2> /dev/null
> modprobe -k unix 2> /dev/null
> modprobe -k megaraid2
> modprobe -k sd_mod
> ~# cat /mnt/linuxrc.conf
> Maybe the problem is the order of modules on loadmodules as we can see
> on loadmodules file megaraid is the first module and it should be just
> before megaraid2 (that won't load because it doesn't exist on kernel
> 2.6.8) is this correct or the order doesn't matter?
I don't think the order is that important.
Though perhaps megaraid doesn't support your card,
or perhaps it needs something else.
Ok, I just checked, yes, it seems to need scsi_mod.
scsi_mod doesn't seem to need anything else.
So could you try adding scsi_mod before megaraid
> Then I've boot the machine and get the expected "Kernel Panic".
If it fails again could you please paste the boot log like you
did in your original post? That information is often quite