-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add support for CUDA 12 #13637
Comments
@hawkinsp XLA was updated to CUDA 12 few days ago. Is there any chance to start working with support to CUDA 12? |
@GrzegorzWarzecha The current blocker is that NVIDIA has not released a version of CUDNN that works with CUDA 12. Until they do that there's not much we can do! |
@nouiz for viz |
Why NVIDIA cannot release CUDA with compatible CuDNN? I'm really surpirsed how bad is support from NVIDIA - I buy GPU mainly for AI, but this problems are Hell on Earth. When I try tensorflow-gpu on Mac Mini M1 be a no problem - 5 minutes and done - everything works, but on PC still any problems with version compatibility etc. |
wait! The release is coming in the following weeks! |
CUDNN 8.8 GA for CUDA 12 is scheduled for Feb 2023, so it's almost around the corner. 😃 |
Oh, I gave last weekend for preparing system dedicated for GPU machine learning, but I falsely hoped about CUDA and CuDNN it's released together 🫣 |
when cudNN is rolling out for CUDA12 |
this month |
How to run my U-net model in GPU , And i have GT1650 TI with i510300H processor, |
@hawkinsp |
It's out now. |
Great! |
It looks like all JAX tests pass under CUDA 12, provided NCCL is updated to 2.16, which is newer than the default version JAX uses. If you want to try building a
where We'll work on getting this checked in. |
hi, where can i download cudnn 8.8? cant find the version online |
you have to register in nvidia page. |
thank you!!! i already am, but if u google cudnn 8.8, u dont find anything. |
it's still not uploaded in archives |
Does the tensorflow gpu compatibility already work for cuda 12 and cudnn 8.8? because my rtx 4070ti still doesnt get detected :/ |
you have to wait to tensorflow 2.12 or use nightly versions |
what do you mean by nightly versions? |
|
i still dont get an 1 as output, i dont get it. |
This is not the right place to discuss TensorFlow. Please keep discussions in this project related to JAX. |
Anyone know when jaxlib wheels are expected to be available for CUDA 12? |
I think that when the cudnn is uploaded to archive page |
…ntime stubs. Fixes NCCL test failures in JAX test suite. Issue google/jax#13637 PiperOrigin-RevId: 509597231
…ntime stubs. Fixes NCCL test failures in JAX test suite. Issue google/jax#13637 PiperOrigin-RevId: 509610727
…ntime stubs. Fixes NCCL test failures in JAX test suite. Issue google/jax#13637 PiperOrigin-RevId: 509610727
…ntime stubs. Fixes NCCL test failures in JAX test suite. Issue google/jax#13637 PiperOrigin-RevId: 509610727
Cuda 12.1 is out |
Note that JAX should build/work fine with CUDA 12, we just need to figure out our CI/wheel release process. If you need a CUDA 12 wheel right now, you can build it from source. |
If this didn't or doesn't work why do the docs say "or newer"? |
The docs should be reworded; they were written when CUDA 11 was the newest version. That said, the next release of JAX will have CUDA 12 wheels. |
It's an interesting problem. Feels like github and LLM might be on the verge of detecting and highlighting these kind of things with one of their bug bots. It is somewhat non-trivial for the reader to find last timestamp of that edit, then find the state of versions available at that time and then make the call. |
I haven't yet updated the installation instructions, but we released
or
Installation instructions in the README coming soon. |
@hawkinsp I installed it with both options and am getting following error when trying to execute
|
@terafo Can you open a new bug with details? In particular, the |
@hawkinsp sure, just did it. |
There are three pieces we need before we can release jaxlib wheels for CUDA 12:
The text was updated successfully, but these errors were encountered: