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
ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory #15604
Comments
I think this is due to the fact that you have CUDA 9.1 and not 9.0, I am facing exactly the same issue. |
@Timonzimm I know and I think the whole issue is this f** naming libcublas.so.xxx that nvidia puts. This inherently is mismatch on linux systems whenever that number changes, so since it can not find the exact matches then it thinks the file doesn't exist and throws the error. |
I think you should use symbol link from ''cuda/'' to ''cuda/9.1",or your cuda version is too new to tensorflow master branch |
@burui11087 I completely forgot about symlinking. Thanks for reminding me. |
I also occur the exactly same problem with kirk86. For me, I installed cuda toolkit 8.0, and cudnn 5.1. |
For using nightlies, you have to have CUDA 9.0 and cudnn 7 installed. |
@Timonzimm I am facing the same issue. Have you figured it out? |
I have 8.0, 9.0, 9.1 installed + cudnn versions which seem specific to each. The sym linking didn't work from the 9.1 libs. I suspect that sometimes the symlink in the LD_LIBRARY_PATH doesn't work either when I switch versions on the /usr/local/cuda link. I ended up just doing it the low tech way to get the libraries loaded into my java program until I can figure out a cleaner way to handle the paths inside of Eclipse.
. |
@asimshankar Would like to know that in your above comment you mean that we should downgrade cuda to 9.0 and tensorflow 1.5 doesn't work with cuda 9.1 ? You have closed this issue but its not clear what is the correct action that we should take! Note: I also have cuda 9.1 installed instead of cuda 9.0. |
Just FYI, I have both installed. Building from scratch will work w/ either, but the nightly binaries use 9.0. |
@AwasthiMaddy - Yes TensorFlow 1.5 release binaries are built for CUDA 9. |
Have you solved it ? This problem is caused tensorflow-gpu-1.5 required cuda 9.0 ,so you should install tensorflow-gpu-1.4. And rember uninstall tensorflow-gpu-1.5. Please use this"pip install --upgrade tensorflow-gpu==1.4" |
@aipeteryao - Thank you. |
Someone needs to fix the https://www.tensorflow.org/install/install_linux page if this is true, I just followed its instructions exactly, and tells you to install CUDA 8.0 (specifically, not "latest CUDA"). Then as soon as you're done, you get this error (it is looking for cublas 9.0, which, from what I can read here, would not have worked either, as CUDA 9.1 is the default you get from NVIDIA). Either the webpage instructions should work with the default latest of everything, or it should tell you explicitly to install tensorflow-gpu-1.4 (for example) and not tensorflow-gpu.. |
Seconding bwesons's comment. I have CUDA 8.0 and Tensorflow 1.3. I followed the current install instructions for TF 1.5 (GPU, ubuntu, virtualenv) and it breaks as described above. Reverting to TF 1.3 until this is resolved. |
@aipeteryao This fixed it, thanks! I ended up uninstalling the latest version and installing 1.4, in my virtualenv.
The install page for Ubuntu should be updated: https://www.tensorflow.org/install/install_linux |
In fact, we should view the official document of tensorflow ,it give tensorflow‘s envirment(include python,gcc,cuda,cudnn,an so on). |
@bwesen yes,you were right .My computer installed CUDA 8.0,cudnn 6.0 ,tensorflow 1.4. |
I think this issue should still be open. @bwesen's comment is correct. The docs tell you to install Cuda 8.0 and use pinging @asimshankar |
I have the same issue (with cuda 9.1 + tensorflow 1.5). I think to resolve it, one option is that to downgrade cuda to 9.0. The other option would be to downgrade both cuda to 8.0 and tensorflow to 1.4. If you have already installed cuda 8.0, you only need to modify |
I'm getting this issue (Cuda 9.1.85, cuDNN 7.05) Tried with tensorflow 1.5, it broke. Uninstalled, installed 1.4 with |
@DylanDmitri 1.5 expects Cuda 9.0, not 9.1 Have you tried with Cuda 9.0 drivers? |
@DylanDmitri @mkaze You need Cuda 9.0. Also, for anyone having trouble installing requirements, I suggest double checking your cuDNN installation. The .deb file didn't work for me because it did not copy files to the right place. I had to use the .tgz file and manually copy files according to nVidia's directions in order to get a working installation. |
Why not just install cuda-9-0?
|
I have installed Cuda 10 and the latest version of Tensor Flow, but I have received |
Could you tell us the OS version and the exact command you issued to "downgrade"? |
@sphinxs, in my opinion you have two ways: a) to recompile the python wheel locally so it points to the installed cuda version or b) install cuda-9.0 as I did for my 18.04 installation and it's still working after months. |
the man has got a point. TF CAN be compiled to work with more modern CUDA versions... why not just offer that to most people with a |
I am sick of it!!!! |
This comment does not add anything to the issue. Also no one forces anyone to use TF, but If you really need to and can't get pip packages working, why not to build it yourself? That's what I ended up doing at some point. I saw there are also community supported builds here |
This is an issue page. Please, state your issues so they can be fixed, or, even better, help fixing them. |
@raphaunix may I ask where this chart comes from? |
I got Tensorflow 1.11.0 working by running the following commands:
|
I have find the reason is ldconf, ldconfig is a dynamic link library management command whose purpose is to allow the dynamic link library to be usedby the system. The default ldconf only search /lib and /usr/lib, as well as the library file under the directory listed in the configuration file /etc/ld. so. conf. so all of this is caused by the dynamic library of CUDA in the installed CUDA path such as : /path/cuda-9.0/lib64 or /path/cuda-9.0/lib. (for example my CUDA is installed in /usr/local/cuda-9.0) 1.if you install the CUDA manual, then after install, you should add the path of cuda/lib64 to /etc/ld.so.conf file if you install the CUDA by command such as 'dpkg -i cuda-repo-ubuntu1604_9.0.176-1_amd64.deb' or others, it may add the cuda lib path to the /etc/ld.so.conf automatically . but to be on the safe side, check the /etc/ld.so.conf and see if the path add to it . |
@jabalazs Instead of |
I found that my runtime on colab was not using GPU that's how come I got my error |
Good solution @dodler ! but I think you are missing the commands to make this great advice easy to follow through xD.
Happy coding! |
I faced this same error trying to use Thundersvm to speedup NuSVR with GPUs on Google Colab.
|
solves my problem. |
|
This solution worked for me. Thanks for this solution. |
My TensorFlow and TensorFlow-gpu are 1.12.0 and CUDA 11.0 and I am facing this issue -
Someone please help. I have been struggling for days! :'( |
@meghbhalerao I guess your problem's cause is tensorflow and cuda version mismatch. Check compatible versions here. Have you tried to installed different cuda or tensorflow versions? |
Trying to install thundersvm on Colab instance, hit this error:
|
I installed tf-nightly build and I get the following error on import of tensorflow.
ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory
.If I check for cuda 9, I get the following:
I that due to a name mismatch.
libcublas.so.9.0 =! libcublas.so.9.1
? And if so how can we overcome this?The text was updated successfully, but these errors were encountered: