I compile a kernel(2.6.20) and produce an initramfs with sys-kernel/genkernel-3.4.7_pre5 with the needed modules(sata drivers for my chipset are selected as modules. multi device drivers are selected as modules). While creating the initramfs, genkernel says it copies the modules to the initramfs(dm* modules are copied to the image according to the output) and genkernel exits successfully. When I reboot the new kernel some of the modules are not loaded(missing??)( those starting with dm-* ) and my disk is unreachable. Thus preventing me to boot into my new system. Currently I am using a 2.6.19 based kernel that was built with genkernel(with the same options). When I boot this kernel I see the dm-* modules that are missing in 2.6.20 are loaded. The rest of the modules are same. Reproducible: Always Steps to Reproduce: 1. fire genkernel: genkernel --disklabel --dmraid --gensplash-res=1024x768 --gensplash=XXX --install --save-config --menuconfig --color --debuglevel=5 all 2. edit grub accordingly 3. reboot Actual Results: initramfs does not load needed dm-* modules. disk is unknown. prompt waits for proper disk name. Expected Results: initramfs loads needed dm-* modules and Gentoo boots. Two sata disks using sil3112 controller.
So what are the new module names, then? If you manually add them to /usr/share/genkernel/$arch/moduels_load under MODULES_DMRAID it works?
The module names are the same as always. The ones under /lib/modules/2.6.20-viper6/kernel/drivers/md/ dm-crypt.ko dm-multipath.ko faulty.ko raid10.ko dm-emc.ko dm-round-robin.ko linear.ko raid1.ko dm-mirror.ko dm-snapshot.ko multipath.ko raid456.ko dm-mod.ko dm-zero.ko raid0.ko xor.ko Genkernel says it adds dm-mod, dm-mirror, raid0, raid1, raid10 to the initramfs but when I reboot it loads modules for sil_sata and other stuff but there are no dm-mod, dm-mirror. The modules I mention are already in my /usr/share/genkernel/$arch/moduels_load . I will try again and be sure to remove reiser4 related stuff in menuconfig because I do not use them and genkernel says they are problematic. If it works voila! if it does not I will attach the genkernel log and initramfs if possible. (In reply to comment #1) > So what are the new module names, then? > > If you manually add them to /usr/share/genkernel/$arch/moduels_load under > MODULES_DMRAID it works? > (In reply to comment #1) > So what are the new module names, then? > > If you manually add them to /usr/share/genkernel/$arch/moduels_load under > MODULES_DMRAID it works? >
Did you use --dmraid when building your kernel (hint, you should)... ?
yes I did use.
Strange... genkernel uses MODULES_DMRAID when booting. Does it even *try* to load the dmraid modules? You should see it in the verbose output (Alt+F1 when you see your splash) of the kernel boot.
No it does not try to load dmraid modules. They just seem inexistent, like I have not used the --dmraid option. Now I will try with --evms2 as it seems to include modules used by --dmraid.
I used --lvm2(includes modules that the --dmraid option will embed) instead of --evms2 because the evms2 option required the evms package to be installed. It worked. Now my kernel is bootable. So how do I or you mark this bug? Do you need any further info?
I'll leave this open until the next stable genkernel release.
3.4.7 is out now...
I confirm that it is fixed :)
Closing so it disappears from my open bugs list :P
