[QUOTE=Prime95;519691]That worked, thanks!

What changes do I need to make to be able to run gpuowl as a normal user again?[/QUOTE]


I'm stumbled that you were able before ... it never worked for me.
I have always run gpuowl as root because of this issue, I have filed a github issue for ROCm about this.


[url]https://github.com/RadeonOpenCompute/ROCm/issues/823[/url]

[QUOTE=Prime95;519691]That worked, thanks!

What changes do I need to make to be able to run gpuowl as a normal user again?[/QUOTE]


I have found how to resolve the issue partially.
The file /etc/OpenCL/vendors/amdocl64.icd has owner root and group root. Assigning this ownership to a regular user makes that user able to run OpenCL applications.

[QUOTE=SELROC;519882]I have found how to resolve the issue partially.
The file /etc/OpenCL/vendors/amdocl64.icd has owner root and group root. Assigning this ownership to a regular user makes that user able to run OpenCL applications.[/QUOTE]

Unless rebooting is also required, this fix didn't work for me. I'll look for other OpenCL files installed as root.

[QUOTE=Prime95;519885]Unless rebooting is also required, this fix didn't work for me. I'll look for other OpenCL files installed as root.[/QUOTE]


Which system are you using ?

An old Haswell system. Originially Ubuntu 16 upgraded to 19. Rocm 2.4 initially loaded, downgraded to 2.2 for development, since upgraded to 2.5.

At least I'm crunching now. If I have to run as root forever, not too big a deal.

[QUOTE=Prime95;519887]An old Haswell system. Originially Ubuntu 16 upgraded to 19. Rocm 2.4 initially loaded, downgraded to 2.2 for development, since upgraded to 2.5.

At least I'm crunching now. If I have to run as root forever, not too big a deal.[/QUOTE]


I have tested the fix on Ubuntu 19 and Debian Testing and it works in both cases. It is a partial fix however, only root and that owner user have the ability to run OpenCL applications.

What permissions does that file have? Does it get written to when gpuowl runs? If not then any user who can read the file ought to be able to run it.

Chris

[QUOTE=chris2be8;519895]What permissions does that file have? Does it get written to when gpuowl runs? If not then any user who can read the file ought to be able to run it.

Chris[/QUOTE]


the permissions:


-rw-r--r--

Check when the file was last updated, [c]stat /etc/OpenCL/vendors/amdocl64.icd[/c] would tell you. If it's updated when you run gpuowl then changing permissions to group-writeable and adding multiple users to it's group should let them run gpuowl (you can change it's group if you want).

But it sounds odd for gpuowl to need to write to that file. So there may be something else involved. And since I don't have any amd GPU to test gpuowl on I can't help any more.

Chris

[QUOTE=chris2be8;519992]Check when the file was last updated, [c]stat /etc/OpenCL/vendors/amdocl64.icd[/c] would tell you. If it's updated when you run gpuowl then changing permissions to group-writeable and adding multiple users to it's group should let them run gpuowl (you can change it's group if you want).

But it sounds odd for gpuowl to need to write to that file. So there may be something else involved. And since I don't have any amd GPU to test gpuowl on I can't help any more.

Chris[/QUOTE]


it is not gpuowl fault, it is ROCm failing to load the file (maybe trying to update it).

Trying to run /opt/rocm/bin/rocmsmi as a normal user produces this:

[CODE]hsa api call failure at line 900, file: /data/jenkins_workspace/compute-rocm-rel-2.4/rocminfo/rocminfo.cc.[/CODE]

This could be a clue to our run-as-root problem.