Bluetooth LE Mouse not detected in Fedora 38

Ask Fedora
, , , , , , , , ,
1

Hi everyone, I am new to Fedora. I cannot detect my Bluetooth Mouse (MX Master 3S) which uses BLE. The mouse does work as I can connect it with the dual boot windows on the same PC and even can connect it to my Android Phone. The issue seems only to arise between the Fedora PC and the mouse, as I can connect my Android Smartphone to Fedora without any problems.

I already followed this thread, but nothing worked for me:

output of inxi -Fzxx:

Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-9:7 chip-ID: 8087:0029
  Report: hciconfig ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
    lmp-v: 11 sub-v: 20ce

output of bluetoothctl show:

Controller B0:7D:64:F5:81:FF (public)
	Name: fedora
	Alias: fedora
	Class: 0x007c0104 (8126724)
	Powered: yes
	PowerState: on
	Discoverable: yes
	DiscoverableTimeout: 0x0000012c (300)
	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: 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:v1D6Bp0246d0545
	Discovering: yes
	Roles: central
	Roles: peripheral

output of: lspci:

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 980
02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller
02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller
02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea
29:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04)
2b:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
2b:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1)
2c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
2d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
2d:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
2d:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
2d:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

output of rfkill:

ID TYPE      DEVICE      SOFT      HARD
 1 wlan      phy0   entsperrt entsperrt
 2 bluetooth hci0   entsperrt entsperrt

output of uname -a:

Linux fedora 6.4.15-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep  7 00:25:01 UTC 2023 x86_64 GNU/Linux

output of 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 Fri 2023-09-15 21:17:34 CEST; 3h 40min ago
       Docs: man:bluetoothd(8)
   Main PID: 965 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38354)
     Memory: 2.6M
        CPU: 118ms
     CGroup: /system.slice/bluetooth.service
             └─965 /usr/libexec/bluetooth/bluetoothd

Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSink/sbc
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/sbc
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSink/sbc_xq
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/sbc_xq
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/faststream
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSink/opus_05
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/opus_05
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 15 22:39:31 fedora bluetoothd[965]: Endpoint registered: sender=:1.548 path=/MediaEndpoint/A2DPSource/opus_05_duplex

I also tried power on, scan on etc in bluetoothctl which directly shows my phone, but not the mouse, when I put in pairing mode. From other devices, I also know the MAC adress of the mouse and tried to connect to it directly with pair xx:xx:xx:xx:xx:xx which also did not work.

As a sidenode, before I tried Fedora 38 Desktop, I tried Silverblue 38, and strangely there the mouse immediately connected without any complains.

2

Linux Hardware Database entries for usb:8087-0029 have many reports of weird behaviour. This is often the case with systems that enable BT mouse and keyboard at boot or dual boot with an alternate OS that uses BT. I assume the “BIOS” or alternate OS drivers clash with the linux driver. Some systems allow you to disable BT in BIOS settings (but you may need USB mouse and keyboard). The last few lines of modinfo btusb list parameters needed for some systems/use cases – reset might help with mouse issues. Vendor forums for your PC model may have a solution (or tell you that there is no good solution for BLE devices).

3

Thanks for the reply, i will have a look into the BIOS and also remove the mouse from the windows system. In the meantime, here are the last few param lines of my output of modinfo btusb:

parm:           disable_scofix:Disable fixup of wrong SCO buffer size (bool)
parm:           force_scofix:Force fixup of wrong SCO buffers size (bool)
parm:           enable_autosuspend:Enable USB autosuspend by default (bool)
parm:           reset:Send HCI reset command on initialization (bool)
4

The btusb module is used by most linux distributions, so you should search for solutions across multiple distros. Arch Linux generally has excellent documentation, but Ubuntu has a very large user community so more chances of findng someone with the same issue.

Linux Kernel Parameters shows how to set parameter values on the boot command line using the grub edit mode.

You should keep the btusb paramters in mind while searching across distros for BTLE fixes related to your 8087:0029 device ID or the btusb module.