Will try it later on my R9 380.

---

With each crime and every kindness we birth our future.

One round with the default CAL detection case also marked out.

25-Dec-2015 10:12:44 [---] CAL: ATI GPU 0: (CAL version 1.4.1848, 2048MB, 2008MB available, 6400 GFLOPS peak)
25-Dec-2015 10:12:44 [---] OpenCL: AMD/ATI GPU 0: (driver version 1912.5 (VM), device version OpenCL 1.2 AMD-APP (1912.5), 2048MB, 2008MB available, 6400 GFLOPS peak)

Neeh, my GPU is being seen as CAL capable. Perhaps that it works if I mark out all the CAL detection code, but that's for some later time. One other option is of course for someone with a non-CAL capable AMD GPU to test this BOINC executable. Preferably an advanced user who knows what he's doing.

A client with the new code can be found here. Your GPU doesn't support CAL through hardware when you have an R5, R7, R9 etc. GPU.

---

Rom says it will only be used when CAL cannot detect the GPU, so I remarked out my GPU in the client code and rebuild.

Not getting any better. ;-)
25/12/2015 08:58:01 | | CAL: ATI GPU 0: AMD Radeon HD (unknown) (CAL version 1.4.1848, 2048MB, 2008MB available, 6400 GFLOPS peak)
25/12/2015 08:58:01 | | OpenCL: AMD/ATI GPU 0: AMD Radeon HD (unknown) (driver version 1912.5 (VM), device version OpenCL 1.2 AMD-APP (1912.5), 2048MB, 2008MB available, 6400 GFLOPS peak)

---

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

---

This tells us that AMD started implementing CL_DEVICE_BOARD_NAME_AMD prior to officially indicating they did. SDK 2.6 may have had this feature as beta. Maybe it goes back even further.
Given the documentation for the feature states OpenCL 1.2. It is likely the BOINC devs will choose to only lookup the information when OpenCL 1.2+ is detected.

---

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

 
clinfo.exe from the driver shows 'Board name':
(I may post the full text (156 lines) if requested)

in Command Prompt (cmd.exe) typed 'clinfo'
clinfo.exe (159 744 bytes, 09.11.2011) was started from D:\Program Files\AMD APP\bin\x86\ (which is in the %Path%)
clinfo.exe itself started amdocl_as.exe from the same directory

56b986d13c74903fe27b71ba85c76037 *amdocl_as.exe
dd169b5f417931d642e9c33706c8e347 *clinfo.exe

Number of platforms:				 1
  Platform Profile:				 FULL_PROFILE
  Platform Version:				 OpenCL 1.1 AMD-APP (831.4)
  Platform Name:				 AMD Accelerated Parallel Processing
  Platform Vendor:				 Advanced Micro Devices, Inc.
  Platform Extensions:				 cl_khr_icd cl_amd_event_callback cl_amd_offline_devices


  Platform Name:				 AMD Accelerated Parallel Processing
Number of devices:				 2
  Device Type:					 CL_DEVICE_TYPE_GPU
  Device ID:					 4098
  Board name:					 AMD Radeon HD 6570
  Max compute units:				 6
  Max work items dimensions:			 3
    Max work items[0]:				 256
    Max work items[1]:				 256
    Max work items[2]:				 256
  Max work group size:				 256

