Ubuntu
linux package

06a3:ffb5 iforce kernel module doesn't recognize my joystick

Bug #792937 reported by davygrvy on 2011-06-04

18

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

apparently, drivers/input/joystick/iforce dates back to Dec 9 2009, but missed getting a patch that would make it recognize my Saitek Cyborg EVO Force stick: https://patchwork.kernel.org/patch/68558/

Please either apply this patch, or grab the latest from the iforce project.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-32-generic 2.6.32-32.62
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
Uname: Linux 2.6.32-32-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: davygrvy 2186 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xd2000000 irq 18'
   Mixer name : 'Nvidia ID b'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card0.Amixer.values:

Card1.Amixer.info:
Card hw:1 'UART'/'MPU-401 UART at 0x330, irq 10'
   Mixer name : ''
   Components : ''
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

Card2.Amixer.info:
Card hw:2 'CK804'/'NVidia CK804 with ALC850 at irq 22'
   Mixer name : 'Realtek ALC850 rev 0'
   Components : 'AC97a:414c4790'
   Controls : 42
   Simple ctrls : 27
Date: Sat Jun 4 14:55:17 2011
HibernationDevice: RESUME=UUID=0e388931-7f23-49ff-ab0f-489602918a37
MachineType: System manufacturer System Product Name
ProcCmdLine: root=UUID=8e7e9abd-7319-4cff-b071-0213a06e5b2b ro splash quiet
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.7
RfKill:

SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 08/10/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS A8N-SLI Premium ACPI BIOS Revision 1303
dmi.board.name: A8N-SLI Premium
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.02
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIPremiumACPIBIOSRevision1303:bd08/10/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8N-SLIPremium:rvr1.02:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Tags:

Revision history for this message

davygrvy (davygrvy) wrote on 2011-06-04:

#1

AlsaDevices.txt Edit (878 bytes, text/plain; charset="utf-8")
AplayDevices.txt Edit (285 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (286 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (48.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.0.txt Edit (906 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec.1.txt Edit (906 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec.2.txt Edit (906 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec.3.txt Edit (906 bytes, text/plain; charset="utf-8")
Card2.Amixer.values.txt Edit (5.6 KiB, text/plain; charset="utf-8")
Card2.Codecs.codec97.0.ac97.0.0.txt Edit (732 bytes, text/plain; charset="utf-8")
Card2.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (44.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (138 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (16.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (487 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.7 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (111.4 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (249.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

davygrvy (davygrvy) wrote on 2011-06-05:

#2

patch Edit (7.9 KiB, text/plain)

3rd iteration of the patch made by Johannes Ebke (Dec. 21, 2009, 11:45 a.m): https://patchwork.kernel.org/patch/69106/

Brad Figg (brad-figg) on 2011-06-06

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

davygrvy (davygrvy) wrote on 2011-06-06:

#3

I can confirm the attached patch does work for me as I built the module and tested it yesterday. fftest works with it, but ffcfstress does not, which I have yet to debug.

Revision history for this message

davygrvy (davygrvy) wrote on 2011-06-07:

#4

My output of evtest:

$ evtest /dev/input/event4
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x6a3 product 0xffb5 version 0x0
Input device name: "Saitek Cyborg Evo Force"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 288 (Trigger)
    Event code 289 (ThumbBtn)
    Event code 291 (TopBtn)
    Event code 292 (TopBtn2)
    Event code 294 (BaseBtn)
    Event code 295 (BaseBtn2)
    Event code 296 (BaseBtn3)
    Event code 297 (BaseBtn4)
    Event code 298 (BaseBtn5)
    Event code 304 (BtnA)
    Event code 305 (BtnB)
    Event code 306 (BtnC)
  Event type 3 (Absolute)
    Event code 0 (X)
      Value 1948
      Min 0
      Max 4096
      Fuzz 16
      Flat 128
    Event code 1 (Y)
      Value 2092
      Min 0
      Max 4096
      Fuzz 16
      Flat 128
    Event code 6 (Throttle)
      Value 254
      Min 0
      Max 255
    Event code 7 (Rudder)
      Value 105
      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 0 (?)
    Event code 1 (?)
    Event code 80 (Rumble)
    Event code 81 (Periodic)
    Event code 82 (Constant)
    Event code 83 (Spring)
    Event code 85 (Damper)
    Event code 88 (Square)
    Event code 89 (Triangle)
    Event code 90 (Sine)
    Event code 91 (SawUp)
    Event code 92 (SawDown)
    Event code 96 (Gain)
    Event code 97 (AutoCenter)
  Event type 23 (ForceFeedbackStatus)
Testing ... (interrupt to exit)
...

Revision history for this message

Lauri Peltonen (lauri-peltonen) wrote on 2011-11-27:

#5

I just applied the patch in post #2 on Ubuntu 11.10 (kernel 3.0.0-14-generic) after some modifications to get it apply cleanly.

After some tweaking of modules (I think iforce needs to be loaded before usbhid or the force effects do not work?) I can confirm that the force feedback effects work on Saitek Cyborg Evo Force.

ffset works, fftest works (though spring & damping don't do much, and constant force is quite weak), ffmvforce works (though it seems to only apply the first click, later clicks do not change force direction).

ffcfstress does not work, every line prints out "upload effect: Resource temporarily unavailable". Also after running this, no effect works afterwards. Dmesg shows lines like this: "[ 5481.742833] input input30: not enough space in xmit buffer to send new packet"

bzflag works, both rumble and directional effect.

I'd like to see this patch in future kernel versions :) At least the identification parts, because I guess the axis values are not that critical?

Lauri Peltonen

Ubuntu Foundations Team Bug Bot (crichton) on 2011-11-27

tags:

added: patch

Joseph Salisbury (jsalisbury) on 2011-11-28

Changed in linux (Ubuntu):
importance:	Undecided → Medium

penalvch (penalvch) on 2012-07-29

summary:

- iforce kernel module doesn't recognize my joystick
+ 06a3:ffb5 iforce kernel module doesn't recognize my joystick

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Patches

patch Edit

Add patch

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.