[BusyBox] /bind/modprobe problems

[Fabian]

I found out that the problem only occurs when the according module
isn't mentioned in the modules.dep file, a depmod -a solved the
problem for me.

Fabian. 


On Fri, 15 Oct 2004 23:54:48 +0400, egor duda <deo at corpit.ru> wrote:
> Martin Bogomolni wrote:
> > Same problem here.  What's odd, is that modprobe worked fine with the 1.0-pre7
> > code in our lab.
> >
> > I'm also going the same route, as far as stripping down the modprobe from
> > modutils for the current software release.  I don't see anything major in the
> > code checkins that would have broken modprobe, with the possible exception of:
> >
> > --Patch from Egor Duda
> > --Attached patch prevents modprobe from trying to call 'insmod (null)'
> > --whenever nonexistent module is either passed to modprobe via command
> > --line or mentioned in modules.dep
> >
> > I'm thinking there is an error in the patch that now causes modprobe to
> > utterly ignore modules.dep. :)
> 
> can you provide your modprobe.dep file? you can also try to check with
> strace if busybox is finding and using it at all.
> 
> egor.
>