Problems with insmod & modprobe

[Scott Kirkpatrick]

It doesn't appear to be that problem.  All the modules are listed with 
full paths in modules.dep.  The weird thing is that the binary of 
busybox that is working is v1.00-pre8 that we build on 10/8/2004 and 
rebuilding it causes modprobe/insmod to not work.  The problem is that 
we don't know what gcc or uclibc version was used to build it, although 
it should be the same that we are using now.


Scott


Egor Duda wrote:

>Scott Kirkpatrick wrote:
>  
>
>>It's a 2.6 kernel.  That's my next step in debugging it.  I couldn't
>>find anything in the archives and didn't know if this was a known issue.
>>    
>>
>
>Could it be possibly this one?
>http://www.busybox.net/lists/busybox/2004-October/012936.html
>
>It only affects modprobe, but not insmod, though.
>
>egor
>  
>

-- 
----------------------------------------
Scott Kirkpatrick
Nexus Technologies, Inc.
1851 Plaza Dr.
Hickory, NC 28602

(828) 294-2716 Phone
(828) 238-8417 Cell
(828) 294-2716 Fax (call voice first)

Email: skirkpatrick at nexus-tech.net
AIM: KirkpatrickNexus
Jabber: skirkpatrick at jabber.org
MSN: skirkpatrick at nexus-tech.net
----------------------------------------