USB Bluetooth not working correctly with bullseye

[ljones0]

Hello all!

Just posting here as I'm having an issue with bluetooth not working quite right in debian bullseye. First of all though here is the spec of the system I'm using;

OS = Debian bullseye 64 bit
Motherbard = Asus rog strix b450f gaming (this board is a very recent purchase made only in the last few weeks)
CPU = AMD Ryzen 3 3200G
Graphics = Onboard radeon vega graphics
RAM = 16GB
Desktop=MATE desktop
Kernel=5.7.0-3-amd64
Sound=pulseaudio

Almost everything on this system seems to be working ok. I have working graphics; keyboard and mouse are ok and even normal on-board (wired) audio is ok. I do have the relevent packages installed and have non-free and contrib listed in /etc/apt/sources and have run apt-get update then upgrade . I also have the bluez-firmware package installed.

The system is detecting the bluetooth usb stick (this device is showing as "conwise CW6622", usb id 0e5e:6622 . However the problem occurs when I try to use a pair of bluetooth headphones.

Pairing completes successfully but if I try to use bluetooth headphones I notice in pavucontrol that bluetooth profile is set to "off". If I try to set it to use "HSP/HFP" or "A2DP Sink" then the result is that the system seems to partially hang (my guess is that either whatever is controlling bluetooth or pulseaudio is getting stuck). No sound is produced through the headphones. I'm not sure why a2dp sink isn't avaliable (I have installed pulseaudio-module-bluetooth btw). Here's the output of the profile btw:

Code: Select all

	Profiles:
		headset_head_unit: Headset Head Unit (HSP/HFP) (sinks: 1, sources: 1, priority: 30, available: yes)
		a2dp_sink: High Fidelity Playback (A2DP Sink) (sinks: 1, sources: 0, priority: 40, available: no)
		off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
	Active Profile: off

While all this is happening dmesg is throwing some errors:

Code: Select all

[   52.578056] Bluetooth: hci0: command 0x1405 tx timeout
[   54.594114] Bluetooth: hci0: command 0x1403 tx timeout
[   56.610178] Bluetooth: hci0: command 0x0c2d tx timeout
[   58.626210] Bluetooth: hci0: command 0x1405 tx timeout
[   60.642281] Bluetooth: hci0: command 0x1403 tx timeout
[   62.658337] Bluetooth: hci0: command 0x0c2d tx timeout
[   64.674371] Bluetooth: hci0: command 0x1405 tx timeout
[   66.690420] Bluetooth: hci0: command 0x1403 tx timeout
[   68.706477] Bluetooth: hci0: command 0x0c2d tx timeout
[   70.722529] Bluetooth: hci0: command 0x1405 tx timeout
[   72.738577] Bluetooth: hci0: command 0x1403 tx timeout
[   74.754637] Bluetooth: hci0: command 0x0c2d tx timeout
[   76.770682] Bluetooth: hci0: command 0x1405 tx timeout
[   78.786735] Bluetooth: hci0: command 0x1403 tx timeout
[   80.806782] Bluetooth: hci0: command 0x0c2d tx timeout

Also I am seeing some ACPI errors although I don't know if they are relevent to the problem at all especially as the problem is with bluetooth and the bluetooth adapter is a USB device (there is no onboard bluetooth). I have read elsewhere on other websites btw that acpi errors like this are usually caused by a buggy bios. (I have updated the bios firmware on the motherboard to the latest version).

Code: Select all

[    1.341900] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20200326/psargs-330)
[    1.342007] ACPI Error: Aborting method \_SB.PCI0.GPP0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20200326/psparse-529)
[    1.342110] ACPI Error: Evaluating _BCM failed (20200326/video-357)
..
..
..
[    1.433103] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.POT5._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433256] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.POT6._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433403] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.POT7._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433551] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.POT8._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433697] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.POT9._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433842] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.PO10._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.433982] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.PO11._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.434123] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.PO12._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.434262] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.PO13._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
[    1.434415] ACPI Error: Aborting method \_SB.PCI0.GPP1.PTXH.RHUB.PO14._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200326/psparse-529)
..
..
..
[    1.434675] xhci_hcd 0000:02:00.0: xHCI Host Controller
[    1.434677] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[    1.434678] xhci_hcd 0000:02:00.0: Host supports USB 3.1 Enhanced SuperSpeed
[    1.434726] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.434738] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.07
[    1.434739] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.434740] usb usb2: Product: xHCI Host Controller
[    1.434740] usb usb2: Manufacturer: Linux 5.7.0-3-amd64 xhci-hcd
[    1.434741] usb usb2: SerialNumber: 0000:02:00.0
[    1.434796] hub 2-0:1.0: USB hub found

FYI The problem still occurs no matter if I plug the usb bluetooth stick into a USB 2 or 3 port.

I must admit I'm scratching my head on this one!

ljones

[MikeLieberman]

Just a quick note that I am having the same problem. This particular PC was running Windows 10 until 02Nov2022 and the BT USB worked fine. I installed bullseye (replacing Win) and while bullseye sees the BT USB is can't 'find' anything and nothing else can see it. Oddly enough, I have a different older BT USB running on another unit running bullseye and that one works.