Solution for CUDA Installation Issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9k
- Forks
- 1.5k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 3
Description
I noticed there were a few issues regarding CUDA, and I had ran into the same issue while installing on Google Colab.
It's worth noting that there's often multiple versions of CUDA installed when using pre-installed VMs or Containers, and symbolic links may exist that aren't correctly pointing to what nvidia-smi is stating as the driver CUDA version.
In my case, nvidia-smi was showing CUDA version 10.1 while installing apex was trying to use CUDA 10.0, which was symbolically linked to /usr/local/cuda
Here's how I was able to resolve it on Colab-GPU (Linux) with Latest Pytorch with CUDA enabled
# Check Nvidia-smi
nvidia-smi
# Checks which CUDA is Symlinked
ls -al /usr/local/cuda
# Unlinks Symbolic Link
sudo unlink /usr/local/cuda
# Creates New System Link to CUDA 10.1
sudo ln -s /usr/local/cuda-10.1 /usr/local/cuda
# Install APEX based on another issue
sudo pip3 install -v --no-cache-dir --global-option="--pyprof" --global-option="--cpp_ext" --global-option="--cuda_ext" .
EDIT: installing with --user led to apex package not being found when running code in a notebook
Hope this helps!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is identified. Start by reproducing the reported Colab/Linux setup with nvidia-smi and ls -al /usr/local/cuda; done would require a maintainer-defined change or documentation target for handling mismatched CUDA links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python, pytorch
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100