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: 167
Popularity: 0.074063
First Submitted: 2007-06-28 14:55 (UTC)
Last Updated: 2021-01-09 21:16 (UTC)

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

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 GPU does not function properly.

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.

merlock commented on 2020-08-27 02:15 (UTC) (edited on 2020-08-27 02:16 (UTC) by merlock)

I think you need to add


To the service file; otherwise the client logs to both /var/log/foldingathome/log.txt and the journal.

alucryd commented on 2020-05-26 17:48 (UTC)

@geripgeri Thought that directory existed even with no graphics card, made it optional.

geripgeri commented on 2020-05-21 06:45 (UTC)

Hey @jpkotta!

/dev/dri doesn't exist in my your system, /usr/bin/chown and /etc/foldingathome both exist.

After I added ReadWritePaths=-/dev/dri to foldingathome.service the service starts without any issue!

Thank you for your help!

jpkotta commented on 2020-05-20 20:59 (UTC)

@geripgeri: Does /dev/dri exist on your system? If not, try editing foldingathome.service to have ReadWritePaths=-/dev/dri (this should probably be changed in the package, you shouldn't need /dev/dri if you're doing CPU folding).

As for the chown, that doesn't make sense. Do /usr/bin/chown and /etc/foldingathome both exist?

geripgeri commented on 2020-05-18 13:03 (UTC)

Hey! I'm getting this error message: The system is up to date. I don't have GPU in this pc, FAH worked for me before.

systemd[1]: Starting Folding@home distributed computing client...
systemd[2846840]: foldingathome.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/dri: No such file or directory
systemd[2846840]: foldingathome.service: Failed at step NAMESPACE spawning /usr/bin/chown: No such file or directory
systemd[1]: foldingathome.service: Control process exited, code=exited, status=226/NAMESPACE
systemd[1]: foldingathome.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Folding@home distributed computing client

What could cause this issue?

katt commented on 2020-05-16 19:35 (UTC) (edited on 2020-05-18 09:04 (UTC) by katt)

@alucryd: I realise I should've tried this before, either way it does not help. Moved back sleep to the main service and re-activated the nvidia one and I ended up having to run startx manually. (as wasn't active)

EDIT: It's now happening with only foldingathome.service, so I guess it's the sleep command then, but it used to work before? Computers yo...

alucryd commented on 2020-05-16 08:21 (UTC)

@katt: Can you try putting the sleep command back to the foldingathome.service unit?

katt commented on 2020-05-14 19:29 (UTC) (edited on 2020-05-14 19:30 (UTC) by katt)

I've just discovered that with the foldingathome-nvidia service activated, stays "inactive (dead)" until I've logged out and back in. This causes problems such as xorg not autostarting (

This didn't happen a while back so possibly has something to do with the moved sleep command?

AntiComposite commented on 2020-05-09 15:15 (UTC) (edited on 2020-05-09 15:23 (UTC) by AntiComposite)

Yes, fully updated. After a sudo useradd fah, the service starts fine.

Correction: I found an /etc/nsswitch.conf.pacnew. My existing /etc/nsswitch.conf didn't allow systemd to control users and groups. I fixed that, removed the manually-created user, and the service started normally.

alucryd commented on 2020-05-09 10:13 (UTC)

@AntiComposite: Those should be created automatically by systemd, and automatically deleted when the service exits. It's working fine here, is your system up to date? Can you try creating these manually?

AntiComposite commented on 2020-05-09 02:52 (UTC)

Trying to start the service with sudo systemctl start foldingathome fails for me with chown[60820]: /usr/bin/chown: invalid user: ‘fah:fah’.

SebRut commented on 2020-05-07 15:16 (UTC) (edited on 2020-05-07 15:17 (UTC) by SebRut)

shellcheck shows "SC2206: Quote to prevent word splitting/globbing, or split robustly with mapfile or read -a" warning for the pkgver variable in the download url.

alucryd commented on 2020-04-27 12:13 (UTC)

@Wild_Penguin I was planning to move it to the nvidia unit with the next update indeed, like you said it's most likely unnecessary for any AMD GPU.

@noalwin: Nope, we're using a dynamic user, there's no need for that.

Wild_Penguin commented on 2020-04-27 07:38 (UTC)


About the PreExec : 60 seconds delay

I hope this hack / workaround is temporary. I've decreased the default timeouts for all systemd units, since I consider anything taking tens of seconds to start as failed. Hence, foldingathome will never start with the current way. Also, being an AMD user, I can not have problems with CUDA. Maybe the delay should be added to foldingathome-nvidia instead, and have foldingathome depend on that (untill a less-hacky workaround is found)?

Just my comments.

noalwin commented on 2020-04-25 13:24 (UTC) (edited on 2020-04-25 13:25 (UTC) by noalwin)

Please, add to the post install and post upgrade message that users should add the "fah" user to the "video" group (gpasswd -a fah video) or maybe the script should do it.

curtispf commented on 2020-04-24 09:11 (UTC)

Thanks @alucryd and @Superice97 - that update works for me!

alucryd commented on 2020-04-24 08:09 (UTC)

@rsa: Done.

@Superice97: Was hoping to do without, but I added it back. Thanks for the heads up.

@curtispf: Does it change anything for you?

SuperIce97 commented on 2020-04-24 00:50 (UTC)

My GTX1050 stopped working between 7.6.9-7 and 7.6.9-8. Adding ExecStart=/usr/bin/clinfo back to foldingathome-nvidia.service fixes it.

curtispf commented on 2020-04-23 19:03 (UTC)

I've lost GPU folding on updating to the latest release :(

My logs show the following rather interesting few lines:

18:58:25:           GPUs: 0
18:58:25:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2
18:58:25:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:440.82

Not wholly sure how it's working that one out... anyone have any ideas? I have a Nvidia GeForce GTX 1060. foldingathome-nvidia is enabled, and says "Succeeded" in the logs. The 60 second wait is working, too, as I've watched it happening.

rsa commented on 2020-04-22 16:47 (UTC) (edited on 2020-04-22 16:49 (UTC) by rsa)

May you replace the dependencies opencl- with opencl-driver? It's a generic name that all opencl- packages provide, however you miss several providers from the array, it would be cleaner to use opencl-driver straight away :) see foldingathome-beta

Pezlu commented on 2020-04-22 16:31 (UTC)

In the end, to update I didn't wait for the WUs to finish, since the new versions were basically contained the changes you already suggested and that I already made.

Thus, I can confirm that version 7.6.9-8 works flawlessly for me! :)

keithy commented on 2020-04-22 16:04 (UTC)

@alucryd: 7.6.9-8 still working fine for me :)

alucryd commented on 2020-04-22 15:58 (UTC)

Alright, I added the 60s sleep and removed the clinfo line. Hopefully this make it work for everybody.

Pezlu commented on 2020-04-22 11:57 (UTC)

@alucryd: I removed the clinfo invocation and everything is still working

alucryd commented on 2020-04-22 11:41 (UTC)

@keithy @Pezlu Awesome, thanks for the feedback! 60s is probably fine for most, if not all people. One last thing I'd like you to try if you find the time, is to remove the clinfo invocation from the nvidia service, I did on my desktop, and the delay was enough to get everything working.

Pezlu commented on 2020-04-22 11:22 (UTC) (edited on 2020-04-22 11:23 (UTC) by Pezlu)

@alucryd: I'm still on 7.6.9-6, and after adding ExecStartPre=/usr/bin/sleep 60 to the service file everything works fine! I've not fiddled (yet) with the delay length, however. I can try reducing it later if needed.

PS: I'll update to the latest version after finishing the current WUs... considering my ancient GPU, it will take a while!

keithy commented on 2020-04-22 11:18 (UTC)

@alucryd: working perfectly now with 7.6.9-7 - Thanks :)

alucryd commented on 2020-04-22 09:25 (UTC)

FYI, waiting for 60s works on my desktop.

alucryd commented on 2020-04-22 09:20 (UTC)

@YanDoroshenko: And thank you for your contribution to solving the issue, whining and being a smartass is always helpful :) I suggest you write to the arch-security mailing list explaining why you think, rather why you know, it's a good idea to run this as root ;)

@keithy: Oh, that's probably me, please try the latest revision.

@Pezlu: Almost there! I've been reading on the f@h forums that there might be some race condition, and just waiting a bit before actually starting FAHClient could be enough to get it working. Can you try adding ExecStartPre=/usr/bin/sleep 60 to the unit file and report back, and maybe play with the delay a bit? I'll do the same on my desktop.

YanDoroshenko commented on 2020-04-21 20:11 (UTC) (edited on 2020-04-21 20:11 (UTC) by YanDoroshenko)

Thanks, great job on keeping my system secure! Yesterday I was able to get the GPU to work running sudo FAHClient, but I'm not anymore, so no more nasty proprietary code running with superuser access.

Pezlu commented on 2020-04-21 19:20 (UTC) (edited on 2020-04-22 06:57 (UTC) by Pezlu)

@alucryd: I just updated to 7.6.9-6 and enabled the foldingathome-nvidia service. I tried to reboot only once, but the issue seems partially solved: OpenCL is detected, while CUDA is not:

19:12:42:           GPUs: 1
19:12:42:          GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:3 GK106 [GeForce GTX 660]
19:12:42:           CUDA: Not detected: cuInit() returned 100
19:12:42:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:440.82

Restarting the foldingathome service corrects the issue as before:

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

keithy commented on 2020-04-21 19:14 (UTC)

@alucryd: My issue actually appears to be entirely to do with foldingathome.service not starting.

During startup I get this error

systemd[1]: Found ordering cycle on foldingathome.service/start
systemd[1]: Found dependency on foldingathome-nvidia.service/start
systemd[1]: Found dependency on
systemd[1]: Job foldingathome.service/start deleted to break ordering cycle starting with

Thanks, I hope this doesn't create more confusion

alucryd commented on 2020-04-21 18:17 (UTC)

@cubethethird: right apologies, this is more of a hack and I hope to find a better way to initialize opencl for nvidia in the future, but for now I've added it to optdeps

cubethethird commented on 2020-04-21 15:51 (UTC)

It seems there is now a missing dependency for clinfo that is needed for the foldingathome-nvidia service.

alucryd commented on 2020-04-21 15:46 (UTC)

@keithy: I moved the logs to /var/log/foldingathome so it's easier for you guys to access logs.

Also removed the shipped GPUs.txt, looking at the log the download failure has been fixed upstream.

alucryd commented on 2020-04-21 14:33 (UTC) (edited on 2020-04-21 14:43 (UTC) by alucryd)

@keithy can you get the full log of foldingathome-nvidia with journalctl? And what does foldingathome say? There's really no reason why even CPU folding wouldn't work after these changes.

@Buddlespit: don't know what to say, it works on both my 1050 and my 1080Ti, well enjoy giving root access to your whole system to some closed proprietary code then

keithy commented on 2020-04-21 14:26 (UTC)

@alucryd: No change with 7.6.9-4. Neither CPU nor GPU fold until I restart foldingathome.service

This is the status of the foldingathome-nvidia service in case it sheds some light!

foldingathome-nvidia.service - Folding@home helper for NVIDIA GPUs
Loaded: loaded (/usr/lib/systemd/system/foldingathome-nvidia.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Tue 2020-04-21 15:07:10 BST; 11min ago
Process: 748 ExecStart=/usr/bin/nvidia-modprobe (code=exited, status=0/SUCCESS)
Process: 763 ExecStart=/usr/bin/nvidia-modprobe -c 0 -u (code=exited, status=0/SUCCESS)
Process: 794 ExecStart=/usr/bin/clinfo (code=exited, status=0/SUCCESS)
Main PID: 794 (code=exited, status=0/SUCCESS)

Apr 21 15:07:10 ryzen-antergos clinfo[794]:   clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR)  No devices found in platform
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM)  Invalid device type for platform
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL)  No platform
Apr 21 15:07:10 ryzen-antergos clinfo[794]: ICD loader properties
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   ICD loader Name                                 OpenCL ICD Loader
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   ICD loader Vendor                               OCL Icd free software
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   ICD loader Version                              2.2.12
Apr 21 15:07:10 ryzen-antergos clinfo[794]:   ICD loader Profile                              OpenCL 2.2
Apr 21 15:07:10 ryzen-antergos systemd[1]: foldingathome-nvidia.service: Succeeded.
Apr 21 15:07:10 ryzen-antergos systemd[1]: Finished Folding@home helper for NVIDIA GPUs.

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.

alucryd commented on 2020-04-21 14:09 (UTC)

@keithy: the latest foldingathome-nvidia service consistently works for me on my desktop

@Buddlespit: Did you read the latest install notes and enable foldingathome-nvidia? Did you try restarting the service like others do?

keithy commented on 2020-04-21 12:06 (UTC) (edited on 2020-04-21 12:34 (UTC) by keithy)


Sorry, 7.6.9-3 is a backward step for me.

Now neither CPU nor GPU fold until I restart foldingathome.service.

After restart only CPU folds :(

Edit: GPU does fold as well after service restart - it was just trying to download another WU

alucryd commented on 2020-04-21 09:03 (UTC)

@xuanruiqi: Awesome, we're getting there.

@Pezlu @keithy: I can't find confirmation in the systemd documentation, but I believe ReadWritePaths is evaluated before ExecStartPre, so the first time those paths don't exist so systemd doesn't give you access to them.

I've added a new service named foldingathome-nvidia.service, if you enable both this one and foldingathome.service, the nvidia service should run first, and by the time foldingathome starts, the paths should be there. Please let me know how it goes.

xuanruiqi commented on 2020-04-21 08:27 (UTC)

@alucryd: OK, my GPU is working again...

Pezlu commented on 2020-04-20 14:10 (UTC)

@alucryd: I just updated to 7.6.9-2 and the client behaviour didn't change, I still have to restart the service. I'm on a desktop.

alucryd commented on 2020-04-20 12:23 (UTC)

@xuanruiqi: Wonder why my 1050 works fine, may depend on the workload :/ I've added /dev/nvidia0 and /dev/nvidiactl to ReadWritePaths, please let me know if that changes anything.

@keithy: Thanks for the feedback, I'll keep looking into this as well.

keithy commented on 2020-04-20 12:02 (UTC)


It worked this morning without having to restart service. Sadly that means its random. Don't have enough data points to tell, but guessing from what I've seen so far its 50/50 as to whether it starts or not.

I'll try the systemd service alteration at some point and see if it makes any difference.

xuanruiqi commented on 2020-04-20 09:01 (UTC)

@alucryd: Yes I have all the requirements (cuda, ocl-icd, opencl-nvidia) and it worked perfectly before the changes.

alucryd commented on 2020-04-20 06:25 (UTC) (edited on 2020-04-20 06:26 (UTC) by alucryd)

@xuanruiqi: Did it work before the recent changes? Did you install all the requirements for opencl? I have the exact same card on my server and it works just fine.

@keithy: Hmm, what if you replace by in the systemd service?

xuanruiqi commented on 2020-04-19 23:11 (UTC)

I'm still having trouble with my GPU (NVIDIA GTX 1050), and restarting the service doesn't help. It just doesn't detect my device. Can confirm I have latest ver of the package.

keithy commented on 2020-04-19 15:55 (UTC)


I have the same issue as Pezlu - service restart fixes it.

Nvidia 1050 Ti on desktop

running latest 7.6.9


alucryd commented on 2020-04-19 14:41 (UTC)

Updated to 7.6.9.

@Pezlu: Is that with the very latest changes to the systemd unit? Desktop or server?

@Emil, Thanks, in an effort to make cleanup easier, I'd rather have everything in .config/fah so I added a unit to reflect that.

@igorselsking: The config is in /etc/foldingathome now. As for it to be reset, that's not exactly possible, although foldingathome itself modifies it and rotates it periodically...

@mnd999: Nvidia or AMD? Just added /dev/dri to ReadWritePaths as several sources indicate opencl on AMD needs direct access to the card. Please let me know if that works for you.

mnd999 commented on 2020-04-19 07:50 (UTC)

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 (UTC)

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 (UTC) (edited on 2020-04-18 12:13 (UTC) by Emil)

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 (UTC) (edited on 2020-04-19 09:00 (UTC) by Pezlu)

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 (UTC)

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 (UTC) (edited on 2020-04-18 09:33 (UTC) by BS86)

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 (UTC)

Awesome, thanks for the heads up.

Takei commented on 2020-04-18 08:12 (UTC)

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

alucryd commented on 2020-04-18 07:49 (UTC) 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 (UTC)

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

alucryd commented on 2020-04-18 05:04 (UTC)

@Takei: On a server? I'll probably go with it, but will change to

Takei commented on 2020-04-18 04:59 (UTC)

@BS86 @alucryd Can confirm works with the settings from BS86.

alucryd commented on 2020-04-18 04:06 (UTC) (edited on 2020-04-18 04:15 (UTC) by alucryd)

@lesto: Please have a read, look for DynamicUser:

@andrej: You can't trust most people to know how to do that, this must come with the package. I added those lines with both ! and -. That way nvidia will work out of the box and non nvidia systems will not be impacted. If this fails on an nvidia system you probably have bigger problems to deal with anyway. Also, nvidia-modprobe is setuid, so anyone can invoke this binary as root, but it seems systemd still applies some restrictions to it so ! it is.

@BS86: I still can't figure out why the video group is needed since virtually all the filesystem is read-only thanks to DynamicUser, unless amd has some files needed for opencl that are no world-readable? Also, before I add I want to make sure it still works fine on a headless server.

@YanDoroshenko: You might want to read the comments.

YanDoroshenko commented on 2020-04-17 23:21 (UTC)

I'm unable to use GPU since today's update. I've tried everything I was able to find (and a couple of my own inventions) - all quite fruitless. Running FAHClient via sudo does the trick and GPU picks up right away with the same config and same command.

BS86 commented on 2020-04-17 21:46 (UTC) (edited on 2020-04-17 21:47 (UTC) by BS86)

And Success: With and booting now works as expected.

Tried and first, but would not work due to obvious cycle-detection. System booted, but FAH service was not loaded.

BS86 commented on 2020-04-17 21:38 (UTC) (edited on 2020-04-17 21:48 (UTC) by BS86)

ok, with SupplementaryGroups=video, OpenCL and FAH works and does find my Vega64 running with opencl-amd, but on reboot, the system breaks like expected. Had to chroot to get the system back working.

Will play around a bit with the WantedBy and After options to get fah loaded after X.

andrej commented on 2020-04-17 21:37 (UTC)

@alucryd As for NVidia, it's better to add a drop-in instead of changing the unit file. Also, I think the prefix should be !, not -. (A failure is not OK and, AFAIK, only root can modprobe.) This is only relevant for people with NVidia GPUs anyway.

On my system I've created /etc/systemd/system/foldingathome.service.d/modprobe.conf containing this:

ExecStartPre=!/usr/bin/nvidia-modprobe -c0 -u

(The first nvidia-modprobe is a no-op if you run a desktop or otherwise load the module automatically.)

The drop-in will show up in the status (after systemctl daemon-reload etc.):

● foldingathome.service - Folding@home distributed computing client
     Loaded: loaded (/usr/lib/systemd/system/foldingathome.service; disabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/foldingathome.service.d
     Active: active (running) since Fri 2020-04-17 22:51:46 CEST; 10min ago
    Process: 15205 ExecStartPre=/usr/bin/chown -R fah:fah /etc/foldingathome (code=exited, status=0/SUCCESS)
    Process: 15207 ExecStartPre=/usr/bin/nvidia-modprobe (code=exited, status=0/SUCCESS)
    Process: 15209 ExecStartPre=/usr/bin/nvidia-modprobe -c0 -u (code=exited, status=0/SUCCESS)
   Main PID: 15212 (FAHClient)
      Tasks: 65 (limit: 77025)
     CGroup: /system.slice/foldingathome.service

lesto commented on 2020-04-17 20:22 (UTC)

in the service file you do: "/usr/bin/chown -R fah:fah /etc/foldingathome" I think this should be done by the install script instead, so it is done once and that is it.

also my xt5700x is seen as 5600, not sure where this GPUs.txt come from

fagianijunior commented on 2020-04-17 20:11 (UTC)

What is a newer or older AMD GPU? I has a Radeon R7

Takei commented on 2020-04-17 20:05 (UTC)

@alucryd sorry but it doesn't seem to work. Still the same error code even after another restart of the service. Anyways i'm off to bed.

alucryd commented on 2020-04-17 19:23 (UTC) (edited on 2020-04-17 19:27 (UTC) by alucryd)

Nevermind that, cuda depends on it. Looking at the manpage, nvidia-modprobe -u should create the device. Not sure if it's right to automatically call it with fah though, but can you try adding ExecStartPre=-/usr/bin/nvidia-modprobe -u to the systemd service?

alucryd commented on 2020-04-17 19:16 (UTC)

Do you guys have nvidia-utils installed? It contains nvidia-modprobe which is a setuid binary that can create this device without sudo.

katt commented on 2020-04-17 18:56 (UTC)

@Takei I really don't know what this application does for CUDA, I just know it works really.

Anyway the file is only created when I've run the the application using CUDA.

alucryd commented on 2020-04-17 18:47 (UTC)

I never ever use cuda, still /dev/nvidia-uvm is automatically created for me, so yeah it works even after a reboot :/

Takei commented on 2020-04-17 18:44 (UTC)

@katt if true that would make it atleast possible to make this run as a normal user. Could you see if you can find something in that application that might help us out? Maybe it has a service file or something else from what we could get the info we need.

katt commented on 2020-04-17 18:36 (UTC) (edited on 2020-04-17 18:40 (UTC) by katt)

@alucryd Added just ReadWritePaths=/dev/nvidia-uvm and SupplementaryGroups=video and it seems to be working now, not quite sure why it was complaning that /dev/nvidia-uvm didnt exist, havent even rebooted since..

Now to just get a new WU ;p

18:32:32:  CUDA Device 0: Platform:0 Device:0 Bus:9 Slot:0 Compute:6.1 Driver:10.2
18:32:32:OpenCL Device 0: Platform:0 Device:0 Bus:9 Slot:0 Compute:1.2 Driver:440.82

EDIT: Maybe related to why it suddenly "showed up", just realised I was doing some CUDA work earlier, that's probably why. (that application was not run as root though)

Takei commented on 2020-04-17 18:35 (UTC)

@alucryd tried sudo modprobe nvidia_uvm just now. Does not create the device.

Takei commented on 2020-04-17 18:32 (UTC)

@alucryd did you also try after a reboot?If you use cuda once per session as root, it will also work for a normal user,but only root can create the device.

Just tried with ReadWritePaths=/dev/nvidia-uvm after reboot, did not work. Errormsg foldingathome.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev/nvidia-uvm: No such file or directory

alucryd commented on 2020-04-17 18:30 (UTC)

Actually this should work even without KMS, does sudo modprobe nvidia_uvm create the /dev/nvidia-uvm device?

alucryd commented on 2020-04-17 18:23 (UTC) (edited on 2020-04-17 18:24 (UTC) by alucryd)

@katt, @Takei: Tried on my desktop with a 1080Ti, I can reproduce.

I'm not exactly sure, but it seems you need /dev/nvidia-uvm, seems to be linked to KMS:

Then I added it to ReadWritePaths and restarted foldingathome and it worked fine.

Can you try that before I add it to the service file? Would be great if someone could write that down on the wiki as well.

Takei commented on 2020-04-17 18:16 (UTC)

@katt Same problem as me. Only way i was able to solve it till now was to let the client run as root. Otherwise it wasn't able to create the necessary device and access cuda.

katt commented on 2020-04-17 17:56 (UTC) (edited on 2020-04-17 17:57 (UTC) by katt)

@alucryd I added /dev/nvidia0 and /dev/nvidiactl (the others dont exist) and still didnt work. Here's the output of that command though:


17:50:38:       CUDA: Not detected: cuInit() returned 999
17:50:38:     OpenCL: Not detected: clGetPlatformIDs() returned -1001

alucryd commented on 2020-04-17 17:43 (UTC)

You can also try installing clinfo and run sudo -u fah clinfo. Might give us some insight.

Takei commented on 2020-04-17 17:40 (UTC) (edited on 2020-04-17 17:41 (UTC) by Takei)

@katt What is the output for the cuda and opencl device in the log?

alucryd commented on 2020-04-17 17:39 (UTC)

@katt: If that still doesn't work, you may also try the following devices:

/dev/nvidia0 /dev/nvidiactl /dev/nvidia-uvm /dev/nvidia-uvm-tools

You can add as many ReadWritePaths lines as you want, they stack up.

alucryd commented on 2020-04-17 17:35 (UTC)

@jpkotta: Thanks, will switch to the newer syntax.

@katt: Can you try adding ReadWritePaths=/dev/dri to the systemd service file, on top of the SupplementaryGroups stanza?

katt commented on 2020-04-17 17:31 (UTC) (edited on 2020-04-17 17:31 (UTC) by katt)

@jpkotta Adding SupplementaryGroups=video did not help unfortunely.

Still getting this: 17:30:16:ERROR:WU00:FS01:Failed to start core: OpenCL device matching slot 1 not found, make sure the OpenCL driver is installed or try setting 'opencl-index' manually

Yes, opencl-nvidia is installed and it worked perfectly before all this.

alucryd commented on 2020-04-17 17:31 (UTC)

@zegkljan: chown -R it is then.

@zero456: sigh... thanks for the heads up, shipping a GPUs.txt until upstream fixes it. That's what happens when you refuse to go open source.

@jpkotta, @BS86: I can use my GPU just fine without being in the video group, got a 1050 on my server. I never started this service as root. And no the fah user should not be created, that's what DynamicUser is all about. I can definitely add SupplementaryGroups though.

jpkotta commented on 2020-04-17 17:27 (UTC)

@alucryd PermissionsStartOnly is deprecated ( Try ExecStartPre=!... for the chown command.

jpkotta commented on 2020-04-17 17:12 (UTC)

@BS86 Not sure, my GPU is too old for F@H. Maybe an After= in the unit file would fix it?

BS86 commented on 2020-04-17 17:11 (UTC) (edited on 2020-04-17 17:11 (UTC) by BS86)

And apparently, the user "fah" also does not exist on my system because it was not required by this package until now. Only the noroot-package needed it.

@alucryd: If the xorg breakage and GPU detection is solved with the previous comments, and you want to stick with the DynamicUser approach, might you please add a installation warning that the user "fah" needs to be created?

BS86 commented on 2020-04-17 17:06 (UTC)

@jpkotta: Does this also solve the xorg - breakage mentioned in the Wiki?

jpkotta commented on 2020-04-17 17:03 (UTC)

@BS86 @alucryd You need to add SupplementaryGroups=video to the service file.

zero456 commented on 2020-04-17 16:59 (UTC) (edited on 2020-04-17 17:01 (UTC) by zero456)

@alucryd There seems to be a regression in the latest version that is causing folding@home to not download the GPUs.txt file. This is what it uses to detect what GPUs it can and cannot use. Without it, it will not use any GPU.

Copying from the old directory /opt/fah/GPUs.txt to /etc/foldingathome fixes the issue.


Takei commented on 2020-04-17 16:55 (UTC) (edited on 2020-04-17 17:23 (UTC) by Takei)

New version breaks folding@home for Nvidia gpus, because only root can create the device necessary to use cuda. Atleast according to what i found so far. Problem only starts after the first reboot, because the necessary device does not exist anymore.

GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:8 GP104 [GeForce GTX 1080] 8873 CUDA: Not detected: cuInit() returned 999 OpenCL: Not detected: clGetPlatformIDs() returned -1001

Log when FAHclient is started as root: GPU 0: Bus:1 Slot:0 Func:0 NVIDIA:8 GP104 [GeForce GTX 1080] 8873 CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2 OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:440.82

BS86 commented on 2020-04-17 16:55 (UTC)

apparently, foldingathome switched to the noroot - approach with DynamicUser which breaks GPU usage (check Wiki for details:

would be great to have this package here in the future, too (if foldingathome copies the approach from here, that would work to)

BS86 commented on 2020-04-17 16:44 (UTC) (edited on 2020-04-17 17:01 (UTC) by BS86)

For some reason, with that commit today (Version 7.5.1-2) :

This package switched to the DynamicUser approach which is troublesome, check the wiki:


To use your graphics card for this task the fah user has to be in the required group (video). But doing this will also cause the foldingathome.service to start before Xorg and breaking it in the process.

The last working version for me is 7.5.1-1

zegkljan commented on 2020-04-17 16:34 (UTC)

@alucryd The chown way is definitely the way to go but it still does not work because the directory /etc/foldingathome is owned by root and therefore FAHClient cannot remove the old configuration when it needs to update (yes, it first removes it and then writes a new one). There are 16:31:39:WARNING:Exception: Failed to remove '/etc/foldingathome/config.xml': Permission denied warnings in the log when it tries to update.

keithy commented on 2020-04-17 16:21 (UTC)


Thanks thats fixed it.

alucryd commented on 2020-04-17 16:17 (UTC)

@DNAblue2112 GPU works fine here, please describe how you can't add it. The minimal provided config should auto discover any GPU.

alucryd commented on 2020-04-17 16:11 (UTC)

@keithy: remove the fahclient package, I don't know where you got that from.

alucryd commented on 2020-04-17 16:10 (UTC)

Yes the default power setting is coming directly from their sample configuration, which is a sane default. Feel free to crank it up if you want.

Also, how the software itself works is not good, trying to make it sane is not exactly straightforward.

I changed the service again, it will chown the config in /etc/foldingathome so that it is writable to the fah user, now modifications by the software itself will be remembered, and we can still benefit from config backups, and potential changes in defaults from upstream.

Please let me know how it goes.

jpkotta commented on 2020-04-17 15:52 (UTC)

I think the default power setting changed. Set <power value="medium"/> in config.xml. For me, the CPUSchedulingPolicy in the systemd unit didn't affect it nearly as much as the power setting.

DNAblue2112 commented on 2020-04-17 15:08 (UTC)

Unfortunately installing the most recent versions has totalled everything. I cant add my GPU even after downgrading to the old versions, and file permissions got screwed over so no changes stay applied. So now I can only use FAH on my laptop where I haven't updated yet because updating has made everything fall apart on my desktop.

zegkljan commented on 2020-04-17 14:48 (UTC) (edited on 2020-04-17 15:19 (UTC) by zegkljan)

The new way of handling config.xml is not good. If I change the configuration using FAHControl, it is updated only in the working directory /var/lib/fah but not in /etc/foldingathome.

Also, for some reason the utilized CPU power is now miniscule compared to the prior version and when it was running as root (I'm not sure which one of these is the cause). EDIT: the cause is the CPUSchedulingPolicy=idle. If I comment it out, the utilized CPU power is back to where it was before the update.

keithy commented on 2020-04-17 14:33 (UTC)

I get

error: failed to commit transaction (conflicting files) foldingathome: /usr/bin/FAHClient exists in filesystem (owned by fahclient) foldingathome: /usr/bin/FAHCoreWrapper exists in filesystem (owned by fahclient) Errors occurred, no packages were upgraded.

How to fix please??

Thank you

alucryd commented on 2020-04-17 14:32 (UTC)

Bumped to 7.6.8 and added a warning about the new config location.

katt commented on 2020-04-17 13:57 (UTC)

Maybe add a warning that people will have to manually migrate their configs etc? Just got someone yelling at me for breaking their stuff in fahcontrol ;D

mbloms commented on 2020-04-17 11:51 (UTC) (edited on 2020-04-17 12:20 (UTC) by mbloms)

@katt it is, but are you sure this is the one that should be removed? The name of this package matches upstream.

EDIT: Yes this probably should be removed, but foldingathome should probably be named fahclient instead

alucryd commented on 2020-04-17 11:46 (UTC)

@jpkotta I just took over the regular foldingathome package, it no longer runs as root as you did, making this package redundant so I'll merge it in foldingathome.

Thanks for maintaining this until now!

alucryd commented on 2020-04-17 11:37 (UTC)

Adopted and updated to not run as root. I'll make a systemd user service for those who rely on idle detection when I've got some time.

katt commented on 2020-04-17 09:15 (UTC)

Isn't this a duplicate of the foldingathome package?

artafinde commented on 2020-04-13 09:17 (UTC)

@jpkotta: batch should be used if you have lots of idle tasks so they don't starve of CPU. In a "normal" desktop PC I'd say idle and batch should operate the same.

jpkotta commented on 2020-04-09 23:38 (UTC)

@artafinde I added the idle policies. FAH already lowers its priority with nice, but setting the scheduling policy made a small but measurable difference. The difference was much bigger with CPUSchedulingPolicy=batch, but I don't understand it well enough to say it's a good idea.

artafinde commented on 2020-04-09 13:44 (UTC)

Consider adding the below on the service


artafinde commented on 2020-04-09 12:59 (UTC)

Found the issue, I had the opencl-headers installed and I think the program was confused.

artafinde commented on 2020-04-09 09:55 (UTC)

I'm getting an error for GPU folding

Apr 09 10:52:39 tiamat FAHClient[19926]: 09:52:39:ERROR:WU01:FS00:Failed to start core: OpenCL device matching slot 0 not found, try setting 'opencl-index' manually

My GPU is nvidia 1080 with proprietary drivers installed and working and the fah user is in video group. I've tried setting the opencl-index to -1 and 0 without luck. Any suggestions welcome.

Emil commented on 2020-04-08 11:28 (UTC)

You can make a systemd user service as a workaround/solution for this problem.

curtispf commented on 2020-04-07 20:47 (UTC)

When running FAH as a service using the systemd file included here, the idle detection used in FAHClient breaks. See this thread for more detail:

alucryd commented on 2020-03-31 07:58 (UTC)

We're still waiting for permission to distribute, this has been brought to F@H's attention.

katt commented on 2020-03-31 07:53 (UTC)

I'd love to see the changes that were in the temporary official packages applied here, currently using that one instead as it's just overall better and didn't use root.

igorselsking commented on 2020-03-31 01:49 (UTC)

Hello, what's the difference with the other packages? why there is so many?

oxalin commented on 2020-03-30 11:45 (UTC)

Could you add fahviewer and fahcontrol as optional dependencies, which are the protein viewer and the GUI?

Could you add rocm-opencl-runtime, opencl-amdgpu-pro-orca, opencl-amdgpu-pro-pal as optional depencies to complete the OpenCL options?

Your comment about opencl-mesa and opencl-amd are technically not right. Please, if you are to add comments, calk them on ArchLinux's Wiki: - opencl-mesa: free runtime for AMDGPU and Radeon - opencl-amd: proprietary standalone runtime for AMDGPU (pal and legacy stacks in a single package) - rocm-opencl-runtime: Part of AMD's fully open-source ROCm GPU compute stack, which supports GFX8 and later cards(Fiji, Polaris, Vega) - opencl-amdgpu-pro-orca: proprietary runtime for AMDGPU PRO (supports legacy products older than Vega 10) - opencl-amdgpu-pro-pal: proprietary runtime for AMDGPU PRO (supports Vega 10 and later products)

yurikoles commented on 2020-03-27 11:21 (UTC)


It's a user service, basically to handle it append --user argument to systemctl, e.g. systemctl --user enable --now fahclient.service.

More documentation is here:

whatshisname commented on 2020-03-26 22:50 (UTC)

Thanks for putting up this package. This is an important project.

But no matter how I tried to run the service, I kept getting variations of "Failed to start ... service: Unit not found" error messages. This even when I tried to start the service as a user service using the "fahclient@myusername.service" syntax.

Finally, I copied the "/usr/lib/systemd/user/fahclient.service" file to "/usr/lib/systemd/system" and was able to enable and start the service.

jpkotta commented on 2020-03-25 22:04 (UTC)

@minore What command exactly are you running? The client runs under a special systemd environment (consisting of a user, PWD, and other state), and it won't work unless you run your command in that environment too. The fah-config script gives an example of how to do this. But when I want to pause I just systemctl stop foldingathome. The client should gracefully shut down.

jpkotta commented on 2020-03-25 22:01 (UTC) (edited on 2020-03-25 22:05 (UTC) by jpkotta)

@PeXArtZ Looks like permissions issues. Make sure /var/lib/fah/* is owned by user fah.

PeXArtZ commented on 2020-03-25 17:27 (UTC)

@jpkotta I don't think there is anything useful, because I always need to restore the backup before I updated. But if you want to take a look:

minore commented on 2020-03-25 14:09 (UTC)

Entering command --send-pause on a terminal window (for pausing all slots on an already running client) has no effect. Any ideas?

jpkotta commented on 2020-03-24 17:04 (UTC)

@PexArtZ What do the logs say (journalctl -b -u foldingathome)? They're having trouble with the work servers due to increased demand.

PeXArtZ commented on 2020-03-24 10:14 (UTC)

Newest update prevents my install from booting. Anyone else having this problem?

yurikoles commented on 2020-03-23 13:47 (UTC)

Hi @eliasjackson, Thanks for report, fixed.

Hi @whatshisname,

I don't see any new binaries on project page.

jpkotta commented on 2020-03-23 02:01 (UTC)

@minore AFAIK the default is all diseases, so you don't need to do anything.

minore commented on 2020-03-22 21:50 (UTC)

Thank you for this package. Is there a way to opt for a project, as in specifying the preference to contribute to "All Diseases" projects (the COVID-19 research)?

jpkotta commented on 2020-03-22 18:05 (UTC)

They can't put it in community yet. There was a comment (now deleted for some reason) that said there's a license issue and they're asking for permission.

whatshisname commented on 2020-03-22 14:54 (UTC)

This project has changed to focus on the coronavirus. If we download this version will it work for that purpose?

afekete commented on 2020-03-22 09:58 (UTC)

@andrej: that's actually normal according to this article: Also the version here is the same as the one in the .deb package on the official website, but it really should be moved to community

andrej commented on 2020-03-21 21:23 (UTC)

Yet another problem is in f@h itself: There are "cause preferences" in the control app, but coronavirus is not one of them!

andrej commented on 2020-03-21 20:13 (UTC)

+1 what @xuanruiqi said "Mother" Nature needs yet another big punch right in her face!

robinc commented on 2020-03-21 00:16 (UTC)

That also does the trick! Thanks for the quick response.

jpkotta commented on 2020-03-21 00:13 (UTC)


What does ls -l /dev/nvidia* show? If possible, reboot and run the ls command both before and after running that mknod script from nvidia.

jpkotta commented on 2020-03-20 23:53 (UTC)

@robinc @gourdcaptain

Can you try SupplementaryGroups=video instead? That seems more correct. I don't have fancy GPU hardware so I can't test this.

robinc commented on 2020-03-20 23:35 (UTC) (edited on 2020-03-20 23:44 (UTC) by robinc)

@gourdcaptain This seems to be a permissions problem. Adding Group=video to the service file solved this for me (AMD Vega 56). This is what my foldingathome.service looks like now:

Description=Folding@home distributed computing client



@jpkotta Could you please update the package to include this fix?

entropie commented on 2020-03-20 09:30 (UTC)

+1 what @xuanruiqi said

pluckobtain commented on 2020-03-20 00:33 (UTC)

+1 what @xuanruiqi said

direc85 commented on 2020-03-19 19:47 (UTC)

@jpkotta It looks like foldingathome community package has been removed.

direc85 commented on 2020-03-19 18:08 (UTC)

No, it isn't the 'video' group. Today I ran a script from NVIDIA CUDA Installation Guide for Linux and it seemed to have worked...

eliasjackson commented on 2020-03-19 02:55 (UTC)

For whatever reason, one of the commands in the installed systemd service (ExecStartPre=/usr/bin/mkdir -p %h/.local/share/fahclient) wasn't working, so I had to create that directory manually in order to get the service to work. Might be worth adding to the PKGBUILD.

direc85 commented on 2020-03-19 02:34 (UTC)

I had hard time getting my NVidia GTX 1060 to work with OpenCL and/or Cuda. I kept getting OpenCL init error 999 and Cuda init error 1001. I think the final straw was adding user "fah" to group "video" and restarting the service...

jpkotta commented on 2020-03-19 01:50 (UTC)

There's a foldingathome in Community now: It uses basically the same systemd unit file that this package does, which is what enables running as a non-root user. I recommend you install that instead of this package. However, you're expected to hand edit the config.xml instead of using a script. That file is only quasi-human-writable, so I might just convert the fah-config script to its own package.

restore commented on 2020-03-18 03:17 (UTC)

+1 what @xuanruiqi said

gourdcaptain commented on 2020-03-18 00:25 (UTC) (edited on 2020-03-18 00:25 (UTC) by gourdcaptain)

Anyone know why it would be failing to detect my AMD Radeon RX 5600 XT card for OpenCL? It shows in FAHControl a "Not detected: clGetDeviceIDs() returned -1". I have the opencl-amd package installed and the card shows up in clinfo (and vapoursynth plugins have been able to use it.)

GI_Jack commented on 2020-03-16 22:26 (UTC)

Upvote for COVID-19 research. Everyone upvote and lets get on the science win train. Tell everyone.

Daniel071 commented on 2020-03-15 07:30 (UTC)

+1 what @xuanruiqi said

strobelite commented on 2020-03-14 19:20 (UTC)

+1 what @xuanruiqi said

niklaszantner commented on 2020-03-14 16:44 (UTC)

+1 what @xuanruiqi says.

pwr22 commented on 2020-03-14 12:04 (UTC)

I also agree - it would be great to make this more available!

kaipyroami commented on 2020-03-14 04:16 (UTC)

I agree with xuanruiqi. This package needs to be updated...

xuanruiqi commented on 2020-03-13 21:48 (UTC)

Given the current COVID-19 situation, I believe that effort should be made for this package to be moved into [community] ASAP, to make it much easier for Arch users to help with the effort to develop a medicine for the virus. This will be the right thing to do, IMO.

Niklas commented on 2020-03-12 19:30 (UTC)

Can you add provides=('foldinghome') to the PKGBUILD and remove the replaces part? It is an alternative to the other methods of installing FAH, not a replacement or successor.

ArnaudNux commented on 2019-09-25 11:35 (UTC)

There is a software conflict between foldingathome and the opencl-amd program. When it is installed, the program no longer works.

ArnaudNux commented on 2018-10-16 23:11 (UTC) (edited on 2018-10-16 23:20 (UTC) by ArnaudNux)

foldingathome.service - Folding@home distributed computing client Loaded: loaded (/usr/lib/systemd/system/foldingathome.service; enabled; vendor preset: disabled) Active: failed (Result: core-dump) since Tue 2018-10-16 19:56:42 CEST; 5h 9min ago Main PID: 529 (code=dumped, signal=SEGV)

oct. 16 19:56:25 AMD systemd[1]: Started Folding@home distributed computing client. oct. 16 19:56:26 AMD FAHClient[529]: 17:56:26:INFO(1):Read GPUs.txt

oct. 16 19:56:35 AMD FAHClient[529]: amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x. oct. 16 19:56:41 AMD FAHClient[529]: amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x.

oct. 16 19:56:42 AMD systemd[1]: foldingathome.service: Main process exited, code=dumped, status=11/SEGV oct. 16 19:56:42 AMD systemd[1]: foldingathome.service: Failed with result 'core-dump'.

jpkotta commented on 2018-10-05 02:31 (UTC)

You may need to add vsyscall=emulate to your kernel commandline if you get segfaults and messages like vsyscall attempted with vsyscall=none. See

ARandomOWL commented on 2017-06-26 16:34 (UTC) (edited on 2017-06-26 16:35 (UTC) by ARandomOWL)

I have an older install of Arch without the Cuda package, and NVidia GPU folding works fine. However on a new Arch install, it wouldn't work without it. Anyone know what might be going on?

mosh5382 commented on 2017-05-23 21:10 (UTC)

Along the same lines as Skeevy420's request, I think the cuda package for nvidia should be an optional dependency: My nvidia GPU errored out until I installed this package.

skeevy420 commented on 2017-03-12 15:28 (UTC)

Could "opencl-amd" be added as an optional dependency? With CIK enabled to use AMDGPU (free) with my R7 260X, opencl-mesa doesn't work and my GPU always fails. After installing "opencl-amd" which uses AMDGPU Pro's OpenCL with the mesa driver, my GPU folds just fine. Using mesa 17.0.1 and linux-lqx 4.9.13-2.

musasabi commented on 2016-11-11 22:09 (UTC)

Freshly installed, ran FAHClient --configure, enabled/started the service, and it fails to grab work units. I checked the IP's it's requesting against the server status page, and they weren't listed. Does this have anything to do with the FAH blog post from yesterday about certain servers being down? Can I control which IP's my FAHClient is trying to talk to?

hongleong commented on 2016-05-30 03:25 (UTC)

Hi jpkotta, the file has moved to

zekesonxx commented on 2015-09-09 16:45 (UTC)

opencl-mesa should be added as an optional dep for folding with AMD GPUs.

Synthead commented on 2014-12-08 23:49 (UTC)

foldingathome.service should be installed to /usr/lib/systemd/system/, not /etc/systemd/system/.

dmartins commented on 2013-12-21 19:05 (UTC)

In order to use the GPU client on a Nvidia card, opencl-nvidia is also required.

jpkotta commented on 2013-10-30 16:53 (UTC)

I've made a new version of this that creates an fah user and runs the client as that instead of root. Let me know what you think.

paul2lv commented on 2013-02-20 14:39 (UTC)

Updated to the latest version and dropped initscript support.

paul2lv commented on 2013-01-06 19:58 (UTC)

Adopted and updated! If anyone was using my old foldingathome-v7 package, please update to this one and copy your config.xml from the /opt/fah-v7/ folder to the /opt/fah/ folder.

paul2lv commented on 2013-01-02 19:37 (UTC)

@Snowman I just sent that TU an email and asked him if would orphan it for me. We will see....

Snowman commented on 2013-01-02 18:44 (UTC)

It would make more sense to update the foldingathome PKGBUILD instead of creating this one. The foldingathome PKGBUILD is maintained by a TU but it has been out-of date for 6 months. You might want to report/ask for help on the aur ML.

paul2lv commented on 2012-10-02 08:55 (UTC)

Updated the package to include a systemd script and to fix the download error. Thanks to luolimao for all the help!

luolimao commented on 2012-10-02 00:46 (UTC)

Also, the systemd script appears to work fine; it should be all right to add to the package.

luolimao commented on 2012-10-02 00:40 (UTC)

After googling a bit, and learning about the DLAGENTS option, the error can be fixed by adding the line DLAGENTS=("https::/usr/bin/curl -k -o %o %u") to the PKGBUILD. Although for some reason the wiki fails to mention this under "PKGBUILD" or "Creating packages" but instead lists it under "Nonfree Applications Package Guidelines":

paul2lv commented on 2012-09-30 09:23 (UTC)

@luolimao The download error is caused by a certificate error on Stanford's servers. If you manually download the file, it should build with no problems. I put together a systemd script and uploaded it to here --> Copy it to /etc/systemd/system/foldingathome-v7.service and tell me if it works before I add it to the package.

luolimao commented on 2012-09-29 20:18 (UTC)

Also, the file doesn't download for me (x86_64); see error:

luolimao commented on 2012-09-29 20:16 (UTC)

Can you add a systemd script (since rc.d scripts are being phased out)?

paul2lv commented on 2012-09-16 09:49 (UTC)

I fixed up the PKGBUILD so it should work with i686 and x86_64 with out any issues. Let me know if there are any more problems.

bremm commented on 2012-09-13 06:27 (UTC)

There's a way to avoid '--skipinteg', changing the last (32bit) md5sum to the 64bit md5sum. Worked as a charm. :-) I'm not sure if this works for i686 people flawlessly, but my pkgbuild is here: Thank you.

commented on 2012-09-12 18:53 (UTC)

Edit PKGBUILD and change i686 to x86_64 and 32bit to 64bit or vise versa and build with makepkg --skipinteg I don't know exactly what is wrong with the PKGBUILD, but this seems to work.

bremm commented on 2012-09-11 22:04 (UTC)

Even using a downloaded tarball from Stanford: ==> Continue building foldingathome-v7 ? [Y/n] ==> ------------------------------------------ ==> ==> Building and installing package ==> ERROR: An unknown error has occurred. Exiting... /usr/lib/yaourt/ line 200: 18333 User defined signal 1 PKGDEST="$YPKGDEST" makepkg "${MAKEPKG_ARG[@]}" -s -f -p ./PKGBUILD ==> ERROR: Makepkg was unable to build foldingathome-v7.

paul2lv commented on 2012-09-11 11:18 (UTC)

If makepkg complains about a ssl certificate error, please manually download the package from Stanford and try again.

paul2lv commented on 2012-09-11 11:16 (UTC)

Added i686 support

commented on 2011-01-09 16:05 (UTC)

Here is my version of foldingathome daemon script: See my last comment on foldingathome-smp ( ) to know why.

xrchz commented on 2010-10-10 07:11 (UTC)

Can you make the folding@home daemon depend on the nscd daemon? This will save people who forget to load nscd first (or want to load f@h in the background). (Add "ck_daemon nscd && /etc/rc.d/nscd start" to the top of /etc/rc.d/foldingathome)

xrchz commented on 2010-10-10 07:07 (UTC)

Yes the instructions after the end of install messed me up for a while too - please remove them or just add a pointer to the wiki.

Marcel_K commented on 2010-04-24 19:43 (UTC)

Why do you recommend "Please cd to /opt/fah/ and execute ./fah6 -smp -configonly" in post_install()? This is inconsistent with the Wiki (causing confusion, at least to me) and installs/configures fah as root, which is discouraged. Explaining or at least pointing to the post-install steps in the Wiki is way better, IMHO, as those explain what's needed for running fah as another user.