The GPU-Z OpenCL driver has a problem. The OpenCL module is installed but it is not being used. This results in an error message.
This is a known and rather annoying issue. The OpenCL error is only displayed when OpenCL is compiled with the GPU support enabled. This problem happens on both Intel and AMD chips, but the AMD chip used by AMD’s Fusion platform is the only one that has this problem.
You can fix it by enabling the GPU support for AMD chipsets. This has nothing to do with the OpenCL problem. They may know about this problem because they’re having the problem themselves.
AMD should know about this problem. If they don’t, I don’t know who does, and it’s their responsibility.
The problem of the opencl error is fixed in the opencl-0.8.10. The bug is fixed in the latest opencl-0.8.12.
As far as we know, there is no way to fix the AMD chip on the AMDs platform, and that would be like fixing the AMD chip on the AMDs Fusion platform, but that would be the most complicated thing to do. The problem, however, is that the AMD chip does not support the AMDs OpenCL toolkit, it supports the opencl-0.8.10, but the problem is that it doesn’t support OpenCL.
OpenCL-0.8.11 is used by the opencl-0.8.10 as a default tool in some applications, but not necessarily as a default tool in others. Many of the applications we run on opencl-0.8.11 are not available in AMDs.
The solution is to use AMDs free opencl-0.11 tool. The problem is that the opencl-0.11 tool does not support OpenCL.
This is a problem that we have run into in the past, which is why we have switched over to opencl-0.11 in the past few months. It’s a bit of a chicken and egg problem: AMDs OpenCL toolkit is newer that openscl-0.11, and the newer one is only supported if AMDs OpenCL toolkit is used.
However, at least one user on reddit has a workaround: You can use the opencl-0.11 tool to enable OpenCL on the command line and then use AMDs opencl-0.11 tool to build a kernel that will work.