• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

POEM@Home GPU work

Gilthanis

Gilthanis

[H]ard|DCer of the Year - 2014
Joined
Jan 29, 2006
Messages
9,046
POEM@Home now has GPU capabilities for Linux and Windows ATI cards and are working on getting nVidia to work. They are using OpenCL.

For those who aren't familiar with them, they are a BOINC project that does protein research.
http://boinc.fzk.de/poem/

Available for AMD/ATI OpenCL1.0 capable GPU's (4000series to recent). Up and running for Win and Linux. For Win you need to have a recent Catalyst driver. You also need Boinc 7.x which is the current development version. nVidia will be OpenCL1.1 once it is finished.
 
Last edited:
Running 2x "POEM++ OpenCL 0.01 - opencl_ati_100" in Windows Boinc on ATI video card by downloading app_info.txt into your C:\ProgramData\BOINC\projects\boinc.fzk.de_poem folder and rename it app_info.xml and restart Boinc.
All old Poem++ work units will be sent back and new ones will be downloaded.
Raises my GPU usage up to nearly 100% - be sure to free up 1-2 CPU cores.
 
I didn't have to make the app_info.xml to get it to work. Just updated my Catalyst driver and made sure it was the right version of BOINC and the rest was done from their end. And yes, it does require quite a bit of a core for the GPU work units. Keep in mind that this is new and tweaks will be made as time goes by.

I'm running it with an old AMD Radeon HD4350.

Edit: I take that back...after posting, my test machine started puking out errors. I will now try it your way...lol
 
Last edited:
The app_info.xml file is only if you want to run 2 work units simultaneously on a ATI video card.
Same app_info.xml file will run 2 work units on each video card in multi ATI video card machines also.
 
Ahh...gotcha...I'm looking into the failed tasks....apparently I'm having the lockfile error and have to track down why. POEM is the only app having the trouble.
 
For Linux users, change the poemcl_0.1_windows_intelx86__opencl_ati_100 to poemcl_0.1_x86_64-pc-linux-gnu (I think thats the Linux app name?)

app_info.xml
Code: 
<app_info>
 <app>
  <name>poemcl</name>
  <user_friendly_name>POEM++ OpenCL</user_friendly_name>
 </app>
 <file_info>
  <name>poemcl_0.1_x86_64-pc-linux-gnu</name>
  <executable/>
 </file_info>
 
 <app_version>
  <app_name>poemcl</app_name>
  <version_num>1</version_num>
  <plan_class>opencl_ati_100</plan_class>
  <avg_ncpus>0.5</avg_ncpus>
  <max_ncpus>0.5</max_ncpus>
  <flops>2.1e10</flops>
  <coproc>
   <type>ATI</type>
   <count>0.5</count>
  </coproc>
  <cmdline></cmdline>
  <file_ref>
   <file_name>poemcl_0.1_x86_64-pc-linux-gnu</file_name>
   <main_program/>
  </file_ref>
 </app_version>
</app_info>
 
I reverted Catalyst software from 11.12 to 11.9 and still getting errors.

<core_client_version>7.0.3</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
<stderr_txt>
04:58:16 (2576): Can't acquire lockfile (32) - waiting 35s
05:50:06 (2784): Can't acquire lockfile (32) - waiting 35s

</stderr_txt>
]]>
 
The Cuda app is having problems from what I read in their forum.
I run strictly the ATI app that Boinc downloads automatically with the addition of the app_info.xml file.
I wont run the Cuda app until Boinc downloads it like a regular app without the additional poemclwin.zip file needed.
 
Gilthanis said:
I reverted Catalyst software from 11.12 to 11.9 and still getting errors.

<core_client_version>7.0.3</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
<stderr_txt>
04:58:16 (2576): Can't acquire lockfile (32) - waiting 35s
05:50:06 (2784): Can't acquire lockfile (32) - waiting 35s

</stderr_txt>
]]>
Click to expand...



it could just be the 4350 doesn't really support it given that its an ultra low end gpu and instead gives a lockfile error.. just my guess.
 
sirmonkey1985, I'm guessing that is probably more then likely. I will keep an eye on it. I am only running that one ATI card there for testing anyways. I currently only have nVidia in the rest of my rigs, so will wait like Razor_FX_II for them to get the other going. Unfortunately, pretty much all my cards are low end right now.
 
Evidently, the current consensus is that some cards may only be OpenCL 1.0 compliant under certain operating systems. So, I will move this card to a Vista machine sometime this weekend and see if there is better results. The 4350 is supposed to be OpenCL 1.0 which is the requirement.
 
I tried moving the card to a Windows 7 Premium x64 system and it had the same problems. I think I will conclude the card incompatible until they figure out more. Evidently, they don't even really know which cards will officially work yet.
 
Just upgraded to the .xml file and now my 6970's are running 2 instances each of POEM. Very nice production now.
 
Just an update for those interested. nVidia cards are still not supported. The new credit system is still terrible. And if I remember correctly, you still need to run a 4700 card or newer from ATI even though older cards SHOULD be capable. Berkeley also has the 7.0.8 available for testing, but I have not tried it yet with POEM.
 
Gilthanis said:
Just an update for those interested. nVidia cards are still not supported. The new credit system is still terrible. And if I remember correctly, you still need to run a 4700 card or newer from ATI even though older cards SHOULD be capable. Berkeley also has the 7.0.8 available for testing, but I have not tried it yet with POEM.
Click to expand...

Give them time man. The GPU app is beta and there is bound to be some growing pains. Just out of curiosity why is the new credit system terrible?
 
It (as in the credits) is all over the place. Evidently there is a problem with balancing credits between CPU work units and GPU work units. So, some tasks get normal credit and some get little credit. The CreditNew system is supposed to be a new way of making credits more balanced. However, it just takes too long and many people get discouraged. Most projects are avoiding the new credit system.

And I'm not complaining, just giving an update for those who don't wanna drudge through their forums. My statement about the cards that "should' be supported is that POEM hasn't fully tested what does and does not work. So, the members are having to iron that out on an experimental basis.

Edit: And some people are experiencing more credits/day by running a single work unit rather then two when others using the same card are experiencing more credits running more then one. As you said, it is still kinda Beta. Time will solve most problems, but it is still good to be informed.
 
Last edited:
You must log in or register to reply here.
Back
Top