Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Cuda can not be installed #327

Closed
dtracers opened this issue May 5, 2016 · 13 comments
Closed

Cuda can not be installed #327

dtracers opened this issue May 5, 2016 · 13 comments

Comments

@dtracers
Copy link

dtracers commented May 5, 2016

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)

@russalex
Copy link
Contributor

russalex commented May 6, 2016

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.

@firewave
Copy link

firewave commented Oct 4, 2016

I also ran into the lspci problem - should this be tracked as a separate issue or is fine having it here implicitly?

@russalex
Copy link
Contributor

russalex commented Oct 4, 2016

@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.

@firewave
Copy link

firewave commented Oct 4, 2016

@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.

@ghost
Copy link

ghost commented Feb 7, 2017

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.

@firewave
Copy link

FYI lspci is also used by do-release-upgrade. The errors messages mentioned in the first post happen very early during "Reading cache...".

@craigloewen-msft
Copy link
Member

craigloewen-msft commented May 19, 2020

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.

@therealkenc
Copy link
Collaborator

The OP lspci | grep -i nvidia repro is (academically) now LZ #5492

For CUDA and DirectML, /fixed 20150

@ghost ghost closed this as completed Aug 7, 2020
@ghost ghost added the fixedininsiderbuilds label Aug 7, 2020
@ghost
Copy link

ghost commented Aug 7, 2020

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!

@Munyola
Copy link

Munyola commented Nov 18, 2021

#327 implications problems not yet working not unless render from neighborhood docs.Microsoft.com/windows/wsl

@Munyola
Copy link

Munyola commented Nov 18, 2021

#11045Terminal now supports actions that can run multiple other actions (we heard you like actions,even if azure failed but colour succeed.

@Munyola
Copy link

Munyola commented Nov 18, 2021

No automatic link on terminal run with your experience

@nonsec
Copy link

nonsec commented Oct 20, 2022

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?

This issue was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

7 participants