In data domenica 2 luglio 2023 15:08:24 CEST, Jogchum Reitsma ha scritto:
Op 02-07-2023 om 14:13 schreef Carlos E. R.:
On 2023-07-02 14:00, Jogchum Reitsma wrote:
Hi Carlos,
Both
lsmod | grep blue lsmod | grep btusb
give an empty result here, so even more an indication of broken hardware, I would say
No, for that you have to check "lsusb". The above is software.
OK, no bluetooth there too:
lsusb Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 11b0:6368 ATECH FLASH TECHNOLOGY Multi-Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04b8:0130 Seiko Epson Corp. GT-X770 [Perfection V500] Bus 001 Device 008: ID 1377:600e Sennheiser electronic GmbH & Co. KG PXC 550-II Bus 001 Device 007: ID 248a:8366 Maxxter Wireless Optical Mouse ACT-MUSW-002 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I do not know if this helps, but especially with Leap I had a BT adapter that had troubles to wake up after suspend. The only way (if it is one of these dongles) to find out is, to unplug and replug during the session. Then you scan again. Chances are good that it will appear, but from then on, the possible solutions are not known to me. A second advice would be: try it on another sub plug to see if it is not an issue of the usb controller it used/uses. For what I recall the usb dongle having the issue was an ASUS.