-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
No longer able to access FTDI device in WSL2 #948
Comments
Does |
Here's the output of
So it looks like it is listed. I'm curious, how could I be missing the right driver for this device in the kernel when it was working previously, and with no changes to my WSL2 instance it just stops working? Here's my WSL2 info
Also, how would I install the driver for this device if it is missing all of a sudden? |
Hmmm. This is a fairly standard FTDI device. And a driver is included in the stock WSL kernel. You said it worked before? How long before? Because:
is relatively new (see https://github.com/microsoft/WSL2-Linux-Kernel/releases/tag/linux-msft-wsl-5.15.146.1). Maybe it is |
I know I was using it last year after July at least. It's been a few months since I have connected this device. But the only things I've been doing in my WSL2 instance is compiling my c++ code, sometimes switching to WSL version 1 and then back to version 2, and the occasional |
Okay so I found these instuctions Run FTDI USB devices on Windows 10/11 WSL2 which I found here FTDI device not working WSL with usbipd-win. This issue also pointed to that same blog so I'm gonna post it here in case anyone else finds it helpful WSL/issues/11346 In the instructions it has you install pahole and that didn't work for me initially, so I installed it following the instructions in the repo python-pahole-utility At the end of all of that I finally see
|
Ah, I hadn't realized that Microsoft changed the way they build the kernel. Previously it was monolithic (all drivers built-in), but apparently they switched to modules:
|
These are the ones that are now modules:
|
Change happened in Januari: microsoft/WSL2-Linux-Kernel@afb2c95 |
Oh, so those things that we previously built in, by default with the kernel update are now modules you have to install separately? Did I install all of those modules you listed, or just the SERIAL_FTDI module? I don't know too much about the kernel I built, just followed the instructions. |
If you use |
@dorssel solution works for me too. Actually, it is not necessary to rebuild the kernel like @crose72 did in his previous message. It is sufficient to enable systemd on WSL. |
I'm on Windows 11 and using WSL2 with Ubuntu-20.04. In July 2023 I followed the instructions at Connect USB devices usbipd to attach an FTDI to USB device. I did it successfully for several months. After several months of not attaching any USB devices to WSL2 I went to try it again and it's not working.
It seems that I can still successfully bind and attach my usb device to WSL2 (though I previously didn't need to use the bind command) and here's the result
After doing that I should see the device listed as
/dev/ttyUSB0
but this is what I seeI did uninstall the version of usbipd that I was using and installed the latest, but no dice. I've looked all over but none of the suggestions I've found online have yielded any results. I didn't change anything so I'm not sure why it stopped working all of a sudden.
Can someone help me troubleshoot this?
The text was updated successfully, but these errors were encountered: