Xbox One S controller is not detected by Garuda

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?

no garuda-inxi + no forum or google search = no etiquette and no respect for the Garuda team volunteers.

read the freakin’ template you deleted before you posted.

thank you and have a nice day =-)

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.

Hello @Sermor .

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.

1 Like

Meanwhile, thank you very much for the comprehensive answer, here is the result after typing the command you gave me:

╭─sermor@sermor in ~
╰─λ garuda-inxi
System:
Kernel: 6.6.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=1d370faa-bee7-4061-bbc3-06cd46203086 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 4021
date: 08/09/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus
M705 serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA201204
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3400 min/max: 2200/4662 boost: enabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3400 2: 3400 3: 3400
4: 3400 5: 3400 6: 3400 7: 3400 8: 3400 9: 3400 10: 3400 11: 3400 12: 3400
13: 3400 14: 3400 15: 3400 16: 3400 bogomips: 108597
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 0a:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: VG258 serial: <filter>
built: 2021 res: 1920x1080 dpi: 90 gamma: 1.2 size: 544x303mm (21.42x11.93")
diag: 623mm (24.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6750 XT (navi22 LLVM
16.0.6 DRM 3.54 6.6.1-zen1-1-zen) device-ID: 1002:73df memory: 11.72 GiB
unified: no
API: Vulkan v: 1.3.269 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6750 XT (RADV NAVI22) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:73df surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP OMEN Blast Headset driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:2
chip-ID: 03f0:4941 class-ID: 0300 serial: <filter>
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 14.55 TiB used: 411.32 GiB (2.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 35.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD60EFZX-68B3FN0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5640 serial: <filter>
fw-rev: 0A81 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 870 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 3.64 TiB size: 3.64 TiB (100.00%) used: 411.32 GiB (11.0%)
fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 411.32 GiB (11.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 411.32 GiB (11.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 411.32 GiB (11.0%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.24 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 35.5 C mobo: N/A gpu: amdgpu temp: 33.0 C
mem: 28.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 424 Uptime: 3m wakeups: 0 Memory: total: 32 GiB
available: 31.24 GiB used: 4.01 GiB (12.8%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 2059 libs: 581 tools: octopi,pamac,paru
Shell: fish v: 3.6.1 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-11
Last full system update: 2023-11-13
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

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.

4 Likes

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.

╭─sermor@sermor in ~
╰─λ garuda-inxi
System:
Kernel: 6.6.1-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=1d370faa-bee7-4061-bbc3-06cd46203086 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 5003
date: 10/07/2023
Battery:
Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus
M705 serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard
serial: <filter> charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 7 5700X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3462 high: 3619 min/max: 2200/4662 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3601 2: 3400
3: 3400 4: 3595 5: 3400 6: 3400 7: 3400 8: 3400 9: 3400 10: 3591 11: 3619
12: 3593 13: 3400 14: 3400 15: 3400 16: 3400 bogomips: 108596
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
vendor: Sapphire driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3 bus-ID: 0a:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting,radeon
alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: VG258 serial: <filter>
built: 2021 res: 1920x1080 dpi: 90 gamma: 1.2 size: 544x303mm (21.42x11.93")
diag: 623mm (24.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
inactive: gbm,wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6750 XT (navi22 LLVM
16.0.6 DRM 3.54 6.6.1-zen1-1-zen) device-ID: 1002:73df memory: 11.72 GiB
unified: no
API: Vulkan v: 1.3.269 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6750 XT (RADV NAVI22) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:73df surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0a:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0c:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP OMEN Blast Headset driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:2
chip-ID: 03f0:4941 class-ID: 0300 serial: <filter>
API: ALSA v: k6.6.1-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.84 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 14.55 TiB used: 414.25 GiB (2.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 PRO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 34.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD60EFZX-68B3FN0 size: 5.46 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5640 serial: <filter>
fw-rev: 0A81 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 4TB
size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-4: /dev/sdc maj-min: 8:32 vendor: Samsung model: SSD 870 EVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-5: /dev/sdd maj-min: 8:48 vendor: Samsung model: SSD 860 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
ID-6: /dev/sde maj-min: 8:64 vendor: Samsung model: SSD 870 QVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 3.64 TiB size: 3.64 TiB (100.00%) used: 414.25 GiB (11.1%)
fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 580 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 414.25 GiB (11.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 414.25 GiB (11.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 3.64 TiB size: 3.64 TiB (100.00%)
used: 414.25 GiB (11.1%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 37.5 C mobo: N/A gpu: amdgpu temp: 32.0 C
mem: 28.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Processes: 432 Uptime: 1m wakeups: 0 Memory: total: 32 GiB
available: 31.25 GiB used: 3.78 GiB (12.1%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 2059 libs: 581 tools: octopi,pamac,paru
Shell: fish v: 3.6.1 running-in: konsole inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-11
Last full system update: 2023-11-13
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Probably (Run as root to verify)
Failed units:

What is the exact make of the controller? Have you tried other USB ports or cables?

1 Like
lsusb
1 Like

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).

How can I enable the driver you mention?

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.

1 Like

Are you sure you have the xpad package installed?

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!

Yes.

Thank you all for your availability and advice.

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.

4 Likes

Thanks, I’ll do this too.

The Xbox controllers should be the same. I have no issues with it playing Elden Ring.

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.

2 Likes