#[SOLVED] Getting a usb bluetooth adapter to work

242 messages · Page 1 of 1 (latest)

spice island
#

Have a ax210 internal card in the the pc I'm using which is intel chip that provides both bluetooth and wifi, but the bluetooth range isn't good. So I bought a bluetooth usb adapter (realtek) and plugged it in and then ran rfkill list:

[dan@archlinux ~]$ rfkill list
1: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
8: hci3: Bluetooth
Soft blocked: no

So 1 is the internal bluetooth from the AX210 card, and 8 is the usb adapter. I ran rkill block 1 but all that does is completely turn off my bluetooth and then I have to run systemctl start bluetooth to get it back, at which point 1 is unblocked again.

Is there any way to get this to work? Any advice much appreciated. I think the realtek usb adapter has to work since it shows up in the list but I can't get it to be used

crimson trellis
#

What chipset does the usb adapter have

spice island
#

Realtek

#

its this one

quaint plinth
#

What is the chipset of that usb adapter

#

@spice island

spice island
#

Realtek

quaint plinth
#

No like do you know what the name of the chip inside of the realtek card is

#

I know the brand is realtek

spice island
#

@quaint plinth

#

according to advertisement page

#

is there a way to find out

quaint plinth
#

Yeah just look up the product name

#

There's also probably a command you can run to figure it out

spice island
#

google won't help .. tried.. it's a generic chinese brand

#

think most of these chips should be supported in linux kernel

quaint plinth
#

Realtek is Taiwanese but yeah most should be supported

spice island
#

yea, it does show up in rfkill list

spice island
#

lsusb tells me

#

Bus 001 Device 016: ID 0bda:a728 Realtek Semiconductor Corp. Bluetooth 5.4 Radio

#

[dan@archlinux ~]$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 25a7:fa67 Areson Technology Corp 2.4G Receiver
Bus 001 Device 005: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 006: ID 0573:1573 Zoran Co. Personal Media Division (Nogatech) USB Audio and HID
Bus 001 Device 015: ID 145f:02c9 Trust Trust Keyboard
Bus 001 Device 016: ID 0bda:a728 Realtek Semiconductor Corp. Bluetooth 5.4 Radio
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[dan@archlinux ~]$

#

can see also the AX210 bluetooth there

#

think the issue is less whether arch has driver for it, and more how to get it to be used instead of the AX210

spice island
#

i've managed to find the MAC address of the usb adapter

#

8C:68:8B:A0:80:4C

#

not sure what to do with it tho

#

I ran bluetoothctl list to get that

brittle hemlock
#

@spice island

sudo nano /etc/udev/rules.d/99-disable-ax210-bluetooth.rules

SUBSYSTEM=="usb", ATTR{idVendor}=="8087", ATTR{idProduct}=="0032", ATTR{authorized}="0"
#

Then

sudo udevadm control --reload-rules
sudo udevadm trigger
#

Then reboot

#

After reboot bluetoothctl list should just show the realtek one

#

If you want to revert later

sudo rm /etc/udev/rules.d/99-disable-ax210-bluetooth.rules
sudo udevadm control --reload-rules
sudo udevadm trigger
sudo reboot
forest craterBOT
#

cviper13 received a thank you cookie!

spice island
#

i just rebooted

#

so now I just see

#

[dan@archlinux ~]$ bluetoothctl list
Controller 8C:68:8B:A0:80:4C archlinux [default]
[dan@archlinux ~]$

#

but have no bluetooth working, blueman isn't detecting my headphones

#

before I had two in the list so seems we sucess disable the ax210 bluetooth

#

could I be missing something

#

like firmware

brittle hemlock
#

even if it shows up, it might be soft-blocked or not powered on

rfkill list bluetooth

spice island
#

[dan@archlinux ~]$ rfkill list bluetooth
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
[dan@archlinux ~]$

brittle hemlock
#

Yep

#

rfkill unblock bluetooth

#

And reboot once again

spice island
#

ok rebooting

#

so after rebooting

#

[dan@archlinux ~]$ rfkill list bluetooth
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

#

but then I have to run systemctl start bluetooth like I always run

#

and then it changes to

#

[dan@archlinux ~]$ rfkill list bluetooth
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
[dan@archlinux ~]$

#

no bluetooth working

#

maybe its not powered on?

#

there's no light on the bluetooth usb stick anymore

#

used to be a small blue led on it

brittle hemlock
spice island
#

how power it on

