Mouse is detected as keyboard

suleyma · May 4, 2013, 3:40pm

Hi everybody!

My mouse “Thermalright Leetgion Hellion” is detected as keyboard in OpenSUSE 12.3. What to do?

linux-j9bc:~ # grep -i mouse /var/log/Xorg.0.log
29.370] (==) NOUVEAU(0): Silken mouse enabled
29.882] (II) config/udev: Adding input device Holtek USB Gaming Mouse (/dev/input/event0)
29.882] () Holtek USB Gaming Mouse: Applying InputClass “evdev keyboard catchall”
29.882] () Holtek USB Gaming Mouse: Applying InputClass “LocalKeyboard”
29.882] (II) Using input driver ‘evdev’ for ‘Holtek USB Gaming Mouse’
29.882] () Holtek USB Gaming Mouse: always reports core events
29.882] () evdev: Holtek USB Gaming Mouse: Device: “/dev/input/event0”
29.882] (–) evdev: Holtek USB Gaming Mouse: Vendor 0x4d9 Product 0xa072
29.882] (–) evdev: Holtek USB Gaming Mouse: Found keys
29.882] (II) evdev: Holtek USB Gaming Mouse: Configuring as keyboard
29.882] (II) XINPUT: Adding extended input device “Holtek USB Gaming Mouse” (type: KEYBOARD, id 8)

hcvv · May 4, 2013, 4:44pm

Hello, welcome here.

We have a hidden feature on the forums that is very important using CODE tags around copied/pasted computer text. You get those tahs by clicking on the # button in the tolbar of the post editor.

There is no need to repost the above This is just for future posting.

knurpht · May 4, 2013, 5:53pm

Hi, welcome

What you don’t tell, is whether the mouse works :D. If it does, don’t bother about it.

suleyma · May 4, 2013, 8:53pm

Unfortunately it does not work.
However, there is periodically reaction to the red button. А search box appears.
The pointer does not move at all.

arvidjaar · May 5, 2013, 9:41am

Please paste output of

udevadm info -q all -n /dev/input/event0

suleyma · May 5, 2013, 11:45am

linux-j9bc:~ # udevadm info -q all -n /dev/input/event0

P: /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0/event0
N: input/event0
S: input/by-id/usb-Holtek_USB_Gaming_Mouse-event-kbd
S: input/by-path/pci-0000:00:1a.1-usb-0:2:1.0-event-kbd
E: DEVLINKS=/dev/input/by-id/usb-Holtek_USB_Gaming_Mouse-event-kbd /dev/input/by-path/pci-0000:00:1a.1-usb-0:2:1.0-event-kbd
E: DEVNAME=/dev/input/event0
E: DEVPATH=/devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0/event0
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_MODEL=USB_Gaming_Mouse
E: ID_MODEL_ENC=USB\x20Gaming\x20Mouse
E: ID_MODEL_ID=a072
E: ID_PATH=pci-0000:00:1a.1-usb-0:2:1.0
E: ID_PATH_TAG=pci-0000_00_1a_1-usb-0_2_1_0
E: ID_REVISION=0126
E: ID_SERIAL=Holtek_USB_Gaming_Mouse
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030102:030000:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=Holtek
E: ID_VENDOR_ENC=Holtek
E: ID_VENDOR_ID=04d9
E: MAJOR=13
E: MINOR=64
E: SUBSYSTEM=input
E: USEC_INITIALIZED=58337

In windows 7, the mouse works fine on the same PC.

arvidjaar · May 5, 2013, 12:03pm

Yes, it is indeed considered as keyboard by udev. Could you additionally show

udevadm info -q all -p /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0

suleyma · May 5, 2013, 12:13pm

With great pleasure:

linux-j9bc:~ # udevadm info -q all -p /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0

P: /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0
E: DEVPATH=/devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0
E: EV=120013
E: ID_BUS=usb
E: ID_FOR_SEAT=input-pci-0000_00_1a_1-usb-0_2_1_0                                                                       
E: ID_INPUT=1                                                                                                           
E: ID_INPUT_KEY=1                                                                                                       
E: ID_INPUT_KEYBOARD=1                                                                                                  
E: ID_MODEL=USB_Gaming_Mouse                                                                                            
E: ID_MODEL_ENC=USB\x20Gaming\x20Mouse                                                                                  
E: ID_MODEL_ID=a072                                                                                                     
E: ID_PATH=pci-0000:00:1a.1-usb-0:2:1.0                                                                                 
E: ID_PATH_TAG=pci-0000_00_1a_1-usb-0_2_1_0                                                                             
E: ID_REVISION=0126                                                                                                     
E: ID_SERIAL=Holtek_USB_Gaming_Mouse                                                                                    
E: ID_TYPE=hid                                                                                                          
E: ID_USB_DRIVER=usbhid                                                                                                 
E: ID_USB_INTERFACES=:030101:030102:030000:                                                                             
E: ID_USB_INTERFACE_NUM=00                                                                                              
E: ID_VENDOR=Holtek                                                                                                     
E: ID_VENDOR_ENC=Holtek                                                                                                 
E: ID_VENDOR_ID=04d9                                                                                                    
E: KEY=e080ffdf01cfffff fffffffffffffffe                                                                                
E: LED=1f                                                                                                               
E: MODALIAS=input:b0003v04D9pA072e0110-e0,1,4,11,14,k77,7D,7E,7F,ram4,l0,1,2,3,4,sfw                                    
E: MSC=10
E: NAME="Holtek USB Gaming Mouse"
E: PHYS="usb-0000:00:1a.1-2/input0"
E: PRODUCT=3/4d9/a072/110
E: PROP=0
E: SUBSYSTEM=input
E: TAGS=:seat:
E: UNIQ=""
E: USEC_INITIALIZED=58318

arvidjaar · May 5, 2013, 1:22pm

Try to boot with usbhid.quirks=0x4d9:0xa072:0x40 appended to kernel command line. So far it looks like kernel finds keyboard “personality” and stops there. Adding this parameter tells kernel device supports more than single input functionality.

suleyma · May 5, 2013, 2:05pm

I have tried. Nothing has changed.

My GRUB2 Optional Kernel Command Line Parameter looks like this:

 resume=/dev/disk/by-id/ata-WDC_WD5000AACS-00ZUB0_WD-WCASU0807241-part5 splash=silent quiet showopts usbhid.quirks=0x4d9:0xa072:0x40

arvidjaar · May 5, 2013, 2:45pm

Could you upload output of dmesg to SUSE Paste ?

suleyma · May 5, 2013, 3:30pm

I have done it. URL: SUSE Paste

arvidjaar · May 5, 2013, 9:35pm

I’m afraid this device is not well behaving

    2.015009] usb 4-2: new full-speed USB device number 2 using uhci_hcd
    2.217538] usb 4-2: New USB device found, idVendor=04d9, idProduct=a072
    2.217541] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    2.217544] usb 4-2: Product: USB Gaming Mouse
    2.217546] usb 4-2: Manufacturer: Holtek
    2.226778] input: Holtek USB Gaming Mouse as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input0
    2.226835] input: Holtek USB Gaming Mouse as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/input/input1
    2.226880] hid-generic 0003:04D9:A072.0001: input,hidraw0: USB HID v1.10 Keyboard [Holtek USB Gaming Mouse] on usb-0000:00:1a.1-2/input0
    2.233876] hid-generic 0003:04D9:A072.0002: usage index exceeded
    2.234104] hid-generic 0003:04D9:A072.0002: item 0 2 2 2 parsing failed
    2.234353] hid-generic: probe of 0003:04D9:A072.0002 failed with error -22
    2.238611] hid-generic 0003:04D9:A072.0003: hiddev0,hidraw1: USB HID v1.10 Device [Holtek USB Gaming Mouse] on usb-0000:00:1a.1-2/input2

The message “usage index exceeded” suggests that device returns bogus information. Kernel driver for Holtek keyboard contains explicit workaround for similar problem (driver simply discards information returned by device and uses built-in “known good” one). May be this needs similar treatment. I would suggest to open bug report on http://bugzilla.novell.com/ against kernel (you can use your forum account to login), attach dmesg, “lsusb -v” output and explain your problem - device is not recognized as mouse.

suleyma · May 6, 2013, 7:37am

Thank you very much Arvidjaar - Wise Penguin. You saved me from the endless reboots.
Tonight I will open a bug report, as you advised.
Thank you again!

suleyma · May 7, 2013, 7:35pm

I have opened the bug report https://bugzilla.novell.com/show_bug.cgi?id=818806