Using another clinfo.exe (713 728 bytes, 21.02.2011) (which don't start any other .exe)
d470daaaef37fc6499b3bc5bc61ad553 *clinfo.exe
do Not show 'Board name' (and some other ~20 lines are missing - 136 lines total log)

Number of platforms:				 1
  Platform Profile:				 FULL_PROFILE
  Platform Version:				 OpenCL 1.1 AMD-APP (831.4)
  Platform Name:				 AMD Accelerated Parallel Processing
  Platform Vendor:				 Advanced Micro Devices, Inc.
  Platform Extensions:				 cl_khr_icd cl_amd_event_callback cl_amd_offline_devices


  Platform Name:				 AMD Accelerated Parallel Processing
Number of devices:				 2
  Device Type:					 CL_DEVICE_TYPE_GPU
  Device ID:					 4098
  Max compute units:				 6
  Max work items dimensions:			 3
    Max work items[0]:				 256
    Max work items[1]:				 256
    Max work items[2]:				 256
  Max work group size:				 256

---

 


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

Rom's been busy, since I sent him that info.

client: AMD decided to put the more descriptive version of the GPU name in a custom extension, so use the custom attribute to get the board name.
lib: Add defines for Nvidia specific OpenCL extensions. To be used later
lib: Add more OpenCL defines and HTTP references to the extension documentation

So, it looks like Nvidia's OpenCL capability detection is getting worked on as well. Note, none of this is coming to BOINC 7.6, I think. This will probably warrant a new testing version, big code change and all.

Thanks for the initial hint, Hal. Kudos have been forwarded up the line. :)

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.

Like how we see:
AMD AMD Radeon HD 7850/7870 series (Pitcairn) (2048MB) driver: 1.4.1848 OpenCL: 1.2

Perhaps it could be
AMD Radeon R9 390 Series (8192MB) driver: 1912.5 OpenCL: 2.0
or
AMD Radeon R9 390 Series (Hawaii) (8192MB) driver: 1912.5 OpenCL: 2.0

---

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

The sentence also included this:
"so here it doesn't matter which driver you have installed"

Hmmmm, perhaps you need a new hobby.

Welcome back to my ignore list. You're in good company.

---

(Catalyst 11.12) / XP

For OpenCL 1.2 APP SDK 2.7 is needed, which starts at Catalyst 12.4

The sentence also included this:
"so here it doesn't matter which driver you have installed"

So driver matters if bellow Catalyst 12.4

Nevertheless maybe cl_amd_device_attribute_query will work partially even on OpenCL 1.1 driver:

You can check by running clinfo.exe. You are looking for Board Name near the top of the information for the device.

Like this:

  Platform Name:                                 AMD Accelerated Parallel Pro
Number of devices:                               2
  Device Type:                                   CL_DEVICE_TYPE_GPU
  Vendor ID:                                     1002h
  Board name:                                    AMD Radeon HD 6300M Series

Note: You may need to use a newer clinfo.exe than the one provided with your driver.

---

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

(Catalyst 11.12) / XP

For OpenCL 1.2 APP SDK 2.7 is needed, which starts at Catalyst 12.4

The sentence also included this:
"so here it doesn't matter which driver you have installed"

So driver matters if bellow Catalyst 12.4

Nevertheless maybe cl_amd_device_attribute_query will work partially even on OpenCL 1.1 driver:
https://www.khronos.org/registry/cl/extensions/amd/cl_amd_device_attribute_query.txt
Revision History
Version 1, 2010/03/26 (Laurent Morichetti) - initial extension specification.
Version 2, 2015/03/08 (Brian Sumner) - update query list


Question is what was updated/added on 2015/03/08:

As was 2010-2014
https://web.archive.org/web/20140806045615/http://www.khronos.org/registry/cl/extensions/amd/cl_amd_device_attribute_query.txt

= Very bare for OpenCL 1.0 - only one param, no revision/change for OpenCL 1.1
https://web.archive.org/web/20100401000000*/https://www.khronos.org/registry/cl/extensions/amd/cl_amd_device_attribute_query.txt

---

 


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

Some of the newer drivers still include the old ATI CAL files

True that, but for the capability of the new board name detection OpenCL 1.2 comliancy is required, something that the early HD3xxx (OpenCL 1.0)and HD4xxx (OpenCL 1.1) GPUs didn't have, so that automatically excludes them.

All GPUs from HD5xxx onwards are at least OpenCL 1.2 complaint, so here it doesn't matter which driver you have installed, as long as it has OpenCL included and still supports the older hardware. And when it has OpenCL installed, the old CAL detection on the GPU will no longer be used, in favor of the Board Name detection.

