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
Installation with CUDA11 #20
Comments
Hi, Thanks for reporting. Would it be possible for you to try out with CUDA 11.2? It seems to be a known issue with CUDA 11.1 as reported on nvidia forums. Thanks! |
I see. Unfortunately we don't have 11.2 available on our cluster yet. I will check with our cluster admins if it's possible to add 11.2. |
By the way, you can also install the CUDA toolkit locally. The driver does not need to be updated. I did it from: Then run: |
That's not really helpful on our cluster set-up; if I can't use one of our precompiled CUDA versions I can't deploy this and it's overall much more effort for me to setup. We have a CUDA 11.4 set-up now and I can run the installation with it, but it fails at runtime:
|
Sorry for the inconvenience. The error with CUDA 11.4 seems like the CUDA driver is old and does not support CUDA 11.4. For 11.4 you need a driver of version >=470.42.01 as per CUDA release notes. Could you please check if the driver version satisfies this version using |
No worries, that's the downside of custom CUDA code, installation is always a pain.
Ok, that makes sense. Indeed the driver is older |
Ok, I managed to install with CUDA 10.2 now. (This failed for me earlier because I didn't use the gcc that was used to compile this CUDA version.) Thanks for the help. I will look into running some of my own benchmarks for rama and will for sure follow up with some other questions ;). |
Hi,
I tried to install RAMA with CUDA11, using the pip installation instruction (
python -m pip install git+https://github.com/pawelswoboda/RAMA.git
). UsingThis fails with the following error:
I also tried with CUDA 10, but ran into other issues. CUDA 11 would be much better for me in order to be compatible with our stack.
The text was updated successfully, but these errors were encountered: