This is probably super-basic, but this is my first "testing" kernel... I usually go after the precompiled packages, but I like 2.6 too much to wait. Anyway, I upgraded from the stock Fedora Core1 2.4 kernel which loads ext3 as a module. If I try that in 2.6 I get a kernel panic, so I built it into the kernel and everything is happy. During boot, however, the kernel still tries to load ext3.o as a module and yells at me. Along the same line, I can't get evdev to load early enough in the boot to let my synaptics touchpad load in time to allow a GUI startup screen...
So my first question is, how do I edit which modules are loaded with the kernel? Thus far I've just stuck a 'modprobe' or 'insmod' into rc.sysinit for each device I wish to load (sound, touchpad, etc.) but that loads too late in the bootup.
Related to that, with the loss of "make dep" I can't make a new initrd, so I'm using the 2.4 kernel's initrd... This wouldn't be a big deal, but without deps I am unable to compile a few things (like my precious NVidia drivers). What I really don't get is why I need initrd at all if I'm not loading ext3 as a module..?
I've asked these questions on Fedora boards and lists, but no one seems to know the answer, so TIA to whomever takes the time to point me in right direction.
Previous post
Sorry, I had cookies disabled, I'm actually not "anonymous"
re: Previous post
Fixed...
initrd in FC1
The initrd in FC1 is like every RH version before. Gunzip the initrd, mount it and change linuxrc in it. Details:
zcat /boot/initrd* > /tmp/initrd
mount -o loop /tmp/initrd /mnt/cdrom
vi /mnt/cdrom/linuxrc # remove unwanted insmod
umount /mnt/cdrom
gzip /tmp/initrd
mv /tmp/initrd.gz /boot/initrd*
Hope that helps.
Till Bubeck, t.bubeck@reinform.de
initrd in FC1
Useful. Thanks!