Difference between revisions of "ATI"

From ArchWiki
Jump to: navigation, search
(rm temporary i18n template)
m (Reverted edits by Lahwaacz.bot (talk) to last revision by Alad)
 
(353 intermediate revisions by 81 users not shown)
Line 1: Line 1:
 
[[Category:Graphics]]
 
[[Category:Graphics]]
[[Category:X Server]]
+
[[Category:X server]]
[[cs:ATI]]
+
[[de:ATI]]
 
[[es:ATI]]
 
[[es:ATI]]
 
[[fr:ATI]]
 
[[fr:ATI]]
 
[[it:ATI]]
 
[[it:ATI]]
 +
[[ja:ATI]]
 
[[pl:ATI]]
 
[[pl:ATI]]
 
[[ru:ATI]]
 
[[ru:ATI]]
 
[[tr:ATI]]
 
[[tr:ATI]]
 
[[zh-CN:ATI]]
 
[[zh-CN:ATI]]
{{Article summary start}}
+
{{Related articles start}}
{{Article summary text|An overview of the open source ATI/AMD video card driver.}}
+
{{Related|AMD Catalyst}}
{{Article summary heading|Related}}
+
{{Related|AMDGPU}}
{{Article summary wiki|ATI Catalyst}}
+
{{Related|Xorg}}
{{Article summary wiki|KMS}}
+
{{Related articles end}}
{{Article summary wiki|Xorg}}
+
{{Article summary end}}
+
  
Owners of '''ATI/AMD''' video cards have a choice between ATI's [[ATI Catalyst|proprietary driver]] ({{AUR|catalyst}}) and the open source driver ({{Pkg|xf86-video-ati}}). This article covers the open source driver.
+
Owners of '''AMD''' (previously '''ATI''') video cards have a choice between [[AMD Catalyst|proprietary driver]] ({{AUR|catalyst}}) and the open source drivers ([[ATI]] for older or [[AMDGPU]] for newer cards). This article covers the '''ATI'''/[https://wiki.freedesktop.org/xorg/radeon/ Radeon] open source driver for older cards.
  
The open source driver is currently not ''on par'' with the proprietary driver in terms of 3D performance on newer cards or reliable TV-out support. It does, however, offer better dual-head support, excellent 2D acceleration, and provide sufficient 3D acceleration for OpenGL-accelerated [[window manager]]s, such as [[Compiz]] or KWin.
+
The open source driver is ''on par'' performance-wise with the proprietary driver for many cards. (See this [http://www.phoronix.com/scan.php?page=article&item=radeonsi-cat-wow&num=1 benchmark].) It also has good dual-head support but worse TV-out support. Newer cards support might be lagging behind Catalyst.
  
If unsure, try the open source driver first, it will suit most needs and is generally less problematic (see the [http://www.x.org/wiki/RadeonFeature feature matrix] for details).
+
If unsure, try the open source driver first, it will suit most needs and is generally less problematic. See the [http://www.x.org/wiki/RadeonFeature feature matrix] to know what is supported for the GPU.
  
==Naming conventions==
+
== Selecting the right driver ==
ATI's [[Wikipedia:Radeon|Radeon]] brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both ''product'' names (e.g. HD 4850, X1900) and ''code'' or ''core'' names (e.g. RV770, R580). Traditionally, a ''product series'' will correspond to a ''core series'' (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series – including the RV515, RV530, R520, and R580 cores).
+
  
For a table of core and product series, see [[Wikipedia:Comparison of AMD graphics processing units]].
+
Depending on the card you have, find the right driver in [[Xorg#ATI]]. This page has instructions for '''ATI'''.
  
==Overview==
+
== Naming conventions ==
The {{ic|xf86-video-ati}} (radeon) driver:
+
*Works with Radeon chipsets up to HD 6xxx and 7xxxM (latest Northern Islands chipsets).
+
**Radeons up to the X1xxx series are fully supported, stable, and full 2D and 3D acceleration are provided.
+
**Radeons from HD 2xxx to HD 6xxx have full 2D acceleration and functional 3D acceleration, but are not supported by all the features that the proprietary driver provides (for example, powersaving is still in a testing phase).
+
*Supports DRI1, RandR 1.2/1.3, EXA acceleration and [[KMS|kernel mode-setting]]/DRI2 (with the latest Linux kernel, libdrm and Mesa versions).
+
  
Generally, '''xf86-video-ati''' should be your first choice, no matter which ATI card you own. In case you need to use a driver for newer ATI cards, you should prefer the proprietary '''catalyst''' driver.
+
The [[Wikipedia:Radeon|Radeon]] brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both ''product'' names (e.g. HD 4850, X1900) and ''code'' or ''core'' names (e.g. RV770, R580). Traditionally, a ''product series'' will correspond to a ''core series'' (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series – including the RV515, RV530, R520, and R580 cores).
  
{{Note|xf86-video-ati is recognized as "'''radeon'''" by Xorg (in {{ic|xorg.conf}}). }}
+
For a table of core and product series, see [[Wikipedia:Radeon]] and [[Wikipedia:List of AMD graphics processing units]].
  
==Installation==
+
== Installation ==
=== Preparing system for catalyst users ===
+
If you have the proprietary driver (catalyst) installed, you need to get rid of it. Basically you need to remove {{ic|catalyst}} and {{ic|catalyst-utils}} packages. Also you should remove {{Aur|catalyst-daemon}}, {{Aur|catalyst-generator}}, {{Aur|catalyst-hook}} and {{Aur|lib32-catalyst-utils}} packages if they have been installed on your system.
+
  
{{Warning|You may need to use {{ic|pacman -Rdd}} to remove {{aur|catalyst-utils}} (and/or {{aur|lib32-catalyst-utils}}) because that package contains ''gl'' related files and many of your installed packages depend on them.}}
+
{{Note|If coming from the proprietary Catalyst driver, see [[AMD Catalyst#Uninstallation]] first.}}
  
{{Note|You should remove unofficial reporitories which are menitoned in [[ATI Catalyst]] wiki page from your {{ic|/etc/pacman.conf}} and run {{ic|pacman -Syu}}. Because, those repositories include out-dated Xorg packages to allow use of catalyst and {{Pkg|xf86-video-ati}} package needs up-to-date Xorg packages from [[Official repositories]]}}
+
[[Install]] the {{Pkg|xf86-video-ati}} package. It provides the DDX driver for 2D acceleration and it pulls in {{Pkg|mesa}} as a dependency, providing the DRI driver for 3D acceleration.
  
Also follow these steps:
+
To enable OpenGL support, also install {{Pkg|mesa-libgl}}. If you are on x86_64 and need 32-bit support, also install {{Pkg|lib32-mesa-libgl}} from the [[multilib]] repository.
  
* If you have a {{ic|/etc/modprobe.d/blacklist-radeon.conf}} file remove it or comment the line {{ic|blacklist radeon}} in that file.
+
Support for [[#Enabling video acceleration|accelerated video decoding]] is provided by {{Pkg|mesa-vdpau}} and {{Pkg|lib32-mesa-vdpau}} packages.
* Make sure to remove the old {{ic|/etc/X11/xorg.conf}}
+
* If you have installed {{Aur|catalyst-hook}} package, make sure to remove ''fglrx'' from "HOOKS" array of {{ic|/etc/mkinitcipo.conf}} in case if post-removal script of the package don't work.
+
* If you have installed {{Aur|catalyst-generator}} package, make sure to remove "fglrx" from "MODULES" array of {{ic|/etc/rc.conf}} in case if post-removal script of the package don't work.
+
* If you have installed {{Aur|catalyst-daemon}} package, make sure to remove "autofglrx" from "DAEMONS" array of {{ic|/etc/rc.conf}} in case if post-removal script of the package don't work.
+
* If you used "nomodeset" option in your {{ic|/boot/grub/menu.lst}} file in kernel parameters line and plan to use [[#Kernel mode-setting (KMS)|KMS]], remove it.
+
* '''Reboot''' before installing the radeon driver.
+
  
=== Installing xf86-video-ati ===
+
== Configuration ==
[[pacman|Install]] {{Pkg|xf86-video-ati}}, available in the [[Official Repositories]].
+
  
The -git version of the driver and other needed packages (linux-git, etc) can be found in the [https://bbs.archlinux.org/viewtopic.php?id=79509&p=1 radeon repository] or the [[AUR]].
 
 
==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.
 
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.
  
Line 74: Line 55:
 
Using this section, you can enable features and tweak the driver settings.
 
Using this section, you can enable features and tweak the driver settings.
  
== Kernel mode-setting (KMS) ==
+
== Loading ==
  
[[KMS]] enables native resolution in the framebuffer and allows for instant console (tty) switching. KMS also enables newer technologies (such as DRI2) which will help reduce artifacts and increase 3D performance, even kernel space power-saving.
+
The radeon kernel module should load fine automatically on system boot.
  
KMS for ATI video cards requires the [[Xorg]] free video user space driver {{Pkg|xf86-video-ati}} version 6.12.4 or later.
+
If it does not happen, then:
  
=== Enabling KMS ===
+
* Make sure you do '''not''' have {{ic|nomodeset}} or {{ic|1=vga=}} as a [[kernel parameter]], since radeon requires [[KMS]].
 +
* Also, check that you have not disabled radeon by using any [[Kernel_modules#Blacklisting|kernel module blacklisting]].
  
Since Linux kernel v.2.6.33, KMS is '''enabled''' by default for ATI cards.
+
=== Enable early KMS ===
  
==== Early KMS start ====
+
{{Tip|If you have problems with the resolution, [[Kernel mode setting#Forcing modes and EDID]] may help.}}
  
''This method will start KMS as early as possible in the [[boot process]] (when the [[initramfs]] is loaded).''
+
[[Kernel mode setting]] (KMS) is supported by the radeon driver and is mandatory and enabled by default.  
  
If you have a special kernel (e.g. linux-zen), remember to use appropriate mkinitcpio configuration file, e.g. {{ic|/etc/mkinitcpio-zen.conf}}. These instructions are written for the default kernel ({{Pkg|linux}}).
+
KMS is typically initialized after the [[Arch boot process#initramfs|initramfs stage]]. It is possible, however, to enable KMS during the initramfs stage. To do this, add the {{ic|radeon}} module to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}:
  
# Remove all {{ic|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader configuration file ({{ic|/boot/grub/menu.lst}} or {{ic|/boot/grub/grub.cfg}} for [[GRUB]] users). Using other framebuffer drivers (such as {{ic|[[uvesafb]]}} or {{ic|radeonfb}}) will conflict with KMS. Remove any framebuffer related modules from {{ic|/etc/mkinitcpio.conf}}. {{ic|<nowiki>video=</nowiki>}} can now be used in conjunction with KMS.
+
  MODULES="... radeon ..."
# Add {{ic|radeon}} to {{ic|MODULES}} array in {{ic|/etc/mkinitcpio.conf}}. For AGP support, it is necessary to add {{ic|intel_agp}} (or {{ic|ali_agp}}, {{ic|ati_agp}}, {{ic|amd_agp}}, {{ic|amd64_agp}} etc.) before the {{ic|radeon}} module.
+
# Re-generate your initramfs: {{ic|# mkinitcpio -p linux}}
+
# AGP speed can be set with {{ic|<nowiki>radeon.agpmode=x</nowiki>}} kernel option, where x is 1, 2, 4, 8 (AGP speed) or -1 (PCI mode).
+
# '''Reboot''' the system.
+
  
==== Late start ====
+
Now, regenerate the initramfs:
  
''With this choice, KMS will be enabled when modules are loaded during the [[boot process]].''
+
# mkinitcpio -p linux
  
If you have a special kernel (e.g. linux-zen), remember to use appropriate mkinitcpio configuration file, e.g. {{ic|/etc/mkinitcpio-zen.conf}}. These instructions are written for the default kernel ({{Pkg|linux}}).
+
The change takes effect at the next reboot.
  
# Remove all {{ic|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader configuration file ({{ic|/boot/grub/menu.lst}} for [[GRUB]] users).  Using other framebuffer drivers (such as {{ic|[[uvesafb]]}} or {{ic|radeonfb}}) will conflict with KMS. Remove any framebuffer related modules from {{ic|/etc/mkinitcpio.conf}}. {{ic|<nowiki>video=</nowiki>}} can now be used in conjunction with KMS.
+
== Performance tuning ==
# Add {{ic|radeon}} to {{ic|MODULES}} array in {{ic|/etc/rc.conf}}. For AGP support, it may be necessary to add {{ic|intel_agp}} (or ali_agp, {{ic|ati_agp}}, {{ic|amd_agp}}, {{ic|amd64_agp}} etc.) before the {{ic|radeon}} module.
+
=== Enabling video acceleration ===
# '''Reboot''' the system.
+
  
{{Tip|Some users have reported faster [[udev]] module loading by adding {{ic|<nowiki>options radeon modeset=1</nowiki>}} to {{ic|/etc/modprobe.d/modprobe.conf}}.}}
+
See [[Hardware video acceleration]].
  
=== Troubleshooting KMS ===
+
=== Driver options ===
 +
The following options apply to {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}.
  
==== Disable KMS ====
+
Please read {{ic|man radeon}} and [http://www.x.org/wiki/RadeonFeature/#index4h2 RadeonFeature] first before applying driver options.
  
Users should consider disabling kernel mode-setting if encountering kernel panics, distorted framebuffer on boot, no GPU signal, [[Xorg]] refusing to start, Xorg falling back to Mesa software rasterizer (no 3D acceleration) or 'POWER OFF' problem (kernel 2.6.33-2)at shutdown.
+
'''ColorTiling''' and '''ColorTiling2D''' is completely safe to enable and supposedly is enabled by default. Most users will notice increased performance but it is not yet supported on R200 and earlier cards. Can be enabled on earlier cards, but the workload is transferred to the CPU:
  
# Add {{ic|<nowiki>radeon.modeset=0</nowiki>}} (or {{ic|nomodeset}}, if this does not work) to the kernel options line in the bootloader configuration file ({{ic|/boot/grub/menu.lst}} for [[GRUB]] users). That should work. {{Note| Adding '''nomodeset''' to the kernel boot line might prevent GNOME 3's gnome-shell or KDE's desktop effects from running.}} If you want to remove KMS support from the initramfs, follow the next two steps.
+
Option "ColorTiling" "on"
# If {{ic|radeon}} was added to the {{ic|MODULES}} array in {{ic|mkinitcpio.conf}} to enable ''early start'', remove it.
+
Option "ColorTiling2D" "on"
# Rebuild the [[initramfs]] with {{bc|# mkinitcpio -p linux}}
+
  
Alternatively, module options can be specified in a file within the {{ic|/etc/modprobe.d}} directory. If using the '''radeon''' module ({{ic|<nowiki>lsmod | grep radeon</nowiki>}}) disable KMS by creating a file containing the above code:
+
'''DRI3''' support can be enabled, instead of using the default '''DRI2'''. You may want to read the following benchmark by [http://www.phoronix.com/scan.php?page=article&item=radeon-dri3-perf&num=1 Phoronix] to give you an idea of the performance of DRI2 vs DRI3:
  
{{hc|/etc/modprobe.d/radeon.conf|2=options radeon modeset=0}}
+
Option "DRI" "3"
  
==== Renaming {{ic|xorg.conf}} ====
+
'''TearFree''' is a tearing prevention using the hardware page flipping mechanism. Enabling  this
 +
option currently disables Option "EnablePageFlip":
  
Renaming {{ic|/etc/X11/xorg.conf}}, which may include options that conflict with KMS, will force Xorg to autodetect hardware with sane defaults. After renaming, '''restart''' Xorg.
+
Option "TearFree" "on"
  
== Performance tuning ==
+
'''Acceleration architecture'''; Glamor is available as 2D acceleration method implement through OpenGL, and it should work with graphic cards whose drivers are newer or equal to R300.
The following options apply to {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}.
+
Since xf86-video-ati driver-1:7.2.0-1, it is automatically enabled with radeonsi drivers (Southern Islands and superior GFX cards); on other graphic cards the method can be forced by adding AccelMethod '''glamor''' to the configuration file:
  
By design, xf86-video-ati runs at AGP 4x speed. It is generally safe to modify this. If you notice hangs, try reducing the value or removing the line entirely (you can use values 1, 2, 4, 8). If KMS is enabled, this option is not used and it is superseded by {{ic|radeon.agpmode}} kernel option.
+
Option "AccelMethod" "glamor"
  
Option "AGPMode" "8"
+
When using Glamor as acceleration architecture it is possible to enable the option '''ShadowPrimary''', enables a so-called "shadow primary" buffer for fast CPU access to pixel data, and separate scanout  buf‐fers  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 that enabling this option currently disables Option "EnablePageFlip":
  
'''ColorTiling''' is completely safe to enable and supposedly is enabled by default. Most users will notice increased performance but it is not yet supported on R200 and earlier cards. Can be enabled on earlier cards, but the workload is transferred to the CPU
+
Option "ShadowPrimary" "on"
  
  Option "ColorTiling" "on"
+
'''EXAVSync ''' is only available when using EXA and can be enabled to avoid tearing by stalling the engine until the display controller has passed the destination region. It reduces tearing at the cost of performance and has been know to cause instability on some chips:
  
'''Acceleration architecture'''; this will work only on '''newer''' cards. If you enable this and then cannot get back into X, remove it.
+
Option "EXAVSync" "yes"
  
Option "AccelMethod" "EXA"
+
Below is a sample configuration file of {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:
  
'''Page Flip''' is generally safe to enable. This would mostly be used on older cards, as enabling this would disable EXA. With recent drivers can be used together with EXA.
+
{{bc|
 +
Section "Device"
 +
Identifier  "Radeon"
 +
Driver "radeon"
 +
Option "AccelMethod" "glamor"
 +
        Option "DRI" "3"
 +
        Option "TearFree" "on"
 +
EndSection
 +
}}
  
Option "EnablePageFlip" "on"
+
{{Tip|{{Pkg|driconf}} is a tool that allows to modify several settings: vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).}}
  
'''AGPFastWrite''' will enable fast writes for AGP cards. This one can cause instabilities, so be prepared to remove it if you cannot get into X. This option is not used when KMS is on.
+
=== Kernel parameters ===
 +
{{Tip|You may want to debug the newly parameters with {{ic|systool}} as stated in [[Kernel modules#Obtaining information]].}}
 +
Useful [[kernel parameters]] may be {{ic|1=radeon.bapm=1}} [https://www.phoronix.com/scan.php?page=news_item&px=MTczMzI], {{ic|1=radeon.disp_priority=2}} [http://lists.freedesktop.org/pipermail/xorg/2013-February/055477.html], {{ic|1=radeon.hw_i2c=1}} [https://superuser.com/questions/723760/does-radeon-hw-i2c-1-has-any-thing-to-do-with-temperature-readings], {{ic|1=radeon.mst=1}} [https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.1-Radeon-DP-MST], {{ic|1=radeon.msi=1}} (force-enable MSI-support), {{ic|1=radeon.audio=0}} (force-disable GPU audio) and/or {{ic|1=radeon.tv=0}} (disable TV-out).
  
Option "AGPFastWrite" "yes"
+
Defining the '''gartsize''', if not autodetected, can be done by adding {{ic|1=radeon.gartsize=32}} into [[kernel parameters]].
  
'''EXAVSync ''' option  attempts  to avoid tearing by stalling the engine until the display controller has passed the destination region.  It reduces tearing at the cost of performance and has been know to cause instability on some chips.
+
{{Note|Setting this parameter should not be needed anymore with modern AMD videocards:
Really useful when enabling Xv overlay on videos on a 3D accelerated desktop. It is not necessary when KMS (thus DRI2 acceleration) is enabled.
+
{{bc|<nowiki>
 +
[drm] Detected VRAM RAM=2048M, BAR=256M
 +
[drm] radeon: 2048M of VRAM memory ready
 +
[drm] radeon: 2048M of GTT memory ready.
 +
</nowiki>}}
 +
}}
  
Option "EXAVSync" "yes"
+
The changes take effect at the next reboot.
  
Bellow is a sample config file {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:
+
==== Deactivating PCI-E 2.0 ====
  
{{bc|
+
Since kernel 3.6, PCI-E v2.0 in '''radeon''' is turned on by default.
Section "Device"
+
      Identifier  "My Graphics Card"
+
        Option "AGPMode"              "8"  #not used when KMS is on
+
Option "AGPFastWrite"          "off" #could cause instabilities enable it at your own risk
+
Option "SWcursor"              "off" #software cursor might be necessary on some rare occasions, hence set off by default
+
Option "EnablePageFlip"        "on"  #supported on all R/RV/RS4xx and older hardware and set off by default
+
Option "AccelMethod"          "EXA" #valid options are XAA and EXA. EXA is the newest acceleration method and it is the default.
+
Option "RenderAccel"          "on"  #enabled by default on all radeon hardware
+
Option "ColorTiling"          "on"  #enabled by default on RV300 and later radeon cards.
+
Option "EXAVSync"              "off" #default is off, otherwise on
+
Option "EXAPixmaps"            "on"  #when on icreases 2D performance, but may also cause artifacts on some old cards
+
Option "AccelDFS"              "on"  #default is off, read the radeon manpage for more information
+
EndSection
+
}}
+
  
Defining the '''gartsize''', if not autodetected, can be done with the following option:
+
It may be unstable with some motherboards, deactivation can be done by adding {{ic|1=radeon.pcie_gen2=0}} as a [[kernel parameters]].
  
In the kernel options (in this case {{ic|syslinux.cfg}}):
+
See [http://www.phoronix.com/scan.php?page=article&item=amd_pcie_gen2&num=1 Phoronix article] for more information.
  
APPEND root=/dev/sda1 ro 5 radeon.modeset=1 radeon.agpmode=8 radeon.gartsize=32 quiet
+
=== Gallium Heads-Up Display ===
  
Size is in megabytes and 32 is for RV280 cards.
+
The radeonsi driver supports activating a heads up display which can draw transparent graphs and text on top of applications that are rendering such as games. These can show such values as the current frame rate or the CPU load for each CPU core or an average of all of them. The HUD is controlled by the GALLIUM_HUD environment variable, and can be passed the following list of parameters among others:
 +
*"fps" - displays current frames per second
 +
*"cpu" - displays the average CPU load
 +
*"cpu0" - displays the CPU load for the first CPU core
 +
*"cpu0+cpu1" - displays the CPU load for the first two CPU cores
 +
*"draw-calls" - displays how many times each material in an object is drawn to the screen
 +
*"requested-VRAM" - displayed how much VRAM is being used on the GPU
 +
*"pixels-rendered" - displays how many pixels are being displayed
  
Alternatively, do it with a modprobe option in {{ic|/etc/modprobe.d/radeon.conf}}:
+
To see a full list of parameters as well as some notes on operating GALLIUM_HUD you can also pass the "help" parameter to a simple application such as glxgears and see the corresponding terminal output:
 +
{{bc|1=# GALLIUM_HUD="help" glxgears }}
  
options radeon gartsize=32
+
More information can be found from this [http://lists.freedesktop.org/archives/mesa-dev/2013-March/036586.html mailing list post] or [https://kparal.wordpress.com/2014/03/03/fraps-like-fps-overlay-for-linux/ this blog post].
  
'''For further information and other options, read the radeon manpage and the module's info page''':
+
== Hybrid graphics/AMD Dynamic Switchable Graphics ==
man radeon
+
  
modinfo radeon
+
It is the technology used on recent laptops equiped with two GPUs, one power-efficent (generally Intel integrated card) and one more powerful and more power-hungry (generally Radeon or Nvidia). There are two ways to get it work:
  
A fine tool to try is [https://www.archlinux.org/packages/community/any/driconf/ driconf]. It will allow you to modify several settings, like vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).
+
* If it is not required to run 'GPU-hungry' applications, it is possible to disable the discrete card (see [https://help.ubuntu.com/community/HybridGraphics#Using_vga_switcheroo Ubuntu wiki]): {{ic|echo OFF > /sys/kernel/debug/vgaswitcheroo/switch}}.
 +
* [[PRIME]]: Is a proper way to use hybrid graphics on Linux, but still requires a bit of manual intervention from the user.
  
=== Activate PCI-E 2.0 ===
+
== Powersaving ==
Can be unstable with some motherboards or not produce any performarce, test yourself adding "radeon.pcie_gen2=1" on the kernel command line.
+
{{Note|Power management is supported on all chips that include the appropriate power state tables in the vbios (R1xx and newer). "dpm" is only supported on R6xx and newer chips.}}
  
More info on [http://www.phoronix.com/scan.php?page=article&item=amd_pcie_gen2&num=1 Phoronix article]
+
With the radeon driver, power saving is disabled by default and has to be enabled manually if desired.
  
==Powersaving==
+
You can choose between three different methods:
  
The powersaving part is totally different with and without KMS.
+
# [[#Dynamic power management|dpm]] (enabled by default since kernel 3.13)
 +
# [[#Dynamic frequency switching|dynpm]]
 +
# [[#Profile-based frequency switching|profile]]
  
===With KMS enabled===
+
See http://www.x.org/wiki/RadeonFeature/#index3h2 for more details.
  
With the radeon driver, power saving is disabled by default but the stock kernel (2.6.35 as of this writing) provides a "sysfs" utility to enable it.
+
=== Dynamic power management ===
  
Power saving through KMS is still a work in progress for the most part. It should work, but some chips do have problems with it. A common issue for all is screen blinking when the kernel switches between power states, and in some configurations it even causes system freezes. But KMS is awesome, so it is your choice. The UMS method is generally more stable, however its power savings might not be as good as those provided by KMS options.
+
Since kernel 3.13, DPM is enabled by default for [http://kernelnewbies.org/Linux_3.13#head-f95c198f6fdc7defe36f470dc8369cf0e16898df lots of AMD Radeon hardware]. If you want to disable it, add the parameter {{ic|1=radeon.dpm=0}} to the [[kernel parameters]].
  
There are two ways to enable power management:
+
Unlike [[#Dynamic frequency switching|dynpm]], the "dpm" method uses hardware on the GPU to dynamically change the clocks and voltage based on GPU load. It also enables clock and power gating.
  
#Try adding {{ic|1=radeon.dynpm=1}} to the kernel parameters (if using the stock kernel < 2.6.35). If you are using Linux kernel >= 2.6.35 this option is no longer needed and the sysfs interface will be present by default. If this option is passed to a kernel >= 2.6.35, the driver will fail and fall back to software rendering.
+
There are 3 operation modes to choose from:
#Use the (unsupported) [radeon] repo:
+
  
This repository will grant you up-to-date packages of the radeon driver and its dependencies, from (mostly) git snapshots.
+
* {{ic|battery}} lowest power consumption
 +
* {{ic|balanced}} sane default
 +
* {{ic|performance}} highest performance
  
{{bc|1=
+
They can be changed via sysfs
[radeon]
+
# echo battery > /sys/class/drm/card0/device/power_dpm_state
Server = http://spiralinear.org/perry3d/$arch/
+
}}
+
  
You can select the methods via sysfs.
+
For testing or debugging purposes, you can force the card to run in a set performance mode:
  
With root access, you have two choices:
+
* {{ic|auto}} default; uses all levels in the power state
 +
* {{ic|low}} enforces the lowest performance level
 +
* {{ic|high}} enforces the highest performance level
  
1. '''Dynamic frequency switching (depending on GPU load)'''
+
# echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level
  
{{bc|# echo dynpm > /sys/class/drm/card0/device/power_method}}
+
==== Commandline Tools ====
  
The "dynpm" method dynamically changes the clocks based on the number of pending fences, so performance is ramped up when running GPU intensive apps, and ramped down when the GPU is idle. The re-clocking is attempted during vertical blanking periods, but due to the timing of the re-clocking functions, does not always complete in the blanking period, which can lead to flicker in the display. Due to this, dynpm only works when a single head is active.
+
* [https://github.com/superjamie/snippets/blob/master/radcard radcard] - A script to get and set DPM power states and levels
  
{{Note|The "profile" method mentioned below is not as aggressive as "dynpm," but is currently much more stable and flicker free and works with multiple heads active.}}
+
=== Old methods ===
  
2. '''Profile-based frequency switching'''
+
==== Dynamic frequency switching ====
  
{{bc|# echo profile > /sys/class/drm/card0/device/power_method}}
+
This method dynamically changes the frequency depending on GPU load, so performance is ramped up when running GPU intensive apps, and ramped down when the GPU is idle. The re-clocking is attempted during vertical blanking periods, but due to the timing of the re-clocking functions, does not always complete in the blanking period, which can lead to flicker in the display. Due to this, dynpm only works when a single head is active.
  
The "profile" mode will allow you to select one of the five profiles below.
+
It can be activated by simply running the following command:
Different profiles, for the most part, end up changing the frequency/voltage of the card.
+
  
* "default" uses the default clocks and does not change the power state. This is the default behavior.
+
# echo dynpm > /sys/class/drm/card0/device/power_method
* "auto" selects between "mid" and "high" power states based on the whether the system is on battery power or not. The "low" power state are selected when the monitors are in the dpms off state.
+
* "low" forces the gpu to be in the low power state all the time. Note that "low" can cause display problems on some laptops; this is why auto only uses "low" when displays are off.
+
* "mid" forces the gpu to be in the "mid" power state all the time. The "low" power state is selected when the monitors are in the dpms off state.
+
* "high" forces the gpu to be in the "high" power state all the time. The "low" power state is selected when the monitors are in the dpms off state.
+
  
So lets say we want the "low" option...for this, run the following command:
+
==== Profile-based frequency switching ====
  
{{bc|# echo low > /sys/class/drm/card0/device/power_profile}}
+
This method will allow you to select one of the five profiles (described below). Different profiles, for the most part, end up changing the frequency/voltage of the GPU. This method is not as aggressive, but is more stable and flicker free and works with multiple heads active.
  
Replace "low" with any of the aforementioned profiles as necessary.
+
To activate the method, run the following command:
  
{{Note|Echoing a profile value to this file is not permanent, so when you find something that fits your needs, you will need to add it to /etc/rc.local, so it is executed at system startup.}}
+
# echo profile > /sys/class/drm/card0/device/power_method
{{Note|Gnome-shell users may be interested in the following extension: [https://extensions.gnome.org/extension/356/radeon-power-profile-manager Radeon Power Profile Manager] for manually controlling the GPU profiles.}}
+
  
Power management is supported on all asics (r1xx-evergreen) that include the appropriate power state tables in the vbios; not all boards do (especially older desktop cards).
+
Select one of the available profiles:
 +
* {{ic|default}} uses the default clocks and does not change the power state. This is the default behaviour.
 +
* {{ic|auto}} selects between {{ic|mid}} and {{ic|high}} power states based on the whether the system is on battery power or not.
 +
* {{ic|low}} forces the gpu to be in the {{ic|low}} power state all the time. Note that {{ic|low}} can cause display problems on some laptops, which is why {{ic|auto}} only uses {{ic|low}} when monitors are off. Selected on other profiles when the monitors are in the [[DPMS]]-off state.
 +
* {{ic|mid}} forces the gpu to be in the {{ic|mid}} power state all the time.
 +
* {{ic|high}} forces the gpu to be in the {{ic|high}} power state all the time.
  
To view the speed that the GPU is running at, perform the following command and you will get something like this output:
+
As an example, we will activate the {{ic|low}} profile (replace {{ic|low}} with any of the aforementioned profiles as necessary):
  
{{hc|$ cat /sys/kernel/debug/dri/0/radeon_pm_info|<nowiki>  state: PM_STATE_ENABLED
+
# echo low > /sys/class/drm/card0/device/power_profile
  default engine clock: 300000 kHz
+
  current engine clock: 300720 kHz
+
  default memory clock: 200000 kHz</nowiki>}}
+
  
If /sys/kernel/debug is empty, run this command:
+
==== Persistent configuration ====
  
{{bc|# mount -t debugfs none /sys/kernel/debug}}
+
The activation described above is not persistent, it will not last when the computer is rebooted. To make it persistent, you can use [[systemd#Temporary files|systemd-tmpfiles]] (example for [[#Dynamic frequency switching]]):
  
To permanently mount, add the following line to /etc/fstab:
+
{{hc|/etc/tmpfiles.d/radeon-pm.conf|<nowiki>
 +
w /sys/class/drm/card0/device/power_method - - - - dynpm
 +
</nowiki>}}
  
debugfs  /sys/kernel/debug  debugfs   defaults   0   0
+
Alternatively, you may use this [[udev]] rule instead (example for [[#Profile-based frequency switching]]):
 +
 
 +
{{hc|/etc/udev/rules.d/30-radeon-pm.rules|<nowiki>
 +
KERNEL=="dri/card0", SUBSYSTEM=="drm", DRIVERS=="radeon", ATTR{device/power_method}="profile", ATTR{device/power_profile}="low"
 +
</nowiki>}}
 +
 
 +
{{Note|If the above rule is failing, try removing the {{ic|dri/}} prefix.}}
 +
 
 +
==== Graphical tools ====
 +
 
 +
* {{App|Radeon-tray|A small program to control the power profiles of your Radeon card via systray icon. It is written in PyQt4 and is suitable for non-Gnome users.|https://github.com/StuntsPT/Radeon-tray|{{AUR|radeon-tray}}}}
 +
* {{App|power-play-switcher|A gui for changing powerplay setting of the open source driver for ati radeon video cards.|https://code.google.com/p/power-play-switcher/|{{AUR|power-play-switcher}}{{Broken package link|{{aur-mirror|power-play-switcher}}}}}}
 +
* {{App|Gnome-shell-extension-Radeon-Power-Profile-Manager|A small extension for Gnome-shell that will allow you to change the power profile of your radeon card when using the open source drivers.|https://github.com/StuntsPT/shell-extension-radeon-power-profile-manager|{{AUR|gnome-shell-extension-radeon-ppm}}{{Broken package link|{{aur-mirror|gnome-shell-extension-radeon-ppm}}}} {{AUR|gnome-shell-extension-radeon-power-profile-manager-git}}{{Broken package link|{{aur-mirror|gnome-shell-extension-radeon-power-profile-manager-git}}}}}}
 +
 
 +
=== Other notes ===
 +
 
 +
To view the speed that the GPU is running at, perform the following command and you will get something like this output:
 +
 
 +
{{hc|# cat /sys/kernel/debug/dri/0/radeon_pm_info|<nowiki>
 +
   state: PM_STATE_ENABLED
 +
   default engine clock: 300000 kHz
 +
   current engine clock: 300720 kHz
 +
   default memory clock: 200000 kHz
 +
</nowiki>}}
  
 
It depends on which GPU line yours is, however. Along with the radeon driver versions, kernel versions, etc. So it may not have much/any voltage regulation at all.
 
It depends on which GPU line yours is, however. Along with the radeon driver versions, kernel versions, etc. So it may not have much/any voltage regulation at all.
  
Thermal sensors are implemented via external i2c chips or via the internal thermal sensor (rv6xx-evergreen only). To get the temperature on asics that use i2c chips, you need to load the appropriate hwmon driver for the sensor used on your board (lm63, lm64, etc.). The drm will attempt to load the appropriate hwmon driver. On boards that use the internal thermal sensor, the drm will set up the hwmon interface automatically. When the appropriate driver is loaded, the temperatures can be accessed via lm_sensors tools or via sysfs in /sys/class/hwmon .
+
Thermal sensors are implemented via external i2c chips or via the internal thermal sensor (rv6xx-evergreen only). To get the temperature on asics that use i2c chips, you need to load the appropriate hwmon driver for the sensor used on your board (lm63, lm64, etc.). The drm will attempt to load the appropriate hwmon driver. On boards that use the internal thermal sensor, the drm will set up the hwmon interface automatically. When the appropriate driver is loaded, the temperatures can be accessed via [[lm_sensors]] tools or via sysfs in {{ic|/sys/class/hwmon}}.
  
There is a GUI for switching profiles [http://code.google.com/p/power-play-switcher here] ([https://aur.archlinux.org/packages.php?ID=53752 available in AUR]).
+
== Fan Speed ==
  
===Without KMS===
+
While the power saving features above should handle fan speeds quite well, some cards may still be too noisy in their idle state. In this case, and when your card supports it, you can change the fan speed manually.
  
In your {{ic|xorg.conf}} file, add 2 lines to "Device" Section:
+
{{Note|
        Option      "DynamicPM"          "on"
+
* Keep in mind that the following method sets the fan speed to a fixed value, hence it will not adjust with the stress of your gpu, which can lead to overheating under heavy load.
        Option      "ClockGating"        "on"
+
* Better check your gpu temperature when applying lower than standard values. 
 +
}}
 +
 +
First, issue the following command to enable the manual adjustment of the fan speed of your graphics card (or your first gpu in case of a multi gpu setup).
  
If the two options are enabled successfully, you will see following lines in /var/log/Xorg.0.log:
+
# echo 1 > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1_enable
  
        (**) RADEON(0): Option "ClockGating" "on"
+
Then set your desired fan speed from 0 to 255, which corresponds to 0-100% fan speed (The following command sets it to roughly 20%)
        (**) RADEON(0): Option "DynamicPM" "on"
+
  
        Static power management enable success
+
# echo 55 > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1
        (II) RADEON(0): Dynamic Clock Gating Enabled
+
        (II) RADEON(0): Dynamic Power Management Enabled
+
  
If you desire low power cost, you can add an extra line to "Device" Section of {{ic|xorg.conf}}:
+
For persistence, use [[systemd#Temporary files|systemd-tmpfiles]] as shown above by the example with power profiles.
        Option      "ForceLowPowerMode"  "on"
+
  
==TV out==
+
If a fixed value isn't desired, there are possibilities to define a custom fan curve manually by, for example, writing a script in which fan speeds are set depending on the current temperature (current value in /sys/class/drm/card0/device/hwmon/hwmon2/temp1_input), preferably with hystereses. There is also a gui solution: http://github.com/marazmista/radeon-profile{{AUR|radeon-profile-git}}.
{{out of date}}
+
Since August 2007, there is TV-out support for all Radeons with integrated TV-out.
+
  
It is somewhat limited for now, it does not always autodetect the output correctly and only NTSC mode works.
+
== TV out ==
  
 
First, check that you have an S-video output: {{ic|xrandr}} should give you something like
 
First, check that you have an S-video output: {{ic|xrandr}} should give you something like
Line 305: Line 313:
  
 
Now we should tell Xorg that it is actually connected (it ''is'', right?)
 
Now we should tell Xorg that it is actually connected (it ''is'', right?)
  xrandr --output S-video --set load_detection 1
+
  xrandr --output S-video --set "load detection" 1
  
Setting tv standard to use:
+
Setting TV standard to use:
  xrandr --output S-video --set tv_standard ntsc
+
  xrandr --output S-video --set "tv standard" ntsc
  
Adding a mode for it (currently it supports only 800x600):
+
Adding a mode for it (currently supports only 800x600):
 
  xrandr --addmode S-video 800x600
 
  xrandr --addmode S-video 800x600
  
I will go for a clone mode:
+
Clone mode:
 
  xrandr --output S-video --same-as VGA-0
 
  xrandr --output S-video --same-as VGA-0
  
So far so good. Now let us try to see what we have:
+
Now let us try to see what we have:
 
  xrandr --output S-video --mode 800x600
 
  xrandr --output S-video --mode 800x600
  
Line 326: Line 334:
 
Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.
 
Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.
  
To send the output to the TV, I do
+
To send the output to the TV, do:
 
  xvattr -a XV_CRTC -v 1
 
  xvattr -a XV_CRTC -v 1
  
{{Note| you need to install '''xvattr''' from [[AUR]] to execute this command.}}
+
{{Note| you need to install {{AUR|xvattr}}{{Broken package link|{{aur-mirror|xvattr}}}} to execute this command.}}
  
To switch back to my monitor, I change this to {{ic|0}}. {{ic|-1}} is used for automatic switching in dualhead setups.
+
To switch back to the monitor, I change this to {{ic|0}}. {{ic|-1}} is used for automatic switching in dualhead setups.
  
 
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg configuration file.
 
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg configuration file.
Line 337: Line 345:
 
=== Force TV-out in KMS ===
 
=== Force TV-out in KMS ===
  
Kernel can recognize {{ic|1=video=}} parameter in following form:
+
The kernel can recognize {{ic|1=video=}} parameter in following form (see [[KMS]] for more details):
  
  video=<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
+
video=<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]
 
+
(see [[KMS]])
+
  
 
For example:
 
For example:
  
  video=DVI-I-1:1280x1024-24@60e
+
video=DVI-I-1:1280x1024-24@60e
or
+
  "video=9-pin DIN-1:1024x768-24@60e"
+
  
Parameters with whitespaces must be quoted. Current mkinitcpio implementation also requires # before. For example:
+
Parameters with whitespaces must be quoted:
  
  root=/dev/disk/by-uuid/d950a14f-fc0c-451d-b0d4-f95c2adefee3 ro quiet radeon.modeset=1 security=none # video=DVI-I-1:1280x1024-24@60e "video=9-pin DIN-1:1024x768-24@60e"
+
"video=9-pin DIN-1:1024x768-24@60e"
 +
 
 +
Current mkinitcpio implementation also requires {{ic|#}} in front. For example:
 +
 
 +
root=/dev/disk/by-uuid/d950a14f-fc0c-451d-b0d4-f95c2adefee3 ro quiet radeon.modeset=1 security=none # video=DVI-I-1:1280x1024-24@60e "video=9-pin DIN-1:1024x768-24@60e"
  
 
* Grub can pass such command line as is.
 
* Grub can pass such command line as is.
* Lilo needs backslashes for doublequotes (append="...... # .... \"video=9-pin DIN-1:1024x768-24@60e\"")
+
* Lilo needs backslashes for doublequotes (append {{ic|1=# \"video=9-pin DIN-1:1024x768-24@60e\"}})
 
* Grub2: TODO
 
* Grub2: TODO
  
 
You can get list of your video outputs with following command:
 
You can get list of your video outputs with following command:
  
{{bc|<nowiki>ls -1 /sys/class/drm/ | grep -E '^card[[:digit:]]+-' | cut -d- -f2-</nowiki>}}
+
{{bc|<nowiki>$ ls -1 /sys/class/drm/ | grep -E '^card[[:digit:]]+-' | cut -d- -f2-</nowiki>}}
  
== HDMI Audio ==
+
== HDMI audio ==
  
'''xf86-video-ati''' can enable HDMI audio output for all supported chipsets up to r7xx when using [[ATI#Kernel_mode-setting_.28KMS.29|KMS]]. Just use xrandr to enable the output and Test as described below.
+
HDMI audio is supported in the {{Pkg|xf86-video-ati}} video driver. If you are using a kernel 3.x older than 3.13, HDMI audio is disabled by default because it can be problematic. To enable HDMI audio add {{ic|1=radeon.audio=1}} to your [[kernel parameters]].
  
=== Testing HDMI Audio ===
+
If there is no video after boot up, the driver option has to be disabled.
# Connect your PC to the Display via HDMI cable.
+
# Use xrandr to get picture to the Display. Ex: {{ic|xrandr --output DVI-D_1 --mode 1280x768 --right-of PANEL}}. Simply typing {{ic|xrandr}} will give you a list of your valid outputs.
+
# Run {{ic|aplay -l}} to get the list of your sound devices. Find HDMI and note the card number and corresponding device number. Example of what you want to see: {{ic|card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]}}
+
# Try sending sound to this device: {{ic|aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav}}. Be sure to change plughw:z,y to match your hardware number found with last command. You should be able to hear the test sound from your Display.
+
  
* The audio module is disabled by default in kernel >=3.0. Add {{ic|1=radeon.audio=1}} to the end of your "kernel" line in /boot/grub/menu.lst to enable it.
+
{{Note|
* See [https://bbs.archlinux.org/viewtopic.php?id=124130 this thread]
+
* If HDMI audio does not work after installing the driver, test your setup with the procedure at [[Advanced Linux Sound Architecture/Troubleshooting#HDMI Output does not work]].
* If the sound is distorted try [[PulseAudio#Glitches, skips or crackling|setting tsched=0]] and make sure {{ic|rtkit}} daemon is running.
+
* If the sound is distorted in PulseAudio try setting {{ic|1=tsched=0}} as described in [[PulseAudio/Troubleshooting#Glitches, skips or crackling]] and make sure {{ic|rtkit}} daemon is running.
 +
* Your sound card might use the same module, since HDA compliant hardware is pretty common. [[Advanced_Linux_Sound_Architecture#Set_the_default_sound_card|Change the default sound card]] using one of the suggested methods, which include using the {{ic|defaults}} node in alsa configuration.
 +
}}
  
== Dual Head Setup ==
+
== Multihead setup ==
=== Independent X Screens ===
+
Independent dual-headed setups can be configured the usual way. However you might want to know that the radeon driver has a {{ic|"ZaphodHeads"}} option which allows you to bind a specific device section to an output of your choice, for instance using:
+
        Section "Device"
+
        Identifier    "Device0"
+
        Driver        "radeon"
+
        Option        "ZaphodHeads"  "VGA-0"
+
        VendorName    "ATI"
+
        BusID          "PCI:1:0:0"
+
        Screen          0
+
        EndSection
+
  
This can be a life-saver, because some cards which have more than two outputs (for instance one HDMI out, one DVI, one VGA), will only select and use HDMI+DVI outputs for the dual-head setup, unless you explicitely specify {{ic|"ZaphodHeads"  "VGA-0"}}.
+
=== Using the RandR extension ===
  
Moreover, this option allows you to easily select the screen you want to mark as primary.
+
See [[Multihead#RandR]] how to setup multiple monitors by using [[Wikipedia:RandR|RandR]].
 +
 
 +
=== Independent X screens ===
 +
 
 +
Independent dual-headed setups can be configured the usual way. However you might want to know that the radeon driver has a {{ic|"ZaphodHeads"}} option which allows you to bind a specific device section to an output of your choice:
 +
{{hc|/etc/X11/xorg.conf.d/20-radeon.conf|
 +
Section "Device"
 +
  Identifier "Device0"
 +
  Driver "radeon"
 +
  Option "ZaphodHeads" "VGA-0"
 +
  VendorName "ATI"
 +
  BusID "PCI:1:0:0"
 +
  Screen 0
 +
EndSection
 +
}}
 +
 
 +
This can be a life-saver, when using videocards that have more than two outputs. For instance one HDMI out, one DVI, one VGA, will only select and use HDMI+DVI outputs for the dual-head setup, unless you explicitly specify {{ic|"ZaphodHeads" "VGA-0"}}.
 +
 
 +
== Turn vsync off ==
 +
 
 +
The radeon driver will enable vsync by default, which is perfectly fine except for benchmarking. To turn it off, create {{ic|~/.drirc}} (or edit it if it already exists) and add the following section:
 +
{{hc|~/.drirc|<nowiki>
 +
<driconf>
 +
    <device screen="0" driver="dri2">
 +
        <application name="Default">
 +
            <option name="vblank_mode" value="0" />
 +
        </application>
 +
    </device>
 +
    <!-- Other devices ... -->
 +
</driconf>
 +
</nowiki>}}
 +
Make sure the driver is '''dri2''', not your video card code (like r600).
 +
 
 +
{{Accuracy|If the above does not work, please file a bug report. Also, why is the {{ic|SwapbuffersWait}} option relevant here?}}
 +
 
 +
If vsync is still enabled, you can try to disable it by editing the xf86-video-ati configuration :
 +
 
 +
{{hc|/etc/X11/xorg.conf.d/20-radeon.conf|<nowiki>
 +
Section "Device"
 +
Identifier  "My Graphics Card"
 +
Driver "radeon"
 +
Option "EXAVSync" "off"
 +
Option "SwapbuffersWait" "false"
 +
EndSection
 +
</nowiki>}}
  
 
== Troubleshooting ==
 
== Troubleshooting ==
  
=== I encounter artifacts when logging into my DE or WM ===
+
=== Artifacts upon logging in ===
  
If you encounter artifacts, first try starting X without {{ic|/etc/X11/xorg.conf}}. Recent versions of Xorg are capable of reliable auto-detection and auto-configuration for most use cases. Outdated or improperly configured {{ic|xorg.conf}} files are known to cause trouble.
+
If encountering artifacts, first try starting X without {{ic|/etc/X11/xorg.conf}}. Recent versions of Xorg are capable of reliable auto-detection and auto-configuration for most use cases. Outdated or improperly configured {{ic|xorg.conf}} files are known to cause trouble.
  
 
In order to run without a configuration tile, it is recommended that the {{ic|xorg-input-drivers}} package group be installed.
 
In order to run without a configuration tile, it is recommended that the {{ic|xorg-input-drivers}} package group be installed.
  
Artifacts may also be related to [[kernel mode setting]]. Consider [[#Disable KMS|disabling KMS]].
+
You may as well try disabling {{ic|EXAPixmaps}} in {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}}:
 
+
You may as well try disabling '''EXAPixmaps''' in {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}}:
+
  
 
  Section "Device"
 
  Section "Device"
Line 409: Line 447:
 
  EndSection
 
  EndSection
  
Further tweaking could be done by disabling '''AccelDFS'''
+
=== Adding undetected resolutions ===
 
+
Option "AccelDFS" "off"
+
 
+
=== I have installed the open source driver and my card is painfully slow ===
+
 
+
{{Note|Make sure you are member of '''video''' group.}}
+
 
+
Some cards can be installed by default trying to use [[ATI#AMD/Ati cards and kernel mode-setting (KMS)|KMS]]. You can check whether this is your case running:
+
dmesg | egrep "drm|radeon"
+
 
+
This command might show something ''like'' this, meaning it is trying to default to KMS:
+
[drm] radeon default to kernel modesetting.
+
...
+
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL
+
  
If your card is not supported by KMS (anything older than r100), then you can [[ATI#Disable KMS|disable KMS]]. This should fix the problem.
+
Please see the [[Xrandr#Adding_undetected_resolutions|Xrandr page]].
  
 
=== AGP is disabled (with KMS) ===
 
=== AGP is disabled (with KMS) ===
Line 431: Line 455:
 
If you experience poor performance and dmesg shows something like this
 
If you experience poor performance and dmesg shows something like this
 
  [drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19
 
  [drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19
then check if the agp driver for your motherboard (e.g., {{ic|via_agp}}, {{ic|intel_agp}} etc.) is loaded before the {{ic|radeon}} module, see [[ATI#Enabling KMS|Enabling KMS]].
+
then check if the agp driver for your motherboard (e.g., {{ic|via_agp}}, {{ic|intel_agp}} etc.) is loaded before the {{ic|radeon}} module, see [[#Enabling KMS|Enabling KMS]].
  
=== My TV is showing a black border around the screen ===
+
=== TV showing a black border around the screen ===
  
 
When I connected my TV to my Radeon HD 5770 using the HDMI port, the TV showed a blurry picture with a 2-3cm border around it. This is not the case when using the proprietary driver. However, this protection against overscanning (see [[Wikipedia:Overscan]]) can be turned off using xrandr:
 
When I connected my TV to my Radeon HD 5770 using the HDMI port, the TV showed a blurry picture with a 2-3cm border around it. This is not the case when using the proprietary driver. However, this protection against overscanning (see [[Wikipedia:Overscan]]) can be turned off using xrandr:
 
  xrandr --output HDMI-0 --set underscan off
 
  xrandr --output HDMI-0 --set underscan off
  
=== No Desktop Effects in KDE4 with X1300 and Radeon Driver ===
+
=== Black screen with mouse cursor on resume from suspend in X ===
 +
 
 +
Waking from suspend on cards with 32MB or less can result in a black screen with a mouse pointer in X.  Some parts of the screen may be redrawn when under the mouse cursor.  Forcing {{ic|EXAPixmaps}} to {{ic|"enabled"}} in {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}} may fix the problem.  See [[#Performance tuning|performance tuning]] for more information.
 +
 
 +
=== No desktop effects in KDE4 with X1300 and Radeon driver ===
  
 
A bug in KDE4 may prevent an accurate video hardware check, thereby deactivating desktop effects despite the X1300 having more than sufficient GPU power. A workaround may be to manually override such checks in KDE4 configuration files {{ic|/usr/share/kde-settings/kde-profile/default/share/config/kwinrc}} and/or {{ic|.kde/share/config/kwinrc}}.  
 
A bug in KDE4 may prevent an accurate video hardware check, thereby deactivating desktop effects despite the X1300 having more than sufficient GPU power. A workaround may be to manually override such checks in KDE4 configuration files {{ic|/usr/share/kde-settings/kde-profile/default/share/config/kwinrc}} and/or {{ic|.kde/share/config/kwinrc}}.  
Line 444: Line 472:
 
Add:
 
Add:
 
  DisableChecks=true
 
  DisableChecks=true
+
 
 
To the [Compositing] section. Ensure that compositing is enabled with:
 
To the [Compositing] section. Ensure that compositing is enabled with:
 
  Enabled=true
 
  Enabled=true
  
 
=== Black screen and no console, but X works in KMS ===
 
=== Black screen and no console, but X works in KMS ===
This is a solution to no-console problem that might come up, when using two or more ATI cards on the same PC. Fujitsu Siemens Amilo PA 3553 laptop for example has this problem. This is due to fbcon console driver mapping itself to wrong framebuffer device that exist on the wrong card. This can be fixed by adding a this to the kernel boot line:
+
 
 +
This is a solution to the no-console problem that might come up, when using two or more ATI cards on the same PC. Fujitsu Siemens Amilo PA 3553 laptop for example has this problem. This is due to fbcon console driver mapping itself to the wrong framebuffer device that exists on the wrong card. This can be fixed by adding this to the kernel boot line:
 
  fbcon=map:1
 
  fbcon=map:1
This will tell the fbcon to map itself to the {{ic|/dev/fb1}} framebuffer dev and not the {{ic|/dev/fb0}}, that in our case exist on the wrong graphics card.
+
This will tell the fbcon to map itself to the {{ic|/dev/fb1}} framebuffer dev and not the {{ic|/dev/fb0}}, that in our case exists on the wrong graphics card. If that does not fix your problem, try booting with
 +
fbcon=map:0
 +
instead.
  
=== Some 3D applications show textures as all black or crash ===
+
=== 2D performance (e.g. scrolling) is slow ===
You might need texture compression support, which is not included with the open source driver.  Install [https://aur.archlinux.org/packages.php?ID=15571 libtxc_dxtn] from AUR (or [https://aur.archlinux.org/packages.php?ID=40343 lib32-libtxc_dxtn] for multilib systems).
+
  
For a list of supported games have a look at the [http://xorg.freedesktop.org/wiki/RadeonProgram Radeon Program] page.
+
If you're having problems with 2D performance, like scrolling in terminal or browser, you might need to add {{ic|Option  "MigrationHeuristic"  "greedy"}} into the {{ic|"Device"}} section of your {{ic|xorg.conf}} file.
  
On R600 chips you additionally have to
+
{{Note|This only applies to EXA.}}
export R600_ENABLE_S3TC=1
+
to enable the texture compression support (for permanent change write this line to your ~/.bashrc).
+
  
=== 2D performance (e.g. scrolling) is slow ===
+
Below is a sample configuration file {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:
If you have problem with 2D performance, like scrolling in terminal or browser, you might need to add {{ic|Option  "MigrationHeuristic"  "greedy"}} into the {{ic|"Device"}} section of your {{ic|xorg.conf}} file.
+
 
+
Bellow is a sample config file {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:
+
  
 
{{bc|
 
{{bc|
Line 474: Line 499:
 
EndSection
 
EndSection
 
}}
 
}}
 +
 +
=== Monitor rotation works for cursor but not windows/content ===
 +
 +
Users with newer graphics boards who have enabled EXA instead of glamor may find that rotating their monitor with xrandr causes the cursor and monitor dimensions to rotate, but windows and other content stay in their normal orientation. Additionally, the cursor moves according to normal rotation when the user moves the mouse. Look for the following line in your {{ic|/var/log/Xorg.0.log}} when you issue the xrandr rotate command:
 +
{{bc|
 +
(EE) RADEON(0): Rotation requires acceleration!
 +
}}
 +
Acceleration is disabled when using EXA on newer graphics cards (source: [https://bugs.freedesktop.org/show_bug.cgi?id=73420#c17 comment 17]). You must choose between enabling EXA ([[#Glamor|detailed above in the glamor section]]) and the ability to rotate.
  
 
=== ATI X1600 (RV530 series) 3D application show black windows ===
 
=== ATI X1600 (RV530 series) 3D application show black windows ===
 +
 
There are three possible solutions:
 
There are three possible solutions:
* Try editing {{ic|/boot/grub/menu.lst}} and add {{ic|<nowiki>pci=nomsi</nowiki>}} at the end of your kernel line.
+
* Try adding {{ic|<nowiki>pci=nomsi</nowiki>}} to your boot loader [[Kernel parameters]].
* If this doesn't work, you can try adding {{ic|noapic}} instead of {{ic|<nowiki>pci=nomsi</nowiki>}}.
+
* If this does not work, you can try adding {{ic|noapic}} instead of {{ic|<nowiki>pci=nomsi</nowiki>}}.
* If none of the above work, then you can try running {{ic|<nowiki>vblank_mode=0 glxgears</nowiki>}} or {{ic|<nowiki>vblank_mode=1 glxgears</nowiki>}} to see which one works for you, then install {{ic|driconf}} via pacman and set that option in {{ic|~/.drirc}}.
+
* If none of the above work, then you can try running {{ic|<nowiki>vblank_mode=0 glxgears</nowiki>}} or {{ic|<nowiki>vblank_mode=1 glxgears</nowiki>}} to see which one works for you, then install {{pkg|driconf}} and set that option in {{ic|~/.drirc}}.
 +
 
 +
=== Cursor corruption after coming out of sleep ===
 +
 
 +
If the cursor becomes corrupted like it's repeating itself vertically after the monitor(s) comes out of sleep, set {{ic|"SWCursor" "True"}} in the {{ic|"Device"}} section of the {{ic|20-radeon.conf}} configuration file.
 +
 
 +
=== DisplayPort stays black on multimonitor mode ===
 +
 
 +
Try booting with the [[kernel parameter]] {{ic|1=radeon.audio=0}}.
 +
 
 +
=== Low 2D performance in console and X ===
 +
{{Accuracy|This disables Power Management that may result in overheating and/or damaging the GPU.}}
 +
Since kernel 4.1.4, [[#Dynamic power management|dpm]] is broken on certain R9 270X cards (chip device number 6810, subsystem 174b:e271, shown as Curacao XT, PC Partner Limited / Sapphire Technology Device e271 in lspci). The regression is caused by a [https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=ea039f927524e36c15b5905b4c9469d788591932 fix] for cards with the same PCI ids. Disabling dpm (add {{ic|1=radeon.dpm=0}} to the [[kernel parameters]]) solves the problem.

Latest revision as of 09:08, 25 July 2016

Related articles

Owners of AMD (previously ATI) video cards have a choice between proprietary driver (catalystAUR) and the open source drivers (ATI for older or AMDGPU for newer cards). This article covers the ATI/Radeon open source driver for older cards.

The open source driver is on par performance-wise with the proprietary driver for many cards. (See this benchmark.) It also has good dual-head support but worse TV-out support. Newer cards support might be lagging behind Catalyst.

If unsure, try the open source driver first, it will suit most needs and is generally less problematic. See the feature matrix to know what is supported for the GPU.

Selecting the right driver

Depending on the card you have, find the right driver in Xorg#ATI. This page has instructions for ATI.

Naming conventions

The Radeon brand follows a naming scheme that relates each product to a market segment. Within this article, readers will see both product names (e.g. HD 4850, X1900) and code or core names (e.g. RV770, R580). Traditionally, a product series will correspond to a core series (e.g. the "X1000" product series includes the X1300, X1600, X1800, and X1900 products which utilize the "R500" core series – including the RV515, RV530, R520, and R580 cores).

For a table of core and product series, see Wikipedia:Radeon and Wikipedia:List of AMD graphics processing units.

Installation

Note: If coming from the proprietary Catalyst driver, see AMD Catalyst#Uninstallation first.

Install the xf86-video-ati package. It provides the DDX driver for 2D acceleration and it pulls in mesa as a dependency, providing the DRI driver for 3D acceleration.

To enable OpenGL support, also install mesa-libgl. If you are on x86_64 and need 32-bit support, also install lib32-mesa-libgl from the multilib repository.

Support for accelerated video decoding is provided by mesa-vdpau and lib32-mesa-vdpau packages.

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-radeon.conf, and add the following:

Section "Device"
    Identifier "Radeon"
    Driver "radeon"
EndSection

Using this section, you can enable features and tweak the driver settings.

Loading

The radeon kernel module should load fine automatically on system boot.

If it does not happen, then:

Enable early KMS

Tip: If you have problems with the resolution, Kernel mode setting#Forcing modes and EDID may help.

Kernel mode setting (KMS) is supported by the radeon 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 radeon module to the MODULES line in /etc/mkinitcpio.conf:

MODULES="... radeon ..."

Now, regenerate the initramfs:

# mkinitcpio -p linux

The change takes effect at the next reboot.

Performance tuning

Enabling video acceleration

See Hardware video acceleration.

Driver options

The following options apply to /etc/X11/xorg.conf.d/20-radeon.conf.

Please read man radeon and RadeonFeature first before applying driver options.

ColorTiling and ColorTiling2D is completely safe to enable and supposedly is enabled by default. Most users will notice increased performance but it is not yet supported on R200 and earlier cards. Can be enabled on earlier cards, but the workload is transferred to the CPU:

Option "ColorTiling" "on"
Option "ColorTiling2D" "on"

DRI3 support can be enabled, instead of using the default DRI2. You may want to read the following benchmark by Phoronix to give you an idea of the performance of DRI2 vs DRI3:

Option "DRI" "3"

TearFree is a tearing prevention using the hardware page flipping mechanism. Enabling this option currently disables Option "EnablePageFlip":

Option "TearFree" "on"

Acceleration architecture; Glamor is available as 2D acceleration method implement through OpenGL, and it should work with graphic cards whose drivers are newer or equal to R300. Since xf86-video-ati driver-1:7.2.0-1, it is automatically enabled with radeonsi drivers (Southern Islands and superior GFX cards); on other graphic cards the method can be forced by adding AccelMethod glamor to the configuration file:

Option "AccelMethod" "glamor"

When using Glamor as acceleration architecture it is possible to enable the option ShadowPrimary, enables a so-called "shadow primary" buffer for fast CPU access to pixel data, and separate scanout buf‐fers 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 that enabling this option currently disables Option "EnablePageFlip":

Option "ShadowPrimary" "on"

EXAVSync is only available when using EXA and can be enabled to avoid tearing by stalling the engine until the display controller has passed the destination region. It reduces tearing at the cost of performance and has been know to cause instability on some chips:

Option "EXAVSync" "yes"

Below is a sample configuration file of /etc/X11/xorg.conf.d/20-radeon.conf:

Section "Device"
	Identifier  "Radeon"
	Driver "radeon"
	Option "AccelMethod" "glamor"
        Option "DRI" "3"
        Option "TearFree" "on"
EndSection
Tip: driconf is a tool that allows to modify several settings: vsync, anisotropic filtering, texture compression, etc. Using this tool it is also possible to "disable Low Impact fallback" needed by some programs (e.g. Google Earth).

Kernel parameters

Tip: You may want to debug the newly parameters with systool as stated in Kernel modules#Obtaining information.

Useful kernel parameters may be radeon.bapm=1 [1], radeon.disp_priority=2 [2], radeon.hw_i2c=1 [3], radeon.mst=1 [4], radeon.msi=1 (force-enable MSI-support), radeon.audio=0 (force-disable GPU audio) and/or radeon.tv=0 (disable TV-out).

Defining the gartsize, if not autodetected, can be done by adding radeon.gartsize=32 into kernel parameters.

Note: Setting this parameter should not be needed anymore with modern AMD videocards:
[drm] Detected VRAM RAM=2048M, BAR=256M
[drm] radeon: 2048M of VRAM memory ready
[drm] radeon: 2048M of GTT memory ready.

The changes take effect at the next reboot.

Deactivating PCI-E 2.0

Since kernel 3.6, PCI-E v2.0 in radeon is turned on by default.

It may be unstable with some motherboards, deactivation can be done by adding radeon.pcie_gen2=0 as a kernel parameters.

See Phoronix article for more information.

Gallium Heads-Up Display

The radeonsi driver supports activating a heads up display which can draw transparent graphs and text on top of applications that are rendering such as games. These can show such values as the current frame rate or the CPU load for each CPU core or an average of all of them. The HUD is controlled by the GALLIUM_HUD environment variable, and can be passed the following list of parameters among others:

  • "fps" - displays current frames per second
  • "cpu" - displays the average CPU load
  • "cpu0" - displays the CPU load for the first CPU core
  • "cpu0+cpu1" - displays the CPU load for the first two CPU cores
  • "draw-calls" - displays how many times each material in an object is drawn to the screen
  • "requested-VRAM" - displayed how much VRAM is being used on the GPU
  • "pixels-rendered" - displays how many pixels are being displayed

To see a full list of parameters as well as some notes on operating GALLIUM_HUD you can also pass the "help" parameter to a simple application such as glxgears and see the corresponding terminal output:

# GALLIUM_HUD="help" glxgears

More information can be found from this mailing list post or this blog post.

Hybrid graphics/AMD Dynamic Switchable Graphics

It is the technology used on recent laptops equiped with two GPUs, one power-efficent (generally Intel integrated card) and one more powerful and more power-hungry (generally Radeon or Nvidia). There are two ways to get it work:

  • If it is not required to run 'GPU-hungry' applications, it is possible to disable the discrete card (see Ubuntu wiki): echo OFF > /sys/kernel/debug/vgaswitcheroo/switch.
  • PRIME: Is a proper way to use hybrid graphics on Linux, but still requires a bit of manual intervention from the user.

Powersaving

Note: Power management is supported on all chips that include the appropriate power state tables in the vbios (R1xx and newer). "dpm" is only supported on R6xx and newer chips.

With the radeon driver, power saving is disabled by default and has to be enabled manually if desired.

You can choose between three different methods:

  1. dpm (enabled by default since kernel 3.13)
  2. dynpm
  3. profile

See http://www.x.org/wiki/RadeonFeature/#index3h2 for more details.

Dynamic power management

Since kernel 3.13, DPM is enabled by default for lots of AMD Radeon hardware. If you want to disable it, add the parameter radeon.dpm=0 to the kernel parameters.

Unlike dynpm, the "dpm" method uses hardware on the GPU to dynamically change the clocks and voltage based on GPU load. It also enables clock and power gating.

There are 3 operation modes to choose from:

  • battery lowest power consumption
  • balanced sane default
  • performance highest performance

They can be changed via sysfs

# echo battery > /sys/class/drm/card0/device/power_dpm_state

For testing or debugging purposes, you can force the card to run in a set performance mode:

  • auto default; uses all levels in the power state
  • low enforces the lowest performance level
  • high enforces the highest performance level
# echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level

Commandline Tools

  • radcard - A script to get and set DPM power states and levels

Old methods

Dynamic frequency switching

This method dynamically changes the frequency depending on GPU load, so performance is ramped up when running GPU intensive apps, and ramped down when the GPU is idle. The re-clocking is attempted during vertical blanking periods, but due to the timing of the re-clocking functions, does not always complete in the blanking period, which can lead to flicker in the display. Due to this, dynpm only works when a single head is active.

It can be activated by simply running the following command:

# echo dynpm > /sys/class/drm/card0/device/power_method

Profile-based frequency switching

This method will allow you to select one of the five profiles (described below). Different profiles, for the most part, end up changing the frequency/voltage of the GPU. This method is not as aggressive, but is more stable and flicker free and works with multiple heads active.

To activate the method, run the following command:

# echo profile > /sys/class/drm/card0/device/power_method

Select one of the available profiles:

  • default uses the default clocks and does not change the power state. This is the default behaviour.
  • auto selects between mid and high power states based on the whether the system is on battery power or not.
  • low forces the gpu to be in the low power state all the time. Note that low can cause display problems on some laptops, which is why auto only uses low when monitors are off. Selected on other profiles when the monitors are in the DPMS-off state.
  • mid forces the gpu to be in the mid power state all the time.
  • high forces the gpu to be in the high power state all the time.

As an example, we will activate the low profile (replace low with any of the aforementioned profiles as necessary):

# echo low > /sys/class/drm/card0/device/power_profile

Persistent configuration

The activation described above is not persistent, it will not last when the computer is rebooted. To make it persistent, you can use systemd-tmpfiles (example for #Dynamic frequency switching):

/etc/tmpfiles.d/radeon-pm.conf
w /sys/class/drm/card0/device/power_method - - - - dynpm

Alternatively, you may use this udev rule instead (example for #Profile-based frequency switching):

/etc/udev/rules.d/30-radeon-pm.rules
KERNEL=="dri/card0", SUBSYSTEM=="drm", DRIVERS=="radeon", ATTR{device/power_method}="profile", ATTR{device/power_profile}="low"
Note: If the above rule is failing, try removing the dri/ prefix.

Graphical tools

  • Radeon-tray — A small program to control the power profiles of your Radeon card via systray icon. It is written in PyQt4 and is suitable for non-Gnome users.
https://github.com/StuntsPT/Radeon-tray || radeon-trayAUR
  • power-play-switcher — A gui for changing powerplay setting of the open source driver for ati radeon video cards.
https://code.google.com/p/power-play-switcher/ || power-play-switcherAUR[broken link: archived in aur-mirror]
  • Gnome-shell-extension-Radeon-Power-Profile-Manager — A small extension for Gnome-shell that will allow you to change the power profile of your radeon card when using the open source drivers.
https://github.com/StuntsPT/shell-extension-radeon-power-profile-manager || gnome-shell-extension-radeon-ppmAUR[broken link: archived in aur-mirror] gnome-shell-extension-radeon-power-profile-manager-gitAUR[broken link: archived in aur-mirror]

Other notes

To view the speed that the GPU is running at, perform the following command and you will get something like this output:

# cat /sys/kernel/debug/dri/0/radeon_pm_info
  state: PM_STATE_ENABLED
  default engine clock: 300000 kHz
  current engine clock: 300720 kHz
  default memory clock: 200000 kHz

It depends on which GPU line yours is, however. Along with the radeon driver versions, kernel versions, etc. So it may not have much/any voltage regulation at all.

Thermal sensors are implemented via external i2c chips or via the internal thermal sensor (rv6xx-evergreen only). To get the temperature on asics that use i2c chips, you need to load the appropriate hwmon driver for the sensor used on your board (lm63, lm64, etc.). The drm will attempt to load the appropriate hwmon driver. On boards that use the internal thermal sensor, the drm will set up the hwmon interface automatically. When the appropriate driver is loaded, the temperatures can be accessed via lm_sensors tools or via sysfs in /sys/class/hwmon.

Fan Speed

While the power saving features above should handle fan speeds quite well, some cards may still be too noisy in their idle state. In this case, and when your card supports it, you can change the fan speed manually.

Note:
  • Keep in mind that the following method sets the fan speed to a fixed value, hence it will not adjust with the stress of your gpu, which can lead to overheating under heavy load.
  • Better check your gpu temperature when applying lower than standard values.

First, issue the following command to enable the manual adjustment of the fan speed of your graphics card (or your first gpu in case of a multi gpu setup).

# echo 1 > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1_enable

Then set your desired fan speed from 0 to 255, which corresponds to 0-100% fan speed (The following command sets it to roughly 20%).

# echo 55 > /sys/class/drm/card0/device/hwmon/hwmon2/pwm1

For persistence, use systemd-tmpfiles as shown above by the example with power profiles.

If a fixed value isn't desired, there are possibilities to define a custom fan curve manually by, for example, writing a script in which fan speeds are set depending on the current temperature (current value in /sys/class/drm/card0/device/hwmon/hwmon2/temp1_input), preferably with hystereses. There is also a gui solution: http://github.com/marazmista/radeon-profileradeon-profile-gitAUR.

TV out

First, check that you have an S-video output: xrandr should give you something like

Screen 0: minimum 320x200, current 1024x768, maximum 1280x1200
...
S-video disconnected (normal left inverted right x axis y axis)

Now we should tell Xorg that it is actually connected (it is, right?)

xrandr --output S-video --set "load detection" 1

Setting TV standard to use:

xrandr --output S-video --set "tv standard" ntsc

Adding a mode for it (currently supports only 800x600):

xrandr --addmode S-video 800x600

Clone mode:

xrandr --output S-video --same-as VGA-0

Now let us try to see what we have:

xrandr --output S-video --mode 800x600

At this point you should see a 800x600 version of your desktop on your TV.

To disable the output, do

xrandr --output S-video --off

Also you may notice that the video is being played on monitor only and not on the TV. Where the Xv overlay is sent is controlled by XV_CRTC attribute.

To send the output to the TV, do:

xvattr -a XV_CRTC -v 1
Note: you need to install xvattrAUR[broken link: archived in aur-mirror] to execute this command.

To switch back to the monitor, I change this to 0. -1 is used for automatic switching in dualhead setups.

Please see Enabling TV-Out Statically for how to enable TV-out in your xorg configuration file.

Force TV-out in KMS

The kernel can recognize video= parameter in following form (see KMS for more details):

video=<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]

For example:

video=DVI-I-1:1280x1024-24@60e

Parameters with whitespaces must be quoted:

"video=9-pin DIN-1:1024x768-24@60e"

Current mkinitcpio implementation also requires # in front. For example:

root=/dev/disk/by-uuid/d950a14f-fc0c-451d-b0d4-f95c2adefee3 ro quiet radeon.modeset=1 security=none # video=DVI-I-1:1280x1024-24@60e "video=9-pin DIN-1:1024x768-24@60e"
  • Grub can pass such command line as is.
  • Lilo needs backslashes for doublequotes (append # \"video=9-pin DIN-1:1024x768-24@60e\")
  • Grub2: TODO

You can get list of your video outputs with following command:

$ ls -1 /sys/class/drm/ | grep -E '^card[[:digit:]]+-' | cut -d- -f2-

HDMI audio

HDMI audio is supported in the xf86-video-ati video driver. If you are using a kernel 3.x older than 3.13, HDMI audio is disabled by default because it can be problematic. To enable HDMI audio add radeon.audio=1 to your kernel parameters.

If there is no video after boot up, the driver option has to be disabled.

Note:

Multihead setup

Using the RandR extension

See Multihead#RandR how to setup multiple monitors by using RandR.

Independent X screens

Independent dual-headed setups can be configured the usual way. However you might want to know that the radeon driver has a "ZaphodHeads" option which allows you to bind a specific device section to an output of your choice:

/etc/X11/xorg.conf.d/20-radeon.conf
Section "Device"
  Identifier "Device0"
  Driver "radeon"
  Option "ZaphodHeads" "VGA-0"
  VendorName "ATI"
  BusID "PCI:1:0:0"
  Screen 0
EndSection

This can be a life-saver, when using videocards that have more than two outputs. For instance one HDMI out, one DVI, one VGA, will only select and use HDMI+DVI outputs for the dual-head setup, unless you explicitly specify "ZaphodHeads" "VGA-0".

Turn vsync off

The radeon driver will enable vsync by default, which is perfectly fine except for benchmarking. To turn it off, create ~/.drirc (or edit it if it already exists) and add the following section:

~/.drirc
<driconf>
    <device screen="0" driver="dri2">
        <application name="Default">
            <option name="vblank_mode" value="0" />
        </application>
    </device>
    <!-- Other devices ... -->
</driconf>

Make sure the driver is dri2, not your video card code (like r600).

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: If the above does not work, please file a bug report. Also, why is the SwapbuffersWait option relevant here? (Discuss in Talk:ATI#)

If vsync is still enabled, you can try to disable it by editing the xf86-video-ati configuration :

/etc/X11/xorg.conf.d/20-radeon.conf
Section "Device"
	Identifier  "My Graphics Card"
	Driver	"radeon"
	Option	"EXAVSync" "off"
	Option "SwapbuffersWait" "false" 
EndSection

Troubleshooting

Artifacts upon logging in

If encountering artifacts, first try starting X without /etc/X11/xorg.conf. Recent versions of Xorg are capable of reliable auto-detection and auto-configuration for most use cases. Outdated or improperly configured xorg.conf files are known to cause trouble.

In order to run without a configuration tile, it is recommended that the xorg-input-drivers package group be installed.

You may as well try disabling EXAPixmaps in /etc/X11/xorg.conf.d/20-radeon.conf:

Section "Device"
    Identifier "Radeon"
    Driver "radeon"
    Option "EXAPixmaps" "off"
EndSection

Adding undetected resolutions

Please see the Xrandr page.

AGP is disabled (with KMS)

If you experience poor performance and dmesg shows something like this

[drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19

then check if the agp driver for your motherboard (e.g., via_agp, intel_agp etc.) is loaded before the radeon module, see Enabling KMS.

TV showing a black border around the screen

When I connected my TV to my Radeon HD 5770 using the HDMI port, the TV showed a blurry picture with a 2-3cm border around it. This is not the case when using the proprietary driver. However, this protection against overscanning (see Wikipedia:Overscan) can be turned off using xrandr:

xrandr --output HDMI-0 --set underscan off

Black screen with mouse cursor on resume from suspend in X

Waking from suspend on cards with 32MB or less can result in a black screen with a mouse pointer in X. Some parts of the screen may be redrawn when under the mouse cursor. Forcing EXAPixmaps to "enabled" in /etc/X11/xorg.conf.d/20-radeon.conf may fix the problem. See performance tuning for more information.

No desktop effects in KDE4 with X1300 and Radeon driver

A bug in KDE4 may prevent an accurate video hardware check, thereby deactivating desktop effects despite the X1300 having more than sufficient GPU power. A workaround may be to manually override such checks in KDE4 configuration files /usr/share/kde-settings/kde-profile/default/share/config/kwinrc and/or .kde/share/config/kwinrc.

Add:

DisableChecks=true

To the [Compositing] section. Ensure that compositing is enabled with:

Enabled=true

Black screen and no console, but X works in KMS

This is a solution to the no-console problem that might come up, when using two or more ATI cards on the same PC. Fujitsu Siemens Amilo PA 3553 laptop for example has this problem. This is due to fbcon console driver mapping itself to the wrong framebuffer device that exists on the wrong card. This can be fixed by adding this to the kernel boot line:

fbcon=map:1

This will tell the fbcon to map itself to the /dev/fb1 framebuffer dev and not the /dev/fb0, that in our case exists on the wrong graphics card. If that does not fix your problem, try booting with

fbcon=map:0

instead.

2D performance (e.g. scrolling) is slow

If you're having problems with 2D performance, like scrolling in terminal or browser, you might need to add Option "MigrationHeuristic" "greedy" into the "Device" section of your xorg.conf file.

Note: This only applies to EXA.

Below is a sample configuration file /etc/X11/xorg.conf.d/20-radeon.conf:

Section "Device"
        Identifier  "My Graphics Card"
        Driver  "radeon"
        Option  "MigrationHeuristic"  "greedy"
EndSection

Monitor rotation works for cursor but not windows/content

Users with newer graphics boards who have enabled EXA instead of glamor may find that rotating their monitor with xrandr causes the cursor and monitor dimensions to rotate, but windows and other content stay in their normal orientation. Additionally, the cursor moves according to normal rotation when the user moves the mouse. Look for the following line in your /var/log/Xorg.0.log when you issue the xrandr rotate command:

(EE) RADEON(0): Rotation requires acceleration!

Acceleration is disabled when using EXA on newer graphics cards (source: comment 17). You must choose between enabling EXA (detailed above in the glamor section) and the ability to rotate.

ATI X1600 (RV530 series) 3D application show black windows

There are three possible solutions:

  • Try adding pci=nomsi to your boot loader Kernel parameters.
  • If this does not work, you can try adding noapic instead of pci=nomsi.
  • If none of the above work, then you can try running vblank_mode=0 glxgears or vblank_mode=1 glxgears to see which one works for you, then install driconf and set that option in ~/.drirc.

Cursor corruption after coming out of sleep

If the cursor becomes corrupted like it's repeating itself vertically after the monitor(s) comes out of sleep, set "SWCursor" "True" in the "Device" section of the 20-radeon.conf configuration file.

DisplayPort stays black on multimonitor mode

Try booting with the kernel parameter radeon.audio=0.

Low 2D performance in console and X

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: This disables Power Management that may result in overheating and/or damaging the GPU. (Discuss in Talk:ATI#)

Since kernel 4.1.4, dpm is broken on certain R9 270X cards (chip device number 6810, subsystem 174b:e271, shown as Curacao XT, PC Partner Limited / Sapphire Technology Device e271 in lspci). The regression is caused by a fix for cards with the same PCI ids. Disabling dpm (add radeon.dpm=0 to the kernel parameters) solves the problem.