insmod works; modprobe fails

[quendor]

Why would 'insmod prism2_pci' work, but 'modprobe prism2_pci' fail?

# insmod prism2_pci
Using /lib/modules/2.4.19-gentoo-r7/net/prism2_pci.o

# modprobe prism2_pci
modprobe: Can't locate module prism2_pci

I have complied from source using '/usr/src/linux-2.4.19-gentoo-r7'. After running 'make modules_install', '/lib/modules/2.4.19-gentoo-r7' appears as expected. The module 'prism2_pci' is a wireless module compiled from source: 'linux-wlan-ng-0.1.14-pre6' Moreover, after installation prism2_pci is added to /lib/modules/2.4.19.../net/prism2_pci as expected.

I have run 'uname -r' and it shows the expected kernel version. I have run
'depmod -a' and examined /lib/modules/2.4.19.../modules.dep and see that the path to prism2_pci is there.

The only change that I have made to /etc/modules.d/aliases is to add an entry 'alias prism2_pci wlan0'

Finally, I have been able to get this all to work fine in Debian.

I am new to gentoo--but relatively familiar with other distros--and I have a feeling that maybe there is another level of indirection effecting modprobe and modules.dep that I am not totally aware of.

Any help welcome.

Thanks,

[flater]

Yeah, I had the same kind of problem but reversed. I could type modprobe <module> and no problems loading it, whereas insmod <same module> gave errormessages. As a severe n00b I don't understand the difference between the two commands, and as one works and does what I want, I basically don't care...

[Aruspex]

Could it be your /etc/modules.conf file? Try backing it up and doing a "update-modules" to regenerate it.

See also: man insmod, modprobe, depmod, modules.conf, update-modules...
_________________
"If you want to make an apple pie from scratch, you must first create the universe" -Carl Sagan

[rac]