AMDGPU

AMDGPU is Article description:: the next generation family of open source graphics drivers using the new Display Core (DC) framework for Vega GPUs and Raven Ridge APUs. It is however also capable of handling newer AMD/ATI Radeon graphics cards based on GCN1.1+, namely the Southern Islands, Sea Islands, Volcanic Islands, and Arctic Islands chipsets.

If the card in question does not appear in the Feature support section below, it is not supported by AMDGPU. In that case check the radeon article, which contains instructions for older open-source AMD/ATI Radeon graphics card drivers.

Prior to Kernel 4.15 Display Core (DC, developed from Display Abstraction Layer, DAL) was not included in the vanilla kernel sources, thus AMDGPU was not able to provide graphics output to a monitor on VEGA and later chips.

Installation
Setting up a system to use AMDGPU requires identifying the proper card, installing the corresponding firmware, configuring the kernel, and installing the X11 driver.

Hardware detection
To choose the right driver, first detect the graphics card. Use lspci for this task:

Check the output for one of the product names listed in the table below.

Feature support

 * A GCN stands for Graphics Core Next Architecture and was introduced with the Radeon HD7000 series (GCN1.0). Raven Ridge APUs feature a mobile Vega graphics core and are referred to as DCN1.0.
 * 1 Support is optional in the kernel.
 * 2 Since kernel 4.7-rc6
 * 3 Experimental, optional support added since kernel 4.9-rc1
 * 4 usable for graphics output since kernel 4.15
 * 5 planned for kernel 4.16 to be finally usable

Firmware
It is necessary to install the proper firmware (or microcode) for your card. Firmware files are provided by. Make sure you have all necessary files for your hardware in your configuration file if you use the savedconfig flag.

The firmware files installed this way will be incorporated into the kernel.

Kernel
Set the following kernel options for the graphic chipsets mentioned above:

The options from the Sound card support menu need only to be set if the card supports HDMI or DisplayPort audio and you want to use it. On newer kernels where Enable AMD Audio CoProcessor IP support appears, that should also be set.

AMDGPU with Display Core works primarily for VEGA10 (GCN5.0) and RAVEN (with DCN 1.0) GPUs/APUs. Older cards (GCN1.1 and newer) can be activated in the kernel or using the kernel command line option amdgpu.dc=1 and provide better (but experimental) support than the older radeon kernel module.

See the radeon article for more details about using HDMI/DisplayPort audio.

Incorporating firmware
The firmware package installed in an earlier section provides files in (for Volcanic Islands and Arctic Islands cards) and/or  (for Southern Islands and Sea Islands cards). Configure the kernel to use the correct firmware files by setting the following options:

should be replaced with the full list of filenames given with the chipset's name in the table below, separated by spaces. Use  to expand the filenames. E.g. for Volcanic Islands/TONGA, run

Then  is the string that should be put into the kernel configuration.

After expanding the firmware file names from the following table and copying them into the kernel configuration, save the configuration, then compile and install the new kernel and modules.

USE flags
Set the USE flags for the  driver as needed.

The package will be automatically emerged as a dependency of after setting VIDEO_CARDS following the instructions in the next section.

Emerge
Portage uses the VIDEO_CARDS variable for enabling support for various graphics cards in packages. Setting VIDEO_CARDS to  (see the feature matrix section above) and asking Portage to update changed USE flags in the @world set will pull in the correct driver:

The system should now be prepared to use amdgpu after the next reboot.

dpm
In most cases since Linux 3.13 dpm is the default power management method. Unlike with dynpm and profile methods enabling or disabling dpm must be done via kernel command line. Users who have GPUs older than HD5000 -series may need to add  on kernel command-line to enable dpm.

In most cases just enabling dpm is enough but there are some tunable settings. dpm has three main modes of operating: battery, balanced and performance. The names are quite self-explanatory. To set the GPU to most performant mode the following command is needed to run:

Even if GPU is set to performance -mode it does not mean that the GPU is running with highest clockspeeds at all the time. This is the normal and intended way how dpm works. If it is desirable to run the GPU at the highest speeds all the time, even if there is no actual load, users can then run following command:

This manually overrides dpm's own bahaviour. This is however mainly intended for testing purposes but may also be useful when doing GPU benchmanks.

To give control back to dpm following command is needed to run:

Kernel
Older kernels which do not support the amdgpu driver will not provide the AMDGPU option. But even with amdgpu there is no video output on VEGA and newer chips without DC (Display Code), which was first included in vanilla Kernel 4.15. In both cases, trying an unstable (denoted by a ) kernel can provide the required kernel-sources.

SME
Currently, amdgpu does not work with AMD Secure Memory Encryption (SME) enabled, so you need to disable its use either in the kernel configuration or on the kernel command line (i.e. in as part of GRUB_CMDLINE_LINUX ).

AMD_MEM_ENCRYPT may remain enabled, but either AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT must remain unset or the kernel command line option mem_encrypt=off must be used in order to turn Memory Encryption off. With mem_encrypt=on amdgpu fails to load and the screen stays frozen as it was at the time of the modprobe, or, when included in the kernel, in early printk.

AMDGPU/RadeonSI drivers do not work
If the graphics card is not supported by including  and   alone in VIDEO_CARDS, try adding   to 's VIDEO_CARDS definition. For example:

After the values have been set update the system so the changes take effect:

Full-screen windows perform poorly
The installed version of may be too old. Try emerging an unstable version.

Pixel-wide line on left side of screen when X server is started when using a Southern Island card
Those using a Southern Island card may notice a pixel-wide line on the left of the screen in both the X server and console environments after having started a X server (This issue doesn't exist when using Linux 4.13 or newer). This is a known bug. Disabling audio through HDMI for that display resolves this issue. This may be done via:

where  should be replaced by the name of the output, obtained by running

For more information please see https://bugs.freedesktop.org/show_bug.cgi?id=97861.

Wrong ELF class
ERROR ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_intel.so: wrong ELF class: ELFCLASS32

ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32

INFO

1) This issue is present if vulkan is compiled with  on 64bit AMD64(?) system. Ignoring the error is sane.

2) Build is corrupted `strace vulkaninfo` should be invoked prior to reporting bug. a) recompile vulkan+mesa+(nvidia,intel,amd driver). b) check strace of vulkanifo which is present in vulkan-tools.

RELEVANT

https://github.com/KhronosGroup/Vulkan-Loader/issues/108#issuecomment-443294716

External resources

 * A list of RadeonSI articles on the Phoronix site.