-
Notifications
You must be signed in to change notification settings - Fork 644
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
undefined symbol: cudaRuntimeGetVersion Error #85
Comments
Was able to workaround this with |
I have the exact same issue, but in my case the workaround does not seem to work, unfortunately. |
I had this error and was stumped by it until I realised that my CUDA toolkit had been installed ~incorrectly and was in a place where |
Following along from the following StackOverflow, this seems to be a solution to ensuring conda is using the 'right
And based on this StackOverflow + a little extra digging, I found that the reason it wasn't able to find my
|
Do you think there is a workaround for those that are using |
@RamonBeast Just stumbled across this page, seems like it should probably work for you?
And for reference, here is the
@RamonBeast I haven't specifically tried it myself yet, but it could well be the case |
In case it's helpful to people, here are the lists of the various packages that are installed for each of
|
What fixed this for me was:
in ~/.bashrc along with ensuring libcudart.so exists there using: sudo ln -s /usr/lib/x86_64-linux-gnu/libcudart.so.11.0 /usr/lib/x86_64-linux-gnu/libcudart.so |
Thank you, everyone, for contributing to the discussion! It is a strange error because it indicates that For now, I added an error message for cases like this and added the path to I am going to release a new version tomorrow. If you can reproduce the error then and post the additional information printed in the CUDA SETUP error trace, that would be very helpful! |
FWIW @0xdevalias comment solved it for me, there was one oddity though in case someone else runs into it. If you run a script in your conda env with bitsandbytes or a jupyter lab it works. If you exit the environment but have a kernel for that environment it doesn't work with the kernel in your default env. I believe it's because the cuda libraries are installed in your specific conda env which is why it's so finicky. Not sure if full environment spec would be easier to manage here.
... |
This doesn't solve the error on my side. I updated
But I still get
Unfortunately, I cannot use Conda. |
I am also using virtualenv on and Arch based system, and none of the solutions related to virtualenv have worked for me. I have Are there more suggestions for this issue for virtualenv? |
For ubuntu 22.04, this worked but changed the command to export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu |
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. |
Device setup:
Code:
StackTrace:
The text was updated successfully, but these errors were encountered: