On Sat, 2 May 2009, Sean Hildebrand wrote: > >> Here are the pertinent lines: > >> > >> May 2 20:32:50 lithium kernel: usbcore: registered new interface driver hiddev > >> May 2 20:32:50 lithium kernel: input: CH PRODUCTS CH COMBATSTICK USB > >> as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input8 > >> May 2 20:32:50 lithium kernel: generic-usb 0003:068E:00F4.0001: > >> input,hidraw0: USB HID v1.00 Joystick [CH PRODUCTS CH COMBATSTICK USB] > >> on usb-0000:00:1d.0-1/input0 > >> May 2 20:32:50 lithium kernel: usbcore: registered new interface driver usbhid > >> May 2 20:32:50 lithium kernel: usbhid: v2.6:USB HID core driver > >> > >> And here's the unabridged kernel log from that boot, in case there's > >> anything else useful in there: http://pastebin.com/m13e77ed7 > >> > >> To be clear, the device does not work in 2.6.29 and 2.6.30 at all, but > >> after being unplugged and plugged back in under 2.6.28 and earlier, it > >> would function. > > > > It would help to see a usbmon trace showing what happens when you plug > > in the joystick after booting without it, under 2.6.30-rc. See the > > instructions in the kernel source file /Documentation/usb/usbmon.txt. > > > > Alan Stern > > > > > > As you asked, here's the output of usbmon, plugging in the joystick. > > http://deiz2.ath.cx/usbmon-joystick.txt It looks like your joystick needs the NOGET quirk. You can test this by setting the "quirks=" parameter in the usbhid module: modprobe usbhid quirks=0x68e:0xf4:0x8 before plugging in the joystick. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
