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 . . . 15 · Next

AuthorMessage
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1000975 - Posted: 5 Jun 2010, 16:32:00 UTC

I had seen an old post from Sciman Stev on where he put the file but have been unable to tack down his post.


ID: 1000975 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15183
Credit: 4,362,181
RAC: 3
Netherlands
Message 1000987 - Posted: 5 Jun 2010, 16:54:56 UTC - in response to Message 1000975.  

Did you follow the FAQ on the subject? It says where to put these files.

If that's not written clearly enough, let me know and I'll change the text.
ID: 1000987 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001029 - Posted: 5 Jun 2010, 18:15:04 UTC - in response to Message 1000987.  

Richard,
Thanks for your time and effects.

I would recommend the following changes to the guide.

Install the Lunatic
FreeBSD science apps first as the app_info file does not exist with out it.
(Newbei info like me)

I Installed the FreeBSD 64bit Science Apps
(64bit AstroPulse_V505)
I am running a Intel 920 cpu ( It would help if you provided links in the FAQ)
to the follow your guide.

I am assumming That I have done this correctly as the Boinc Manager in messages now reports

Seti@Home (date/Time) Found app_info.xml; Using Anonymous platform
(What can a user expect to see if install correctly)

A complete XML text that can be copy and pasted into the app_info would be helpful

As most people are going to be unsure what a completed info_app.xml should look like.

(Under Win 7 64 bit the xml data and dll where put in c:\programdata\Boinc\projects\setiahome.berkeley.ed
I do not know if the file structure changes between windows versions.

I will keep the project on no ne tasks until I hear from you that I have installed coorectly.

I really do appreciate you time a efforts.

Below is the XML as modified is this correct?

<app_info>
<app>
<name>astropulse_v505</name>
</app>
<file_info>
<name>ap_5.06r237_sse3_x86_64-pc-freebsd</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>506</version_num>
<file_ref>
<file_name>ap_5.06r237_sse3_x86_64-pc-freebsd</file_name>
<main_program/>
</file_ref>
</app_version>
</app_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>
<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>


thanks once again for all your efforts


ID: 1001029 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1001031 - Posted: 5 Jun 2010, 18:20:44 UTC - in response to Message 1001029.  
Last modified: 5 Jun 2010, 18:23:31 UTC

John, you CAN'T use FreeBSD, Linux or any Other OS's apps on Windows, use the Lunatics Installer to install the WINDOWS apps, then modify the app_info for Fermi,

Claggy
ID: 1001031 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001035 - Posted: 5 Jun 2010, 18:29:32 UTC

can you provide a link and the the file name?

ID: 1001035 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001037 - Posted: 5 Jun 2010, 18:33:50 UTC

is Astropulse 5.05 win32 rev 409 sse4 the coorect file?

ID: 1001037 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1001038 - Posted: 5 Jun 2010, 18:39:57 UTC - in response to Message 1001035.  
Last modified: 5 Jun 2010, 18:42:46 UTC

can you provide a link and the the file name?


Lunatics Downloads

Choose the Installer according to your OS,

Win98me Lunatics' Unified Installer v0.36 is for Win98 or Me

Win32 Lunatics' Unified Installer v0.36 is for 32bit Windows

Win64 Lunatics' Unified Installer v0.36 is for 64bit Windows

Make sure you only use the 64bit Version with the 64bit version of Boinc,

Claggy
ID: 1001038 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001039 - Posted: 5 Jun 2010, 18:40:17 UTC

OK I see the Win64 Lunatic's Unified Installer V0.36 should be the coreect one.

ID: 1001039 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001041 - Posted: 5 Jun 2010, 18:43:49 UTC

installed win64 Lunatics Unified Installed V0.36
my info_app.xml looks like this is this correct?
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSE3.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_SSE3.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_SSE3.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_info>

Thanks in advance

ID: 1001041 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1001042 - Posted: 5 Jun 2010, 18:47:09 UTC - in response to Message 1001041.  
Last modified: 5 Jun 2010, 19:09:02 UTC

Rerun the Installer, and choose SSSE3 (instead of SSE3),

Claggy
ID: 1001042 · Report as offensive
John

Send message
Joined: 21 May 99
Posts: 51
Credit: 5,667,907
RAC: 0
United States
Message 1001043 - Posted: 5 Jun 2010, 18:51:53 UTC

Sorry about that I did not remodify after Unified installed Update.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_x64_SSE3.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_SSE3.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_SSE3.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_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>
<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>
ID: 1001043 · 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 1001052 - Posted: 5 Jun 2010, 19:26:25 UTC - in response to Message 1001043.  

John,
As Claggy asked you, please rerun the unified installer and choose SSSE3, that's three S's not just two. Other than that, to my untrained eyes that looks pretty good.


PROUD MEMBER OF Team Starfire World BOINC
ID: 1001052 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1001054 - Posted: 5 Jun 2010, 19:37:40 UTC - in response to Message 1001043.  
Last modified: 5 Jun 2010, 19:41:51 UTC

Your app_info won't work, you can't just tag the fermi stuff on the end, after the </app_info> close tag,
the <file_info>'s also need to be at the start of the fermi section after the <app><name>setiathome_enhanced</name></app> tags (that you don't have).

Once you're rerun the installer and choosen the SSSE3 (3S's) version of AK_V8 instead of the SSE3 version (2S's), as well as the Astropulse_v505 r409 app,
then you can use this following app_info:

<app_info> 
    <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>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>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>
       <platform>windows_intelx86</platform>
       <avg_ncpus>0.200000</avg_ncpus>
       <max_ncpus>0.200000</max_ncpus>
       <plan_class>cuda_fermi</plan_class>
       <coproc>
          <type>CUDA</type>
          <count>1</count>
       </coproc>
       <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>
   </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>
       <coproc>
          <type>CUDA</type>
          <count>1</count>
       </coproc>
       <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>
   </app_version>
</app_info>


Claggy
ID: 1001054 · 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 1001516 - Posted: 7 Jun 2010, 17:17:24 UTC

Hi there

Im getting the following messages in my logs everytime I try and run rescheduler?
I have the 610 CUDA app as I can see it in my processes, and my gtx470 is crunching away merrily. Is rescheduler compatible with the latest fermi workunits? Should I stop using it?

06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding

Thanks

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

Send message
Joined: 30 Nov 03
Posts: 65052
Credit: 55,293,173
RAC: 49
United States
Message 1001520 - Posted: 7 Jun 2010, 17:43:14 UTC - in response to Message 1001516.  

Hi there

Im getting the following messages in my logs everytime I try and run rescheduler?
I have the 610 CUDA app as I can see it in my processes, and my gtx470 is crunching away merrily. Is rescheduler compatible with the latest fermi workunits? Should I stop using it?

06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding
06/06/2010 18:38:09 SETI@home [error] No application found for task: windows_x86_64 610 cuda; discarding

Thanks

From what I've read and unless It has been updated, No.
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's
ID: 1001520 · 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 1001521 - Posted: 7 Jun 2010, 17:47:04 UTC - in response to Message 1001520.  

Ok, thanks for that - will keep an eye out on the lunatics forum..
ID: 1001521 · 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 1001523 - Posted: 7 Jun 2010, 17:48:34 UTC - in response to Message 1001516.  

You should be OK rescheduling from GPU to CPU.

I would expect that ReSchedule would have problems creating entries for plan class cuda_fermi, as specified in the opening post in this thread. If you really feel the need to move tasks from CPU to GPU (and there's no need to do that, if your primary need is simply to process VLAR efficiently), you could:

1) Allow ReSchedule to move tasks to the GPU, but prevent BOINC running afterwards
2) Examine client_state.xml, to see how they've been marked up
3) Make a duplicate <app_version> block for app_info.xml, matching the entries that ReSchedule makes.

Or you could just wait for Marius to publish a new version.....
ID: 1001523 · Report as offensive
Profile Todd Hebert
Volunteer tester
Avatar

Send message
Joined: 16 Jun 00
Posts: 648
Credit: 228,292,957
RAC: 0
United States
Message 1001531 - Posted: 7 Jun 2010, 18:55:36 UTC

I suspect that when the ReScheduler operation runs it is taking the tasks that previously have been marked to run with a CPU app that is not present on the system. If you are running another optimized app from Lunatic's (AK's) it should work.

I am not running a specific Fermi app on my system - currently Cuda23 and the AK x64 - but I don't experience the same behavior. My Rescheduling does work, for the most part, properly.

I believe that Richard is correct - those tasks are being marked up to an app other than what is on the system and in the app_Info.xml there is no app available to process those.

His suggestion should work. Best of luck!
ID: 1001531 · 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 1001547 - Posted: 7 Jun 2010, 20:29:01 UTC

The Fermi application (v6.10) has become visible on the SETI applications page. That means Fermi users should be able to handle work correctly without using the techniques described in this thread. We need to check that everything's working OK: if anyone has a Fermi they have not yet attached to SETI, feel free to attach now and post your HostID so we can check the results with you.
ID: 1001547 · 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 1001578 - Posted: 7 Jun 2010, 21:18:00 UTC - in response to Message 1001523.  

Thanks for this Richard, I will give this a go...

You should be OK rescheduling from GPU to CPU.

I would expect that ReSchedule would have problems creating entries for plan class cuda_fermi, as specified in the opening post in this thread. If you really feel the need to move tasks from CPU to GPU (and there's no need to do that, if your primary need is simply to process VLAR efficiently), you could:

1) Allow ReSchedule to move tasks to the GPU, but prevent BOINC running afterwards
2) Examine client_state.xml, to see how they've been marked up
3) Make a duplicate <app_version> block for app_info.xml, matching the entries that ReSchedule makes.

Or you could just wait for Marius to publish a new version.....


ID: 1001578 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5 . . . 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.