Hi guys!!! Before writing I have already read all about the driver and controller on this forum and also on an arch website.
I can’t use my controller either bluethoot or usb. I have tried any driver (xpad, xpadneo, xboxdrv) but none of them make my pc recognize the controller. I even updated the firmware of the controller through Windows. But nothing! My bluethoot does not find the controller in pairing mode, and when I use the usb cable and on the terminal dmesg |grep USB is not in the list. I really don’t know what to do, does anyone have any ideas?
I have already used this controller on this machine (with windows and fedora) without a dongle (using bluethoot on the motherboard). But this time it just doesn’t want to work.
I have my Xbox series X controller working, without xpadneo-dkms I had issues with bluetooth but after I installed that the bluetooth wireless connection worked without any issues. When you connect it using usb does it not even show up when you run “lsusb”?
Here’s mine connected using bluetooth(bluetoothctl info):
Device 00:00:00:00:00:00 (public)
Name: Xbox Wireless Controller
Alias: Xbox Wireless Controller
Appearance: 0x03c4 (964)
Icon: input-gaming
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
Okay, I tried the xpadneo-dkms again, instead of the git version, and now the usb recognizes the controller
Bus 003 Device 010: ID 045e:0b12 Microsoft Corp. Xbox controller
But bluethoot can’t see the controller. I don’t know if I got the bluethoot driver wrong, but it can see the devices I have at home, so I don’t understand why I can’t see the controller via bluetooth.
You have to press the tiny top button at the top of your controller so that it goes into pairing mode, then you can do a rescan of your bluetooth devices using whatever graphical tool you are using for bluetooth.
Yes, I know, I have tried many times, but bluethoot seems not to see the controller. I tried both with a cinnamon graphical tool and bluetoothctl from terminal, but it seems invisible.
Do you have any bluetooth errors in your logs? if you type journalctl -a -p err or use dmesg. I know you mentioned you looked in dmesg for USB devices, but would be also good to check if bluetooth has any errors.
Also if you are using an onboard bluetooth receive it might be worth into getting a usb bluetooth receiver, I’ve read more than once that people had issues with the onboard bluetooth receivers.