Bluetooth Mouse and Keyboard Keeps Disconnecting

I have a PC with manjaro deepin and I have a plugable USB bluetooth adapter. Every few minutes my mouse and keyboard keep disconnecting. What’s worst is that when it does disconnect, it will say it’s connected again but it’s not. I install blueman and made sure the devices are trusted, it doesn’t help. I disabled tlp from another post and that didn’t help either. I am very frustrated that I can’t reliably use my mouse and keyboard here. I never had this issue when on windows with the same adapter.

windows comparison … deepin … no information.

sorry mate, these kind of posts bug me. And I’m usually very nice about it.

But this time … sorry its you … please search the forums, please read how to provide better information. Those things :wink:

Wow way to turn off someone new away from using Linux jerk. The windows comparison was to let you know it’s not a hardware issue and it’s something with the way Manjaro is out of the box. And way to not tell me what information I should put out to help with my problem. And I guess you didn’t read that I did look at the forums and the only info I found was to turn off tlp which I did with no luck and another post to try blueman and make sure devices are trusted. Not everyone has every knowledge of Linux like you so if your not going to help me maybe you shouldn’t be a jerk about how tired you are of new people wanting to try Linux for the first time :wink:

Turn off if you want. But I am not going to post “please copy paste your system information” for the 87th time today. sorry. There is literally a search button in the corner and a FAQ section and even a tutorial on ‘how to provide good information’ at this point I’ve spent more time typing this so it seems ridiculous. But since its not my best day and you want to dig in to your position … fine.
I will continue to not help until you show one ounce of initiative.

There are other people here too. If you’re tired of helping people out then maybe don’t bother. But thank you for letting me know there’s an faq and maybe I just didn’t look hard enough even though all the posts I find are irrelevant to my situation. And maybe you should get off the internet for the day if you’re gonna lash out at a noob online asking a harmless question

Yes, there are many great helpers on the forum, and @cscs is one of the best. You would be well advised to not cop attitude towards helpers on the forum if you want help, even if you are catching some yourself.

Please post:

inxi -Fxxxz
hwinfo --netcard --wlan --bluetooth | grep -Ei "model\:|driver\:|status\:|cmd\:|file\:|detected\:" | grep -v "Config Status" 

Please post all terminal commands as text with code tags, (not as pics).

Information on how to properly post hardware specs and logs:

Please format any terminal output with three backticks before and after, as shown in this picture:

I’m sorry for that, I’m just new here so I feel very intimidated by the steep learning curve for switching to Linux. Anyways here’s the information and sorry for being a bother to everyone.

System:    Host: chris-PC Kernel: 4.19.20-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Deepin 15.9 
           tk: Qt 5.12.0 info: dde-dock wm: DeepinWM dm: LightDM 1.28.0 Distro: Manjaro Linux 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <filter> Chassis: type: 3 serial: <filter> 
           Mobo: Gigabyte model: X79S-UP5 v: x.x serial: <filter> BIOS: American Megatrends v: F1 date: 07/13/2012 
CPU:       Topology: 6-Core model: Intel Core i7-3960X bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 
           L2 cache: 15.0 MiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 79232 
           Speed: 1200 MHz min/max: 1200/3900 MHz Core speeds (MHz): 1: 1200 2: 1200 3: 1200 4: 1200 5: 1200 6: 1200 
           7: 1200 8: 1200 9: 1199 10: 1200 11: 1200 12: 1200 
Graphics:  Device-1: NVIDIA GK104 [GeForce GTX 680] vendor: eVga.com. driver: nvidia v: 415.27 bus ID: 05:00.0 
           chip ID: 10de:1180 
           Display: x11 server: X.Org 1.20.3 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 680/PCIe/SSE2 v: 4.6.0 NVIDIA 415.27 direct render: Yes 
Audio:     Device-1: Intel C600/X79 series High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:1d20 
           Device-2: NVIDIA GK104 HDMI Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus ID: 05:00.1 
           chip ID: 10de:0e0a 
           Sound Server: ALSA v: k4.19.20-1-MANJARO 
Network:   Device-1: Intel 82579LM Gigabit Network vendor: Gigabyte driver: e1000e v: 3.2.6-k port: f040 
           bus ID: 00:19.0 chip ID: 8086:1502 
           IF: eno1 state: down mac: <filter> 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8168 
           v: 8.045.08-NAPI port: c000 bus ID: 0a:00.0 chip ID: 10ec:8168 
           IF: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.98 TiB used: 812.18 GiB (40.0%) 
           ID-1: /dev/sda vendor: Western Digital model: WD2002FAEX-007BA0 size: 1.82 TiB speed: 6.0 Gb/s 
           serial: <filter> rev: 1D05 scheme: MBR 
           ID-2: /dev/sdb vendor: Corsair model: Force 3 SSD size: 167.68 GiB speed: 3.0 Gb/s serial: <filter> 
           rev: 5.03 scheme: GPT 
