An external USB keypad I'd like to use gets recognised as a USB HID device, but it is not functional when Linux is booted. It does work when plugged into a Windows desktop and it does work while in grub, but not when the system has booted.
The device is visible on the USB port (05a4:8003):
$ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 002: ID 046d:c078 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05a4:8003 Ortek Technology, Inc.
dmesg shows no error when the device gets connected:
[ 466.932272] usb 1-1.2: new full-speed USB device number 4 using ehci_hcd [ 467.026740] usb 1-1.2: New USB device found, idVendor=05a4, idProduct=8003 [ 467.026745] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 467.026756] usb 1-1.2: Product: USB Keypad [ 467.026758] usb 1-1.2: Manufacturer: Keypad [ 467.027939] input: Keypad USB Keypad as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input13 [ 467.028099] hid-generic 0003:05A4:8003.0004: input,hidraw1: USB HID v1.10 Keyboard [Keypad USB Keypad ] on usb-0000:00:1a.0-1.2/input0 [ 467.029600] input: Keypad USB Keypad as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input14 [ 467.029726] hid-generic 0003:05A4:8003.0005: input,hidraw2: USB HID v1.10 Mouse [Keypad USB Keypad ] on usb-0000:00:1a.0-1.2/input1
The input/event devices are created, but not responding. I wonder whether it is problematic that the device gets registered twice, as Keyboard input and as Mouse input.
I'm testing on a Ubuntu 13.04 system. The intended target system is a Raspberry Pi with Rasbian. Since the problem appears on Rasbian in the same way I'm thinking it is Linux related.
How can I debug this further? Any idea what could cause this unresponsive behaviour?