- #Logitech mx master 2s disconnecting Patch#
- #Logitech mx master 2s disconnecting Bluetooth#
- #Logitech mx master 2s disconnecting windows#
The more the computer stays on, the more likely it is to happen.Īlso, it seems to happen a lot while moving the mouse during videos.Ĭontacting Logitech was futile. I've noticed it happens much less after the computer gets restarted.
#Logitech mx master 2s disconnecting Bluetooth#
Entering Windows' Bluetooth & other devices settings, clicking Remove device on the mouse, then re-pair it.Entering Windows' Bluetooth & other devices settings, turning the general Bluetooth setting to Off, then On again.Entering Windows' Bluetooth & other devices settings, then closing it without doing anything!.Sometimes only some of them work, but anyway here they are by order of comfort and speed (if any of them works, there's no need to move the next trick): I found some methods to wake it up again. But sometimes even in the middle of usage!
#Logitech mx master 2s disconnecting windows#
Turning the mouse off stopped the messages, so pretty sure it was the culprit of the repeated messages.Using the latest Windows 10, this mouse keeps disconnecting, usually upon exiting sleep mode. Jun 14 10:01:37 kernel: usb usb1-port2: unable to enumerate USB device Jun 14 10:01:37 kernel: usb 1-2: device not accepting address 124, error -71 Jun 14 10:01:36 kernel: usb 1-2: new full-speed USB device number 124 using xhci_hcd Jun 14 10:01:36 kernel: usb 1-2: device not accepting address 123, error -71 Jun 14 10:01:36 kernel: usb 1-2: Device not responding to setup address. Jun 14 10:01:36 kernel: usb 1-2: new full-speed USB device number 123 using xhci_hcd Jun 14 10:01:35 kernel: usb usb1-port2: attempt power cycle Jun 14 10:01:35 kernel: usb 1-2: new full-speed USB device number 122 using xhci_hcd Jun 14 10:01:34 kernel: usb 1-2: new full-speed USB device number 121 using xhci_hcd Jun 14 10:01:19 kernel: usb usb1-port2: unable to enumerate USB device Jun 14 10:01:19 kernel: usb 1-2: device not accepting address 120, error -71 Jun 14 10:01:19 kernel: usb 1-2: new full-speed USB device number 120 using xhci_hcd Jun 14 10:01:19 kernel: usb 1-2: device not accepting address 119, error -71 Jun 14 10:01:19 kernel: usb 1-2: Device not responding to setup address.
Jun 14 10:01:18 kernel: usb 1-2: Device not responding to setup address. Jun 14 10:01:18 kernel: usb 1-2: new full-speed USB device number 119 using xhci_hcd Jun 14 10:01:18 kernel: usb usb1-port2: attempt power cycle Jun 14 10:01:17 kernel: usb 1-2: new full-speed USB device number 118 using xhci_hcd
Installed a bunch of different bt-managers and still got the errors below in journalctl: Jun 14 10:01:17 kernel: usb 1-2: new full-speed USB device number 117 using xhci_hcd Mouse would work, freeze for a few seconds, and usually start working again (sometimes they would just die until a reboot). I came across this thread in searching for a similar issue on a Thinkpad Yoga 11e with any bluetooth mice I tried using stock Gnome. Installing bluez-hid2hci fixed this issue for me. usb 3-1: new full-speed USB device number 10 using xhci_hcd usb 3-1: USB disconnect, device number 9 When your mouse is powered off, press both the right and left buttons at the same time, switch the button on the rear case to the Bluetooth icon, then wait for. usb 3-1: new full-speed USB device number 9 using xhci_hcd usb 3-1: USB disconnect, device number 8 Bluetooth: hci0 command 0x0401 tx timeout Bluetooth: hci0 advertising data length corrected
#Logitech mx master 2s disconnecting Patch#
Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e8.hcd not found bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e8.hcd failed with error -2 usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1: New USB device found, idVendor=0a5c, idProduct=21e8 usb 3-1: new full-speed USB device number 8 using xhci_hcd usb 3-1: USB disconnect, device number 7 Bluetooth: hci0 command 0x2005 tx timeout My MX Master 2S connected with USBBT2EDR4 (StarTech) keeps coming and going with connectivity, here's a sample of dmesg showing the cycle of a few disconnections and reconnections: Bluetooth: hci0 command 0x0401 tx timeout
0 kommentar(er)
