My Bluetooth adapter is not working, whenever I try to turn it on in GNOME Settings it quickly switches back to off. I tried to update Fedora (39 to 40) and the kernel (I think I tried 6.7.10, 6.8.4 and 6.8.5) but it didn’t work. I also tried restarting the bluetooth service with no success.
systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Sat 2024-04-13 19:32:40 -03; 1s ago
Docs: man:bluetoothd(8)
Main PID: 5625 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9328)
Memory: 572.0K (peak: 5.0M)
CPU: 46ms
CGroup: /system.slice/bluetooth.service
└─5625 /usr/libexec/bluetooth/bluetoothd
Apr 13 19:32:40 x450ca bluetoothd[5625]: Starting SDP server
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support bap plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support bass plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support mcp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support vcp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support micp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support ccp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support csip plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: Bluetooth management interface 1.22 initialized
rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
1 wlan phy0 unblocked unblocked
bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# power on
No default controller available
journalctl -xe | grep -i blue
Apr 13 18:58:02 x450ca systemd[1839]: Starting obex.service - Bluetooth OBEX service...
Apr 13 18:58:02 x450ca systemd[1839]: Started obex.service - Bluetooth OBEX service.
Apr 13 19:27:25 x450ca sudo[5191]: luiz : TTY=pts/0 ; PWD=/home/luiz ; USER=root ; COMMAND=/usr/bin/bluetoothctl
Apr 13 19:27:25 x450ca audit[5191]: USER_CMD pid=5191 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='cwd="/home/luiz" cmd="bluetoothctl" exe="/usr/bin/sudo" terminal=pts/0 res=success'
Apr 13 19:32:40 x450ca sudo[5609]: luiz : TTY=pts/0 ; PWD=/home/luiz ; USER=root ; COMMAND=/usr/bin/systemctl restart bluetooth
Apr 13 19:32:40 x450ca bluetoothd[867]: Terminating
Apr 13 19:32:40 x450ca systemd[1]: Stopping bluetooth.service - Bluetooth service...
░░ Subject: A stop job for unit bluetooth.service has begun execution
░░ A stop job for unit bluetooth.service has begun execution.
Apr 13 19:32:40 x450ca bluetoothd[867]: Stopping SDP server
Apr 13 19:32:40 x450ca bluetoothd[867]: Exit
Apr 13 19:32:40 x450ca systemd[1]: bluetooth.service: Deactivated successfully.
░░ The unit bluetooth.service has successfully entered the 'dead' state.
Apr 13 19:32:40 x450ca audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 19:32:40 x450ca systemd[1]: Stopped bluetooth.service - Bluetooth service.
░░ Subject: A stop job for unit bluetooth.service has finished
░░ A stop job for unit bluetooth.service has finished.
Apr 13 19:32:40 x450ca systemd[1]: Starting bluetooth.service - Bluetooth service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ A start job for unit bluetooth.service has begun execution.
Apr 13 19:32:40 x450ca bluetoothd[5625]: Bluetooth daemon 5.73
Apr 13 19:32:40 x450ca audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 19:32:40 x450ca systemd[1]: Started bluetooth.service - Bluetooth service.
░░ Subject: A start job for unit bluetooth.service has finished successfully
░░ A start job for unit bluetooth.service has finished successfully.
Apr 13 19:32:40 x450ca bluetoothd[5625]: Starting SDP server
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support bap plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support bass plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support mcp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support vcp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support micp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support ccp plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: src/plugin.c:init_plugin() System does not support csip plugin
Apr 13 19:32:40 x450ca bluetoothd[5625]: Bluetooth management interface 1.22 initialized
It didn’t work, but I found a setting in the BIOS where I could lock the Wireless/Bluetooth adapter, so I tried it out. Now when I run rfkill the Wi-Fi device doesn’t appear at all. The hci0 bluetooth device appears and it says that it’s unblocked though. I think there might be something wrong with my hardware.
I tried installing kernel-6.8.6, no success. I also tried Fedora 39 live USB with kernel-6.5.6, and I had the same problem.
I have discovered that my laptop has an AW-NB078H network adapter, and it seems that it ships the RTL8188CE chipset for Wi-Fi and CSR BC8510-A06 chipset for Bluetooth. Wi-Fi works fine. lsusb shows me this:
lsusb | grep CSR
Bus 004 Device 003: ID 0bda:0002 Realtek Semiconductor Corp. CSR BS8510
That’s all the information I could gather. I suspect it’s either a kernel problem or something to do with the hardware.
So, I tried a live USB with Ubuntu 22.04 LTS kernel-6.5.0 and had the same issue, so it’s not Fedora-related. I do remember of this device working on some older installation though. But I think you’re right, it must be a clone device.
I did an unhealthy amount of Internet digging for this, and apparently a Solus ISO from I don’t know when “apparently” works it would have been helpful to identify that and find out what driver was being loaded. . . Maybe more unhealthy Internet searching is required.
In other News. . . A Windows build with the Generic Bluetooth Driver “seemed to have worked too . . .”
You could consider replacing this with a newer wifi+BT adapter that has the same Mini PCIE form factor. There are 3rd party cards that use Intel chipsets with robust linux support.
I had a similar problem on my desktop computer with an Intel AX200 chipset and was able to get it working with “sudo rmmod btusb & sudo modprobe btusb” not exactly a root cause solution, but a work around that has it up and running again. I only mention it because this thread is one of the first I found when searching for bluetooth problems on Fedora 39 and reloading the kernel module was not already recommended here.
This is a cloned Bluetooth card that has historically had issues on Linux. Your card is completely different. “Intel AX200” the card in question is a clone of " Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" which is completely different.
Which is why I explained that I only mentioned it because this thread was one of the first results I got when searching for Fedora 39 bluetooth problems and this simple recommendation would have saved me a lot of time. Hoping it helps someone.
it would have been helpful to identify that and find out what driver was being loaded. . . Maybe more unhealthy Internet searching is required.