Amd drivers linux arch

Arch Linux User Repository

Here’s a quick guide to install amdgpu-dkms + mesa-git to get Navi cards working on Linux 5.2.x:

Note that amdgpu-dkms cannot be used with linux-zen (the driver will segfault on boot and you need a hard poweroff to turn the machine off).

Latest Comments

sirn commented on 2020-08-02 11:34 (UTC) (edited on 2020-08-02 11:39 (UTC) by sirn)

@gardotd426 unfortunately I’m no longer using Arch. Since AMDGPU now targets 5.4.x it should be relatively easy to repackage without the need to patch for compatibility.

From a quick glance, 20.30 code this seems to be 5.6 driver code plus few features backported from -staging (mainly support for unreleased Sienna Cichlid/Navi 21/RX 6000 whatever you name it). If anything, linux-amd-staging-drm-next-git should contains all the fixes that exists in 20.30.

gardotd426 commented on 2020-08-02 11:02 (UTC)

@sirn, Please update this to the actual newest driver release (20.30). There is a suggestion that the 20.30 dkms driver solves long-standing driver crashes for some Navi users (and no, 20.30’s dkms is not identical to the upstream kernel driver).

The entire package structure of the tarball has changed, amdgpu-dkms’s versioning system seems to have changed, the PKGBUILD fails even with substituting the correct url, package number version, all that, because of a changed directory structure within the .deb package.

gbin commented on 2020-07-14 03:43 (UTC) (edited on 2020-07-14 03:48 (UTC) by gbin)

[Ignore, please set this as DEPRECATED as the module has been merged upstream . ]

This package fails to compile so far with: linux-5.7.8-arch1-1 (look for the drmP.h that doesn’t exist anymore) linux-5.7.8-AMD (look for the drmP.h that doesn’t exist anymore) linux-5.4.51-1-lts (/include/kcl/kcl_reservation.h:4:10: fatal error: linux/reservation.h: No such file or directory)

Can we set the dependencies right so we don’t have to fish in the dark for a compatible linux version? Does the 19.50 fix some of those issues?

sirn commented on 2019-10-20 04:02 (UTC)

@TomCatT you should not need to use this package with kernel 5.3, the in-kernel amdgpu driver is already newer than AMDGPU 19.30.

TomCatT commented on 2019-10-18 19:04 (UTC)

LD [M] /var/lib/dkms/amdgpu-19.30/855429/build/ttm/amdttm.o make[1]: [scripts/Makefile.build:497: /var/lib/dkms/amdgpu-19.30/855429/build/amd/amdgpu] Error 2 make: [Makefile:1626: module/var/lib/dkms/amdgpu-19.30/855429/build] Error 2 make: Leaving directory ‘/usr/lib/modules/5.3.6-1-MANJARO/build’

sirn commented on 2019-08-24 15:03 (UTC)

@Terence I’m out of town at the moment, but I’ll look into it as soon as I’m back!

Terence commented on 2019-08-24 14:23 (UTC) (edited on 2019-08-24 14:23 (UTC) by Terence)

@sirn I tried it again but for some reason now it’s working. I’m wondering it was something with my graphic card (Vega 56).

• linux-tkg 5.2 with ck-patcheset and some stuffs from zen: https://github.com/Tk-Glitch/PKGBUILDS/tree/master/linux52-tkg
• mesa-aco-git
• Put the following to enable freesync:

Section "Device" Identifier "AMD" Driver "amdgpu" Option "VariableRefresh" "true" Option "DRI" "3" EndSection 

And the black screen occured when I turned it on from the monitor settings.

PS: Do you think you can include the 2 patches (radeon_extratemps-5.2.patch and amdgpu_extratemps-5.2.patch) from the repo I linked you?

sirn commented on 2019-08-24 04:00 (UTC) (edited on 2019-08-24 04:01 (UTC) by sirn)

@Terence I don’t use Freesync, but can you tell me more about your setup?

Terence commented on 2019-08-23 22:46 (UTC)

Hmm freesync seems broken with this package? I get a black screen upon activating it.

Terence commented on 2019-08-22 22:06 (UTC)

@sirn Ah ok thank you very much for the clarification. Do you think you can include https://github.com/matszpk/amdgpu-vega-hotspot ?

Copyright © 2004-2023 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

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

Источник