Either you have problems with your USB stack in the Linux kernel or
there is another program accessing the device already.
Chris
No, that's done be default to ensure that we get a cleanly initialized
driver. Maybe /var/log/messages has some helpful details.
Chris
Cheers,
Riku
Mar 1 19:52:35 HamServer kernel: [63184.660591] usb 2-2: new low speed USB
device using ohci_hcd and address 4
Mar 1 19:52:35 HamServer kernel: [63184.867575] usb 2-2: New USB device
found, idVendor=0fde, idProduct=ca01
Mar 1 19:52:35 HamServer kernel: [63184.867621] usb 2-2: New USB device
strings: Mfr=0, Product=1, SerialNumber=0
Mar 1 19:52:35 HamServer kernel: [63184.867663] usb 2-2: Product: Universal
Bridge
Mar 1 19:52:35 HamServer kernel: [63184.869971] usb 2-2: configuration #1
chosen from 1 choice
Mar 1 19:52:35 HamServer kernel: [63184.879003] generic-usb
0003:0FDE:CA01.000C: hiddev0,hidraw0: USB HID v1.10 Device [Universal
Bridge] on usb-0000:00:0f.4-2/input0
Mar 1 19:55:24 HamServer kernel: [63354.398098] usb 2-2: reset low speed
USB device using ohci_hcd and address 4
Mar 1 19:55:25 HamServer kernel: [63354.756474] generic-usb
0003:0FDE:CA01.000D: hiddev0,hidraw0: USB HID v1.10 Device [Universal
Bridge] on usb-0000:00:0f.4-2/input0
Mar 1 19:55:25 HamServer kernel: [63355.258336] usb 2-2: usbfs: process
1370 (wfrog) did not claim interface 0 before use
Mar 1 19:55:25 HamServer kernel: [63355.263377] usb 2-2: usbfs: process
1370 (wfrog) did not claim interface 0 before use
That looks suspiciously like you have some program probing the USB
devices and this is jamming the usbhid or hid driver.
Chris