Hi, I have a problem with my Xbox One S controller (connected via USB), meaning it isn’t recognized at all. In the “input devices” section in the controller section nothing is detected, even when the pad is connected. I believe I have all xbox drivers installed. On other distributions I didn’t have this problem, the pad was recognized automatically (endeavouros, manjaro, mint, nobara, xubuntu, opensuse, yes I tried various Linux distributions). I only have the problem on Garuda.
I also tried with another Xbox pad but it still isn’t detected. I tried to put the PS4 one on and it detected it without problems, allowing me to play straight away via Steam.
But I would like my Xbox One S pad to work too. How can I solve the problem?
Thank you dear for your kind reply, but I have already installed the driver in question:
╭─sermor@sermor in ~
╰─λ cd xone
sudo ./install.sh --release
[sudo] password di sermor:
Driver is already installed!
As well as the other drivers: xboxdrv, xpadneo, and xbox generic controller.
I installed these drivers via garuda gamer at startup after installation. You could say it’s among the first things I did. The drivers are installed, but the xbox pad is still not recognized. Thank you for the time you dedicated to me.
Please read the following template before requesting assistance:
Please post the terminal/konsole input and output as text (no pictures) from the following command:
garuda-inxi
Refusing to post the output of the required “garuda-inxi” on a help request will likely result in you not receiving any help from the Garuda team. A failure to provide your system specs may also result in your thread being closed without notice, (as without this information providing assistance is often next to impossible).
Before opening a new help request, please search the Arch and Garuda Wiki’s, and read any relevant sections related to your issue. Also, thoroughly search any error messages in the forum’s search engine and on the web. For in depth information on how to search for answers to Linux issues effectively, read the tips on the Garuda Wiki:
Please report in detail everything you have already attempted to solve your problem.
For the rest I limited myself to installing the xboxdrv, xbox+dkms, xbox-generic-controller, xpadneo-dkms drivers from the Garuda Gamer game menu. Other drivers like xone-dkms and xone-dongle-firmware are already present.
Not being familiar with Linux in general (I just recently got into it), I didn’t try to mess around with various commands, at the moment the guides aren’t very intuitive for me.
In any case, if I put the PS4 pad instead of the Xbox pad, the PS4 pad works and is also recognized by Steam. All without typing any commands.
You run Windows. You have hardware device peripherals, your XBox & controller. Windows loves to take and keep hardware peripherals hostage.
The first suspect, is to check your BIOS and make sure it has FULL HARDWARE RECOGNITION selected. It may be hidden under a menu item such as Fastboot.
The next thing I would check, is to see if there is a BIOS newer than yours dated 2021. BIOS updates address hardware issues in the main. They are common and fairly frequent.
Thanks for the suggestions, I did what you told me, and as you can see I also updated the bios, but nothing has changed, Garuda still doesn’t detect my xbox pad.
I don’t remember the brand of the pad. But I tried to get another Nacon xbox pad and it still doesn’t work.
And yes, I tried changing the USB port, even putting it in the rear ones, but nothing, it doesn’t work.
╭─sermor@sermor in ~ took 9ms
╰─λ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 03f0:4941 HP, Inc OMEN Blast Headset
Bus 001 Device 003: ID 04b8:118b Seiko Epson Corp. ET-2850 Series
Bus 001 Device 014: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 015: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 016: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 017: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 018: ID 045e:02ea Microsoft Corp. Xbox One Controller
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0b05:18f3 ASUSTek Computer, Inc. AURA LED Controller
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Have you tried enabling the just the xbox-generic-controller in Garuda Gamer (gaming tab far down in the list)? Looks like most DKMS packages are having issues for that ID
No, I haven’t tried, also because not being very familiar with Linux I limited myself to installing the drivers and that’s it (via the Garuda Gamer menu).
hit alt+space keys. Search for garuda gamer and select it from the list. In the gaming tab far down in the list there should be check-boxes for various drivers. Try just having the xbox-generic-controller checked and hit apply. A restart might be needed if you removed DKMS modules.
If that doesn’t work, try each one separately, with most needing reboots because they are DKMS modules. xone-dkms would probably be the next best one to try.
The drivers can be finicky at best with 3rd party support
A lot of 3rd party xbox controllers tend to have issues until full support is baked into the kernel.
So, I managed to solve it this way: I uninstalled all the drivers and rebooted.
Then, with each new driver installation I rebooted. I first installed the xboxdrv driver via garuda gamer, then the xbox-generic-controller driver. Then from Garuda Gamer I switched to Octopi and installed the xpadneo-dkms-git package, and again from octopi I installed the xone-dkms-git driver and xone-dongle-firmware.
At the last reboot the generic xbox pad whose brand I don’t remember is detected in the pad section of the “input devices” menu, but I can’t calibrate it. While the xbox nacon pad works perfectly!
I still think it’s in your BIOS settings, fastboot. And also from within Windows (use Control Panel to turn off fast start which is similar to the BIOS setting). Then turn your computer OFF–unplug it, even-- before re-starting and logging into Garuda, not Windows.
Hardware peripheral issues like this arise constantly, and for the same two reasons outlined above. It is all because of effing Microsoft.
always do a full shutdown of windoze rather than a restart when you want to switch the OS you’re using.
in this way peripheral devices get released by the OS and are not ‘held hostage’.
i learned this the hard way a couple years ago and i have not had any hardware resource allocation issues since i began doing full shutdowns.
