PyTorch 1.8.1 - CUDA 11.1 - Windows 10 - unsatisfied link
See original GitHub issueI am running into a Problem on a MS Windows 10 OS.
With djl.version=0.11.0-SNAPSHOT and
<dependency>
<groupId>ai.djl.pytorch</groupId>
<artifactId>pytorch-native-auto</artifactId>
<version>1.8.1-SNAPSHOT</version>
</dependency>
on CUDA 11.1 I get a java.lang.UnsatisfiedLinkError. I see links to the following libraries that are not found
on CUDA 10.2 (on a Turing GPU) everything works fine.
Issue Analytics
- State:
- Created 2 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Previous PyTorch Versions
An open source machine learning framework that accelerates the path from research prototyping to production deployment.
Read more >Conflict with cudatoolkit 11.0.221 · Issue #51080 - GitHub
This should be resolved now that we're no longer producing CUDA 11.0 binaries and now only produce CUDA 11.1 binaries. For nightlies use:...
Read more >Cuda not compatible with PyTorch installation error while ...
I tried to train the model with A100 computing cluster. I implemented the totally same command I used for V100 computing cluster, ...
Read more >Pytorch cuda is unavailable even installed ... - Stack Overflow
My environment is (Ubuntu 20.04 with NVIDIA GTX 1080Ti): $ nvidia-smi | grep CUDA | NVIDIA-SMI 470.74 Driver Version: 470.74 CUDA Version: ...
Read more >Install CUDA 11.2, cuDNN 8.1.0, PyTorch v1.8.0 (or ... - Medium
1.0 (released on January 26th, 2021), for CUDA 11.0,11.1, and 11.2 from the link above. Then, unzip the embedded folder. tar -zvxf cudnn-11.2- ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@enpasos nice catch! I will apply this change accordingly
I checked out the latest code with #854, compiled it, tested -> problem solved