I am reading http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1 as the installation guide. I am installing from LiveCD with a 2.4.21-gss kernel. But instead of using a 2.4 kernel, I emerged a 2.6 kernel with: emerge gentoo-dev-sources and compiled it (including make modules_install). Following that, in Code Listing 23 I am instructed to run modules-update, but that gives me: cdimage boot # modules-update Warning: could not generate /etc/modprobe.conf! Looking at modules-update source tells me the problem is caused by a call to generate-modprobe.conf: cdimage boot # generate-modprobe.conf modprobe: Can't open dependencies file /lib/modules/2.4.21-gss/modules.dep (No such file or directory) In /lib/modules I only have /lib/modules/2.6.3-gentoo-r1 I hope this is just a documentation bug, and that I will be able to run modules-update when I reboot and run my new 2.6 kernel. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
I rebooted the machine and it loaded the 2.6 kernel. Then I was able to issue a modules-update that succeded and created a modprobe.conf. So I guess the documentation should say that modules-update should be run when you are running your new kernel.
I'm wondering if we can fix the scripts to allow for another kernel (one that is installed but not booted). modules-update doesn't have this option and generate-modprobe.conf doesn't either (or at least not that I saw); depmod does, but I'm not sure this'll help. @agriffis: any input?
Yes, I agree that the best solution would be to fix the scripts, either allowing for an option to specify what kernel version you are running, or some way of detecting it (but this could cause problems if a person installed multiple kernels maybe?)
I am also having this issue on a new stage3 install. It's not really an option for me to do it after reboot, as it will load my networking module, and I need that to log on remotely to finish the install.
Fixed in baselayout-1.9.0 and module-init-tools-3.0-r2 You need to merge both of them, there aren't auto-dependencies between them right now. Now you can specify --assume-kernel=x.x.x to modules-update. If it doesn't work, please re-open the bug (and give me lots of juicy debugging feedback)
