Arch Linux

lynix

Member

From: Karlsruhe, Germany

Registered: 2008-04-23

Posts: 230

OpenCL with Navi2 - not supported yet?

Hi,

I'm trying to get OpenCL working with a Navi2 card (RX 6800XT).

I'm running the opensource amdgpu driver and would prefer to keep it this way, avoiding amdgpu-pro. If I understand the Wiki article correctly I should be fine going with 'opencl-mesa'.

Unfortunately 'clinfo' gives me:

Number of platforms                               1
  Platform Name                                   Clover
  Platform Vendor                                 Mesa
  Platform Version                                OpenCL 1.1 Mesa 21.0.2
  Platform Profile                                FULL_PROFILE
  Platform Extensions                             cl_khr_icd
  Platform Extensions function suffix             MESA

  Platform Name                                   Clover
Number of devices                                 1
  Device Name                                     AMD Radeon RX 6800 XT (SIENNA_CICHLID, DRM 3.40.0, 5.11.15-arch1-2, LLVM 11.1.0)
  Device Vendor                                   AMD
  Device Vendor ID                                0x1002
  Device Version                                  OpenCL 1.1 Mesa 21.0.2
  Device Numeric Version                          0x401000 (1.1.0)
  Driver Version                                  21.0.2
  Device OpenCL C Version                         OpenCL C 1.1 
  Device Type                                     GPU
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Max compute units                               72
  Max clock frequency                             2575MHz
  Max work item dimensions                        3
  Max work item sizes                             256x256x256
  Max work group size                             256
=== CL_PROGRAM_BUILD_LOG ===
fatal error: cannot open file '/usr/share/clc/gfx1030-amdgcn-mesa-mesa3d.bc': No such file or directory
(snip)

Does anybody know if my gpu ist just not supported yet?

I mean, the card is quite new and I would perfectly understand if there is just no support in mesa for it yet. Just trying to verify that I'm not misconfiguring something.

Thanks!

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,893

Re: OpenCL with Navi2 - not supported yet?

Nope, nothing misconfigured .

gallium-opencl in mesa relies on external libraries to support chipsets .
For amd cards those come from the llvm libclc project libclc from llvm.org .

libclc supports r600 and amdgcn targets, but nothing newer. (basically everything amd released after polaris11 is unsupported by libclc )

You have 2 choices for your Navi21 card :
- the (mostly) proprietary opencl-amd
no need to install any other amdgpu-pro component, opencl-amd contains everything needed for opencl and works well with opensource driver.

- rocm
opensource by amdgpu ,  officially it doesn't seem to support navi21 .

recent releases of opencl-amd use some code from RocM, so opencl-amd should now be described as partially closed source.

I'd start with opencl-amd (don't forget to remove opencl-mesa to keep things simpler).

Last edited by Lone_Wolf (2021-04-24 11:40:13)

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

upgrayedd

Member

Registered: 2021-04-30

Posts: 1

Re: OpenCL with Navi2 - not supported yet?

I've not been lucky enough to get a 6800XT, but I got a 6700XT which afaik works in a subset of versions that the 6800XT does, and FWIW so far I've not had much luck with opencl-amd yet (as of 21.10.something).  Nor with ubuntu 20.04 and the amd release opencl-amd is based on.  But I have a chroot built from an image I found which DOES work with hashcat, phoenixminer and clinfo on either of those OSes and with amdgpu from many kernel versions, so I'm pretty sure it's just a matter of finding the right userspace bits, which I'm sorting through presently.