Logitech Unifying Receiver stops working after it's removed and plugged back in

M

matthei

Member
Aug 20, 2021
32
8
13
39
If I disconnect and reconnect the Logitech Unifying Receiver (usb-passthru to a Windows VM) it no longer works, I have to restart the VM to get it working again.

The USB passthru is per-port (from config file: usb0: host=3-1.1.1,usb3=1)
When disconnecting the USB receiver dongle, the host outputs these messages:

usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: Cannot enable. Maybe the USB cable is bad?
usb 3-1.1.1-port2: cannot disable (err = -71)

usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: cannot reset (err = -71)
usb 3-1.1.1-port2: Cannot enable. Maybe the USB cable is bad?
usb 3-1.1.1-port2: cannot disable (err = -71)

... and so on, about 5 repetitions, and then final line:
hub 3-1.1.1:1.0:  hub_ext_port_status failed (err = -71)

I can unplug & replug other devices just fine, it's just this Unifying receiver that's causing this. Perhaps the unifying receiver is itself a USB hub, and it's not playing well with something? I can also unplug & re-plug a regular USB hub (ugreen brand) and all devices connected to it get reconnected back normally within seconds.

Reasons: I'd like to use the same mouse & keyboard for both VMs (each has it's own GPU passed thru). I have a 4-port USB "switch" that can toggle the USBs between two devices, but i've just wired both inputs into the same host machine. But to make sure that the issue is not this USB switch, I've tested simply removing the Unifying receiver and reconnecting it back, and it's this error.

I appreciate any help or pointers you can give me on this subject, thanks!
 
Last edited:
Hi,
a stupid suggestion from me :). Did you try plugin the Unifiying receiver into a USB hub plugin that into the passed through port?
 
You plug your Unifying receiver into a usb hub. This usb hub you plug into the passed through port on your proxmox host.
 
shrdlicka said:
You plug your Unifying receiver into a usb hub. This usb hub you plug into the passed through port on your proxmox host.
Click to expand...
Yes, it is plugged into a USB Hub. But if i remove the receiver i get these errors, and then when I plug it back, the mouse no longer works until I restart the VM.
 
You could try the same thing with a Linux VM and see if the same thing happens as with the Windows VM.
 
Hey, just wanted to thank you for your reply and the idea what to try. I have just taken some time to investigate this further, and yes a Linux guest machine works just fine. When I unplug and re-plug the Unifying Receiver, the mouse resumes working after a few seconds.

So it looks like a windows issue.
(Or possibly Windows in combination with Proxmox)



Just an FYI: I remember that in the past, there have been cases when after unplugging some device from a USB port, it no longer worked after re-plugging it back. However, it did start working after I plugged it into another USB connector.
I have just tried this same approach: I unplugged the Unifying Receiver, and plugged it back into a different port, but although windows played the "device connected sound", the mouse remained unmovable.
 
Last edited:
  • Like
Reactions: shrdlicka
matthei said:
Hey, just wanted to thank you for your reply and the idea what to try. I have just taken some time to investigate this further, and yes a Linux guest machine works just fine. When I unplug and re-plug the Unifying Receiver, the mouse resumes working after a few seconds.

So it looks like a windows issue.
(Or possibly Windows in combination with Proxmox)



Just an FYI: I remember that in the past, there have been cases when after unplugging some device from a USB port, it no longer worked after re-plugging it back. However, it did start working after I plugged it into another USB connector.
I have just tried this same approach: I unplugged the Unifying Receiver, and plugged it back into a different port, but although windows played the "device connected sound", the mouse remained unmovable.
Click to expand...
By any chance did you find a solution for this @matthei?

I have 2 USB switches, 1 works fine and the other behaves like yours.
 
I have just been playing with this a bit more, the problem is the Hub. It's an "Orico 7-port powered usb hub". https://www.orico.cc/usmobile/product/detail/id/3305 - or well, whatever chip is inside.

Plugging the Unifying Receiver directly into the motherboard's rear-panel-IO, I can remove the Unifying Receiver and plug it back in, the mouse starts working again without needing to restart the Windows Guest VM.

Well, there seems to be some issues with timing the unplugging & replugging it. It seems as if, when I unplug and plug it back right away, like a second, the mouse still doesn't work. But waiting about 10 seconds, then plugging it in, seems to work. Well, sometimes it doesnt work, but sometimes it worked even with the very short delay.



rtgy said:
I ended up getting a new mouse with the Logitech Bolt receiver and the USB switch works fine on that.
Click to expand...
Thanks for sharing your solution!
 
Update on the situation. I got a Logitech MX Master 3s for Business.
The "Logi Bolt" receiver works without any problems, in this same USB Hub. I can unplug, replug to the same port, replug to a different port... in all cases, the mouse resumes working in a second or two.
 
  • Like
Reactions: rtgy
I'm running into this same issue, with the Logitech Unifying Receiver USB dongle and a Windows 11 VM. I am using it for a Logitech K400 Plus combo keyboard/trackpad.

I spent some time debugging and it looks like Logitech maintains their own kernel drivers for their devices. Which is likely where this bug is coming from...

I was able to get hot-plugging to work by adding a modprobe alias to prevent the driver from being loaded at runtime:

I made a new file /etc/modprobe.d/my-blacklist.conf:

Code: 
alias hid:b0003g*v0000046Dp0000C52B my_blacklist

I found the string to use by running `modinfo hid-logitech-dj` and looking for the "alias" line that most closely matched the vendor/product ID reported by the kernel for my USB dongle. Yours might be different. When I plug the dongle in the usbhid driver still loads but it doesn't prevent the device from being passed to the VM now.
 
You must log in or register to reply here.
Top Bottom