-
Notifications
You must be signed in to change notification settings - Fork 822
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
Cannot find GPU devices on Bash #829
Comments
Not currently. This is a highly requested feature on our User Voice forum. I would suggest you add your workflow to the discussion there so help us prioritize features we work on in the future. Thanks for trying out WSL! |
@forhonourlx I wonder if it ever will (and if it did, how would it work). If MS could code some kind of generic driver that passed openGL DRM stuff to the Windows driver stack and passed the rest of it onwards to an X or Wayland server on Windows, maybe it could work, but otherwise I think the best you might get is something that will inevitably be kind of crappy virtualized graphics card. If not, AIGLX is still a supported (if not the absolute fastest) way of doing graphics rendering in Linux (and according to my sources (Arch Wiki) was still the way that most desktop composition was done until at least 2009). Support for something like AIGLX (which is hardware-agnostic on the X client side) already exists in vcXsrv (although the most important plugin GL_PIX_FROM_TEXMAP) is not implemented right now in hardware accelerated mode, leading to very bad performance due to falling back to software rendering. |
Another major use case for GPUs is OpenCL/CUDA/etc, which I don't think AIGLX will help with? And it's more relevant to the sorts of use cases that WSL is initially targeting. If there were enough demand and if the relevant players felt like playing nice (inter-company coordination is complicated...), in principle the WSL team could collaborate with NVidia (I'd list all vendors but really NVidia seems to be the big player in this particular field) and build a WSL driver. Not saying that's the best approach, nor that it would ever necessarily happen; just saying it could. (If you care about CUDA in particular, it might be worth making some noise on the NVidia forums as well; make sure they also hear about any demand for support.) |
If cuda is okay on bash, maybe some deep learning tools, such as tensorflow, caffe, can directly run on windows. |
Truly! |
Would be nice! |
Any insights on how challenging, technically, this would be? Just to adjust expectations accordingly. |
Expecting... |
Ok it's 2017 November. Any updates on this so far? |
Can we have it for Thanksgiving or a super early Christmass present the latest, please? |
We are quite aware of the demand of this feature and are working to see how best we can support it. It's very unlikely to be part of the next (FCU + 1) release. @jotaf98 - The challenge here is not just technical but also logistical and other. Because there are multiple players involved here, and not everything is in direct control. But, we are exploring all possibilities here. |
@sunilmut Thanks for the insight! Rooting for you guys to find a way to make it work. |
Looking forward! |
Ditto! |
I'd like to add to the chorus, OpenCL support from the bash shell is very important to me. Thank you. |
Any new updates on this? I would love to be able to run OpenGL apps. |
Really looking forward to being able to use WSL for running/testing our GPU-intensive programs. Now executing nvidia-smi in WSL Ubuntu, I get "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." |
+1 on @peterjc123 request. I'm trying to run some deep learning libs on WSL and can't. Some help here guys. Can you get Abolade on the case? 👍 |
any updates! |
C'mon guys, I really need this feature... |
please add also sound system. no sound can be played from wsl |
I literally took a shot 🥃🍻 |
I followed the documentation and it seems like it's successfully installed, but this code hangs indefinitely with one cpu core at 99%
is this the normal behavior and I should just wait? |
@Riccorl It could be a nvdia driver problem https://forums.developer.nvidia.com/t/known-limitations-with-cuda-on-wsl-2/128506 |
Unfortunately, I'm using a Ryzen CPU. I think I should just wait then. Thank you for the link! |
I'm not on the insider branch and from the blog entry it seems, that the rocm/rock and opencl apis arent yet supported, and therefore the hip library not functional. |
New nvidia drivers 455.41 available should fix the freeze problems |
Can someone please post the steps to get this working?
Sorry if this is hijacking the thread, but I do think my problem is "cannot find gpu devices on bash" |
@Kyle2142 what's the output of |
thanks for the quick reply, please see edit above. Should've remembered to include that |
It seems the gpu is available only for the first wsl2 running distro. Try |
lspci still shows no nvidia device |
Any error message related to dxg in |
It still does not show on |
how did you upgrade the kernel? i have 4.19.104 and cannot upgrade to latest.. in downlaod section, only get source... do i need to compile?! |
@y0d4a You need to be in build 20150 it comes via Windows Update or with |
Again asking will and drivers and therfor rocm/hip sopport come to wsl or is there already a way to get it to work |
I can't get WSL 2 and Ubuntu and NVidia GPU to work. I started a thread on AskUbuntu with my experience. Microsoft/NVidia please help and contribute that thread to raise the visibility for the idea of having a complete, correct and simple set of instructions for WSL 2/Ubuntu/NVidia. I am doing this on a Lenovo Yoga P40 with latest Windows fast track and Quadro M500M with latest NVidia drivers, as described in the thread. |
I'm marking this issue as complete, since the original ask (Making GPU devices available in WSL) is fulfilled. If you're running into specific issues please open another issue on this repo using our bug template! :) |
Does win10 bash support GPU devices?
The text was updated successfully, but these errors were encountered: