ASUS USB-BT500 bluetooth doesn't work

Tem2 · 08-06-2023, 01:05 PM

I bought the ASUS USB-BT500 bluetooth device because it specifically included linux in its advertisement. My previous device just stopped working one day and I figured that for $10 it wasn't worth the time to try to troubleshoot it. (Do these things wear out? They seem like solid state with no wearable parts.)

I don't have any of the specs for my previous device, but I have attached front and back pictures. I remember that it did not work out of the box, but that I had to follow the procedures found at the following web page, which I saved for future reference (but alas does not work for this new device).

https://www.maketecheasier.com/setup...ooth-in-linux/

I have installed and re-installed my bluetooth apps, so I don't know if I should start from scratch.

Any advice will be greatly appreciated.

Here is some data:

Code:

~:$ :sudo /etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Aug 05 19:23:47 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:24:57 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:26:23 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:26:42 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:27:36 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:29:31 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:31:21 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:33:14 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:33:24 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Aug 05 19:33:54 master-Latitude-E6440 systemd[1]: Condition check resulted i…ed.
Hint: Some lines were ellipsized, use -l to show in full.

Code:

~:$ :lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:64d0 Microdia Integrated Webcam
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0b05:190e ASUSTek Computer, Inc. ASUS USB-BT500
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Emerson · 08-08-2023, 10:25 AM

Your old device stopped working. Yet, your bluetooth service is not started, dead. Perhaps looking at its log would help, why it is not starting. Then your old device may also start working again ...

Tem2 · 08-08-2023, 10:48 AM

How do I check the log?

Emerson · 08-08-2023, 11:01 AM

I don't know systemd stuff ... but I do know how to use a search engine:

https://search.brave.com/search?q=sy...+bluetooth+log

Tem2 · 08-08-2023, 07:07 PM

Thanks for the guidance!

I have determined that my BTUSB-500 dongle works on my Windows laptop, whereas my old dongle does not. I guess that means that the old dongle wore out somehow, but it should be possible to configure the new one to work on my Ubuntu 20.04 Xfce Desktop.

Going over the doc provided in the last reply (https://fedoraproject.org/wiki/How_t...tooth_Problems) the very first step is to make sure the bluetooth hardware is found and enabled with the hciconfig command. When I issue the hciconfig command I get no output. This is probably an important clue as to how to solve this problem. Unfortunately, my research into how to remedy this is coming up empty.

The bluetooth service seems to be okay:

Code:

systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
     Active: active (running) since Tue 2023-08-08 15:15:43 PDT; 1h 33min ago
       Docs: man:bluetoothd(8)
   Main PID: 4983 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9317)
     Memory: 1.6M
     CGroup: /system.slice/bluetooth.service
             └─4983 /usr/lib/bluetooth/bluetoothd -d

Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/profile.c:register_>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/profile.c:create_ex>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/profile.c:register_>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/profile.c:create_ex>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/agent.c:add_default>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/agent.c:agent_ref()>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: src/agent.c:register_ag>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: plugins/hostname.c:prop>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: plugins/hostname.c:prop>
Aug 08 15:15:43 master-Latitude-E6440 bluetoothd[4983]: plugins/hostname.c:prop>
root@master-Latitude-E6440:/usr/lib/systemd/system# hciconfig
root@master-Latitude-E6440:/usr/lib/systemd/system#

And I've attached the log from the following command:

Code:

journalctl -r -u bluetooth > /tmp/bluetoothd.txt