Yeah well I know that already, but thanks for answering! :)
I may have shaped my question wrong.
What I was meaning is the efficiency, meaning how much power used to complete certain amount of project data in what time or something like that.

Generally, the same answer for efficiency.

I think I see the problem, the app_info is definitely out of order and is getting closed prematurely. It also does not list the correct app for CUDA processing.

Try pasting this one into the app_info and saving.

<app_info>
 <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_0.88_x86_64-pc-linux-gnu</name>
    <executable/>
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>88</version_num>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_separation_0.88_x86_64-pc-linux-gnu</file_name>
      <main_program/>
    </file_ref>
  </app_version>
  <app>
    <name>milkyway</name>
  </app>
  <file_info>
    <name>milkyway_separation_0.82_x86_64-pc-linux-gnu__cuda_opencl</name>
    <executable/>
  </file_info>
  <app_version>
    <app_name>milkyway</app_name>
    <version_num>82</version_num>
    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>1</max_ncpus>
    <plan_class>cuda</plan_class>
    <coproc>
      <type>CUDA</type>
      <count>0.5</count>
    </coproc>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_separation_0.82_x86_64-pc-linux-gnu__cuda_opencl</file_name>
      <main_program/>
    </file_ref>
  </app_version>
  <app>
    <name>milkyway_nbody</name>
  </app>
  <file_info>
    <name>milkyway_nbody_0.62_x86_64-pc-linux-gnu__mt</name>
    <executable/>
  </file_info>
  <app_version>
    <app_name>milkyway_nbody</app_name>
    <version_num>62</version_num>
	<cmdline></cmdline>
    <file_ref>
      <file_name>milkyway_nbody_0.62_x86_64-pc-linux-gnu__mt</file_name>
      <main_program/>
    </file_ref>
  </app_version>
</app_info>

---

Thanks so much for the help.

Right off, this solved the problem of Boinc not seeing the app_info.xml.

At first, I was still having problems getting MW to run and more and more it just felt like some sort of file ownership/permissions problem even though I had been back and forth on this for days.

Finally, it occurred to me to see how Collatz was handling things since it ran from the very start with no fuss. Of course, when their app installs it also installs a properly configured app_info.xml file and spares the user all the needless troubleshooting grief.

I then changed all of the MW file ownerships/permissions to match those of Collatz, and bingo, everything works great.

So, thanks again for the help. It's great to have things not only working but working at extra efficiency with the GPUs.

Regards,
Steve

I just received a message regarding the GPU: Notice from server: An ATI GPU supporting double precision math is required.

If I don't upgrade hardware, is this message telling me that I cannot run any milky way tasks and I should delete the project until I do upgrade? Or does it just use the CPU? I have some milky way credits, but maybe tasks that completed some time ago did not have a Double Precision arithmetic requirement. Please clarify. Thanks much.

BTW - I recently rejoined after some time away, so I am not current on issues.

I just received a message regarding the GPU: Notice from server: An ATI GPU supporting double precision math is required.

If I don't upgrade hardware, is this message telling me that I cannot run any milky way tasks and I should delete the project until I do upgrade? Or does it just use the CPU? I have some milky way credits, but maybe tasks that completed some time ago did not have a Double Precision arithmetic requirement. Please clarify. Thanks much.

BTW - I recently rejoined after some time away, so I am not current on issues.

Milkyway has applications for the CPU, ATI GPU's and Nvidia GPU's. Only problem is all GPU's have to have Double Precision to be used here. Your 58x0 GPU does not meet that requirement. You can still use the CPU to process though.

---

That's what I thought, so thanks for letting me know. Appreciate the response!

I just received a message regarding the GPU: Notice from server: An ATI GPU supporting double precision math is required.

If I don't upgrade hardware, is this message telling me that I cannot run any milky way tasks and I should delete the project until I do upgrade? Or does it just use the CPU? I have some milky way credits, but maybe tasks that completed some time ago did not have a Double Precision arithmetic requirement. Please clarify. Thanks much.

BTW - I recently rejoined after some time away, so I am not current on issues.

Milkyway has applications for the CPU, ATI GPU's and Nvidia GPU's. Only problem is all GPU's have to have Double Precision to be used here. Your 58x0 GPU does not meet that requirement. You can still use the CPU to process though.

I think you mean her HD 5x00 GPU. If she had a 58x0 GPU, she would be golden.

---

I think you mean her HD 5x00 GPU. If she had a 58x0 GPU, she would be golden.

It was getting late when I posted that!!

Yes, that is what I meant.

---

Has anyone had a chance to see if the new AMD Llano APUs have DP Graphics and any experience with getting MW@H to run on them? I know AMD has put a lot into marketing these chips as having integrated direct computer capabilities, but it wont help us here if the double-precision ability is not there, otherwise it looks like a very power-efficient alternative.

I recently built a system using the A8-3850 and it does not support DP on the GPU. Figured I would post my experiences in case anyone goes looking through these threads. The other projects that support AMD/ATI GPUs that do not require DP math will recognize and use the A8-3850's integrated GPU, however. The IGP only runs at 600MHz by default and, while there are BIOS out there (I'm looking at you, A75M-UD2H) that offer you an option to overclock the GPU only, it does not work. The only way to overclock the IGP currently is to raise the BCLK for the entire CPU. I was able to get the IGP from 600MHz to 876MHz with 146 x 6 but it came at significant cost of power and heat.

So no, no DP on the Llano IGPs.

I recently built a system using the A8-3850 and it does not support DP on the GPU. Figured I would post my experiences in case anyone goes looking through these threads. The other projects that support AMD/ATI GPUs that do not require DP math will recognize and use the A8-3850's integrated GPU, however. The IGP only runs at 600MHz by default and, while there are BIOS out there (I'm looking at you, A75M-UD2H) that offer you an option to overclock the GPU only, it does not work. The only way to overclock the IGP currently is to raise the BCLK for the entire CPU. I was able to get the IGP from 600MHz to 876MHz with 146 x 6 but it came at significant cost of power and heat.

What completion times are you getting on other projects (Collatz, Moo!, Primegrid)(OCed and stock speeds)?

What completion times are you getting on other projects (Collatz, Moo!, Primegrid)(OCed and stock speeds)?

I will get back to you on this. I am still playing around with the system and threw a HIS 6950 in it last night, thinking I would be able to have BOINC recognize two distinct GPUs but it seems that the Gigabyte A75M-UD2H BIOS disables the IGP when a discreet card is added that it cannot do hybrid crossfire with. Any options to tune the IGP just vanish from BIOS with the 6950 plugged in (at least in the x16 slot, I haven't tried the x4 slot yet).

. The other projects that support AMD/ATI GPUs that do not require DP math will recognize and use the A8-3850's integrated GPU, however.

I've got an Asus F1A75-M Pro with an A8-3850 running Ubuntu 10.10 64 bit.

I've tried MilkyWay, Moo and Prime - Boinc states no useable GPU in all cases.

Running ATI 11.8 drivers.

Using just the onboard graphics the Unigine Heaven benchmark runs great, can run 2 Nexius windows simultaneously with no significant load on the cores.

However - can't run AMDOverdriveCtrl, which works with pretty well any discrete card.
And Linux doesn't recognize the sensors, so I don't like to push the CPU without knowing what the temps are.

What completion times are you getting on other projects (Collatz, Moo!, Primegrid)(OCed and stock speeds)?

Due to some strange issues I had with the Gigabyte A75M-UD2H, I swapped to an ASUS F1A75-V PRO which is proving to be a much better board. I can now use both the integrated GPU on the A8-3850 and the 6950 simultaneously.

This is a very small sampling at stock speeds (everything is stock, no tuning at all yet since I just got the system together) but here are some timings.

A8-3850 IGP on mini_collatz 2.09 (ati13ati)
Run 1: 12:56
Run 2: 13:09
Run 3: 13:25

HIS 6950 on mini_collatz 2.09 (ati13ati)
Run 1: 3:11
Run 2: 3:07
Run 3: 3:14

A8-3850 single core on mini_collatz 2.00 (sse)
Run 1: 5:24:27
Run 2: 5:12:03
Run 3: 5:04:34

A8-3850 IGP on collatz 2.09 (ati13ati)
Run 1: 1:44:46
Run 2: 1:46:21

HIS 6950 on collatz 2.09 (ati13ati)
Run 1: 26:34
Run 2: 26:12


A8-3850 IGP on Primegrid task (I forgot to capture the application name):
Run 1: 2:05:34

HIS 6950 on Primegrid task:
Run 1: 31:57

Based on the numbers above, the A8-3850's 6550D (600MHz core, 400 stream processors) is approximately 1/4 the speed of the HIS 6950 (840MHz core, 1408 stream processors) for number crunching purposes.

The IGP is 25 times faster than a single core on the A8-3850 for the same kind of Collatz and Primegrid tasks. The HIS 6950 is 101 times faster.

Based on the numbers above, the A8-3850's 6550D (600MHz core, 400 stream processors) is approximately 1/4 the speed of the HIS 6950 (840MHz core, 1408 stream processors) for number crunching purposes.

The IGP is 25 times faster than a single core on the A8-3850 for the same kind of Collatz and Primegrid tasks. The HIS 6950 is 101 times faster.

Thanks much for posting this, pretty interesting. It seems the A8 IGP is much faster than anything previously integrated with the CPU. Not a bad crunching option for corporate users and those not wanting to buy expensive GPUs. One last question, any idea of the power draw (total watts: GPU running WUs, not running WUs).

I have the HD 5570.

Based on the numbers above, the A8-3850's 6550D (600MHz core, 400 stream processors) is approximately 1/4 the speed of the HIS 6950 (840MHz core, 1408 stream processors) for number crunching purposes.

The IGP is 25 times faster than a single core on the A8-3850 for the same kind of Collatz and Primegrid tasks. The HIS 6950 is 101 times faster.

Thanks much for posting this, pretty interesting. It seems the A8 IGP is much faster than anything previously integrated with the CPU. Not a bad crunching option for corporate users and those not wanting to buy expensive GPUs. One last question, any idea of the power draw (total watts: GPU running WUs, not running WUs).

Unfortunately, I managed to kill my kill-a-watt and my UPSs with meters in them are all tied up. Anand puts the A8-3850 at 43.6W idle and 126W loaded, however. At stock speeds, with all cores and the IGP crunching, with a CM Hyper 212+ HSF installed, it heats up to somewhere between 36 and 38C in a room that is between 82 and 85F.

I just hooked an ASUS GeForce GT 440 in my server. So far, it works with MW, Einstein, Collatz, PrimeGrid, GPUGRID, DNETC and DistrRTgen

You can add the Nvidia Quadro 600 (do not confuse with 6000).

Tested and 100% working.

It's a little bit slow, but it's better than nothing :)

Why does that document, "AMD_APP_SDK_Getting_Started_Guide_v2.4" say that the ATI FirePro V5800 card supports double-precision if it doesn't?

seems that ther is a mistake:

wiki:
http://en.wikipedia.org/wiki/Comparison_of_AMD_graphics_processing_units#FirePro_3D_series
FirePro 3D V5800[96] April 26, 2010 Juniper XT(RV840)
But the V5900 has a Cayman proc. so this must have DP