Package Details: foldingathome 8.4.3-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: fah science
Licenses: GPL-3.0-or-later
Submitter: dtw
Maintainer: PlasticSoup
Last Packager: PlasticSoup
Votes: 180
Popularity: 0.65
First Submitted: 2007-06-28 14:55 (UTC)
Last Updated: 2024-08-21 01:37 (UTC)

Dependencies (16)

Required by (0)

Sources (2)

Pinned Comments

SovietReimu1228 commented on 2024-08-22 14:48 (UTC)

I'll leave a note for those who are having trouble starting FAH after updating. You should do pacman -Rs foldingathome and install again. This will create the fah-client user.

Latest Comments

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

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: https://gist.github.com/Kattus/70f88c424bc6450f1337ddd3fc5cb606

@Takel

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 (https://github.com/systemd/systemd/blob/master/NEWS#L1878). Try ExecStartPre=!... for the chown command.

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