BT łączy i rozłącza mysz

[dedito]

0

[  290.354726] Bluetooth: hci0: Controller not accepting commands anymore: ncmd = 0
[  290.354748] Bluetooth: hci0: Injecting HCI hardware error event
[  290.354798] Bluetooth: hci0: hardware error 0x00

Wygląda na błąd w jądrze.
Na poniższej stronie użytkownik podał parę rozwiązań na obejście problemu
https://peterbabic.dev/blog/bluetooth-mo...fter-boot/

Temporary workarounds
For the previous two months I had to do the following to get the mouse to work on Bluetooth again.

Option 1: Power cycle the mouse
The most obvious fix is to turn the mouse off and on again via the upper switch on it's bottom. The mouse reconnects and becomes responsive. Annoying to do this many times a day.

Option 2: Cycle the source
Another thing that forces the mouse to reconnect is to press the source button described above exactly three times. Since there are three sources, it ends on the exactly the same source. This is exactly as annoying as the previous option.

Option 3: Gnome Bluetooth GUI
Navigating into Bluetooth settings in Gnome, disconnecting and re-connecting the mouse via GUI switch also does the job. But since it is in GUI, it requires many clicks with touchpad. Absolutely the worst option.

Option 4: bluetoothctl CLI
Obviously, It is possible to use command line to resolve the issue. The command bluetoothctl from the package bluez-utils can do the job:

bluetoothctl -- disconnect MAC_ADDRESS
Which outputs the following:

Attempting to disconnect from E7:B9:C9:15F:80
[CHG] Device E7:B9:C9:15F:80 ServicesResolved: no
Successful disconnected
MAC address of the mouse can be found for instance like this:

bluetoothctl -- devices | grep Master | cut -d' ' -f2
The disconnect seems to be enough, the mouse reconnects itself back and becomes responsive automatically. Not sure what to take out of it.

Note: using bluetoothctl in the interactive mode (just running the command) offers completion for commands and MAC addresses too, using it so this way it might be even faster when not inside a script.

oraz znalazł rozwiązanie w postaci instalacji starszego kernela:

I was thankfully able to find a solution to this painful issue in the end. I have used the older LTS kernel from the AUR package https://aur.archlinux.org/packages/linux-lts54/ currently sitting at version 5.4.155 and let it compile overnight.

This kernel does not appear to do any harm to my workflow and gracefully solves the Bluetooth mouse issue. With this kernel on ThinkPad T470, the dmesg is entirely clear without any obvious hiccups, so I might keep it for a while and see how it goes. Hope that helps!

Myślę, że najprostszym wyjściem będzie poczekać na poprawkę i obchodzić problem za pomocą np. bluetoothctl (to można podpiąć pod skrót klawiszowy lub skrypt odpalany z pulpitu) lub zainstalować starszy kernel.