Can't get bluetooth to work in Acer Aspire A515-51g laptop w

[dmshakur]

So when I first installed Debian the Bluetooth worked, for the first day. Since then it has worked twice, completely at random, and only for a few hours. I have a dual boot with Windows 10. At first I thought that it had something to do with the fresh install of Debian or the boot loader, since after I reinstalled the Debian boot loader it worked again, but then it stopped and worked randomly one other time when I didn't reinstall the boat loader. I have the same issue in Windows 10 as well, the issue has presisted in Windows 10 long before I ever installed Debian. I followed along with a lot of posts online with no luck.

Code: Select all

(base) dangelo@debianone:~$ bluetoothctl show
No default controller available


Code: Select all

(base) dangelo@debianone:~$ bluetoothctl list


Code: Select all

(base) dangelo@debianone:~$ systemctl | grep bluetooth
  sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d5-1\x2d5:1.0-bluetooth-hci0.device         loaded active plugged   /sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/bluetooth/hci0         
  sys-subsystem-bluetooth-devices-hci0.device                                              loaded active plugged   /sys/subsystem/bluetooth/devices/hci0                                       
  bluetooth.service                                                                        loaded active running   Bluetooth service                                                           
  bluetooth.target                                                                         loaded active active    Bluetooth


Code: Select all

                                                                   
(base) dangelo@debianone:~$ sudo dmesg | grep -i hci0
[    6.552101] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[    6.552104] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[    6.552107] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[   41.636064] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[   41.636067] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[   41.636069] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[12747.193493] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[12747.193500] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[12747.193503] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[22808.763742] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[22808.763746] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[22808.763748] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[35161.697394] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[35161.697399] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[35161.697403] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[35378.776528] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[35378.776531] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[35378.776532] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[45628.060285] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[45628.060289] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[45628.060290] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
[56659.114173] bluetooth hci0: firmware: failed to load qca/rampatch_usb_00000302.bin (-2)
[56659.114179] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
[56659.114182] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)


Code: Select all

(base) dangelo@debianone:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b5f7 Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Code: Select all

(base) dangelo@debianone:~$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2020-07-31 11:33:31 CDT; 1 day 1h ago
     Docs: man:bluetoothd(8)
 Main PID: 821 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 2.4M
   CGroup: /system.slice/bluetooth.service
           └─821 /usr/lib/bluetooth/bluetoothd


[Head_on_a_Stick]

I included a picture of whatever information I thought might be necessary for helping diagnose this issue

Please don't post images of text, post the actual text instead (using code tags).

What is the hardware & driver? I presume it's a PCI device rather that USB so lspci(1) will show the information we need (consult the man page for details).

[dmshakur]

Alright, I entered in the lspci command and this was the output. I'm pretty sure that the Bluetooth is part of the Qualcomm chip.

Code: Select all

(base) dangelo@debianone:~/projects$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)
02:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981


[4D696B65]

https://packages.debian.org/buster/firmware-atheros

[dmshakur]

I put the hw1.0 folder in the directory /etc/lib/firmware, and nothing seems to be happening, the wifi stopped working as well. Also tried to up it in a folder labeled ath10k/QCA9377, this didn't work either but the wifi works.

[4D696B65]

Why not install the deb package like normal

[dmshakur]

I used the command sudo apt-get install firmware-atheros, and the Bluetooth appears to be working until I try to connect. Usually, the Bluetooth will only ever say that it is off when it is either on or off and the menu showing the different devices won't show anything. But now it is showing the menu except every time I try to connect, it seems to connect for what seems like a tenth of a second then it immediately reverts back to its previous state. My headphones don't seem to be affected by my laptop at all.

This is my file tree for the /lib/firmware/ath10pk directory if that helps at all.

Code: Select all

├── QCA4019
│   └── hw1.0
│       ├── board-2.bin
│       └── firmware-5.bin
├── QCA6174
│   ├── hw2.1
│   │   ├── board-2.bin
│   │   ├── board.bin
│   │   └── firmware-5.bin
│   └── hw3.0
│       ├── board-2.bin
│       ├── board.bin
│       ├── firmware-4.bin
│       └── firmware-6.bin
├── QCA9377
│   └── hw1.0
│       ├── board-2.bin
│       ├── board.bin
│       ├── firmware-5.bin
│       ├── firmware-6.bin
│       ├── notice_ath10k_firmware-5.txt
│       └── notice_ath10k_firmware-6.txt
├── QCA9887
│   └── hw1.0
│       ├── board.bin
│       └── firmware-5.bin
├── QCA9888
│   └── hw2.0
│       ├── board-2.bin
│       └── firmware-5.bin
├── QCA988X
│   └── hw2.0
│       ├── board.bin
│       ├── firmware-4.bin
│       └── firmware-5.bin
├── QCA9984
│   └── hw1.0
│       ├── board-2.bin
│       └── firmware-5.bin
└── QCA99X0
    └── hw2.0
        ├── board.bin
        └── firmware-5.bin


Edit:
I'm getting the following in the bluetoothctl, and it keeps populating.

Code: Select all

(base) dangelo@debianone:~$ cd /lib/firmware/
(base) dangelo@debianone:/lib/firmware$ ls
ar3k           BCM2033-FW.bin  qca
ar5523.bin     BCM2033-MD.hex  STLC2500_R4_00_03.ptc
ar7010_1_1.fw  carl9170-1.fw   STLC2500_R4_00_06.ssf
ar7010.fw      cis             STLC2500_R4_02_02_WLAN.ssf
ar9271.fw      dsp56k          STLC2500_R4_02_04.ptc
ath10k         hp              usbduxfast_firmware.bin
ath3k-1.fw     htc_7010.fw     usbdux_firmware.bin
ath6k          htc_9271.fw     usbduxsigma_firmware.bin
ath9k_htc      isci            wil6210.brd
av7110         keyspan_pda     wil6210.fw
(base) dangelo@debianone:/lib/firmware$ cd ath10k/
(base) dangelo@debianone:/lib/firmware/ath10k$ ls
QCA4019  QCA9377  QCA9888  QCA9984
QCA6174  QCA9887  QCA988X  QCA99X0
(base) dangelo@debianone:/lib/firmware/ath10k$
(base) dangelo@debianone:/lib/firmware/ath10k$ ls
QCA4019  QCA9377  QCA9888  QCA9984
QCA6174  QCA9887  QCA988X  QCA99X0
(base) dangelo@debianone:/lib/firmware/ath10k$ cd QCA9377
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377$ ls
hw1.0
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377$ cd hw1.0/
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$ sl
bash: sl: command not found
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$ ls
board-2.bin  firmware-5.bin  notice_ath10k_firmware-5.txt
board.bin    firmware-6.bin  notice_ath10k_firmware-6.txt
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$ ls ../]
ls: cannot access '../]': No such file or directory
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$









(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$ tree
.
├── board-2.bin
├── board.bin
├── firmware-5.bin
├── firmware-6.bin
├── notice_ath10k_firmware-5.txt
└── notice_ath10k_firmware-6.txt

0 directories, 6 files
(base) dangelo@debianone:/lib/firmware/ath10k/QCA9377/hw1.0$ cd ../../
(base) dangelo@debianone:/lib/firmware/ath10k$ tree
.
├── QCA4019
│   └── hw1.0
│       ├── board-2.bin
│       └── firmware-5.bin
├── QCA6174
│   ├── hw2.1
│   │   ├── board-2.bin
│   │   ├── board.bin
│   │   └── firmware-5.bin
│   └── hw3.0
│       ├── board-2.bin
│       ├── board.bin
│       ├── firmware-4.bin
│       └── firmware-6.bin
├── QCA9377
│   └── hw1.0
│       ├── board-2.bin
│       ├── board.bin
│       ├── firmware-5.bin
│       ├── firmware-6.bin
│       ├── notice_ath10k_firmware-5.txt
│       └── notice_ath10k_firmware-6.txt
├── QCA9887
│   └── hw1.0
│       ├── board.bin
│       └── firmware-5.bin
├── QCA9888
│   └── hw2.0
│       ├── board-2.bin
│       └── firmware-5.bin
├── QCA988X
│   └── hw2.0
│       ├── board.bin
│       ├── firmware-4.bin
│       └── firmware-5.bin
├── QCA9984
│   └── hw1.0
│       ├── board-2.bin
│       └── firmware-5.bin
└── QCA99X0
    └── hw2.0
        ├── board.bin
        └── firmware-5.bin

17 directories, 26 files
(base) dangelo@debianone:/lib/firmware/ath10k$
(base) dangelo@debianone:/lib/firmware/ath10k$ bluetoothctl
Agent registered
[CHG] Device 46:D4:83:7E:1C:D0 RSSI: -70
[CHG] Device 46:D4:83:7E:1C:D0 ManufacturerData Key: 0x004c
[CHG] Device 46:D4:83:7E:1C:D0 ManufacturerData Value:
  10 06 0e 1e 1e 46 2f d2                          .....F/.       
[CHG] Device 68:64:4B:57:13:6D RSSI: -72
[CHG] Device 88:C6:26:9F:0D:84 ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:9F:0D:84 ManufacturerData Value:
  00 66 48 00 00 0c a8 51 5b 47 6a ec 88 c6 26 9f  .fH....Q[Gj...&.
  0d 84 32                                         ..2             
[CHG] Device 98:52:3D:65:BD:C6 RSSI: -35
[CHG] Device 69:5A:B3:B5:78:AE RSSI: -79
[CHG] Device 68:64:4B:57:13:6D RSSI: -88
[CHG] Device 62:58:98:0A:10:F7 RSSI: -66
[CHG] Device 47:28:FD:94:C1:AE RSSI: -76
[CHG] Device 62:58:98:0A:10:F7 RSSI: -80
[CHG] Device 47:28:FD:94:C1:AE RSSI: -65
[CHG] Device 98:52:3D:65:BD:C6 RSSI: -49
[CHG] Device 88:C6:26:9F:0D:84 ManufacturerData Key: 0x0003
[CHG] Device 88:C6:26:9F:0D:84 ManufacturerData Value:
  00 66 48 00 00 0c a8 51 5b 47 6a ec 88 c6 26 9f  .fH....Q[Gj...&.
  0d 84 32                                         ..2             
[CHG] Device 47:28:FD:94:C1:AE RSSI: -76
[CHG] Device 68:64:4B:57:13:6D RSSI: -74
[CHG] Device 62:58:98:0A:10:F7 RSSI: -67
[CHG] Device 47:28:FD:94:C1:AE RSSI: -64
[CHG] Device 46:D4:83:7E:1C:D0 RSSI: -79
[bluetooth]# list
Controller 70:C9:4E:A8:85:F8 debianone [default]
[bluetooth]#


[dmshakur]

I attempted to manually pair with my device and I go the following message.

Code: Select all

bluetooth]# connect 98:52:3D:65:BD:C6
Attempting to connect to 98:52:3D:65:BD:C6
Failed to connect: org.bluez.Error.Failed


[dmshakur]

Got it working with the following post on unix.stackexchange.com after installing the drivers from sudo apt-get install atheros-firmware.

https://unix.stackexchange.com/a/402453/418114

Before I could get it to work I had to remove all the Bluetooth devices and install the following packages.

I'm still not all that sure what the issue was though, and I suspect that this may not last and I might lose Bluetooth connectivity again. Fingers crossed it doesn't break