I've been trying for a week to get seti working.
It seems that it refuses to download any gpu binary files ie: setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah
I had a hacked setup downloading tasks and working if I created a app_info.xml with setiathome_8.04_x86_64-pc-linux-gnu__opencl_ati5_sah,
but the same thing fails if I try to use 8.22 :
SETI@home: Notice from BOINC
Task blc14_2bit_guppi_58691_69181_HIP39096_0055.14995.0.21.44.210.vlar_1 postponed for 300 seconds: Can't read CL file

Why can't I just add the seti project to boinc and start downloading opencl tasks and working ?
einstein, amicable numbers, and numberfields work out of the box no problems.

Do I really need to manually download every file for the projects dir and setup an app_info.xml file ?

---

No. What you will need to do is the download and install a compatible OpenCL programming language runtime support package, to work alongside your graphics driver.

You need to install the OpenCL component of your AMD drivers. Something like:

$ ./amdgpu-install -y --opencl=legacy

These AMD docs show the installation commands for OpenCL

https://amdgpu-install.readthedocs.io/en/latest/install-overview.html?highlight=OpenCL

https://amdgpu-install.readthedocs.io/en/latest/install-script.html?highlight=OpenCL#specifying-an-opencl-implementation

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I'm using ROCm in linux on an unsupported distro. I created my own packages, because that's the only option.

This is how I was able to trick boinc into letting me download seti workunits and the binaries:

cd ~/boinc-home/projects/setiathome.berkeley.edu
wget http://boinc2.ssl.berkeley.edu/beta/download/setiathome_8.22_x86_64-pc-linux-gnu__opencl_ati5_sah
wget http://boinc2.ssl.berkeley.edu/beta/download/MultiBeam_Kernels_rXXXX.cl XXXX = svn revision used to build the binary supposdely. 3584
Then I have to create a custom app_info.xml

My laptop I used setiathome_8.22_x86_64-pc-linux-gnu__opencl_atiapu_sah

It works after doing this, I guess this is my only option unless I become an ubuntu user or whatever distro AMD or whoever else likes.

I'm not sure what is being checked differently for seti causing it to not work out of the box. Other projects don't have a problem with opencl/ROCm.

---

Not all projects work with ROCm, eg. Milkyway fails straight away with CL errors as well.
Einstein and others work, though I found ROCm OpenCL is still a bit slower than the AMDGPU-PRO OpenCL.

I'm running Ubuntu 19.04, which is also unsupported by the official package.
I created http://kerbodyne.com/boinc/create_amdgpu-ocl-pkg.sh (based on an Arch build script I found) to extract the OpenCL libs from the official driver archive and build a package that just installs these few files.
Maybe it can serve as a reference for your own Slack version, so you can finally get the "real driver" working on your machine.

---

It's neat to see you managed to get the stock multibeam OpenCL app working with ROCm. The reason this doesn't happen automatically is that the the official SETI@Home plan classes that pick the apps for you are based on OpenCL and core driver versions that don't have any overlap with the versions reported by the ROCm OpenCL Runtime. Only the Astropulse app will automatically chose the ROCm OpenCL cards because of the flexible of version constraint in the opencl_ati_100 plan class the Astropulse OpenCL app uses.

You can see the beta plan_class_spec.xml here for the version constraints that have been preventing ROCm users from participating.

---