CH joysticks not working

[Ákos Maróy]

Ville Ranki: I have submitted a patch for this to upstream kernel. I hope it is included in Ubuntu kernel ASAP if it is accepted. http://www.spinics.net/lists/linux-input/msg19380.html

OR: I can't seem to make my CH Fighterstick Pro and my CH Pro Throttle work on my Karmic Koala (9.10) 64 bit system. The CH Pro Pedals joystick seems to work just fine on the same system.

Interestingly, the joysticks do register:

Code:

[ 2892.341212] usb 2-2.1: new low speed USB device using ehci_hcd and address 26
[ 2892.478972] usb 2-2.1: configuration #1 chosen from 1 choice
[ 2892.581231] generic-usb: probe of 0003:068E:00F3.001C failed with error -71
[ 2905.162801] usb 2-2.1: USB disconnect, address 26
[ 2907.950527] usb 2-2.1: new low speed USB device using ehci_hcd and address 27
[ 2908.089320] usb 2-2.1: configuration #1 chosen from 1 choice
[ 2908.099219] input: CH PRODUCTS CH FIGHTERSTICK USB as /devices/pci0000:00/0000:00:04.1/usb2/2-2/2-2.1/2-2.1:1.0/input/input28
[ 2908.099411] generic-usb 0003:068E:00F3.001D: input,hidraw3: USB HID v1.00 Joystick [CH PRODUCTS CH FIGHTERSTICK USB ] on usb-0000:00:04.1-2.1/input0

and they do show up using jstest:

Code:

$ jstest /dev/input/js0 | head
Driver version is 2.1.0.
Joystick (CH PRODUCTS CH FIGHTERSTICK USB ) has 5 axes (X, Y, Z, Hat0X, Hat0Y)
and 19 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6, BtnDead, BtnA, BtnB, BtnC, BtnX, BtnY, BtnZ).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0:-32767 1: 0 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0:-32767 1:-32767 2: 0 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0:-32767 1:-32767 2:-32767 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0:-32767 1:-32767 2:-32767 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0:-32767 1:-32767 2:-32767 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:oAxes: 0: 0 1:-32767 2ff 14:off 15:off 16:off 17:off 18:off

but no matter how I move the joystick, there's no effect.

this is the case for the CH FigherStick Pro and the CH Pro Throttle. interestingly, a CH Pro Pedal works fine in the same system.

the same joysticks work fine on an Ubuntu 8.10 system.

was there some major change in the kernel that made the joystick not work?

see also http://ubuntuforums.org/showthread.php?t=1363249 and http://forums.x-plane.org/index.php?showtopic=42738

[Thigmark (marks-millerhilifes)]

Same issue. CH FLIGHTSTICK PRO and PRO PEDALS worked in 9.04, but only the PRO PEDALS have worked since upgrading to 9.10. Sees the FLIGHTSTICK, but doesn't read any of the inputs.

$ jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (CH PRODUCTS CH FLIGHTSTICK PRO) has 5 axes (X, Y, Z, Hat0X, Hat0Y)
and 4 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn).
Testing ... (interrupt to exit)
Axes: 0: -5406 1: -3716 2:-32767 3: 0 4: 0 Buttons: 0:off 1:off 2:off 3:off

The old trick of removing and reconnecting the USB cable does not work.

[Ákos Maróy (akos-maroy)]

on the x-plane.org forum, a workaround has been suggested: after plugging in the joysticks, run "lsusb -v" - and afterwards, the joysticks start to work magically.

still, this is quite cumbersome, and there's no reason this shouldn't 'just work'

[Thigmark (marks-millerhilifes)]

Had to run "lsusb -v" as sudo, to get it to work, but at least I have a work around now. Thanks Akos.

I agree, it should 'just work', like it did before 9.10

[adriangoodyer (adriangoodyer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.

Please run the following command which will attach necessary information:

apport-collect BUGNUMBER
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Jaunty Jackalope (9.04)

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

[Thigmark (marks-millerhilifes)]

Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mark 2837 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7bf8000 irq 22'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,18491890,00100101'
   Controls : 35
   Simple ctrls : 20
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=b949d26c-cb00-45c3-bbe0-a28928641027
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcCmdLine: root=/dev/mapper/m1l-root ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-18-generic N/A
 linux-firmware 1.26
RfKill:

Uname: Linux 2.6.31-18-generic x86_64
UserGroups: adm admin audio backuppc bacula cdrom dialout fax fuse lpadmin mail netdev plugdev sambashare tape video
WpaSupplicantLog:

dmi.bios.date: 07/16/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.40
dmi.board.name: X58 SuperComputer
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.40:bd07/16/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58SuperComputer:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[adriangoodyer (adriangoodyer)]

Thanks for providing the requested apport information. This bug now has enough information provided for a developer to begin work so I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time on this bug and making Ubuntu better.

[Ville Ranki (ville-ranki)]

I marked #108875 as duplicate of this bug. The bug still exists in Lucid, so the subject could be updated.

I also confirm that the lsusb-workaround works, but is cumbersome.

This bug has been around for years, and still no fix :(

[ArdyFalls (afalls)]

This is still broken in Kubuntu 10.10
Linux earth 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

[ArdyFalls (afalls)]

This is still broken in 11.04 amd64

[Ákos Maróy (akos-maroy)]

yes, unfortunately it still is :(

[Lfarkas (lfarkas)]

the same is true for rhel-6. but why the lsusb -v working???

[Ville Ranki (ville-ranki)]

I have submitted a patch for this to upstream kernel. I hope it is included in Ubuntu kernel ASAP if it is accepted.

http://www.spinics.net/lists/linux-input/msg19380.html

[penalvch (penalvch)]

Ákos Maróy, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Ville Ranki (ville-ranki)]

This bug still exists, as my patch isn't yet in the kernel. I don't know how long it takes for it to appear but seems to be pretty slow.

[penalvch (penalvch)]

Action items from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500834/comments/31 not provided. As well, patch details as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/500834/comments/32 not provided. In addition, Fix Committed is wrong Status as per https://wiki.ubuntu.com/Bugs/Status .

[Ville Ranki (ville-ranki)]

This can be moved to Invalid, the bug does not happen anymore. Moved to Fix Committed by mistake.