mkinitrd doesn't copy modules to initrd tree [new problem]

[GJones]

Edit: duh, I am an idiot. Forgot to run the all-important depmod -a on the new kernel. Duh.

I'm trying to test the Liquorix kernel to see if the patchset has any performance impact. To save time I unpacked the Debian package and manually installed the kernel and modules. The Liquorix kernel needs an initrd, and doesn't have device drivers built in, so I ran mkinitrd for it...

Code: Select all

mkinitrd -c -k 3.0.0-4.dmz.2-liquorix-686 -m ahci:sd_mod:ext4

The initrd was generated, but no modules were mentioned in the output, and boot failed because the root FS could not be mounted. When I looked in the intrd tree and in the decompressed initrd, I discovered that no modules whatsoever had been copied into the tree.

mkinitrd did not produce any error messages, and works fine for the generic Salix kernel. So why is it failing for this kernel?

[GJones]

Okay, got something else going on here... Despite the requisite modules being present the system still won't boot, because block devices aren't being generated in /dev - not even with udev added to the initrd.

Is there some kind of generic block device module that I need to add?

[gapan]

I don't know what a Liquiorix kernel is, but why don't you take the initrd from there too?

[GJones]

Because the Liquorix kernel is for Debian, which auto-generates initrds. One isn't provided with it.

(Thanks though. FWIW I wound up abandoning my attempt to set up the Liquorix kernel; it just wasn't worth it.)

[pevsner]

AlienBobs slackware wiki on kernelbuilding ( scroll about 1/2 down for creating an initrd) may be of help. He wrote a mkinitrd_command_generator shell script too.
http://wiki.alienbase.nl/doku.php?id=li ... elbuilding