Cuda can not be installed
dtracers opened this issue · 13 comments
As of right now cuda 7.5 can not be installed through the usual means because of the same issue affecting java. (just thought I would create this and link it to the same issue before someone else does and)
(Also does anyone know if cuda will work at all when compiled manually?)
Same problem as issue #49
This is through the debian local package method.
Additionally cuda will not work even when this bug is fixed because bash is now aware of the graphics card.
running this command is supposed to list the nvidia card if your computer has one installed
lspci | grep -i nvidia
its output is this:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
This could also be related to the other issues people are having with /proc
(cant find an official issue number for /proc issues)
Cuda is not supported at this time. We have requests to get Cuda on our User Voice page. We're using the user voice to help inform our priority decisions.
I also ran into the lspci problem - should this be tracked as a separate issue or is fine having it here implicitly?
@firewave, just wondering, but did you hit lspci trying out Cuda or was it in another scenario? Either way, it would be interesting to have a new User Voice just for lspci to see if it gets any traction. We know this is a blocker for some people, but it's always good to get a feel for about how many.
@russalex I hit the issue using lspci explicitly. I use it to get information about the graphics cards of the system. It's part of a bigger script which fetches hardware information about the system.
I can confirm with @firewave that this is something you do to check if there is a GPU installed so it could be a broader issue than just for CUDA support.
FYI lspci is also used by do-release-upgrade. The errors messages mentioned in the first post happen very early during "Reading cache...".
Hi folks, we announced today that WSL will support GPU compute! I'll be posting more details about this change today. :)
And here are the details on our blog post.
This bug or feature request originally submitted has been addressed in whole or in part. Related or ongoing bug or feature gaps should be opened as a new issue submission if one does not already exist.
Thank you!
#327 implications problems not yet working not unless render from neighborhood docs.Microsoft.com/windows/wsl
#11045Terminal now supports actions that can run multiple other actions (we heard you like actions,even if azure failed but colour succeed.
No automatic link on terminal run with your experience
lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
5 years later and this still isn't fixed? what's the point of using WSL if you don't even have a real working linux os? virtualbox can do it, why can't WSL? What else is broken?