KUbuntu Version: 24.04.1 LTS
Desktop Environment (if applicable): KDE Plasma
Problem Description:
On my new computer, I have never been able to enable bluetooth or successfully scan for or add devices. The system tray does try to scan for devices, which it doesn’t find, and the Bluetooth system settings indicate that bluetooth is disabled and nothing happens when I click ‘Enable’. I have a dual boot and Bluetooth works fine in Windows.
Relevant System Information:
$ uname -a
Linux 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
- From inxi:
Mobo: ASUSTeK model: Z890 MAX GAMING WIFI7 v: Rev 1.xx
Bluetooth:
Device-1: IMC Networks Wireless_Device driver: btusb type: USB
Report: hciconfig ID: hci0 rfk-id: 2 state: down
bt-service: enabled,running rfk-block: hardware: no software: no
address: 00:00:00:00:00:00
- From lsusb:
Bus 003 Device 006: ID 13d3:3602 IMC Networks Wireless_Device
- From usb-devices:
usb-devices:
Bus=03 Lev=01 Prnt=08 Port=13 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3602 Rev=01.00
S: Manufacturer=MediaTek Inc.
S: Product=Wireless_Device
S: SerialNumber=000000000
Conclusion: The manufacturer is MediaTek; the vendor is IMC Networks; the product name is Wireless_Device.
- bluetooth service is running:
$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-01-12 14:31:02 CST; 1h 2min ago
Docs: man:bluetoothd(8)
Main PID: 2322 (bluetoothd)
Status: "Running"
- Active modules:
$ lsmod |grep bt
btusb 77824 0
btrtl 32768 1 btusb
btintel 57344 1 btusb
btbcm 24576 1 btusb
btmtk 12288 1 btusb
bluetooth 1028096 15 btrtl,btmtk,btintel,btbcm,bnep,btusb
Screenshots or Error Messages:
- From dmesg (see below). Last line apparently indicates it chokes on the device:
dmesg:
[ 20.560636] Bluetooth: Core ver 2.22
[ 20.560649] NET: Registered PF_BLUETOOTH protocol family
[ 20.560650] Bluetooth: HCI device and connection manager initialized
[ 20.560652] Bluetooth: HCI socket layer initialized
[ 20.560654] Bluetooth: L2CAP socket layer initialized
[ 20.560662] Bluetooth: SCO socket layer initialized
[ 20.737210] Bluetooth: hci0: Opcode 0x0c03 failed: -16
- Some lines from systemlog that might indicate bluetooth service is unable to load a number of plugins:
Jan 12 14:31:02 pm-cpp systemd[1]: Started bluetooth.service - Bluetooth service.
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: Starting SDP server
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 12 14:31:02 pm-cpp bluetoothd[2322]: Bluetooth management interface 1.22 initialized
What I’ve Tried:
I tried installing firmware-realtek-rtl8723cs-bt and Bluetooth support (metapackage) from the repos and restarting the OS. These actions had no effects.
I gather there are a number of linux drivers that are supposed to help realtek devices work, but I’m not clear on which, if any, might help with this device. It doesn’t help that the device name / serial number are vague.
Maybe the solution is to wait for or install a more advanced hardware support version of the kernel. My experience with upgrading to a more advanced kernel to solve problems in the past have not been good–problem not solved and new problems introduced that required reinstalling my OS. Or maybe I should file a bug report with launchpad in the hopes this will prompt a fix sooner?