Modules init script fails

[Timo]

Hmm, seems I'm stuck (searched the forums and tried to fix the problem, but I'm lost).

I've setup the box like my other 40+ gentoo installs I've made so far (at least I hope).

I usually build a new kernel using genkernel --udev all, and then place the modules I need into /etc/modules.autoload.d/kernel-2.6. During boot, the modules init script complains that it can't find the modules specified. I tried (for sanity) to load the modules with their full path, it still complains.

When I login, a modprobe works, as well as an insmod with the full path, however, just an insmod <modulename> doesn't work. The output of uname -a is correct, and ls /usr/lib/`uname -r`/ shows the correct directory contents.

My questions:

- How does insmod/modprobe know where to pull the modules from?
- genkernel automatically creates an initial ramdisk, could it be that there's some trouble with that? Can I tell genkernel to include my network driver (3c59x)?
- To my knowledge, the modules initscript just does call modprobe, so why doesn't modprobe work in the modules init script?

[Gherald]

as a workaround, you can try putting the modprobe/insmod commands in /etc/conf.d/local.start

[Timo]

I don't like "unclean" solutions

If it's a bug, we should fix it.
If it's a feature, we should document it.