-
Notifications
You must be signed in to change notification settings - Fork 19
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
Can't run nvidia-smi on 64-bit Ubuntu 13.04 #2
Comments
Hi! Sorry for the delay; I was on vacation until today. Could you show me the output of |
No worries :) Before nvml_fix installation: $ ls -l /usr/lib/libnvidia-ml* Installation: $ sudo make install TARGET_VER=319.32 PREFIX=/usr After: $ ls -l libnvidia-ml* Try to use nvidia-smi: $ nvidia-smi In case it helps, a trace of the relevant syscalls when opening the library: $ strace nvidia-smi 2>&1 | grep -n -A10 nvidia-ml On 08/08/2013 10:13 PM, CFSworks wrote:
|
@mrj10: @CFSworks: I see on the other thread ("New driver version 325.15") that several other people are reporting the same problem. Is it only with 64-bit Linux kernels? I'd really appreciate any help in getting this to work. |
I had the same issue on Ubuntu 12.04 x86_64. Install gcc-4.4 and compile with that version instead. Here's a list of gcc versions I tried that didn't work (with the compiled library I get the "Mismatch in versions between nvidia-smi and NVML." error): And finally the one that made it work as expected: See my other comment on #3 for how to fix this with newer gcc versions. |
OS: Ubuntu 13.04, 64-bit
Kernel: 3.8.0-27
NVIDIA Driver: 319.32
I can build libnvidia-ml.so.1 just fine, but when I install it and try to run nvidia-smi, I get:
Mismatch in versions between nvidia-smi and NVML.
Are you sure you are using nvidia-smi provided with the driver?
Failed to properly shut down NVML: Function Not Found
I have tried:
Curiously, I am able to compile and run http://cfsworks.com/files/downloads/nvml_bug.c successfully.
Any insight would be greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered: