You are not logged in.
Pages: 1
Until today I had no issues with bluetooth. I noticed this morning that I was able to connect my headphones but after a few seconds it would go all static-y and give out. Now, bluetoothctl doesn't seem to be working. I go in, power it on, scan on, and I see
Discovery started
[CHG] Controller 04:7B:CB:29:6C:3B Discovering: yes
but no devices come up. There are plenty of devices around me it should be able to detect. Can anyone point me on the right direction?
Edit: I booted into my windows partition and I connected to bluetooth no problem so fortunately it's not a hardware issue.
Edit 2: I booted back into linux and the scan did work but I immediately had the static issues again.
Edit 3: Scan stopped working again
Last edited by Zaxioms (2023-07-06 03:11:26)
Offline
Make sure you disable the Windows "fast startup" feature, which can interfere will certain resources such as the network card when Windows is supposedly shut down.
Offline
Thanks I'll be sure to try that
Offline
That doesn't seem to have helped ![]()
Last edited by Zaxioms (2023-07-07 20:04:21)
Offline
Running dmesg yields
[ 0.746073] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
[ 6.030637] Bluetooth: Core ver 2.22
[ 6.030682] NET: Registered PF_BLUETOOTH protocol family
[ 6.030684] Bluetooth: HCI device and connection manager initialized
[ 6.030693] Bluetooth: HCI socket layer initialized
[ 6.030698] Bluetooth: L2CAP socket layer initialized
[ 6.030708] Bluetooth: SCO socket layer initialized
[ 6.283287] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
[ 6.283293] Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
[ 6.690774] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.690778] Bluetooth: BNEP filters: protocol multicast
[ 6.690783] Bluetooth: BNEP socket layer initialized
[ 6.786494] Bluetooth: hci0: using NVM file: qca/nvm_usb_00130201_gf.bin
[ 6.927526] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 7.270787] Bluetooth: MGMT ver 1.22
[ 13.379175] Bluetooth: RFCOMM TTY layer initialized
[ 13.379186] Bluetooth: RFCOMM socket layer initialized
[ 13.379188] Bluetooth: RFCOMM ver 1.11
[ 81.664151] Bluetooth: hci0: command 0x0c03 tx timeout
[ 89.773787] Bluetooth: hci0: HCI reset during shutdown failed
[ 90.351192] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00130201.bin
[ 90.351200] Bluetooth: hci0: QCA: patch rome 0x130201 build 0x5073, firmware rome 0x130201 build 0x38e6
[ 90.857929] Bluetooth: hci0: using NVM file: qca/nvm_usb_00130201_gf.bin
[ 91.000507] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 91.343849] Bluetooth: MGMT ver 1.22
[ 130.128746] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 130.473498] Bluetooth: MGMT ver 1.22
so that looks good, but I should mention now bluetooth isn't working on my windows partition, so maybe it is just a hardware issue
Offline
Is there any difference if you start from a cold boot (as opposed to a reboot)?
Offline
Pages: 1