Closed l0b0 closed 3 years ago
Did the udev rules install? According to the pkg build, they should be in /usr/lib/udev/rules.d
.
Looks like it:
$ find /usr/lib/udev/rules.d -iname '*xpad*'
/usr/lib/udev/rules.d/98-xpadneo.rules
$ cat /usr/lib/udev/rules.d/98-xpadneo.rules
ACTION=="add", KERNEL=="0005:045E:02FD.*|0005:045E:02E0.*|0005:045E:0B05.*|0005:045E:0B13.*", SUBSYSTEM=="hid", DRIVER!="xpadneo", ATTR{driver/unbind}="%k", ATTR{[drivers/hid:xpadneo]bind}="%k"
ACTION=="add|change", DRIVERS=="xpadneo", SUBSYSTEM=="input", ENV{ID_INPUT_JOYSTICK}=="1", TAG+="uaccess", MODE="0664"
There should also be a file modprobe.d/xpadneo.conf
, usually it's installed in /etc
but maybe in /usr/lib
.
Yep:
$ cat /etc/modprobe.d/xpadneo.conf
alias hid:b0005g*v0000045Ep000002E0 hid_xpadneo
alias hid:b0005g*v0000045Ep000002FD hid_xpadneo
alias hid:b0005g*v0000045Ep00000B05 hid_xpadneo
alias hid:b0005g*v0000045Ep00000B13 hid_xpadneo
Then it should just work when you connect the controller via Bluetooth. The module won't auto-load at boot. This is triggered by the module aliases and the udev rules. If it doesn't work, couldn't you start from a fresh reboot, run sudo udevadm monitor
and then connect the controller? Maybe we can find the problem if we see what udev does (or doesn't do)...
Sounds awfully familiar to the issue I had. Ended up blacklisting hid_microsoft.
You're right, I think this ended up being an X-Y problem: I tried a bunch of different things to connect the controller at all, and when I couldn't I reported this as a likely culprit. Now that I've actually connected the controller and rebooted it does indeed connect automatically after powering on, buzz as expected, and lsmod
shows hid_xpadneo as loaded. Thank you for your patience!
Version of xpadneo
xpadneo-dkms-git 0.9.r36.gb827510-1
Severity / Impact
Describe the bug
After installing the very latest version on Arch Linux and rebooting the hid_xpadneo kernel module is not loaded.
Steps to Reproduce
Expected behavior
The kernel module should be loaded after rebooting.
System information
A possibly unrelated module called just "xpad" is loaded:
Additional context
sudo modprobe hid-xpadneo
loads the module successfully. But even after that the path/sys/module/hid_xpadneo/drivers/hid:xpadneo/0005:045E:*/report_descriptor
does not exist. The closest I can get is this: