Closed D33M0N closed 3 years ago
Please cross-check that the module actually loaded by running lsmod
. Also, you may need to sign the kernel module as described here: https://github.com/atar-axis/xpadneo/blob/master/docs/SECUREBOOT.md although I cannot help here as I'm running a kernel without module signing.
Looking at your dmesg log, this also looks like it first bound to hid-generic which then passed its control to hid-microsoft. So the gamepad is using the hid-microsoft driver but not xpadneo, thus no connection rumble, and thus the extra buttons which are dead.
Are you sure that the udev rules were installed and are working? Try udevadm monitor
before switching the gamepad on to trace udev.
First tried temporary solution with modprobe -r hid_microsoft
and instantly got xpadneo greeting rumble.
Then created such file:
[deemon@Zen ~]$ cat /etc/modprobe.d/hid_microsoft.conf
blacklist hid_microsoft
and now everything is good. :)
So instead of trying to tell my computer which driver to use by some hid matching numbers (which btw the offending kernel in-built driver also uses) I just disabled the offending driver.
Apparently, blacklisting hid-microsoft is not an option to ship with xpadneo as it would also disable all the other input devices that are covered by that driver. In some cases, hid-generic may take over but you would lose some quirk handling, lose some functionality, or such devices would just not work correctly anymore.
The udev rules are there to actually fix this and re-bind the device to hid-xpadneo. The hid matching numbers are only there to trigger loading of the module in the first place. So I still think the udev rules did not execute properly, udevadm monitor -p
could tell us more.
Version of xpadneo
v0.9-23-g6162dbc
Severity / Impact
Describe the bug
Initial connection rumble doesn't work. Also it does look like it might be using some wrong driver entirely... (and I don't know how to check which driver it uses). Also jstest-gtk shows some different device than I am used to see there ... with 15 buttons... might be due to wrong driver being used (although all the triggers and buttons on the physical device are triggering, just many buttons in jstest-gtk can't be triggered at all because they don't exist physically). Also it whines about missing signature and tainting kernel.
Steps to Reproduce
press the controller X button to connect.
Expected behavior
Friendly connection rumble :-)
Screenshots/Gifs
System information
there aren't any numbered items at all.
Controller and Bluetooth information
xpadneo-lsusb.txt xpadneo-dmesg.txt xpadneo-btmon.txt
Additional context