Bluetooth adapter doesn't scan/discover devices

udarh9 · January 5, 2025, 6:46pm

Hello,

So as the title says, for some reason my BT doesn’t work anymore for me…
I’ve used other and older kernel versions, bluez package, snapshots, all that was provided by the Tumbleweed boot screen. Got into rescue mode “as a last resort” for perhaps a better isolation or whatever.

Still not even bluetoothctl in that instance is unable to find my headphone(s) devices. Having that said i’m beginning to think it is a hardware failure maybe. But how can it be if Wi-Fi is working, not perfectly but fair enough? Being on the same chipset for the bluetooth functionality afaik?

I don’t know nevertheless and I have no ideea what to try as my know-how is very limited. I use Linux just for very trivial stuff, so I expect this basic functionality to work anytime and stop using cables hehe

Anyway if somebody can shed some light in resolving this issue would be greatly appreciated. Here’s some system info, will provide more if necessary:

sudo hwinfo --bluetooth

sudo hwinfo --bluetooth
02: USB 00.1: 11500 Bluetooth Device
[Created at usb.122]
Unique ID: …
Parent ID: …
SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-2/3-2:1.1
SysFS BusID: 3-2:1.1
Hardware Class: bluetooth
Model: “IMC Networks Bluetooth Radio”
Hotplug: USB
Vendor: usb 0x13d3 “IMC Networks”
Device: usb 0x3571 “Bluetooth Radio”
Serial ID: “00e04c000001”
Driver: “btusb”
Driver Modules: “btusb”
Speed: 12 Mbps
Module Alias: “usb:v13D3p3571d0000dcE0dsc01dp01icE0isc01ip01in01”
Driver Info #0:
Driver Status: btusb is active
Driver Activation Cmd: “modprobe btusb”
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #3 (Hub)

dmesg | grep -i blue

[ 2.540943] [ T143] usb 3-2: Product: Bluetooth Radio
[ 5.935793] [ T803] Bluetooth: Core ver 2.22
[ 5.980561] [ T803] NET: Registered PF_BLUETOOTH protocol family
[ 5.980564] [ T803] Bluetooth: HCI device and connection manager initialized
[ 5.980570] [ T803] Bluetooth: HCI socket layer initialized
[ 5.980573] [ T803] Bluetooth: L2CAP socket layer initialized
[ 5.980578] [ T803] Bluetooth: SCO socket layer initialized
[ 6.104755] [ T178] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852
[ 6.106749] [ T178] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 6.107176] [ T178] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin
[ 6.111311] [ T178] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin
[ 6.112773] [ T178] Bluetooth: hci0: RTL: cfg_sz 6, total sz 65603
[ 6.697748] [ T178] Bluetooth: hci0: RTL: fw version 0x04479301
[ 6.824222] [ T178] Bluetooth: hci0: AOSP extensions version v1.00
[ 6.825244] [ T178] Bluetooth: hci0: AOSP quality report is supported

lsusb | grep -i blue

Bus 003 Device 003: ID 13d3:3571 IMC Networks Bluetooth Radio

Removed those for now(they were with i+), don’t know what is with kf6-stuff so i’ve let them as they are because of too many dependencies. Maybe i can try something else instead of them, but what?

sudo zypper se -s bluez

S  | Name                      | Type    | Version                                              | Arch   | Repository
---+---------------------------+---------+------------------------------------------------------+--------+------------------------
   | bluez                     | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-auto-enable-devices | package | 5.79-1.2                                             | noarch | openSUSE-Tumbleweed-Oss
   | bluez-cups                | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-deprecated          | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-devel               | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-devel-32bit         | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-firmware            | package | 1.2-150.4                                            | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-obexd               | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-devel            | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-imports          | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-udev             | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-test                | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-zsh-completion      | package | 5.79-1.2                                             | noarch | openSUSE-Tumbleweed-Oss
i  | kf6-bluez-qt              | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
   | kf6-bluez-qt-devel        | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
i  | kf6-bluez-qt-imports      | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
i  | libKF5BluezQt6            | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
i  | libKF6BluezQt6            | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
   | python310-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python311-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python312-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python313-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss

sudo zypper lr -u

Repository priorities in effect:                                                                                         (See 'zypper lr -P' for details)
      90 (raised priority)  :  1 repository
      99 (default priority) :  9 repositories

#  | Alias         | Name                | Enabled | GPG Check | Refresh | URI
---+---------------+---------------------+---------+-----------+---------+-------------------------------------------------------------------------------
 1 | Google-Chrome | Google-Chrome       | Yes     | (r ) Yes  | Yes     | https://dl.google.com/linux/chrome/rpm/stable/x86_64
 2 | VLC           | VLC                 | Yes     | (r ) Yes  | Yes     | https://download.videolan.org/SuSE/Tumbleweed
 3 | brave-browser | Brave Browser       | Yes     | (r ) Yes  | Yes     | https://brave-browser-rpm-release.s3.brave.com/x86_64
 4 | code          | Visual Studio Code  | Yes     | (r ) Yes  | Yes     | https://packages.microsoft.com/yumrepos/vscode
 5 | packman       | packman             | Yes     | (r ) Yes  | Yes     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
 6 | repo-debug    | openSUSE-Tumblewe-> | No      | ----      | ----    | http://download.opensuse.org/debug/tumbleweed/repo/oss/
 7 | repo-non-oss  | openSUSE-Tumblewe-> | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/non-oss/
 8 | repo-openh264 | Open H.264 Codec -> | Yes     | (r ) Yes  | Yes     | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
 9 | repo-oss      | openSUSE-Tumblewe-> | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/tumbleweed/repo/oss/
10 | repo-source   | openSUSE-Tumblewe-> | No      | ----      | ----    | http://download.opensuse.org/source/tumbleweed/repo/oss/
11 | repo-update   | openSUSE-Tumblewe-> | Yes     | (r ) Yes  | Yes     | http://download.opensuse.org/update/tumbleweed/
12 | snappy        | snappy              | Yes     | (r ) Yes  | Yes     | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed/

I really don’t get it, this worked for my some time ago, with some hiccups, but fine enough. Any suggestions?

malcolmlewis · January 5, 2025, 7:00pm

@udarh9 Hi and welcome to the forum
You will need bluez, bluez-firmware and bluez-auto-enable-devices also is kernel-firmware-bluetooth installed?

udarh9 · January 5, 2025, 8:12pm

Yes,

The rest were all installed

yoman · January 5, 2025, 8:31pm

@udarh9 , hi

share the output of these two commands:

sudo rfkill list all

sudo systemctl status bluetooth

This will help identify if your Bluetooth is blocked (software or hardware) and check the status of the Bluetooth service on your system. The output will show us if there are any obvious issues preventing your Bluetooth from working.

udarh9 · January 5, 2025, 10:06pm

sudo systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Mon 2025-01-06 00:00:12 EET; 1s ago
 Invocation: c14b5b034b2f4f519b353414256c8cb1
       Docs: man:bluetoothd(8)
   Main PID: 8823 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18310)
        CPU: 62ms
     CGroup: /system.slice/bluetooth.service
             └─8823 /usr/libexec/bluetooth/bluetoothd

Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_g
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_g
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 06 00:00:12 <...> bluetoothd[8823]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05_duplex

sudo rfkill list

0: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

yoman · January 5, 2025, 11:29pm

@udarh9

Since all necessary packages are installed and your hardware is correctly detected, this might be a configuration issue. Here’s a workaround that often helps with shared WiFi/Bluetooth chipsets:

Enable Airplane Mode
Wait a few seconds
Turn Bluetooth ON while keeping Airplane Mode active
Try to connect your Bluetooth device
Once connected, disable Airplane Mode
Re-enable WiFi

This method helps reset the shared WiFi/Bluetooth controller and often resolves connection issues. It’s particularly effective with Realtek chipsets like your RTL8852BU.If this works, you’ll only need to do it once, as subsequent connections should work normally.

If the above solution doesn’t work, you can try these additional troubleshooting :

Reload the Bluetooth module

sudo modprobe -r btusb
sudo modprobe btusb

Check the Bluetooth logs for any error messages:
sudo journalctl -u bluetooth -n 50

These commands will help identify any potential driver or firmware issues that might be preventing your Bluetooth from working properly.

udarh9 · January 6, 2025, 9:54am

Didn’t find any airplane mode but this should do the trick also by unloading the kernel module for wifi entirely I guess:

sudo modprobe -rv rtw89_8852be

[sudo] password for user: 
rmmod rtw89_8852be
rmmod rtw89_pci
rmmod rtw89_8852b

However I’ve tried this combo before with no effective results, anyway:

bluetoothctl

[bluetooth]# hci0 new_settings: bondable ssp br/edr le secure-conn wide-band-speech cis-central cis-peripheral 
[bluetooth]# Agent registered
[bluetooth]# [CHG] Controller XX:XX.. Pairable: yes
[bluetooth]# agent on
Agent is already registered
[bluetooth]# angent off
Invalid command in menu main: angent
[bluetooth]# agent off
[bluetooth]# hci0 new_settings: ssp br/edr le secure-conn wide-band-speech cis-central cis-peripheral 
[bluetooth]# Agent unregistered
[bluetooth]# [CHG] Controller XX:XX.. Pairable: no
[bluetooth]# power off
[bluetooth]# Changing power off succeeded
[bluetooth]# power on
[bluetooth]# [CHG] Controller XX:XX.. PowerState: off-enabling
[bluetooth]# hci0 class of device changed: 0x6c010c
[bluetooth]# [CHG] Controller XX:XX.. Class: 0x006c010c (7078156)
[bluetooth]# hci0 new_settings: powered ssp br/edr le secure-conn wide-band-speech cis-central cis-peripheral 
[bluetooth]# Changing power on succeeded
[bluetooth]# [CHG] Controller XX:XX.. PowerState: on
[bluetooth]# [CHG] Controller XX:XX.. Powered: yes
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller XX:XX.. Discovering: yes
[bluetooth]# devices
[bluetooth]# devices
[bluetooth]# devices
[bluetooth]#

As you can see no devices get discovered above.

sudo journalctl -u bluetooth -n 50

Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSink/sbc
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSource/sbc
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSource/faststream
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSink/opus_05
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSource/opus_05
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 06 11:09:26 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.205 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/ldac
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/aac
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/aac
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_g
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_g
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/sbc
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/sbc
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 06 11:09:27 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/ldac
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSink/aac
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/aac
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_g
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_g
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSink/sbc
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/sbc
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 06 11:09:41 wtv bluetoothd[8823]: Endpoint unregistered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 06 11:09:41 wtv bluetoothd[8823]: Battery Provider Manager destroyed
Jan 06 11:09:42 wtv bluetoothd[8823]: Battery Provider Manager created
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/ldac
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/aac
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/aac
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_g
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_g
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/sbc
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/sbc
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 06 11:09:42 wtv bluetoothd[8823]: Endpoint registered: sender=:1.233 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 06 11:17:24 wtv bluetoothd[8823]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down

I tried also with btmon for live monitoring, alien stuff for me there, but no mac addresses jumped in my eyes though.
So I still don’t understand what is the problem, what to try else?

matbhm · January 6, 2025, 10:30am

In my opinion, the bluez packages are not installed, but there would be an ‘i’ in the first column.

udarh9 · January 6, 2025, 10:38am

i+ | bluez                     | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
i+ | bluez-auto-enable-devices | package | 5.79-1.2                                             | noarch | openSUSE-Tumbleweed-Oss
i  | bluez-cups                | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-deprecated          | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-devel               | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-devel-32bit         | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
i+ | bluez-firmware            | package | 1.2-150.4                                            | x86_64 | openSUSE-Tumbleweed-Oss
i  | bluez-obexd               | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-devel            | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-imports          | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-qt-udev             | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-test                | package | 5.79-1.2                                             | x86_64 | openSUSE-Tumbleweed-Oss
   | bluez-zsh-completion      | package | 5.79-1.2                                             | noarch | openSUSE-Tumbleweed-Oss
i  | kf6-bluez-qt              | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
   | kf6-bluez-qt-devel        | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
i  | kf6-bluez-qt-imports      | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
i  | libKF5BluezQt6            | package | 5.116.0-1.1                                          | x86_64 | openSUSE-Tumbleweed-Oss
i  | libKF6BluezQt6            | package | 6.9.0-1.1                                            | x86_64 | openSUSE-Tumbleweed-Oss
   | python310-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python311-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python312-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss
   | python313-pybluez         | package | 0.23+git5096047f90a1f6a74ceb250aef6243e144170f92-2.7 | x86_64 | openSUSE-Tumbleweed-Oss

hui · January 6, 2025, 11:11am

Is it a Mediatek BT device?

udarh9 · January 6, 2025, 11:22am

I think the internal adapter is a combo one from Realtek. Or in the context of what are you asking for the BT device?

hui · January 6, 2025, 11:46am

I asked because there are known (upstream) BT driver defects starting from kernel 6.11.x for Mediatek chips/devices. But nvm if you use Realtek.

Sauerland · January 6, 2025, 3:23pm

Bluetooth Chips will be shown with:
lsusb
Post it and also post
/sbin/lspci -nnk | grep -iA3 net

udarh9 · January 6, 2025, 3:57pm

01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
	Subsystem: AzureWave Device [1a3b:5471]
	Kernel driver in use: rtw89_8852be
	Kernel modules: rtw89_8852be

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 003 Device 003: ID 13d3:3571 IMC Networks Bluetooth Radio
Bus 003 Device 004: ID 13d3:54a1 IMC Networks USB2.0 HD UVC WebCam
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Sauerland · January 6, 2025, 4:24pm

See here:

Disable and enable it?

udarh9 · January 6, 2025, 5:45pm

Yea, thx, I did. Booted with BT disabled from BIOS. Checked lsusb to make sure it really doesn’t “exist” anymore and all that. Even started bluetoothctl but it complained like a little girl of missing controller and etc. So I’ve rebooted, enabled it and then ran this:

sudo journalctl --since “30 min ago” | grep -i failed

Jan 06 19:35:01 wtv systemd[1915]: gnome-terminal-server.service: Failed with result 'exit-code'.
Jan 06 19:35:01 wtv systemd[1915]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Jan 06 19:35:01 wtv systemd[1915]: blueman-applet.service: Failed with result 'exit-code'.
Jan 06 19:35:01 wtv dbus-broker-launch[1349]: Activation request for 'org.bluez' failed.
Jan 06 19:35:01 wtv dbus-broker-launch[1349]: Activation request for 'org.bluez' failed.
Jan 06 19:35:03 wtv dbus-broker-launch[1349]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 06 19:35:03 wtv NetworkManager[1588]: <warn>  [1736184903.1145] dispatcher: (11) failed (after 0.002 sec): Could not activate remote peer 'org.freedesktop.nm_dispatcher': activation request failed: unit is invalid
Jan 06 19:35:03 wtv dbus-broker-launch[1349]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 06 19:35:18 wtv kernel: ee1004 6-0051: probe with driver ee1004 failed with error -5
Jan 06 19:35:18 wtv kernel: asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Jan 06 19:35:18 wtv kernel: asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -19
Jan 06 19:35:18 wtv kernel: asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
Jan 06 19:35:18 wtv (udev-worker)[815]: controlC0: Process '/usr/sbin/alsactl restore 0' failed with exit code 99.
Jan 06 19:35:19 wtv (udev-worker)[814]: controlC1: Process '/usr/sbin/alsactl restore 1' failed with exit code 99.
Jan 06 19:35:21 wtv irqbalance[1354]: thermal: failed to receive messages.
Jan 06 19:35:21 wtv irqbalance[1354]: Failed to initialize thermal events.
Jan 06 19:35:37 wtv sddm-helper[1895]: Failed to write utmpx:  No such file or directory
Jan 06 19:35:39 wtv accounts-daemon[2575]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed

So no, unfortunately it still doesn’t work…

marel · January 11, 2025, 12:56pm

udarh9:

[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller XX:XX.. Discovering: yes
[bluetooth]# devices
[bluetooth]# devices
[bluetooth]# devices

So if you run “scan on” in bluetoothctl you do not see devices popping up?

For me it looks like:

[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller 00:1A:7D:DA:71:13 Discovering: yes
[bluetooth]# [NEW] Device 5D:B1:64:2A:B0:5B 5D-B1-64-2A-B0-5B
[bluetooth]# [CHG] Device 5D:B1:64:2A:B0:5B ManufacturerData.Key: 0x004c (76)
[bluetooth]# [CHG] Device 5D:B1:64:2A:B0:5B ManufacturerData.Value:
[bluetooth]#   01 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00  ................
[bluetooth]#   00                                               .               
[bluetooth]# [CHG] Device D8:5A:37:9B:44:05 RSSI: 0xffffffb8 (-72)
[bluetooth]# [CHG] Device D8:5A:37:9B:44:05 ManufacturerData.Key: 0x0702 (1794)
[bluetooth]# [CHG] Device D8:5A:37:9B:44:05 ManufacturerData.Value:
[bluetooth]#   21 0a 04 00 00 09 00                             !......         
[bluetooth]# [CHG] Device 5D:B1:60:2A:D0:5B ManufacturerData.Key: 0x004c (76)
[bluetooth]# [CHG] Device 5D:B1:60:2A:D0:5B ManufacturerData.Value:
[bluetooth]#   01 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00  ................

Is the device in a laptop? If so, it could be that the antenna connection is broken. Typically you then see no device unless they are very close by. I.e. try with a BT device very close by. If you see a device this way, report the RSSI.

The other option is to make the card discoverable: power on, discoverable on. Now use another device (for example your smartphone) to scan. Be sure to do that soon after making the device discoverable as the longer it takes the less message will be sent.

If that is also not successful you could check the antenna connection and if that is no option I think it is better to go for a separate BT dongle and choose one that is well supported:

udarh9 · January 11, 2025, 3:51pm

How could the antenna be broken if my wi-fi works? This realtek adapter is a combo one afaik, so the same chipset is used for both wifi and bluetooth, hence I would say that they use also the same antenna but on different frequencies/channels, innit? Also even without antennas it should work, at least very closely.

I did try to find out also if there is a way to switch on different antenna(cuz’ well maybe there are 2) or channels but other priorities came in so i didn’t find a way to try that yet.

It is worth mentioning that i’ve disabled wifi from bios and booted only with bt, but still didn’t work, neither from GUI nor CLI. Installed also some deprecated bluez to access hci0 but as of now i’ve forgot what was I trying to to. Will Investigate further some time soon.

Last but not least, yes it’s a laptop, but it is out of discussion in buying a separate USB dongle or a new mini PCIe card(maybe after warranty expires), i would rather use the jack output :)) onwards

udarh9 · January 11, 2025, 6:18pm

@marel

Now i am really confused, everything works again for some reason:

discoverable on - my phone was able to detect the system, canceled the pairing.
discoverable off
agent off > power off
agent on > power on > scan on - started to see a lot of devices again
pairing successful

Interesting…thx much!

udarh9 · January 17, 2025, 11:39am

Again it stopped working . So that solution was a temporary one I guess. I’ve noticed that bluez got updated during my last distro update but it worked afterwards for a while. I don’t know what happened, other than while listening through my headphones the connection dropped and it wasn’t able to connect again, neither discovering my phone.