Folding Forum

OpenCL: Not detected

looks like you need to reinstall the driver and reboot?

Also, by default when this shows:
1:09:02:Enabled folding slot 00: PAUSED cpu:2 (not configured)

The client will wait for (not configured) to allow the donor to configure their client. If you don't it will wait and then start contributing anonymously.

nvidia drivers reinstalled, will reboot shortly. Other test says "no". But I will now reboot and reinstall .21.

nope, no dice. Everything was fine until last week or so.

So far, then:

v 7.6.21_x86 tested - nothing, installs, starts when pushed to do so by command line, but dies after "GPUs.txt". -v does not help.
v 7.5.1_x86 tested. Gives a far more thorough logfile, but still does nothing.

NVidia drivers - 456.71 - are reinstalled. These were initially installed mid-October and this is the same file for installation.

There's no registry entries? I couldn't find any.

Always with the same user. I have tried creating a local user and logging in as them, installing... no difference. Installing the service - it won't start.

I'm out of ideas at this point and my office is freezing as I've turned the heat down to cope with the machine being on most of the time....any thoughts welcome.

Just curious, if you run the task manager do you see any fah* process running that may have been started by hideconsole in the startup group? Or anything in services that could interfere with the command line starting? Just thinking out loud.

Sorry for the late answer, I though I activated email notification but obviously, I did not

I did uninstall everything data included but no joy.

My symptoms are exactly the same as bretti_kivi.

I don't see any fah* process

You have NOT successfully installed the GPU drivers from nvidia.com. When you install them, OpenCL is included and FAHClient will not start without it.

I installed NVidia 457.09 and start FaH and it works!

bretti_kivi wrote:...my office is freezing as I've turned the heat down to cope with the machine being on most of the time....any thoughts welcome.

Please note that as per the EULA, you would need permission (generally written) from the people who are allowed to make decisions on what is allowed or not to run on work systems. It can be your manager, internal IT, CISO, etc.

this is my office at home and it's my personal machine

I am beginning to despise Nvidia and graphics drivers generally. I will go get the newest Nvidia - seems to be 457.30, released Monday - and update and see what happens.

no, no change. v 20 found and downloaded and tested - nope.

I will go find a much earlier release of the 7.6 branch and test that.

but first I decided to go digging. And lo and behold, there's an error message stashed away in Event Viewer, highlightin igdrcl32.dll as a source of the problem.
What's that? one of the DLLs for the Onboard UHD 630 Graphics. In other words, the onboard graphics driver seems to be getting in the way. Why? I have no idea. I will reboot again now and see what happens.

works. Now to configure properly...

great job! some versions of cliens started tested the feasibility of the onboard graphics if i'm remembering correctly. The advised method of dealing with this is to leave the UHD slot permanently on paused.

PantherX wrote:Assuming a fresh installation of the latest version, this is what I would expect:
FAHClient can run in CLI mode (the GUI version is FAHControl).

Thanks PantherX. I actually prefer this CLI mode. v7.6.21 is working perfectly for me with Windows 10 when FAHClient is used in CLI mode.