reassign 293569 initrd-tools On Fri, Feb 04, 2005 at 12:56:46PM +0000, [EMAIL PROTECTED] wrote: > Package: kernel-image-2.6.8-2-686-smp > Version: 2.6.8-2 > Severity: important > Justification: prevents boot > > The package runs mkinitrd to build an initial ramdisk > The hardware is using the Dell 'megaraid' controller which was supported as > megaraid2 under the 2.4 series kernels. > mkinitrd probes the root and finds megaraid2 and add the line to > loadmodules in the initrd: > > 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 > > the version of the megaraid module shipped with the 2.6 kernel is v2, and > should support the controller just fine
Hi Robin, The name of this module changed from megaraid2 to megaraid for 2.6 as far as I can see. Unfortunately the tool the generates the ramdisk doesn't know how to work this out. Actually, I don't think we know how it could work this out, short of puting everything pluss the kitchen sink into the initrd image. Could you please try adding megaraid to /etc/mkinitrd/modules and rebuilding the intird image using mkinitrd on the command line. This will likely result in an ininitrd image that tries to modprobe megaraid2 and megaraid, but only the latter will succeede as only it will be inculded in the initrd image as only it exists in 2.6. Hopefully this will allow your system to boot. I have reassigned this bug to initrd-tools as the problem seems to lie there rather than with the kernel image itself. > running mkinitrd: > > uk2a:/home/robin# mkinitrd -o /tmp/initrd.img 2.6.8-2-686-smp > /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. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
