I cannot get Bluetooth to work consistently on Fedora 40 KDE
It has very rarely worked with various restarts of computer, services, etc, but I haven’t found a stable formula.
In the current state, it shows as disabled in system settings, and clicking enable does nothing.
Using the bluetooth tool in the taskbar shows “No Adapters Available” in the tooltip, and I can still try to pair, but it won’t find any devices.
Also noticed this is the driver: ibt-20-1-3.sfi, but I do have a …1-4 in the same dir, but not sure if 1-4 is correct, nor how/if to change that
sudo 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 Wed 2024-10-30 12:44:09 PDT; 2h 54min ago
Docs: man:bluetoothd(8)
Main PID: 1176 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 75820)
Memory: 2.0M (peak: 6.1M)
CPU: 29ms
CGroup: /system.slice/bluetooth.service
└─1176 /usr/libexec/bluetooth/bluetoothd
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support bap plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support bass plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support mcp plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support vcp plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support micp plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support ccp plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support csip plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: src/plugin.c:init_plugin() System does not support asha plugin
Oct 30 12:44:09 fedora bluetoothd[1176]: Bluetooth management interface 1.23 initialized
bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
lsusb | grep Bluetooth
Bus 001 Device 010: ID 8087:0029 Intel Corp. AX200 Bluetooth
lspci -nnk | grep -A3 -i network
6e:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Device [8086:0080]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
rfkill
ID TYPE DEVICE SOFT HARD
1 wlan phy0 unblocked unblocked
6 bluetooth hci0 unblocked unblocked
sudo dmesg | grep hci0
[ 7237.063082] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 7237.067972] Bluetooth: hci0: Device revision is 1
[ 7237.067976] Bluetooth: hci0: Secure boot is enabled
[ 7237.067977] Bluetooth: hci0: OTP lock is enabled
[ 7237.067979] Bluetooth: hci0: API lock is enabled
[ 7237.067980] Bluetooth: hci0: Debug lock is disabled
[ 7237.067981] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 7237.094803] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 7237.094813] Bluetooth: hci0: Boot Address: 0x24800
[ 7237.094815] Bluetooth: hci0: Firmware Version: 132-3.24
[ 7239.112886] Bluetooth: hci0: command 0xfc09 tx timeout
[ 7239.112898] Bluetooth: hci0: Failed to send firmware header (-110)
[ 7239.112926] Bluetooth: hci0: Intel reset sent to retry FW download
[ 7239.269053] Bluetooth: hci0: Reading supported features failed (-56)
[ 7239.269056] Bluetooth: hci0: Error reading debug features
[ 7239.269059] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[ 7239.274045] Bluetooth: hci0: Failed to read MSFT supported features (-56)
this says secure boot is enabled, but note that I dont have secure boot enabled in uefi.
TRIED:
- various systemclt stop/start disable/enable
- sudo modprobe -r btusb then sudo modprobe btusb
- Bluetooth is on in uefi, not off or auto, Ive tried toggling this.
I dual boot, when I go back into windows Bt is broken, I have to disable the Bluetooth driver, then reenable in device manager to get it working, I believe this is basically to reset whatever linux is doing to get it into a state that is carrying over to windows somehow, haven’t done a ton of tests to confirm this is 100% repro though.
Note I’ve tried OpenSuse Tumbleweed KDE as well, and same issue.
I’m not seeing any errors that jump out as to why it can’t find that controller.