Logitech Rumble Gamepad F510 does not work

[NiBu]

Not all buttons and sticks of the device do work correctly in Ubuntu - they seem to be wrong calibrated. Because of this, playing native Linux games like Trine or Steel Storm with the gamepad is not possible.

Connecting the gamepad I get following dmesg output:
[28445.660054] usb 4-3: new full speed USB device number 2 using ohci_hcd
[28446.504708] Registered led device: xpad0
[28446.504858] input: Generic X-Box pad as /devices/pci0000:00/0000:00:12.1/usb4/4-3/4-3:1.0/input/input7
[28446.505403] usbcore: registered new interface driver xpad

Following values I get with the device information tool evtest (all gamepad sticks are in the center):
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0xc21e version 0x2019
Input device name: "Generic X-Box pad"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 304 (BtnA)
    Event code 305 (BtnB)
    Event code 307 (BtnX)
    Event code 308 (BtnY)
    Event code 310 (BtnTL)
    Event code 311 (BtnTR)
    Event code 314 (BtnSelect)
    Event code 315 (BtnStart)
    Event code 316 (BtnMode)
    Event code 317 (BtnThumbL)
    Event code 318 (BtnThumbR)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value 128
      Min -32768
      Max 32767
      Fuzz 16
      Flat 128
    Event code 1 (Y)
      Value -129
      Min -32768
      Max 32767
      Fuzz 16
      Flat 128
    Event code 2 (Z)
      Value 0
      Min 0
      Max 255
    Event code 3 (Rx)
      Value 128
      Min -32768
      Max 32767
      Fuzz 16
      Flat 128
    Event code 4 (Ry)
      Value -129
      Min -32768
      Max 32767
      Fuzz 16
      Flat 128
    Event code 5 (Rz)
      Value 0
      Min 0
      Max 255
    Event code 16 (Hat0X)
      Value 0
      Min -1
      Max 1
    Event code 17 (Hat0Y)
      Value 0
      Min -1
      Max 1
  Event type 21 (ForceFeedback)
    Event code 80 (Rumble)
    Event code 81 (Periodic)
    Event code 88 (Square)
    Event code 89 (Triangle)
    Event code 90 (Sine)
    Event code 96 (Gain)

Please tell me if there is more information needed to analyze/solve the problem.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-13-generic-pae 3.0.0-13.22
ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6
Uname: Linux 3.0.0-13-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: nibu 1714 F.... pulseaudio
 /dev/snd/controlC0: nibu 1714 F.... pulseaudio
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a102,00100101'
   Controls : 39
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'U0x46d0x81b'/'USB Device 0x46d:0x81b at usb-0000:00:12.2-1, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:081b'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 6144
   Mono: Capture 6144 [100%] [30.00dB] [on]
Date: Fri Dec 9 23:44:12 2011
HibernationDevice: RESUME=UUID=9fc47957-b92c-4fc9-af79-3a96457290e1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic-pae root=UUID=324423fa-4d5f-457a-9283-c77803c319a9 ro quiet splash nomodeset video=uvesafb:mode_option=1680x1050-24,mtrr=3,scroll=ywrap vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.0.0-13-generic-pae N/A
 linux-backports-modules-3.0.0-13-generic-pae N/A
 linux-firmware 1.60
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to oneiric on 2011-09-28 (72 days ago)
WifiSyslog:
 Dec 9 22:49:15 nibu-GA-MA790XT-UD4P kernel: [ 565.473572] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
 Dec 9 23:39:20 nibu-GA-MA790XT-UD4P wpa_supplicant[1022]: WPA: Group rekeying completed with 00:1c:4a:d4:db:2e [GTK=CCMP]
dmi.bios.date: 07/12/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8g
dmi.board.name: GA-MA790XT-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8g:bd07/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-MA790XT-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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 by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.2-rc1'.

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'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[Gregor Riepl (onitake)]

Has this been fixed upstream?

The joypad works fine on 3.2.0-30 (precise), and I can calibrate all its axes using jscal.
Note that the Xbox360 joypads have a weird sense of direction. You might need to flip the axes to make them work as expected.

[penalvch (penalvch)]

NiBu, 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? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

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

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

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[NiBu (niko-buzki)]

Today, I have tested my device with the games Steel Storm and Trine. I suppose this bug is a software specific bug, because with Trine now it works very well but with Steel Storm there is the same problem.