Can't get bt500 (bluetooth dongle) to work

General system Kernel, boot, graphics & hardware
1

I can’t get the BT500 USB dongle to work. :frowning:

The BT500 should work on linux/EOS:

I followed this wiki-article:
https://discovery.endeavouros.com/audio/bluetooth/2021/03/
Did several reboots, just to be sure.

Still I can’t add a bluetooth device, not through settings/gui nor through bluetoothctl.

I’ve added a bluetooth device to other pc’s before, without hassle, so I didn’t expect I would get stuck. I may well be missing something very obvious, but well, I’m stumped… :frowning:

Any help appreciated.

I looked at:
https://wiki.archlinux.org/title/Bluetooth

And there saw some notes that are perhaps relevant?

By default the Bluetooth daemon will only give out bnep0 devices to users that are a member of the lp group. Make sure to add your user to that group if you intend to connect to a Bluetooth tether. You can change the group that is required in the file /usr/share/dbus-1/system.d/bluetooth.conf.

and

Some Bluetooth cards (e.g. Broadcom) conflict with the network adapter. Thus, you need to make sure that your Bluetooth device gets connected before the network service boot.

bluetoothctl says:

No default controller available


lspci
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21)
00:13.0 SATA controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SATA Controller (rev 21)
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 21)
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 21)
00:1b.0 Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 21)
00:1c.1 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #2 (rev 21)
00:1c.2 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #3 (rev 21)
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 21)
00:1f.3 SMBus: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx SMBus Controller (rev 21)
02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 11)

journal:


journalctl -b | grep -i 'bluetooth'
sep 30 16:27:46 willem-afk20c kernel: Bluetooth: Core ver 2.22
sep 30 16:27:46 willem-afk20c kernel: NET: Registered PF_BLUETOOTH protocol family
sep 30 16:27:46 willem-afk20c kernel: Bluetooth: HCI device and connection manager initialized
sep 30 16:27:46 willem-afk20c kernel: Bluetooth: HCI socket layer initialized
sep 30 16:27:46 willem-afk20c kernel: Bluetooth: L2CAP socket layer initialized
sep 30 16:27:46 willem-afk20c kernel: Bluetooth: SCO socket layer initialized
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART driver ver 2.3
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol H4 registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol BCSP registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol LL registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol ATH3K registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol Intel registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol Broadcom registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol QCA registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol AG6XX registered
sep 30 16:27:47 willem-afk20c kernel: Bluetooth: HCI UART protocol Marvell registered
sep 30 16:27:51 willem-afk20c NetworkManager[496]: <info>  [1727706471.2429] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.48.10-1/libnm-device-plugin-bluetooth.so)
sep 30 16:28:19 willem-afk20c systemd[1]: Starting Bluetooth service...
sep 30 16:28:20 willem-afk20c bluetoothd[906]: Bluetooth daemon 5.78
sep 30 16:28:20 willem-afk20c systemd[1]: Started Bluetooth service.
sep 30 16:28:20 willem-afk20c bluetoothd[906]: Starting SDP server
sep 30 16:28:20 willem-afk20c kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
sep 30 16:28:20 willem-afk20c kernel: Bluetooth: BNEP filters: protocol multicast
sep 30 16:28:20 willem-afk20c kernel: Bluetooth: BNEP socket layer initialized
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support bap plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support bass plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support mcp plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support vcp plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support micp plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support ccp plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support csip plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: src/plugin.c:init_plugin() System does not support asha plugin
sep 30 16:28:20 willem-afk20c bluetoothd[906]: Bluetooth management interface 1.22 initialized
sep 30 16:28:30 willem-afk20c kdeconnectd[1030]: 2024-09-30T16:28:30 kdeconnect.core: No local bluetooth adapter found

Systeminfo:

System:
  Kernel: 6.6.52-1-lts arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop System: ASUSTeK product: A_F_K20CE v: 0701
    serial: <superuser required>
  Mobo: ASUSTeK model: A_F_K20CE v: Rev 1.xx serial: <superuser required>
    part-nu: All UEFI: American Megatrends v: 0701 date: 11/25/2015
