Arch linux amd drivers

abbotto / arch-amd-catalyst

# 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

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Arch Linux

You are not logged in.

#1 2018-04-21 15:15:39

AMD GPU Drivers Installation

Guys, I don’t have much experience with AMD drivers and their compatibility. I recently purchased a laptop with amd gpu. However, I am unable to decide which packages should I install for the it. The lspci generated this output for the graphics card and I am really uncertain which one is needed.
Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] (rev c1)
Please help. Thanks!

#2 2018-04-21 21:18:47

Re: AMD GPU Drivers Installation

All you can do is search, really. Take a look in the wiki and here.

It’s important to know what specific card is in your computer first. One specific model is preferred over lspci output. Can you find some specifications for your laptop somewhere?

#3 2018-04-21 21:52:03

Re: AMD GPU Drivers Installation

What is the full output of `lspci -nnk`

#4 2018-04-22 09:09:24

Re: AMD GPU Drivers Installation

First of all — take a look at: https://support.amd.com/en-us/download and try «Manually select your driver». If the driver for your GPU is: RN-AMDGPU-UNIFIED-LINUX you should to use amdgpu, see: https://wiki.archlinux.org/index.php/AMDGPU. You can use AMDGPU-PRO from AUR, but only when you really had to do this. AMDGPU is good enaugh for common use.
If the driver will be Crimson (Catalyst) you should to use radeonsi, see: https://wiki.archlinux.org/index.php/ATI. Only when your driver is See or Southern Islands you can try to use amdgpu, too (but if I think well, the proper driver for R7 M260 is amdgpu).

#5 2018-04-22 10:06:10

Re: AMD GPU Drivers Installation

Yes, R7 M260 works with AMDGPU. This is actually the best case scenario — the driver is included in the kernel, so you don’t need to install anything. Don’t download anything from AMD’s website (that driver has no benefit at all) and don’t install the AMDGPU-PRO package from AUR unless you absolutely need FreeSync right now. I think that’s the only popular PRO feature that’s not yet in the kernel, but it’s only a matter of months until we also see it there.

edit: If you want to play a game in steam that’s using the vulkan api you need to install vulkan-radeon. Since steam games cannot make use of pacman’s dependency resolution you need to think of dependencies like this for yourself.

edit2: And please check if you’ve installed xf86-video-amdgpu. I thought xorg-server depends on it, but according to the package browser it doesn’t.

Last edited by thorstenhirsch (2018-04-22 10:24:58)

#6 2018-04-25 13:25:24

Re: AMD GPU Drivers Installation

I have installed xf86-video-amdgpu and it does show up in the display driver list. However, the boot log shows some bugs in there.
Output of lspci -nnk

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1028:0810]
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07)
Subsystem: Dell UHD Graphics 620 [1028:0810]
Kernel driver in use: i915
Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: Dell Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [1028:0810]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)
Subsystem: Dell Sunrise Point-LP USB 3.0 xHCI Controller [1028:0810]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Thermal subsystem [8086:9d31] (rev 21)
Subsystem: Dell Sunrise Point-LP Thermal subsystem [1028:0810]
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 [8086:9d60] (rev 21)
Subsystem: Dell Sunrise Point-LP Serial IO I2C Controller [1028:0810]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: Dell Sunrise Point-LP CSME HECI [1028:0810]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 RAID bus controller [0104]: Intel Corporation 82801 Mobile SATA Controller [RAID mode] [8086:282a] (rev 21)
Subsystem: Dell 82801 Mobile SATA Controller [RAID mode] [1028:0810]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 [8086:9d10] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 [8086:9d14] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 [8086:9d15] (rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:9d4e] (rev 21)
Subsystem: Dell Device [1028:0810]
00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-LP PMC [8086:9d21] (rev 21)
Subsystem: Dell Sunrise Point-LP PMC [1028:0810]
Kernel driver in use: intel_pmc_core
00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21)
Subsystem: Dell Sunrise Point-LP HD Audio [1028:0810]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21)
Subsystem: Dell Sunrise Point-LP SMBus [1028:0810]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1002:6900] (rev c1)
Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [1028:0810]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 07)
Subsystem: Dell RTL810xE PCI Express Fast Ethernet controller [1028:0810]
Kernel driver in use: r8169
Kernel modules: r8169
03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31)
Subsystem: Dell QCA9377 802.11ac Wireless Network Adapter [1028:1810]
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

Output of dmesg | grep amdgpu

Apr 25 18:21:44 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: enabling device (0006 -> 0007)
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 — 0x000000F4FFFFFFFF (4096M used)
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 — 0x000000000FFFFFFF
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: 4096M of VRAM memory ready
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: 4096M of GTT memory ready.
Apr 25 18:21:44 archlinux kernel: [drm] amdgpu: irq initialized.
Apr 25 18:21:44 archlinux kernel: amdgpu: [powerplay] amdgpu: powerplay sw initialized
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000000400080, cpu addr 0xffffb0cac1621080
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000000400100, cpu addr 0xffffb0cac1621100
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000000400180, cpu addr 0xffffb0cac1621180
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000000400200, cpu addr 0xffffb0cac1621200
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000000400280, cpu addr 0xffffb0cac1621280
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000400300, cpu addr 0xffffb0cac1621300
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 6 use gpu addr 0x0000000000400380, cpu addr 0xffffb0cac1621380
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 7 use gpu addr 0x0000000000400400, cpu addr 0xffffb0cac1621400
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 8 use gpu addr 0x0000000000400480, cpu addr 0xffffb0cac1621480
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 9 use gpu addr 0x0000000000400520, cpu addr 0xffffb0cac1621520
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 10 use gpu addr 0x00000000004005a0, cpu addr 0xffffb0cac16215a0
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: fence driver on ring 11 use gpu addr 0x0000000000400620, cpu addr 0xffffb0cac1621620
Apr 25 18:21:44 archlinux kernel: amdgpu: [powerplay] can’t get the mac of 5
Apr 25 18:21:44 archlinux kernel: amdgpu 0000:01:00.0: kfd not supported on this ASIC
Apr 25 18:21:44 archlinux kernel: [drm] Initialized amdgpu 3.19.0 20150101 for 0000:01:00.0 on minor 1

This can’t get the mac of 5, kfd not supported issue is the reason I am not able to use this thing. The VGA driver still shows intel instead of both intel and amdgpu

Источник

AMDGPU

AMDGPU is the open source graphics driver for AMD Radeon graphics cards from the Graphics Core Next family.

Contents

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. At the moment there is Xorg radeon driver support for Southern Islands (SI) through Arctic Islands (AI) cards. AMD has no plans to support pre-GCN GPUs. Owners of unsupported GPUs may use the open source radeon driver.

Installation

Install the mesa package, which provides the DRI driver for 3D acceleration.

• For 32-bit application support, also install the lib32-mesa package from the multilib repostory.
• For the DDX driver (which provides 2D acceleration in Xorg), install the xf86-video-amdgpu package.
• For Vulkan support, install the vulkan-radeon or amdvlk package. Optionally install the lib32-vulkan-radeon or lib32-amdvlk package for 32-bit application support.

Experimental

It may be worthwhile for some users to use the upstream experimental build of mesa, to enable features such as AMD Navi improvements that have not landed in the standard mesa packages.

Install the mesa-git AUR package, which provides the DRI driver for 3D acceleration.

• For 32-bit application support, also install the lib32-mesa-gitAUR package from the mesa-git repository or the AUR.
• For the DDX driver (which provides 2D acceleration in Xorg), install the xf86-video-amdgpu-gitAUR package.
• For Vulkan support using the mesa-git repository below, install the vulkan-radeon-git package. Optionally install the lib32-vulkan-radeon-git package for 32-bit application support. This should not be required if building mesa-gitAUR from the AUR.

Enable Southern Islands (SI) and Sea Islands (CIK) support

The linux package enables AMDGPU support for cards of the Southern Islands (SI, ie. GCN 1) and Sea Islands (CIK, ie. GCN 2). When building or compiling a kernel, CONFIG_DRM_AMDGPU_SI=Y and/or CONFIG_DRM_AMDGPU_CIK=Y should be be set in the config.

Specify the correct module order

Even when AMDGPU support for SI/CIK has been enabled by the kernel, the radeon driver may be loaded before the amdgpu driver.

Make sure amdgpu has been set as first module in the Mkinitcpio#MODULES array, e.g. MODULES=(amdgpu radeon) .

Set required module parameters

The module parameters of both amdgpu and radeon modules are cik_support= and si_support= .

They need to be set as kernel parameters or in a modprobe configuration file, and depend on the cards GCN version.

Set module parameters in kernel command line

Set one of the following kernel parameters:

• Southern Islands (SI): radeon.si_support=0 amdgpu.si_support=1
• Sea Islands (CIK): radeon.cik_support=0 amdgpu.cik_support=1

Set module parameters in modprobe.d

Create the configuration modprobe files in /etc/modprobe.d/ , see modprobe.d(5) for syntax details.

For Southern Islands (SI) use option si_support=1 , for Sea Islands (CIK) use option cik_support=1 , e.g.:

