warning: cound not generate /etc/modprobe.conf
reopen with a *lot* more information please.
this is ppc64 install time issue
grabbing as this is for ppc64
from discussions in irc last this ... this is affecting ppc32 as well as ppc64. Seems like it's a script problem of some sort.... curious
I'd like to know where does this show up, because it seems my chroots are behaving... so is modules-update.
I'm new here so I don't know if this is the right place for this.. apologies in advance...
It seems to affect amd64 as well. When following the handbook to install after configuring the kernel and beginning configuration of modules in section 7.e running modules-update. After looking through modules-update error seems to be generated by generate-modprobe.conf. generate-modprobe.conf seems to be looking in wrong location for kernel. It seems to be looking for the /lib/modules/<kernel version> path used to boot the live cd with. For example I booted with the smp kernel so my path was /lib/modules/2.6.5-gentoo-smp, however, The path of me generated kernel was /lib/modules/2.6.5-gentoo so it failed with the error "warning: cound not generate /etc/modprobe.conf" generated by modules-update due to generate-modprobe.conf failing.
My workaround was to ln -s /lib/modules/2.6.5-gentoo /lib/modules/2.6.5-gentoo-smp
I needed the modules working to boot with my sata drive otherwise I would have simply done it after booting the new install.
Well I honestly don't see an issue here anymore. It would appear the 2004.2 release profile for ppc64 is working so unless someone has an honestly to gosh recreation scenario, my fork is ready to stick in this bug.
and now... as promised!
Stick a fork in it!