CPU:
  Info: dual core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont
    rev: 3 cache: L1: 112 KiB L2: 2 MiB
  Speed (MHz): avg: 880 min/max: 480/2160 cores: 1: 880 2: 880
    bogomips: 6402
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
    Integrated Graphics driver: i915 v: kernel arch: Gen-8 ports:
    active: HDMI-A-2 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:22b1
  Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: crocus gpu: i915 display-ID: 0
  Monitor-1: HDMI-A-2 res: 2560x1440 size: N/A
  API: EGL v: 1.5 platforms: device: 0 drv: crocus device: 1 drv: swrast
    gbm: drv: crocus surfaceless: drv: crocus wayland: drv: crocus x11:
    drv: crocus
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 400 (BSW)
    device-ID: 8086:22b1 display-ID: :1.0
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series
    High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
    bus-ID: 00:1b.0 chip-ID: 8086:2284
  API: ALSA v: k6.6.52-1-lts status: kernel-api
  Server-1: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: e000 bus-ID: 03:00.0 chip-ID: 10ec:8168
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-1:8 chip-ID: 148f:7601
  IF: wlan0 state: down mac: <filter>
Drives:
  Local Storage: total: 223.57 GiB used: 18.03 GiB (8.1%)
  ID-1: /dev/sda vendor: Crucial model: CT240BX200SSD1 size: 223.57 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 218.01 GiB used: 18.03 GiB (8.3%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 1022 MiB used: 288 KiB (0.0%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 1.5 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 4 GiB available: 3.74 GiB used: 2.46 GiB (65.8%)
  Processes: 174 Power: uptime: 12m wakeups: 0 Init: systemd v: 256
    default: graphical
  Packages: pm: pacman pkgs: 1041 Compilers: gcc: 14.2.1 Shell: Bash
    v: 5.2.37 running-in: yakuake inxi: 3.3.36
2

If it’s a usb dongle did you check lsusb

1 Like
3

Had forgotten to run lsusb:

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 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 003: ID 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 004: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
Bus 003 Device 005: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 003 Device 008: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 1d5c:5002 Fresco Logic USB3.0 Hub
Bus 004 Device 003: ID 1d5c:5002 Fresco Logic USB3.0 Hub

I don’t think the usb-dongle is showing up in this list…

4

I moved the usb dongle to a different port, the one on the back of the pc.
To be able to put the bt-dongle in there I had to remove the wifi-dongle that was in there.
Now it does show up, and now I can in fact add a device!

So, perhaps this arch note is pertinent:

Some Bluetooth cards (e.g. Broadcom) conflict with the network adapter. Thus, you need to make sure that your Bluetooth device gets connected before the network service boot.

Thanks @ricklinux for pointing out I forgot to look at lsusb.

Case solved!

5

I think it is on the WiFi adapter here? Is that correct?

6

No, that one is only wifi. Bluetooth is a separate dongle.
I got it working, though, see above.

:+1:t4:

7

You said it shows now so i was just wondering which one it is?

Edit: So it is a separate BT dongle. Just wondered how it showed up in the output after.

8

Still this doesn’t mean that it was a conflict with your wifi usb, although it is possible of course

sometimes moving the adapter (this Bluetooth device) to a different usb port is the solution, especially if that port is a usb 2.0 port (there seems to be issues with Bluetooth and usb 3.0 ports)

And sometimes it is possible to upgrade the firmware to make it working.
Either way this issue is a hardware issue, kernel does not find the device.

9

This is true.

10

I’ll put the output here later tonight.

11

It’s the fourth item in the list:


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 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500**
Bus 003 Device 003: ID 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 004: ID 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 005: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
Bus 003 Device 006: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 1d5c:5002 Fresco Logic USB3.0 Hub
Bus 004 Device 003: ID 1d5c:5002 Fresco Logic USB3.0 Hub
1 Like
12

Just for completeness’ sake I put the Wifi-dongle back in.
So now both dongles are present - bluetooth is still working.
And they are both in lsusb:


Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
**Bus 001 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter**
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 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500**
Bus 003 Device 003: ID 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 004: ID 1d5c:5012 Fresco Logic USB2.0 Hub
Bus 003 Device 005: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse
Bus 003 Device 006: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 1d5c:5002 Fresco Logic USB3.0 Hub
Bus 004 Device 003: ID 1d5c:5002 Fresco Logic USB3.0 Hub
1 Like
13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.