Running Fedora 39 on Ryzen 7, my controller is actually the 8bitdo pro 2 which has a switch on the back which essentially makes it 4 separate bluetooth devices with different profiles and drivers in some cases. While in the XInput mode the controller will disconnect and reconnect fine, but in the Switch Pro Controller mode it will pair and work fine immediately, but after disconnecting and reconnecting there is no joystick device seen by any application. The bluetooth settings reports the controller is connected. The only thing I can do is unpair the controller and add a new device all over again.
Hi @Seth_Merkley , welcome to the community.
Best bet is going to be to monitor your logs, see if they indicate anything useful.
In real time, everything:
journalctl -f
Just bluetooth events in real time:
journalctl -f -u bluetooth
I’d also try managing the connection using bluetoothctl vs the GUI, you may see more detail there.
Hi, thanks for the reply. I just got around today to monitoring bluetooth events while I pair the controller, the only message I get is when pairing:
profiles/input/device.c:ioctl_is_connected() Can't get HIDP connection info
No other messages when trying to disconnect/reconnect.
At this stage, we’ll want to run down my list for Bluetooth. Note, the guide is primarily targeting headset users. But most of it will still apply.
Got around to troubleshooting this again. So I neglected to mention I was using KDE as my desktop environment, I installed it over the top of the usual Fedora 39 release since the chipset firmware that shipped had a bug that made it impossible to start Wayland in the initial login screen or something.
So if I switch to GNOME I can’t get the controller to connect at all. Upon initial pairing it just disconnects immediately. But if I use the GUI to pair under KDE then it works fine until I disconnect and have to unpair and repair.
Today I tried pairing using bluetoothctl and the command line. It behaves similarly to GNOME where it will pair but immediately disconnect:
Attempting to pair with E4:17:D8:D3:AC:B1
[CHG] Device E4:17:D8:D3:AC:B1 Connected: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Bonded: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Modalias: usb:v057Ep2009d0001
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 ServicesResolved: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Paired: yes
[Pro Controller]# Pairing successful
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 WakeAllowed: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 ServicesResolved: no
[CHG] Device E4:17:D8:D3:AC:B1 Connected: no
Here’s what the output looks like when I pair using the KDE GUI (I removed entries related to other nearby bluetooth devices):
bluetooth]# [CHG] Controller 14:AC:60:46:87:D4 Discovering: yes
[bluetooth]# [NEW] Device E4:17:D8:D3:AC:B1 Pro Controller
[bluetooth]# [CHG] Device E4:17:D8:D3:AC:B1 RSSI is nil
[bluetooth]# [CHG] Device E4:17:D8:25:89:B9 RSSI is nil
[bluetooth]# [CHG] Controller 14:AC:60:46:87:D4 Discovering: no
[CHG] Device E4:17:D8:D3:AC:B1 Connected: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Bonded: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Modalias: usb:v057Ep2009d0001
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 ServicesResolved: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Paired: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 WakeAllowed: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 Trusted: yes
[Pro Controller]# [CHG] Device E4:17:D8:D3:AC:B1 ServicesResolved: no
and from here the controller will work just fine and be detected.
[CHG] Device E4:17:D8:D3:AC:B1 Connected: no
[CHG] Device E4:17:D8:D3:AC:B1 Connected: yes
but here after reconnecting the controller there are no devices detected.
Hi @Seth_Merkley , is the working Bluetooth connection via KDE settings? or is It a separate KDE Bluetooth App, apologies haven’t been to KDE land as of late.
The controller is seen when pairing through the KDE Plasma’s system settings. If I pair using GNOME’s it disconnects immediately, same as with bluetoothctl.
btw, are we sure both desktop environment uses same kernel version?
Yes, both are 6.5.2-301.fc39.x86_64
Hi, did you figure it out? I am having the exact same issue. I’m using a switch pro controller, and it only connects on the first pairing. I have a 11th gen framework.