Partition: ID-1: / size: 151.55 GiB used: 9.05 GiB (6.0%) fs: ext4 dev: /dev/sdb1 
           ID-2: swap-1 size: 12.70 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb2 
Sensors:   System Temperatures: cpu: 33.0 C mobo: N/A gpu: nvidia temp: 42 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:      Processes: 257 Uptime: 3h 07m Memory: 15.61 GiB used: 1.53 GiB (9.8%) Init: systemd v: 239 Compilers: 
           gcc: 8.2.1 Shell: bash v: 5.0.0 running in: deepin-terminal inxi: 3.0.30 

  Model: "Gigabyte Onboard Ethernet"
  Driver: "r8168"
  Device File: enp10s0
  Link detected: yes
    Driver Status: r8169 is not active
    Driver Activation Cmd: "modprobe r8169"
    Driver Status: r8168 is active
    Driver Activation Cmd: "modprobe r8168"
  Model: "Intel 82579LM Gigabit Network Connection"
  Driver: "e1000e"
  Device File: eno1
  Link detected: no
    Driver Status: e1000e is active
    Driver Activation Cmd: "modprobe e1000e"

Its OK my friend, thats all I wanted :slight_smile:

(and I am heartily sorry my ‘no’ timer landed on you … it really was just that)

this is more tbg’s realm … so they will probably help … but I wonder if we can find something

journalctl | grep bluetooth

Specifically this scenario:
https://wiki.archlinux.org/index.php/Bluetooth#Device_connects,_then_disconnects_after_a_few_moments

I was actually using journalctl -f to record when it disconnects and I got this:

Feb 15 20:25:17 chris-PC kernel: usb 4-1-port1: disabled by hub (EMI?), re-enabling...
Feb 15 20:25:17 chris-PC kernel: usb 4-1.1: reset full-speed USB device number 18 using ehci-pci
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: USB disconnect, device number 18
Feb 15 20:25:18 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-disconnected Disconnected MX Vertical
Feb 15 20:25:18 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-disconnected Disconnected Keyboard K780
Feb 15 20:25:18 chris-PC systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 15 20:25:18 chris-PC systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Feb 15 20:25:18 chris-PC systemd[1]: Stopped target Bluetooth.
Feb 15 20:25:18 chris-PC systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 15 20:25:18 chris-PC audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 15 20:25:18 chris-PC kernel: audit: type=1130 audit(1550291118.191:79): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: new full-speed USB device number 19 using ehci-pci
Feb 15 20:25:18 chris-PC bluetoothd[503]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSource
Feb 15 20:25:18 chris-PC bluetoothd[503]: Endpoint unregistered: sender=:1.122 path=/MediaEndpoint/A2DPSink
Feb 15 20:25:18 chris-PC NetworkManager[498]: <info>  [1550291118.4666] bluez5: NAP: removed interface 5C:F3:70:8C:7E:46
Feb 15 20:25:18 chris-PC daemon/bluetooth[915]: adapter.go:75: AdapterRemoved adapter chris-PC [5C:F3:70:8C:7E:46]
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: New USB device found, idVendor=0a5c, idProduct=21e8, bcdDevice= 1.12
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: Product: BCM20702A0
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: Manufacturer: Broadcom Corp
Feb 15 20:25:18 chris-PC kernel: usb 4-1.1: SerialNumber: 5CF3708C7E46
Feb 15 20:25:18 chris-PC mtp-probe[5723]: checking bus 4, device 19: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 15 20:25:18 chris-PC mtp-probe[5723]: bus: 4, device: 19 was not an MTP device
Feb 15 20:25:18 chris-PC mtp-probe[5730]: checking bus 4, device 19: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1"
Feb 15 20:25:18 chris-PC systemd[1]: Reached target Bluetooth.
Feb 15 20:25:18 chris-PC mtp-probe[5730]: bus: 4, device: 19 was not an MTP device
Feb 15 20:25:18 chris-PC kernel: Bluetooth: hci0: BCM: chip id 63
Feb 15 20:25:18 chris-PC kernel: Bluetooth: hci0: BCM: features 0x07
Feb 15 20:25:18 chris-PC kernel: Bluetooth: hci0: chris-PC
Feb 15 20:25:18 chris-PC kernel: Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
Feb 15 20:25:18 chris-PC kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2
Feb 15 20:25:18 chris-PC kernel: Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found
Feb 15 20:25:18 chris-PC NetworkManager[498]: <info>  [1550291118.6877] bluez5: NAP: added interface 5C:F3:70:8C:7E:46
Feb 15 20:25:18 chris-PC dbus-daemon[496]: [system] Activating service name='com.deepin.api.Device' requested by ':1.79' (uid=1000 pid=915 comm="/usr/lib/deepin-daemon/dde-session-daemon ") (using servicehelper)
Feb 15 20:25:18 chris-PC bluetoothd[503]: Endpoint registered: sender=:1.122 path=/MediaEndpoint/A2DPSource
Feb 15 20:25:18 chris-PC bluetoothd[503]: Endpoint registered: sender=:1.122 path=/MediaEndpoint/A2DPSink
Feb 15 20:25:18 chris-PC dbus-daemon[496]: [system] Successfully activated service 'com.deepin.api.Device'
Feb 15 20:25:18 chris-PC daemon/trayicon[915]: traymanager.go:369: Add tray icon 44040356 name: "blueman-applet"
Feb 15 20:25:18 chris-PC daemon/bluetooth[915]: adapter.go:69: AdapterAdded adapter chris-PC [5C:F3:70:8C:7E:46]
Feb 15 20:25:19 chris-PC daemon/dock[915]: dock_manager_xevent.go:154: WindowError{code=3, seq=7839, major=2, minor=0, bad=25170963}
Feb 15 20:25:19 chris-PC bamfdaemon[1089]: Got an X error: BadWindow (invalid Window parameter)
Feb 15 20:25:19 chris-PC bamfdaemon[1089]: Got an X error: BadWindow (invalid Window parameter)
Feb 15 20:25:19 chris-PC bamfdaemon[1089]: Got an X error: BadWindow (invalid Window parameter)
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: advertising data len corrected
Feb 15 20:25:21 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-connected Connected MX Vertical
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 2587
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 1024
Feb 15 20:25:21 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 143
Feb 15 20:25:23 chris-PC audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 15 20:25:23 chris-PC kernel: audit: type=1131 audit(1550291123.515:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 15 20:25:24 chris-PC kernel: Bluetooth: hci0: advertising data len corrected
Feb 15 20:25:24 chris-PC kernel: Bluetooth: hci0: advertising data len corrected
Feb 15 20:25:24 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-connected Connected Keyboard K780
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 10
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 0
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: ACL packet for unknown connection handle 2816
Feb 15 20:25:25 chris-PC kernel: Bluetooth: hci0: corrupted ACL packet
Feb 15 20:25:31 chris-PC bluetoothd[503]: Error reading PNP_ID value: Unexpected error code
Feb 15 20:25:31 chris-PC bluetoothd[503]: HID Information read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Report Map read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-disconnected Disconnected MX Vertical
Feb 15 20:25:31 chris-PC kernel: usb 4-1.1: USB disconnect, device number 19
Feb 15 20:25:31 chris-PC daemon/bluetooth[915]: utils_notify.go:42: notify notification-bluetooth-disconnected Disconnected Keyboard K780
Feb 15 20:25:31 chris-PC bluetoothd[503]: Error reading PNP_ID value: Unexpected error code
Feb 15 20:25:31 chris-PC bluetoothd[503]: HID Information read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Report Map read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC bluetoothd[503]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Feb 15 20:25:31 chris-PC systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 15 20:25:31 chris-PC systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Feb 15 20:25:31 chris-PC systemd[1]: Stopped target Bluetooth.

I’ve been reading somewhere that autosuspend is the culprit, so I’ll see if turning that off helps, but since I can sometimes go a whole day without this issue happening I wouldn’t know right away.

sudo modprobe -r btusb && sudo modprobe btusb

Ah thats some extra info … I thought immediately on/off/on/off.

Thanks :grin:

Thanks are nice … but do you mean it worked? does it work reliably? In what situations? etc ?
[im still trying to pin down exactly how this occurs … you say sometimes not for days … so sometimes after suspends, but not on boot? … actually curious]

Bad FW according to dmesg. Bloody broadcom.

I meant thanks as in I was looking for how to turn off autosuspend then saw he typed it in for me. Sorry I should’ve been more specific

According to dmesg it is a firmare problem.

You might want to try the firmware at the bottom of this page:

https://forums.linuxmint.com/viewtopic.php?t=260636

More details here:

Be sure wget is installed, then run:

wget https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd

sudo mkdir /lib/firmware/brcm

sudo mv fw-0a5c_21e8.hcd /lib/firmware/brcm/BCM20702A0-0a5c-21e8.hcd

sudo cp /lib/firmware/brcm/BCM20702A0-0a5c-21e8.hcd /lib/firmware/brcm/BCM20702A1-0a5c-21e8.hcd

Then reboot.

There is also firmware in the AUR. It has not been updated since 2017 though. So it’s a bit of a coin toss as to which one to try first. The AUR package should be fully automated, so it is definitely the easier of the 2 firmware’s to install.

https://aur.archlinux.org/packages/bcm20702a1-firmware/

As both these firmware are not very recent, you might want to try an older kernel like 4.14 with these fw.

1 Like

I wanted to wait to see if turning off autosuspend fixed the problem, but it happened again last night. So I installed the firmware from AUR and will report back in a few days if I encounter the issue again.

1 Like

Very glad that fixed it for you. Thanks for updating us on the solution.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.