Forum > Linux
SETI MB CUDA for Linux
sunu:
--- Quote from: pp on 11 Jun 2009, 04:57:57 am ---Yes, this is an SSE3 capable Athlon64. My nvidia drivers are 180.60 and if you know what the boinc client are looking for to identify them, I can inform the maintainer.
--- End quote ---
It doesn't matter much what boinc shows. Get the newer nvidia driver if you can.
--- Quote from: pp on 11 Jun 2009, 04:57:57 am ---I compiled the trunk version of boinc successfully yesterday but I'll have to go through that Makefile in detail before I swap to it.
--- End quote ---
Why compile? Use the ready packages from the links I gave you above.
--- Quote from: pp on 11 Jun 2009, 04:57:57 am ---The app_info.xml that came with the CUDA client contains several identical sections but with different version numbers. Aren't they redundant?
# grep version_num app_info.xml
<version_num>528</version_num>
<version_num>603</version_num>
<version_num>605</version_num>
<version_num>606</version_num>
<version_num>608</version_num>
--- End quote ---
Some of them maybe, but leave them as they are. It doesn't matter.
--- Quote from: pp on 11 Jun 2009, 04:57:57 am ---I downloaded the SSE3-capable version of Astropulse v5 and there's a new app_info.xml included with it. Can I just add that info to my current app_info.xml to have boinc use both programs?
--- End quote ---
Get the 64bit one if you haven't already. It's much faster than the 32bit one. Yes add the info to your current app_info.xml.
--- Quote from: pp on 11 Jun 2009, 04:57:57 am ---To have it use two instances on my dual core, I assume that's controlled by the "100% CPU" setting in my S@H profile?
--- End quote ---
That's a bit more complicated. If you want to run 2+1 (that is 2 astropulse in your cpu and 1 multibeam in your gpu) you'll need to get the 185.18.14 nvidia driver just to begin with. More tinkering will be needed but we are here to help. If you stay with your current 180.60 you can only use 1+1 (1cpu + 1gpu).
pp:
Thanks sunu. Plenty of valuable information to work with there. I'll see if I can try to isolate the cpu hog first before I try Astropulse.
About the compilation... that's what working with Gentoo for a few years does to you. I didn't even consider the precompiled binary... ;D Well, no harm done, it was a fun experience...
sunu:
--- Quote from: pp on 11 Jun 2009, 12:46:26 pm ---I'll see if I can try to isolate the cpu hog first before I try Astropulse.
--- End quote ---
What cpu hog?
Richard Haselgrove:
Didn't early Linux CUDA builds take 100% CPU? I though that was cured by the 185 driver.
pp:
--- Quote from: sunu on 11 Jun 2009, 01:14:39 pm ---
--- Quote from: pp on 11 Jun 2009, 12:46:26 pm ---I'll see if I can try to isolate the cpu hog first before I try Astropulse.
--- End quote ---
What cpu hog?
--- End quote ---
I was referring to the behaviour dtiger reported last in his post a few pages back in this thread: http://lunatics.kwsn.net/linux/seti-mb-cuda-for-linux.msg14847.html#msg14847
setiathome-CUDA is using 100% of one of my my regular CPU's cores even though no actual work is done there. Richard's idea about nvidia-drivers is interesting. Was that ever confirmed? I actually found this forum looking for a solution to that problem...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version