Persisting insmod problems (Re: [BusyBox] busybox insmod problem)

[Charlie Brady]

On Tue, 27 Jan 2004, Eric Spakman wrote:

> > > It seems that busybox insmod (busybox pre5, latest from CVS but also 
> > > previous versions) has problems loading the crypto modules from 
> > > kernel-2.4.24. It also has problems with the airo module (which uses 
> > > crypto)
> > > 
> > > # insmod aes
> > > Using /lib/modules/aes.o
> > > insmod: unresolved symbol crypto_unregister_alg
> > > insmod: unresolved symbol crypto_register_alg
> > > 
> > This means that the crypto core module is not loaded.
> > 
> The crypto core is loaded and the /proc/crypto interface is also 
> available. Using insmod from modutils-2.4.21 does work, so it must be 
> something with busybox insmod.

I'm also finding insmod to be unreliable (all versions 1.00-pre5 through 
1.00-pre10). Thanks to your hint I've fallen back to using insmod from 
modutils, which is working perfectly.

I'm happy to help debug if anyone has any suggestions. Target is mipsel, 
compiled against uClibc 0.9.19.

--
Charlie

A: Because we read from top to bottom, left to right.
Q: Why should i start my reply below the quoted text?