CH produts do not initialize

[bazzaah]

I have a CH Products combatcstick and pro-pedals. Neither seems to initialise at boot though both are recognised by jscal. A quick unplug and replug gets them working but would rather have the problem resolved. TIA for any help.

here's the output of dmesg | grep usb

[ 2.991642] usbcore: registered new interface driver usbfs
[ 2.991675] usbcore: registered new interface driver hub
[ 2.991709] usbcore: registered new device driver usb
[ 2.993386] usb usb1: configuration #1 chosen from 1 choice
[ 3.095366] usb usb2: configuration #1 chosen from 1 choice
[ 3.199363] usb usb3: configuration #1 chosen from 1 choice
[ 3.303714] usb usb4: configuration #1 chosen from 1 choice
[ 3.408140] usb usb5: configuration #1 chosen from 1 choice
[ 3.439862] usb 2-1: new low speed USB device using uhci_hcd and address 2
[ 3.512499] usb usb6: configuration #1 chosen from 1 choice
[ 3.622389] usb 2-1: configuration #1 chosen from 1 choice
[ 3.628235] usb usb7: configuration #1 chosen from 1 choice
[ 3.635470] usb 2-1: USB disconnect, address 2
[ 3.732896] usb usb8: configuration #1 chosen from 1 choice
[ 4.831798] usb 7-8: new high speed USB device using ehci_hcd and address 3
[ 4.969143] usb 7-8: configuration #1 chosen from 1 choice
[ 5.550093] usbcore: registered new interface driver hiddev
[ 5.550160] usbcore: registered new interface driver libusual
[ 5.786745] usb 5-1: new low speed USB device using uhci_hcd and address 2
[ 5.963722] usb 5-1: configuration #1 chosen from 1 choice
[ 6.221137] usb 5-2: new low speed USB device using uhci_hcd and address 3
[ 6.397980] usb 5-2: configuration #1 chosen from 1 choice
[ 6.415057] usb-storage: device found at 3
[ 6.415060] usb-storage: waiting for device to settle before scanning
[ 6.434883] input: USB HID v1.00 Joystick [CH PRODUCTS CH COMBATSTICK USB] on usb-0000:02:06.0-1
[ 6.446864] input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on usb-0000:02:06.0-2
[ 6.446887] usbcore: registered new interface driver usbhid
[ 6.446891] usbcore: registered new interface driver usb-storage
[ 6.446902] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 6.655211] usb 2-1: new low speed USB device using uhci_hcd and address 3
[ 6.837210] usb 2-1: configuration #1 chosen from 1 choice
[ 6.860205] input: USB HID v1.11 Keyboard [Cypress WirelessUSB] on usb-0000:00:1d.1-1
[ 6.893215] input,hiddev96: USB HID v1.11 Mouse [Cypress WirelessUSB] on usb-0000:00:1d.1-1
[ 11.405364] usb-storage: device scan complete
[ 17.731567] usbcore: registered new interface driver xpad
[ 17.731574] drivers/usb/input/xpad.c: driver for Xbox controllers v0.1.6
[ 18.321375] usbcore: registered new interface driver iforce

[Karl Ostmo (kostmo)]

I can confirm this problem with a CH Flightstick USB joystick on Ubuntu 8.04. On the initial connect, the output of "dmesg | grep usb" is:

[ 126.832253] usb 1-2: new low speed USB device using ohci_hcd and address 2
[ 127.047204] usb 1-2: configuration #1 chosen from 1 choice
[ 127.256344] usbcore: registered new interface driver hiddev
[ 127.265044] input: CH PRODUCTS CH FIGHTERSTICK USB as /devices/pci0000:00/0000:00:1e.0/0000:02:0e.0/usb1/1-2/1-2:1.0/input/input8
[ 127.308347] input,hidraw0: USB HID v1.00 Joystick [CH PRODUCTS CH FIGHTERSTICK USB ] on usb-0000:02:0e.0-2
[ 127.308384] usbcore: registered new interface driver usbhid
[ 127.308391] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver

After this initial connect, jstest finds the Flightstick, but does not respond to button presses. After plug cycling, jstest works flawlessly. Full output of "dmesg | grep usb" then reads:

[ 18.689406] usbcore: registered new interface driver usbfs
[ 18.689447] usbcore: registered new interface driver hub
[ 18.701327] usbcore: registered new device driver usb
[ 19.748169] usb usb1: configuration #1 chosen from 1 choice
[ 20.948322] usb usb2: configuration #1 chosen from 1 choice
[ 21.476041] usb usb3: configuration #1 chosen from 1 choice
[ 126.832253] usb 1-2: new low speed USB device using ohci_hcd and address 2
[ 127.047204] usb 1-2: configuration #1 chosen from 1 choice
[ 127.256344] usbcore: registered new interface driver hiddev
[ 127.265044] input: CH PRODUCTS CH FIGHTERSTICK USB as /devices/pci0000:00/0000:00:1e.0/0000:02:0e.0/usb1/1-2/1-2:1.0/input/input8
[ 127.308347] input,hidraw0: USB HID v1.00 Joystick [CH PRODUCTS CH FIGHTERSTICK USB ] on usb-0000:02:0e.0-2
[ 127.308384] usbcore: registered new interface driver usbhid
[ 127.308391] /build/buildd/linux-2.6.24/drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[ 393.793299] usb 1-2: USB disconnect, address 2
[ 405.849181] usb 1-2: new low speed USB device using ohci_hcd and address 3
[ 406.064247] usb 1-2: configuration #1 chosen from 1 choice
[ 406.090481] input: CH PRODUCTS CH FIGHTERSTICK USB as /devices/pci0000:00/0000:00:1e.0/0000:02:0e.0/usb1/1-2/1-2:1.0/input/input9
[ 406.113401] input,hidraw0: USB HID v1.00 Joystick [CH PRODUCTS CH FIGHTERSTICK USB ] on usb-0000:02:0e.0-2

This procedure of unplugging and plugging back in must be repeated every time the computer is rebooted, which is especially inconvenient. Other joysticks I have connected (e.g. "Logitech, Inc. Dual Action Gamepad") work correctly on the first try.

Output of "lsusb":
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 068e:00f3 CH Products, Inc.
Bus 001 Device 001: ID 0000:0000

[Karl Ostmo (kostmo)]

Correction to above:
The joystick in question was a CH Products "Fighterstick" USB joystick.

Vendor website is here:
http://www.chproducts.com/retail/j_fighter_usb.html

Also listed on "Linux USB Device Overview" website:
http://www.qbik.ch/usb/devices/showdev.php?id=2844

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

[Ville Ranki (ville-ranki)]

This bug still exists in Intrepid's kernel.

Kernel version is 2.6.27-9-generic

[Ville Ranki (ville-ranki)]

Workaround: add the following lines in /etc/init.d/bootmisc.sh in the end of do_start:

/sbin/rmmod ehci_hcd
/sbin/modprobe ehci_hcd

[Leann Ogasawara (leannogasawara)]

Hi Ville,

Would you be willing to test the latest pre-release of Jaunty, currently Alpha 5 - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel. You should be able to test using a LiveCD. Please let us know your results. Thanks.

[Ville Ranki (ville-ranki)]

Ok, i'll try it.

[Ville Ranki (ville-ranki)]

I tested this on Jaunty alpha 5 and the bug still exists.

[Ville Ranki (ville-ranki)]

Has this been reported to kernel developers?

[nlinux (mekelly5)]

I'm seening this same bug on a fresh install of Jaunty. Has there been any solution to it?

[nlinux (mekelly5)]

The above workaround doesn't work for jaunty:

/sbin/rmmod ehci_hcd
/sbin/modprobe ehci_hcd

apparently ehci_hcd is not compiled as a module but is built directly into the kernel. The even tried installing later kernel versions from the kernel ppa, all the way up to 2.6.31rc3 which was just released and this bug is still there.