Just to clarify things a bit, if CP comes out with a corrected 'current generation' app before you release your new source code, that would provide an immediate solution to the 'invalids' problem if all 5800 series owners were to immediately adopt the new app.

Yeah, it seems like CP (and Anthony) are working on new version of the 58x0 application, which will solve this problem. Hopefully they'll be out soon.

You have mentioned several times about 'releasing the new code' and 'allowing people to compile their own apps' but I don't think you actually spelled out exactly what precompiled apps you would be releasing as well. I might be wrong but I got the impression at one point that you might be building for CPU and CUDA but perhaps not for ATI? In other words, we would need to rely on the continuing services of CP or someone else to port the new code and build the appropriate ATI apps. Is this how things will work when you release the new code?

Right now I've compiled some OSX applications, and they're on the server right now as milkyway3 (technically what people are running right now is milkyway2, as before that was just astronomy). I don't have the hardware to compile the windows applications so I'm going to need Anthony to do that. But for the time being I'm going to test it on OS X which should effect the least amount of our users and what I have direct control over upgrading if there are any problems.

I just reconnected my iMac to Milkyway and got one task, just to do a quick test.

---

Yeah, it seems like CP (and Anthony) are working on new version of the 58x0 application, which will solve this problem. Hopefully they'll be out soon.

Just confirmed that the problem is indeed the format definition of the arrays in GPU memory. I have to thank again loeakaodas, who found and linked the appropriate KB article from AMD. The solution offered there appears to work (tested independently by two members of my team on their HD5850 GPUs).

Unfortunately it took a bit longer to resolve this issue, as the format definitions have changed and are not compatible between different CAL versions (i.e. between 1.3 and 1.4). But as the HD5800 GPUs require a driver with CAL 1.4 support, that is not a showstopper. But as a consequence, I will now provide only builds for CAL 1.4 (i.e. Catalyst 9.3 and up). As newer Catalyst versions appear to run quite well also for older GPUs, I think it is about time for this step.

Just give me a few more minutes to compile the different versions. I will post the links in the number crunching section so Travis/Anthony can upload them as stock apps and everybody with a HD58x0 GPU can use them as soon as possible.

@Travis:
You may consider to reject any results calculated on HD5800 GPUs with application versions prior to 0.23. Older GPUs can use older versions without a problem.

I will get them up ASAP as well.

---

Yeah, it seems like CP (and Anthony) are working on new version of the 58x0 application, which will solve this problem. Hopefully they'll be out soon.

Just confirmed that the problem is indeed the format definition of the arrays in GPU memory. I have to thank again loeakaodas, who found and linked the appropriate KB article from AMD. The solution offered there appears to work (tested independently by two members of my team on their HD5850 GPUs).

Unfortunately it took a bit longer to resolve this issue, as the format definitions have changed and are not compatible between different CAL versions (i.e. between 1.3 and 1.4). But as the HD5800 GPUs require a driver with CAL 1.4 support, that is not a showstopper. But as a consequence, I will now provide only builds for CAL 1.4 (i.e. Catalyst 9.3 and up). As newer Catalyst versions appear to run quite well also for older GPUs, I think it is about time for this step.

Just give me a few more minutes to compile the different versions. I will post the links in the number crunching section so Travis/Anthony can upload them as stock apps and everybody with a HD58x0 GPU can use them as soon as possible.

@Travis:
You may consider to reject any results calculated on HD5800 GPUs with application versions prior to 0.23. Older GPUs can use older versions without a problem.

Awesome! Great news ;) If you guys let me know where they are available for download I'll make a news post.

---

... the format definitions have changed and are not compatible between different CAL versions (i.e. between 1.3 and 1.4). But as the HD5800 GPUs require a driver with CAL 1.4 support, that is not a showstopper. But as a consequence, I will now provide only builds for CAL 1.4 (i.e. Catalyst 9.3 and up). As newer Catalyst versions appear to run quite well also for older GPUs, I think it is about time for this step.

Also any person still using an older card with CAL 1.3 could still continue using their current app (rather than upgrading to CAL 1.4 and the corrected app) since (until Travis pulls the plug on Milkyway2) the old app would continue to give correct answers on their old hardware. People in that category should make preparations to upgrade to CAL 1.4 as they would seem to need that once Milkyway3 replaces Milkyway2.

Just give me a few more minutes to compile the different versions. I will post the links in the number crunching section so Travis/Anthony can upload them as stock apps and everybody with a HD58x0 GPU can use them as soon as possible.

Thank you very much for sorting this out so quickly.

---

Cheers,
Gary.

Awesome! Great news ;) If you guys let me know where they are available for download I'll make a news post.

You can find it here.

When you set it up as stock app, be sure to exchange also the brook##.dll files as the changes there are a crucial part of the solution.

Glad I could help.

---

Glad I could help.

Yeah, thank you very much for the good find :)

---