Ok got it to work. Thanks to Joe Morris for providing part of the missing pieces. However, once I supplied the list of modules on the command line, mkinitrd still failed to mount /. I had to build and load the LOOP module before running mkinitrd. thanks Joe. I am now running with my 3Ware ATA Raid driver as a module and not in the kernel. :-)
Jim Norton wrote, On 07/16/2003 05:36 PM:
I am trying to build in initrd fail for a kernel that I compiled. I want to use my 3Ware ATA raidcard as a module. So I made sure the module was added to the /etc/sysconfig/kernel file and did the following:
==================================================================== 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")
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.
Any ideas what I am doing wrong?
IIANM, the sysconfig file is only used for the defaults. Try adding -m <modules you want to put in the initrd.>
-- 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