-
Notifications
You must be signed in to change notification settings - Fork 74k
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
tensorflow doesn't work with CUDA 12 on WSL2 #59413
Comments
Hi @luckeyca, Anyways you can try these first.
After that please try the below code and confirm output. Also please share the output of the command Thank you! |
Hi @SuryanarayanaY, my question is related to CUDA 12, yet your conda example is using cuda 11.2. |
Did you try your suggested procedure with CUDA 12? @SuryanarayanaY When I change the cudatoolkit=11.2 to cudatoolkit=12.0, it says there is no such package |
Iam following Tested configurations as per Official documentation here. With TF 2.11v CUDA 11.2 is tested configuration and with tf-nightly CUDA 11.8 is tested. CUDA 12 not yet a tested configuration and there might be compatibility issues(may be with some APIs) which may not be addressed now. However As per Official documentation it refers to this source where the steps to install CUDA toolkit are mentioned below.It seems you have missed installation of CUDA toolkit as per your mentioned steps the below command is missing. Attached below is snapshot of commands to follow as per Tensorflow/Nvidia official source. Once above steps followed for CUDA toolkit installation please follow remaining steps from Tensorflow documentation here from step2 and in Step4 skip GPU driver installation and continue from CUDA and cuDNN installations using conda. We recommend to use cuda toolkit 11.2 for TF 2.11v and 11.8 for tf-nightly. Please follow the steps thoroughly and let us know if any problem still exists. Thanks! |
Hi @SuryanarayanaY , I did install cuda 12.0 already. If you looked at the top, in the problem description, "relevant log output" section, from nvidia-smi command output, it clearly listed cuda 12.0 there. |
I think the problem is with cudnn, even the latest 8.7 does not support cuda 12 yet, only up to 11.8. |
Yes. Current TF-nightly was tested on CUDA 11.8 version only.Hence there is chance of compatibility issues with higher version. After installing the driver one has to install compatible CUDA and cuDNN toolkit with the required TF version using the conda command and setting the paths correctly as mentioned in documentation which are listed below also.
|
Same question with you, even same version of CUDA. I've got through various forums and been tormented by this problem for a day now. T_T
|
@piwawa I wasted the entire day today on this. I think that part of the problem is the Nvidia WSL2 instructions will get you to install CUDA 12, and that may not work properly with Tensorflow right now. Also, the Tensorflow instructions use conda to install some CUDA 11 stuff, and I am wondering if that is a disconnect with the Nvidia instructions. So tomorrow with a clear head I'm going to try to re-do everything with CUDA 11 and see if I can get it to work. @SuryanarayanaY I was trying to avoid using conda, as I usually manage 100% with pip. However, I don't think I fully understand these 2 instructions:
I use Linux but don't do much at system level if I can avoid it. I had previously modified by .bashrc in WSL Ubuntu 20.04 to update the LD_LIBRARY_PATH. With these instructions I'm unclear what is CONDA_PREFIX and what the desired end result is. If I already have a venv (made using Python) and want to install all this there, I'm confused by these new instructions forcing the use of conda. |
Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
binary
Tensorflow Version
v2.11.0-rc2-17-gd5b57ca93e5 2.11.0
Custom Code
No
OS Platform and Distribution
WSL2 Ubuntu 22.04
Mobile device
N/A
Python version
3.10.6
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
12.0
GPU model and memory
No response
Current Behaviour?
Standalone code to reproduce the issue
Relevant log output
The text was updated successfully, but these errors were encountered: