[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

I'm losing it!



this post was:  (was usb mouse not recognised in kernel 2.4.22)
I have renamed it in order to try and clean up the mess again, and hopefully attract some more input.

thanks to all that have contributed so far, please continue!!

ok. here is where I am at:

latest kernel-2.4.22  compile using config from 2.4.18-bf2.4

in kernel 2.4.18-bf2.4 the usb mouse works perfectly.
lsmod shows:

Module                  Size  Used by    Tainted: P
mousedev                3744   1
usbmouse                1760   0  (unused)
hid                        18784   0  (unused)
usb-uhci               20676   0  (unused)
usbcore                48000   1  [usbmouse hid usb-uhci]
keybdev                 1664   0  (unused)
input                   3040   0  [mousedev usbmouse hid keybdev]

if i disconnect and then reconnect mouse it appears in messages as:
Sep 12 14:47:17 zeus kernel: usb.c: USB disconnect on device 2
Sep 12 14:47:20 zeus kernel: hub.c: USB new device connect on bus1/1, assigned device number 3 Sep 12 14:47:20 zeus kernel: input0: USB HID v1.10 Mouse [Logitech Logitech] on usb1:3.0


in kermel 2.4.22 lsmod shows:

Module                  Size  Used by    Not tainted
mousedev              3864   1
usbmouse              1820   0  (unused)
hid                       16708   0  (unused)
usb-uhci               21996   0  (unused)
usbcore                58464   1  [usbmouse hid usb-uhci]
keybdev                1696   0  (unused)
input                     3456   0  [mousedev usbmouse keybdev]

if i disconnect and then reconnect mouse it appears in messages as:
Sep 12 14:38:23 zeus kernel: usb.c: USB disconnect on device 00:1d.0-1 address 3 Sep 12 14:38:25 zeus kernel: hub.c: new USB device 00:1d.0-1, assigned address 4 Sep 12 14:38:25 zeus kernel: hiddev0: USB HID v1.10 Mouse [Logitech USB Optical Mouse] on usb1:4.0

From this I can see that in the working kernel the last line shows that input0 is picking up the mouse whereas the non working kernel shows hiddev0 picking up the mouse.

when compiling the new kernel if i select all of the hid options I get this result:
drivers/usb/usbdrv.o(.text+0xeaf5): In function `hidinput_hid_event':
: undefined reference to `input_event'
drivers/usb/usbdrv.o(.text+0xeb6e): In function `hidinput_hid_event':
: undefined reference to `input_event'
drivers/usb/usbdrv.o(.text+0xeb80): In function `hidinput_hid_event':
: undefined reference to `input_event'
drivers/usb/usbdrv.o(.text+0xebc5): In function `hidinput_hid_event':
: undefined reference to `input_event'
drivers/usb/usbdrv.o(.text+0xebe8): In function `hidinput_hid_event':
: undefined reference to `input_event'
drivers/usb/usbdrv.o(.text+0xec0a): more undefined references to `input_event' follow
drivers/usb/usbdrv.o(.text+0xeed3): In function `hidinput_connect':
: undefined reference to `input_register_device'
drivers/usb/usbdrv.o(.text+0xef31): In function `hidinput_connect':
: undefined reference to `input_register_device'
drivers/usb/usbdrv.o(.text+0xef65): In function `hidinput_disconnect':
: undefined reference to `input_unregister_device'
make: *** [vmlinux] Error 1

If I build the kernel without HID input layer support I do not get this message. from this I am guessing that HID input layer support is what I need to make the mouse work.

how do I go about fixing this?!!

or is it a problem with the kernel sources (which I kinda doubt) :p

once again, thanks to all that have contributed so far, I am getting the feeling that I need a kernel building guru to step in and sort out this mess I am in!







Reply to: