Forum > Linux
SETI MB CUDA for Linux
Raistmer:
Apparently BOINC can't find 2 required libraries.
try to put these 3 libs with executable. Not sure Linux checks that place in attempt to load shared libs though...
riofl:
easiest way is to simply copy everything from the sdk lib dir into /var/lib/boinc and also into the project directory /var/lib/boinc/projects/<projectname>/
also depending on what your distro requires, add the projectname directory path to /etc/ld.so.conf or to whatever master file your distro says to and re-run ldconfig or env-update or whatever you have to scan the lib locations.
it will magically start working. my seti project dir contains these lib files:
lrwxrwxrwx 1 root wheel 17 2009-07-17 13:05 libcublasemu.so -> libcublasemu.so.2
lrwxrwxrwx 1 root wheel 19 2009-07-17 13:05 libcublasemu.so.2 -> libcublasemu.so.2.2
-rwxr-xr-x 1 root wheel 4704664 2009-07-09 08:00 libcublasemu.so.2.2
lrwxrwxrwx 1 root wheel 14 2009-07-17 13:06 libcublas.so -> libcublas.so.2
lrwxrwxrwx 1 root wheel 16 2009-07-17 13:05 libcublas.so.2 -> libcublas.so.2.2
-rwxr-xr-x 1 root wheel 18643744 2009-07-09 08:00 libcublas.so.2.2
lrwxrwxrwx 1 root wheel 14 2009-07-17 13:06 libcudart.so -> libcudart.so.2
lrwxrwxrwx 1 root wheel 16 2009-07-17 13:05 libcudart.so.2 -> libcudart.so.2.2
-rwxr-xr-x 1 root wheel 261472 2009-07-09 08:00 libcudart.so.2.2
lrwxrwxrwx 1 root wheel 16 2009-07-17 13:06 libcufftemu.so -> libcufftemu.so.2
lrwxrwxrwx 1 root wheel 18 2009-07-17 13:05 libcufftemu.so.2 -> libcufftemu.so.2.2
-rwxr-xr-x 1 root wheel 273064 2009-07-09 08:00 libcufftemu.so.2.2
lrwxrwxrwx 1 root wheel 13 2009-07-17 13:06 libcufft.so -> libcufft.so.2
lrwxrwxrwx 1 root wheel 15 2009-07-17 13:06 libcufft.so.2 -> libcufft.so.2.2
-rwxr-xr-x 1 root wheel 1153440 2009-07-09 08:00 libcufft.so.2.2
if you are not using the 2.2 cuda environment you will not have some of these files but no matter. as long as all files from the sdk lib dir are copied in it will work.
riofl:
--- Quote from: Kunin on 19 Jul 2009, 07:17:51 am ---I can confirm the above, I tried it with 6.6.36, 6.6.20 and 6.4.5 and ONLY 6.4.5 worked correctly (one WU to one GPU). Both 6.6.20 and 6.6.36 put both on the same device, and 6.6.36 I had to do funky things to get it working (had to install 6.6.20, run it, shut down, install 6.6.36 without removing anything, start 6.6.36... and repeat that any time I shut it down, VERY odd).
It could just be something with our OS, Ubuntu 8.10 x64, but for now 6.4.5 works... now I just need to find some way to get the CPU to do some work.
--- End quote ---
i'm using the AK optimized MB app for my cpus and with this plus the cuda app in my app_info.xml my cpus and gpus are all happily crunching away. i don't know where it would be on this site but if it is not here i can give you a link to crunch3r's download page where i got mine. my app name is
AK_V8_linux64_ssse3
they are highly optimized for the processor so be sure you get the correct one. a "cat /proc/cpuinfo" will get you the processor capabilities.
sunu:
After a catastrophic GPU failure (probably something burned inside my GTX280 :D) that left me offline for a week, I'm back up and slowly catching up.
Since many linux users, lately, had problems with multi-GPU configs, I decided my next card would be a GTX 295 so I have a proper testbed to research things further. My various tweaks and experiments with xorg.conf or different video drivers didn't have any effect. Boinc still used only one of the two GPUs.
Then I started with the latest boinc (6.6.37) and moved backwards to see if I could find a boinc version that worked as expected.
I've found that the last boinc that can use both GPUs properly is 6.6.11. Boinc 6.6.12 doesn't even assign --device X flags to cuda instances. It just launches two of them and they (probably automatically) go straight to the first GPU. The next boinc linux release (6.6.15) corrects the missing --device X flags but it does this wrongly, it assigns both of them to --device 0.
So something in the transition 6.6.11 --> 6.6.12 --> 6.6.15 broke and stayed broken ever since with all subsequent boinc releases.
I'm using 6.6.11 for a few hours now with no apparent problems or bugs. Direct link http://boincdl.ssl.berkeley.edu/dl/boinc_6.6.11_x86_64-pc-linux-gnu.sh .
If someone remembers any showstopper bugs with 6.6.11 please tell.
Richard Haselgrove:
--- Quote from: sunu on 22 Jul 2009, 08:40:46 am ---
If someone remembers any showstopper bugs with 6.6.11 please tell.
--- End quote ---
That was just before the bombshell about not supporting app_info.xml properly. v6.6.12 doesn't aupport app_info, v6.6.14 started to put it back together (there was no .13). So you may have problems getting v6.6.11 working with both CUDA and an optimised CPU app, or indeed Astropulse.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version