usbipd-win icon indicating copy to clipboard operation
usbipd-win copied to clipboard

WSL usbip: error: Attach Request for 1-2 failed - Unknown Op Common Status

Open xyf2002 opened this issue 5 months ago • 4 comments


Description:

I encountered an error while trying to attach a USB device to my WSL 2 distribution using usbipd. The command fails with an "Unknown Op Common Status" error.

Steps to Reproduce:

  1. Connect the USB device to the Windows host.
  2. Run the following command in PowerShell:
    usbipd wsl list
    
    • The device is listed with busid=1-2.
  3. Attempt to attach the device to the WSL distribution:
    usbipd attach --wsl --busid=1-2
    
  4. The following error occurs:
    usbipd: info: Using WSL distribution 'Ubuntu' to attach; the device will be available in all WSL 2 distributions.
    usbipd: info: Using IP address 172.29.48.1 to reach the host.
    WSL usbip: error: Attach Request for 1-2 failed - Unknown Op Common Status
    usbipd: error: Failed to attach device with busid '1-2'.
    

Expected Behavior: The USB device should be successfully attached and available in the WSL 2 environment.

Actual Behavior: The attachment fails with an "Unknown Op Common Status" error.

System Information:

  • OS: Windows 11 (Specify version and build number)
  • WSL Version: WSL 2 Prerelease
  • WSL Distribution: Ubuntu 22.04
  • usbipd-win Version: 4.3.0
  • USB Device: Jlink

Additional Information:

  • I have verified that the device is recognized correctly in Windows Device Manager.
  • I have tried restarting the usbipd service and rebooting the system, but the issue persists.
  • I ran usbipd in debug mode, and the following logs were generated: (Attach any relevant logs if available)
  • Network connectivity between WSL and the host is working correctly. I can ping 172.29.48.1 from within WSL.

Logs and Debug Output: (Include any relevant logs from running usbipd in debug mode or dmesg output from WSL, if applicable)

Questions:

  • Are there any known limitations or additional configurations required for this type of USB device?
  • Could this issue be related to specific WSL 2 kernel configurations or compatibility issues?

xyf2002 avatar Sep 20 '24 13:09 xyf2002