Make sure modconf is in the the HOOKS array in /etc/mkinitcpio.conf and regenerate the initramfs.

AMDGPU PRO

AMD provides a proprietary, binary userland driver called AMDGPU PRO, 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.

Install the amdgpu-pro-libgl AUR . Optionally install the lib32-amdgpu-pro-libgl AUR package for 32-bit application support.

ACO compiler

The ACO compiler is an open source shader compiler created and developed by Valve Corporation to directly compete with the LLVM compiler, the AMDVLK drivers, as well as Windows 10. It offers lesser compilation time and also performs better while gaming than LLVM and AMDVLK.

Some benchmarks can be seen in It’s FOSS and Phoronix (1) (2) (3).

Since mesa version 20.2, the ACO compiler is enabled by default.

Loading

The amdgpu kernel module is supposed to load automatically on system boot.

• Make sure to #Enable Southern Islands (SI) and Sea Islands (CIK) support when needed.
• Make sure you have the latest linux-firmware package installed. This driver requires the latest firmware for each model to successfully boot.
• Make sure you do not have nomodeset or vga= as a kernel parameter, since amdgpu requires KMS.
• Check that you have not disabled amdgpu by using any kernel module blacklisting.

It is possible it loads, but late, after the X server requires it. In this case:

Xorg configuration

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:

Using this section, you can enable features and tweak the driver settings, see amdgpu(4) first before setting driver options.

Tear free rendering

TearFree controls tearing prevention using the hardware page flipping mechanism. If this option is set, the default value of the property is ‘on’ or ‘off’ accordingly. If this option is not 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 slave outputs, otherwise off:

You can also enable TearFree temporarily with xrandr:

Where output should look like DisplayPort-0 or HDMI-A-0 and can be acquired by running xrandr -q .

DRI level

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:

Variable refresh rate

10-bit color

Newer AMD cards support 10bpc color, but the default is 24-bit color and 30-bit color must be explicitly enabled. Enabling it can reduce visible banding/artifacts in gradients, if the applications support this too. To check if your monitor supports it search for «EDID» in your Xorg log file (e.g. /var/log/Xorg.0.log or

To check whether it is currently enabled search for «Depth»):

With the default configuration it will instead say the depth is 24, with 24 bits stored in 4 bytes.

To check whether 10-bit works, exit Xorg if you have it running and run Xorg -retro which will display a black and white grid, then press Ctrl-Alt-F1 and Ctrl-C to exit X, and run Xorg -depth 30 -retro . If this works fine, then 10-bit is working.

To launch in 10-bit via startx , use startx — -depth 30 . To permanently enable it, create or add to:

Various software may have graphical artifacts or crash with 10-bpc color.

Reduce output latency

If you want to minimize latency you can disable page flipping and tear free:

See Gaming#Reducing DRI latency to further reduce latency.

Features

Video acceleration

Monitoring

Monitoring your GPU is often used to check the temperature and also the P-states of your GPU.

CLI (default)

To check your GPU’s P-states, execute:

To monitor your GPU, execute:

To check your GPU utilization, execute:

To check your GPU frequency, execute:

To check your GPU temperature, execute:

To check your VRAM frequency, execute:

To check your VRAM usage, execute:

To check your VRAM size, execute:

With radeontop utility you can view your GPU utilization, both for the total activity percent and individual blocks. Install it with radeontop package. If it does not recognize your GPU, try radeontop-git AUR .

• WattmanGTK — A GTK GUI tool to monitor your GPU’s temperatures P-states

https://github.com/BoukeHaarsma23/WattmanGTK || wattman-gtk-gitAUR .

• TuxClocker — A Qt5 monitoring and overclocking tool.

https://github.com/Lurkki14/tuxclocker || tuxclockerAUR

Overclocking

Since Linux 4.17, it is possible to adjust clocks and voltages of the graphics card via /sys/class/drm/card0/device/pp_od_clk_voltage .

Boot parameter

It is required to unlock access to adjust clocks and voltages in sysfs by appending the Kernel parameter amdgpu.ppfeaturemask=0xffffffff .

Manual (default)

To set the GPU clock for the maximum P-state 7 on e.g. a Polaris GPU to 1209MHz and 900mV voltage, run:

The same procedure can be applied to the VRAM, e.g. maximum P-state 2 on Polaris 5xx series cards:

To check if it worked out, read out clocks and voltage under 3D load:

You can reset to the default values using this:

It is also possible to forbid the driver so switch to certain P-states, e.g. to workaround problems with deep powersaving P-states like flickering artifacts or stutter. To force the highest VRAM P-state on a Polaris RX 5xx card, while still allowing the GPU itself to run with lower clocks, run:

