Been running the tests at Einstein using their beta app that relies on the RocM driver. Boinc does not see multiple GPUs, only the one in the X16 slot. Going to post url to the message over at Einstein rather than duplicate it all here. I actually was unaware of this driver prior to seeing the complaint over there that the app was not working.

https://einsteinathome.org/content/clbuildprogramfailure-02mdf-gw-opencl-ati?page=1#comment-175716

It is supposed to be the next big thing for compute on AMD. Still in infancy regarding majority of compatibility with BOINC projects.

yea, next big thing if you buy the best AMD motherboard and GPUs money can buy.. Not going to repost everything from that thread over at Einstein, summery below as applies to linux:

ROCm or rocM or WTF it is called requires you have as many GEN3 PCIe lanes to the GPU as you have GPUs. It is part of all recent amdpro drivers, just needs to be activated to work.

Once installed, if you do not have enough "PCIe atomics" (nice word for gen3) then those GPUs not having a gen3 lane to the CPU disappear for apps like boinc. They will show up using, for example "clinfo", or "sensors" or any diagnostics program. So, like me, if you have 5 GPUs but boinc only sees a single one and all the diagnostics you run indicated there are 4 more GPUs available you starts suspecting that something is wrong with BOINC not realizing the problem is the AMD driver that wants to run only on a superhighway and ignores all the little x1 back roads.

Do you say that boinc works for you with a single card and ROCm? This will be very interesting to know.

You shouldn't need atomics for vega and later cards. Only for older. With a VEGA 10 I was running on PCIe 1.1. I was on ROCm 1.9.
I fail to run Folding@Home so if I can run BOINC that would be nice.

Been running the tests at Einstein using their beta app that relies on the RocM driver.

I've highlighted the bit that is just plain wrong. There is no app that needs ROCm. Maybe it would be a good idea to read the whole thread in it's entirety and the following key points would then emerge.

* A user who had a properly configured ROCm system posted about the GW app crashing.

• The precise error message (clearly listed) pointed to a coding style in the Einstein app that wasn't supported under ROCm.
  
• When Bernd's attention was eventually attracted, the problem got passed to the app author/developer.
  
• A 'fix' was quickly developed and a test app was distributed that solved the problem for ROCm.
  
• I ran this app deliberately on non-ROCm systems to make sure there were no regressions. There was no problem.
  * Bernd has since taken the app out of beta. It became the default app. To my knowledge, there continue to be no app related problems.

I suspect any problem you have is down to you trying to use non-ROCm-compliant hardware configurations. Have you really tried reading some documentation? Here are a couple of key points from that link that might be appropriate to your setup. You should read the whole document carefully to really be sure your setup is fully compliant with all the restrictions.

As such, by default ROCm requires that these GPUs be installed in PCIe slots with PCI Express 3.0 or higher capabilities with transfer rates of 8.0 GT/s in either x16 or x8 lanes. The system configuration can have the PCIe slots directly on CPU’s root port or a PCIe switch, but everything between the CPU and the GPU must support atomics.

Note that the physical PCIe slot size does not guarantee support for ROCm. Some motherboards have physical x16 PCIe slots, but the PCIe connector is electrically connected as PCIe Express 2.0 to the southbridge. Since the PCIe slot connector matters to the GPU, care must be taken to not place them in on motherboards configured this way.

The ROCm kernel driver logs if ROCm capable GPUs are installed on system that does not support PCIe atomics.

Example text from kernel log:

kfd: skipped device 1002:7300, PCI rejects atomics

You actually posted that very message (shown above) over at Einstein. I know nothing about ROCm but the documentation (which I've just now found and read) seems to be saying that your problem is your non-ROCm-compliant hardware setup. In other words, nothing to do with any purported conflict between ROCm and BOINC. You should try to be less misleading in your choice of thread title.

---

Cheers,
Gary.