I have tried to download the newer BOINC version 3 times, each time, it failed with a generic failure message. I guess it will sort itself out after a while, I had not seen the problem anyway, so not a critical issue.

Berkeley is having their usual down times and downloads are difficult, give it a day or so and they should be back up again.

SETI@home Network Outage (August 17-18)
Due to network and DNS upgrades/changes we will be shutting down the projects tonight (August 17th) and we will be offline until the next morning. 18 Aug 2015, 3:46:32 UTC

I unchecked the N-body box but am still getting them Why?

could someone tell me how to disable nbody tasks from being fetched by boinc ? they clog up my system for hours on end if i dont check boinc as they stay at 100% on 4 cores and never finish, one time i came back to my computer to see it was stuck for 17hours. my computer does not like them.

so please how can i disable them ?

From the home page, your account, Preferences for this project MilkyWay@Home preferences, Edit MilkyWay@Home preferences, and you will see this:

Run only the selected applications
MilkyWay@Home
MilkyWay@Home N-Body Simulation
Milkyway@Home Separation
Milkyway@Home Separation (Modified Fit)

uncheck the n-body simulation box, save the changes and from then on no more n-body tasks will come your way.

Hey guys, I know this thread is a couple of weeks old now, but I was wanting to ask a question. My main system has an R290X, but that is because it is also my gaming system. My other systems have a 7970 and 6970. At this point I have been unable to get my 290X system to obtain new work units.

I have removed and re-added the project, and even have gone so far as to completely remove and reinstall BOINC. No matter what I do I cannot get this 290X to get MW@H work units.

Anyone else having this problem, or know of any suggestions on how to fix it? I'm out of ideas, and while it may not be my fastest cruncher, I really hate the fact that I can't get MW@H units to keep it occupied when I'm not using it for gaming.

Thanks a lot.
What exactly is NBODY?
Why isn't it included?
Where do I have to copy that app_info.xml file to?
Can I modify the number of WUs being processed in parallel on my GPU (it has 4 GB of GDDR5 RAM onboard) and if so how/where?

Michael.

Well, is there a sample file available to get my R9 290X working for Milkyway@home?

Michael.

I have an AMD R9 290X (MSI Lightning) graphics board, capable of double-precision and OpenCL 1.2 in my machine. For unknown reasons, it does not get any work from this project. It works excellently with Folding@home and Einstein@home, so I was wondering what the problem could be?

Michael.

Well, I think I finally figured out why MW@H isn't sending me any GPU WU's on my ATI machine. It see's my HD7950 and HD7850 as:

"Message from server: ATI GPU R600 (R38xx) does not support OpenCL"

I'm using the Catalyst 14.4 driver and E@H is going like gangbusters crunching multiple GPU WU's per card.

Basically, E@H has this machine all to itself right now and would like to thank MW@H for their generosity!

Regards,
Steve

See my reply in your thread.
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3710&postid=63088#63088

Arkayn,

Thanks for the suggestion but I'm on Linux Mint (17.1), not Windows.

Regards,
Steve

Well, I think I finally figured out why MW@H isn't sending me any GPU WU's on my ATI machine. It see's my HD7950 and HD7850 as:

"Message from server: ATI GPU R600 (R38xx) does not support OpenCL"

I'm using the Catalyst 14.4 driver and E@H is going like gangbusters crunching multiple GPU WU's per card.

Basically, E@H has this machine all to itself right now and would like to thank MW@H for their generosity!

Regards,
Steve

Are you getting any error messages about why you are not receiving GPU work?

Arkayn,

I checked the event log and there aren't any error messages. I went onto my MW@H and Seti preferences pages and even de-selected the option for cpu units to try to force some gpu WU's but no luck.

I'm using the Catalyst 14.10 drivers and E@H seems happy as a clam. But, Seti is like MW; no gpu units.

I just had an idea. I'll switch to a different HD and re-install the OS (Linux Mint 17.1) and then install the Catalyst 13.x drivers that I have archived instead of the Catalyst 14.10 and see if that makes a difference. If it doesn't, I don't lose anything.

Regards,
Steve

I just converted a machine with an ATI HD7950 and HD7850 GPUs over to BOINC but am not receiving any GPU work units. I checked and both are DP-capable so that's not it. I've checked my MW computing prefs and everything looks fine. The machine in question is M6400T.

The machine is happily crunching E@H GPU WU's so it's not a question of BOINC not seeing the GPUs.

All of my other machines are NVIDIA and are doing fine.

Any help would be appreciated.

Regards,
Steve

Is BOINC using GPU GT660 for their calculations? I don't hear any higher working fans of graphic card.

I can't answer this but maybe you want to ask this on the Boinc GPU forum?

....the runs might not fully utilize your GPU. ...try configuring your GPU to run 2 of these at the same time...

Jake

Uhm, is there a tutorial for that?

Copy this in Notepad (not Word):


<app_config>
<app>
<name>milkyway</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
<app>
<name>milkyway_separation__modified_fit</name>
<gpu_versions>
<gpu_usage>0.5</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>


Save the file as "app-config.xml" and place the file here:
(Unhide your folders if you haven't already)
Program data\Boinc\Projects\MilkyWay
Restart Boinc and you'll be running two at a time.

Is this app not available on Linux? I simply get an error that it cannot find an app by that name, so it only discovers the normal milkyway app.

I see the native CUDA application has been pulled. This card would work with that, but will not work because it cannot do above the OpenCL 1.0. There is no driver that can fix this.

Thanks for the link. When I look at benchmarks to compare Nvidia vs. AMD cards, there seems to be a lot of disagreement on what benchmark is a good & fair comparison. When comparing the GPU’s, what number should I look for in regards to MW Projects?

Thanks for the download link, but I have already located a copy on a sister machine. My problems have moved on a little since then.

I have discovered that your app_info is coded for two of the four available applications. I have disabled the unconfigured applications in my profile until I can resolve the issue, either by the sysadmins fixing the generic problem or by using an app_info which covers all four applications.

Are you able/willing to supply a comprehensive app_info - I would have a go myself, but there are parameters in there that I have no idea what they are for.

I have also now discovered that the client does not seem willing to update to the server automatically on a frequent-enough schedule to keep the cache flowing. The sister machine seems to run a scheduler every 60 seconds, clearing completed tasks and requesting new ones, but this new installation doesn't seem to run any automatic scheduler.

Is that configured (or missing) in the app_info?

Contact rate is set by the cache settings that you use.

This should be the CPU app version of Milkyway.


<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Paste them below the ATI versions that are already there.

<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

If you want NBODY, I cannot help you on that one.

NBODY is one of the two unconfigured applications. The other is MilkyWay@Home (you have given me the two "Separation" applications).

I am dedicating the CPU processing to a different project (WCG) so do not need the CPU aspect of MW@H.

I have been fiddling with settings trying to sort out conflicting global settings with project-specific ones and think I have finally got the cache setting right to keep up the MW@H feed.

I guess I can live with my new status quo until the general problem is sorted centrally.

Thanks very much for your help.