Jason Kraftcheck wrote:
ben wrote:
note 1 : the mouse works fine in kernel 2.4.18, but not in kernel
2.4.22 - on the same machine.
Have you tested without X or gpm running? When I upgraded to 2.4.22 I
noticed some issues when X tried to open /dev/input/mice before
mousedev was loaded.
note 2: lsmod while running 2.4.18 shows
input 3456 0 [keybdev mousedev hid]
lsmod while running 2.4.22 shows
input 3456 0 [mousedev]
I presume from this that for some reason hid is not using input, but
I can't figure out why!
That's strage. I don't know if it is supposed to be or not, as I
linked most of the USB subsystem (including HID) into my kernel rather
than building them as modules.
Do you get a USB event when you connect your mouse? You should see
something like the following in /var/log/messages:
Sep 11 10:37:55 localhost kernel: hub.c: new USB device 00:1d.0-1,
assigned address 13
Sep 11 10:37:55 localhost kernel: input: USB HID v1.10 Mouse
[Microsoft Microsoft USB Mouse] on usb1:13.0
this is what I get:
Sep 12 12:09:48 zeus kernel: mice: PS/2 mouse device common for all mice
Sep 12 12:17:21 zeus kernel: hub.c: new USB device 00:1d.0-1, assigned
address 2
Sep 12 12:17:21 zeus kernel: hiddev0: USB HID v1.10 Mouse [Logitech USB
Optical Mouse] on usb1:2.0
note that your mouse connects to input. mine seems to connect to
hiddev0.. maybe thats the problem!!
will have a bit of a play.
