well for modprobe to work you have to run depmod to calculate out the dependancies of the module.
You see each module depends on certain functionality in the kernel to be present. Much of the time this functionality is found in the form of more modules. Depmod figures out these relationships for your.. Like how snd-whatever needs to have snd module loaded before it will work, that sort of thing.
Otherwise you can use insmod /path/to/module.filename to try to insert the module into protected memory and if you have everything pre-loaded that it needs for basic functionality it will work.
Generally, however the 'make install' script runs depmod as a matter of course, but not always.
Module files are located in /lib/modules/<kernelversion>/ also.
So run depmod, then double check /lib/modules/<kernelversion>/
You can find your kernel version easily by using the command "uname -a".
To find files easily you can use "locate" and "find" commands/tools. Locate depends on a simple database that has been made of your filing system.. generally this is generated every day at a certain time via a cronjob. However you can manually update it to reflect recent changes in the filing system by running "updatedb". It will generate a lot of disk activity, though, as it trolls thru your directory system, so it may take some time.
To use locate you simply go:
locate filename
and it will display everything that has that filename string it it's name.
Find is the other way. Find is a command that basicly does a recursive 'ls' of a directory.. I like to go:
find /directoryname/ |grep filename
to find specific files, but that's lazy way. Find has some powerfull options beyond a simple ls-style search and can use expressions and look for files or directories and whatnot. See the man file.
But if a module is not located then either you haven't run depmod, or it isn't present in the correct /lib/module/<kernelversion> directory....
Sometimes the scripts that make isntall use are stupid and may put it in the wrong directory or whatnot, in that case you can just find the module and copy it over and run depmod then modprobe it.
Also if you've run make correctly it will probably have the compiled module laying around in your source tree your working with and sometimes finding that and copying it over will work.
Probably though you just have to run depmod.
also, at least on my system, there is a alsaconf script that I use to configure and setup my sound card in Debian so that it loads and is configured at boot-up time. Saves me the effort of having to manually create the files that you need for oss emulation and such like that. See the alsa project website for details.. also they will have notes and have a wiki with a page dedicated to each alsa module they have.
Sometimes, and especially with ISA sound cards you'll have to pass options to the module at modprobe/insmod time for specific configurations, too.
also if you install the modulname-source package for a module thru apt-get be sure to take a look at the documentation aviable with the package at /usr/share/doc/<packagename>
Looks like you use modules-assistant with official Debian kernels mostly.
Facebook
Twitter