so with my openCl configuration, how many providers do I have?
FAH keeps saying my openCl is not detected, what do I search for to find the right packages. I am hitting a wall with finding people with similar setups to mine
That’s the configuration file the OpenCL ICD loader reads to find OpenCL providers. Then maybe you can do rpm -qf /etc/OpenCL/vendors/mesa.icd or rpm -qf /etc/OpenCL/vendors/pocl.icd, for example, to find what RPM installed what provider.
Figured it out, going to mark this post as the solution!
The issue was the conflicting OpenCL libraries, I had installed. The toughest part of setting this up was figuring out what was broken. If you have similar issues to this viewing the outputs of FAHClient from terminal the terminal would help solve this issue. The types of OpenCL errors as seen below.
OpenCL: Not detected: clGetDeviceIDs() returned -1
this error I think combined with the other errors I think helped people determine my OpenCL was the issue.
Failed to start core: OpenCL device matching slot 1 not found, try setting 'opencl-index' manually
looking online for this error gave prompted either no results or results that were for different issues
Once we figured out it was a OpenCL was causing the issues, it was a matter of figuring out which were the specific packages
Turns out it was a issue with the mesa-libOpenCL, which was when installed Dec 18, when I installed the nvidia drivers from someone else’s packages instead of nvidia’s official packages.
running sudo dnf remove mesa-libOpenCL in the terminal uninstalled the mesa OpenCL libraries. Once I uninstalled the mesa OpenCL library, FAH automatically started folding on my nvidia 2070
Massive thanks to @zlynx for helping me figure out how to interpret the output of clinfo from the terminal and which the OpenCL library was causing the errors.
Hopefully someone will find this post when searching for similar outputs
This will be very relevant considering that modern distros are far enough ahead of the legacy codebase that new users wanting to contribute will fall victim to this gotcha. Thanks for your tenacity in the wake of this issue!