insmod not working by module name in Linux 2.4.30 / MIPS
Denys Vlasenko
vda.linux at googlemail.com
Thu Sep 30 21:55:07 UTC 2010
On Monday 27 September 2010 22:48, RiCH Busybox wrote:
> On Mon, 2010-09-27 at 07:49 +1000, Stuart Longland wrote:
> > On Sun, Sep 26, 2010 at 10:03:50PM +0100, RiCH Busybox wrote:
> > > Hi,
> > >
> > >
> > > I am trying to upgrade Busybox from busybox-1.1.0.5VT to 1.17.2 on a
> > > Belkin F5D8235 v1 router. (Cross compiling under ubuntu x64 with
> > > supplied toolchain , which works all fine using supplied old busybox
> > > etc.)
> > >
> > > I am currently stuck because insmod won't load from the module name
> > > alone, although it is fine pointing it to the module with full path -
> > > the problem being loading via name is hard coded in a sysinit binary so
> > > I need loading via name to work :)
> > >
> > > Here is sample output. (USB storage module was allready loaded with full
> > > path in sysinit, the only one that had a full path specified)
> >
> > > / # lsmod
> > > / # insmod rtl
> > > insmod: can't read 'rtl': No such file or directory
> > > / # insmod /lib/modules/2.4.30/kernel/drivers/usb/storage/usb-storage.o
> > > insmod: can't insert
> > > '/lib/modules/2.4.30/kernel/drivers/usb/storage/usb-storage.o': unknown
> > > symbol in module or invalid parameter
> > > / # modinfo rtl
> > > filename: /lib/modules/2.4.30/kernel/drivers/net/rtl8366/rtl.o
> > > license: GPL
> > > / #
> >
> > Have you perhaps tried 'modprobe'? My understanding is that insmod
> > always did require the full path (from memory this has been the case
> > since modutils days in kernel 2.0), and that 'modprobe' was the tool if
> > you just wanted to recall a module by name rather than by file.
>
> Hi Stuart,
>
> I just looked in insmod.c
>
> "
> //usage: IF_FEATURE_2_4_MODULES("[OPTIONS] MODULE ")
> //usage: IF_NOT_FEATURE_2_4_MODULES("FILE ")
> "
>
> ------
>
> "
> /* Compat note:
> * 2.6 style insmod has no options and required filename
> * (not module name - .ko can't be omitted).
> * 2.4 style insmod can take module name without .o
> * and performs module search in default directories
> * or in $MODPATH.
> */
> "
>
> I have also tried specifying its location in $MODPROBE var and that
> doesn't work either so assume it is in fact a bug?
Did you enable FEATURE_2_4_MODULES in your 1.17.2 build?
--
vda
More information about the busybox
mailing list