Hardware - Support > Other

Bluetooth Disconnects, then Fails to Reconnect

(1/2) > >>

Hey, everyone.

I'm very new to Linux in general and forums as well, so if I'm going to make a lot of mistakes here, haha.
Anyway, I'm going to attempt to be more specific about my issue.

Basically, upon a fresh installation of Linux Lite 5.8, and kernel version 5.4.0-109-generic.

My goal here was to connect my bluetooth keyboard and bluetooth mouse to my linux system and generally stay connected for continuous use, but what ends up happening is that upon a fresh install of this linux version, I can identify, connect to, select as a trusted device, and pair my mouse just fine. Then the keyboard appears and lets me connect, trust, but not pair. This usually manages to work for a while, but when I restart the pc, the mouse remains connected and functional, but I have to reconnect the keyboard. This also remains working for a while, but my bluetooth manager crashes and I lose all control over my bluetooth devices. When this happens, I either a) cannot even open the bluetooth manager; it acts as if it will open, but then stays frozen, which linux then offers to force close it, or b) I can open the manager, see my devices to connect to, but I cannot pair nor connect to them. A pairing failed message will appear when trying to pair and a Connection Failed:  Connection timed out appears when trying to connect. However, sometimes the connection message changes and says a different reasoning for the failure to connect.

This seems to be my bluetooth device:

Bus 003 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0

When I use the command (below) in the terminal, this is what pops up. I see an error and then something about unknown packets and corruption handles.

dmesg | grep -i blue

[   13.770309] Bluetooth: Core ver 2.22
[   13.770340] Bluetooth: HCI device and connection manager initialized
[   13.770344] Bluetooth: HCI socket layer initialized
[   13.770346] Bluetooth: L2CAP socket layer initialized
[   13.770349] Bluetooth: SCO socket layer initialized
[   14.815666] Bluetooth: hci0: BCM: chip id 63
[   14.817665] Bluetooth: hci0: BCM: features 0x07
[   14.834666] Bluetooth: hci0: linuxman-IdeaCentre
[   14.836670] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[   14.962632] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
[   14.962638] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
[   29.671268] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.671271] Bluetooth: BNEP filters: protocol multicast
[   29.671277] Bluetooth: BNEP socket layer initialized
[   57.581729] Bluetooth: RFCOMM TTY layer initialized
[   57.581736] Bluetooth: RFCOMM socket layer initialized
[   57.581747] Bluetooth: RFCOMM ver 1.11
[   96.820211] Bluetooth: hci0: ACL packet for unknown connection handle 16
[   96.820225] Bluetooth: hci0: ACL packet for unknown connection handle 16
[  101.098335] Bluetooth: hci0: corrupted ACL packet
[  126.473362] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[  126.473376] Bluetooth: HIDP socket layer initialized
[  126.930750] Bluetooth: hci0: corrupted ACL packet
[  128.305749] Bluetooth: hci0: corrupted ACL packet
[  131.817802] Bluetooth: hci0: ACL packet for unknown connection handle 12
[  131.817811] Bluetooth: hci0: ACL packet for unknown connection handle 12
[ 2164.534710] Bluetooth: hci0: ACL packet for unknown connection handle 2049

The only other things I have downloaded are: visualboyadvance and znes emulators.

If anyone has any suggestions I would greatly appreciate your time. I am eager to share more information and the like if necessary.

I guess the driver is not installed. I found this post in the Linux Mint forum to add the driver for your BCM20702A0
The post is three years old, but the wget link still works.


They used the following commands to install the driver (I don't think you need the rfkill command):

sudo wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd -O /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd
sudo rfkill unblock bluetooth

Thanks for the response and advice.

So, after downloading that driver, resetting my system, and troubleshooting further to check if this works, now its doing something else.

My mouse connects, pairs, and works well now. Even when I restart my pc, the mouse reconnects itself and is good to go. However, my keyboard acts different.

I can connect to it only; if I try to "pair", the pairing will always fail. Despite this, after connecting, the keyboard is functional until I restart my pc. Unlike the mouse I'm using, this keyboard will not reconnect itself. I end up having to remove it as a device in my bluetooth manager, put it in pairing mode, research for it, then I have to "connect" to it, because pairing will always fail. This process seems to repeat after every restart of my pc. Looking back, I think the bluetooth is overall more stable in general now. So, I guess its functional, but it would be awesome if the keyboard could maintain its connection.

If you have any further suggestions, I would be eager to listen. Thanks for your help!

Doesn't sound good, but simple things first. Is the adapter set to 'always visible'?
Does the command 'dmesg | grep -i blue' show the same result as before?
Does the command 'sudo systemctl status bluetooth' show any errors?
Bluetooth can really be a a pain in the ....   >:(

dmesg | grep -i blue

[79901.864404] input: bluetooth mouse4.0 Mouse as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/bluetooth/hci0/hci0:13/0005:0A5C:0001.0009/input/input28
[79901.866919] hid-generic 0005:0A5C:0001.0009: input,hidraw2: BLUETOOTH HID v1.29 Mouse [bluetooth mouse4.0] on 5c:f3:70:a8:03:f6
[79938.987168] input: Keyboard K380 Keyboard as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/bluetooth/hci0/hci0:11/0005:046D:B342.000A/input/input30
[79938.987536] input: Keyboard K380 Consumer Control as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/bluetooth/hci0/hci0:11/0005:046D:B342.000A/input/input31
[79938.987635] input: Keyboard K380 System Control as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/bluetooth/hci0/hci0:11/0005:046D:B342.000A/input/input32
[79938.987741] hid-generic 0005:046D:B342.000A: input,hidraw3: BLUETOOTH HID v42.01 Keyboard [Keyboard K380] on 5c:f3:70:a8:03:f6

sudo systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre>
     Active: active (running) since Sat 2022-05-14 13:37:54 PDT; 22h ago
       Docs: man:bluetoothd(8)
   Main PID: 815 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4224)
     Memory: 2.4M
     CGroup: /system.slice/bluetooth.service
             └─815 /usr/lib/bluetooth/bluetoothd

May 14 13:37:50 linuxman-IdeaCentre systemd[1]: Starting Bluetooth service...
May 14 13:37:51 linuxman-IdeaCentre bluetoothd[815]: Bluetooth daemon 5.53
May 14 13:37:54 linuxman-IdeaCentre systemd[1]: Started Bluetooth service.
May 14 13:37:54 linuxman-IdeaCentre bluetoothd[815]: Starting SDP server
May 14 13:37:55 linuxman-IdeaCentre bluetoothd[815]: Bluetooth management inter>
May 14 13:38:31 linuxman-IdeaCentre bluetoothd[815]: Endpoint registered: sende>
May 14 13:38:31 linuxman-IdeaCentre bluetoothd[815]: Endpoint registered: sende>
May 14 13:42:06 linuxman-IdeaCentre bluetoothd[815]: Can't get HIDP connection >
May 15 11:49:42 linuxman-IdeaCentre bluetoothd[815]: Can't get HIDP connection >

It is set to "always visible", but it does appear those "Can't get HIDP connection" errors could be something, but I'm so unsure haha.

But yeah! Bluetooth seems to be a huge pain here lol. I had issues with Wifi adapters at first until I looked into one that could be plug-and-play. This bluetooth adapter was supposed to be the same deal but now I'm like  :024:


[0] Message Index

[#] Next page

Go to full version