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.046559
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

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

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