In my "ultra-low-end" GT 520 I'm getting this message in results:

Estimated Nvidia GPU GFLOP/s: 104 SP GFLOP/s, 13 DP FLOP/s
Warning: Bizarrely low flops (13). Defaulting to 50

Bizarre ;-)

Maybe this 13 GFLOP/s info is correct and the default of 50 is too high, affecting the estimated time of polling period...

The AMD drivers have an issue that seems to show up every few driver releases where they are detected as 0 or very low Mhz so that is supposed to catch that breaking; I thought the 50 threshold was a bit lower than any DP GPUs which actually exist.

I have upgraded my BOINC version to 6.12.34, inserted the app_info.xml file in the milkyway@home project directory as instructed (downloaded from the link kindly supplied by arkayn), and am still not getting any WU's. If there is anything else that I can check or may have done wrong, suggestions would be greatly appreciated.

Also, I'm not entirely sure what the app_info.xml file I just inserted in the milkyway@home project directory actually does. I understand about downloading the application and the fact that older BOINC versions don't necessarily recognise graphics hardware as appropriately OpenCL capable, but what I'm not clear on is what the app_info.xml file does with regard to correcting this. Will the one app_info.xml file be universal to all machines utilising AMD graphics cards that are OpenCL capable? Does my CPU type, clock, core number, or my PC's operating system not require any tweak to the app_info to make this application run properly?

Thanks to everyone for the support on this forum and I would appreciate any reply I can get, because I'm confused and just trying to figure out if I've done something wrong trying to get work for this project. I just want to help! Milkyway is a great project, happy crunching everyone!

Everything errors out immediately on a Mac mini Core 2 Duo running OS X Leopard (10.5.x) since the update to 1.00. Everything was fine with 0.82.

I can't find other cases of that, but I reverted the OS X ones anyway since I guess nothing relevant for it was changed anyway.

Burned tons of WUs with
Exit status -1073740777 (0xffffffffc0000417) Unknown error number

Stderr output

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
- exit code -1073740777 (0xc0000417)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.00 Windows x86 double OpenCL </search_application>
Unrecognized XML in project preferences: nvidia_block_amount
Skipping: 128
Skipping: /nvidia_block_amount
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE3 path
Found 1 platform
Platform 0 information:
Name: AMD Accelerated Parallel Processing
Version: OpenCL 1.1 AMD-APP-SDK-v2.4-rc1 (595.9)
Vendor: Advanced Micro Devices, Inc.
Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices
Profile: FULL_PROFILE
Using device 0 on platform 0
Found 2 CL devices ??? huh ???
Device 'Cypress' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU)
Driver version: CAL 1.4.1332
Version: OpenCL 1.1 AMD-APP-SDK-v2.4-rc1 (595.9)
Compute capability: 0.0
Max compute units: 18
Clock frequency: 775 Mhz
Global mem size: 536870912
Local mem size: 32768
Max const buf size: 65536
Double extension: cl_amd_fp64

</stderr_txt>
]]>

WInXP 32bit, AMD 5830
Back to v0.82 for the moment

Found 2 CL devices ??? huh ???

Your CPU counts a 2nd device on AMD's OpenCL.

WInXP 32bit, AMD 5830
Back to v0.82 for the moment

Using Catalyst 11.3 it looks like. Try a newer driver. I am sort of aware of a few various crashes with different Catalyst versions on different GPUs. I think 11.3-4 and 11.10-11.12 are the most problematic versions; 12.1 seems to be working most consistently on everything. Around 11.3 the binary format stuff was introduced (which it says it supports) but it's probably crasher around then.

FWIW, OSX 10.6.8 Boinc 6.12.35 MWAH 1.00...

Received 7 1.00 WUs, processing normally (4 completed as of now). MWAH will not send any work either automatically or via manual update. Server status indicates everything functioning normally...

Any clues as to why no work issuance?

:)

Is there a command that can be added to the app-info file that will throttle back the GPU usage. It's now running @ 99% and I really don't want to run it that hard.
Thanks.

---

Is there a command that can be added to the app-info file that will throttle back the GPU usage. It's now running @ 99% and I really don't want to run it that hard.
Thanks.

You can raise the target frequency with the --gpu-target-frequency argument, or you can do it in the project preferences now which would be less annoying.

FWIW, OSX 10.6.8 Boinc 6.12.35 MWAH 1.00...

Received 7 1.00 WUs, processing normally (4 completed as of now). MWAH will not send any work either automatically or via manual update. Server status indicates everything functioning normally...

Any clues as to why no work issuance?

:)

And, now all WUs complete, task queue empty & computer idle, log says, "Project has no tasks available", server status as of 2:18:32 UTC, "Tasks ready to send 1,980" and "MilkyWay@Home unsent 1,759 MilkyWay@Home N-Body Simulation unsent 221"

???

Matt

I have no idea if this is symptomatic of the problem ... however its been stated above that its probably connected with recognising OpenCL capability on some cards. The lines below seem strange as I am sure before it also claimed to see GPU1 as OpenCL capable, whereas now it only claims one is. That ties in with a download I did get at one point - just two WUs on GPU0

09/02/2012 02:32:27 | | ATI GPU 0: AMD Radeon HD 79x0 series (Tahiti) (CAL version 1.4.1658, 3072MB, 3033MB available, 12493 GFLOPS peak)
09/02/2012 02:32:27 | | ATI GPU 1: AMD Radeon HD 79x0 series (Tahiti) (CAL version 1.4.1658, 3072MB, 3033MB available, 12493 GFLOPS peak)
09/02/2012 02:32:27 | | OpenCL: ATI GPU 0: Tahiti (driver version CAL 1.4.1658 (VM), device version OpenCL 1.1 AMD-APP (844.5), 3072MB, 3033MB available)
09/02/2012 02:32:27 | | OpenCL: ATI GPU 1: Tahiti (driver version CAL 1.4.1658 (VM), device version OpenCL 1.1 AMD-APP (844.5), 3072MB, 3033MB available)
09/02/2012 02:32:27 | | ATI GPU 0 is OpenCL-capable

Apologies if old news ..... am aware you will be beavering away.

Regards
Zy

Matt

I have no idea if this is symptomatic of the problem ... however its been stated above that its probably connected with recognising OpenCL capability on some cards. The lines below seem strange as I am sure before it also claimed to see GPU1 as OpenCL capable, whereas now it only claims one is. That ties in with a download I did get at one point - just two WUs on GPU0

09/02/2012 02:32:27 | | ATI GPU 0: AMD Radeon HD 79x0 series (Tahiti) (CAL version 1.4.1658, 3072MB, 3033MB available, 12493 GFLOPS peak)
09/02/2012 02:32:27 | | ATI GPU 1: AMD Radeon HD 79x0 series (Tahiti) (CAL version 1.4.1658, 3072MB, 3033MB available, 12493 GFLOPS peak)
09/02/2012 02:32:27 | | OpenCL: ATI GPU 0: Tahiti (driver version CAL 1.4.1658 (VM), device version OpenCL 1.1 AMD-APP (844.5), 3072MB, 3033MB available)
09/02/2012 02:32:27 | | OpenCL: ATI GPU 1: Tahiti (driver version CAL 1.4.1658 (VM), device version OpenCL 1.1 AMD-APP (844.5), 3072MB, 3033MB available)
09/02/2012 02:32:27 | | ATI GPU 0 is OpenCL-capable

Apologies if old news ..... am aware you will be beavering away.

Regards
Zy

That stuff isn't in my department. I've been seeing that sort of too, but that's the BOINC client's problem.

Everything errors out immediately on a Mac mini Core 2 Duo running OS X Leopard (10.5.x) since the update to 1.00. Everything was fine with 0.82.

I can't find other cases of that, but I reverted the OS X ones anyway since I guess nothing relevant for it was changed anyway.

Oh derp. Since last time I did this I updated to Lion and I forgot the 10.5 SDK was removed from the new stuff so it turns out I was building against the 10.6 SDK. I rebuilt it as 1.01 for the OS X ones.

Hi

I attached Milkyway@home and Milky won't any files. I did check this from boinc programdata milkyway folder. So no work,no exes no nothing.
My win7 64 bit+amd 6950 and 5830 were crunching everything ok before this update to 1.00.

I have Boinc 6.12.34 x64 version and Boinc 7.xx versions won't even start running(no boincmanager window would start even fresh windows 7 instal or deleting files manually after unistal) so it won't solution for this milkyway issue for me atleast.

Any ideas?

---

My Boinc Blog

Thanks for the quick action. I will have to wait until work is available to see if it works. My Mac mini Core Duo running Tiger (10.4.x) is still working on several units with the 0.82 version. I hope it continues to work when it gets the 1.01.

---

Plus SETI Classic = 21,082 WUs

Anyone actually manage to get the Linux x86_64 opencl app to work? I have an HD 4870 and it looks like I've been upgraded out of the ability to crunch. The 4870 doesn't like the new AMD drivers and it doesn't appear that the new app likes the old one.

This couldn't have waited til after the double credit day?

Anyone actually manage to get the Linux x86_64 opencl app to work? I have an HD 4870 and it looks like I've been upgraded out of the ability to crunch. The 4870 doesn't like the new AMD drivers and it doesn't appear that the new app likes the old one.

This couldn't have waited til after the double credit day?

What problem are you having? The 4870 drivers were broken with the OpenCL stuff from 11.8 to 11.12 or so. 12.1 works.

What problem are you having? The 4870 drivers were broken with the OpenCL stuff from 11.8 to 11.12 or so. 12.1 works.

I'm currently at 11.8 because anything (stable) after that broke other OpenCL apps. I see that 12.1 is in Gentoo Portage, so I'll try that. Thanks for the info.

Right now I'm suspecting that people aren't getting work because it seems that clients < 7 don't report having OpenCL and I updated the scheduler to check for the new stuff.

What combination and version of Windows os, catalyst driver and BOINC manager have you tested the new application on?

It's not the application, it's the project scheduler

Hmm... ok. What combination and version of Windows os, catalyst driver and BOINC manager have you tested the separation applications 1.00 against? I want to know caus I'm not getting any WUs. I gues that you have tested against some combination of OS & drivers or are you just make an update and hope for the best? ;)

Right now I'm suspecting that people aren't getting work because it seems that clients < 7 don't report having OpenCL and I updated the scheduler to check for the new stuff.

What combination and version of Windows os, catalyst driver and BOINC manager have you tested the new application on?

It's not the application, it's the project scheduler

Hmm... ok. What combination and version of Windows os, catalyst driver and BOINC manager have you tested the separation applications to 1.00 against? I want to know caus I'm not getting any WUs. I gues that you have tested against some combination of OS & drivers or are you just make an update and hope for the best? ;)

Right now, there is no work available. I am doing Collatz.

---

I'm getting "Server Error recompile needed", the first time was a couple of mins ago.