I have genkernel 3.1.6. I tried rebuilding the kernel 2.6.11-r11 and it errored out after building the kernel -- somewhere during the initrd, I think. Here's a piece of the log ... the whole log is attached: if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.11-gentoo-r11; fi * Copying config for successful build to /etc/kernels/kernel-config-x86-2.6.11-gentoo-r11 * initrd: >> Initializing... * Gentoo Linux Genkernel; Version 3.1.5^[[0m * ERROR: Could not extract udev binary cache! * -- Grepping log... -- * -- End log... -- * Please consult /var/log/genkernel.log for more information and any * errors that were reported above. * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * /var/log/genkernel.log so that your issue can be dealt with effectively.
Created attachment 61187 [details] genkernel log
Run emerge sync, emerge the latest genkernel and make sure you run etc-update on gnekernel.conf. Reopen if issue still occurs.
(In reply to comment #2) > Run emerge sync, emerge the latest genkernel and make sure you run etc-update on > gnekernel.conf. Reopen if issue still occurs. I've actually done that. I was going to close this as "unable to reproduce" because only one of my machines is doing this. Something genkernel is looking for seems to have gotten corrupted on this one machine. I took a brief look at the script genkernel is calling to do this, but nothing jumped out at me. I also tried re-emerging "udev" and that didn't help. So ... time to dig into the udev debugging, I think, unless someone has some bright ideas for me.
(In reply to comment #3) Well ... I tried a few other simple things and nothing seemed to help. I finally decided it was time for extreme measures -- reinstall, drop back to devfs, or something like that. In any event, I cleaned out just about everything from /etc/portage/package.keywords, did an "emerge -e system" and installed "devfsd". Something in this must have fixed it; genkernel now completes successfully, although I haven't attempted to boot the new kernel yet. I suspect it was the "emerge -e system" that fixed it.
Strange... generally this is caused by the config file not updating after updating genkernel but not updating genkernel.conf with etc-update.
