Yes, I always leave at least one core free to handle GPU load, and nothing has changed. I just started noticing that I wasn't getting any MW units. I still get lots of SETI units, but they are all CPU only. The only project I can get to pull any GPU units is Colatz.

I may have to completely remove BOIC and reinstall it and see if that helps.

What does BOINC log say about GPU task requests?

Just noticed you posted ages ago, sorted now?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

I just attached with a R7 240 (Oland) GPU and I also get the BOINC statement

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

Of course it does (OpenCL 1.2) and it also has Double Precision capability.
IMHO this points to a detection/identification issue on the server side, as the Oland GPU is not an R600 (R38xx) (?)

---

Which driver are you using?

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

I'm using the latest Catalyst 14.4 WHQL Driver.

To rule out any Driver issue, I completely un- and re-installed the entire Driver package to make sure (on my Host with HD7790 Bonaire GPU). It didn't make any difference however.

My System with the R7 240 Oland GPU is an absolutely fresh Windows install and also uses the Cat 14.4 WHQL.

The only difference I can spot in the BOINC host listing is that the GPUs not getting any Work are listed without their Series/ID.

Example (getting no work, Win7 64bit w/ latest Cat 14.4 WHQL) :

AMD Bonaire (1024MB) OpenCL: 1.02
AMD Oland (2048MB) OpenCL: 1.02

(getting work, Vista 64bit w/ latest Cat 13.12 WHQL )
AMD AMD Radeon HD 7700 series (Capeverde) (1024MB) driver: 1.4.1848 OpenCL: 1.02

Other projects list these Hosts with their GPUs in exactly the same manner but have no issues distributing work to them, so technically it shouldn't make a difference.
Hence my suspicion Milkyway relies on other tables/means of GPU identification than them (which I think might be the cause of the issues).
After all, it clearly misidentifies the Oland GPU as an old HD38xx series (RV6xx) and thus claims lack of OpenCL support.

---

Other projects list these Hosts with their GPUs in exactly the same manner but have no issues distributing work to them, so technically it shouldn't make a difference.
Hence my suspicion Milkyway relies on other tables/means of GPU identification than them (which I think might be the cause of the issues).
After all, it clearly misidentifies the Oland GPU as an old HD38xx series (RV6xx) and thus claims lack of OpenCL support.

I wonder if this requires a full Server side software update, which they may not have done in a while.

From the looks of it - it would seem so.

But not having seen an official response to the problem, I don't even know if the staff is working on it or not.
If they don't, they'll gradually lose more and more GPU power, as all modern AMD cards will fail to get work assigned.

---

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

Thats after upgrading HD7970 to an R9 290, it must be a MW server issue as I am getting OpenCL work units from SETI.

I've replaced the HD7790 (Bonaire) against a HD7850 (Pitcairn) for a test, using the already installed Catalyst 14.4 Driver - and as expected MilkyWay immediately recognized the GPU and distributed work.

The MilkyWay BOINC Server really needs at least updated GPU identification tables.

---

I've replaced the HD7790 (Bonaire) against a HD7850 (Pitcairn) for a test, using the already installed Catalyst 14.4 Driver - and as expected MilkyWay immediately recognized the GPU and distributed work.

The MilkyWay BOINC Server really needs at least updated GPU identification tables.

Yup I agree, the only problem is no Admins seem to be reading this thread!! Blurf are you in here?

I've replaced the HD7790 (Bonaire) against a HD7850 (Pitcairn) for a test, using the already installed Catalyst 14.4 Driver - and as expected MilkyWay immediately recognized the GPU and distributed work.

The MilkyWay BOINC Server really needs at least updated GPU identification tables.

Yup I agree, the only problem is no Admins seem to be reading this thread!! Blurf are you in here?

I don't handle the GPU identification tables but I have escalated the concern to Jake Weiss.

---

Hey all,

I actually mentioned working on GPU identification on the server around the office recently in another context. It is definitely on my list of things I plan on doing in the near future.

Jake W.

Ah, so this is a server-side issue why MW@H won't download WUs for my GTX 970? Whew, thought it was me :)

For you, an app_info should have this. At least for the GPU.

<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_nvidia_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_nvidia_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_nvidia_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>NVIDIA</type>
<count>1.0000</count>
</coproc>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_nvidia.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_nvidia</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>NVIDIA</type>
<count>1.0000</count>
</coproc>
</app_version>
</app_info>

---

Hey all,

I actually mentioned working on GPU identification on the server around the office recently in another context. It is definitely on my list of things I plan on doing in the near future.

Jake W.

So its been around 2 months now and this issue still doesn't seem to be fixed and haven't seen anything in the way of news about it either in a while....

Hi guys, i have 290X and im not able download gpu units, even there are WUs available for download. Ive got a message about not supported gpu before, but after upgrade of gpu drivers and BOINC manager, everything is fine, except of no work :-)



19. 12. 2014 7:36:25 | Milkyway@Home | Sending scheduler request: Requested by user.
19. 12. 2014 7:36:25 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
19. 12. 2014 7:36:26 | Milkyway@Home | Scheduler request completed: got 0 new tasks

many thanks for any idea.

p.

Hi guys, i have 290X and im not able download gpu units, even there are WUs available for download. Ive got a message about not supported gpu before, but after upgrade of gpu drivers and BOINC manager, everything is fine, except of no work :-)



19. 12. 2014 7:36:25 | Milkyway@Home | Sending scheduler request: Requested by user.
19. 12. 2014 7:36:25 | Milkyway@Home | Requesting new tasks for AMD/ATI GPU
19. 12. 2014 7:36:26 | Milkyway@Home | Scheduler request completed: got 0 new tasks

many thanks for any idea.

p.

I replied in the other thread you ALSO posted this too.

Message 61886 - Posted: 12 Jun 2014, 16:32:31 UTC

I wrote here six months ago , we can not run tasks on the cards R290 + X

Sorry, Jozef, but you are mistaken.

I have a Radeon R9 290X running tasks quite happily and fairly speedily as well.

I was guided by another forum member to create a custom app_info file for the purpose and put the relevant EXE files into the project folder manually.

See the second half of this thread for details:-

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3457

The BOINC manager reports the tasks as "Local:milkyway..." and cannot properly estimate the job length, but it crunches away regardless.

Of course it would be nice if the project technicians were to update the server code to recognise cards that have been around for years now, but that is another discussion.

Looks like the original listing needs to be updated. Since the CUDA application is no longer used, some of the older NVidia cards that can only do OpenCL 1.0 will no longer work on this project.

---

My event log says:
1/16/2015 4:28:31 PM | rosetta@home | Requesting new tasks for AMD/ATI GPU
1/16/2015 4:28:32 PM | | App version needs OpenCL but GPU doesn't support it
1/16/2015 4:28:32 PM | Milkyway@Home | [error] App version uses non-existent ATI GPU
1/16/2015 4:28:32 PM | Milkyway@Home | [error] Missing coprocessor for task de_80_DR8_Rev_8_5_00004_1413455402_44869832_0; aborting

So it seems my app is requesting tasks for a GPU I appear not to have? Why would that be?
I actually have a Radeon 4800, is that not supported?