Xbox (series X) Wireless Controller is not discoverable by bluetoothctl (or any other bluetooth managers) - Arch Linux

Hello,

I can not get my bluetooth to discover my xbox core wireless controller. I'm running a dual boot with a Windows 10 install. There are no issues connecting to bluetooth on windows. I am also able to connect the controller to a laptop running Fedora 29 KDE.

I have already upgraded the firmware of the controller. I have installed xpadneo.

I have tried installing xone-dkms and xboxdrv-stable-git, neither of those worked. I have since uninstalled those to avoid any conflict with xpadneo.

Bluetoothctl sees other bluetooth devices, but never shows the MAC of the controller when I start a scan and put the controller in pairing mode. I verified that it has LE enabled.

Waiting to connect to bluetoothd...[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn cis-central cis-peripheral 

My bluetooth device is an RZ608 (MediaTek MT7921K), which is using the kernel driver to work.

What am I missing that could potentially keep my Arch Linux desktop from even seeing the broadcasted MAC of the controller in order to even start the connection process?

EDIT:

So, the issue is definitely Bluez. I can see the controller broadcasting if I use bettercap and run the command 'ble.recon on'. Still haven't found a good solution, though.

Tried switching to the arch lts kernel. Didn't make a difference. Tried forcing bluetoothctl to only use le and scan le. No devices.

Tried adding the changes to /etc/bluetooth/main.conf and restarting the bluetooth service (and rebooting the computer)

Privacy = device
JustWorksRepairing = always
Class = 0x000100
FastConnectable = true

No changes in behavior.

I know it's not a driver issue, because bettercap could see the bluetooth devices. BlueZ must have a bug or something.

30 points · 10 comments · view on lemmy.world

10 Comments

wonderfulvoltaire@lemmy.world · 4 pts · 2y (2 replies)

I've had consistently good experiences with USB dongles like gulikit for example.

greyjedi@lemmy.world · 3 pts · 2y (1 reply)

Yeah, at this rate I'm probably just going to get a USB wireless adapter since it's not playing nice with my bluetooth

wonderfulvoltaire@lemmy.world · 2 pts · 2y

If it makes you feel any better I had to install windows because my dad refuses to use his phone to print anything.

olsonexi@lemmy.world · 2 pts · 2y (1 reply)

Have you added these lines to /etc/bluetooth/main.conf under [General]? This stack exchange answer says it's required:

Privacy = device
JustWorksRepairing = always
Class = 0x000100
FastConnectable = true
greyjedi@lemmy.world · 2 pts · 2y

Yeah, I tried that. Didn't make a difference, unfortunately.

helenslunch@feddit.nl · 1 pts · 2y
[ removed ]
ramble81@lemm.ee · 1 pts · 2y (3 replies)

Double check your model number on your controller. It’s possible you ended up with one that doesn’t have Bluetooth. That happened with me and I had to swap which controller I was using with my Xbox and which one I was using with my computer.

specseaweed@lemmy.world · 3 pts · 2y (1 reply)

He said he could connect to windows and fedora thru bluetooth.

I was having the same problem last night trying to connect an controller thru bluetoothctl on Mint.

ramble81@lemm.ee · 2 pts · 2y

Missed that line. Read too fast.

greyjedi@lemmy.world · 2 pts · 2y

It has bluetooth. I'm able to connect it to bluetooth on Windows 10 with the same computer and was able to connect it to a Fedora 39 KDE laptop via bluetooth, as well.

I suspect the issue is the Linux driver for the MediaTek MT7921K or the bluetooth configuration on my arch linux system needs to be adjusted somehow

Anonymous@midwest.social · 1 pts · 2y (1 reply)
[ removed ]
greyjedi@lemmy.world · 1 pts · 2y

I updated the firmware on Sunday, before even attempting to connect it to bluetooth