https://wiki.archlinux.org/api.php?action=feedcontributions&user=Paulw&feedformat=atomArchWiki - User contributions [en]2024-03-28T20:31:35ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=ATI&diff=252077ATI2013-03-27T10:33:28Z<p>Paulw: added info about southern island chipsets</p>
<hr />
<div>[[Category:Graphics]]<br />
[[Category:X Server]]<br />
[[cs:ATI]]<br />
[[de:ATI]]<br />
[[es:ATI]]<br />
[[fr:ATI]]<br />
[[it:ATI]]<br />
[[pl:ATI]]<br />
[[ru:ATI]]<br />
[[tr:ATI]]<br />
[[zh-CN:ATI]]<br />
{{Article summary start}}<br />
{{Article summary text|An overview of the open source ATI/AMD video card driver.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|AMD Catalyst}}<br />
{{Article summary wiki|Xorg}}<br />
{{Article summary end}}<br />
<br />
Owners of '''ATI/AMD''' video cards have a choice between AMD's [[AMD Catalyst|proprietary driver]] ({{AUR|catalyst}}) and the open source driver ({{Pkg|xf86-video-ati}}). This article covers the open source driver.<br />
<br />
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.<br />
<br />
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).<br />
<br />
==Naming conventions==<br />
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 &ndash; including the RV515, RV530, R520, and R580 cores).<br />
<br />
For a table of core and product series, see [[Wikipedia:Comparison of AMD graphics processing units]].<br />
<br />
==Overview==<br />
The {{ic|xf86-video-ati}} (radeon) driver:<br />
*Works with Radeon chipsets up to HD 6xxx and 7xxxM (latest Northern Islands chipsets).<br />
**Radeons in the HD 77xx (Southern Islands) series are partially supported. Check the [http://www.x.org/wiki/RadeonFeature feature matrix] for unsupported features.<br />
**Radeons up to the X1xxx series are fully supported, stable, and full 2D and 3D acceleration are provided.<br />
**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.<br />
*Supports DRI1, RandR 1.2/1.3, EXA acceleration and [[KMS|kernel mode-setting]]/DRI2 (with the latest Linux kernel, libdrm and Mesa versions).<br />
<br />
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 consider the proprietary '''catalyst''' driver.<br />
<br />
{{Note|'''xf86-video-ati''' is specified as '''''radeon''''' for the kernel and in {{ic|xorg.conf}}. }}<br />
<br />
==Installation==<br />
If Catalyst/{{ic|fglrx}} has been previously installed, see [[ATI Catalyst#Uninstallation|here]].<br />
<br />
<br />
=== Installing xf86-video-ati ===<br />
[[pacman|Install]] {{Pkg|xf86-video-ati}}, available in the [[Official Repositories]]. <br />
<br />
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]].<br />
<br />
==Configuration==<br />
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.<br />
<br />
If you want manual configuration, create {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}}, and add the following:<br />
<br />
Section "Device"<br />
Identifier "Radeon"<br />
Driver "radeon"<br />
EndSection<br />
<br />
Using this section, you can enable features and tweak the driver settings.<br />
<br />
== Kernel mode-setting (KMS) ==<br />
<br />
{{Tip|If you have problems with the resolution, check [[Kernel_Mode_Setting#Forcing_modes_and_EDID|this page]].}}<br />
<br />
[[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.<br />
<br />
KMS for ATI video cards requires the [[Xorg]] free video user space driver {{Pkg|xf86-video-ati}} version 6.12.4 or later.<br />
<br />
=== Enabling KMS ===<br />
<br />
{{Note| Since Linux kernel v.2.6.33, KMS is '''enabled''' by default for autodetected ATI/AMD cards. This section remains for configurations outside stock. }}<br />
<br />
==== Early KMS start ====<br />
<br />
''These two methods will start KMS as early as possible in the [[boot process]].''<br />
<br />
1. The earliest point is to append the kernel line in your bootloader with {{ic|1= radeon.modeset=1}}. See your bootloader's page for info on how to do this.<br />
* Remove all {{ic|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader [[Boot Loader#Configuration files|configuration file]]. Using other framebuffer drivers (such as {{ic|[[uvesafb]]}} or {{ic|radeonfb}}) will conflict with KMS. <br />
* 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).<br />
<br />
2. Otherwise, when the [[initramfs]] is loaded:<br />
* If you have a special kernel outside of stock {{ic|-ARCH}} (e.g. linux-zen), remember to use a separate ''mkinitcpio'' configuration file (e.g. {{ic|/etc/mkinitcpio-zen.conf}}) and not {{ic|/etc/mkinitcpio.conf}}.<br />
* Remove any framebuffer related modules from your ''mkinitcpio'' file.<br />
* Add {{ic|radeon}} to {{ic|MODULES}} array in your ''mkinitcpio'' file. 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.<br />
* Re-generate your [[mkinitcpio#Image_creation_and_activation | initramfs]].<br />
<br />
Finally, '''Reboot''' the system.<br />
<br />
==== Late start ====<br />
<br />
''With this choice, KMS will be enabled when modules are loaded during the [[boot process]].''<br />
<br />
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}}).<br />
{{Note| For AGP support, it may be necessary to add {{ic|intel_agp}}, {{ic|ali_agp}}, {{ic|ati_agp}}, {{ic|amd_agp}}, or {{ic|amd64_agp}}) to appropriate .conf files in {{ic|/etc/modules-load.d}}.}}<br />
<br />
# Remove all {{ic|<nowiki>vga=</nowiki>}} options from the ''kernel'' line in the bootloader [[Boot Loader#Configuration files|configuration file]]. 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.<br />
# Add {{ic|<nowiki>options radeon modeset=1</nowiki>}} to {{ic|/etc/modprobe.d/modprobe.conf}}. <br />
# '''Reboot''' the system.<br />
<br />
=== Troubleshooting KMS ===<br />
<br />
==== Disable KMS ====<br />
<br />
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.<br />
<br />
# Add {{ic|<nowiki>radeon.modeset=0</nowiki>}} (or {{ic|nomodeset}}, if this does not work) to the kernel options line in the bootloader [[Boot Loader#Configuration files|configuration file]]. 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.<br />
# If {{ic|radeon}} was added to the {{ic|MODULES}} array in {{ic|mkinitcpio.conf}} to enable ''early start'', remove it.<br />
# Rebuild the [[initramfs]] with {{bc|# mkinitcpio -p linux}}<br />
<br />
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:<br />
<br />
{{hc|/etc/modprobe.d/radeon.conf|2=options radeon modeset=0}}<br />
<br />
==== Renaming {{ic|xorg.conf}} ====<br />
<br />
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.<br />
<br />
== Performance tuning ==<br />
The following options apply to {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}.<br />
<br />
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.<br />
<br />
Option "AGPMode" "8"<br />
<br />
'''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<br />
<br />
Option "ColorTiling" "on"<br />
<br />
'''Acceleration architecture'''; this will work only on '''newer''' cards. If you enable this and then cannot get back into X, remove it. <br />
<br />
Option "AccelMethod" "EXA"<br />
<br />
'''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.<br />
<br />
Option "EnablePageFlip" "on"<br />
<br />
'''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.<br />
<br />
Option "AGPFastWrite" "yes"<br />
<br />
'''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.<br />
Really useful when enabling Xv overlay on videos on a 3D accelerated desktop. It is not necessary when KMS (thus DRI2 acceleration) is enabled.<br />
<br />
Option "EXAVSync" "yes"<br />
<br />
Bellow is a sample config file {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:<br />
<br />
{{bc|<br />
Section "Device"<br />
Identifier "My Graphics Card"<br />
Option "AGPMode" "8" #not used when KMS is on<br />
Option "AGPFastWrite" "off" #could cause instabilities enable it at your own risk<br />
Option "SWcursor" "off" #software cursor might be necessary on some rare occasions, hence set off by default<br />
Option "EnablePageFlip" "on" #supported on all R/RV/RS4xx and older hardware and set off by default<br />
Option "AccelMethod" "EXA" #valid options are XAA, EXA and Glamor. EXA is the default.<br />
Option "RenderAccel" "on" #enabled by default on all radeon hardware<br />
Option "ColorTiling" "on" #enabled by default on RV300 and later radeon cards.<br />
Option "EXAVSync" "off" #default is off, otherwise on. Only works '''if EXA activated'''<br />
Option "EXAPixmaps" "on" #when on icreases 2D performance, but may also cause artifacts on some old cards. Only works '''if EXA activated'''<br />
Option "AccelDFS" "on" #default is off, read the radeon manpage for more information<br />
EndSection<br />
}}<br />
<br />
Defining the '''gartsize''', if not autodetected, can be done by adding {{ic|1=radeon.gartsize=32}} into [[kernel parameters]]. Size is in megabytes and 32 is for RV280 cards.<br />
<br />
Alternatively, do it with a modprobe option in {{ic|/etc/modprobe.d/radeon.conf}}:<br />
<br />
options radeon gartsize=32<br />
<br />
'''For further information and other options, read the radeon manpage and the module's info page''':<br />
man radeon<br />
<br />
modinfo radeon<br />
<br />
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).<br />
<br />
=== Activate PCI-E 2.0 ===<br />
Can be unstable with some motherboards or not produce any performarce, test yourself adding "radeon.pcie_gen2=1" on the kernel command line.<br />
<br />
{{Note|As of kernel 3.6, PCI-E v2.0 in '''radeon''' appears to be turned on by default.}}<br />
<br />
More info on [http://www.phoronix.com/scan.php?page=article&item=amd_pcie_gen2&num=1 Phoronix article]<br />
<br />
=== Glamor ===<br />
With the newest version of the free ATI drivers, you can now use a novel AccelMethod called "glamor": it is a 2D acceleration method implemented through OpenGL, and it should work with graphic cards whose driver are newer or equal to R300.<br />
Option "AccelMethod" "glamor"<br />
<br />
However, you need to add the following section before:<br />
{{bc|<br />
Section "Module"<br />
Load "dri2"<br />
Load "glamoregl" <br />
EndSection<br />
}}<br />
<br />
==Powersaving==<br />
<br />
The powersaving part is totally different with and without KMS.<br />
<br />
===With KMS enabled===<br />
<br />
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.<br />
<br />
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.<br />
<br />
There are two ways to enable power management:<br />
<br />
#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.<br />
#Use the (unsupported) [radeon] repo:<br />
<br />
This repository will grant you up-to-date packages of the radeon driver and its dependencies, from (mostly) git snapshots.<br />
<br />
{{bc|1=<br />
[mesa-git]<br />
Server = <nowiki>http://pkgbuild.com/~lcarlier/$repo/$arch/</nowiki><br />
}}<br />
<br />
<br />
You can select the methods via sysfs.<br />
<br />
With root access, you have two choices:<br />
<br />
1. '''Dynamic frequency switching (depending on GPU load)'''<br />
<br />
{{bc|# echo dynpm > /sys/class/drm/card0/device/power_method}}<br />
<br />
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.<br />
<br />
{{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.}}<br />
<br />
2. '''Profile-based frequency switching'''<br />
<br />
{{bc|# echo profile > /sys/class/drm/card0/device/power_method}}<br />
<br />
The "profile" mode will allow you to select one of the five profiles below.<br />
Different profiles, for the most part, end up changing the frequency/voltage of the card.<br />
<br />
* "default" uses the default clocks and does not change the power state. This is the default behavior.<br />
* "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.<br />
* "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.<br />
* "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.<br />
* "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.<br />
<br />
So lets say we want the "low" option...for this, run the following command:<br />
<br />
{{bc|# echo low > /sys/class/drm/card0/device/power_profile}}<br />
<br />
Replace "low" with any of the aforementioned profiles as necessary.<br />
<br />
{{Tip|Echoing a profile value to this file is not permanent, so when you find something that fits your needs, you can use [[Systemd#Temporary files|tmpfiles.d]] or following [[udev]] rule:}}<br />
'''dynpm'''-method example:<br />
{{hc|$ cat /etc/udev/rules.d/30-local.rules|<nowiki><br />
KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="radeon", ATTR{device/power_method}="dynpm"<br />
</nowiki>}}<br />
'''auto'''-profile example:<br />
{{hc|$ cat /etc/udev/rules.d/30-local.rules|<nowiki><br />
KERNEL=="card0", SUBSYSTEM=="drm", DRIVERS=="radeon", ATTR{device/power_method}="profile", ATTR{device/power_profile}="auto"<br />
</nowiki>}}<br />
<br />
{{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. The extension is now available in the [https://aur.archlinux.org/packages/gnome-shell-extension-radeon-power-profile-manager-git/ AUR] and will default to the mid profile at startup.}}<br />
<br />
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).<br />
<br />
To view the speed that the GPU is running at, perform the following command and you will get something like this output:<br />
<br />
{{hc|$ cat /sys/kernel/debug/dri/0/radeon_pm_info|<nowiki> state: PM_STATE_ENABLED<br />
default engine clock: 300000 kHz<br />
current engine clock: 300720 kHz<br />
default memory clock: 200000 kHz</nowiki>}}<br />
<br />
If /sys/kernel/debug is empty, run this command:<br />
<br />
{{bc|# mount -t debugfs none /sys/kernel/debug}}<br />
<br />
To permanently mount, add the following line to /etc/fstab:<br />
<br />
debugfs /sys/kernel/debug debugfs defaults 0 0<br />
<br />
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.<br />
<br />
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 .<br />
<br />
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]).<br />
<br />
===Without KMS===<br />
<br />
In your {{ic|xorg.conf}} file, add 2 lines to "Device" Section:<br />
Option "DynamicPM" "on"<br />
Option "ClockGating" "on"<br />
<br />
If the two options are enabled successfully, you will see following lines in /var/log/Xorg.0.log:<br />
<br />
(**) RADEON(0): Option "ClockGating" "on"<br />
(**) RADEON(0): Option "DynamicPM" "on"<br />
<br />
Static power management enable success<br />
(II) RADEON(0): Dynamic Clock Gating Enabled<br />
(II) RADEON(0): Dynamic Power Management Enabled<br />
<br />
If you desire low power cost, you can add an extra line to "Device" Section of {{ic|xorg.conf}}:<br />
Option "ForceLowPowerMode" "on"<br />
<br />
==TV out==<br />
{{out of date}}<br />
Since August 2007, there is TV-out support for all Radeons with integrated TV-out.<br />
<br />
It is somewhat limited for now, it does not always autodetect the output correctly and only NTSC mode works.<br />
<br />
First, check that you have an S-video output: {{ic|xrandr}} should give you something like<br />
Screen 0: minimum 320x200, current 1024x768, maximum 1280x1200<br />
...<br />
S-video disconnected (normal left inverted right x axis y axis)<br />
<br />
Setting tv standard to use:<br />
xrandr --output S-video --set "tv standard" ntsc<br />
<br />
Adding a mode for it (currently it supports only 800x600):<br />
xrandr --addmode S-video 800x600<br />
<br />
I will go for a clone mode:<br />
xrandr --output S-video --same-as VGA-0<br />
<br />
So far so good. Now let us try to see what we have:<br />
xrandr --output S-video --mode 800x600<br />
<br />
At this point you should see a 800x600 version of your desktop on your TV.<br />
<br />
To disable the output, do<br />
xrandr --output S-video --off<br />
<br />
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.<br />
<br />
To send the output to the TV, I do<br />
xvattr -a XV_CRTC -v 1<br />
<br />
{{Note| you need to install '''xvattr''' from [[AUR]] to execute this command.}}<br />
<br />
To switch back to my monitor, I change this to {{ic|0}}. {{ic|-1}} is used for automatic switching in dualhead setups.<br />
<br />
Please see [http://www.x.org/wiki/radeonTV Enabling TV-Out Statically] for how to enable TV-out in your xorg configuration file.<br />
<br />
=== Force TV-out in KMS ===<br />
<br />
Kernel can recognize {{ic|1=video=}} parameter in following form:<br />
<br />
video=<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]<br />
<br />
(see [[KMS]])<br />
<br />
For example:<br />
<br />
video=DVI-I-1:1280x1024-24@60e<br />
or<br />
"video=9-pin DIN-1:1024x768-24@60e"<br />
<br />
Parameters with whitespaces must be quoted. Current mkinitcpio implementation also requires # before. For example:<br />
<br />
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"<br />
<br />
* Grub can pass such command line as is.<br />
* Lilo needs backslashes for doublequotes (append="...... # .... \"video=9-pin DIN-1:1024x768-24@60e\"")<br />
* Grub2: TODO<br />
<br />
You can get list of your video outputs with following command:<br />
<br />
{{bc|<nowiki>ls -1 /sys/class/drm/ | grep -E '^card[[:digit:]]+-' | cut -d- -f2-</nowiki>}}<br />
<br />
== HDMI Audio ==<br />
<br />
'''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 {{ic|xrandr}} to enable the output and Test as described below.<br />
<br />
=== Testing HDMI Audio ===<br />
# Connect your PC to the Display via HDMI cable.<br />
# Use xrandr to get picture to the Display, e.g.: {{ic|xrandr --output DVI-D_1 --mode 1280x768 --right-of PANEL}}. Simply typing {{ic|xrandr}} will give you a list of valid outputs.<br />
# Run {{ic|aplay -l}} to get the list of 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]}}<br />
# Try sending sound to this device: {{ic|aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav}}. Be sure to change {{ic|plughw:z,y}} to match the hardware number found with last command. You should be able to hear the test sound from the display.<br />
<br />
* The audio module is disabled by default in kernel >=3.0. Add {{ic|1=radeon.audio=1}} to the [[Kernel parameters]].<br />
* If the sound is distorted try [[PulseAudio#Glitches, skips or crackling|setting {{ic|1=tsched=0}}]] and make sure {{ic|rtkit}} daemon is running.<br />
<br />
== Dual Head Setup ==<br />
=== Independent X Screens ===<br />
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:<br />
Section "Device"<br />
Identifier "Device0"<br />
Driver "radeon"<br />
Option "ZaphodHeads" "VGA-0"<br />
VendorName "ATI"<br />
BusID "PCI:1:0:0"<br />
Screen 0<br />
EndSection<br />
<br />
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"}}.<br />
<br />
Moreover, this option allows you to easily select the screen you want to mark as primary.<br />
<br />
== Enabling video acceleration ==<br />
<br />
Latest {{Pkg|mesa}} package added support for MPEG1/2 decoding to free drivers, exported via {{Pkg|libvdpau}}. After installing it assign environment variable {{Ic|LIBVA_DRIVER_NAME}} to {{Ic|vdpau}} and {{Ic|VDPAU_DRIVER}} to the name of driver core, e.g.:<br />
<br />
{{hc|1=~/.bashrc|2=<br />
export LIBVA_DRIVER_NAME=vdpau<br />
export VDPAU_DRIVER=r600<br />
}}<br />
<br />
for r600-based cards (all available VDPAU drivers are in {{Ic|/usr/lib/vdpau/}}).<br />
<br />
== Troubleshooting ==<br />
<br />
=== Artifacts upon logging in ===<br />
<br />
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.<br />
<br />
In order to run without a configuration tile, it is recommended that the {{ic|xorg-input-drivers}} package group be installed.<br />
<br />
Artifacts may also be related to [[kernel mode setting]]. Consider [[#Disable KMS|disabling KMS]].<br />
<br />
You may as well try disabling {{ic|EXAPixmaps}} in {{ic|/etc/X11/xorg.conf.d/20-radeon.conf}}:<br />
<br />
Section "Device"<br />
Identifier "Radeon"<br />
Driver "radeon"<br />
Option "EXAPixmaps" "off"<br />
EndSection<br />
<br />
Further tweaking could be done by disabling {{ic|AccelDFS}}:<br />
<br />
Option "AccelDFS" "off"<br />
<br />
=== Adding undetected resolutions ===<br />
<br />
e.g. When EDID fails on a DisplayPort connection. <br />
<br />
This issue is covered on the [[Xrandr#Adding_undetected_resolutions|Xrandr page]].<br />
<br />
=== Slow performance with open-source drivers ===<br />
<br />
{{Note|Make sure you are member of '''video''' group.}}<br />
<br />
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:<br />
dmesg | egrep "drm|radeon"<br />
<br />
This command might show something like this, meaning it is trying to default to KMS:<br />
[drm] radeon default to kernel modesetting.<br />
...<br />
[drm:radeon_driver_load_kms] *ERROR* Failed to initialize radeon, disabling IOCTL<br />
<br />
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.<br />
<br />
=== AGP is disabled (with KMS) ===<br />
<br />
If you experience poor performance and dmesg shows something like this<br />
[drm:radeon_agp_init] *ERROR* Unable to acquire AGP: -19<br />
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]].<br />
<br />
=== TV showing a black border around the screen ===<br />
<br />
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:<br />
xrandr --output HDMI-0 --set underscan off<br />
<br />
=== Black screen with mouse cursor on resume from suspend in X ===<br />
<br />
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.<br />
<br />
=== No Desktop Effects in KDE4 with X1300 and Radeon Driver ===<br />
<br />
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}}. <br />
<br />
Add:<br />
DisableChecks=true<br />
<br />
To the [Compositing] section. Ensure that compositing is enabled with:<br />
Enabled=true<br />
<br />
=== Black screen and no console, but X works in KMS ===<br />
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:<br />
fbcon=map:1<br />
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.<br />
<br />
=== Some 3D applications show textures as all black or crash ===<br />
You might need texture compression support, which is not included with the open source driver. Install {{Pkg|libtxc_dxtn}} (and {{Pkg|lib32-libtxc_dxtn}} for multilib systems).<br />
<br />
=== 2D performance (e.g. scrolling) is slow ===<br />
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.<br />
<br />
Bellow is a sample config file {{ic|/etc/X11/xorg.conf.d/'''20-radeon.conf'''}}:<br />
<br />
{{bc|<br />
Section "Device"<br />
Identifier "My Graphics Card"<br />
Driver "radeon"<br />
Option "MigrationHeuristic" "greedy"<br />
EndSection<br />
}}<br />
<br />
=== ATI X1600 (RV530 series) 3D application show black windows ===<br />
There are three possible solutions:<br />
* Try add {{ic|<nowiki>pci=nomsi</nowiki>}} to your boot loader [[Kernel parameters]].<br />
* If this doesn't work, you can try adding {{ic|noapic}} instead of {{ic|<nowiki>pci=nomsi</nowiki>}}.<br />
* 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}}.<br />
<br />
<br />
=== Vertical colored stripes on chipset RS482 (Xpress 200M Series) with/out KMS ===<br />
The bug :With the graphical chipset Xpress 200M Series (Radeon Xpress 1150), booting with KMS gives you sometimes, as soon as Xorg boots, a screen with many vertical colored stripes. You cannot Alt+Sys+K or do anything. Take a look [https://bugs.archlinux.org/task/21918] for more information,<br />
How to fixed ? : disable dri (needn't to disable kms)<br />
Side effert: if i disable "dri" and use no kernel options (no "nomodeset") i see the vertical stripes at boot, only for 5 seconds, before having kdm displayed. Then, i have the same results.<br />
If I start for example KDE Desktop Effects, i will see again the vertical stripes for 5 seconds...and return to kdm ! :)</div>Paulw