Hello,
we are trying to use a Logitech Logi MeetUp 2 (VID 046d:0963) with VirtualHere USB Server on a Linux server, but we cannot get the device to work correctly.
The device is detected normally by Linux:
Bus 001 Device 007: ID 046d:0963 Logitech, Inc. Logi MeetUp 2
It is connected as a High Speed USB device:
usb 1-4: new high-speed USB device number 7 using xhci_hcd
usb 1-4: New USB device found, idVendor=046d, idProduct=0963, bcdDevice=2.25
usb 1-4: Product: Logi MeetUp 2
usb 1-4: Manufacturer: Logitech
usb 1-4: SerialNumber: 2543FDN06P78
usb 1-4: Found UVC 1.00 device Logi MeetUp 2 (046d:0963)
Linux also detects the UVC and HID interfaces correctly.
However, when VirtualHere tries to capture the device, we get:
Error -1 resetting device 0x046d/0x0963 for capture
Error binding device 14 [046d:0963] to connection 3, BIND_ERROR
Unmanaging device 14 [046d:0963]
At the same time, the USB device disappears and is re-enumerated:
usb 1-4: USB disconnect, device number 6
usb 1-4: new high-speed USB device number 7 using xhci_hcd
We also tested the device without VirtualHere running.
The device remains visible:
lsusb -d 046d:0963
Bus 001 Device 007: ID 046d:0963 Logitech, Inc. Logi MeetUp 2
but attempting to reset it directly with usbreset:
sudo usbreset /dev/bus/usb/001/007
returns:
No such device found
Interestingly, lsusb continues to detect the device normally afterwards.
So at this point we are unable to determine whether this is related to the MeetUp 2 firmware, its USB implementation, the Linux USB stack/xHCI controller, or something specific to the way the device handles USB reset.
System:
- Linux / Debian 13
- USB controller: Intel xHCI
- Device: Logitech Logi MeetUp 2
- VID:PID:
046d:0963 - Firmware/device revision reported by USB:
2.25 - Serial:
2543FDN06P78
Has anyone encountered this behavior with the MeetUp 2 on Linux or with USB redirection software such as VirtualHere?
Is there a recommended way to reset/reinitialize the MeetUp 2 from Linux, or any known firmware/USB compatibility issue that could explain this behavior?
Any suggestions or diagnostic steps would be greatly appreciated.