I’ve installed xone and xboxdrv.
The controller vibrates on plug in but the LED stays off, if I hold down the Xbox button it boots in Bluetooth mode.
Xboxdrv reports no controllers found.
lsusb reports the controller and it has a file in /dev/js0 (or something similar).
Update: there’s no js file in /dev/input
retroarch reports detection of Xbox controller on plug in.
I added my user to input group.
My system is up to date.
I installed the system with the XFCE build.
The controller works as intended on Arch, Windows and Android via USB and Bluetooth
Update 2: I installed jstest-gtk and it’s not detecting the controller at all
You must log in or register to comment.
do you use libinput or evdev?
How do I know which? I’m using whatever is default on void
Why do you think it’s NOT working if everything says it is?
The LED is off and I’ve tried retroarch and a game, retroarch detects the controller but takes no input, the game didn’t detect it at all
Did you try mapping the buttons?
The LED is off, which means the controller isn’t connected
That LED could mean anything. Just check and see if input is recognized during mapping setup. It doesn’t make sense that’s it’s showing as recognized but not working at all. I’d also check if BT is conflicting with wired connections.
Okay I made a mistake, there’s no js entry in /dev/input
What Xbox controller? 360? One? Wireless? Wired?
Model 1914 (the one currently used with Series S/X) I’m trying to connect it using the usb port
Is the controller listed in the output of “lsusb”? What does the output of “journalctl -b” say when you plug in the controller?
Yes, it’s listed in lsusb output.
Here’s svlogtail output
2025-02-12T11:59:59.37471 kern.info: [ 8726.412768] usb 4-2: new full-speed USB device number 2 using uhci_hcd 2025-02-12T11:59:59.54085 kern.info: [ 8726.578922] usb 4-2: New USB device found, idVendor=045e, idProduct=0b12, bcdDevice= 5.09 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54125 kern.info: [ 8726.578957] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 2025-02-12T11:59:59.54147 kern.info: [ 8726.578974] usb 4-2: Product: Controller 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T11:59:59.54164 kern.info: [ 8726.578986] usb 4-2: Manufacturer: Microsoft 2025-02-12T11:59:59.54191 kern.info: [ 8726.578997] usb 4-2: SerialNumber: 3039564C30313733323634323337 2025-02-12T12:00:00.14687 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: “/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2” 2025-02-12T12:00:00.15166 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.58454 kern.warn: [ 8727.623272] xone_gip: loading out-of-tree module taints kernel. 2025-02-12T12:00:00.58477 kern.notice: [ 8727.623294] xone_gip: module verification failed: signature and/or required key missing - tainting kernel 2025-02-12T12:00:00.70751 kern.info: [ 8727.745802] usb 4-2: reset full-speed USB device number 2 using uhci_hcd 2025-02-12T12:00:00.86144 kern.info: [ 8727.896637] usbcore: registered new interface driver xone-wired 2025-02-12T12:00:00.88730 user.info: Feb 12 15:00:00 mtp-probe: checking bus 4, device 2: “/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-2” 2025-02-12T12:00:00.88984 user.info: Feb 12 15:00:00 mtp-probe: bus: 4, device: 2 was not an MTP device
