-
-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USB storage not accessible #70
Comments
Thx for the report and the dump. After device recognition (which ends at timestamp 23.506548), thing fail (or rather: stall). This is right after a SEND request, probably to access actual disk content for the first time. After that it is just repeated port resets. What I notice is: super_speed. That means either USB 3.0 or 3.1. I must admit, I only tested that with my single USB 3 device I have available (a Kingston USB flash drive). So it could very well be that not all of the USB 3 standard is covered. What does not help either is that the USB 2.0 standard is available online, but the USB 3 standard is not... If you want your device working ASAP, you could try plugging it in a USB 2.0 port, or add a USB 2.0 hub between your USB 3 port and the device. To debug the USB 3.0 side of things: I am interested in a TRACE log of usbipd-win, as explained in https://github.com/dorssel/usbipd-win/wiki/Troubleshooting. |
I tested the USB 2 port as well but the result is the same. I will do some further testing with other devices... Attached the trace log for reference. |
Thx. USBSUP_XFER_UNDERRUN -> EREMOTEIO -> 0 That's the error. I will look into it to find out when/why/how such an error can occur. |
Thank you very much... I appreciate your support! |
Hi, I fixed a bug that may just solve your issue. Would you be willing to try the MSI from this PR: https://github.com/dorssel/usbipd-win/actions/runs/1432468492? You would have to uninstall usbipd-win, and then install this MSI. It is not signed yet (but the drivers are). |
Hi @dorssel, One sidenote for your wsl-wiki since you suggest enabling some features in the kernel and this here is about storage: Have a good day! 👋 |
Forwarding the suggestion to the WSL team: @benmcmorran. Please note that you now have a non-release version running that reports itself as 1.1.2. |
Btw upgrade did work without uninstall as well... just fyi (forgot to uninstall first on the second device). |
Yeah, I always forget that a PR build is already on the next version. When you go to release 1.1.2, you will have to uninstall or else the installer thinks you are trying to go from 1.1.2 to 1.1.2 (which won't work). |
System:
Ubuntu 20.04.3 LTS (Ubuntu package from MS store)
5.10.60.1-microsoft-standard-WSL2+
linux-tools-5.4.0-77-generic.
I am trying to atach a usb flash drive with usbipd
wsl attach --busid 1-4
which works without error.I can see the device with
lsusb
:However, it is not visible with
lsblk
, sda-sdc are the virtual wsl disks:In
dmesg
I can see that it is recognized but further data cannot be obtained:The first three lines indicate everything works normal but after that nothing happens for a long time while errors come up later.
I tried with two different flash drives but the result is the same.
There's no cable involved as well as no external power supply possible, both by design.
Attached is the full dmesg log with USBIP dump messages:
dmesg.txt
Maybe someone has an idea? Thank you very much!
The text was updated successfully, but these errors were encountered: