Package Details: foldingathome 7.6.21-1

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

Pinned Comments

alucryd commented on 2020-04-21 14:23

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

mnd999 commented on 2020-04-19 07:50

My GPU is also now not working. It was working perfectly before the config files and logs started moving around for no reason.

igorselsking commented on 2020-04-18 23:40

I think the configuration gets reset when I restart the client. It's that possible or I'm doing something wrong?

Emil commented on 2020-04-18 12:11

This is the systemd user service I use to make idle detection work: ~/.config/fah/config.xml and ~/.local/share/fah/ need to be created first.

Description=Folding@home distributed computing client

ExecStart=/opt/fah/FAHClient --config %h/.config/fah/config.xml --exec-directory=/opt/fah --data-directory=%h/.local/share/fah/


Pezlu commented on 2020-04-18 11:56

Hello, I'm using a nVidia Geforce GTX 660 and I was using the root version before the latest updates. With the latest version (7.6.8-7) everything works almost as intended.

However, right after boot, CUDA and OpenCL are not detected, so the GPU does not fold. I get:

08:55:49:      GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:3 GK106 [GeForce GTX 660]
08:55:49:       CUDA: Not detected: cuInit() returned 100
08:55:49:     OpenCL: Not detected: clGetPlatformIDs() returned -1001

If I restart the service everything is recognized and works as intended:

10:28:36:          GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:3 GK106 [GeForce GTX 660]
10:28:36:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:3.0 Driver:10.2
10:28:36:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:440.82

It seems to be a timing issue. As a workaround I'm restarting the service after boot with a startup script.

katt commented on 2020-04-18 10:27

Figured I'd also poke in and say it works perfectly with the latest (7.6.8-7) changes. I'm using startx and having no issues with this starting "too soon". nvidia gpu.

BS86 commented on 2020-04-18 09:32

not sure why, but I guess when the opencl entity is started too soon, it blocks the GPU from being accessible for display. Not sure if that is also true for nvidia cards, might be that the timing plays a huge role, and that this timing is different for Nvidia.

When using opencl-mesa, starting an OpenCL workload breaks the display output completely (image is not updated anymore - that information was last checked by me about 2 years ago so that might not be true anymore), that behaviour does not happen with opencl-amd. But that behaviour leads to my conclusion in the first sentence of this post.

alucryd commented on 2020-04-18 08:51

Awesome, thanks for the heads up.

Takei commented on 2020-04-18 08:12

@alucryd Can confirm that works. Hopefully that will work for a while.

alucryd commented on 2020-04-18 07:49 works on my server, it should be the same as on your desktops.

Somehow still works when default is multi-user.

Takei commented on 2020-04-18 05:16

@alucryd sadly cannot confirm on headless server. Sorry should have included that in the previous comment.