Difference between pages "Template:Infobox software/Doc" and "Package:AMD Catalyst Video Drivers"

(Difference between pages)
m (Removed cite web unexisting template)
 
 
Line 1: Line 1:
 +
{{Ebuild
 +
|Summary=Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.
 +
|CatPkg=x11-drivers/ati-drivers
 +
|Maintainer=Drobbins
 +
|Homepage=
 +
|Repository=Funtoo Overlay
 +
|Overlay=Funtoo
 +
}}
 +
 +
{{Important|Version 14.12-r3 and above now include ATI GLESv2 and EGL libraries, which should improve stabilty with GNOME.}}
 +
 +
<tt>x11-drivers/ati-drivers</tt> (often referred to as "<tt>fglrx</tt>", the name of its kernel module) is the proprietary, accelerated driver for AMD (ATI) graphics cards.
 +
 +
=== Preparing to Install ===
 +
 +
==== Default Kernel ====
 +
 +
If you are using the default kernel -- one like debian-sources that was built automatically, then you'll want to blacklist a few modules to prevent them from loading and interfering with the AMD Catalyst module. To avoid having the open source Radeon drivers automatically load and ruin your day, create a blacklist file as follows:
  
== Usage ==
+
{{file|name=/etc/modprobe.d/radeon.conf|desc=Prevent open source DRM and radeon drivers from loading|body=
<pre style="overflow:auto;">
+
blacklist radeon
{{Infobox software
+
blacklist drm
| name                   =  
+
| title                  =
+
| logo                  = <!-- [[File: ]] -->
+
| screenshot            = <!-- [[File: ]] -->
+
| caption                =
+
| collapsible            =
+
| author                =
+
| developer              =
+
| released              = <!-- {{Start date|YYYY|MM|DD|df=yes/no}} -->
+
| discontinued          =  
+
| latest release version =  
+
| latest release date    = <!-- YYYY-MM-DD -->
+
| latest preview version =
+
| latest preview date    = <!-- YYYY-MM-DD -->
+
| frequently updated    = <!-- DO NOT include this parameter unless you know what it does -->
+
| programming language  =
+
| operating system      =
+
| platform              =
+
| size                  =
+
| language              =
+
| status                =
+
| genre                  =
+
| license                =
+
| website                = example.org
+
 
}}
 
}}
</pre>
 
  
 +
==== Custom Kernel ====
  
== Example ==
+
If you are building a custom kernel, rather than blacklisting modules as above, you can simply ensure that the Direct Rendering Manager and in-kernel Radeon drivers are not enabled. If you do build them as modules, you will need to blacklist them as above. Also ensure that the following kernel options are enabled.
<div class="dablink">The following example is captured on 1 September 2010 from [[GIMP]] article and is include '''only with the purpose serving as an example.''' Information included in this example infobox are therefore bound to become obsolete as the time passes. Images in this example are published under free licenses.</div>
+
 
{{Infobox software
+
{{kernelop|desc=
| name                  = GIMP
+
[*] Enable loadable module support
| logo                  = [[File:The GIMP icon - gnome.svg|64px|Wilber, The GIMP mascot]]
+
Processor type and features --->
| screenshot            = [[File:Gimpscreen.png|250px]]
+
      [*] MTRR (Memory Type Range Register) support
| caption                = Screenshot of GIMP 2.6
+
Bus options (PCI etc.) --->
| developer              = The GIMP Development Team
+
      [*] PCI Express Port Bus Support
| released              = 1996
+
       [*] Message Signaled Interrupts (MSI and MSI-X)
| latest preview version = 2.7.1
+
Device Drivers --->
| latest preview date    = 2010-06-29
+
      Graphics support --->
| latest release version = 2.6.10
+
            < > Direct Rendering Manager (xFree86 4.1.0 and higher DRI support) --->
| latest release date    = 2010-07-08
+
| programming language  = [[C (programming language)|C]] and [[GTK+]]
+
| operating system       = [[Linux]], [[Mac OS X]], [[Microsoft Windows]], [[FreeBSD]], [[Solaris (operating system)|Solaris]]
+
| language              = 52 languages in GIMP 2.6, 37 fully translated, others partly translated.[http://www.gimp.org/docs/ GIMP - Documentation][http://l10n.gnome.org/module/gimp/ GNOME GIMP translation statistics, see GIMP 2.6]
+
| status                = Active
+
| genre                  = [[Raster graphics editor]]
+
| license                = [[GNU General Public License]]
+
| website                = www.gimp.org
+
 
}}
 
}}
  
<pre style="overflow:auto;">
+
{{note|If you need support for AGP cards, enable the following kernel options:}}
{{Infobox software
+
{{kernelop|desc=
| name                  = GIMP
+
Device Drivers --->
| logo                  = [[File:The GIMP icon - gnome.svg|64px|Wilber, The GIMP mascot]]
+
      Graphics support --->
| screenshot            = [[File:Gimpscreen.png|250px]]
+
            <*> /dev/agpgart (AGP Support) --->
| caption                = Screenshot of GIMP 2.6
+
                  Select an appropriate AGP driver:
| developer              = The GIMP Development Team
+
                  <*> AMD Opteron/Athlon64 on-CPU GART support
| released              = 1996
+
| latest preview version = 2.7.1
+
| latest preview date    = 2010-06-29
+
| latest release version = 2.6.10
+
| latest release date    = 2010-07-08
+
| programming language  = [[C (programming language)|C]] and [[GTK+]]
+
| operating system      = [[Linux]], [[Mac OS X]], [[Microsoft Windows]], [[FreeBSD]], [[Solaris (operating system)|Solaris]]
+
| language              = 52 languages in GIMP 2.6, 37 fully translated, others partly translated.[http://www.gimp.org/docs/ GIMP - Documentation][http://l10n.gnome.org/module/gimp/ GNOME GIMP translation statistics, see GIMP 2.6]
+
| status                = Active
+
| genre                  = [[Raster graphics editor]]
+
| license                = [[GNU General Public License]]
+
| website                = www.gimp.org
+
 
}}
 
}}
</pre>
 
----
 
  
== Parameters ==
+
=== Editing make.conf ===
All parameters are optional.
+
  
; name: Name of the infobox. Usually, it is used to display the name software product but may be anything, as it used as an internal parameter for use with <code>frequently updated</code> parameter, and "Stable release" / "Preview release" fields. When modifying an article which already has an infobox, be careful not to edit this parameter when <code>frequently updated</code> parameter is set to ''yes''. In such cases, if you want to edit the title at the top of the infobox, use the <code>title</code> parameter instead.
+
Add the following to your <code>/etc/make.conf</code>:
:'''ATTENTION:''' Please do not include a [[Help:Link#Wikilinks|wikilink]], [[hyperlink]] or image in this parameter. This parameter should be composed of pure text.
+
<console>
 +
# ##i##nano /etc/make.conf
 +
VIDEO_CARDS="fglrx"
 +
</console>
  
; title: Name of the software product as displayed above the infobox. When not specified, contents of ''name'' parameter will be displayed instead.
+
=== Enabling AMD Catalyst Control Center ===
:'''Important note:''' Please do not include an image in this field. Wikipedia [[accessibility]] requirements mandates that this field should contain text that can be read by [[screen reader]]s.
+
  
; logo: Code for a small image to be displayed as software product's [[logo]] or [[computer icon]]. The contents of this field should look like:
+
Then, add the following to <code>/etc/portage/package.use</code> if you would like to enable support for AMD Catalyst Control Center:
::<tt>&#91;&#91;File:''File name.ext''{{!}}''Size''px&#93;&#93;</tt>
+
<console>
:Replace ''Filename.ext'' with the name of your image and ''Size'' with width of your image in pixels. For more information regarding use of images and their syntax, please consult: [[Help:Contents/Images and media]].
+
###i## nano /etc/portage/package.use
 +
x11-drivers/ati-drivers qt4
 +
</console>
  
; screenshot: Code for an image to be displayed as software product's [[screenshot]]. The contents of this field should look like:
+
{{Note|If you are using a desktop or workstation profile, this USE flag will be enabled by default.}}
::<tt>&#91;&#91;File:''File name.ext''{{!}}''Size''px&#93;&#93;</tt>
+
:Replace ''Filename.ext'' with the name of your image and ''Size'' with width of your image in pixels. For more information regarding use of images and their syntax, please consult: [[Help:Contents/Images and media]].
+
  
; caption: A caption for screenshot that appears below it. Please include this parameter only when there is an image to display.
+
=== Emerging the package ===
  
; collapsible: Whether this screenshot is by default hidden and is only shown when user clicks on a minuscule "Expand" button. Can be set to "yes". Especially useful in case of long vertical screenshot (see [[QQ]] for example)
+
If you allready have emerged xorg-server, all you need to install the drivers is running the following command:
 +
<console>
 +
###i## emerge -av --changed-use --deep @world
 +
</console>
  
; developer: Name of the current developer of the software product. It can be either an individual or an organization/business.
+
otherwise you may install the drivers with
 +
<console>
 +
###i## emerge -av x11-drivers/ati-drivers
 +
</console>
  
; author: Name of the original author or publisher of the software product. It can be either an individual or an organization/business. Most of the times, it only needs to be specified when <code>developer</code> field is populated.
+
Before using the driver, ensure that the "fglrx" module has been loaded -- run {{c|modprobe fglrx}} as root  -- it should return with no error. If the module can't be found, run {{c|depmod -a}} as root -- then the modprobe command should work. If you are switching from the open source Radeon driver, then shutting down your desktop and rebooting your system (be sure to disable xdm) may be required to get the new "fglrx" module to load cleanly.
  
; released: The date in which version 1.0 (or closely-matching release) of the software product in question reaches its [[Release to manufacturing]] (RTM) stage. In case the article is about a specific major release of a software product (for instance [[Internet Explorer 8]] or [[Microsoft Office 2007]]), this field should contain the date in which that specific major release reached RTM stage. In case the software product is still in development and has not reached its RTM stage, please ignore this field; do not use this field to specify the release date of the first preview/test release of the software product; there is already another parameter for that use.
+
=== Configuring ===
:The content of this field should look like the following:
+
::''year''-''month''-''day''
+
:In case the article uses DMY as date format, use this code instead:
+
::''year''-''month''-''day''
+
:If you are unsure which date format to use, please consult [[WP:MOSDATES]].
+
  
; latest release version: The version number of the latest release of the software product. Please observe the following examples:
+
Next, set ati-drivers to manage the system's OpenGL and OpenCL implementations.  
: Example #1: If the article is about a product called ''Example Software'' whose latest version is 1.5, specify:
+
Doing this is particulary important for desktop environments like GNOME, which use hardware acceleration by default. Not doing this will result in the GNOME display manager not being able to start!
::v1.5
+
: Example #2: If the article is about a product called ''Example Software'' whose latest release is called ''Example Software 2008'' and whose latest version number is 12.2, specify:
+
::2008 (v12.2)
+
: Example #3: If the article is about ''Famous Example Software 2010'', which is a significant release of a product called ''Famous Example Software'' and whose latest version number is 14.0.0.25, just specify:
+
::v14.0.0.25
+
: Example #4: If the article is about ''Famous Example Software 2010'' for which no update is released since its initial release-to-manufacturing (RTM), please omit this parameter unless there is an evidence that it is necessary for the reader to know this number. One reason would be the presence of preview releases of the software product which can only be distinguished from the RTM by their version number.
+
:This parameter and <code>latest release date</code> complement each other but none strictly requires the other.
+
  
; latest release date: The release date of the latest released version. If no update is released for the software since its initial release, please omit this field; filling in the <code>released</code> field would be enough. The content of this field should look like the following:
+
<console>
::''year''-''month''-''day''
+
###i## eselect opengl set ati
:In case the article uses DMY as date format, use this code instead:
+
###i## eselect opencl set amd
::''year''-''month''-''day''
+
</console>
:If you are unsure which date format to use, please consult [[WP:MOSDATES]].
+
:This parameter and <code>latest release version</code> complement each other but none strictly requires the presence of the other.
+
  
; discontinued: Whether this product is no longer being developed, thus changing the phrase "Latest release" in the infobox to "Discontinued". For technical reasons, anything for this parameter has the same effect, be it "yes", "no" or anything else. To nullify the effect of this parameter, you need to omit it.
+
Afterwards, run <code>aticonfig</code> to modify the X-server configuration file to work with the ati-drivers:
 +
<console>
 +
###i## aticonfig --initial
 +
</console>
  
; latest preview version: The version number of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in <code>latest release version</code>) is in progress. Please consult descriptions for <code>latest release version</code> provided above for best practices of specifying this parameter.
+
{{tip|If you would like to have a full-resolution framebuffer with ati-drivers, check out [[uvesafb| uvesafb]]}}
  
; latest preview date: Specifies the release date of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in <code>latest release version</code>) is in progress. Please consult descriptions for <code>latest release date</code> provided above for best practices of specifying this parameter.
+
=== Multi-Head Display ===
  
; frequently updated: Specifies whether the infobox retrieves the software product's latest release version, latest release date, latest preview version and latest preview date from outside the article. Users visiting the article may click the numbers directly in the infobox to edit that external source. This mode is very useful for articles about software products whose vendors keep releasing updates or newer versions. With this mode is enabled, users can quickly and effectively edit the release data without affecting the articles.
+
There are a couple of options for setting up a multi-head display. For some systems, all you need to do is plug in your additional monitor, and it will be detected by your desktop environment, and will work.
:For technical reasons, anything for this parameter has the same effect, be it "yes", "no", "true", "false" or anything else. To nullify the effect of this parameter, you need to omit this parameter or specify nothing for it. Note however, that if any of <code>latest release version</code>, <code>latest release date</code>, <code>latest preview version</code> or <code>latest preview date</code> parameters are specified, external source will be ignored.
+
:To make the infobox retrieve release data from outside the article:
+
#Delete <code>latest release version</code>, <code>latest release date</code>, <code>latest preview version</code> or <code>latest preview date</code> parameters from the infobox.
+
#Save the article.
+
#Create external source that supplies data for latest stable release. To do so:
+
##Copy and paste the following URL into your browser's address bar, replacing ''INFOBOX_NAME'' with the value supplied in <code>name</code> parameter of the infobox: <br/><span class="plainlinks"><code>{{fullurl:Template:Latest stable software release/INFOBOX_NAME|action=edit&preload=Template:LSR/syntax}}</code></span>
+
##In the page that opens, fill in the required information.
+
##Save the page.
+
#Create external source that supplies data for latest preview release. To do so:
+
##Copy and paste the following URL into your browser's address bar, replacing ''INFOBOX_NAME'' with the value suppplied in <code>name</code> parameter of the infobox: <br/><span class="plainlinks"><code>{{fullurl:Template:Latest preview software release/INFOBOX_NAME|action=edit&preload=Template:LPR/syntax}}</code></span>
+
##In the page that opens, fill in the required information.
+
##Save the page.
+
#Refresh the article.
+
  
; programming language: The [[programming language]] of that subject of the article. If the program language of the software product has a corresponding article in Wikipedia, please link to it. Here is an example:
+
If your second monitor does not display anything at all, then play around with your X configuration. Try using the following command to generate a new X config:
::Code: <code><nowiki>[[C++]] and [[C Sharp (programming language)|C#]]</nowiki></code>
+
::Result: [[C++]] and [[C Sharp (programming language)|C#]]
+
:When specifying the name of the programming language please make sure that you [[WP:V|cite your source]]. Unreferenced assertions in Wikipedia may be challenged or removed. If you have a source, do not include this parameter.
+
  
; operating system: The [[operating system]] on which the given software product works. Please be as accurate as possible in specifying this parameter (but also be mindful of the length) and avoid specifying vague phrases such as [[Cross-platform]] (or its redirect, [[Multi-platform]]). Please consider these examples:
+
{{console|body=
:*If the software product works on all incarnations of [[Unix]], [[Linux]] and derived operating systems, please specify:
+
# ##i##aticonfig --initial=dual-head
:**<code><nowiki>[[Unix-like]]</nowiki></code>
+
}}
:*If the software works unconditionally on ALL incarnations of [[Microsoft Windows]], please specify:
+
:**<code><nowiki>[[Microsoft Windows]]</nowiki></code><br/>(Do not specify <code><nowiki>[[Microsoft Windows|Windows]]</nowiki></code>; always write the full name of a registered trademark when no length restriction is imposed upon you.)
+
:*If the software product works only on [[Windows XP]] and all subsequent releases of Microsoft Windows, please specify:
+
:**<code><nowiki>[[Windows XP]] and later</nowiki></code>
+
:*If the software product works only on [[Windows XP]] and all subsequent releases of consumers versions of Microsoft Windows, please specify:
+
:**<code><nowiki>[[Windows XP]], [[Windows Vista]] and [[Windows 7]]</nowiki></code><br/>(At the time of this writing, August 2010, Windows 7 was the latest consumers release of Microsoft Windows.)
+
:*If the software product is released for various families of different operating systems, (such as specific versions of BSD, Linux, Mac OS and Windows) so that listing them in the infobox gives it undue length, please leave the details to article body and specify:
+
:**<code><nowiki>[[BSD]], [[Linux]], [[Mac OS]] and [[Microsoft Windows|Windows]]</nowiki></code>
+
:*If the software is an operating system–independent [[web application]], ignore this parameter.
+
  
; platform: The [[computing platform]] under which the product runs. You might like to include the following information:
+
You can use the {{c|--screen-layout={left|right|above|below}}} option to specify the relationship of the second screen to the first.
:*'''Processor architecture:''' Some software products only run under a certain processor architecture. The most common architectures are [[IA-32]] (also known as ''x86'', ''i386'' and ''32-bit processor''), [[x86-64]] (also known as ''x64'', ''AMD64'', ''EM64T'' and ''64-bit'') and [[Itanium]]. Unfortunately, these information are very technical. Specially, a lot of people do not know that [[x86]] is not the same as [[IA-32]]. For that reason, please consider specifying the following phrases:
+
 
:**For software products that run on IA-32 processors, please specify: '''<code><nowiki>[[IA-32|Intel x86 - 32-bit]]</nowiki></code>''' or '''<code><nowiki>[[IA-32]]</nowiki></code>'''. Do ''not'' specify: <code><nowiki>[[x86]]</nowiki></code> or <code><nowiki>[[32-bit]]</nowiki></code>
+
For more than two heads, or multiple cards, you can use the following approach to generate an appropriate X config. First, list adapters to see what adapters are available:
:**For software products that run on x86-64 processors, please specify: '''<code><nowiki>[[x86-64|x64]]</nowiki></code>'''. Do ''not'' specify: <code><nowiki>[[64-bit]]</nowiki></code>, <code><nowiki>[[AMD64]]</nowiki></code> or <code><nowiki>[[EM64T]]</nowiki></code>
+
 
:*'''Software frameworks:''' Some software products run on [[Java platform]], [[.NET Framework]], [[Adobe Flash]], [[Adobe AIR]], [[Microsoft Silverlight]] or [[XUL]] without regard to the processor architecture. If so, you may ignore processor architecture and instead specify the framework.
+
{{console|body=
:Please avoid specifying vague phrases such as [[Cross-platform]] unless the following conditions meet:
+
# ##i##aticonfig --list-adapters
:#The software product has been released for numerous different platforms, so much so that including all of them causes the infobox size to grow unduly large.
+
}}
:#The article body lists the platforms under which the product runs.
+
 
:If the above do not meet, then specifying such a vague phrase is the same as not specifying it.
+
Now, a variant of one of the following commands to generate an X configuration for your needs:
 +
 
 +
{{console|body=
 +
# ##i##aticonfig --initial --heads=4 --adapter=1
 +
# ##i##aticonfig --adapter=0,2 --initial
 +
# ##i##aticonfig --adapter=all --initial
 +
# ##i##aticonfig --xinerama=on
 +
}}
 +
 
 +
One you have your displays enabled so that your mouse pointer can move to all displays, you still may not be able to drag windows to certain monitors. In this situation, each monitor is probably configured as a separate X screen, and you'll need to use the Catalyst Control Center {{c|amdcccle}} GUI configuration tool to tie them together. The Catalyst Control Center is installed when the {{c|qt4}} USE variable is enabled.
 +
 
 +
Open up a graphical terminal, and become root by typing {{c|su -}} -- your user will need to be in the {{c|wheel}} group to do this:
 +
 
 +
{{console|body=
 +
$ ##i##su -
 +
Password: ##i##*******
 +
# source /etc/profile
 +
# amdcccle
 +
}}
  
; size: Size of the installer package. Only applies to software products that are available via download. For products distributed physically in boxes of packages, ignore this parameter. Do not forget to include your unit of measurements (i.e. Kilobytes, megabytes or gigabytes). Observe the following examples:
+
[[File:amdcccle.png|class=img-responsive|center]]
:*<code><nowiki>760&#x26;nbsp&#x3B;[[Kilobyte|KB]]</nowiki></code> → 760&nbsp;[[Kilobyte|KB]]
+
Navigate to Display Manager, and choose the option {{c|Multi-display desktop with display(s) X}} for each display. Then, drag and drop the blue displays to arrange them to match how they are arranged in front of you. Click {{c|OK}}. The Catalyst Control Center will tell you that you will need to restart your system for the changes to take effect. Simply log out if you are running {{c|xdm}}, or end your X session, and start it up again. You should now have a fully-functioning multi-head display.
:*<code><nowiki>32&#x26;nbsp&#x3B;[[Megabyte|MB]]</nowiki></code> → 32&nbsp;[[Megabyte|MB]]
+
:*<code><nowiki>1.5&#x26;nbsp&#x3B;[[Gigabyte|GB]]</nowiki></code> → 1.5&nbsp;[[Gigabyte|GB]]
+
:'''Note:''' "&#x26;nbsp&#x3B;" generates a non-breaking space. Words connected by this mark won't separate when "word wrapping" occurs.
+
:For more information, visit [[WP:UNITS]]
+
  
; language: Lists the Natural languages in which the software product user interface can interact with user. Please do not supply "Multilingual" or such vague phrases which do not add to the knowledge of the reader. When the list of languages is huge AND when those languages are listed in the article body, please specify number of the supported languages instead. Also please do not wikilink the name of languages: Readers are most likely unwilling to read about those languages.
+
=== Troubleshooting ===
 +
==== I am using a HDMI connection, and my monitor's display has a black border around it. ====
 +
Disable overscan as follows:
  
; status: The development status of the computer program, such as: Planned, Active, Unmaintained, Discontinued, Stalled or [[Abandonware]]
+
<console>
 +
$ ##i##su -
 +
Password: ##i##*********
 +
# ##i##aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
 +
</console>
  
; genre: Type of program.  Should be wikilinked to an article such as [[Geographic information system]]. For more information, consult [[List of software categories]]. Please do not use this field to briefly describe the role and function of the subject of the article. For example, instead of "SVG creator, editor and converter", consider using "[[Vector graphics editor]]". Instead of "PDF creator, editor, converter and viewer", consider using "[[Desktop publishing software]]". Instead of "DWG creator/editor", consider using "[[Computer-aided design]]".
+
You will need to restart your X session for the changes to take effect. If you are using a display manager, logging out and back in again should cause the new settings to be visible.
  
; license: Type of the software license under which the consumer is allowed to use the product. You may specify it in two forms:
+
==== The tabs in Google Chrome are becoming garbled/corrupted ====
:*You may specify a type of well-known license. For example:
+
:**[[Proprietary software|Proprietary]] [[commercial software]] (<code><nowiki>[[Proprietary software|Proprietary]] [[commercial software]]</nowiki></code>): Software products which are licensed for use for a price. Most software today are published under this license type.
+
:**[[Freeware]]: Software products which are licensed for use (and sometimes redistribution) but free of charge.
+
:**[[Free software]]: Software products that can be used, studied, and modified without restriction, and which can be copied and redistributed in modified or unmodified form.
+
:*You may specify a well-known licensing scheme, such as:
+
:**[[GNU General Public License]]
+
:**[[GNU Lesser General Public License]]
+
:**[[BSD License]]
+
:Please avoid specifying phrases that makes no sense to the reader such as "Microsoft EULA", "Adobe End-User License Agreement" or "Symantec Terms of License", etc. (Always bear in mind that you are writing the article for those who do not know about the subject and come to the article to gain knowledge. You are not writing Wikipedia articles for your fellow co-editors who already know!)
+
  
;licence: Same as <code>license</code>. Pick either ''license'' (American English) or ''licence'' (Commonwealth English), not both - select the one which matches the content of the article the template is used in.
+
New versions of Google Chrome use hardware acceleration by default which appears to have rendering issues with AMD's drivers. To work around this, disable hardware acceleration in Google Chrome by going to {{c|Settings}}, {{c|Show advanced settings...}} and then uncheck the {{c|Use hardware acceleration when available (requires Chrome restart)}}. Once Chrome is restarted, the rendering problem should be resolved.
  
; website: Web site of software package. Please make sure that, whenever possible, the significant portion of the website address remains visible. For example, instead of "<code><nowiki>[http://www.example.com Example website]</nowiki></code>", specify "<code><nowiki>[http://www.example.com www.example.com]</nowiki></code>". You can also specify "<code><nowiki>http://www.example.com</nowiki></code>". The URL template will automatically generate compatible code.
+
==== Compton with backend glx does not work well with ati-drivers ====
 +
Try running compton with the following switches:
 +
<console>
 +
###i## compton --backend glx --vsync none --paint-on-overlay
 +
</console>
  
{{delete}}
+
[[Category:Video Cards]]
 +
[[Category:First Steps]]
 +
{{EbuildFooter}}

Revision as of 17:42, February 22, 2015

x11-drivers/ati-drivers


Current Maintainer(s):Daniel Robbins
Source Repository:Funtoo Overlay

Summary: Accelerated ATI/AMD binary drivers for Radeon HD 5000 and newer chipsets.

Use Flags

qt4
Install qt4 dependent optional tools (e.g Catalyst Control Panel)
modules
Build the kernel modules
disable-watermark
Do a potentially dangerous binary search and replace to disable watermark
pax_kernel
Enable pax kernel specific patches
vaapi
Enabled Video Acceleration API

News

Mgorny

New OpenGL management in Funtoo

Funtoo is switching to an improved system for managing multiple OpenGL providers (Mesa/Xorg, AMD and nVidia). The update may involve blockers and file collisions.
30 March 2015 by Mgorny
Drobbins

Subarch Profiles are coming...

Subarch profiles are on their way! Learn more here.
29 March 2015 by Drobbins
Drobbins

RSS/Atom Support

You can now follow this news feed at http://www.funtoo.org/news/atom.xml .
10 February 2015 by Drobbins
View More News...

AMD Catalyst Video Drivers

Tip

This is a wiki page. To edit it, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.


Important

Version 14.12-r3 and above now include ATI GLESv2 and EGL libraries, which should improve stabilty with GNOME.

x11-drivers/ati-drivers (often referred to as "fglrx", the name of its kernel module) is the proprietary, accelerated driver for AMD (ATI) graphics cards.

Preparing to Install

Default Kernel

If you are using the default kernel -- one like debian-sources that was built automatically, then you'll want to blacklist a few modules to prevent them from loading and interfering with the AMD Catalyst module. To avoid having the open source Radeon drivers automatically load and ruin your day, create a blacklist file as follows:

/etc/modprobe.d/radeon.conf - Prevent open source DRM and radeon drivers from loading
blacklist radeon
blacklist drm

Custom Kernel

If you are building a custom kernel, rather than blacklisting modules as above, you can simply ensure that the Direct Rendering Manager and in-kernel Radeon drivers are not enabled. If you do build them as modules, you will need to blacklist them as above. Also ensure that the following kernel options are enabled.


[*] Enable loadable module support
Processor type and features --->
      [*] MTRR (Memory Type Range Register) support
Bus options (PCI etc.) --->
      [*] PCI Express Port Bus Support
      [*] Message Signaled Interrupts (MSI and MSI-X)
Device Drivers --->
      Graphics support --->
            < > Direct Rendering Manager (xFree86 4.1.0 and higher DRI support) --->
Note

If you need support for AGP cards, enable the following kernel options:

Device Drivers --->
      Graphics support --->
            <*> /dev/agpgart (AGP Support) --->
                  Select an appropriate AGP driver:
                  <*> AMD Opteron/Athlon64 on-CPU GART support

Editing make.conf

Add the following to your /etc/make.conf:

# nano /etc/make.conf
VIDEO_CARDS="fglrx"

Enabling AMD Catalyst Control Center

Then, add the following to /etc/portage/package.use if you would like to enable support for AMD Catalyst Control Center:

# nano /etc/portage/package.use
x11-drivers/ati-drivers qt4
Note

If you are using a desktop or workstation profile, this USE flag will be enabled by default.

Emerging the package

If you allready have emerged xorg-server, all you need to install the drivers is running the following command:

# emerge -av --changed-use --deep @world

otherwise you may install the drivers with

# emerge -av x11-drivers/ati-drivers

Before using the driver, ensure that the "fglrx" module has been loaded -- run modprobe fglrx as root -- it should return with no error. If the module can't be found, run depmod -a as root -- then the modprobe command should work. If you are switching from the open source Radeon driver, then shutting down your desktop and rebooting your system (be sure to disable xdm) may be required to get the new "fglrx" module to load cleanly.

Configuring

Next, set ati-drivers to manage the system's OpenGL and OpenCL implementations. Doing this is particulary important for desktop environments like GNOME, which use hardware acceleration by default. Not doing this will result in the GNOME display manager not being able to start!

# eselect opengl set ati
# eselect opencl set amd

Afterwards, run aticonfig to modify the X-server configuration file to work with the ati-drivers:

# aticonfig --initial
Tip

If you would like to have a full-resolution framebuffer with ati-drivers, check out uvesafb

Multi-Head Display

There are a couple of options for setting up a multi-head display. For some systems, all you need to do is plug in your additional monitor, and it will be detected by your desktop environment, and will work.

If your second monitor does not display anything at all, then play around with your X configuration. Try using the following command to generate a new X config:

# aticonfig --initial=dual-head


You can use the right} option to specify the relationship of the second screen to the first.

For more than two heads, or multiple cards, you can use the following approach to generate an appropriate X config. First, list adapters to see what adapters are available:

# aticonfig --list-adapters


Now, a variant of one of the following commands to generate an X configuration for your needs:

# aticonfig --initial --heads=4 --adapter=1 
# aticonfig --adapter=0,2 --initial
# aticonfig --adapter=all --initial
# aticonfig --xinerama=on


One you have your displays enabled so that your mouse pointer can move to all displays, you still may not be able to drag windows to certain monitors. In this situation, each monitor is probably configured as a separate X screen, and you'll need to use the Catalyst Control Center amdcccle GUI configuration tool to tie them together. The Catalyst Control Center is installed when the qt4 USE variable is enabled.

Open up a graphical terminal, and become root by typing su - -- your user will need to be in the wheel group to do this:

$ su -
Password: *******
# source /etc/profile
# amdcccle


Amdcccle.png

Navigate to Display Manager, and choose the option Multi-display desktop with display(s) X for each display. Then, drag and drop the blue displays to arrange them to match how they are arranged in front of you. Click OK. The Catalyst Control Center will tell you that you will need to restart your system for the changes to take effect. Simply log out if you are running xdm, or end your X session, and start it up again. You should now have a fully-functioning multi-head display.

Troubleshooting

I am using a HDMI connection, and my monitor's display has a black border around it.

Disable overscan as follows:

$ su -
Password: *********
# aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

You will need to restart your X session for the changes to take effect. If you are using a display manager, logging out and back in again should cause the new settings to be visible.

The tabs in Google Chrome are becoming garbled/corrupted

New versions of Google Chrome use hardware acceleration by default which appears to have rendering issues with AMD's drivers. To work around this, disable hardware acceleration in Google Chrome by going to Settings, Show advanced settings... and then uncheck the Use hardware acceleration when available (requires Chrome restart). Once Chrome is restarted, the rendering problem should be resolved.

Compton with backend glx does not work well with ati-drivers

Try running compton with the following switches:

# compton --backend glx --vsync none --paint-on-overlay