Baslinux mailing list

[Lee Forrest <lforrestster AT gmail.com>]

On Fri, Dec 15, 2006 at 10:07:39PM +1300, 3aoo-cvfd AT dea.spamcon.org wrote:
> Lee Forrest wrote:
> >
> > Except the mouse doesn't work, but that's just a matter of 
> > moving some more modules over. 
> 
> What kind of mouse is it?  Serial?  PS/2?  USB?
> Is /dev/mouse correctly set?

It's USB. Following the example of my debian, I made /dev/mouse
a symlink to /dev/usbmouse (created the device file).

I cped the USB/HID and mousedev modules over from my debian OS,
those being the ones that show up with 'cat /proc/modules' there.

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:

BL/proc/modules:

unix                   13196   7
mousedev                3496   0 (unused)
usbmouse                1528   0 (unused)
usbcore                53600   0 [usbmouse]

Here's a /dev/vcs1 screenshot of the last screenful of bootup messages:

ip_tables: (C) 2000-2002 Netfilter core
team                                    VFS: Mounted root (ext2
filesystem).                                            Freeing unused
kernel memory: 96k freed                                         kmod:
failed to exec /sbin/modprobe -s -k net-pf-1, errno = 2
init started:  BusyBox v1.01 (2006.01.02-09:39+0000) multi-call binary
kmod: failed to exec /sbin/modprobe -s -k net-pf-1, errno = 2
The superblock could not be read or does not describe a correct
ext2            filesystem.  If the device is valid and it really contains
an ext2              filesystem (and not swap or ufs or something else),
then the superblock         is corrupt, and you might try running
e2fsck with an alternate superblock:          e2fsck -b 8193 <device>

[I ran e2fsck on the partition from debian and it checked out
clean. ???]

Using /lib/modules/2.4.19/kernel/drivers/usb/usb-uhci.o
insmod: unresolved symbol usb_release_bandwidth_R6d7b732a
insmod: unresolved symbol usb_alloc_bus_R5d9d35f3
insmod: unresolved symbol usb_inc_dev_use_R8164c87c
insmod: unresolved symbol usb_register_bus_R5646c924
insmod: unresolved symbol usb_root_hub_string_Ra68718f0
insmod: unresolved symbol usb_free_dev_Rf4e0464a
insmod: unresolved symbol usb_deregister_bus_Ra08a520a
insmod: unresolved symbol usb_claim_bandwidth_Rfd10eac6
insmod: unresolved symbol usb_check_bandwidth_R8ad7380c
insmod: unresolved symbol usb_disconnect_Rdfbd1ba7
insmod: unresolved symbol usb_free_bus_R231e4c48
insmod: unresolved symbol usb_connect_R2f288b02
insmod: unresolved symbol usb_alloc_dev_Rac3158f7
insmod: unresolved symbol usb_new_device_R56556b3a
Using /lib/modules/2.4.19/kernel/drivers/usb/hid.o
insmod: unresolved symbol __usb_get_extra_descriptor_R9924c496
insmod: unresolved symbol usb_submit_urb_R9a00aaf8
insmod: unresolved symbol usb_get_report_R9a4f33cb
insmod: unresolved symbol usb_unlink_urb_R41125ca4
insmod: unresolved symbol usb_deregister_R0857ae05
insmod: unresolved symbol usb_set_idle_Rc82f5cf5
insmod: unresolved symbol usb_string_Rd2174f89
insmod: unresolved symbol usb_get_class_descriptor_R9492a243
insmod: unresolved symbol usb_register_R17f6028e
Using /lib/modules/2.4.19/kernel/drivers/usb/usbcore.o
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
Using /lib/modules/2.4.19/kernel/drivers/usb/usbmouse.o
usb.c: registered new driver usb_mouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
Using /lib/modules/2.4.19/kernel/drivers/input/mousedev.o
mice: PS/2 mouse device common for all mice
Using /lib/modules/2.4.19/kernel/net/unix/unix.o
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Please press Enter to activate this console.

And the mouse still doesn't work. Tried commenting out all the
USB/HID and mousedev insmods and rebooting, to see if the mouse
would work with just the new /dev/usbmouse, but no luck.

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?

Lee