Package Details: foldingathome 7.6.21-1

Git Clone URL: https://aur.archlinux.org/foldingathome.git (read-only, click to copy)
Package Base: foldingathome
Description: A distributed computing project for simulating protein dynamics
Upstream URL: https://foldingathome.org/
Keywords: folding foldingathome
Licenses: custom
Submitter: dtw
Maintainer: rustymech
Last Packager: rustymech
Votes: 175
Popularity: 0.123741
First Submitted: 2007-06-28 14:55 (UTC)
Last Updated: 2021-01-09 21:16 (UTC)

Required by (0)

Sources (4)

Pinned Comments

alucryd commented on 2020-04-21 14:23 (UTC) (edited on 2020-04-22 15:57 (UTC) by alucryd)

To be clear, nvidia users need to enable both foldingathome.service and foldingathome-nvidia.service.

Latest Comments

1 2 3 4 5 6 .. 22 Next › Last »

merlock commented on 2023-02-22 04:29 (UTC)

@merzo: You're posting this error in the wrong place. That error pertains to the GUI control (fahcontrol), not the actual folding software.

You'd probably be better off building/installing the GTK3 fork of the control.

merzo commented on 2023-02-21 23:11 (UTC)

Can't run with latest Arch.

$ FAHControl Traceback (most recent call last): File "/usr/bin/FAHControl", line 25, in <module> from fah import FAHControl, load_fahcontrol_db File "/usr/lib/python2.7/site-packages/fah/init.py", line 25, in <module> import util File "/usr/lib/python2.7/site-packages/fah/util/init.py", line 26, in <module> import gtk File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/init.py", line 40, in <module> from gtk import _gtk File "/usr/lib/python2.7/site-packages/cairo/init.py", line 1, in <module> from ._cairo import * # noqa: F401,F403 ImportError: /usr/lib/python2.7/site-packages/cairo/_cairo.so: undefined symbol: cairo_tee_surface_index

merlock commented on 2022-05-17 23:02 (UTC) (edited on 2022-05-19 02:20 (UTC) by merlock)

Thanks,ajgringo619. Mine's AMD, so that might help narrow it down.

ETA: The problem was having the opencl-amd and opencl-mesa packages installed concurrently. Back to normal after removing the opencl-mesa package...

ajgringo619 commented on 2022-05-17 19:56 (UTC)

Using two: GTX 1050 and 1070

merlock commented on 2022-05-17 19:55 (UTC)

@ajgringo619: what GPU are you using?

ajgringo619 commented on 2022-05-17 16:58 (UTC)

Interesting...I upgraded this morning, rebooted, and FaH is working with the new llvm-libs package.

merlock commented on 2022-05-17 03:59 (UTC)

Updated llvm-libs to 13.0.1-3...now GPU does not function properly.

https://bugs.archlinux.org/task/74762

ajgringo619 commented on 2022-01-18 23:24 (UTC) (edited on 2022-01-18 23:24 (UTC) by ajgringo619)

After running this client for nearly a month, I just discovered the foldingathome-nvidia.service. Can you please explain what it's for and why it's required? My (2) GPU system has been running fine without it, although I did enable it today.

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

Wild_Penguin:

Hi!

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)

Hi,

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)