Forum > Linux
SETI MB CUDA for Linux
sunu:
--- Quote from: glennaxl on 08 Dec 2010, 11:47:13 am ---Anyone tried setiathome-CUDA_3.0_6.09.x86_64_vlarkill with cuda32?
--- End quote ---
Supposedly setiathome-CUDA_3.0_6.09.x86_64_vlarkill was done for fermi compatibility but when I tested it, it wasn't working.
Jason G:
--- Quote from: sunu on 15 Dec 2010, 08:08:28 am ---
--- Quote from: glennaxl on 08 Dec 2010, 11:47:13 am ---Anyone tried setiathome-CUDA_3.0_6.09.x86_64_vlarkill with cuda32?
--- End quote ---
Supposedly setiathome-CUDA_3.0_6.09.x86_64_vlarkill was done for fermi compatibility but when I tested it, it wasn't working.
--- End quote ---
Not surprising given the Fermi incompatibilities inherited from 'old stock' Cuda code (all platforms) are fairly specific, complex, and not related directly to Cuda version (apart from needing at least Cuda 3 for fermi binaries)
FYI,
Have got a few other responsibilities sorted today, so should hopefully be able to get some Linux guys on the case soon. No firm timetable yet, for Linux, but wheels are in motion. Will try to provide more info as something more tangible develops.
Jason
sunu:
--- Quote from: Jason G on 15 Dec 2010, 08:19:21 am ---Not surprising given the Fermi incompatibilities inherited from 'old stock' Cuda code (all platforms) are fairly specific, complex, and not related directly to Cuda version (apart from needing at least Cuda 3 for fermi binaries)
--- End quote ---
When I tested it, it produced garbage results in all WUs except VLAR ones. It could run VLAR workunits in fermi GPUs and produce valid results.
--- Quote from: Jason G on 15 Dec 2010, 08:19:21 am ---FYI,
Have got a few other responsibilities sorted today, so should hopefully be able to get some Linux guys on the case soon. No firm timetable yet, for Linux, but wheels are in motion. Will try to provide more info as something more tangible develops.
--- End quote ---
Nice to hear that :)
Jason G:
--- Quote from: sunu on 15 Dec 2010, 08:55:36 am ---When I tested it, it produced garbage results in all WUs except VLAR ones. It could run VLAR workunits in fermi GPUs and produce valid results.
--- End quote ---
LoL, that's kindof amusing but logical by nature of some of the issues. Thanks. That info will help track down & check any issues that might need resolving in an x32f port. Fingers crossed it should be reasonably straightforward from here. Once operational will likely be attempting to keep Linux builds up to date with Windows ones (My primary Platform) , so all going well shouldn't miss out on coming optimisations worked out in the Unit test threads.
Jason
riofl:
i just upgraded my nvidia driver to linux 64 version 260.19.29 and nvidia-settings of the
same version.
since this upgrade my 2nd video card will not release gpu core temps.
gpu0 is a gtx285
gpu1 and 2 is a dual processor gtx295
gpu0 still reads out fine in gkrellm properly but shows 0 for gpu1 and gpu2.
gkrellm is asking for the temps for all gpus according to the process list
when i run the command manually here is what i get:... the number 64 in the gpu0 readout
is the correct temp. the other 2 return a 0:
odyssey bin # nvidia-settings -q [gpu:0]/GPUCoreTemp
Xlib: extension "RANDR" missing on display ":0".
Attribute 'GPUCoreTemp' (odyssey:0[gpu:0]): 64.
'GPUCoreTemp' is an integer attribute.
'GPUCoreTemp' is a read-only attribute.
'GPUCoreTemp' can use the following target types: X Screen, GPU.
odyssey bin # nvidia-settings -q [gpu:2]/GPUCoreTemp
Xlib: extension "RANDR" missing on display ":0".
Attribute 'GPUCoreTemp' (odyssey:0[gpu:2]): 0.
'GPUCoreTemp' is an integer attribute.
'GPUCoreTemp' is a read-only attribute.
'GPUCoreTemp' can use the following target types: X Screen, GPU.
odyssey bin # nvidia-settings -q [gpu:1]/GPUCoreTemp
Xlib: extension "RANDR" missing on display ":0".
Attribute 'GPUCoreTemp' (odyssey:0[gpu:1]): 0.
'GPUCoreTemp' is an integer attribute.
'GPUCoreTemp' is a read-only attribute.
'GPUCoreTemp' can use the following target types: X Screen, GPU.
is this a problem with the new driver?
i also recompiled cuda toolkit 2.3 to be sure everything was synchronized.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version