You are not logged in.
Pages: 1
In the interest of slowly saving the world by contributing to Folding@home, I am trying to get opencl working on my system. Specifically, for folding@home the proprietary amdgpu-pro version of opencl is required. I have been successful in installing the aur package (opencl-amd and other variants) and running opencl, but when I do so I can no longer start x. I suspect I may be overlooking something trivial, but I would appreciate it if someone could point me in the right direction to make this all work together.
Here is the output the xorg log:
https://pastebin.com/bVjDtNtb
and the output of clinfo showing that Opencl is working while X is not
https://pastebin.com/vPZPvUjw
I am sure that I am missing some crucial piece of diagnostic information, so please let me know what else you might need to know.
Thank you in advance for considering my problem.
Offline
What packages exactly did you install? Were you trying to install all of AMDGPU-PRO, or did you just install the "opencl-amd" package from the AUR?
In the Xorg log, this here is the spot where things start going wrong:
[ 98.961] (II) AMDGPU(0): [KMS] Kernel modesetting enabled.
[ 98.961] (EE) AMDGPU(0): [drm] Failed to open DRM device for pci:0000:0b:00.0: No such file or directory
[ 98.961] (II) AMDGPU(1): [KMS] Kernel modesetting enabled.
[ 98.961] (EE) AMDGPU(1): [drm] Failed to open DRM device for pci:0000:0b:00.0: No such file or directoryThose messages are printed by the Xorg module from the package "xf86-video-amdgpu". Afterwards, Xorg falls back to using the "modeset" module and that one then seems to fail with a similar problem:
[ 99.016] (EE) modeset(0): drmSetMaster failed: Permission deniedOffline
The output I provided was with just the aur package opencl-amd installed. I tried other variants such as opencl-amdgpu-pro-pal, amdgpu-pro-libgl, and amdgpu-pro-installer in an attempt to rule out the idea that I was misunderstanding the dependencies. The results were similar if not exactly the same. I can try a different variant if you think it might be useful. I believe I tried uninstalling xf86-video-amdgpu as well to see if it was causing the problem and it had no noticeable effect.
Offline
Are you aware of this?
You should probably restore your AMD config back to before you started playing with F@H, then try again.
Last edited by merlock (2020-09-11 22:17:22)
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
Thank you for the link. I hadn't read that thread, but it seems like it is out of date at this point as Navi is now supported for core 22 and works, at least to some extent, out of the box. Your suggestion to restore my AMD config back to its original state led me to disable the foldingathome service which make it possible to start X with Opencl installed on my system. Now I am able to manually start the foldingathome service after logging in and things seem to mostly work. Any ideas as to why there might be a conflict between the folding at home service and Xorg when opencl is installed? Or perhaps how to resolve this underlying issue?
Offline
I can't even begin to guess why F@H would conflict with X.
Prior to F@H, I had just a stock AMD graphics stack (my card is an RX560). Installed F@H and opencl-amd and modified the config file.
Enabled the service, and everything is ok (I hear my fans kick up right before the lightdm-greeter appears on the monitor).
I only made one change to the F@H service...by default it logs to both the journal and to /var/log/foldingathome/ . I did a drop in to turn off the journal logging.
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
Pages: 1