Xbox 360 Controller

Hello,

I started a Retroarch Discord converstaion here on the topic, hoping they could help me. I can play N64 games through the Mupen core, however I cannot get my Xbox 360 controller to work. Tried multiple settings. Log file has an error message:
[ERROR] [Wayland]: Failed to connect to Wayland server.
and what looks to be controller related line outputs:
[INFO] [udev]: Pad #0 (/dev/input/event3) supports 0 force feedback effects. [INFO] [udev]: Pad #1 (/dev/input/event20) supports 0 force feedback effects. [INFO] [udev]: Pad #2 (/dev/input/event21) supports 0 force feedback effects.
Also, Xbox 360 controller is working perfectly in non-Retroarch related games.
I'm also already in the 'input' group as a user. Makes me think it is either Wayland or udev (although I cycled through other input drivers). I also received the picture (on Discord) and have tried to configure the Xbox 360 controller in port #1 as well, while making the ASRock and Xbox Gamepad
marked as disabled. I don't understand why these are showing up as there is only the one Xbox 360 controller connected to my PC. Any help would be appreciated.

Thanks,
Zonsopkomst

System:
Kernel: 5.15.13-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=404607fd-df6a-4caf-809e-3ed3d90d8595 rw [email protected]
quiet
cryptdevice=UUID=b11dc19b-73d3-4cce-b4e9-54931a0c1dea:luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea
root=/dev/mapper/luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea splash
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASRock model: H570M Pro4 serial: <superuser required>
UEFI: American Megatrends LLC. v: P1.50 date: 04/13/2021
Battery:
Device-1: hidpp_battery_0 model: Logitech M570 serial: <filter> charge: 35%
rechargeable: yes status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K360
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: Discharging
CPU:
Info: model: Intel Core i5-10400 bits: 64 type: MT MCP arch: Comet Lake
family: 6 model-id: 0xA5 (165) stepping: 3 microcode: 0xEA
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 4091 high: 4100 min/max: 800/4300 scaling:
driver: intel_pstate governor: performance cores: 1: 4098 2: 4097 3: 4100
4: 4097 5: 4087 6: 4100 7: 4100 8: 4092 9: 4074 10: 4058 11: 4096
12: 4100 bogomips: 69597
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: Gigabyte driver: amdgpu v: kernel bus-ID: 01:00.0
chip-ID: 1002:67df class-ID: 0300
Device-2: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.1:4 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Device-3: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.2:7 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Device-4: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 82
size: 598x336mm (23.5x13.2") diag: 686mm (27")
OpenGL: renderer: AMD Radeon RX 570 Series (POLARIS10 DRM 3.42.0
5.15.13-zen1-1-zen LLVM 13.0.0)
v: 4.6 Mesa 21.3.4 direct render: Yes
Audio:
Device-1: Intel vendor: ASRock driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:f0c8 class-ID: 0403
Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 01:00.1
chip-ID: 1002:aaf0 class-ID: 0403
Device-3: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.1:4 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Device-4: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-1.2:7 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Device-5: Logitech HD Webcam B910 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-3:3 chip-ID: 046d:0823
class-ID: 0e02 serial: <filter>
Sound Server-1: ALSA v: k5.15.13-zen1-1-zen running: yes
Sound Server-2: sndio v: N/A running: no
Sound Server-3: JACK v: 1.9.20 running: no
Sound Server-4: PulseAudio v: 15.0 running: no
Sound Server-5: PipeWire v: 0.3.43 running: yes
Network:
Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15fa class-ID: 0200
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.84 TiB used: 306.04 GiB (16.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: TeamGroup model: TM8PS7001T
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
type: SSD serial: <filter> rev: 3A0 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate
model: ST1000LM024 HN-M101MBB size: 931.51 GiB block-size: physical: 512 B
logical: 512 B type: HDD rpm: 5400 serial: <filter> rev: 0608 scheme: MBR
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 306.04 GiB (32.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 720 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 306.04 GiB (32.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 306.04 GiB (32.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 306.04 GiB (32.1%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-b11dc19b-73d3-4cce-b4e9-54931a0c1dea
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 15.5 GiB used: 24.5 MiB (0.2%)
priority: 100 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 34.0 C mobo: N/A gpu: amdgpu temp: 47.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 733
Info:
Processes: 379 Uptime: 4h 15m wakeups: 36 Memory: 15.5 GiB
used: 4.57 GiB (29.5%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1952 lib: 540 Shell: fish
v: 3.3.1 default: Bash v: 5.1.16 running-in: konsole inxi: 3.3.11

Have you tried the xboxdrv driver? It's worth a shot. :man_shrugging:

1 Like

I have used XBox 360 wired controller across many Linux distros such as Elementary, Linux Mint, Kubuntu and now Garuda Linux.

Our only difference is one thing, I use Xorg which is universally supported. I still consider Wayland as a wild west when it comes to application support. Maybe that will change once Valve releases their Steamdeck to the public and provides better support (as it comes with Wayland only by default.)

3 Likes

Given the controller works in games other than Retroarch it would seem the issue is with Retroarch rather than something in Garuda itself - perhaps, as Maynne suggests, something to do with Wayland.

People can't access links to Discord posts unless they're in that server, and it also hides it from the public web which makes it much less useful for pretty much everyone. (I have a dim opinion of Discord - it sets out to specifically create closed communities.)

3 Likes

It looks like folks have experienced issues with this controller on Wayland for a while; this thread goes back to 2017.

Toward the bottom of the discussion a fix that worked for a few people is laid out. It involves blacklisting the xpad kernel module and running xboxdrv instead. It might be worth a shot if your Discord stuff doesn't turn up a fix.

2 Likes

Since your system isn't fully update to date, you might have a RetroArch version that is suffering from the bug outlined here: Controllers not found steam/linux - r/RetroArch

update your system and you should have v 1.9.14 of RetroArch, then try resetting the controls.

1 Like

Hi All,

Thanks for the responses. I had some other items come up and must have not setup this account for notifications via email, so apologies for the delay. As BluishHumility stated, I tried updating the xboxdrv, but still had the same problem. I also uninstalled and reinstalled Retroarch. I cycled through most of the settings in Retroarch and set the input drivers to sdl2 and udev and finally back to x. I really don't know what changed, but I the Xbox 360 controller inexplicably works. I wish I learned something that I could share, but sadly I do not know what caused the controller to work. I've tried Retroarch on three different systems now and it seems finicky to me at least.

Anyways, thanks for all the suggestions!
Zonsopkomst

I'm not a fan of Discord either. But it was the route for assistance with Retroarch so I thought I would post it here for reference.

1 Like

I think I have a separate issue on updating my system, as I was using Garuda Assitant to manage updates (this is my media PC which I don't want to maintain, just for fun).

Hopefully so!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.