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
require 'cudnn' error #279
Comments
updating cutorch will fix this. |
I've got last version of cutorch and cudnn.torch (cudnn version 5, CUDA 8.0), lua 5.2, but I've got the same bug.
|
hi @v1993 . this error is definitely because of a non updated cutorch. Maybe what is happening is that you have another cutorch on your system somewhere you dont expect. |
Now works perfectly. |
Works for me |
Hi, |
You need to update cutorch |
I had made a full torch install after using clean-old.sh to clean all the old versions. When I run the command: luajit -lcutorch When I install cutorch with this command: luarocks install cutorch 1.0-0 |_ | | | JIT: ON SSE2 SSE3 SSE4.1 fold cse dce fwd dse narrow loop abc sink fuse ##################################################### now I get the error: after removing cudnn: luarocks remove cudnn I had installed it with: now it works, but it is not stable. |
do you have to use cutorch 1.0-0? Your problem would be solved if you used latest cutorch (luarocks install cutorch). |
i had tried to install the latest versions, like this: luarocks install cutorch Then I get an error from cutorch |
@shimen, you need to check your luarocks config if it gets cutorch from standard place. luarocks install cutorch |
I have the same problem. I could install neither cutorch nor cudnn. |
hello, and still the error so , how to update cutorch to latest version ??? More, my error: |
@soumith How to upgrade the cutorch? thanks |
Hi all.
When I run
require cudnn
(in one of my files load_caffe.lua, line 3), this kind of error is raised:I've installed cuDNN 7.5, luarocks install'ed all nn, cudnn, torch again, but problem's not solved.
What do you think is the matter?
Thank you.
The text was updated successfully, but these errors were encountered: