Ugreen BT 5.0 USB bluetooth not working

English Hardware
1

I am a bit stuck here.
I have no clue if the issue is on the OS/kernel/KDE or the adapter.

I have a UGreen BT 5.0 USB adapter for my desktop. According to the leaflet, it should work under Linux as a plug and play device.

However, in my Leap it’s not even recognized.
First of all dmesg doesn’t show the device. I had to manually load the btusb module and add it to start during boot. (I created a file as

echo "btusb" >> /etc/modules-load.d/btusb.conf

)

After this, the bluetooth service started:


 journalctl -u bluetooth.service  
-- Logs begin at Wed 2022-03-30 23:38:00 EEST, end at Thu 2022-03-31 02:37:59 EEST. -- 
Mar 30 23:38:10 peter.home systemd[1]: Condition check resulted in Bluetooth service being skipped. 
Mar 30 23:49:18 peter.home systemd[1]: Condition check resulted in Bluetooth service being skipped. 
Mar 30 23:50:23 peter.home systemd[1]: Starting Bluetooth service... 
Mar 30 23:50:23 peter.home bluetoothd[4959]: Bluetooth daemon 5.55 
Mar 30 23:50:23 peter.home systemd[1]: Started Bluetooth service. 
Mar 30 23:50:23 peter.home bluetoothd[4959]: Starting SDP server 
Mar 30 23:50:23 peter.home bluetoothd[4959]: Bluetooth management interface 1.14 initialized

But, the KDE BT applet doesn’t find (no adapters found) and rfkill reports nothing:


rfkill list

Is there anything that I could do to discover the device? According to UGreen, it’s not a Windows-specific device, so it should work out-of-the-box. Any help would be appreciated.

2

Update:
I tested the BT adapter on my Lenovo laptop with F34.
In Fedora, the device is recognized and the rfkill command display it properly.

So, this looks like an issue with openSUSE.

3

What does “bluetoothctl show” give you?

4

Nothing :slight_smile:


**#** bluetoothctl show 
No default controller available

Something is missing. Driver, kernel module or firmware.

The only module that is different between the F35 and the Leap 15.3 is the rfcomm:

Leap 13.3


lsmod | grep bt[FONT=monospace]**

bt**usb                  65536  0 
**bt**rtl                  24576  1 **bt**usb 
**bt**bcm                  16384  1 **bt**usb 
**bt**intel                32768  1 **bt**usb 
bluetooth             626688  11 **bt**rtl,**bt**intel,**bt**bcm,bnep,**bt**usb 
usbcore               311296  9 xhci_hcd,ehci_pci,snd_usb_audio,usbhid,snd_usbmidi_lib,uvcvideo,ehci_hcd,**bt**usb,xhci_pci
[/FONT]

Fedora:


lsmod | grep bt
[FONT=monospace]**bt**usb                  65536  0 
**bt**rtl                  28672  1 **bt**usb 
**bt**bcm                  20480  1 **bt**usb 
**bt**intel                45056  1 **bt**usb 
bluetooth             692224  45 **bt**rtl,**bt**intel,**bt**bcm,bnep,**bt**usb,rfcomm
[/FONT]

Also, I see this:
Leap 15.3


lsmod | grep rf
[FONT=monospace]**rf**kill                 28672  6 bluetooth
[/FONT]

Fedora:


lsmod | grep rf
[FONT=monospace]**rf**comm                 90112  16 
bluetooth             692224  45 btrtl,btintel,btbcm,bnep,btusb,**rf**comm 
**rf**kill                 28672  8 bluetooth,thinkpad_acpi,cfg80211

[/FONT]

But even if I enable the rfcomm, the controller is not recognized.
On Fedora, the device is recognized and Teams for example, has it as an option.

Mind you, I use KDE on both environments.