AMD RX 480 in Ubuntu 18.04LTS: fails to chooch

[_The_Editor_]

Assuming that you installed the AMD closed source drivers (proprietary), you will also need to install the OpenCL package as you're getting this error:
06:23:56: OpenCL: Not detected: clGetDeviceIDs() returned -1

I have read that you can use this command to install the OpenCL package:
sudo apt install ocl-icd-opencl-dev

As I said earlier in the thread, I already have that packaged installed.

This morning I've rolled on to the newest version of the amdgpu-pro drivers this morning (version 20.10-1048554), and installed just the opencl packages using:

Code: Select all

./amdgpu-pro-install --opencl=legacy,pal --headless --no-dkms

in the extracted package archive. Have just verified OpenCl in Ubuntu by running clinfo, and it's the same as previous except the platform version is newer:

Code: Select all

Platform Version:                              OpenCL 2.1 AMD-APP (3075.10)

Do you know any other ways of verifying the correct OpenCl installation/packages are present? In every way I can check, it appears everything is present and working properly, but F@H still fails.

[PantherX]

...Do you know any other ways of verifying the correct OpenCl installation/packages are present? In every way I can check, it appears everything is present and working properly, but F@H still fails.

Unfortunately, I don't have sufficient Linux experience to help you... all I can tell you (which you may already know) is that for some reason, the client can't access the required driver/OpenCL packages:
06:23:56:ERROR:}. You may need to update your graphics drivers.
06:23:56: OpenCL: Not detected: clGetDeviceIDs() returned -1

There are members here who are more experienced at Linux that might help you once they read this topic

[_The_Editor_]

...Do you know any other ways of verifying the correct OpenCl installation/packages are present? In every way I can check, it appears everything is present and working properly, but F@H still fails.

Unfortunately, I don't have sufficient Linux experience to help you... all I can tell you (which you may already know) is that for some reason, the client can't access the required driver/OpenCL packages:
06:23:56:ERROR:}. You may need to update your graphics drivers.
06:23:56: OpenCL: Not detected: clGetDeviceIDs() returned -1

There are members here who are more experienced at Linux that might help you once they read this topic

This is the wall I'm currently beating my head against too!

OpenCL is installled and verified by running clinfo, drivers are fresh from AMD this morning!!!!

I guess I'm gonna perform some sort of rain-dance to try and summon the elder linux heads!

[Neil-B]

OK … previous caveats in that I know nothing about Linux … but have seen some posts where people use something called DDU … They uninstall FAH (keeping config details for passkey etc.) then DDU to clear all traces or drivers (I think that is what they are doing) … then they install drivers from vendor, then install that dev package (not sure if the order of those two matters) then reboot then finally reinstall FAH.

May not be a rain dance - probably more like a song and dance (sorry) … but that seems to be the most extreme I have spotted - with the exception of a disk wipe and total rebuild

… and Thanks for persevering with trying to get this working ... Honestly it isn't usually quite this tough … !!

[_The_Editor_]

… and Thanks for persevering with trying to get this working ... Honestly it isn't usually quite this tough … !!

Haha! Yea the team I'm with is made up of a bunch of co-workers from my research center... Those running windows just installed the program, hit go, and immediately started ripping on the GPU... I got jealous of their big pile of points so I've been plugging away at it! Plus I've only switched to Linux full time within the last 9 months, so having an actual problem like this to troubleshoot is a great way to learn how it works, albeit frustating at times.

So DDU is a Windows utility - as far as I can tell there's not at Linux equivilent, but that being said you shouldn't need a Linux equivilent because you can directly modify the installed packages and libraries relateively easily... Plus the AMD GPU drivers are baked directly into the Linux kernel now, so even if I purge every user added package and level the OS back to the bone-stock installation, I'll still have the standard drivers running...

Thanks for taking the time to help troubleshoot, I'll have a think and try some things today.

[Joe_H]

