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?
Search Criteria
Package Details: foldingathome 8.4.9-1
Package Actions
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: | 179 |
Popularity: | 0.32 |
First Submitted: | 2007-06-28 14:55 (UTC) |
Last Updated: | 2024-12-09 00:07 (UTC) |
Dependencies (16)
- bzip2 (bzip2-gitAUR)
- expat (expat-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- lz4 (lz4-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- sqlite (sqlite-fossilAUR)
- systemd-libs (systemd-chromiumos-libsAUR, systemd-libs-selinuxAUR, systemd-libs-gitAUR, systemd-libs-fmlAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compat)
- git (git-gitAUR, git-glAUR) (make)
- leveldb (leveldb-gitAUR) (make)
- libyaml (libyaml-gitAUR) (make)
- re2 (re2-gitAUR) (make)
- scons (make)
- snappy (snappy-gitAUR) (make)
- opencl-driver (opencl-nvidia-410xxAUR, amdapp-sdkAUR, opencl-nvidia-440xxAUR, vc4cl-gitAUR, opencl-nvidia-430xxAUR, opencl-legacy-amdgpu-proAUR, intel-compute-runtime-gitAUR, beignetAUR, opencl-nvidia-vulkanAUR, beignet-gitAUR, intel-openclAUR, clvk-gitAUR, opencl-rusticl-mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, opencl-nvidia-535xxAUR, opencl-nvidia-470xxAUR, amdonly-gaming-opencl-clover-mesa-gitAUR, amdonly-gaming-opencl-rusticl-mesa-gitAUR, opencl-nvidia-390xxAUR, opencl-nvidia-teslaAUR, opencl-amdAUR, intel-compute-runtime-binAUR, opencl-nvidia-betaAUR, intel-compute-runtime-legacy-binAUR, intel-compute-runtime-legacyAUR, opencl-nvidia-525xxAUR, opencl-510xx-nvidiaAUR, opencl-nvidia-340xxAUR, opencl-nvidia-550xxAUR, intel-compute-runtime, intel-oneapi-compiler-shared-runtime, opencl-clover-mesa, opencl-nvidia, opencl-rusticl-mesa, rocm-opencl-runtime) (optional) – GPU support
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 23 Next › Last »
alucryd commented on 2020-04-17 19:23 (UTC) (edited on 2020-04-17 19:27 (UTC) by alucryd)
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. https://github.com/DeadSix27/waifu2x-converter-cpp
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: https://wiki.archlinux.org/index.php/NVIDIA#DRM_kernel_mode_setting
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.
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 thefah-client
user.