Update conda-forge installation docs after drop of support for CUDA 11 #25374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since April 2024
jax
does not support anymore CUDA 11, see https://github.com/jax-ml/jax/blob/jax-v0.4.37/CHANGELOG.md#jaxlib-0426-april-3-2024 .If only CUDA 12 is supported, the installation instructions for the
conda-forge
build ofjax
can be simplified:ptxas
executable is now available directly in conda-forge and is automatically installed as a dependency of cuda-enabledjaxlib
builds (see Add run dependency on cuda-nvcc when using CUDA 12 conda-forge/jaxlib-feedstock#241), so there is no need to manually add thenvidia
channel or install additional packages, or explain what this additional packages arejaxlib
gets marked asbroken
(i.e.yanked
) for any reason, on a machine with a CUDA-enabled GPUconda install jax -c conda-forge
will automatically install the CUDA-enabled build ofjaxlib
. However, this will silently fail if for any reasonnvidia-smi
does not work on the machine, so I also left the documentation on the command to explicitly request the installation of a CUDA-enabled build ofjaxlib
.