this post was submitted on 01 Mar 2024
29 points (96.8% liked)

Linux Gaming

14926 readers
2 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 1 year ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 8 months ago (1 children)

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

[–] [email protected] 3 points 8 months ago (1 children)

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

[–] [email protected] 2 points 8 months ago

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