12/30/2015 3:32:39 PM App version needs CAL but GPU doesn't support it
12/30/2015 3:32:39 PM PrimeGrid Application uses missing ATI GPU

Adjust which GPU application you want to use at Primegrid

Proth Prime Search Sieve (PPS-Sieve) and all Generalized Fermat Prime Searches support OpenCL. Then the message will change, I bet.

Your GPU doesn't support CAL anymore, but for Primegrid you probably have an application chosen that only does/did CAL.

The way the message came up it looked it it was associated with SETI@home.
I was only doing (PPS-Sieve) OpenCL on PrimeGrid with my HD 6870 before upgrading to the R9 390x. I must have had something in my client_state.xml referring to some older CAL app. Given it looks like they only support the OpenCL apps now. After doing a project reset on PrimeGrid that message has gone away. So whatever it was is cleaned up. Plus the GPUs & CPUs are being detected well.
I might be able to try popping in a CAL GPU at the same time to see what BOINC does with that. My PSU should be able to handle my old HD 5750 at the same time. At least for detection.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

By the way, the just released 7.6.22 does not have this new code. For people who do upgrade and don't see the new AMD GPU detection.

---

12/30/2015 3:32:39 PM App version needs CAL but GPU doesn't support it
12/30/2015 3:32:39 PM PrimeGrid Application uses missing ATI GPU

Adjust which GPU application you want to use at Primegrid

Proth Prime Search Sieve (PPS-Sieve) and all Generalized Fermat Prime Searches support OpenCL. Then the message will change, I bet.

Your GPU doesn't support CAL anymore, but for Primegrid you probably have an application chosen that only does/did CAL.

---

I have "intel_sdk_for_ocl_applications_2013_x64_setup.exe"

That's also a possibility. Forgot I had an Intel SDK installed on my system, so it's probably coming from that. Thanks for the reminder. :)

---

Oh damn, that's true, when doing debug it needs special builds of the libraries AND their large *.pdb versions. Not going to pack all that in, as then the download becomes a little too large.

I've rebuilt as release with the correct libraries.
http://boincfaq.mundayweb.com/resources/alpha/boinc-7.6.23.r.zip

(removing the previous version)

I'm a bit unsure why my other machine will run the previous build. Given I don't have any VS libraries installed. However the 7.6.23r my main machine liked just fine. Looks like we are detecting everything correctly.

12/30/2015 3:32:39 PM Starting BOINC client version 7.6.23 for windows_x86_64
12/30/2015 3:32:39 PM log flags: sched_ops
12/30/2015 3:32:39 PM Libraries: libcurl/7.42.1 OpenSSL/1.0.2a zlib/1.2.8
12/30/2015 3:32:39 PM Data directory: z:\BOINC
12/30/2015 3:32:39 PM Running under account nimda
12/30/2015 3:32:39 PM OpenCL: AMD/ATI GPU 0: AMD Radeon (TM) R9 390 Series (driver version 1800.5 (VM), device version OpenCL 2.0 AMD-APP (1800.5), 8192MB, 8192MB available, 3802 GFLOPS peak)
12/30/2015 3:32:39 PM OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 10.18.14.4156, device version OpenCL 1.2, 1195MB, 1195MB available, 32 GFLOPS peak)
12/30/2015 3:32:39 PM OpenCL CPU: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 4.2.0.148, device version OpenCL 1.2 (Build 148))
12/30/2015 3:32:39 PM OpenCL CPU: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1800.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1800.5))
12/30/2015 3:32:39 PM SETI@home Found app_info.xml; using anonymous platform
12/30/2015 3:32:39 PM App version needs CAL but GPU doesn't support it
12/30/2015 3:32:39 PM PrimeGrid Application uses missing ATI GPU
12/30/2015 3:32:39 PM Host name: HAL9000II
12/30/2015 3:32:39 PM Processor: 4 GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz [Family 6 Model 60 Stepping 3]
12/30/2015 3:32:39 PM Processor features: <blah blah blah>
12/30/2015 3:32:39 PM OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
12/30/2015 3:32:39 PM Memory: 15.70 GB physical, 31.40 GB virtual
12/30/2015 3:32:39 PM Disk: 40.00 GB total, 18.11 GB free
12/30/2015 3:32:39 PM Local time is UTC -5 hours

It looks like we have a new message about non CAL GPUs now? Maybe that has been in 7.6.x for a while. I've been using 7.4.42 until testing this.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

30/12/2015 17:31:26 | | OpenCL CPU: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))