The CAL detection which is hard-coded in the client puts old GPUs together with new GPUs, based on the code-name of the GPU (Tahiti, Pitcairn, Fiji, Hawaii). The Board Name will show the actual series the GPU belongs to, like HD 7800 Series.
I don't think the precise version can ever be detected, like HD 7870.

Having the series name is much nicer than seeing "Radeon HD 7870/7950/7970/R9 280X series (Tahiti)". There can be a large difference in performance between GPUs with the same base family.
The OpenCL Board Name value looks to be the name supplied by the driver. AMD likes using "xxxx Series" instead of specific names in their drivers. So users that want their specific device name to be displayed can modify the driver .inf or registry if they wish.

EDIT: Testing on my notebook with 15.7.1 I changed every instance of "AMD Radeon HD 6300M Series" to "Radeon HD 6370M" in the .inf & then the registry. However clinfo still gives me "AMD Radeon HD 6300M Series". They might have coded the name in one of the .dlls.

---

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

(Catalyst 11.12) / XP

For OpenCL 1.2 APP SDK 2.7 is needed, which starts at Catalyst 12.4
The ATI driver cheat sheet teaches you that for Cat 12.4 onwards OpenCL XP support completely dropped, so until you update the Windows on that system, you won't be able to use the full capabilities of the GPU.

Similarly, while your GPU is DirectX 11 compliant, you won't be able to use it because of Windows XP, which supports DirectX 9.0c at maximum.

There is a possibility that the 12.1 drivers have an OpenCL 1.2 preview built in, but it may also have been a specialized driver set that had that, not the full released driver set.

---

All GPUs from HD5xxx onwards are at least OpenCL 1.2 complaint, so here it doesn't matter which driver you have installed, as long as it has OpenCL included and still supports the older hardware.

For my system it seems not true:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4832843

AMD Radeon HD 6570 / Turks
ati2mtag 8.920.0.0 (Catalyst 11.12) / XP
CAL 1.4.1646
OpenCL 1.1 AMD-APP (831.4) FULL_PROFILE

Detected by GPU Caps Viewer
http://www.ozone3d.net/gpudb/gpu.php?which=3581&v=2#opencl

and SETI@home apps:
http://setiathome.berkeley.edu/result.php?resultid=4596948648


cl_amd_device_attribute_query shown among OpenCL extensions for this driver, so why there is:

Dependencies
OpenCL 1.2 is required.
https://www.khronos.org/registry/cl/extensions/amd/cl_amd_device_attribute_query.txt

Just because you use a driver that does not support OpenCL 1.2 does not mean your hardware does not support OpenCL 1.2. All GPUs from the HD 5000 series & newer support OpenCL 1.2. Apparently GPUs based on GCN 1.1 or newer support OpenCL 2.0.
I'm not sure which driver first supported OpenCL 1.2, but I would guess that it might be in SDK 2.7. Which started with Cat 12.4. OpenCL 1.2 was officially added as a spec on 2011-11-15. It could also be that no XP driver supports OpenCL 1.2.

---

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

All GPUs from HD5xxx onwards are at least OpenCL 1.2 complaint, so here it doesn't matter which driver you have installed, as long as it has OpenCL included and still supports the older hardware.

For my system it seems not true:
http://setiathome.berkeley.edu/show_host_detail.php?hostid=4832843

AMD Radeon HD 6570 / Turks
ati2mtag 8.920.0.0 (Catalyst 11.12) / XP
CAL 1.4.1646
OpenCL 1.1 AMD-APP (831.4) FULL_PROFILE

Detected by GPU Caps Viewer
http://www.ozone3d.net/gpudb/gpu.php?which=3581&v=2#opencl

and SETI@home apps:
http://setiathome.berkeley.edu/result.php?resultid=4596948648


cl_amd_device_attribute_query shown among OpenCL extensions for this driver, so why there is:

Dependencies
OpenCL 1.2 is required.
https://www.khronos.org/registry/cl/extensions/amd/cl_amd_device_attribute_query.txt

---

 


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

Some of the newer drivers still include the old ATI CAL files

True that, but for the capability of the new board name detection OpenCL 1.2 comliancy is required, something that the early HD3xxx (OpenCL 1.0)and HD4xxx (OpenCL 1.1) GPUs didn't have, so that automatically excludes them.

All GPUs from HD5xxx onwards are at least OpenCL 1.2 complaint, so here it doesn't matter which driver you have installed, as long as it has OpenCL included and still supports the older hardware. And when it has OpenCL installed, the old CAL detection on the GPU will no longer be used, in favor of the Board Name detection.

The CAL detection which is hard-coded in the client puts old GPUs together with new GPUs, based on the code-name of the GPU (Tahiti, Pitcairn, Fiji, Hawaii). The Board Name will show the actual series the GPU belongs to, like HD 7800 Series.
I don't think the precise version can ever be detected, like HD 7870.

---

But, as you see from other posts, the future BOINC versions will get the full name from (newer?) drivers
(I don't know which is the minimum ATI AMD driver version that have the extensions needed to get the full name)

Not drivers per se, but OpenCL 1.2 compliancy. In other words, all ATI/AMD GPUs that can do OpenCL 1.2, will be able to report their board name. GPUs before that time are hard-coded in the client, but that requires that the driver that's installed detects CAL on the GPU.

Newer drivers may no longer have the CAL component, because newer hardware doesn't support it anymore, but then the GPUs that use this (HD 4xxx mainly) have been deprecated long ago and are no longer supported in present drivers.

Some of the newer drivers still include the old ATI CAL files, but it looks like they are only referenced for the older not GCN GPUs. I would guess GCN GPUs support CAL as much as they support CUDA.

In fact the current 15.11 & 15.12 drivers only list 7700 & higher GPUs as supported. However there are still some lower end GPUs listed in the .inf.

---

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

But, as you see from other posts, the future BOINC versions will get the full name from (newer?) drivers
(I don't know which is the minimum ATI AMD driver version that have the extensions needed to get the full name)

Not drivers per se, but OpenCL 1.2 compliancy. In other words, all ATI/AMD GPUs that can do OpenCL 1.2, will be able to report their board name. GPUs before that time are hard-coded in the client, but that requires that the driver that's installed detects CAL on the GPU.

Newer drivers may no longer have the CAL component, because newer hardware doesn't support it anymore, but then the GPUs that use this (HD 4xxx mainly) have been deprecated long ago and are no longer supported in present drivers.

---

Now it's not possible to edit boinc.exe with a Hex Editor ...

Why? It have some check for it's checksum?
Or you don't find the string "AMD Fiji"? (this string is retrieved from the driver and is not in boinc.exe)

But, as you see from other posts, the future BOINC versions will get the full name from (newer?) drivers
(I don't know which is the minimum ATI AMD driver version that have the extensions needed to get the full name)

---

 


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

I have BOINC v7.6.22 installed.

Now it's not possible to edit boinc.exe with a Hex Editor that instead of (in my case): AMD Fiji (4096MB) OpenCL: 2.0
...it will shown: AMD Radeon R9 Fury X (Fiji) (4096MB) OpenCL: 2.0 ?

---

Rom's been busy, since I sent him that info.

client: AMD decided to put the more descriptive version of the GPU name in a custom extension, so use the custom attribute to get the board name.
lib: Add defines for Nvidia specific OpenCL extensions. To be used later
lib: Add more OpenCL defines and HTTP references to the extension documentation

So, it looks like Nvidia's OpenCL capability detection is getting worked on as well. Note, none of this is coming to BOINC 7.6, I think. This will probably warrant a new testing version, big code change and all.

Thanks for the initial hint, Hal. Kudos have been forwarded up the line. :)

---