USB Mouse issue
Hi all :))
I've recently installed a USB mouse, and I want it to run with
HIDBP. I have USB and USB_UHCI (and USB_DEVICEFS) built into the kernel and I successfully use my printer thru the USB interface. No problem with that, with a 2.4.18 kernel.
The USB mouse support I have it as a module, as well as the input
core support. Well, I do:
$ insmod input
$ insmod usbmouse and I have a char device with major 180, minor 16 (first USB
mouse, per Documentation/devices.txt). I load the modules by hand because the default 'above' settings for modprobe with this modules want to install keybdev and others.
My system log says:
<30>Apr 2 21:30:32 kernel: usb.c: registered new driver usb_mouse <30>Apr 2 21:30:32 kernel: input0: Logitech USB-PS/2 Trackball on usb1:2.0 <30>Apr 2 21:30:32 kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
that is, seems to detect the mouse properly, doesn't it?
But when I do 'gpm -m mouse -p -t imps2' I have a 'ENODEV'. Same
if I try to open 'mouse' with cat or the like, always ENODEV:
crw-r--r-- 1 root root 180,16 mouse
Is the node correct? I'm doing all this as root, so no permission
problems should arise :? and I've tested too 13,32 and 13,63 nodes, too, no one worked :( (same: ENODEV).
I don't want to use the /dev/input/... interface, since this
mouse should work with HIDBP. Must I use any additional module? If so, why the kernel is not telling me anything about unresolved symbols, lack of support, etc...? Must I use another minor?
Thanks in advance :)
Raúl Núñez de Arenas Coronado
Signature · 2 lines
Linux Registered User 88736 http://www.pleyades.net & http://www.pleyades.net/~raulnac
Quoted 4 lines · DervishD
But when I do 'gpm -m mouse -p -t imps2' I have a 'ENODEV'. Same
if I try to open 'mouse' with cat or the like, always ENODEV:crw-r--r-- 1 root root 180,16 mouse
No, this interface (Major 180, minor 16) is long out of date. You have to use the input core now.
greg k-h
Hi Greg :)
Greg KH dixit:
Quoted 5 lines
Quoted 3 lines
But when I do 'gpm -m mouse -p -t imps2' I have a 'ENODEV'. Same
if I try to open 'mouse' with cat or the like, always ENODEV:crw-r--r-- 1 root root 180,16 mouseNo, this interface (Major 180, minor 16) is long out of date. You have to use the input core now.
And that means activate INPUT_MOUSEDEV and load the module, ok,
but then, usbmouse does anything? Is it necessary for the USB mouse? Right now I have INPUT activated, but INPUT_MOUSEDEV not. I have INPUT_EVDEV activated, which is supposed to work for the Wacom Graphire digitizer (I have one too), but because the Configure.help file says so, in USB_MOUSE I don't see such advise :?
If usbmouse depends on INPUT_MOUSEDEV it should say it in the
Configure.help entry...
Excuse me, none of the above was needed, just created the node
(char 13,64) and run gpm saying that the mouse is of 'evdev' type. No INPUT_MOUSEDEV needed :) Just one curiosity: the usbmouse module shows as 'unused', in fact is 'evdev' the one used by 'gpm', but if I unload the usbmouse module (which I can do even with gpm running) then gpm stops working! I mean, the usbmouse module can be rmmod'ed but it is in use! Is this a bug? I'm afraid I must mark this module as not autocleanable :((( and it will remain loaded even if I stop using the mouse. Any advice?
Thanks for the information, Greg, you've saved me a few hours of
testing ;))
Raúl Núñez de Arenas Coronado
Signature · 2 lines
Linux Registered User 88736 http://www.pleyades.net & http://www.pleyades.net/~raulnac
Quoted 11 lines · DervishD
Hi Greg :)
Greg KH dixit:
Quoted 5 lines
Quoted 3 lines
But when I do 'gpm -m mouse -p -t imps2' I have a 'ENODEV'. Same
if I try to open 'mouse' with cat or the like, always ENODEV:crw-r--r-- 1 root root 180,16 mouseNo, this interface (Major 180, minor 16) is long out of date. You have to use the input core now.
And that means activate
INPUT_MOUSEDEVand load the module, ok,
but then, usbmouse does anything? Is it necessary for the USB mouse?
The ONLY reason you would want to use the usbmouse driver is if you are building an embedded system. Please read the configuration help files about this.
What you want is the hid driver. Use that, and select INPUT_MOUSEDEV.
Quoted 9 lines
Excuse me, none of the above was needed, just created the node
(char 13,64) and run gpm saying that the mouse is of 'evdev' type. NoINPUT_MOUSEDEVneeded :) Just one curiosity: the usbmouse module shows as 'unused', in fact is 'evdev' the one used by 'gpm', but if I unload the usbmouse module (which I can do even with gpm running) then gpm stops working! I mean, the usbmouse module can be rmmod'ed but it is in use! Is this a bug? I'm afraid I must mark this module as not autocleanable :((( and it will remain loaded even if I stop using the mouse. Any advice?
No, it's not a bug, it's the way the author wants it. The module does not show up as being used as it would be a bit hard to unplug your mouse or keyboard and then try to unload the module :)
thanks,
greg k-h
Hi Greg :)
Thanks for your help about this issue :)
Greg KH dixit:
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
No, this interface (Major 180, minor 16) is long out of date. You have to use the input core now.
And that means activate
INPUT_MOUSEDEVand load the module, ok,
but then, usbmouse does anything? Is it necessary for the USB mouse?The ONLY reason you would want to use the usbmouse driver is if you are building an embedded system. Please read the configuration help files about this.
Which one, Configure.help? I've read the entry for usbmouse and I
didn't found any info :?
Quoted 1 line
What you want is the hid driver. Use that, and select
INPUT_MOUSEDEV.
Which advantages has this method. I mean, the mouse works with
gpm and usbmouse, and that is all I need. Maybe X problems?
Quoted 6 lines
Quoted 3 lines
but it is in use! Is this a bug? I'm afraid I must mark this module as not autocleanable :((( and it will remain loaded even if I stop using the mouse. Any advice?
No, it's not a bug, it's the way the author wants it. The module does not show up as being used as it would be a bit hard to unplug your mouse or keyboard and then try to unload the module :)
Didn't think about that, obviously ;))) The fact that I never
hotunplug a USB device doesn't mean it cannot be done ;)) Anyway, this renders the autoclean feature unusable for that module ¿true?. So, you must unload it by hand or, better, built into core.
Thanks for your kindness, Greg, and for clarifying all that for
me. I owe you a beer if you come to Spain sometime.
Raúl Núñez de Arenas Coronado
Signature · 3 lines
Linux Registered User 88736 http://www.pleyades.net & http://www.pleyades.net/~raulnac Quite embarrased of being spanish...
Quoted 11 lines · DervishD
Greg KH dixit:
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
No, this interface (Major 180, minor 16) is long out of date. You have to use the input core now.
And that means activate
INPUT_MOUSEDEVand load the module, ok,
but then, usbmouse does anything? Is it necessary for the USB mouse?The ONLY reason you would want to use the usbmouse driver is if you are building an embedded system. Please read the configuration help files about this.
Which one, Configure.help? I've read the entry for usbmouse and I
didn't found any info :?
The help entry for CONFIG_USB_MOUSE says:
Say Y here only if you are absolutely sure that you don't want to use the generic HID driver for your USB keyboard and prefer to use the keyboard in its limited Boot Protocol mode instead.
This is almost certainly not what you want.
This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called usbmouse.o. If you want to compile it as a module, say M here and read <file:Documentation/modules.txt>.
If even remotely unsure, say N.
Based on that, I would hope it would have enough info to scare you from trying to use it :)
Quoted 4 lines
Quoted 1 line
What you want is the hid driver. Use that, and select
INPUT_MOUSEDEV.Which advantages has this method. I mean, the mouse works with
gpm and usbmouse, and that is all I need. Maybe X problems?
Please use the HID driver, it will work out much better in the long run.
Quoted 11 lines
Quoted 6 lines
Quoted 3 lines
but it is in use! Is this a bug? I'm afraid I must mark this module as not autocleanable :((( and it will remain loaded even if I stop using the mouse. Any advice?
No, it's not a bug, it's the way the author wants it. The module does not show up as being used as it would be a bit hard to unplug your mouse or keyboard and then try to unload the module :)
Didn't think about that, obviously ;))) The fact that I never
hotunplug a USB device doesn't mean it cannot be done ;)) Anyway, this renders the autoclean feature unusable for that module ¿true?. So, you must unload it by hand or, better, built into core.
Yes, "autoclean" does not like usb drivers (among others.) I don't think any distro uses that anymore.
Glad it's working for you.
greg k-h