I don't think there ever was a problem detecting the Intel GPU, because you only have it installed and the motherboard chipset drivers have added the Intel OpenCL driver for the CPU. Which is what shows there.

Actually, I added it myself round about

Preliminary Change Log 7.2.20 --> 7.2.21:

client: Detect OpenCL CPUs with the latest Intel drivers.

I have "intel_sdk_for_ocl_applications_2013_x64_setup.exe" downloaded on the same day as that checkin - I think you and I both helped Rom check that it worked. I don't think I've updated the chipset drivers since then, and I'm not sure whether OpenCL would be included. [checks - the SDK says "OpenCL CPU Runtime version - 3.0.0.63463", so maybe I have]

30/12/2015 17:31:26 | | OpenCL CPU: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))

I don't think there ever was a problem detecting the Intel GPU, because you only have it installed and the motherboard chipset drivers have added the Intel OpenCL driver for the CPU. Which is what shows there.

The problem was with people who have an AMD CPU or GPU or both, and an AMD (APP) OpenCL driver installed. The AMD OpenCL driver would not detect their CPU correctly, or at least not show what kind of CPU they had.

So... my CPU was detected as:
26/12/2015 17:59:02 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
26/12/2015 17:59:02 | | OpenCL CPU: (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

And is now detected as:
30/12/2015 19:00:18 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
30/12/2015 19:00:18 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

The first line shows the Intel OpenCL driver details.
The second line shows the AMD OpenCL driver details.

---

Oh damn, that's true, when doing debug it needs special builds of the libraries AND their large *.pdb versions. Not going to pack all that in, as then the download becomes a little too large.

I've rebuilt as release with the correct libraries.
http://boincfaq.mundayweb.com/resources/alpha/boinc-7.6.23.r.zip

(removing the previous version)

---

I continued this until I got to a dll I didn't have. It was either msvcp120.dll or msvcr120.dll. BOINC only includes msvcp100.dll & msvcr100.dll. So I stopped there.

I hit that the first time I copied a self-build to a machine that didn't have VS2013 installed locally.

So I added the workround to the build instructions.

Rom added code that should fix the OpenCL CPU detection problem.
Should work on AMD CPUs, but please test it on the Intel CPUs as well.

Self-build from Head, I got

30/12/2015 17:31:25 | | Starting BOINC client version 7.7.0 for windows_x86_64
30/12/2015 17:31:26 | | OpenCL: Intel GPU 0: Intel(R) HD Graphics 4600 (driver version 10.18.10.3621, device version OpenCL 1.2, 1298MB, 1298MB available, 184 GFLOPS peak)
30/12/2015 17:31:26 | | OpenCL CPU: Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 3.0.1.10878, device version OpenCL 1.2 (Build 76413))

Rom added code that should fix the OpenCL CPU detection problem.
Should work on AMD CPUs, but please test it on the Intel CPUs as well.

Still called BOINC 7.6.23 x64, but a debug version this time. I added in BOINC Manager as well.
http://boincfaq.mundayweb.com/resources/alpha/boinc_7.6.23.zip

On my i5-2500K it now does this:
30/12/2015 17:03:37 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
30/12/2015 17:03:37 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

I copied the files on top of a 7.6.22 installation. Instead of my edited 7.4. When I ran that version on my machine with a R9 390x I got this.



So I copied zlib1.dll to zlib1d.dll. Then I got the same for libcurl.dll. I continued this until I got to a dll I didn't have. It was either msvcp120.dll or msvcr120.dll. BOINC only includes msvcp100.dll & msvcr100.dll. So I stopped there.

Oddly enough my J1900 system, which I tested first, ran it without any issues. OpenCL CPU detection looked the same as 7.6.22 vanilla.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

Rom added code that should fix the OpenCL CPU detection problem.
Should work on AMD CPUs, but please test it on the Intel CPUs as well.

Still called BOINC 7.6.23 x64, but a debug version this time. I added in BOINC Manager as well.
http://boincfaq.mundayweb.com/resources/alpha/boinc_7.6.23.zip

On my i5-2500K it now does this:
30/12/2015 17:03:37 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
30/12/2015 17:03:37 | | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

---

Online is shown:
[4] AMD AMD Radeon (TM) R9 Fury Series (4096MB) OpenCL: 2.0

(maybe just one time 'AMD'?)

