amdgpu is the open source graphics driver for the latest AMD Radeon graphics cards.
- 1 Selecting the right driver
- 2 Installation
- 3 Loading
- 4 Xorg configuration
- 5 Performance tuning
- 6 Troubleshooting
Selecting the right driver
Depending on the card you have, find the right driver in Xorg#AMD. This page has instructions for AMDGPU and AMDGPU PRO.
Install the package. It provides the DDX driver for 2D acceleration and it pulls in as a dependency, providing the DRI driver for 3D acceleration.
For 32-bit application support on x86_64, also install multilib.from
Support for accelerated video decoding is provided by and packages.
Enable Southern Islands (SI) and Sea Islands (CIK) support
CONFIG_DRM_AMDGPU_CIK=Y should be be set in the config.
Even when AMDGPU support for SI/CIK has been enabled by the kernel, the radeon driver may be used instead of the AMDGPU driver.
The following workarounds are available:
amdgpuas first to load in the Mkinitcpio#Modules array, e.g.
- Blacklist the
AMD provides a proprietary, binary userland driver called AMDGPU PRO, which works on top of the open-source AMDGPU kernel driver. The driver provides OpenGL, OpenCL, Vulkan and VDPAU support. For some workloads it provides better performance than the open-source driver (example benchmark), while for others it is true the contrary (example benchmark).
A patched version of the official AMDGPU PRO driver is available as AUR.AUR in
amdgpu kernel module should load fine automatically on system boot.
If it does not happen, then:
- Make sure you have the latest package installed. This driver requires the latest firmware for each model to successfully boot.
- Make sure you do not have
vga=as a kernel parameter, since
- Also, check that you have not disabled
amdgpuby using any kernel module blacklisting.
Enable early KMS
Kernel mode setting (KMS) is supported by the amdgpu driver and is mandatory and enabled by default.
KMS is typically initialized after the initramfs stage. It is possible, however, to enable KMS during the initramfs stage. To do this, add the
amdgpu module to the
MODULES line in
MODULES="... amdgpu ..."
Now, regenerate the initramfs:
# mkinitcpio -p linux
The change takes effect at the next reboot.
Xorg will automatically load the driver and it will use your monitor's EDID to set the native resolution. Configuration is only required for tuning the driver.
If you want manual configuration, create
/etc/X11/xorg.conf.d/20-amdgpu.conf, and add the following:
Section "Device" Identifier "AMD" Driver "amdgpu" EndSection
Using this section, you can enable features and tweak the driver settings.
Enabling video acceleration
The following options apply to
man amdgpu first before setting driver options.
DRI sets the maximum level of DRI to enable. Valid values are 2 for DRI2 or 3 for DRI3. The default is 3 for DRI3 if the Xorg version is >= 1.18.3, otherwise DRI2 is used:
Option "DRI" "3"
TearFree controls tearing prevention using the hardware page flipping mechanism. If this option is set, the default value of the property is set to auto, which means that TearFree is on for outputs with rotation or other RandR transforms:
Option "TearFree" "true"
No HDMI/DP Audio
The open source AMDGPU driver relies on the DAL code that currently being worked on. Until DAL is mainlined, audio suppport for HDMI and DisplayPort will not be available. The only current way to get HDMI and DisplayPort audio is to install the #AMDGPU PRO driver.
Incorrect screen position on HDMI
Xorg or applications won't start
- "(EE) AMDGPU(0): [DRI2] DRI2SwapBuffers: drawable has no back or front?" error after opening glxgears, can open Xorg server but OpenGL apps crash.
- "(EE) AMDGPU(0): Given depth (32) is not supported by amdgpu driver" error, Xorg won't start.
Setting the screen's depth under Xorg to 16 or 32 will cause problems/crash. To avoid that, you should use a standard screen depth of 24 by adding this to your "screen" section (assuming you have one, assuming you don't add this to
Section "Screen" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection
Screen artifacts and frequency problem
If you have screen artifacts when setting your screen frequency up to 120+Hz your "Memory Clock" and "GPU Clock" are certainly too low to handle the screen request.
A workaround  is saving
There is a GUI solution  were you can manage the "power_dpm" with AUR and AUR.