On Thursday 19 March 2009, maximilian attems wrote: > > Recently kernels I built from upstream kernel source failed to boot > > after unpacking them because no modules got included in the initramfs > > initrd (and thus no root file system). > > This problem was solved after downgrading to m-i-t 3.4.1. > > how can i reproduce this? > > upgraded to latest m-i-t 3.7-pre9-1 and run depmod + mkinitramfs. > the generated initramfs had all modules i expect it to have.
You have to build a kernel from source while having the new m-i-t installed. And then install that kernel *without* running depmod (which is currently also not done by i-t). If you do run an extra depmod manually before calling i-t the problem will have fixed itself because depmod is then called differently than during the kernel build. I saw this issue after installing a kernel built from upstream source using 'fakeroot make deb-pkg' (i.e. without using kernel-package or anything). With the stable version of m-i-t kernels built that way install perfectly (using custom hook scripts to create the initrd and update grub etc.). You can probably also reproduce it by running the following sequence of commands, which should emulate the way the upstream kernel Makefile calls depmod (using any kernel version you have installed for <kvers>): # kvers=<kvers> # mkdir -p /tmp/lib/modules # cp -r /lib/modules/$kvers /tmp/lib/modules/ # rm /tmp/lib/modules/$kvers/modules.* # depmod -ae -F /boot/System.map-$kvers -b /tmp/ -r $kvers The file /tmp/lib/modules/<kvers>/modules.dep should then show the problem. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
