Package Details: foldingathome-beta 7.6.21-1

Git Clone URL: (read-only, click to copy)
Package Base: foldingathome-beta
Description: Folding@Home is a distributed computing project which studies protein folding, misfolding, aggregation, and related diseases - beta version.
Upstream URL:
Licenses: custom
Conflicts: fahclient, foldingathome
Provides: fahclient, foldingathome
Submitter: dark-saber
Maintainer: dark-saber
Last Packager: dark-saber
Votes: 4
Popularity: 0.000000
First Submitted: 2017-06-02 07:14 (UTC)
Last Updated: 2021-09-12 13:32 (UTC)

Latest Comments

dark-saber commented on 2020-09-11 18:30 (UTC)



I don't have AMD GPUs currently, but I guess it's an upstream issue, and I'm unsure if it's already known or not, but several people have reported issues with OpenCL. At this point, I'd probably suggest to revert to 7.6.13 (aur/foldingathome?) until the next beta release and then, if the problem persists, report it upstream.

Wild_Penguin commented on 2020-09-11 14:45 (UTC) (edited on 2020-09-11 14:47 (UTC) by Wild_Penguin)


For some reason foldingathome does not work if it does not have a freshly configured GPU slot (amdgpu, opencl-amd). Instead I get this in the log:

14:41:57:WARNING:FS00:No OpenCL 1.2+ support detected for GPU slot gpu:-1:-1.  Disabling.
14:41:57:FS00:Initialized folding slot 00: gpu:-1:-1 - DISABLED
14:41:57:ERROR:No valid folding configuration

I've noticed these two lines (in the config file at /opt/fah/config.xml) are the culprit:

    <pci-bus v='3'/>
    <pci-slot v='0'/>

Removing those, and on the next restart foldingathome will start folding on the GPU as it should. Same can be achieved by removing these options via the GUI (FAHControl), and restarting service (just removal is not enough). However, on next shutdown, foldingathome will rewrite those options into the configuration file, and subsequent starts of the service will fail detecting the slot.

Is this an upstream issue? I can not find anything similar via search. Can other opencl-amd users confirm this?

Foldingathome (stable) has other problems with the cores on the GPU, and I'm trying to determine if this client has fixes for those.

(as a sidenote, the slots automatically added to the configuration file seem to be right according to lspci; why it still fails, I have no idea)

Buddlespit commented on 2020-04-21 14:37 (UTC)

Good job. This package gives some of us options to actually start gpu folding again. Up-voted

DNAblue2112 commented on 2020-04-20 05:24 (UTC)

That fixed it, all working again. Thanks

dark-saber commented on 2020-04-19 14:26 (UTC)


Thank you! Could you please try the updated package? --exec-directory and --data-directory options were replaced with --chdir in beta.

DNAblue2112 commented on 2020-04-19 09:50 (UTC) (edited on 2020-04-19 09:53 (UTC) by DNAblue2112)

Having an issue with the latest version. The error claims the dir doesn't exist which obviously isn't the case. I think this might be an upstream issue though?

systemd[1]: Started Folding@home distributed computing client.

FAHClient[15524]: 09:45:51:INFO(1):Read GPUs.txt

FAHClient[15524]: 09:45:51:ERROR:Exception: Invalid argument '--exec-directory=/opt/fah'

FAHClient[15524]: 09:45:51:ERROR:Caused by: Option 'exec-directory' does not exist.

systemd[1]: foldingathome.service: Main process exited, code=exited, status=1/FAILURE

systemd[1]: foldingathome.service: Failed with result 'exit-code'.

$cd /opt/fah

$ ls -l

total 8888

-rw-r--r-- 1 root root 39517 Apr 19 19:13

drwxr-xr-x 2 root root 4096 Apr 19 15:26 configs

-rw-r--r-- 1 root root 247 Apr 19 19:15 config.xml

drwxr-xr-x 3 root root 4096 Apr 18 14:26 cores

-rwxr-xr-x 1 root root 8058200 Apr 19 19:13 FAHClient

-rwxr-xr-x 1 root root 847984 Apr 19 19:13 FAHCoreWrapper

-rw-r--r-- 1 root root 92198 Apr 18 14:25 GPUs.txt

drwxr-xr-x 2 root root 4096 Apr 19 15:04 logs

-rw-r--r-- 1 root root 17884 Apr 19 18:40 log.txt

-rw-r--r-- 1 root root 4755 Apr 19 19:13

-rwxr-xr-x 1 root root 2010 Apr 19 19:13 sample-config.xml

drwxr-xr-x 4 root root 4096 Apr 19 18:40 work