[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Persisting insmod problems (Re: [BusyBox] busybox insmod problem)
From:       "K.-P. =?iso-8859-15?q?Kirchd=F6rfer?=" <kapeka () epost ! de>
Date:       2004-04-27 19:19:16
Message-ID: 200404272119.16421.kapeka () epost ! de
[Download RAW message or body]

Am Montag, 26. April 2004 20:34 schrieb Manuel Novoa III:
> On Mon, Apr 26, 2004 at 11:58:38AM -0400, Charlie Brady wrote:
> > 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 not seeing this problem.  I just tried and busybox insmod
> successfully loaded aes.o.

It needs check_tainted_modules set in kernel; bb insmod is not the pb.

kp


_______________________________________________
busybox mailing list
busybox@mail.busybox.net
http://codepoet.org/mailman/listinfo/busybox


[prev in list] [next in list] [prev in thread] [next in thread]