Running SETI@home on an nVidia Fermi GPU

Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 15 · Next

AuthorMessage
Profile Todd Hebert
Volunteer tester
Avatar

Send message
Joined: 16 Jun 00
Posts: 648
Credit: 228,292,957
RAC: 0
United States
Message 1003654 - Posted: 12 Jun 2010, 16:22:45 UTC

When I tried it out the performance actually dropped by a significant margin even while having better GPU utilization at 100% instead of the normal average of 72%. But my tests were on alpha and beta editions of the app. I haven't changed the app to the latest version since I have WU's still and at the moment they are hard to come by.

Todd
ID: 1003654 · Report as offensive
Profile RottenMutt
Avatar

Send message
Joined: 15 Mar 01
Posts: 1011
Credit: 230,314,058
RAC: 0
United States
Message 1003753 - Posted: 13 Jun 2010, 19:10:00 UTC - in response to Message 997948.  

Re-posting, by popular request, from CUDA MB V12b rebuild supposed to work with Fermi GPUs.

This note is aimed at people running optimised apps already. That's essential: you will need to modify an existing app_info.xml file.

This isn't the place to go into the whole science of installing optimised applications by hand, but in brief: stop BOINC first, keep backups, use a simple ANSI-mode text editor. If in doubt, read the BOINC FAQ version - fuller, and can be updated in the future.

You will need to add a whole new <app_version> section:

    <app_version>
        <app_name>setiathome_enhanced</app_name>
    	<version_num>610</version_num>
    	<avg_ncpus>0.200000</avg_ncpus>
    	<max_ncpus>0.200000</max_ncpus>
    	<plan_class>cuda_fermi</plan_class>
	<file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
            <main_program/>
	</file_ref>
	<file_ref>
            <file_name>cudart32_30_14.dll</file_name>
	</file_ref>
   	<file_ref>
            <file_name>cufft32_30_14.dll</file_name>
   	</file_ref>
	<file_ref>
            <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
   	</file_ref>
	<coproc>
            <type>CUDA</type>
            <count>1</count>
	</coproc>
    </app_version>

You'll also have to add <file_info> sections for any file you're not already using. You may have libfftw3f-3-1-1a_upx.dll already, in which case you don't need to add it again: but the full set is

    <file_info>
        <name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart32_30_14.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cufft32_30_14.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-1-1a_upx.dll</name>
        <executable/>
    </file_info>

Finally, you'll need the files themselves: download from

http://boinc2.ssl.berkeley.edu/beta/download/setiathome_6.10_windows_intelx86__cuda_fermi.exe (2,476 KB)
http://boinc2.ssl.berkeley.edu/beta/download/cudart32_30_14.dll (280 KB)
http://boinc2.ssl.berkeley.edu/beta/download/cufft32_30_14.dll (12,188 KB)
http://boinc2.ssl.berkeley.edu/beta/download/libfftw3f-3-1-1a_upx.dll (439 KB)

Make sure the file sizes are correct - sometimes these manual downloads crash out early.


so run the lunatic 64bit installer and then add the above to the app_info.xml file, leaving all the old 6.08 v12 stuff, what about the platform stuff?
ID: 1003753 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1003760 - Posted: 13 Jun 2010, 19:21:05 UTC - in response to Message 1003753.  
Last modified: 13 Jun 2010, 19:22:36 UTC

so run the lunatic 64bit installer and then add the above to the app_info.xml file, leaving all the old 6.08 v12 stuff, what about the platform stuff?

I honestly don't know - I don't have a 64-bit OS here to test with.

My best suggestion - run the lunatics 64-bit installer as you suggest, including for the time being the Cuda23 application - but don't let it actually run on a Fermi, you won't get valid results.

Then, inspect the app_info.xml file the installer has created for you, and adjust it to match this sample - change the executable name, and the two cuda DLL names, wherever they occur. Leave the platform tag(s) as they were made by the installer. Edit: Remember to download the new files as well!

Jason is working on a new installer, to incorporate a genuinely optimised (though not yet optimal) Fermi application - hopefully the apps can go to beta testing in the next couple of days (if the project is up), and the installer will follow after that.
ID: 1003760 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1003765 - Posted: 13 Jun 2010, 19:28:20 UTC - in response to Message 1003753.  

... leaving all the old 6.08 v12 stuff ...

No, don't do that. The 6.08 codebase won't run on a Fermi.

I tried, and got Beta task 7964564:

Cuda error 'cudaMemcpyToSymbol(cudaAcc_GaussFit_settings, (void*) &settings, sizeof(settings))' 
in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_gaussfit.cu' in line 454 : invalid device symbol.
ID: 1003765 · Report as offensive
Profile RottenMutt
Avatar

Send message
Joined: 15 Mar 01
Posts: 1011
Credit: 230,314,058
RAC: 0
United States
Message 1003769 - Posted: 13 Jun 2010, 19:42:40 UTC
Last modified: 13 Jun 2010, 20:04:43 UTC

Is this correct? it seems to be working... i took out the v6.08 stuff
<app_info> 
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AK_v8b_win_x64_SSSE3x.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSSE3x.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.05r409_SSE.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>    
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>libfftw3f-3-1-1a_upx.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart32_30_14.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cufft32_30_14.dll</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.200000</avg_ncpus>
        <max_ncpus>0.200000</max_ncpus>
        <plan_class>cuda_fermi</plan_class>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>cudart32_30_14.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_30_14.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
        </file_ref>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>0.200000</avg_ncpus>
        <max_ncpus>0.200000</max_ncpus>
        <plan_class>cuda_fermi</plan_class>
        <file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>cudart32_30_14.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>cufft32_30_14.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
        </file_ref>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
    </app_version>
</app_info> 

ID: 1003769 · Report as offensive
Profile perryjay
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3377
Credit: 20,676,751
RAC: 0
United States
Message 1003772 - Posted: 13 Jun 2010, 19:53:38 UTC - in response to Message 1003765.  

RottenMutt, Richard said this...


... leaving all the old 6.08 v12 stuff ...

No, don't do that. The 6.08 codebase won't run on a Fermi.

I tried, and got Beta task 7964564:

Cuda error 'cudaMemcpyToSymbol(cudaAcc_GaussFit_settings, (void*) &settings, sizeof(settings))' 
in file 'c:/sw/gpgpu/seti/seti_boinc/client/cuda/cudaAcc_gaussfit.cu' in line 454 : invalid device symbol.



As for not reporting or requesting tasks, do you have a bunch of uploads waiting? This could keep you from downloading and you've probably already reported everything that had uploaded prior to this mess we are in now.



PROUD MEMBER OF Team Starfire World BOINC
ID: 1003772 · Report as offensive
Profile RottenMutt
Avatar

Send message
Joined: 15 Mar 01
Posts: 1011
Credit: 230,314,058
RAC: 0
United States
Message 1003783 - Posted: 13 Jun 2010, 20:18:54 UTC - in response to Message 1003772.  

i rmvd the 6.08 stuff.

all my completion time estimates are way off, 11.5 hours for a fermi wu, 13.5 for a MB enhanced 6.03, 150 hours for a astropulse...
ID: 1003783 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1003785 - Posted: 13 Jun 2010, 20:21:15 UTC - in response to Message 1003783.  

i rmvd the 6.08 stuff.

all my completion time estimates are way off, 11.5 hours for a fermi wu, 13.5 for a MB enhanced 6.03, 150 hours for a astropulse...

I assume you haven't put in the Flops calculations yet. Message 1002997, this thread.
ID: 1003785 · Report as offensive
TheFreshPrince a.k.a. BlueTooth76
Avatar

Send message
Joined: 4 Jun 99
Posts: 210
Credit: 10,315,944
RAC: 0
Netherlands
Message 1003840 - Posted: 13 Jun 2010, 22:58:34 UTC - in response to Message 1003510.  

I have seen a few people stating that they are running 2 tasks on their gtx470&480's - why? When I look at gpu usage, I typically see 69% usage peaking in the 90's for short bursts. Is there any benefit to doing this, would it actually work out any quicker as Im thinking that it might crunch 2 units but would do so at half the speed? Am I right?


1 WU on my GTX 470 took 12 minutes average to process.
2 WU's on my GTX 470 take 16 minutes average to process.
So my output is much higher with 2 tasks on this card.

On my 9800 GTX it was actually a bit slower to run 2 tasks.
ID: 1003840 · Report as offensive
Profile [AF>EDLS] Polynesia
Volunteer tester
Avatar

Send message
Joined: 1 Apr 09
Posts: 54
Credit: 5,361,172
RAC: 0
France
Message 1003984 - Posted: 14 Jun 2010, 12:04:25 UTC - in response to Message 1003840.  

I would have liked to know if all that were only for the gtx 4xx? Because I have only a gtx 260? thank you


Alliance Francophone
ID: 1003984 · Report as offensive
Profile perryjay
Volunteer tester
Avatar

Send message
Joined: 20 Aug 02
Posts: 3377
Credit: 20,676,751
RAC: 0
United States
Message 1004002 - Posted: 14 Jun 2010, 13:06:02 UTC - in response to Message 1003984.  

Yes, most of this was triggered by the new 4xx series Fermi's. Many people ran out and bought them as soon as they hit the market and set them to work on SETI. The problem arose when they tried to do regular GPU tasks with them which don't run on the Fermi cards. They immediately started giving -9 overflow results. When paired with a regular CPU or GPU giving good results they would cause a resend and often, if the third wingman had a 4xx card would validate the work as -9 overflow and discard the good result.


PROUD MEMBER OF Team Starfire World BOINC
ID: 1004002 · Report as offensive
Profile MadMaC
Volunteer tester
Avatar

Send message
Joined: 4 Apr 01
Posts: 201
Credit: 47,158,217
RAC: 0
United Kingdom
Message 1004132 - Posted: 14 Jun 2010, 19:36:25 UTC - in response to Message 1002997.  

Flops estimating for Fermi

In the middle of all the error messages last night, somebody asked about getting the running time estimates for the various applications into balance. This was my initial background explanation:

My figures ended up at:

CPU:	    3,826,762,478
GPU:	   57,462,450,464

or, in multiplier terms,

CPU: multiply <p_fpops> by 1.45
GPU: divide peak GFlops by 18.95

That's a rather narrower spread than we're used to with the earlier cards, which I think is perhaps accounted for by:




Ok, so I have had a go at this, can someone confirm my app_info is correct as Im not sure I have put the flops bit in the right place? The fermi section of my app_info is posted below...

<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
<executable/>
<flops>57462450464</flops>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>

<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>0.200000</max_ncpus>
<flops>57462450464</flops>
<plan_class>cuda_fermi</plan_class>
<file_ref>
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>
<file_info>
<name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_30_14.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<avg_ncpus>0.200000</avg_ncpus>
<max_ncpus>0.200000</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<file_ref>
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_30_14.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

ID: 1004132 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1004141 - Posted: 14 Jun 2010, 20:14:24 UTC - in response to Message 1004132.  

MadMac, try this Fermi section:

<app>
<name>setiathome_enhanced</name>
</app>
<file_info> 
<name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name> 
<executable/> 
</file_info> 
<file_info> 
<name>cudart32_30_14.dll</name> 
<executable/> 
</file_info> 
<file_info> 
<name>cufft32_30_14.dll</name> 
<executable/> 
</file_info> 
<file_info> 
<name>libfftw3f-3-1-1a_upx.dll</name> 
<executable/> 
</file_info>

<app_version> 
<app_name>setiathome_enhanced</app_name> 
<version_num>610</version_num> 
<avg_ncpus>0.200000</avg_ncpus> 
<max_ncpus>0.200000</max_ncpus>
<platform>windows_intelx86</platform>
<flops>57462450464</flops> 
<plan_class>cuda_fermi</plan_class> 
<file_ref> 
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name> 
<main_program/> 
</file_ref> 
<file_ref> 
<file_name>cudart32_30_14.dll</file_name> 
</file_ref> 
<file_ref> 
<file_name>cufft32_30_14.dll</file_name> 
</file_ref> 
<file_ref> 
<file_name>libfftw3f-3-1-1a_upx.dll</file_name> 
</file_ref> 
<coproc> 
<type>CUDA</type> 
<count>1</count> 
</coproc> 
</app_version>

<app_version> 
<app_name>setiathome_enhanced</app_name> 
<version_num>610</version_num> 
<avg_ncpus>0.200000</avg_ncpus> 
<max_ncpus>0.200000</max_ncpus>
<platform>windows_x86_64</platform>
<flops>57462450464</flops> 
<plan_class>cuda_fermi</plan_class> 
<file_ref> 
<file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name> 
<main_program/> 
</file_ref> 
<file_ref> 
<file_name>cudart32_30_14.dll</file_name> 
</file_ref> 
<file_ref> 
<file_name>cufft32_30_14.dll</file_name> 
</file_ref> 
<file_ref> 
<file_name>libfftw3f-3-1-1a_upx.dll</file_name> 
</file_ref> 
<coproc> 
<type>CUDA</type> 
<count>1</count> 
</coproc> 
</app_version>

</app_info>


Claggy
ID: 1004141 · Report as offensive
Profile MadMaC
Volunteer tester
Avatar

Send message
Joined: 4 Apr 01
Posts: 201
Credit: 47,158,217
RAC: 0
United Kingdom
Message 1004146 - Posted: 14 Jun 2010, 20:19:11 UTC - in response to Message 1004141.  

Thank you Claggy - appreciated..
ID: 1004146 · Report as offensive
TheFreshPrince a.k.a. BlueTooth76
Avatar

Send message
Joined: 4 Jun 99
Posts: 210
Credit: 10,315,944
RAC: 0
Netherlands
Message 1004165 - Posted: 14 Jun 2010, 21:01:38 UTC
Last modified: 14 Jun 2010, 21:05:27 UTC

I got work for my CPU but still nothing for the Fermi...
Still the same message...

14-6-2010 22:56:25 SETI@home Message from server: No work sent
14-6-2010 22:56:25 SETI@home Message from server: Your app_info.xml file doesn't have a usable version of SETI@home Enhanced.
14-6-2010 22:56:25 SETI@home Message from server: (reached daily quota of 100 tasks)

I even made a backup, detached, attached and still got nothing because I reached the "daily quota of 100 tasks". I only got about 20 today so where are the other 80 WU's?...

Is there any hope I'll get work for my Fermi (soon)?
It worked perfect for 1 day (with the same app_info.xml)... And now it's just sitting there... Waiting...

I installed Boinc 2 weeks ago to give it a try (again) but for some reason Seti always crashes when I try to join after a period of being inactive...

Okay, I'm a bit frustrated because I can't test my new toy...
Hope you forgive me for that :P
ID: 1004165 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65061
Credit: 55,293,173
RAC: 49
United States
Message 1004178 - Posted: 14 Jun 2010, 21:20:42 UTC - in response to Message 1004165.  

I got work for my CPU but still nothing for the Fermi...
Still the same message...

14-6-2010 22:56:25 SETI@home Message from server: No work sent
14-6-2010 22:56:25 SETI@home Message from server: Your app_info.xml file doesn't have a usable version of SETI@home Enhanced.
14-6-2010 22:56:25 SETI@home Message from server: (reached daily quota of 100 tasks)

I even made a backup, detached, attached and still got nothing because I reached the "daily quota of 100 tasks". I only got about 20 today so where are the other 80 WU's?...

Is there any hope I'll get work for my Fermi (soon)?
It worked perfect for 1 day (with the same app_info.xml)... And now it's just sitting there... Waiting...

I installed Boinc 2 weeks ago to give it a try (again) but for some reason Seti always crashes when I try to join after a period of being inactive...

Okay, I'm a bit frustrated because I can't test my new toy...
Hope you forgive me for that :P

Don't worry, You've got plenty of company in this, No I don't have any Fermi cards, yet, Suffice It to say, their working on It.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 1004178 · Report as offensive
Speedy
Volunteer tester
Avatar

Send message
Joined: 26 Jun 04
Posts: 1639
Credit: 12,921,799
RAC: 89
New Zealand
Message 1004181 - Posted: 14 Jun 2010, 21:31:08 UTC
Last modified: 14 Jun 2010, 21:39:05 UTC

