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.0+, 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.
Prerequisites
Hardware detection
To choose the right driver, first detect the graphics card. Use lspci for this task:
root #
lspci | grep -i VGA
Check the output for one of the product names listed in the table below.
Feature support
Family | Chipset name | ArchitectureA | Product name | OpenGL | OpenGL ES | VIDEO_CARDS |
---|---|---|---|---|---|---|
Southern Islands3 | CAPE VERDE, PITCAIRN, TAHITI, OLAND, HAINAN | GCN1.1+ | HD7750-HD7970, R9 270, R9 280, R9 370X, R7 240, R7 250 | 4.5 | 3.2 | amdgpu radeonsi |
Sea Islands1 | BONAIRE, KABINI, KAVERI, HAWAII, MULLINS | GCN2.x | HD7790, R7 260, R9 290, R7 360, R9 390 | 4.5 | 3.2 | amdgpu radeonsi |
Volcanic Islands | CARRIZO, FIJI, STONEY, TONGA, TOPAZ, WANI | GCN3.x | R9 285, R9 380, R9 380X, R9 Fury, R9 Nano, R9 Fury X, Pro Duo | 4.5 | 3.2 | amdgpu radeonsi |
Arctic Islands2 | POLARIS10/11/12 | GCN4.x | RX 460, RX 470, RX 480, RX 540, RX 550, RX 560, RX 570, RX 580, RX 590 | 4.5 | 3.2 | amdgpu radeonsi |
Vega4 | VEGA10/11/12/20, RAVEN5, Renoir7 | GCN5.x, DCN1.05, DCN2.17 | RX Vega 56, RX Vega 64, Raven Ridge APU series5, Radeon Vega II, Radeon VII, Renoir APU series7 | 4.5 | 3.2 | amdgpu radeonsi |
Navi6 | NAVI10/14/21 | RDNA | RX 5500, RX 5500 XT, RX 5600, RX 5600 XT, RX 5700, RX 5700 XT, RX 6800, RX 6800 XT, RX 6900 XT8 | 4.5 | 3.2 | amdgpu radeonsi |
- 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 since kernel 4.16[1][2]
- 6 atleast kernel 5.3, Mesa 19.2 LLVM 9.0 [3]
- 7 AMD Zen 2 "4000" series 7nm laptop APUs[4][5]
- 8 RX 6*00 series since kernel 5.9.12 with CONFIG_DRM_AMD_DC_DCN3_0=Y [6][7]
Firmware
It is necessary to install the proper firmware (or microcode) for your card. Firmware files are provided by sys-kernel/linux-firmware. Make sure you have all necessary files for your hardware in your configuration file if you use the savedconfig USE flag.
USE flags for sys-kernel/linux-firmware Linux firmware files
initramfs
|
Create and install initramfs for early microcode loading in /boot (only AMD for now) |
redistributable
|
Install also non-free (but redistributable) firmware files |
savedconfig
|
Allows individual selection of firmware files |
unknown-license
|
Install firmware files whose license is unknown |
root #
emerge --ask sys-kernel/linux-firmware
The firmware files installed this way will be incorporated into the kernel.
Navi10 cards (RX 5700, RX 5700XT [FE]) requires at least version 20190923 of sys-kernel/linux-firmware.
Kernel
For ease of installation, it is recommended to choose "AMD GPU" as a module (M) and skip the firmware selection below. This will load the driver a little later once udev becomes active. The firmware will never need to be manually managed in this case.
Set the following kernel options for the graphic chipsets mentioned above:
Processor type and features ---> [*] MTRR (Memory Type Range Register) support (''CONFIG_MTRR'') Device Drivers ---> Graphics support ---> <*/M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> (''DRM_FBDEV_EMULATION'') [*] Enable legacy fbdev support for your modesetting driver < > ATI Radeon <M/*> AMD GPU [ /*] Enable amdgpu support for SI parts (''DRM_AMDGPU_SI'') (only needed for Southern Islands GPUs with the amdgpu driver) [ /*] Enable amdgpu support for CIK parts (''DRM_AMDGPU_CIK'') (only needed for Sea Islands GPUs with the amdgpu driver) ACP (Audio CoProcessor) Configuration ---> [*] Enable AMD Audio CoProcessor IP support (''CONFIG_DRM_AMD_ACP'') (only needed for APUs) Display Engine Configuration ---> [*] AMD DC - Enable new display engine (''DRM_AMD_DC'') [ /*] DC support for Polaris and older ASICs (only needed for Polaris, Carrizo, Tonga, Bonaire, Hawaii) [ /*] AMD FBC - Enable Frame Buffer Compression [ /*] DCN 1.0 Raven family (only needed for Vega RX as part of Raven Ridge APUs) [ /*] DCN 3.0 family (only needed for NAVI21/Sienna Cichlid GPUs with the amdgpu driver) <*/M> HSA kernel driver for AMD GPU devices (''HSA_AMD'') <*/M> Sound card support ---> <*/M> Advanced Linux Sound Architecture ---> [*] PCI sound devices ---> (''CONFIG_SND_PCI'') HD-Audio ---> <*> HD Audio PCI (''CONFIG_SND_HDA_INTEL'') [*] Support initialization patch loading for HD-audio (''CONFIG_SND_HDA_PATCH_LOADER'') <*> whatever audio codec your soundcard needs <*> Build HDMI/DisplayPort HD-audio codec support (''CONFIG_SND_HDA_CODEC_HDMI'') (2048) Pre-allocated buffer size for HD-audio driver (''CONFIG_SND_HDA_PREALLOC_SIZE'')
When using AMDGPU, it is recommended to unset the ATI Radeon option so that the radeon module is not built. Or alternatively, the module can be built and blacklisted (after rebooting check with lsmod | grep radeon to see if the blacklisting worked). The amdgpu and radeon modules are not meant to be loaded simultaneously, unless, for example multiseat, system requires it.
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 was first implemented for VEGA10 (GCN5.0) and RAVEN (with DCN 1.0) GPUs/APUs. Kernels before version 4.17 have (experimental) DC support for older cards (GCN1.1 and newer) via command line option amdgpu.dc=1, which may work better than the older radeon kernel module. Likewise, if DC needs to be disabled for any particular reason, option amdgpu.dc=0 can be used on the kernel command line.
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 /lib/firmware/amdgpu (for Volcanic Islands and Arctic Islands cards) and/or /lib/firmware/radeon (for Southern Islands and Sea Islands cards). Configure the kernel to use the correct firmware files by setting the following options:
Device Drivers ---> Generic Driver Options ---> -*- Userspace firmware loading support [*] Include in-kernel firmware blobs in kernel binary (amdgpu/<YOUR-MODEL>.bin or radeon/<YOUR-MODEL>.bin) (''CONFIG_EXTRA_FIRMWARE'') (/lib/firmware) Firmware blobs root directory
Device Drivers ---> Generic Driver Options ---> Firmware loader ---> -*- Firmware loading facility (amdgpu/<YOUR-MODEL>.bin or radeon/<YOUR-MODEL>.bin) Build named firmware blobs into the kernel binary (/lib/firmware) Firmware blobs root directory
amdgpu/<YOUR-MODEL>.bin
or radeon/<YOUR-MODEL>.bin
should be replaced with the full list of filenames given with the chipset's name in the table below, separated by spaces. Use echo to expand the filenames. E.g. for Volcanic Islands/TONGA, run:
user $
echo amdgpu/tonga_{ce,k_smc,mc,me,mec2,mec,pfp,rlc,sdma1,sdma,smc,uvd,vce}.bin
amdgpu/tonga_ce.bin amdgpu/tonga_k_smc.bin amdgpu/tonga_mc.bin amdgpu/tonga_me.bin amdgpu/tonga_mec2.bin amdgpu/tonga_mec.bin amdgpu/tonga_pfp.bin amdgpu/tonga_rlc.bin amdgpu/tonga_sdma1.bin amdgpu/tonga_sdma.bin amdgpu/tonga_smc.bin amdgpu/tonga_uvd.bin amdgpu/tonga_vce.bin
Then amdgpu/tonga_ce.bin amdgpu/tonga_k_smc.bin amdgpu/tonga_mc.bin amdgpu/tonga_me.bin amdgpu/tonga_mec2.bin amdgpu/tonga_mec.bin amdgpu/tonga_pfp.bin amdgpu/tonga_rlc.bin amdgpu/tonga_sdma1.bin amdgpu/tonga_sdma.bin amdgpu/tonga_smc.bin amdgpu/tonga_uvd.bin amdgpu/tonga_vce.bin
is the string that should be put into the kernel configuration.
If the amdgpu module is compiled as a loadable kernel module (i.e. AMDGPU in the kernel configuration is set to
M
), the firmware files need to be present on the filesystem at the time the module is loaded. In particular, if the module is loaded from an initrd, the firmware also needs to be included in the initrd. On the other hand, if the module is built into the kernel, the firmware files will also be built into the kernel itself.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.
More recent kernels (Aug. 2018, at least 4.15.x and up, and Dec. 2018, 4.19.9[8] and up) require an updated set of firmware files than listed here in order to boot successfully . Make sure that sys-kernel/linux-firmware is updated. If you use the savedconfig USE flag for this package, make sure that the savedconfig configuration file is updated with the new firmware files listed. Incorporate all the newly added files to your kernel configuration file in the firmware line then rebuild and install your new kernel image. Otherwise your boot will likely fail with a blank screen and firmware load errors thrown to the kernel log.
Family | Chipset name | Product name | Firmware |
---|---|---|---|
Southern Islands | CAPE VERDE | HD7750, HD7770, R7 250, R7 250X, R9 370X | radeon/{verde_{ce,mc,me,pfp,rlc,smc},TAHITI_{uvd,vce}}.bin |
PITCAIRN | HD7800, R9 270X | radeon/{pitcairn_{ce,mc,me,pfp,rlc,smc,k_smc},TAHITI_{uvd,vce}}.bin | |
TAHITI | HD7870 XT, HD7900, R9 280X | radeon/{tahiti_{ce,mc,me,pfp,rlc,smc},TAHITI_{uvd,vce}}.bin | |
OLAND | HD8550M-HD8790M, R7 240 | radeon/{oland_{ce,mc,me,pfp,rlc,smc},TAHITI_{uvd,vce}}.bin | |
HAINAN | HD8970M | radeon/{hainan_{ce,mc,me,pfp,rlc,smc},TAHITI_uvd}.bin | |
Sea Islands | BONAIRE | HD7790, R7 260, R7 260X, R7 360 | radeon/bonaire_{ce,k_smc,mc,me,mec,pfp,rlc,sdma1,sdma,smc,uvd,vce}.bin |
KABINI | HD8180-HD8400 | radeon/kabini_{ce,me,mec,pfp,rlc,sdma1,sdma,uvd,vce}.bin | |
KAVERI | radeon/kaveri_{ce,me,mec2,mec,pfp,rlc,sdma1,sdma,uvd,vce}.bin | ||
HAWAII | R9 290, R9 290X, R9 390, R9 390X | amdgpu/hawaii_{ce,k_smc,mc,me,mec,pfp,rlc,sdma,sdma1,smc,uvd,vce}.bin | |
MULLINS | radeon/mullins_{ce,me,mec,pfp,rlc,sdma1,sdma,uvd,vce}.bin | ||
Volcanic Islands | CARRIZO | amdgpu/carrizo_{ce,me,mec2,mec,pfp,rlc,sdma1,sdma,uvd,vce}.bin | |
FIJI | R9 Fury, R9 Fury X, R9 Nano, Pro Duo | amdgpu/fiji_{ce,mc,me,mec2,mec,pfp,rlc,sdma1,sdma,smc,uvd,vce}.bin | |
TONGA | R9 285, R9 380, R9 380X | amdgpu/tonga_{ce,k_smc,mc,me,mec2,mec,pfp,rlc,sdma1,sdma,smc,uvd,vce}.bin | |
TOPAZ | R7 M260, R7 M265, R7 M340, R7 M360, R7 M360, R7 M370, R7 M440, R7 M445, R7 M460, R7 M465 | amdgpu/topaz_{ce,mc,me,mec2,mec,pfp,rlc,sdma1,sdma,smc}.bin | |
STONEY | amdgpu/stoney_{ce,me,mec,pfp,rlc,sdma,uvd,vce}.bin | ||
Arctic Islands | POLARIS10 | RX 470, RX 480, RX 570, RX 580, RX 590 | amdgpu/polaris10_{ce,ce_2,k_smc,k2_smc,k_mc,mc,me,me_2,mec2,mec2_2,mec,mec_2,pfp,pfp_2,rlc,sdma1,sdma,smc,smc_sk,uvd,vce}.bin |
POLARIS11 | RX 460, RX 550 640SP, RX 560 | amdgpu/polaris11_{ce,k_smc,k2_smc,k_mc,mc,me,mec2,mec,pfp,rlc,sdma1,sdma,smc,smc_sk,uvd,vce}.bin | |
POLARIS12 | RX 540, RX 550 | amdgpu/polaris12_{ce,ce_2,k_mc,k_smc,mc,me,me_2,mec,mec2,mec2_2,mec_2,pfp,pfp_2,rlc,sdma,sdma1,smc,uvd,vce}.bin | |
Vega | VEGA10 | RX Vega 56, RX Vega 64 | amdgpu/vega10_{acg_smc,asd,ce,gpu_info,me,mec,mec2,pfp,rlc,sdma,sdma1,smc,sos,uvd,vce}.bin |
RAVEN | Raven Ridge APU series | amdgpu/raven_{asd,ce,gpu_info,me,mec,mec2,pfp,rlc,sdma,vcn}.bin | |
VEGA12 | Raven 2 Vega Mobile | amdgpu/vega12_{asd,ce,gpu_info,me,mec,mec2,pfp,rlc,sdma,sdma1,smc,sos,uvd,vce}.bin | |
RENOIR | Renoir APU series | amdgpu/renoir_{asd,ce,dmcub,gpu_info,me,mec2,mec,pfp,rlc,sdma,vcn}.bin | |
Navi | NAVI10 | RX 5700, RX 5700 XT | amdgpu/navi10_{asd,ce,gpu_info,me,mec2,mec,pfp,rlc,sdma1,sdma,smc,sos,ta,vcn}.bin |
NAVI14 | RX 5500 XT | amdgpu/navi14_{asd,ce,ce_wks,gpu_info,me,mec2,mec2_wks,mec,mec_wks,me_wks,pfp,pfp_wks,rlc,sdma1,sdma,smc,sos,ta,vcn}.bin | |
NAVI21 | RX 6800, RX 6800 XT, RX 6900 XT | amdgpu/sienna_cichlid_{ce,dmcub,me,mec2,mec,pfp,rlc,sdma,smc,sos,ta,vcn}.bin |
X11 driver
USE flags
Set the USE flags for the amdgpu
driver as needed.
USE flags for x11-drivers/xf86-video-amdgpu Accelerated Open Source driver for AMDGPU cards
udev
|
Enable virtual/udev integration (device discovery, power and storage device support, etc) |
The package will be automatically emerged as a dependency of x11-base/xorg-drivers 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 amdgpu radeonsi
(see the feature matrix section above) and asking Portage to update changed USE flags in the @world set will pull in the correct driver:
/etc/portage/make.conf
<syntaxhighlight lang="bash">VIDEO_CARDS="amdgpu radeonsi"</syntaxhighlight>
root #
emerge --ask --changed-use @world
The system should now be prepared to use amdgpu after the next reboot.
Power management
This section only covers dpm method. This method is only available for GPUs from R6xx -series onwards. Users of AMDGPU driver are thus automatically covered. Older dynpm and profile methods aren't covered here. Users who want to read about those should read radeon article instead.
This section assumes that card0 is the GPU users want to adjust. Users should check that paths like /sys/class/drm/card0/ belong to the right GPU. Users with more than one GPU will most likely have more than just card0 entry under said locations.
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 radeon.dpm=1
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:
root #
echo performance > /sys/class/drm/card0/device/power_dpm_state
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:
root #
echo high > /sys/class/drm/card0/device/power_dpm_force_performance_level
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:
root #
echo auto > /sys/class/drm/card0/device/power_dpm_force_performance_level
There's also the low forceable performance level, which can be echoed the same way. A list of all available modes can be found on dri.freedesktop.org
Troubleshooting
Debug tools
It might be helpful to install the package x11-apps/mesa-progs, which provides the packages glxgears
and glxinfo
.
Test, if a discrete graphics card is in use
First make sure that the kernel was compiled with the following settings:
Device Drivers ---> Graphics support ---> -*- VGA Arbitration (CONFIG_VGA_ARB) [*] Laptop Hybrid Graphics - GPU switching support (CONFIG_VGA_SWITCHEROO)
Check, if the discrete graphics card was recognized:
user $
lspci -k
[...] 01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] Kernel driver in use: radeon [...]
After that. Make sure that the path /sys/kernel/debug/ was mounted successfully:
root #
findmnt debugfs
TARGET SOURCE FSTYPE OPTIONS /sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime
Then, check, if the driver vga_switcheroo was loaded successfully and can output values:
root #
< /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynOff:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0
This output has the following structure[9]:
Iterator | ID | Active state | Power state | Device ID (xxxx:xx:xx.x) |
---|---|---|---|---|
0 | DIS | inactive | DynOff | 0000:01:00.0 |
1 | IGD | active | Pwr | 0000:00:02.0 |
DIS
represents the discrete graphics card, which is inactive, but currently disconnected (DynOff
).
IGD
is the integrated graphics card, which is active (+
) and is currently in use (Pwr
).
The status can be manipulated using the following command:
root #
echo "<some_parameter>" > /sys/kernel/debug/vgaswitcheroo/switch
Replace <some_parameter>
with one of the following paramters[10]:
Parameter | Description |
---|---|
ON | Turns on the disconnected GPU, which is currently not displaying anything and does not switch outputs. |
IGD | Connects the integrated graphics card with the display. |
DIS | Connects the discrete graphics card with the display. |
OFF | Turns off the graphics card, which is currently disconnected. |
DIGD | Inside of an X session: Queues a switch to the integrated graphics card to occur, when the X server is next restarted. |
DDIS | Inside of an X session: Queues a switch to the discrete graphics card to occur, when the X server is next restarted. |
By using the environment variable DRI_PRIME=1
, one can use the discrete graphics card individually:
user $
DRI_PRIME=1 glxgears
This opens an X window with rotating gears.
Let it run in the background and check, vga_switcheroo
again:
root #
< /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynPwr:0000:01:00.0 1:IGD:+:Pwr:0000:00:02.0
This time the status of the discrete graphics card switched to DynPwr, which means, that it is active and running.
Another indicator is to check the temperature sensors. This requires sys-apps/lm-sensors:
user $
sensors
[...] radeon-pci-0100 Adapter: PCI adapter temp1: +42.0°C (crit = +120.0°C, hyst = +90.0°C)
[...]
When
vga_switcheroo
displays the status DynOff
, sensors
will display the temperature as N/A
or as something else, which may not make sense; for example: -128°C.To use the discrete graphics card globally, one can set the environment variable in /etc/environment:
/etc/environment
DRI_PRIME=1
One might export it in the .bashrc
as an alternative:
/home/larry/.bashrc
export DRI_PRIME=1
Or individually in front of the command, like above using glxgears
:
user $
DRI_PRIME=1 /usr/bin/chromium
user $
DRI_PRIME=1 /usr/bin/vlc
Prime Synchronization
The x11-drivers/xf86-video-amdgpu driver does not support Prime Synchornization. This might cause tearing on monitors connected to the integrated GPU if the AMD GPU is set as the primary GPU. One possible workaround is to use the modesetting driver instead, to do this remove amdgpu
from the VIDEO_CARDS variable. Or use a xorg configuration file to force the use of the modesetting driver. That being said, you might encounter other issues with the modesetting driver[11].
/etc/X11/xorg.conf.d/force-modesetting.conf
Section "Device" Identifier "modesetting" Driver "modesetting" EndSection
Another possible workaround is to set the integrated GPU as the primary GPU. This will not enable Prime Synchronization. However, tearing will be prevented nonetheless through AMD's TearFree. In this case it will be neccesairy to use the DRI_PRIME=1
, VDPAU_DRIVER=radeonsi
(for VDPAU) and LIBVA_DRIVER_NAME=radeonsi
(for VAAPI) variables on applications that should be rendered on the AMD GPU.
VESA
If you have no other machine to browse web pages for solution - emerge x11-drivers/xf86-video-vesa This will allow you to use basic vesa driver so you can start X with no 3d and no 2d acceleration. Your usual kde/gnome/xfce or whatever else should start with vesa driver, so you can bootstrap yourself from within GUI.
Kernel
Older kernels
Older kernels which do not support the amdgpu driver will not provide the AMDGPU option. For VEGA and newer chips there is no video output without DC (Display Code), which was first included in vanilla Kernel 4.15. In both cases a fairly recent kernel can provide the required drivers. For very new AMD graphics cards and APUs trying an unstable (denoted by a ~) kernel may provide the required kernel-sources.
AMD Secure Memory Encryption
If amdgpu fails to load or the screen stays frozen, it might be an incompatibility of the amdgpu module with AMD Secure Memory Encryption (SME).
SME can be temporarily disabled on the kernel command line (using GRUB, or in /etc/default/grub or as part of GRUB_CMDLINE_LINUX) by adding mem_encrypt=off. If this fixes the issue, a permanent solution is to configure the kernel accordingly.
Processor type and features ---> [*] AMD Secure Memory Encryption (SME) support [ ] Activate AMD Secure Memory Encryption (SME) by default
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. Likewise, with mem_encrypt=on SME can be activated for unaffected systems on the kernel command line or more permanently using GRUB_CMDLINE_LINUX in /etc/default/grub for GRUB.
AMDGPU/RadeonSI drivers do not work
If the graphics card is not supported by including amdgpu
and radeonsi
alone in VIDEO_CARDS, try adding radeon
to make.conf's VIDEO_CARDS definition. For example:
/etc/portage/make.conf
<syntaxhighlight lang="bash">VIDEO_CARDS="amdgpu radeonsi radeon"</syntaxhighlight>
After the values have been set update the system so the changes take effect:
root #
emerge --ask --changed-use --deep @world
Full-screen windows perform poorly
The installed version of sys-devel/llvm 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:
user $
xrandr --output HDMI-A-0 --auto --set audio off
where HDMI-A-0
should be replaced by the name of the output, obtained by running xrandr
For more information please see https://bugs.freedesktop.org/show_bug.cgi?id=97861.
See also
- AMDGPU-PRO — the next generation closed source graphics component that operates on top of the open source AMDGPU drivers for newer AMD/ATI Radeon graphics cards.
External resources
References
- ↑ Phoronix - Report: Ryzen "Raven Ridge" APU Not Using HBM2 Memory
- ↑ Phoronix - 25 More AMDGPU DC Patches, Mostly Focused On Raven DCN
- ↑ Phoronix - AMD Navi 10 Firmware Finally Lands In The Linux-Firmware Tree
- ↑ WikiChip - Renoir - Cores - AMD - WikiChip
- ↑ Phoronix - AMD Renoir APUs Bringing "DCN 2.1" Display Engine
- ↑ https://www.phoronix.com/scan.php?page=news_item&px=Radeon-RX-6900-XT
- ↑ https://cateee.net/lkddb/web-lkddb/DRM_AMD_DC_DCN3_0.html
- ↑ Linux kernel commit 39bdb32 with added firmware files to POLARIS10 and POLARIS11
- ↑ https://github.com/torvalds/linux/blob/be8454afc50f43016ca8b6130d9673bdd0bd56ec/drivers/gpu/vga/vga_switcheroo.c#L653-L660
- ↑ https://help.ubuntu.com/community/HybridGraphics
- ↑ https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/11