brittle hemlock
#

Unblock it again but dont reboot

spice island
#

unbocked, still seems powered off

brittle hemlock
#

Hmm

#

journalctl -u bluetooth.service -f

#

Lets see if the bluetooth service is the culprit

#

See if there are any errors or actions that might explain why it’s getting soft-blocked after starting the service

spice island
#

if we get this working there's door dash pizza if u want it

#

on me

brittle hemlock
#

Can you send the logs here

spice island
#

[dan@archlinux ~]$ journalctl -u bluetooth.service -f

Send a message in "Getting a usb bluetooth adapter to work"
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/faststream
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/faststream_duplex
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink/opus_05
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/opus_05
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Apr 20 21:57:31 archlinux bluetoothd[2157]: Endpoint registered: sender=:1.27 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Apr 20 21:57:32 archlinux bluetoothd[2157]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
^C
bash: Send: command not found
[dan@archlinux ~]$

brittle hemlock
#

Ill look thru the frikin source meanwhile try this bluetoothctl scan on

spice island
#

btw I just tried right click on blueman and select bluetooth on and it gave this msg

#

Apr 20 22:03:41 archlinux bluetoothd[2157]: Failed to set mode: Authentication Failed (0x05)

#

[dan@archlinux ~]$ bluetoothctl scan
Missing on/off/bredr/le argument
[dan@archlinux ~]$

brittle hemlock
#

rm -r ~/.cache/blueman rm -r ~/.config/blueman

spice island
#

[dan@archlinux ~]$ rm -r ~/.cache/blueman
rm -r ~/.config/blueman
rm: cannot remove '/home/dan/.cache/blueman': No such file or directory
rm: cannot remove '/home/dan/.config/blueman': No such file or directory
[dan@archlinux ~]$

brittle hemlock
brittle hemlock
#

Where did blueman saved

spice island
#

[dan@archlinux ~]$ whereis blueman
blueman: /usr/lib/blueman /usr/share/blueman
[dan@archlinux ~]$

brittle hemlock
#

I mean its already paired

#

When you clicked on that at blueman it tried to connect to an already paired thing probably

#

But got rejected since your mac is now diffirent

spice island
#

im bit lost now

#

one thing is that there's no blue light on the usb adapter anymore

#

feel like its not powered on

#

[dan@archlinux ~]$ bluetoothctl list
Controller 8C:68:8B:A0:80:4C archlinux [default]
[dan@archlinux ~]$ bluetoothctl power on
[CHG] Controller 8C:68:8B:A0:80:4C PowerState: off-enabling
Failed to set power on: org.bluez.Error.Failed
[dan@archlinux ~]$

brittle hemlock
#

dmesg | grep -i bluetooth

#

God i love bluez error messages

spice island
brittle hemlock
#

Just failed

brittle hemlock
spice island
#

its too long to paste

#

can do it in 2 parts

#

[dan@archlinux ~]$ sudo dmesg | grep -i bluetooth

Send a message in "Getting a usb bluetooth adapter to work"
[sudo] password for dan:
[ 1.051507] usb 1-2: Product: Bluetooth 5.4 Radio
[ 3.151591] Bluetooth: Core ver 2.22
[ 3.151624] NET: Registered PF_BLUETOOTH protocol family
[ 3.151625] Bluetooth: HCI device and connection manager initialized
[ 3.151630] Bluetooth: HCI socket layer initialized
[ 3.151632] Bluetooth: L2CAP socket layer initialized
[ 3.151635] Bluetooth: SCO socket layer initialized
[ 3.228967] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 3.229977] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ 3.229985] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 3.232308] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 3.232520] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[ 3.387958] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[ 46.871445] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 46.871450] Bluetooth: BNEP filters: protocol multicast
[ 46.871455] Bluetooth: BNEP socket layer initialized
[ 46.874840] Bluetooth: MGMT ver 1.23

brittle hemlock
#

Pastebin maybe?

#

Actually sure

spice island
#

[ 46.924254] Bluetooth: RFCOMM TTY layer initialized
[ 46.924267] Bluetooth: RFCOMM socket layer initialized
[ 46.924272] Bluetooth: RFCOMM ver 1.11
[ 49.057272] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 145.189191] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 166.186190] Bluetooth: hci0: Opcode 0x0c03 failed: -110
[ 211.301299] usb 1-2: Product: Bluetooth 5.4 Radio
[ 211.308020] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ 211.309004] Bluetooth: hci1: RTL: rom_version status=0 version=1
[ 211.309014] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ 211.309556] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin
[ 211.309668] Bluetooth: hci1: RTL: cfg_sz 6, total sz 30210
[ 211.460035] Bluetooth: hci1: RTL: fw version 0xdfc6d922
[ 211.527408] Bluetooth: MGMT ver 1.23
[ 581.788693] Bluetooth: hci1: Opcode 0x0c03 failed: -110
[ 797.562372] Bluetooth: hci1: Opcode 0x0c03 failed: -110
[ 817.591334] Bluetooth: hci1: Opcode 0x0c03 failed: -110
[ 943.005701] Bluetooth: hci1: Opcode 0x0c03 failed: -110
bash: Send: command not found
[dan@archlinux ~]$

brittle hemlock
#

The bluettoth has rtl8761bu chipset bte

spice island
#

yea it's realtek, someone posted me this link but its all alien to me

brittle hemlock
#

I just wonder

#

sudo pacman -S linux-firmware

brittle hemlock
spice island
#

[dan@archlinux ~]$ sudo pacman -S linux-firmware
warning: linux-firmware-20250408.c1a774f3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-firmware-20250408.c1a774f3-1

Total Installed Size: 277.84 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n]

brittle hemlock
#

Hmm

spice island
#

it's odd how since we did the first step it no longer has blue light

brittle hemlock
#

It might not have drivers in linux firmware pckage

#

Are you okay with using 3rd party drivers(on github)

spice island
#

anything that'd make it work would be over the moon

#

there's this link

brittle hemlock
#

Wait wait

#

I found

spice island
#

k

brittle hemlock
#
cd /lib/firmware/rtl_bt
sudo ln -s rtl8761b_config.bin rtl8761bu_config.bin
sudo ln -s rtl8761b_fw.bin rtl8761bu_fw.bin
#

Just use tge 8761b drivers for the 8761bu

spice island
#

ok I ran those commands

brittle hemlock
#

Led not turning on means its a power issue

brittle hemlock
#

And try again

spice island
#

run those commands again?

#

just took it out n back in

#

still no light

brittle hemlock
brittle hemlock
brittle hemlock
spice island
#

no errors

#

[dan@archlinux rtl_bt]$ systemctl start bluetooth
[dan@archlinux rtl_bt]$ cd /lib/firmware/rtl_bt
sudo ln -s rtl8761b_config.bin rtl8761bu_config.bin
sudo ln -s rtl8761b_fw.bin rtl8761bu_fw.bin
ln: failed to create symbolic link 'rtl8761bu_config.bin': File exists
ln: failed to create symbolic link 'rtl8761bu_fw.bin': File exists
[dan@archlinux rtl_bt]$

brittle hemlock
#

Yup theres errors

spice island
#

think it's because ran it 2nd time

#

first time seemed no error

brittle hemlock
#
sudo mv rtl8761bu_config.bin rtl8761bu_config.bin.bkp
sudo ln -s rtl8761b_config.bin rtl8761bu_config.bin
sudo mv rtl8761bu_fw.bin rtl8761bu_fw.bin.bkp
sudo ln -s rtl8761b_fw.bin rtl8761bu_fw.bin
#

Try this

spice island
#

done

#

no errors

brittle hemlock
#

Plug in and out

#

Then try powering it on

spice island
#

no luck

#

to power it on im doing

#

systemctl start bluetooth

#

and right clickling blueman gui thing and selecting power on

brittle hemlock
#

bluetoothctl power on

#

Try this way to see if any errors

spice island
#

[dan@archlinux rtl_bt]$ bluetoothctl power on
[CHG] Controller 8C:68:8B:A0:80:4C PowerState: off-enabling
Failed to set power on: org.bluez.Error.Failed
[dan@archlinux rtl_bt]$

brittle hemlock
#

Could you try rebooting by any chance

spice island
#

sure

#

rebooted

#

doing bluetoothctl power on again

#

its stuck like that

brittle hemlock
#

Service started?

spice island
#

^C[dan@archlinux ~]$ systemctl start bluetooth
[dan@archlinux ~]$ bluetoothctl power on
Failed to set power on: org.bluez.Error.Busy
[dan@archlinux ~]$

#

wait i just tried right click on blueman and power on

#

then tried this

#

[dan@archlinux ~]$ bluetoothctl power on
[CHG] Controller 8C:68:8B:A0:80:4C PowerState: off-enabling
hci0 class of device changed: 0x6c010c
[CHG] Controller 8C:68:8B:A0:80:4C Class: 0x006c010c (7078156)
hci0 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn
Changing power on succeeded
[CHG] Controller 8C:68:8B:A0:80:4C PowerState: on
[CHG] Controller 8C:68:8B:A0:80:4C Powered: yes
[dan@archlinux ~]$

brittle hemlock
#

WORKE

#

YES

#

Hell yeah brotha

spice island
#

omfg bro

brittle hemlock
#

Connect to something!!

spice island
#

u did it!!!

brittle hemlock
#

Its a bit diy solution but

spice island
#

can I ask for a ELI5 what the issue was incase i ever reinstall arch

brittle hemlock
#

What we did is

brittle hemlock
#

So the chipset this thing has is rtl8761bu

#

This chipset has a firmware/driver, but its broken.

brittle hemlock
brittle hemlock
spice island
#

im gonna be saving this entire convo

#

btw just managed for first time to walk around entire home with no stuttering or cutting out of headphones

#

:))

spice island
#

made my day, owe u a pizza any time

brittle hemlock
#

Now you can enjoy your musics or podcasts nonstop

spice island
#

yep

#

im asbergers so always need be listening to like chill bladerunner type things or white noise

brittle hemlock
spice island
#

first thing we did was disable the AX210 bluetooth right

brittle hemlock
#

Yes the udev rule

brittle hemlock
brittle hemlock
spice island
#

ah so basically the kernel had similar-ish drivers that we used instead?

brittle hemlock
#

And these revert the dongle fix(incase)

sudo rm rtl8761bu_config.bin
sudo mv rtl8761bu_config.bin.bkp rtl8761bu_config.bin
sudo rm rtl8761bu_fw.bin
sudo mv rtl8761bu_fw.bin.bkp rtl8761bu_fw.bin
spice island
#

ur a genius

#

for real DM me any time for that pizza

#

im in the UK, assuming u are USA

brittle hemlock
#

Thats why i cant sadly accept

#

I'm from turkey

spice island
#

ahhh

brittle hemlock
#

But thanks for offering still

spice island
#

jealous u got the good kebabs there

#

thanks for the help, learnt some things too

brittle hemlock
#

Btw rtl8761bu (the chipset on your dongle) and rtl8761b is no diffirent

#

The u there just means USB

#

So you shouldnt have any feature loss

brittle hemlock
spice island
#

is it basically a bug in the kernel?

#

guess its not that often people buy this specific usb adapter

#

it says windows support only on amazon

brittle hemlock
brittle hemlock
spice island
#

everytime I reboot, do I do systemctl start bluetooth and then bluetoothctl power on?

brittle hemlock
#

By

#

systemctl enable bluetooth

#

This will make it autostart

spice island
#

I had a feeling that it'd work on linux just because from my very limited knowlege, most chips have firmware in kernel

brittle hemlock
#

Reboot to see if it comes powered on after a reboot

spice island
#

[dan@archlinux ~]$ systemctl enable bluetooth
Created symlink '/etc/systemd/system/dbus-org.bluez.service' → '/usr/lib/systemd/system/bluetooth.service'.
Created symlink '/etc/systemd/system/bluetooth.target.wants/bluetooth.service' → '/usr/lib/systemd/system/bluetooth.service'.
[dan@archlinux ~]$

brittle hemlock
#

If not i can craft a udev rule to automate thst

spice island
#

its a little shame that the AX210 wasn't good enough, I don't think it's the chip's fault, just the internal antenna is too weak

#

it's a tiny mini-pc

brittle hemlock
#

I work with radios and stuff

spice island
#

yeah its like just a string inside

brittle hemlock
#

And generally the antenna is the bottleneck of radios

spice island
#

^ vs that that you just got working

brittle hemlock
#

For example you can reach USA from UK with a 5W radio and a good gain antenna but you cant with a 100W radio and bad gain antenna

spice island
spice island
brittle hemlock
spice island
#

u ever listen to air traffic control or police ?

brittle hemlock
#

If you want to check out prob you might have an amateur radio club in your area

brittle hemlock
#

Actually lets move the convo to dms

spice island
#

k

brittle hemlock
#

For sake of this channel's future visitors

#

@spice island
Dont forget to save the commands

#

Also

#

... solved

modern summitBOT
#

#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

  • You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
  • You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you

brittle hemlock
#

:)