The first "AMD" is hard-coded in the web-page-generating code:
https://github.com/BOINC/boinc/blob/aba6d8de95e4f60118ea34e8e1d60836bb43c326/html/inc/host.inc#L120
https://github.com/BOINC/boinc/blob/edfa2bf428934ccfa17175465c5768f35b726c52/html/inc/host.inc#L265

} else if ($d[0] == "CAL") {
$str .= "AMD";

(this obviously is to prepend the generic names like "Fiji" "Turks" "Pitcairn" ...)


The second "AMD" is part of the full string as returned by the driver:
"AMD Radeon (TM) R9 Fury Series"

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

OpenCL CPU: (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

This is missing now @ 'OpenCL CPU': 'Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz'

Might be a problem with how the AMD OpenCL driver detects newer CPUs, not per se a problem with the added code, as it shows my CPU in the normal way:

26/12/2015 17:59:02 |  | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
26/12/2015 17:59:02 |  | OpenCL CPU:  (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

Because the normal detection of the CPU happens further down in the client, and this OpenCL detection of the CPU only happens because you've got an AMD driver installed, it's kind of moot. All the added code does is read the AMD GPU's board name from the GPU itself, it does nothing with the CPU.

I'll forward it to the developers, but wonder if it's not a coincidence. And what happens when someone installs the OpenCL driver for their CPU, instead of relying on the one from AMD for AMD GPUs.

Online is shown:
[4] AMD AMD Radeon (TM) R9 Fury Series (4096MB) OpenCL: 2.0

(maybe just one time 'AMD'?)

It's always shown this double, as far as I know, and whether it's a side effect of the driver, or something in the database I don't know. You'll have to take that up with the BOINC developers or the project. If you check at other projects, you'll see that for loads of AMD GPUs correctly detected by name this mention of AMD happens twice.

I'm pretty sure that is something on the server side of things. It occurs for all non NVIDIA GPUs.
INTEL Intel(R) HD Graphics (1195MB) OpenCL: 1.2
In my client I changed every instance of AMD to ATI.
AMD ATI Radeon HD 6870 (Barts XT) (1024MB) driver: 1.4.1848 OpenCL: 1.2

It is likely that BOINC displays the VENDOR in caps & the rest comes form the GPU. So Intel & AMD are just placing their name at the start of the device name. Aa that is what I see in clinfo:
Board name: AMD Radeon HD 6800 Series
Name: Intel(R) HD Graphics
Instead of:
Board name: Radeon HD 6800 Series
Name: HD Graphics

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

It might already be in the works, but while this is being developed. Perhaps the OpenCL value in Driver Version could be polled as well when using this detection method? It would be helpful to see next to a users GPU for troubleshooting. Instead of digging into their returned results.

That's already being done.

From my 7.6.22 BOINC:
24/12/2015 16:22:34 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7850/7870 series (Pitcairn) (driver version 1912.5 (VM), device version OpenCL 1.2 AMD-APP (1912.5), 2048MB, 2008MB available, 6400 GFLOPS peak)

So a user could give that detail to people, or we should ask that it's stored in the database on the people's account page instead of the CAL version number.

The information is sent to the server via the sched_request*.xml file:

      <opencl_platform_version>OpenCL 2.0 AMD-APP (1912.5)</opencl_platform_version>
      <opencl_device_version>OpenCL 1.2 AMD-APP (1912.5)</opencl_device_version>

Now, I've also seen that Rom added the AMD detection code to the present 7.6 branch and so I built myself a client using all that source code. Here's what it says about my GPU now:

24/12/2015 18:55:33 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7850/7870 series (Pitcairn) (driver version 1912.5 (VM), device version OpenCL 1.2 AMD-APP (1912.5), 2048MB, 2008MB available, 6400 GFLOPS peak)

Yes, spot the difference. There isn't any. Looks like maybe the previous code

Given the CAL version hasn't changes in over 2 years, CAT 13.9, & isn't present on newer GPUs. Displaying the OpenCL version in the host information seems like a good idea. Would that replace the CAL version or would both be displayed for GPUs that support both? Perhaps it would be display CAL version if null display OpenCL version?
Would that effect projects that use the CAL version for app detection? Until 15.11 the OpenCL version has always been lower than the CAL version. These two values are probably stored & used differently on the server end of things.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the BP6/VP6 User Group today!

OpenCL CPU: (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

This is missing now @ 'OpenCL CPU': 'Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz'

Might be a problem with how the AMD OpenCL driver detects newer CPUs, not per se a problem with the added code, as it shows my CPU in the normal way:

26/12/2015 17:59:02 |  | OpenCL CPU: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 1.2, device version OpenCL 1.2 (Build 63463))
26/12/2015 17:59:02 |  | OpenCL CPU:  (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

Because the normal detection of the CPU happens further down in the client, and this OpenCL detection of the CPU only happens because you've got an AMD driver installed, it's kind of moot. All the added code does is read the AMD GPU's board name from the GPU itself, it does nothing with the CPU.

I'll forward it to the developers, but wonder if it's not a coincidence. And what happens when someone installs the OpenCL driver for their CPU, instead of relying on the one from AMD for AMD GPUs.

Online is shown:
[4] AMD AMD Radeon (TM) R9 Fury Series (4096MB) OpenCL: 2.0

(maybe just one time 'AMD'?)

It's always shown this double, as far as I know, and whether it's a side effect of the driver, or something in the database I don't know. You'll have to take that up with the BOINC developers or the project. If you check at other projects, you'll see that for loads of AMD GPUs correctly detected by name this mention of AMD happens twice.

---

BOINC v7.6.22:

OpenCL: AMD/ATI GPU 0: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 1: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 2: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 3: Fiji (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL CPU: Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

Online is shown:
[4] AMD Fiji (4096MB) OpenCL: 2.0


BOINC v7.6.23 (Ageless Mod):

OpenCL: AMD/ATI GPU 0: AMD Radeon (TM) R9 Fury Series (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 1: AMD Radeon (TM) R9 Fury Series (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 2: AMD Radeon (TM) R9 Fury Series (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL: AMD/ATI GPU 3: AMD Radeon (TM) R9 Fury Series (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 5376 GFLOPS peak)	
OpenCL CPU:  (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx), device version OpenCL 1.2 AMD-APP (1912.5))

This is missing now @ 'OpenCL CPU': 'Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz'

Online is shown:
[4] AMD AMD Radeon (TM) R9 Fury Series (4096MB) OpenCL: 2.0

(maybe just one time 'AMD'?)


BOINC show AMD CPUs (e.g.):
AuthenticAMD
AMD FX(tm)-9370 Eight-Core Processor [Family 21 Model 2 Stepping 0]
(8 processors)
-> ™ as (tm).
Maybe this way also for GPUs?


BTW.
I opened boinc.exe with a Hex Editor - and changed:
AMD Radeon R9 Fury/R9 Nano/R9 Fury X/R9 Fury X2 (Fiji)
- to:
AMD Radeon R9 Fury X (Fiji)
- but with no effect, still the above is shown.

Is there a way to let show (just) the real name?


Thanks.

---

Thanks for the test and the confirmation it requires that the GPU does not support CAL detection on the hardware level, Mike. Forwarded to the developers as "working as planned". :)

You are welcome Jord.
If thats O.K. i will let it run to see how it works for me.

---

With each crime and every kindness we birth our future.

Thanks for the test and the confirmation it requires that the GPU does not support CAL detection on the hardware level, Mike. Forwarded to the developers as "working as planned". :)

---

25.12.2015 11:22:54 Starting BOINC client version 7.6.23 for windows_x86_64
25.12.2015 11:22:54 log flags: file_xfer, sched_ops, task, sched_op_debug
25.12.2015 11:22:54 Libraries: libcurl/7.42.1 OpenSSL/1.0.2a zlib/1.2.8
25.12.2015 11:22:54 Data directory: D:\BOINC
25.12.2015 11:22:54 Running under account Mike
25.12.2015 11:22:55 OpenCL: AMD/ATI GPU 0: AMD Radeon (TM) R9 380 Series (driver version 1912.5 (VM), device version OpenCL 2.0 AMD-APP (1912.5), 4096MB, 4096MB available, 2206 GFLOPS peak)
25.12.2015 11:22:55 OpenCL CPU: (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1912.5 (sse2,avx,fma4), device version OpenCL 1.2 AMD-APP (1912.5))
25.12.2015 11:22:55 SETI@home Found app_info.xml; using anonymous platform
25.12.2015 11:22:55 Version change (7.6.9 -> 7.6.23)
25.12.2015 11:22:55 Host name: MikeFX
25.12.2015 11:22:55 Processor: 8 AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor [Family 21 Model 2 Stepping 0]
25.12.2015 11:22:55 Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 fma cx16 sse4_1 sse4_2 popcnt aes f16c syscall nx lm avx svm sse4a osvw ibs xop skinit wdt lwp fma4 tce tbm topx page1gb rd
25.12.2015 11:22:55 OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
25.12.2015 11:22:55 Memory: 3.92 GB physical, 6.91 GB virtual
25.12.2015 11:22:55 Disk: 945.56 GB total, 685.11 GB free
25.12.2015 11:22:55 Local time is UTC +1 hours

---

With each crime and every kindness we birth our future.