Ok thanks again for the information. Now how do I tell GRUB to use the new initrd for a given kernel image?
Jim Norton wrote, On 07/17/2003 12:56 AM:
Jim Norton wrote, On 07/16/2003 05:36 PM:
==================================================================== falcon:/boot # mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-2 using "/dev/sda1" as root device (mounted on "/" as "reiserfs")
Stated a bit differently, try "mkinitrd -k linux-2.4.21-2 -i initrd-linux-2.4.21-3 -m "reiserfs,3w-xxxx" (or a comma separated list of your modules, this was just a guess)
creating initrd "/boot/initrd-linux-2.4.21-2" for kernel "/boot/linux-2.4.21-2" (2.4.21) failed to mount image ====================================================================
The failure message is: failed to mount image.
No /boot/initrd-linux-2.4.21-2 file was created.
The initrd you created had no modules, because you gave it none. Only vmlinuz and vmlinuz.shipped get their modules from /etc/sysconfig/kernel. Therefore, it could not load your /
Thanks for the information. Somebody suggested that 3Ware cards/drivers are the problem. I guess he was having troubles with them. I on the other hand have nothing be great success with my 3Ware card ( 7500 - 4 port ). My issue is that I just want to load the 3Ware module from initrd and not compile it directly into the kernel.
Try the above and let us know. :)
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com