Run depmod -av as root to update the module dependencies in the modules.dep
file.   This happens on reboot automaticly for most distros, however I
forgot this would be neccessary in this case.   If the modules are in
standard locations, you do not need to tell it the path, though there are
ways of telling depmod to look for them.  Checkout "man
depmod/insmod/modprobe/rmmod " in turn.  Problems may occur if you are not
using a standard kernel (rolled your own from source) or the modules were
not compiled.  Have a look at the modules directory and make sure they are
there. (not at my machine so cannot give exact path.)  

BillK

* if this doesnt work, try posting details such as distro, version, whether
you compiled your own kernel (and details that may affect module
compilation) which may give some further insight into the problem.

> 
> Nov 17 08:08:03 linux modprobe: modprobe: Can't locate module
> binfmt-0064
> Nov 17 08:08:32 linux insmod: Note: /etc/conf.modules is more recent
> than /lib/modules/2.2.14-5.0/modules.dep
> 
> Can I assume correct that I gotta tell it the full pathname for
> binfmt_aout?
> ...and do I need to add the same line in
> /lib/modules/2.2.14-5.0/modules.dep as I've put into conf.modules ?
> 
> /Kai