Not an expert in Linux either, but there have been a few install guides posted here over the past month or two. I am still on an occasionally used 16.04LTS install, so am not familiar with the changes involved going forward.

Things that have been mentioned in later versions of Ubuntu include the fahclient account needing to be added to the 'video' group to access the GPU and its associated drivers. Some later versions of Linux also need it added to the 'render' group.

One method posted was the following - viewtopic.php?f=81&t=33353#p318278

Another was posted here - viewtopic.php?f=74&t=31096#p303571

Some of the issues involved have been reported on the software GitHub site, so a later version may eventually do a better setup on newer Linux versions.

[_The_Editor_]

Not an expert in Linux either, but there have been a few install guides posted here over the past month or two. I am still on an occasionally used 16.04LTS install, so am not familiar with the changes involved going forward.

Things that have been mentioned in later versions of Ubuntu include the fahclient account needing to be added to the 'video' group to access the GPU and its associated drivers. Some later versions of Linux also need it added to the 'render' group.

One method posted was the following - viewtopic.php?f=81&t=33353#p318278

Another was posted here - viewtopic.php?f=74&t=31096#p303571

Some of the issues involved have been reported on the software GitHub site, so a later version may eventually do a better setup on newer Linux versions.

Thanks for the links, unfortunately I've already followed the guide in the first link exactly - my FAHClient launches as a systemd.service instead of an initd and has a boat load of group permissions already. I'll try launching the program as sudo just to verify it's not a permissions thing, but I feel like it's probably not.

Thanks all the same!

[_The_Editor_]

Just launched the FAHClient as root, started straight up and started running on the GPU!!!

So it was a permissions problem after all, even though I've followed all the guides to resolving permissions problems... Still, nice to have gotten this far! Thanks for your help so far everyone!

[_The_Editor_]

In case anyone else stumble down this thread and wants to try running their client as root:

First stop the client. If you're running the the standard install initd the command is:

Code: Select all

$ sudo systemctl stop FAHClient

Or if you've already set up the systemd service for running with elevated permissions:

Code: Select all

$ sudo systemctl stop FAHClient.service

Then launch the executable as root directly from the cli:

Code: Select all

$ sudo nohup /usr/bin/FAHClient /etc/fahclient/config.xml --pid-file=/var/run/fahclient.pid &

This launches the executable in your current directory, so will create a bunch of files to hold the current jobs, and logs etc. Run that for a bit and see if it solves your GPU issue, if it does you've got a permission problem.

[_The_Editor_]

Final update, and we can call this problem solved.

The previous posts that instruct to create a systemd service to manage permissions, do so by assigning the executable to a user named `fahclient`. For me, `fahclient` was assigned into the `nogroup` user-group, a group with limited permissions to mitigate the extent of damage that a `nogroup` user can cause if it does something stupid.

This, even though I had the `FAHClient.service` running with a users permissions, that user `fahclient` belonged to a group with no permissions!

So the fix, add `fahclient` to the `video` users group:

Code: Select all

$ sudo usermod -a -G video fahclient
$ sudo usermod -g video fahclient

First line appends the `video` group to the fahclient groups, second line forces `video` as `fahclient`'s primary group. A quick reload of the systemctl daemon, restart the service, and we're folding protein on the graphics card. Turns out it was a permission problem the whole time! Thanks everyone!

[Frogging101]

Glad you got it solved.

I have to ask though, what the hell does "chooch" mean?

[Neil-B]

Thank you for asking that !! ... I so need to know

[_The_Editor_]

Chooch

To operate or move properly.

A word I've picked up from a youtuber that I used to watch a lot of, AvE - https://www.youtube.com/user/arduinoversusevil

An engineer in deepest darkest Canada, doing engineeringy things in their garage/workshop. I and many others have learned a lot of new an interesting vernacular from this chanel, so much so that there's a dictionary just to translate the phrases he uses: https://avedictionary.com/chooch/