Core 0x22:Version 0.0.11

[moritzgedig]

As I see the issue, you had a system with zero supported OpenCL GPUs but somehow it decided you could download a WU.

The situation was very unclear.
The reality was that there were 3 devices and that was recognized by OpenCL.
0x22 did find the GM206 correctly so and then downloaded.
Then 0x22 tried to "get the hook" and start, but at that time OpenCL failed to provide.
I did try to force device 0 but it did not make a difference.
0x22 did go for device 0, OpenCL just would not give it.

By failing to find supported hardware, it decided to make 4 CPU cores busy doing nothing productive.

I found that interesting. In a way it is how OpenCL is supposed to work. But given the fact that four CPU cores won't get anything done it is fairly useless.

[bruce]

Bottom line: FAH will NOT use the OpenCL version provided as a driver for your CPU and I consider it a bug that it tries to run FAHCore_22 on your CPUs. The server can give you an assignment for FAHCore_a* which will run productively on your CPUs (If you have a CPU slot).