Insmod problem with busybox 1.4.2

[Evert Meulie]

Eehh, that is exactly what I did. My command was:

insmod -f bs.ko
(bs.ko was present in the current directory)


This returned:

insmod: -f.ko: no module by that name found


Regards,
	Evert


Stephen Beaver wrote:
> You need to provide the module name. - insmod -f keyspan' to force
> installation of he keyspan.ko module for example.
> 
> 
> On 9/24/07 1:37 PM, "Evert Meulie" <evert at meulie.net> wrote:
> 
>> Hi!
>>
>> I'm having some minor problems with insmod/busybox 1.4.2. I'm trying to
>> force-load a module using
>> 'insmod -f'
>>
>> When I try this on the system, I get:
>>
>> insmod: -f.ko: no module by that name found
>>
>> .
>> That would suggest the insmod version does not support this parameter.
>> So then I tried 'insmod' and
>> I get:
>>
>> BusyBox v1.4.2 (2007-09-13 12:57:14 CEST) multi-call binary
>>
>> Usage: insmod [OPTION]... MODULE [symbol=value]...
>>
>> Load the specified kernel modules into the kernel
>>
>> Options:
>>         -f      Force module to load into the wrong kernel version
>>         -k      Make module autoclean-able
>>         -v      Verbose output
>>         -q      Quiet output
>>         -L      Lock to prevent simultaneous loads of a module
>>         -o NAME Set internal module name to NAME
>>         -x      Do not export externs
>>
>> So it looks like '-f' is supported anyway...?
>>
>>
>>
>> Greetings,
>> Evert
>>
>>
>> _______________________________________________
>> busybox mailing list
>> busybox at busybox.net
>> http://busybox.net/cgi-bin/mailman/listinfo/busybox
> 
>