[BusyBox] Support for 2.6.x kernel modules in BusyBox 1.0.0-pre4
Rob Landley
rob at landley.net
Mon Dec 15 03:33:47 UTC 2003
On Sunday 14 December 2003 00:15, Erik Andersen wrote:
> On Sat Dec 13, 2003 at 05:51:24PM +0100, Arkadiusz Patyk wrote:
> > Hi,
> >
> > Insmod can't load modules on my 2.6 kernel.
> >
> > My config:
> > #
> > # Linux Module Utilities
> > #
> > CONFIG_INSMOD=y
> > # CONFIG_FEATURE_2_2_MODULES is not set
> > CONFIG_FEATURE_2_4_MODULES=y
> > CONFIG_FEATURE_2_6_MODULES=y
>
> If you disable CONFIG_FEATURE_2_4_MODULES but leave
> CONFIG_FEATURE_2_6_MODULES enabled, then does it work?
>
> -Erik
Sigh. I get halfway through doing something, and somebody else does it. Grad
school for you.
insmod isn't the only thing that changed. _all_ of the module commands
changed. Try doing an lsmod under 2.6.0-test11:
[root at dhcppc4 busybox-1.00-pre4]# ./busybox lsmod
lsmod: QM_MODULES: Function not implemented
The entire module subsystem changed. rmmod still seems to work. Dunno 'bout
modprobe, it's shelling out to insmod (I.E. trying to use the one on the
system. It helps to hork one's $PATH when testing to make sure it doesn't
find the built-in system utilities...)
Hmmm... Even with the fixed "standalone shell", modprobe still tries to call
the system insmod. Sigh...
Rob
More information about the busybox
mailing list