And all I am saying is that the point about Android code and BOINC doesn't appear to be relevant to this discussion. But I appreciate you trying to help.
For the record, I've long been using Gianfranco's packages for BOINC on Linux, and I confirm the following against his PPA's packages:
7.16.17 - functional with ROCm, it's what I am currently using even on Ubuntu 22.04 (had to re-use old libssl1.1 from 20.04)
7.18.1 - breaks GPU tasks on ROCm but not legacy OpenCL.
7.20.2 - breaks GPU tasks on ROCm but not legacy OpenCL.
I understand what you are stating. The old legacy amdgpu drivers had not really any issues as long as you installed them with opencl in the command line.
The new Rocm drivers however are a real mess. They won't work on the older legacy cards and they seem to be hit or miss between releases. About they only thing they work on correctly without fiddling are with the datacenter cards like the Instinct series. You can't really expect them to work on the consumer cards consistently.
Recently ROCm has worked great for me (the way it was originally bundled with amdgpu-pro to replace PAL-based OpenCL was a mess for BOINC, however), for GPUs that require them (generally Vega and later). It's that - for whatever reason - their interaction with BOINC after 7.16.17 causes FGRP tasks to fail within seconds. Whether it's ROCm or Einstein or BOINC or some interaction between them that's at fault, I've yet to determine.
And all I am saying is that
)
And all I am saying is that the point about Android code and BOINC doesn't appear to be relevant to this discussion. But I appreciate you trying to help.
For the record, I've long been using Gianfranco's packages for BOINC on Linux, and I confirm the following against his PPA's packages:
7.16.17 - functional with ROCm, it's what I am currently using even on Ubuntu 22.04 (had to re-use old libssl1.1 from 20.04)
7.18.1 - breaks GPU tasks on ROCm but not legacy OpenCL.
7.20.2 - breaks GPU tasks on ROCm but not legacy OpenCL.
Edit: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/boinc/+packages?field.name_filter=&field.status_filter=superseded&field.series_filter=focal
Edit 2: Since this thread seems to be getting more attention, I'll also point out my investigation at https://einsteinathome.org/goto/comment/201651
Soli Deo Gloria
I understand what you are
)
I understand what you are stating. The old legacy amdgpu drivers had not really any issues as long as you installed them with opencl in the command line.
The new Rocm drivers however are a real mess. They won't work on the older legacy cards and they seem to be hit or miss between releases. About they only thing they work on correctly without fiddling are with the datacenter cards like the Instinct series. You can't really expect them to work on the consumer cards consistently.
Um, I don't think that's
)
Um, I don't think that's quite what I meant.
Recently ROCm has worked great for me (the way it was originally bundled with amdgpu-pro to replace PAL-based OpenCL was a mess for BOINC, however), for GPUs that require them (generally Vega and later). It's that - for whatever reason - their interaction with BOINC after 7.16.17 causes FGRP tasks to fail within seconds. Whether it's ROCm or Einstein or BOINC or some interaction between them that's at fault, I've yet to determine.
Soli Deo Gloria
It turns out that removing
)
It turns out that removing some systemd hardening - that appears to be present since BOINC 7.16.1 - is a work-around for this issue.
https://github.com/BOINC/boinc/issues/4948
Soli Deo Gloria