[SOLVED] Gamepads not recognised in lsusb or /dev/input

LordEntr0py · 2024-08-07 21:18:31

SOLUTION EDIT:

It's always a simpler thing than you think. The cables for *both* of these controllers were no good. After digging out another cable and trying it with the Stadia controller (my preferred one) everything works. The thing that helped me was

sudo dmesg -W

That was new to me and exactly what I needed to see. The connection was happening, but quickly being lost again. I could jiggle the cable and watch the connection fail again.

-------------------

original post:

Hi!

I have a problem with USB gamepads not being recognised after being plugged in.

I have an XBox360 joypad and a Stadia joypad, both of which glow and vibrate for a moment after being plugged in, but then go dead.

Output of lsusb is unchanged before and after plugging in:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 010: ID 0424:4206 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 011: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 012: ID 0424:4256 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 013: ID 0424:4252 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 014: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 015: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
Bus 001 Device 016: ID 0424:7260 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 017: ID 04d9:fa59 Holtek Semiconductor, Inc. USB Laser Game Mouse
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 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
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0d8c:0158 C-Media Electronics, Inc. Digital Hifi Audio
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

$ ls /dev/input
by-id  by-path  event0  event1  event2  event3  event4  event5  event6  event7  event8  event9  event10  event11  event12  event13  event14  event15  event16  event17  event18  event19  event20  event21  event22  event23  mice  mouse0

$ ls -l /dev/input/by-id
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-event-if02 -> ../event22
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-event-mouse -> ../event20
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-if01-event-kbd -> ../event21
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-mouse -> ../mouse0
lrwxrwxrwx - root  7 Aug 21:39 usb-Logitech_USB_Keyboard-event-if01 -> ../event19
lrwxrwxrwx - root  7 Aug 21:39 usb-Logitech_USB_Keyboard-event-kbd -> ../event17
lrwxrwxrwx - root  7 Aug 21:10 usb-SENUCN_Digital_Hifi_Audio-event-ifff -> ../event5

I have read the Archpage on gamepads multiple times and have ensured the joydev module is loaded prior to plugging in:

$ modprobe joydev

(actually I'm not sure if I should be running that as root or not; I don't get any feedback to say it hasn't worked when I run it as my own user, but I've run it as both before connecting the joypad and not had any success)

I have also tried loading usbhid with modprobe as well, but since I'm using a USB keyboard and mouse I don't think that can be the issue.

I know the usb port is working because I also have a logitech joystick which is recognised when I plug it in:

$ ls -l /dev/input/by-id
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-event-if02 -> ../event22
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-event-mouse -> ../event20
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-if01-event-kbd -> ../event21
lrwxrwxrwx - root  7 Aug 21:39 usb-04d9_USB_Laser_Game_Mouse-mouse -> ../mouse0
lrwxrwxrwx - root  7 Aug 22:12 usb-Logitech_Logitech_Extreme_3D-event-joystick -> ../event24
lrwxrwxrwx - root  7 Aug 22:12 usb-Logitech_Logitech_Extreme_3D-joystick -> ../js0
lrwxrwxrwx - root  7 Aug 21:39 usb-Logitech_USB_Keyboard-event-if01 -> ../event19
lrwxrwxrwx - root  7 Aug 21:39 usb-Logitech_USB_Keyboard-event-kbd -> ../event17
lrwxrwxrwx - root  7 Aug 21:10 usb-SENUCN_Digital_Hifi_Audio-event-ifff -> ../event5

$ ls /dev/input
by-id  by-path  event0  event1  event2  event3  event4  event5  event6  event7  event8  event9  event10  event11  event12  event13  event14  event15  event16  event17  event18  event19  event20  event21  event22  event23  event24  js0  mice  mouse0

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 010: ID 0424:4206 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 011: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 012: ID 0424:4256 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 013: ID 0424:4252 Microchip Technology, Inc. (formerly SMSC) USB4206 Smart Hub
Bus 001 Device 014: ID 0424:7240 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 015: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
Bus 001 Device 016: ID 0424:7260 Microchip Technology, Inc. (formerly SMSC) USB2 Controller Hub
Bus 001 Device 017: ID 04d9:fa59 Holtek Semiconductor, Inc. USB Laser Game Mouse
Bus 001 Device 019: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
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 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
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0d8c:0158 C-Media Electronics, Inc. Digital Hifi Audio
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

(note Bus 001 Device 19 in the lsusb output)

I normally use the linux-lts kernel, but I have also tried this on the linux kernel without success.

At this point I suspect there must either be some driver clashes, I've somehow failed to install some obvious dependency, or I'm doing something completely wrong with the module loading, but I'm reaching the limit of my know-how.

Resorting to these forums in the hope that a friendly community can help me out!

Last edited by LordEntr0py (2024-08-07 22:17:20)

V1del · 2024-08-07 21:25:28

If it's not in lsusb then it technically doesn't exist to the OS. This is before driver clashes, driver clashes would not prevent it from showing in lsusb unless they completely hose the bus.

Do a

sudo dmesg -W

and then plug in the gamepad, post the output. Can you verify whether this works on Windows/a live disk? You're sure the gamepad works/is properly charged etc?

Last edited by V1del (2024-08-07 21:27:02)

cryptearth · 2024-08-07 21:40:52

I, too, use an authentic official M$ X360 controller and I just upgraded to 6.10.3 after ZFS 2.2.5 dropped - works fine on my end (motherboard: MSI B550-A pro)

Bus 003 Device 003: ID 045e:028e Microsoft Corp. Xbox360 Controller

lrwxrwxrwx 1 root root   9  7. Aug 23:24 usb-©Microsoft_Corporation_Controller_156852D-event-joystick -> ../event8
lrwxrwxrwx 1 root root   6  7. Aug 23:24 usb-©Microsoft_Corporation_Controller_156852D-joystick -> ../js0

LordEntr0py · 2024-08-07 22:19:06

V1del wrote:

If it's not in lsusb then it technically doesn't exist to the OS. This is before driver clashes, driver clashes would not prevent it from showing in lsusb unless they completely hose the bus.
Do a
sudo dmesg -W
and then plug in the gamepad, post the output. Can you verify whether this works on Windows/a live disk? You're sure the gamepad works/is properly charged etc?

sudo dmesg -W

gave me what I needed. It was a loose cable connection, confirmed with that command. Solution edited in above.

Thank you!

Arch Linux

#1 2024-08-07 21:18:31