Arch linux amd driver

abbotto / arch-amd-catalyst

This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters

# INSTRUCTIONS

# ==============

# IMPORTANT NOTICE:

# “catalyst-test”, from AUR, contains the “latest” AMD/ATI testing/beta drivers, primarily for newer cards.

# Please note that Radeons HD 2 3 4 xxx ARE NOT SUPPORTED

# Reference: https://aur.archlinux.org/packages/catalyst-test/

# Reference: https://wiki.archlinux.org/index.php/AMD_Catalyst

# Reference: http://www.ramblgyrl.com/2014/11/install-catalyst-drivers-on-arch-linux/

# ==============

# 1. Install Yaourt

# In the terminal window, type the following:

sudo nano /etc/pacman.conf

# Add the following repository:

[archlinuxfr]

SigLevel = Never

Server = http://repo.archlinux.fr/$arch

# Next, update and install:

sudo pacman -Sy yaourt

# 2. Install Catalyst

# While in the terminal open and type the following:

yaourt catalyst-test

# When asked to remove any conflicting packages, respond with yes [y].

#3. Post Install

# Make sure to install ‘acpid’ by typing the following:

sudo pacman -S acpid

# Then, enter each command below:

sudo systemctl enable atieventsd

sudo systemctl start atieventsd

sudo systemctl enable catalyst-hook

sudo systemctl start catalyst-hook

# Next, we have to write the initial config. Type the following:

sudo aticonfig —initial

# Lastly, we need to configure the bootloader. Follow the appropriate instructions for your bootloader:

# SYSLINUX BOOTLOADER

# Edit “/boot/syslinux/syslinux.cfg” and add nomodeset to the APPEND line, e.g.:

APPEND root=/dev/sda[x] rw nomodeset

# GRUB2 BOOTLOADER

# Edit the “/etc/default/grub” file, and modify the GRUB_CMDLINE_LINUX= line so it looks like this:

GRUB_CMDLINE_LINUX=»nomodeset»

# Then:

sudo grub-mkconfig -o /boot/grub/grub.cfg

# 3. Last But Not Least…

# Reboot:

sudo reboot

Источник

DESCRIPTION

amdgpu is an Xorg driver for AMD RADEON-based video cards with the following features:

• Support for 8-, 15-, 16-, 24- and 30-bit pixel depths; • RandR support up to version 1.4; • 3D acceleration;

SUPPORTED HARDWARE

The amdgpu driver supports SI and newer families’ video cards.

CONFIGURATION DETAILS

Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.

The following driver Options are supported:

Option «SWcursor» «boolean« Selects software cursor. The default is off. Option «Accel» «boolean« Enables or disables all hardware acceleration.
The default is on. Option «ZaphodHeads» «string« Specify the RandR output(s) to use with zaphod mode for a particular driver instance. If you use this option you must use this option for all instances of the driver.
For example: Option «ZaphodHeads» «LVDS,VGA-0» will assign xrandr outputs LVDS and VGA-0 to this instance of the driver. Option «DRI» «integer« Define 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 2 for DRI2. Option «EnablePageFlip» «boolean« Enable DRI2 page flipping. The default is on. Option «TearFree» «boolean« Set the default value of the per-output ‘TearFree’ property, which controls tearing prevention using the hardware page flipping mechanism. TearFree is on for any CRTC associated with one or more outputs with TearFree on. Two separate scanout buffers need to be allocated for each CRTC with TearFree on. If this option is set, the default value of the property is ‘on’ or ‘off’ accordingly. If this option isn’t set, the default value of the property is auto, which means that TearFree is on for rotated outputs, outputs with RandR transforms applied and for RandR 1.4 secondary outputs, otherwise off. Option «VariableRefresh» «boolean« Enables support for enabling variable refresh on the Screen’s CRTCs when an suitable application is flipping via the Present extension.
The default is off. Option «AsyncFlipSecondaries» «boolean« Use async flips for secondary video outputs on multi-display setups. If a screen has multiple displays attached and DRI3 page flipping is used, then only one of the displays will have its page flip synchronized to vblank for tear-free presentation. This is the display that is used for presentation timing and timestamping, usually the one covering the biggest pixel area of the screen. All other displays («Secondaries») will not synchronize their flips. This may cause some tearing on these displays, but it prevents a permanent or periodic slowdown or irritating judder of animations if not all video outputs are running synchronized with each other and with the same refresh rate. There is no perfect solution apart from perfectly synchronized outputs, but this option may give preferrable results if the displays in a multi-display setup mirror or clone each other. The default is off. Option «AccelMethod» «string« Setting this option to none disables use of the glamor acceleration architecture. In that case, all 2D rendering is done by the CPU, but 3D and video hardware acceleration can still work. This is mainly useful for OpenGL driver bring-up.
The default is to use glamor.

The following driver Option is supported for glamor :

Option «ShadowPrimary» «boolean« This option enables a so-called «shadow primary» buffer for fast CPU access to pixel data, and separate scanout buffers for each display controller (CRTC). This may improve performance for some 2D workloads, potentially at the expense of other (e.g. 3D, video) workloads. Note in particular that enabling this option currently disables page flipping. The default is off.

SEE ALSO

Xorg(1), xorg.conf(5), Xserver(1), X(7)

Источник

AMDGPU PRO

This page describes close source drivers for AMD GPUs.

Purpose of proprietary components

AMD releases their open source drivers via standard distribution channels. And they also periodically do releases of their Radeon Software for Linux suite, which includes both open and proprietary components. Open source components are not needed from there, and proprietary components are repacked from the latest ubuntu lts version. They are published in AUR in the amdgpu-pro-installer package base.

Comment by John Bridgman from AMD explaining why they still package close source drivers:

• customers using slower moving enterprise/LTS distros which do not automatically pick up the latest graphics drivers — we offer them both open source and proprietary/workstation options
• customers using workstation apps who need the extra performance/certification from a workstation-oriented driver (although Marek has done a lot of great work over the last year to improve Mesa performance on workstation apps)
• The third target audience is customers looking for ready-to-go OpenCL, either for use with the packaged open/closed drivers or with the upstream-based stack in a recent distro.

There are several proprietary components: OpenGL, OpenCL, Vulkan and AMF. Sometimes you may want to use these components due to specific features that open source components may lack.

AMDGPU PRO OpenGL is a proprietary, binary userland driver, which works on top of the open-source amdgpu kernel driver. From Radeon Software 18.50 vs Mesa 19 benchmarks article: When it comes to OpenGL games, the RadeonSI Gallium3D driver simply dominates the proprietary AMD OpenGL driver. Users of graphic cards other than Radeon Pro are advised to use the amdgpu graphics stack. Mostly used because of lacking compatibility layers that some software relies on. See gentoo wiki linked below.

AMDGPU PRO Vulkan — currently the only implementation that has ray tracing (however, reported by users as glitchy). Also it is required dependency for AMF.

AMDGPU PRO OpenCL — used because Mesa OpenCL is not fully complete. Proprietary component only for Polaris GPUs. The onward GPUs use the open ROCm OpenCL.

AMDGPU AMF — used for gpu encoding/decoding.

Installation

For proprietary OpenGL implementation, use the amdgpu-pro-installer package base. It contains all the following packages:

• amdgpu-pro-oglpAUR : For proprietary OpenGL implementation
• lib32-amdgpu-pro-oglpAUR : For proprietary OpenGL implementation 32 bit applications support
• vulkan-amdgpu-proAUR : For proprietary Vulkan implementation
• lib32-vulkan-amdgpu-proAUR : For proprietary Vulkan implementation 32 bit applications support
• amf-amdgpu-proAUR : For Advanced Media Framework implementation

Note: OGLP is not a performance optimization of opengl, it is an all-new GL driver codebase written from scratch, based on the PAL architecture. in version > 22.20.5 it replaces the libgl

For available OpenCL implementations see GPGPU#AMD/ATI.

For OBS to work with it use obs-studio-amf AUR

Usage

Using proprietary OpenGL

Launch your application with progl prefix, for example:

How to ensure you are using AMDGPU-PRO driver

Run the following command:

$ glxinfo | grep "OpenGL vendor string" | cut -f2 -d":" | xargs

If it returns AMD , then you are running open source driver. If it returns Advanced Micro Devices, Inc. , then you are running proprietary driver.

Alternatively, run glmark2. When using open driver, in OpenGL Information you will see:

GL_VENDOR: AMD GL_RENDERER: Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.7-arch1-1, LLVM 11.0.1) GL_VERSION: 4.6 (Compatibility Profile) Mesa 20.3.3

But when using closed driver, you will see:

GL_VENDOR: ATI Technologies Inc. GL_RENDERER: Radeon RX 580 Series GL_VERSION: 4.6.14756 Compatibility Profile Context

Using proprietary Vulkan

Launch your application with vk_pro , for example:

Using Advanced Multimedia Framework

Troubleshooting

Intel + AMD hybrid graphics

For users of a hybrid setup with both an Intel GPU and an AMD GPU, usage of the proprietary AMDGPU Pro Workstation Driver might not work as expected due to different MESA implementations.

The symptom is the following: when you boot your machine, you get a black screen, but with your mouse cursor is moving normally.

Unfortunately, Reverse PRIME is not a solution. See the developer response.

Uninstalling packages

If you are in trouble, for example, you cannot login to your system due to black screen, you can revert all back by uninstalling all packages related to AMDGPU PRO.

Switch a virtual console (with e.g. Ctrl+Alt+F2 ), login and run:

# pacman -R $(pacman -Qg Radeon_Software_for_Linux | cut -f2 -d" ")

Southern Islands (SI) or Sea Islands (CIK) GPUs

If using Southern Islands (SI) or Sea Islands (CIK) GPU, when running clinfo , you get:

amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only compatible with 3.x.x.

then ensure you are using amdgpu driver, but not radeon.

Check which driver is currently in use:

03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265/M365X/M465] Subsystem: Acer Incorporated [ALI] Aspire V5 Radeon R7 M265 Kernel driver in use: radeon Kernel modules: radeon, amdgpu

Firmware and AMD drivers

AMD drivers and firmware (especially recent firmware) can get out of sync and create issues or not work at all. You can search in the journal for VNC :

system VCN FW Encode interface version=1.9, expected version=1.8

Downgrading the firmware seems to fix the problem.

• As of 2023-05-06, the 7900 cards works with the linux-firmware version 20221214.f3c283e-1, see amdgpu-pro GitHub issue.
• As of 2023-05-30 version 23.10-1595145 of the AMDGPU PRO seems to fix the 7900 cards if use the linux-firmware-gitAUR

See also

Источник