PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
1) Message boards : Problems and Help : Problems with Ubuntu 10.10 and Proth Prime Search (Sieve) v1.35 (cuda23) (Message 30141)
Posted 3514 days ago by MttJocy
Ah, thanks for that, they are even better though you have used a different value for that <cmdline>-m #</cmdline> fix thing not sure without testing if that will work better or worse for me. I have recently realized that some work units are still failing (usually when I have other things going on that use the card for example being in SL etc but then only if in busy places so seems related to the amount of non CUDA work the card is doing). Pretty odd surely the card being busier should not cause a fail but merely a slowdown in processing speed?
2) Message boards : Problems and Help : Problems with Ubuntu 10.10 and Proth Prime Search (Sieve) v1.35 (cuda23) (Message 30129)
Posted 3514 days ago by MttJocy
The adding of -m 8 worked fine in my case with my GTX 460 using Ubuntu's driver for my card which is currently fixed at 260.19.06 I really did not want to have to go in and try messing with that as in the cases I have had to do that before for whatever reason it has been a difficult process causing untold problems.

I did have to dig around for quite some time to find a suitable app_info.xml file that I could use and edit to add the needed entry for the command line. So I am including the one that I used to solve the problem on my machine here at the bottom of this post for the benefit of those it may help.

The following has been tested successfully resolves the problem on Ubuntu 10.10 (Maveric Meerkat) when using the standard Nvida drivers from the Ubuntu Restricted Drivers Manager and an Nvidia GTX 460 graphics card. It is very likely to work with other distributions/cards etc also however I have not any to test so this is at your own risk. The app_info.xml is also set up for version 1.35 of the PPS (Sieve) Cuda app future versions would need appropriate modification to the file before use.

Now for the steps to use this solution, this is based on Ubuntu but could be modified for other operating systems fairly easily, all commands specified bellow are typed into your terminal.

First shut down your boinc-client completely, merely shutting down the manager is NOT sufficient. The following works on ubuntu others may vary.
sudo service boinc-client stop


Then change to your project directory with ubuntu the following command will do this, with other distributions you will have to change the /var/lib/boinc-client part to the correct path for your system.
cd [i]/var/lib/boinc-client[/i]/projects/www.primegrid.com


Next you need to create the app_info.xml file with the following command to bring up a text editor to input the file contents.
sudo nano app_info.xml


Next paste the following contents into the file, take care to edit the file names mentioned if you are not using the same version of PPS (Sieve) Cuda as this is written for namely 1.35.
<app_info>
<app>
<name>pps_sr2sieve</name>
<user_friendly_name>Proth Prime Search (Sieve)</user_friendly_name>
</app>
<file_info>
<name>321_sr2sieve_20090217.sieveinput</name>
<status>1</status>
<sticky/>
</file_info>
<file_info>
<name>gcwsieve_1250180098.sieveinput</name>
<status>1</status>
<sticky/>
</file_info>
<file_info>
<name>psp_sr2sieve_20100629.sieveinput</name>
<status>1</status>
<sticky/>
</file_info>
<file_info>
<name>TRP_20100604.sieveinput</name>
<status>1</status>
<sticky/>
</file_info>
<file_info>
<name>stat_primegrid.png</name>
<status>1</status>
</file_info>
<file_info>
<name>primegrid_slideshow_00.png</name>
<status>1</status>
</file_info>
<file_info>
<name>primegrid_tpsieve_1.35_x86_64-pc-linux-gnu__cuda23</name>
<status>1</status>
<executable/>
</file_info>
<file_info>
<name>libcudart.so.2</name>
<status>1</status>
</file_info>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>135</version_num>
<platform>x86_64-pc-linux-gnu</platform>
<avg_ncpus>0.020000</avg_ncpus>
<max_ncpus>0.020000</max_ncpus>
<flops>100000000000.000000</flops>
<plan_class>cuda23</plan_class>
<api_version>6.2.18</api_version>
<file_ref>
<file_name>primegrid_tpsieve_1.35_x86_64-pc-linux-gnu__cuda23</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libcudart.so.2</file_name>
<open_name>libcudart.so.2</open_name>
</file_ref>
<coproc>
<type>CUDA</type>
<count>1.000000</count>
</coproc>
<cmdline>-m 8</cmdline>
<gpu_ram>209715200.000000</gpu_ram>
</app_version>
</app_info>


Finally for boinc to have access to this file you will need to have it owned by the proper user and with the proper permissions this is a security check in boinc that it will only use files that are owned by it's own user. If your setup uses a different username/group for boinc use that in place of boinc.boinc here in the form username.group
chown [i]boinc.boinc[/i] app_info.xml && chmod 644 app_info.xml


Next all you need to do is restart the boinc service and everything should now work great :)
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2020 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 0.00, 0.01, 0.00
Generated 14 Aug 2020 | 17:22:47 UTC