Bug #1332444 “CH Pedals are not working in 14.04” : Bugs : systemd package : Ubuntu

Revision history for this message

In freedesktop.org Bugzilla #70734, Michal Navratil (f-josef) wrote on 2013-10-21:

#12

Hello,
when a rudder pedals (e.g. 06a3:0763 Saitek PLC Pro Flight Rudder Pedals) are connected, the /dev/input/jsX and /dev/input/eventX are created. The problem is, that while jsX device has 644 permissions (enybody can read), the eventX device is available only to root, while any other joystick-like device receives ACLs for the current user.

If I'm not mistaken, the culprit is in the joystick detection heuristics - it looks for some axes and buttons, while these devices have only three axes.

Would it be possible to either extend the joystick detection heuristics to handle such devices (CH products pedals reportedly behave the same) or to create some exceptions for them, so these devices would work out of the box?

Please let me know if you need any more informations.
Kind regards,

Michal Navratil

Revision history for this message

In freedesktop.org Bugzilla #70734, Martin Pitt (pitti) wrote on 2014-03-05:

#13

Yes, we should certainly extend input_id's logic to also cover these devices. Can you please find the eventX that belongs to that device, and give me the output of

udevadm info --name=input/eventX

Please copy the device path from the first output line ("P:"), and run input id in debug mode:

udevadm test-builtin input_id /devices/...

Finally, please run

udevadm info --attribute-walk --name=input/eventX

and copy&paste the output here.

Thanks!

Revision history for this message

In freedesktop.org Bugzilla #70734, Michal Navratil (f-josef) wrote on 2014-03-07:

#14

Created attachment 95318
Requested udev info on Saitek rudder pedals.

Revision history for this message

In freedesktop.org Bugzilla #70734, Martin Pitt (pitti) wrote on 2014-03-10:

#15

> # udevadm info --name=input/event12
> [...]
> E: ID_INPUT_JOYSTICK=1

Err, that's what we want to achieve.. I suppose you have some local udev rule which attaches that property to the pedals, so that it works for you?

> capabilities/ev raw kernel attribute: 9

That means it's capable of sending ABS and SYN events, not that surprising.

> capabilities/abs raw kernel attribute: 23

== ABS_X, ABS_Y, ABS_RZ

I was hoping that the device would be capable of something distinct like ABS_THROTTLE, ABS_RUDDER, ABS_WHEEL, ABS_GAS, or ABS_BRAKE. I'm afraid I don't really know what ABS_RZ is supposed to mean, the official documentation (https://www.kernel.org/doc/Documentation/input/event-codes.txt) does not mention it and googling for it doesn't help much either.

However, touch screens, touchpads, and accelerometers do *not* use all these "fancy" axes, they really are quite unique to joysticks and similar game controllers.

Revision history for this message

In freedesktop.org Bugzilla #70734, Martin Pitt (pitti) wrote on 2014-03-10:

#16

Fixed in http://cgit.freedesktop.org/systemd/systemd/commit/?id=2658624399 . If you have a chance to test, I'd appreciate, but this ought to match at least your device (and presumably a lot of similar devices).

Revision history for this message

michael (scrat-here) wrote on 2014-06-20:

#1

BootDmesg.txt Edit (75.1 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (11.4 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (701 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (7.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (316 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (182.5 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (398.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Martin Pitt (pitti) wrote on 2014-08-04:

#2

What does "not working" mean? Your game doesn't have permissions to access the pedals? Or they don't send the correct events, etc? (The latter would be a kernel bug, not udev rules).

In a situation when they are not working, can you please find the correct /dev/input/eventNN device for the pedals (e. g. from /dev/input/by-id/) and then the output of "getfacl /dev/input/eventNN"?

Thanks!

Changed in systemd (Ubuntu):
status:	New → Incomplete

Revision history for this message

michael (scrat-here) wrote on 2014-08-04: Re: [Bug 1332444] Re: CH Pedals are not working in 14.04

#3

Download full text (3.9 KiB)

Just tried and for once they work.- Randomly the pedals work or not at all. Best if you send me the terminal commands to execute on Ubuntu 14.04 or I'll try tomorrow or so again.
What I do is taken from here:
http://forums.x-plane.org/index.php?showtopic=71300&page=6

#!/bin/bash
cd /dev/input
sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *
cd ~/X-Plane_10
sudo mount -o loop /media/michael/DATA/img/xplane10.iso /media/michael/XPLANE10
./X-Plane-x86_64

Thanks

________________________________
From: Martin Pitt <email address hidden>
To: <email address hidden>
Sent: Monday, August 4, 2014 4:31 PM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04

What does "not working" mean? Your game doesn't have permissions to
access the pedals? Or they don't send the correct events, etc? (The
latter would be a kernel bug, not udev rules).

In a situation when they are not working, can you please find the
correct /dev/input/eventNN device for the pedals (e. g. from /dev/input
/by-id/) and then the output of "getfacl /dev/input/eventNN"?

Thanks!

** Changed in: systemd (Ubuntu)
Status: New => Incomplete

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1332444

Title:
CH Pedals are not working in 14.04

Status in “systemd” package in Ubuntu:
Incomplete

Bug description:
  I've created a rule in lib/udev/rules.d as 99-xplane.rules:
  # CH PRO PEDALS USB
  KERNEL=="event*", ATTRS{idProduct}=="00f2", ATTRS{idVendor}=="068e", MODE="0666"

  and even do at every x-plane start:
  cd /dev/input
  sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *

but still my CH Pedals are often not working. (sometimes yes but not
always)

  ------
  michael@michael-ubuntu:~$ lsb_release -rd
  Description:    Ubuntu 14.04 LTS
  Release:    14.04
  michael@michael-ubuntu:~$

  ----
  michael@michael-ubuntu:~$ apt-cache policy udev
  udev:
    Installed: 204-5ubuntu20.2
    Candidate: 204-5ubuntu20.2
    Version table:
   *** 204-5ubuntu20.2 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       204-5ubuntu20 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  michael@michael-ubuntu:~$

I expect my CH pedals to work out of the box like on Windows.
But even with the above they only work sometimes.-

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 20 09:46:31 2014
  InstallationDate: Installed on 2014-04-19 (61 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=2c43c000-7e14-4304-9dd6-e10fe2810f92 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi...

Just tried and for once they work.- Randomly the pedals work or not at all. Best if you send me the terminal commands to execute on Ubuntu 14.04 or I'll try tomorrow or so again.
What I do is taken from here:
http://forums.x-plane.org/index.php?showtopic=71300&page=6

#!/bin/bash
cd /dev/input
sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *
cd ~/X-Plane_10
sudo mount -o loop /media/michael/DATA/img/xplane10.iso /media/michael/XPLANE10
./X-Plane-x86_64

Thanks

________________________________
 From: Martin Pitt <martin.pitt@ubuntu.com>
To: scrat_here@yahoo.com 
Sent: Monday, August 4, 2014 4:31 PM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04

What does "not working" mean? Your game doesn't have permissions to
access the pedals? Or they don't send the correct events, etc? (The
latter would be a kernel bug, not udev rules).

In a situation when they are not working, can you please find the
correct /dev/input/eventNN device for the pedals (e. g. from /dev/input
/by-id/) and then the output of "getfacl /dev/input/eventNN"?

Thanks!

** Changed in: systemd (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1332444

Title:
  CH Pedals are not working in 14.04

Status in “systemd” package in Ubuntu:
  Incomplete

Bug description:
  I've created a rule in lib/udev/rules.d as 99-xplane.rules:
  # CH PRO PEDALS USB
  KERNEL=="event*", ATTRS{idProduct}=="00f2", ATTRS{idVendor}=="068e", MODE="0666"

and even do at every x-plane start:
  cd /dev/input
  sudo setfacl --modify u:michael:rw- --modify g::rw- --modify o::rw- *

but still my CH Pedals are often not working. (sometimes yes but not
  always)

------
  michael@michael-ubuntu:~$ lsb_release -rd
  Description:    Ubuntu 14.04 LTS
  Release:    14.04
  michael@michael-ubuntu:~$

----
  michael@michael-ubuntu:~$ apt-cache policy udev
  udev:
    Installed: 204-5ubuntu20.2
    Candidate: 204-5ubuntu20.2
    Version table:
   *** 204-5ubuntu20.2 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       204-5ubuntu20 0
          500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  michael@michael-ubuntu:~$

I expect my CH pedals to work out of the box like on Windows.
  But even with the above they only work sometimes.-

ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 20 09:46:31 2014
  InstallationDate: Installed on 2014-04-19 (61 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=2c43c000-7e14-4304-9dd6-e10fe2810f92 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1405
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd08/19/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1332444/+subscriptions

Revision history for this message

Martin Pitt (pitti) wrote on 2014-08-04:

#4

I did give you the terminal commands mostly. Perhaps just not that one: "find the correct /dev/input/eventNN" translates to "ls -l /dev/input/by-id/" and looking which one sounds like your pedals.

So again, what does "isn't working sometimes" mean exactly? Doesn't XPlane detect the joystick, or does it detect it but doesn't get events from it, or something else?

Revision history for this message

michael (scrat-here) wrote on 2014-08-05:

#5

Download full text (6.7 KiB)

Hi Martin
they worked yesterday after executing the script I've sent. But today they're dead. I don't know why but dead is the only word I find. Events

seem to change hence the * in my script (in my email from yesterday) I see below that my CH Pedals are not even mentioned.

Let me know if I should execute commands to isolate the problem:
Thanks

-----

michael@michael-ubuntu:~$ ls -l /dev/input
total 0
drwxrw-rw-+ 2 root root    140 Aug 5 08:02 by-id
drwxrw-rw-+ 2 root root    160 Aug 5 08:02 by-path
crw-rw-rw-+ 1 root root 13, 64 Aug 5 08:02 event0
crw-rw-rw-+ 1 root root 13, 65 Aug 5 08:02 event1
crw-rw-rw-+ 1 root root 13, 74 Aug 5 08:02 event10
crw-rw-rw-+ 1 root root 13, 75 Aug 5 08:02 event11
crw-rw-rw-+ 1 root root 13, 76 Aug 5 08:02 event12
crw-rw-rw-+ 1 root root 13, 77 Aug 5 08:02 event13
crw-rw-rw-+ 1 root root 13, 78 Aug 5 08:02 event14
crw-rw-rw-+ 1 root root 13, 79 Aug 5 08:02 event15
crw-rw-rw-+ 1 root root 13, 80 Aug 5 08:02 event16
crw-rw-rw-+ 1 root root 13, 81 Aug 5 08:02 event17
crw-rw-rw-+ 1 root root 13, 82 Aug 5 08:02 event18
crw-rw-rw-+ 1 root root 13, 66 Aug 5 08:02 event2
crw-rw-rw-+ 1 root root 13, 67 Aug 5 08:02 event3
crw-rw-rw-+ 1 root root 13, 68 Aug 5 08:02 event4
crw-rw-rw-+ 1 root root 13, 69 Aug 5 08:02 event5
crw-rw-rw-+ 1 root root 13, 70 Aug 5 08:02 event6
crw-rw-rw-+ 1 root root 13, 71 Aug 5 08:02 event7
crw-rw-rw-+ 1 root root 13, 72 Aug 5 08:02 event8
crw-rw-rw-+ 1 root root 13, 73 Aug 5 08:02 event9
crw-r--r--+ 1 root root 13, 0 Aug 5 08:03 js0
crw-rw-rw-+ 1 root root 13, 1 Aug 5 08:02 js1
crw-rw-rw-+ 1 root root 13, 63 Aug 5 08:02 mice
crw-rw-rw-+ 1 root root 13, 32 Aug 5 08:02 mouse0
michael@michael-ubuntu:~$ ls -l /dev/input/by-id
ls: cannot access /dev/input/by-id/usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-joystick: Permission denied
ls: cannot access /dev/input/by-id/usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-event-joystick: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-if01-mouse: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd: Permission denied
total 0
l????????? ? ? ? ?            ? usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-event-joystick
l????????? ? ? ? ?            ? usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-joystick
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-event-kbd
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-if01-event-mouse
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-if01-mouse
michael@michael-ubuntu:~$ uname -a
Linux michael-ubuntu 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
michael@michael-ubuntu:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0b05:17d0 ASUSTek Computer, Inc.
Bus 003 Devic...

Hi Martin
  they worked yesterday after executing the script I've sent. But today they're dead. I don't know why but dead is the only word I find. Events

seem to change hence the * in my script (in my email from yesterday) I see below that my CH Pedals are not even mentioned.

Let me know if I should execute commands to isolate the problem:
Thanks

-----

michael@michael-ubuntu:~$ ls -l /dev/input
total 0
drwxrw-rw-+ 2 root root    140 Aug  5 08:02 by-id
drwxrw-rw-+ 2 root root    160 Aug  5 08:02 by-path
crw-rw-rw-+ 1 root root 13, 64 Aug  5 08:02 event0
crw-rw-rw-+ 1 root root 13, 65 Aug  5 08:02 event1
crw-rw-rw-+ 1 root root 13, 74 Aug  5 08:02 event10
crw-rw-rw-+ 1 root root 13, 75 Aug  5 08:02 event11
crw-rw-rw-+ 1 root root 13, 76 Aug  5 08:02 event12
crw-rw-rw-+ 1 root root 13, 77 Aug  5 08:02 event13
crw-rw-rw-+ 1 root root 13, 78 Aug  5 08:02 event14
crw-rw-rw-+ 1 root root 13, 79 Aug  5 08:02 event15
crw-rw-rw-+ 1 root root 13, 80 Aug  5 08:02 event16
crw-rw-rw-+ 1 root root 13, 81 Aug  5 08:02 event17
crw-rw-rw-+ 1 root root 13, 82 Aug  5 08:02 event18
crw-rw-rw-+ 1 root root 13, 66 Aug  5 08:02 event2
crw-rw-rw-+ 1 root root 13, 67 Aug  5 08:02 event3
crw-rw-rw-+ 1 root root 13, 68 Aug  5 08:02 event4
crw-rw-rw-+ 1 root root 13, 69 Aug  5 08:02 event5
crw-rw-rw-+ 1 root root 13, 70 Aug  5 08:02 event6
crw-rw-rw-+ 1 root root 13, 71 Aug  5 08:02 event7
crw-rw-rw-+ 1 root root 13, 72 Aug  5 08:02 event8
crw-rw-rw-+ 1 root root 13, 73 Aug  5 08:02 event9
crw-r--r--+ 1 root root 13,  0 Aug  5 08:03 js0
crw-rw-rw-+ 1 root root 13,  1 Aug  5 08:02 js1
crw-rw-rw-+ 1 root root 13, 63 Aug  5 08:02 mice
crw-rw-rw-+ 1 root root 13, 32 Aug  5 08:02 mouse0
michael@michael-ubuntu:~$ ls -l /dev/input/by-id
ls: cannot access /dev/input/by-id/usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-joystick: Permission denied
ls: cannot access /dev/input/by-id/usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-event-joystick: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-if01-mouse: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-if01-event-mouse: Permission denied
ls: cannot access /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd: Permission denied
total 0
l????????? ? ? ? ?            ? usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-event-joystick
l????????? ? ? ? ?            ? usb-CH_PRODUCTS_CH_FLIGHT_SIM_YOKE_USB-joystick
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-event-kbd
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-if01-event-mouse
l????????? ? ? ? ?            ? usb-Logitech_USB_Receiver-if01-mouse
michael@michael-ubuntu:~$ uname -a
Linux michael-ubuntu 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
michael@michael-ubuntu:~$ lsusb 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0b05:17d0 ASUSTek Computer, Inc. 
Bus 003 Device 006: ID 068e:00ff CH Products, Inc. Flight Sim Yoke
Bus 003 Device 005: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals
Bus 003 Device 003: ID 174c:2074 ASMedia Technology Inc. 
Bus 003 Device 002: ID 046d:c52e Logitech, Inc. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
michael@michael-ubuntu:~$

________________________________
 From: Martin Pitt <martin.pitt@ubuntu.com>
To: scrat_here@yahoo.com 
Sent: Monday, August 4, 2014 5:45 PM
Subject: [Bug 1332444] Re: CH Pedals are not working in 14.04

I did give you the terminal commands mostly. Perhaps just not that one:
"find the correct /dev/input/eventNN" translates to "ls -l /dev/input
/by-id/" and looking which one sounds like your pedals.

So again, what does "isn't working sometimes" mean exactly? Doesn't
XPlane detect the joystick, or does it detect it but doesn't  get events
from it, or something else?