You are not logged in.
I bought a Baseus BA07 USB bluetooth dongle, and while it works fine on Windows, it doesn't work on Linux (I'm dual-booting). I'm facing two issues. First, half of the time the dongle isn't powered on, and I have to manually unplug and replug it to power on. Second, I can't connect my headphones unless I remove them from the list of paired devices and re-pair them every time I restart. I'm using Linux Arch Kde 6 Plasma (and I've installed BlueZ and bluez-utils).
[f0x@archlinux ~]$ lsusb | grep -i bluetooth
Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
[f0x@archlinux ~]$ lsmod | grep btusb
btusb 86016 0
btrtl 32768 1 btusb
btintel 65536 1 btusb
btbcm 24576 1 btusb
btmtk 12288 1 btusb
bluetooth 1122304 15 btrtl,btmtk,btintel,btbcm,bnep,btusb
[f0x@archlinux ~]$ dmesg | grep -i bluetooth
dmesg: read kernel buffer failed: Operation not permitted
[f0x@archlinux ~]$ sudo dmesg | grep -i bluetooth
[sudo] password for f0x:
[ 3.183827] Bluetooth: Core ver 2.22
[ 3.183839] NET: Registered PF_BLUETOOTH protocol family
[ 3.183840] Bluetooth: HCI device and connection manager initialized
[ 3.183843] Bluetooth: HCI socket layer initialized
[ 3.183844] Bluetooth: L2CAP socket layer initialized
[ 3.183846] Bluetooth: SCO socket layer initialized
[ 3.225133] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=10 rev=0089
[ 3.225137] Bluetooth: hci0: LMP ver=10 subver=0089; manufacturer=2279
[ 3.225138] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds and force-suspending once...
[ 3.225140] Bluetooth: hci0: CSR: Couldn't suspend the device for our Barrot 8041a02 receive-issue workaround
[ 3.225142] Bluetooth: hci0: HCI Delete Stored Link Key command is advertised, but not supported.
[ 3.225143] Bluetooth: hci0: HCI Read Default Erroneous Data Reporting command is advertised, but not supported.
[ 3.225144] Bluetooth: hci0: HCI Set Event Filter command not supported.
[ 5.914034] Bluetooth: hci0: Opcode 0x1005 failed: -110
[ 5.914039] Bluetooth: hci0: command 0x1005 tx timeout
[ 6.096923] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.096926] Bluetooth: BNEP filters: protocol multicast
[ 6.096929] Bluetooth: BNEP socket layer initialized
[f0x@archlinux ~]$Last edited by LinuxF0x (2024-07-11 22:00:31)
Offline
I'm dual-booting
1. 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
2. https://wiki.archlinux.org/title/Blueto … ot_pairing
Also please use [code][/code] tags. Edit your post in this regard.
Offline
Thanks for the answer, but I already did that. Much lager problem seems to be this:
[f0x@archlinux ~]$ bluetoothctl show
No default controller available
[f0x@archlinux ~]$ bluetoothctl power on
No default controller available
[f0x@archlinux ~]$Every time I restart my PC, it's a gamble whether the Bluetooth will work. The only temporary fix seems to be either rebooting the PC or replugging the USB dongle. In the previous message, the output of 'dmesg | grep -i bluetooth' showed a few errors. Maybe that's the problem?"
Last edited by LinuxF0x (2024-05-27 23:02:13)
Offline
[ 5.914034] Bluetooth: hci0: Opcode 0x1005 failed: -110
[ 5.914039] Bluetooth: hci0: command 0x1005 tx timeoutBut that doesn't explain "why" - please don't grep fro random tokens, post your complete system journal for a boot covering the issue:
sudo journalctl -b | curl -F 'file=@-' 0x0.stfro the current one.
Offline
Sorry for the slow response. I got the complete system journal you asked about.
First reboot with bluetoothctl powered on:
http://0x0.st/XNkG.txt
Second reboot, this time "no default controller available":
http://0x0.st/XNkD.txt
Hopefully, you can make sense of that. This issue is too hard to solve on my own, so thanks for the help.
Offline
There're a fancy keyboard and a gaming mouse on the same bus as the BT dongle while the second bus seems completely un-used.
Try to move the BT dongle away from mouse and keyboard.
Offline
My pc has 8 usb ports: 2 black 2 dark blue and 2 light blue. I have connected mouse, keyboard, bluetooth dongle, pendrive and two usb cables. My pc has two buses:
[f0x@archlinux ~]$ lsusb -t
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 001: Dev 018, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M
|__ Port 001: Dev 018, If 1, Class=Communications, Driver=cdc_acm, 480M
|__ Port 001: Dev 018, If 2, Class=CDC Data, Driver=cdc_acm, 480M
|__ Port 001: Dev 018, If 3, Class=Vendor Specific Class, Driver=usbfs, 480M
|__ Port 003: Dev 019, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 003: Dev 019, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 004: Dev 009, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 004: Dev 009, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 005: Dev 017, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 005: Dev 017, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M
|__ Port 002: Dev 006, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
[f0x@archlinux ~]$ All of these usb devices have white usb color except pendrive which is dark blue. I found out that connecting pendrive to any port except black ones always connects it to Bus 2. For all other devices connecting them to any Bus always connects it to Bus 1, regardless of the color of the usb port. It looks like in order for usb device to be connected to bus 2 it has to be usb 3.x compatible, so I can't connect usb 2 devices to usb 3.x speed bus.
Second thing I forgot to mention: when I first connected this bluetooth dongle to my pc I experienced weird bug, where I couldn't use any peripherals after each boot for about ~20 sec (on windows and on linux!). It was fixed by unpluging and plugin back bluetooth dongle. So it do think that the problem is somehow related to usb ports.
Offline
I have connected mouse, keyboard, bluetooth dongle, pendrive and two usb cables.
What do you mean by "cables" - is there nothing attached to them?
Can you replace the keyboard and mouse w/ $5 office supply, remove the "cables" and the pendrive to test whether that gets you consistent behavior reg. the BT dongle?
Offline
I think we might be stuck. I did remove all usb devices except generic keyboard and the dongle and using shortcuts tired powering on bluetoothctl in bash and it still didn't work. This is probably problem with the hardware (I bet it wasn't even tested on linux). I will leave this post open, maybe you or somebody else will come up with a solution, but I kinda lost hope at this point. All I can say is the problem seem to be related to the process o boot, as connecting dongle to pc after it's booted always works. TL;DR if you want to use bluetooth on linux you probably shouldn't buy Baseus BA07 dongle. Thank you Seth for help.
Offline
All I can say is the problem seem to be related to the process o boot, as connecting dongle to pc after it's booted always works.
Does the kind of boot (cold, warm, linux-linux, windows-linux) matter?
Offline
I kind of abandoned this thread without answering you, sorry about that. As I said, this problem is most likely not specific to just my PC, but to this Bluetooth dongle. I decided to give up on it and buy a new one TP-Link (few users confirmed on Reddit works with Linux) and menaged to get it working.
Last edited by LinuxF0x (2024-07-11 22:00:08)
Offline