You are not logged in.
$ lsusb
...
Bus 003 Device 008: ID 0e6f:02d8 Logic3 PDP Wired Controller for Xbox Series X - Blue Camo
...
$ lsusb -t
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ ...
|__ Port 4: Dev 8, If 0, Class=Vendor Specific Class, Driver=xpad, 12M
|__ ...
$ cat /etc/modules-load.d/gamepad.conf
xpad
I have an Xbox Series X wired gamepad. It uses the xpad kernel module. The module loads on boot, but the ready light on the gamepad doesn't come on unless you unplug and replug it. And the gamepad doesn't work until that light is on.
I've tried to load the modules during boot, and the module does get loaded but the device just doesn't get initialized properly.
Any suggestions would be appreciated.
Offline
Moved, by request
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Anything interesting in the journal regarding this?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Output of : journalctl -b 1:
https://gist.github.com/headkase/5bc969 … 14d3d04e63
Honestly though I don't know what I'm looking for in there ewaller.
Offline
https://gist.github.com/headkase/ef8e10 … 86c2cc8f7a
And the above gist is with xpad in modules-load, I removed that and forgot I did for the previous gist. If it doesn't work you always undo it right, forgot I did that so I redid the module load of xpad for this journal listing.
Last edited by headkase (2022-11-20 16:26:50)
Offline
I was looking for stuff a little earlier in the log -- like when the system attempts to initially enumerate the USB bus devices. Your log has (at least) a 20 minute gap at the beginning.
Can you please power down, ensure the controller is attached, powerup, login, and post a link to the output of journalctl -b
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Here is journalctl -b as non-root:
https://gist.github.com/headkase/884eae … 56e2818948
And here is sudo journalctl -b:
https://gist.github.com/headkase/9bb917 … b17c9cf2c2
in /etc/modules-load.d, the config file with "xpad" is there for the boot.
Offline
There is some new information.
On some boots the ready light appears on the gamepad. Not all boots just some boots which makes me think there is some kind of race-condition where the correct order sometimes happens. If I can figure out all the modules needed I'll put them all in /etc/modules-load.d/ and if that works call it a day. I'm not sure how to find out the module chain, I'd appreciate pointers.
Offline
I removed all module-load configuration files and decided to leave it to systemd. It's working now but not in a way you'd expect. I boot, sit there as long as I want and the ready light won't light up. Run Steam, and boom ready light appears. 100% of the time. So, I have Steam set to autostart and Steam makes my gamepad work. I can quit Steam and the gamepad continues to work. So, not really "solved" but more "now working".
Offline