Bluetooth not working

Ask Fedora
, , , , ,
1

The bluetooth no longer works. The icon appears in Gnome but when I turn on the switch in settings it automatically turns off.

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 Fri 2023-11-24 17:02:04 CET; 2min 5s ago
       Docs: man:bluetoothd(8)
   Main PID: 1089 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 19007)
     Memory: 2.1M
        CPU: 37ms
     CGroup: /system.slice/bluetooth.service
             └─1089 /usr/libexec/bluetooth/bluetoothd

nov. 24 17:02:03 fedora bluetoothd[1089]: Starting SDP server
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support csip plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support micp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support vcp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support mcp plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support bass plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: src/plugin.c:plugin_init() System does not support bap plugin
nov. 24 17:02:03 fedora bluetoothd[1089]: Bluetooth management interface 1.22 initialized
nov. 24 17:02:04 fedora systemd[1]: Started bluetooth.service - Bluetooth service.


lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 003: ID 0b05:1939 ASUSTek Computer, Inc. [unknown]
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 005: ID 2516:0051 Cooler Master Co., Ltd. [unknown]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 003 Device 003: ID 04d9:a1cd Holtek Semiconductor, Inc. [unknown]
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub


bluetoothctl show
No default controller available
2

This seems to indicate that bluetooth is an intel chipset, and may be the same as mine.
You may be able to see more info on that particular device with lspci -nnk and selecting the info for the wifi network device.
Then add the output of lsusb -v -s 001:002 to show the detailed portion for that particular bluetooth device.

In my experience usually intel packages the wifi and bluetooth devices together so the combination of devices show on the different listings even though they are a single chipset

Mine shows as this with ‘lspci -nnk’

05:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz [8086:0024]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

and this with ‘lsusb’

Bus 001 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth

This is the same device seen on both the bluetooth side and the wifi side.

3

I have encountered problems with Bluetooth as well, however the first device I connected, a pair of Treblab XR200 earbuds seem to work just fine. I paired 3 other headphones, which connected and then disconnected with a few seconds. The internal bluetooth is Intel, but I got the same behaviour with an Asus bluetooth dongle.
lsusb gives, in part:
Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 007: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth
This is a fresh install of Fedora 39 Cinnamon on a Dell Latitude 5590.
Just updated and rebooted, no change in operation.

4

I seem to be having the same issue. I came back from several days away to find that my bluetooth keyboard/mouse combo no longer worked. I figured the problem would solve itself after update/restart but nada.

I also have an Intel Ax200 network controller. When I run

[20:28:56]$ hciconfig
hci0:   Type: Primary  Bus: USB
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN 
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:4 acl:0 sco:0 commands:1 errors:0

If I run hciconfig up nothing happens - see output:

[20:37:51]$ sudo hciconfig up
hci0:   Type: Primary  Bus: USB
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN 
        RX bytes:0 acl:0 sco:0 events:0 errors:0
        TX bytes:4 acl:0 sco:0 commands:1 errors:0
5

My systemctl status bluetooth output looks similar to yours

[20:44:37]$ 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 Tue 2023-12-26 20:27:56 EST; 16min ago
       Docs: man:bluetoothd(8)
   Main PID: 10848 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38361)
     Memory: 600.0K
        CPU: 32ms
     CGroup: /system.slice/bluetooth.service
             └─10848 /usr/libexec/bluetooth/bluetoothd

Dec 26 20:27:56 drcomputer systemd[1]: Started bluetooth.service - Bluetooth service.
Dec 26 20:27:56 drcomputer bluetoothd[10848]: Starting SDP server
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support csip plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support micp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support vcp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support mcp plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support bass plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: src/plugin.c:plugin_init() System does not support bap plugin
Dec 26 20:27:56 drcomputer bluetoothd[10848]: Bluetooth management interface 1.22 initialized
6

Similar story here – came back to the computer after the holidays and found my bluetooth audio not working. My mouse (thankfully) is working great.

Jan 03 11:29:19 afterman bluetoothd[1439440]: Bluetooth daemon 5.71
Jan 03 11:29:19 afterman bluetoothd[1439440]: Starting SDP server
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 03 11:29:19 afterman bluetoothd[1439440]: Bluetooth management interface 1.22 initialized
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Battery Provider Manager created
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to clear UUIDs: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Failed to add UUID: Failed (0x03)
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_294
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_16676
Jan 03 11:29:19 afterman bluetoothd[1439440]: Player registered: sender=:1.49 path=/_1_133
Jan 03 11:29:20 afterman bluetoothd[1439440]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 03 11:29:20 afterman bluetoothd[1439440]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/ldac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aptx
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/aac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aac
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/sbc
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/sbc
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/sbc_xq
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/sbc_xq
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/faststream
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/opus_05
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/opus_05
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 03 11:30:01 afterman bluetoothd[1439440]: Endpoint registered: sender=:1.7839 path=/MediaEndpoint/A2DPSource/opus_05_duplex

Connecting my Sony WH-1000XM4s gives:

Jan 03 11:37:46 afterman bluetoothd[1439440]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 14:3F:A6:09:5F:0C: Protocol not available

which echos the error message displayed in bluez

7

I’ve updated to 6.6.9-200.fc39.x86_6 and haven’t been able to repoduce this

8

Well I can’t be the only who is having the problem of having bluetooth break after the most recent update AGAIN

9

What kernel are you currently running, I have had Bluetooth problems on 6.7.11 so I changed my default kernel to 6.7.7

11

What kernel are you running? I have found kernel 6.7.7 to be more stable for Bluetooth.

You can try bluetoothctl devices Check if your device is in the list. We can try :

Pairing the Device: If your device is not listed, try putting the mouse in pairing mode. Refer to the mouse manual for instructions. Then, run:
bluetoothctl then Within the Bluetooth CLI, enter the following commands:

power on
agent on
default-agent
scan on

After scanning, you should see your mouse in the list. Pair with it using:
pair XX:XX:XX:XX:XX:XX

systemctl restart bluetooth

12

Same problems after updating kernel twice in a row (Fedora 39). It seems every other kernel update kills bluetooth on Fedora. Can someone please check bluetooth on this chipset in the future? My fix is to reboot to two kernels back every time I restart. I’m on KDE, not Gnome, but the same behavior even on a terminal with the dreaded:
bluetoothctl show
No default controller available
…yet, I still get the “Intel Corp. AX200 Bluetooth” showing up on “lsusb”. Multiple devices with same chipset for bluetooth.

Currently running kernel 6.7.10-200.fc39.x86_64 (working on F39 with bluetooth)

13

Hi, is there any update on this issue?

My bluetooth also stopped working suddenly.

I have:

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 Fri 2024-10-18 12:08:35 CEST; 16min ago
Docs: man:bluetoothd(8)
Main PID: 57751 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 17946)
Memory: 776.0K
CPU: 59ms
CGroup: /system.slice/bluetooth.service
└─57751 /usr/libexec/bluetooth/bluetoothd -d

Oct 18 12:08:45 fedora bluetoothd[57751]: src/adapter.c:discovering_callback() hci0 type 7 discovering 0 method 0
Oct 18 12:08:45 fedora bluetoothd[57751]: src/adapter.c:trigger_start_discovery()
Oct 18 12:08:45 fedora bluetoothd[57751]: src/adapter.c:cancel_passive_scanning()
Oct 18 12:08:50 fedora bluetoothd[57751]: src/adapter.c:start_discovery_timeout()
Oct 18 12:08:50 fedora bluetoothd[57751]: src/adapter.c:start_discovery_timeout() adapter->current_discovery_filter == 0
Oct 18 12:08:50 fedora bluetoothd[57751]: src/shared/mgmt.c:send_request() [0x0000] command 0x0023
Oct 18 12:08:50 fedora bluetoothd[57751]: src/shared/mgmt.c:can_read_data() [0x0000] event 0x0013
Oct 18 12:08:50 fedora bluetoothd[57751]: src/adapter.c:discovering_callback() hci0 type 7 discovering 1 method 0
Oct 18 12:08:50 fedora bluetoothd[57751]: src/shared/mgmt.c:can_read_data() [0x0000] command 0x0023 complete: 0x00
Oct 18 12:08:50 fedora bluetoothd[57751]: src/adapter.c:start_discovery_complete() status 0x00

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 13d3:56ff IMC Networks Integrated Camera
Bus 001 Device 003: ID 0bda:4853 Realtek Semiconductor Corp. Bluetooth Radio
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 048d:c976 Integrated Technology Express, Inc. ITE Device(8176)
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

bluetoothctl show
Controller B8:1E:A4:67:CE:8A (public)
Manufacturer: 0x005d (93)
Version: 0x0b (11)
Name: fedora
Alias: fedora
Class: 0x007c010c (8126732)
Powered: yes
PowerState: on
Discoverable: yes
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: Message Notification Se… (00001133-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb)
UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (00005005-0000-1000-8000-0002ee000001)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d054D
Discovering: yes
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x0a (10)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
SupportedCapabilities.MinTxPower: 0x0001 (1)
SupportedCapabilities.MaxTxPower: 0x001d (29)
SupportedCapabilities.MaxAdvLen: 0xfb (251)
SupportedCapabilities.MaxScnRspLen: 0xfb (251)
SupportedFeatures: CanSetTxPower
SupportedFeatures: HardwareOffload

bluetoothctl devices
(base) mihai@fedora:~$ bluetoothctl
Waiting to connect to bluetoothd…[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
[bluetooth]# Default agent request successful
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]#

And I simply get no devices.

I’ve also been through: Troubleshooting Bluetooth problems :: Fedora Docs

hciconfig
hci0: Type: Primary Bus: USB
BD Address: B8:1E:A4:67:CE:8A ACL MTU: 1021:6 SCO MTU: 255:12
UP RUNNING PSCAN ISCAN
RX bytes:6347 acl:0 sco:0 events:693 errors:0
TX bytes:83047 acl:0 sco:0 commands:682 errors:0

sudo dmesg -w | grep Bluetooth
[ 1.618037] usb 1-4: Product: Bluetooth Radio
[ 14.003979] Bluetooth: Core ver 2.22
[ 14.004006] Bluetooth: HCI device and connection manager initialized
[ 14.004010] Bluetooth: HCI socket layer initialized
[ 14.004013] Bluetooth: L2CAP socket layer initialized
[ 14.004020] Bluetooth: SCO socket layer initialized
[ 14.184175] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[ 14.187185] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 14.187189] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[ 14.192781] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[ 14.202207] Bluetooth: hci0: RTL: cfg_sz 6, total sz 65555
[ 15.050259] Bluetooth: hci0: RTL: fw version 0x048f4008
[ 15.225212] Bluetooth: hci0: AOSP extensions version v1.00
[ 15.225223] Bluetooth: hci0: AOSP quality report is supported
[ 16.598868] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 16.598871] Bluetooth: BNEP filters: protocol multicast
[ 16.598876] Bluetooth: BNEP socket layer initialized
[ 16.602246] Bluetooth: MGMT ver 1.23
[ 108.515555] Bluetooth: RFCOMM TTY layer initialized
[ 108.515562] Bluetooth: RFCOMM socket layer initialized
[ 108.515567] Bluetooth: RFCOMM ver 1.11
[ 158.034089] Bluetooth: hci0: AOSP extensions version v1.00
[ 158.034095] Bluetooth: hci0: AOSP quality report is supported
[11505.038471] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[11505.039995] Bluetooth: hci0: RTL: rom_version status=0 version=1
[11505.040000] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[11505.040092] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[11505.043034] Bluetooth: hci0: RTL: cfg_sz 6, total sz 65555
[11505.890003] Bluetooth: hci0: RTL: fw version 0x048f4008
[11506.064993] Bluetooth: hci0: AOSP extensions version v1.00
[11506.065000] Bluetooth: hci0: AOSP quality report is supported
[11506.065265] Bluetooth: MGMT ver 1.23
[157280.697515] Bluetooth: hci0: AOSP extensions version v1.00
[157280.697522] Bluetooth: hci0: AOSP quality report is supported
[157374.388404] Bluetooth: hci0: AOSP extensions version v1.00
[157374.388415] Bluetooth: hci0: AOSP quality report is supported
[158009.957027] Bluetooth: hci0: AOSP extensions version v1.00
[158009.957072] Bluetooth: hci0: AOSP quality report is supported

I am a bit lost, maybe somewone could help!

Loads of thanks

14

Fedora has gone through 2 release versions since this thread was initially started.
Because the OP was on a much older release and this thread is a year old (and was based on F39 which will become EOL in about a month) I suggest you repost while opening your own thread. You are much more likely to get an applicable suggestion with the newer releases. (F40 has been out for about 6 months and F41 is scheduled for release later this month)

15

It’s an old one. If this can help, i have normally 2 devices: mouse and headphones. Whenever my mouse stops working, if i turn on the headphones, device discovery will turn on again and devices can connect again. Now, i don’t know why that happens, but it might help someone here and Fedora to solve the problem.

My bluetooth card is part of the wifi card, which is Intel Corporation Wi-Fi 6E(802.11ax) AX210. I’m also on Fedora 41 Workstation.