Forum > Linux
SETI MB CUDA for Linux
b0b3r:
ls -al /dev/nv*
crw-rw-rw- 1 root root 195, 0 Jul 12 20:01 /dev/nvidia0
crw-rw-rw- 1 root root 195, 1 Jul 12 20:01 /dev/nvidia1
crw-rw-rw- 1 root root 195, 2 Jul 12 20:01 /dev/nvidia2
crw-rw-rw- 1 root root 195, 255 Jul 12 20:01 /dev/nvidiactl
sunu:
Your system sees three devices.
In your host 5018683, boinc doesn't even see your graphics cards. Are you sure that you have intalled them correctly?
Also in both of your hosts upgrade boinc. 6.4.5 is too old.
pp:
--- Quote from: sunu on 11 Jul 2009, 03:12:31 pm ---
--- Quote from: Richard Haselgrove on 11 Jul 2009, 01:44:56 pm ---Came across an interesting error message in task 1294937260 while researching something else.
--- Quote ---SETI@home MB CUDA 608 Linux 64bit SM 1.0 - r06 by Crunch3r :p
Error: API mismatch: the NVIDIA kernel module has version 180.29,
but this NVIDIA driver component has version 180.60. Please make
sure that the kernel module and all NVIDIA driver components
have the same version.
setiathome_CUDA: Found 1 CUDA device(s):
Cuda error 'cudaGetDeviceProperties( &cDevProp, i )' in file './cudaAcceleration.cu' in line 138 : initialization error.
--- End quote ---
Something to watch for when fiddling about with Linux drivers and modules.
The anonymous owner of host 5011059 seems to be having a real problem getting his or her GTX 295 running under gentoo.
--- End quote ---
He hasn't installed the NVIDIA drivers properly.
--- End quote ---
Well, actually he has. But after installation of the new package he neither rebooted nor loaded the new module. He's still running his system with the old version in memory. Easy mistake to do in Gentoo - been there done that. :)
sunu:
--- Quote from: Raistmer on 12 Jul 2009, 10:10:04 am ---Not sure it exist in linux. It's not GPU feature, it's windows feature - it will kill driver (Vista) with more than 2 secs of "no answer" from it.
Don't know if Linux kerner implements such watchdog machanism or not.
GPUs that don't output video don't subject of this "driver hung" check and can run long kernels. That's why surely not all that work OK on Tesla will work OK on user's GPUs (even if newly GPUs slightly faster than first released Teslas IMHO)
--- End quote ---
Raistmer do you mean something like this? From cuda 2.2 release notes:
o Individual GPU program launches are limited to a run time
of less than 5 seconds on a GPU with a display attached.
Exceeding this time limit causes a launch failure reported
through the CUDA driver or the CUDA runtime. GPUs without
a display attached are not subject to the 5 second run time
restriction. For this reason it is recommended that CUDA is
run on a GPU that is NOT attached to an X display.
So yes, it also exists in linux.
@b0b3r: The error you posted above with the "unspecified launch failure" messages might be because of that.
Curiously I've crunched tens of thousands of workunits with my GPU that also runs X with ever seeing that kind of error.
Jason G:
--- Quote from: sunu on 12 Jul 2009, 03:03:43 pm ---....Individual GPU program launches are limited to a run time
of less than 5 seconds on a GPU with a display attached.....
--- End quote ---
Yes. In embedded microcontroller system terminology, that's called a "Watchdog Timer". Crazy people program GPUs to take longer than that, Lunatics try to fix it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version