You are not logged in.
Hi,
I noticed that games detect a joysticks that is pushed in one direction, even though I have no joystick attached. In /dev/input I see 1 joystick: /dev/input/js0
So I ran jstest to confirm this:
>>> jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (ASRock LED Controller) has 11 axes (X, Y, Z, Rx, Ry, Rz, Throttle, Rudder, Wheel, Hat0X, (null))
and 6 buttons (BtnSelect, BtnStart, (null), (null), (null), (null)).
Testing ... (interrupt to exit)
Axes: 0:-32767 1:-32767 2:-32767 3:-32767 4:-32767 5:-32767 6:-32767 7:-32767 8:-32767 9:-32767 10:-32767 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off ^CSo indeed, the system sees a joystick called 'ASRock LED Controller' with the stick not centered.
hwinfo shows me this entry:
bus = 3, name = ASRock LED Controller
handlers = kbd event22 js0
key = 004000000100000000000012000000000c000000000000000000000800000000000040000010cc0000101680000000000000000000000000
abs = 00000100000101ff
mouse buttons = 0
mouse wheels = 0
is_mouse = 0
is_joystick = 1and lsusb shows this device:
>>> lsusb | grep -i led
Bus 001 Device 009: ID 26ce:01a2 ASRock LED ControllerThe motherboard is a 'Asrock B550 Taichi'
I'm not sure how to make my system stop seeing this 'LED Controller' as a joystick.
Could it be a driver bug that causes this?
Thanks!
Offline
Looking a bit further into this, I found the driver being used for this device using hwinfo:
102: USB 00.0: 0000 Unclassified device
[Created at usb.122]
Unique ID: fHJ1.SvdFbhjcW29
Parent ID: k4bc.kNaPe9SZft4
SysFS ID: /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb1/1-10/1-10:1.0
SysFS BusID: 1-10:1.0
Hardware Class: unknown
Model: "ASRock LED Controller"
Hotplug: USB
Vendor: usb 0x26ce "ASRock"
Device: usb 0x01a2 "LED Controller"
Serial ID: "A02019100900"
Driver: "usbhid"
Driver Modules: "usbhid"
Device File: /dev/input/js0
Device Files: /dev/input/js0, /dev/input/by-id/usb-ASRock_LED_Controller_A02019100900-joystick, /dev/input/by-path/pci-0000:01:00.0-usb-0:10:1.0-joystick
Device Number: char 13:0
Speed: 12 Mbps
Module Alias: "usb:v26CEp01A2d0000dc00dsc00dp00ic03isc00ip00in00"
Driver Info #0:
Driver Status: usbhid is active
Driver Activation Cmd: "modprobe usbhid"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #118 (Hub)The driver is 'usbhid' so I suspect that this device identifies itself as a joystick. No idea why though.
I will just try to disable this device in the bios or otherwise.
Offline
I have the same problems.
And it make a real game pad not work.
Did you have any solution to solve this?
Offline
I just have a script I run at startup to unbind the device:
# Nuke the ASRock LED Controller device (We don't use it and it shows up as a Joystick causing havoc in some games!)
echo '9-5' | tee /sys/bus/usb/drivers/usb/unbindASRock TRX40 Creator B1.70 | AMD TR3970X | 64GB G.Skill Trident Z | AMD RX 6900XT 16GB / AMD RX 6800XT 16GB (VFIO) | Samsung CRG90 | BENQ 1080p (portrait) | 1x Samsung 850 EVO 1TB | 2x Samsung 960 EVO NVMe | 5x WD Red 4TB (RAID6) | Corsair MP600 Force 500GB + 8GB Seagate (store) | Sennheiser MOMENTUM 3 | Roccat KoneXTD Optical
Offline
This udev rule file here should work to fix the problem (if I didn't make a mistake):
# /etc/udev.d/rules.d/51-asrock-led-joystick-fix.conf
SUBSYSTEM=="input", ATTRS{idVendor}=="26ce", ATTRS{idProduct}=="01a2", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="26ce", ATTRS{idProduct}=="01a2", KERNEL=="js[0-9]*", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""I stole the rule from here and changed the vendor/product IDs:
Offline
Ropid's solution doesn't work for me. But this fixed the issue:
#/etc/udev/rules.d/01-asrock-LED-controller.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="26ce", ATTRS{idProduct}=="01a2", ATTR{authorized}="0"With that rule the fake joystick no longer appears.
Found here: https://www.reddit.com/r/ASRock/comment … ecognized/
Offline