Edit: The old broken 32bit Linux Cuda app really should be removed from the first post.
[Mod:] Removed outdated build
Quote from: Claggy on 23 Oct 2010, 01:31:52 pmEdit: The old broken 32bit Linux Cuda app really should be removed from the first post.Done:Quote[Mod:] Removed outdated buildWas 64bit OK ? I can put that back if needed, or better yet, put it in a proepr place.
Quote from: sunu on 22 Mar 2009, 03:07:23 pmQuote from: Lysius on 22 Mar 2009, 12:16:09 pmAny news on this?Unfortunately no. All 32bit builds had the same error. If you can, run the 64bit app, else it's better not run CUDA for the time being.Then I think somebody should add a warning to the original post or remove the 32bit app entirely.Unfortunately I only have 32bit linux installed. The last time I tried 64bit I had a sound problem in some 32bit games, so I just reverted to 32bit. Perhaps I should give it a try again, but I don't think this will happen anytime soon.
Quote from: Lysius on 22 Mar 2009, 12:16:09 pmAny news on this?Unfortunately no. All 32bit builds had the same error. If you can, run the 64bit app, else it's better not run CUDA for the time being.
Any news on this?
[Mod:] Removed outdated/bad 32 bit build
If you read the first dozen pages of this thread, you'll see that the original 32bit Linux Cuda app was broken, it might be that the x86, 2.2, vlar-kill app isn't totally reliable eithier,If you can, try swapping to a 64bit OS and use the 64bit app instead.
ldd setiathome-CUDA_3.0_6.09.x86_64_vlarkill linux-vdso.so.1 => (0x00007ffff6fff000) libcufft.so.3 => /usr/local/cuda/lib64/libcufft.so.3 (0x00007fa18cf7d000) libcuda.so.1 => not found libcudart.so.3 => /usr/local/cuda/lib64/libcudart.so.3 (0x00007fa18cd2f000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007fa18ca29000) libm.so.6 => /lib/libm.so.6 (0x00007fa18c7a6000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007fa18c588000) libc.so.6 => /lib/libc.so.6 (0x00007fa18c205000) /lib64/ld-linux-x86-64.so.2 (0x00007fa18ed44000) libdl.so.2 => /lib/libdl.so.2 (0x00007fa18c001000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fa18bdea000) librt.so.1 => /lib/librt.so.1 (0x00007fa18bbe2000)
Anyone tried setiathome-CUDA_3.0_6.09.x86_64_vlarkill with cuda32?
Quote from: glennaxl on 08 Dec 2010, 11:47:13 amAnyone tried setiathome-CUDA_3.0_6.09.x86_64_vlarkill with cuda32?Supposedly setiathome-CUDA_3.0_6.09.x86_64_vlarkill was done for fermi compatibility but when I tested it, it wasn't working.
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.
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.
what i cannot understand is why then does gpu0 still work under the old syntax?