search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.41k stars 822 forks source link

USBIPD broken by latest WSL pre-release version #11901

Open Conduent-Max opened 2 months ago

Conduent-Max commented 2 months ago

Windows Version

Microsoft Windows [Version 10.0.19045.4651]

WSL Version

2.3.14.0

Are you using WSL 1 or WSL 2?

Kernel Version

6.6.36.3-1

Distro Version

Debian 12.0

Other Software

Hello, I just migrated from WSL 2.2.4 to 2.3.14. The kernel changed from 5.15.153.1 to 6.6.36.3-1. Since then I cannot connect my uSD/USB adapter.

Repro Steps

usbipd list Connected: BUSID VID:PID DEVICE STATE 2-6 0c45:674c Integrated Webcam, Integrated IR Webcam, USB DFU Not shared 2-8 0a5c:5843 Dell ControlVault w/ Fingerprint Touch Sensor, Microsoft ... Not shared 2-10 8087:0033 Intel(R) Wireless Bluetooth(R) Not shared 3-2 0bda:8153 Realtek USB GbE Family Controller Not shared 3-4 0b95:1790 ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter #2 Not shared 4-1 067b:23a3 ATEN USB to Serial Bridge (COM2) Not shared 4-3 0557:2008 ATEN USB to Serial Bridge (COM1) Not shared 4-5 0bda:4014 Realtek USB Audio Not shared 4-6 413c:2113 USB Input Device Not shared 4-7 0b33:1004 USB Input Device Not shared 5-3 1908:0226 USB Mass Storage Device Shared (forced)

usbipd attach --wsl --busid 5-3 usbipd: info: Using WSL distribution 'debian12' to attach; the device will be available in all WSL 2 distributions. usbipd: info: Loading vhci_hcd module. usbipd: error: Loading vhci_hcd failed.

Expected Behavior

The USB device should be available in WSL. Checked using lsusb

Actual Behavior

The USB device is not be available in WSL.

Diagnostic Logs

No response

github-actions[bot] commented 2 months ago

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Conduent-Max commented 2 months ago

After checking, this issue is a duplicate of #11795, thus closing this thread.