I think I have returned my 1st good Gpu 470 result Validate state is Initial as I write.
ID: 1004181 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14542
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1004185 - Posted: 14 Jun 2010, 21:40:58 UTC - in response to Message 1004181.  

I think I have returned my 1st good Gpu 470 result Validate state is Initial as I write.

setiathome_CUDA: CUDA Device 1 specified, checking...
Device 1: GeForce GTX 470 is okay
SETI@home using CUDA accelerated device GeForce GTX 470
V12 modification by Raistmer
Priority of worker thread rised successfully
Priority of process adjusted successfully
Total GPU memory 1309081600 free GPU memory 1238081536
setiathome_enhanced 6.02 Visual Studio/Microsoft C++

No, that version doesn't work on Fermi - see the eponymous thread. You need the stock application, as described in post #2 of this thread.
ID: 1004185 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1004189 - Posted: 14 Jun 2010, 21:42:14 UTC - in response to Message 1004181.  

I think I have returned my 1st good Gpu 470 result Validate state is Initial as I write.


Speedy, you can't run the V12 app with Fermi's, it doesn't produce valid results,

Claggy
ID: 1004189 · Report as offensive
Profile zoom3+1=4
Volunteer tester
Avatar

Send message
Joined: 30 Nov 03
Posts: 65061
Credit: 55,293,173
RAC: 49
United States
Message 1004190 - Posted: 14 Jun 2010, 21:43:57 UTC - in response to Message 997948.  
Last modified: 14 Jun 2010, 21:46:59 UTC

Re-posting, by popular request, from CUDA MB V12b rebuild supposed to work with Fermi GPUs.

This note is aimed at people running optimised apps already. That's essential: you will need to modify an existing app_info.xml file.

This isn't the place to go into the whole science of installing optimised applications by hand, but in brief: stop BOINC first, keep backups, use a simple ANSI-mode text editor. If in doubt, read the BOINC FAQ version - fuller, and can be updated in the future.

You will need to add a whole new <app_version> section:

    <app_version>
        <app_name>setiathome_enhanced</app_name>
    	<version_num>610</version_num>
    	<avg_ncpus>0.200000</avg_ncpus>
    	<max_ncpus>0.200000</max_ncpus>
    	<plan_class>cuda_fermi</plan_class>
	<file_ref>
            <file_name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</file_name>
            <main_program/>
	</file_ref>
	<file_ref>
            <file_name>cudart32_30_14.dll</file_name>
	</file_ref>
   	<file_ref>
            <file_name>cufft32_30_14.dll</file_name>
   	</file_ref>
	<file_ref>
            <file_name>libfftw3f-3-1-1a_upx.dll</file_name>
   	</file_ref>
	<coproc>
            <type>CUDA</type>
            <count>1</count>
	</coproc>
    </app_version>

You'll also have to add <file_info> sections for any file you're not already using. You may have libfftw3f-3-1-1a_upx.dll already, in which case you don't need to add it again: but the full set is

    <file_info>
        <name>setiathome_6.10_windows_intelx86__cuda_fermi.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cudart32_30_14.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>cufft32_30_14.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3-1-1a_upx.dll</name>
        <executable/>
    </file_info>

Finally, you'll need the files themselves: download from

http://boinc2.ssl.berkeley.edu/beta/download/setiathome_6.10_windows_intelx86__cuda_fermi.exe (2,476 KB)
http://boinc2.ssl.berkeley.edu/beta/download/cudart32_30_14.dll (280 KB)
http://boinc2.ssl.berkeley.edu/beta/download/cufft32_30_14.dll (12,188 KB)
http://boinc2.ssl.berkeley.edu/beta/download/libfftw3f-3-1-1a_upx.dll (439 KB)

Make sure the file sizes are correct - sometimes these manual downloads crash out early.

Which is 6.10 currently, On Fermi I think 6.08 and 6.09 are not Fermi compatible either.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 1004190 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 15 · Next

Message boards : Number crunching : Running SETI@home on an nVidia Fermi GPU


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.