Message boards :
Opencl does not always to report the the correct gpu name to the client
Message board moderation
Joined: 27 Jun 08
This is what I get for using really old graphics boards like the S9050 (AMD HD-7950 equivalent with more memory)
Windows 10 correctly reports I have a pair of RX-570 and a single S9050
AMD FirePro S9050 Radeon RX 570 Series Radeon RX 570 Series
clinfo gets the name wrong, thinks I have three RX-570 BUT all the rest of the clinfo is correct: speed, ram, 1.2 instead of 2.0, etc
C:\ProgramData\BOINC> clinfo | find /i "board name" Board name: Radeon RX 570 Series Board name: Radeon RX 570 Series Board name: Radeon RX 570 Series C:\ProgramData\BOINC>
and from event viewer: note the "GPU 2" RX-570 has unusual statistics!
BOINC (7.16.11) gets the same data as clinfo
Apps crunch just fine on all three boards with no error, but the "third RX-570" taking longer as it is a little slower than a "real" RX-570
10 10/26/2021 9:17:17 PM Starting BOINC client version 7.16.11 for windows_x86_64 14 10/26/2021 9:17:18 PM OpenCL: AMD/ATI GPU 0: Radeon RX 570 Series (driver version 2671.3, device version OpenCL 2.0 AMD-APP (2671.3), 4096MB, 4096MB available, 5095 GFLOPS peak) 15 10/26/2021 9:17:18 PM OpenCL: AMD/ATI GPU 1: Radeon RX 570 Series (driver version 2671.3, device version OpenCL 2.0 AMD-APP (2671.3), 4096MB, 4096MB available, 5243 GFLOPS peak) 16 10/26/2021 9:17:18 PM OpenCL: AMD/ATI GPU 2: Radeon RX 570 Series (driver version 2671.3, device version OpenCL 1.2 AMD-APP (2671.3), 12288MB, 12288MB available, 3226 GFLOPS peak)
Thought the Boinc developer might want to know that it is not always the Boinc app with the problem, it is the opencl stuff stuff causing the problem. At least here.
Joined: 17 Nov 16
Could be an issue with the BOINC module that interrogates the OEM API for the board names and capabilities.
Like for example the BOINC code using the wrong Nvidia API call to get the global amount of RAM on a card and only able to report a maximum of 4GB for all Nvidia cards.
But if you change the code in the module then you can call a modern version of the API and get the true amount of RAM on the card.
Still waiting for the BOINC developers to merge that pull request for the past two years. https://github.com/BOINC/boinc/issues/1773
I got impatient and fixed it myself for my client.
Copyright © 2023 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.