Allow only the three highest GPU P-states:

To set the allowed maximum power consumption of the GPU to e.g. 50 Watts, run

Until Linux kernel 4.20, it will only be possible to decrease the value, not increase.

Assisted

If you are not inclined to fully manually overclock your GPU, there are some overclocking tools that are offered by the community to assist you to overclock and monitor your AMD GPU.

CLI tools

• amdgpu-clocks — A script that can be used to monitor and set custom power states for AMD GPUs. It also offers a Systemd service to apply the settings automatically upon boot.

https://github.com/sibradzic/amdgpu-clocks || amdgpu-clocks-gitAUR

GUI tools

• TuxClocker — A Qt5 monitoring and overclocking tool.

https://github.com/Lurkki14/tuxclocker || tuxclockerAUR

• CoreCtrl — A GUI overclocking tool with a WattMan-like UI that supports per-application profiles.

https://gitlab.com/corectrl/corectrl || corectrlAUR

Startup on boot

If you want your settings to apply automatically upon boot, consider looking at this Reddit thread to configure and apply your settings on boot.

Power profiles

AMDGPU offers several optimizations via power profiles, one of the most commonly used is the compute mode for OpenCL intensive applications. Available power profiles can be listed with:

To use a specific power profile you should first enable manual control over them with:

Then to select a power profile by writing the NUM field associated with it, e.g. to enable COMPUTE run:

Enable GPU display scaling

This article or section is a candidate for moving to xrandr.

To avoid the usage of the scaler which is built in the display, and use the GPU own scaler instead, when not using the native resolution of the monitor, execute:

Possible values for «scaling mode» are: None , Full , Center , Full aspect .

• To show the available outputs and settings, execute:

• To set scaling mode = Full aspect for just every available output, execute:

Troubleshooting

Xorg or applications will not 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 will not 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:

Screen artifacts and frequency problem

Dynamic power management may cause screen artifacts to appear when displaying to monitors at higher frequencies (anything above 60Hz) due to issues in the way GPU clock speeds are managed[1][2].

A workaround [3] is saving high or low in /sys/class/drm/card0/device/power_dpm_force_performance_level .

To make it persistent, you may create a udev rule:

To determine the KERNEL name execute:

There is also a GUI solution [4] where you can manage the «power_dpm» with radeon-profile-git AUR and radeon-profile-daemon-git AUR .

Artifacts in Chromium

If you see artifacts in Chromium, try to force the vulkan based backend. Go to chrome://flags and enable #ignore-gpu-blacklist and #enable-vulkan .

R9 390 series poor performance and/or instability

If you experience issues [5] with a AMD R9 390 series graphics card, set radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dc=1 as kernel parameters to force the use of amdgpu driver instead of radeon.

If it still does not work, try disabling DPM, by setting the kernel parameters to: radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1

Freezes with «[drm] IP block:gmc_v8_0 is hung!» kernel error

If you experience freezes and kernel crashes during a GPU intensive task with the kernel error » [drm] IP block:gmc_v8_0 is hung!» [6], a workaround is to set amdgpu.vm_update_mode=3 as kernel parameters to force the GPUVM page tables update to be done using the CPU. Downsides are listed here [7].

Cursor corruption

If you experience issues with the mouse cursor sometimes not rendering properly, set Option «SWCursor» «True» in the «Device» section of the /etc/X11/xorg.conf.d/20-amdgpu.conf configuration file.

If you are using xrandr for scaling and the cursor is flickering or disappearing, you may be able to fix it by setting the TearFree property: xrandr —output HDMI-A-0 —set TearFree on .

System freeze or crash when gaming on Vega cards

Dynamic power management may cause a complete system freeze whilst gaming due to issues in the way GPU clock speeds are managed. [8] A workaround is to disable dynamic power management, see ATI#Dynamic power management for details.

Navi power consumption

Some users have reported higher than usual idle power consumption when using kernel 5.3. There is a patch set available for kernel 5.4 that appears to fix the issues.

WebRenderer (Firefox) corruption

Artifacts and other anomalies may present themselves (e.g. inability to select extension options) when WebRenderer is force enabled by the user. Workaround is to fall back to OpenGL compositing.

Double-speed or «chipmunk» audio, or no audio when a 4K@60Hz device is connected

This is sometimes caused by a communication issue between an AMDGPU device and a 4K display connected over HDMI. A possible workaround is to enable HDR or «Ultra HD Deep Color» via the display’s built-in settings. On many Android based TVs, this means setting this to «Standard» instead of «Optimal».

Источник