Baslinux mailing list

["David Moberg" <davidjmoberg AT gmail.com>]

Lee Forrest wrote:
> BL/etc/rc:
>
> insmod -f usb-uhci
> insmod -f hid
> insmod -f usbcore
> insmod -f usbmouse
> insmod -f mousedev
> insmod -f unix
...
> But some of them wouldn't load:
...
> Using /lib/modules/2.4.19/kernel/drivers/usb/usb-uhci.o
> insmod: unresolved symbol usb_release_bandwidth_R6d7b732a
...
> I thought the kernel (and therefore the modules, I would
> think) were standalone. Why wouldn't the same modules
> load with the very same kernel?

The problem is the order in which you attempt to load the modules.
modprobe automatically finds the dependencies of a module and inserts
those first, then the module you requested to be inserted. With insmod
you must first load the helper modules, and then the main device
module. This is why modprobe is more complex than insmod. So you
should rearrange the above modules lines to look like this:

insmod -f usbcore       # core Linux USB subsystem - required
insmod -f usb-uhci      # driver for your USB host controller
insmod -f hid           # HID device driver - generic for mice, keyboards, 
etc.
insmod -f usbmouse      # This may be optional - normally you either use
this or hid. hid is better but also larger.
insmod -f mousedev
insmod -f unix          # depends on nothing but a kernel with networking 
support

Why do you have -f on every line? That should not be necessary unless
you are trying to insert a module into a different kernel than what it
was intended for.

David