Try mk_initrd -h, you'll get a few options mk_initrd -k "nameofkernel" -i "nameofinitrdfile" -m "ft.o whateverothermoduleyouneed.o" would perhaps work regards Anders On Thursday 22 November 2001 23:25, PCHintz wrote:
On Thursday 22 November 2001 12:15 am, you wrote:
* PCHintz (chris@pchintz.com) [011121 23:38]:
I am recompiling my 2.4.4 SuSE 7.2 kernel with the Win4Lin patches. My system is running RAID 0 hardware (Promise FastTrak100-lite) controlled with reiserfs. I am not able to boot because the orignal initrd file points to the reiserfs & ft modules of the orignal kernel. How do I create a new initrd with the newly compiled kernel & modules when I can't boot
into it? RH has a mkinitrd X Y command where X is the initrd filename
and Y is which kernel version is relevant. Is there something similar in
Yes, make sure /etc/rc.config INITRD_MODULES is correct and use /s bin/mk_initrd.
If you are building your own kernel why don't you just compile stuff that you know you will always need into the kernel though?
t
Thanks for the replies. When I recompiled the kernel I changed the EXTRAVERSION in the Makefile to save the original modules. Running mk_initrd seems to only create an initrd from the current kernel/modules. Things would be straightforward but because I am using hardware RAID, the ft.o (promise fastrack) module must be loaded into ramdisk to be able to access the drives. I somehow need to be able to create a kernel/module initrd for the new kernel, while booted in the old kernel, so it will be able find the ft.o module when booting the new kernel/modules. Might try to see if the RH command will work under SuSE. I guess my other option would be to not modify the Makefile and take my chances with overwriting the existing modules. Hopefully the current initrd would still be able to find the rt.o module if it was in the same location. Any thoughts?
PCHintz