Moderators: Site Moderators, FAHC Science Team
Both GPU's worked or work in every other application such as gaming and benchmarking. I tried numerous times to add the slot but FAH won't have it. "On client "Roadpower" 127.0.0.1
No available GPUs"Thank you. I just reinstalled the client this afternoon so I don't know why it didn't include the GPUs.txt file at the time of installation. Doing research I found that the file is supposed to be in var/lib/fahclient. It wasn't there and nor any other place. So I found the download and put it there. The GPU is now seen and being utilized.JimboPalmer wrote:There is a file GPUs.txt that should have info about your RTX 2070 Super. I am guessing yours doesn't. if you delete your copy, it should redownload
Here is info about sending us the first 200 lines of your log.
viewtopic.php?f=24&t=26036
Okay thank you Jim. Stay well.JimboPalmer wrote:I am a mere Windows user, so I am not experienced in Linux, but almost always it is file permissions. The user you are folding as lacks write permissions. I am just a Windows user, don't take me too literally. (I have not used Solaris Unix since 2002, and have never used Linux.)
That makes sense but then the question becomes why doesn't the client fetch it or check or prompt for it? You would think that it not even being included with a fresh install of the client that some sort of prompting should be going on. Is the current behavior the same on the Microsoft Windows and Mac OS sides as well?Rel25917 wrote:Gpus.txt is always changing so it is downloaded after the install.
I restarted the client plenty of times and and reinstalled it twice, it never got the GPUs.txt file on its own. In fact it seems like the safe assumption is that it never gets the file on its own. Oh well, thank you for the feed back. Hopefully this will either get fixed or I will remember it the next time I install the client or update to recently released GPU.Rel25917 wrote:Same on all, if I remember right its possible fahclient can get loaded before the network is up and running resulting in the client failing to download it. Restarting the client should cause it to get it. Failure to get it could be handled better but it is rarely a problem. Lots of the network functions need work unfortunately.
Hmm, I suspect that between AMD GPU driver installation issues on a *nix platform and the sheer quirkiness of getting the GPUs.txt file it now makes sense why there were crucial stumbling blocks for a novice *nix user like me.Joe_H wrote:Most people have no problem with the client downloading the GPUs.txt file on its first startup. Where it has been a problem is mostly on Linux installs or installs where the GPU and its drivers are not fully installed. If the GPU is not detected at all, the installer sets that GPU folding is not to be set up at all.
It seems like there needs to be a sanity check built in, IE the client looks for the file and either fetches it or warns the user that it is missing. Oh well, thank you Joe for explaining this, it was pretty vexing when stupid me was dealing with it. :[Joe_H wrote:As also mentioned, if the network is not up, the file also might not get downloaded.
Because it worked automatically on all the systems that were tested by the developer ... but not on your system.Roadpower wrote:That makes sense but then the question becomes why doesn't the client fetch it or check or prompt for it? You would think that it not even being included with a fresh install of the client that some sort of prompting should be going on. Is the current behavior the same on the Microsoft Windows and Mac OS sides as well?Rel25917 wrote:Gpus.txt is always changing so it is downloaded after the install.