Difference between revisions of "Debian"

From cchtml.com
Jump to: navigation, search
(Before Starting)
(Catalyst 11.9 and Debian Squeeze x86_64 (October 2011): OBSOLETE)
(30 intermediate revisions by 18 users not shown)
Line 1: Line 1:
On Vista (32 bit), Catalyst 9.1, FRAPS not installed, GPU-Z not ruinnng, not ATT installed, 4 GB RAM (3.2 GB used) with a 4870, 512MB:Still no go, even with FurMark 1.6.4, OR SO I THOUGHT.I have disabled Adaptive Anti-Aliasing AND I moved the slider for Catalyst A.I. back from Advanced to Standard.Please try these options (Adaptive Anti-Aliasing and/or Catalyst A.I. back to standard) and tell us if FurMark works again Suddenly, I also can Login to SecondLife again, I must have been one of the two!
+
= Read Me First =
  
 +
'''Which cards are no longer supported by ATI Catalyst?'''
 +
The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part).  See the complete list [http://wiki.cchtml.com/index.php/9.4 here.]
 +
If your card is on that list, you are limited to open-source drivers on Debian Squeeze/6.0 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use Debian Lenny/5.0.x and install Catalyst 9-3.
 +
{| WIDTH="650" cellpadding=0 cellspacing=0 style="background-color: red; border: solid 1px #666666; color: #ffffff; text-align: center;"
 +
| style="background-color: #666666; border: solid 1px #666666; border-bottom: 1px solid #888;" | <font size="-1">'''ATTENTION RADEON USERS'''</font>
 +
|-
 +
| <br />NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Debian versions later than  Lenny/5.0.x! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers.<br /><br />
 +
|}
 +
 +
= Read Me Second :SLEEP mode  in Debian/testing kernel 3.2.0 =
 +
 +
amd-driver-installer-catalyst-12.10-x86.x86_64.run breaks sleeping mode(notebook hangs up after awaking and reboot without logging anything ). I suppose it is because atievetsd not working correctly. So i first install last fglrx-atieventsd packet and over it amd-driver-installer-catalyst-12.10-x86.x86_64.run. ( Or first
 +
amd-driver-installer-catalyst-12.10-x86.x86_64.run and then manualy copy rest conf files from fglrx-atieventsd
 +
without overwriting.) Then start atieventsd :  "service fglrx-atieventsd restart" and put this command  in
 +
autorun files.
 +
 +
Next step - check /var/syslog if there would be "atieventsd[3141]: Unable to bind control socket to
 +
/var/run/atieventsd.socket: Permission denied " - then it need be run by root.
 +
 +
After this sleeping mode become work correctly  but only sometimes. Research is to be continued.
 +
Good news is that many 3d games are well playing with sound on wine-1.5.6.
 +
 +
UPDATE:
 +
It seems it works correctly. Clean install amd-driver-installer-catalyst-12.10-x86.x86_64.run on Debian/testing kernel 3.2.0 i386.
 +
But after upgrading libxi6 to stable version (apt-get install -t stable libxi6).
 +
Old version have made problems with wine games , something like "malloc() corruption memory" and segfault.
 +
New version amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run and fglrx-driver_12-6+point-1_i386.deb i havenot test.
 +
 +
 
= Installation =
 
= Installation =
  
Line 7: Line 36:
 
This guide focuses on installing the proprietary ATI driver (fglrx/Catalyst).
 
This guide focuses on installing the proprietary ATI driver (fglrx/Catalyst).
  
SEO Services from If you’ve taken us up on our offer of a free SEO analysis, you will have some ioicdatinn of just how personal and bespoke we can make our SEO services to get you the results you desire. Organic, natural, tailor-made SEO services are the best way to get real, positive rankings on the world’s biggest search engines. It will help to increase your visibility, attract greater traffic and garner better conversions for your products.Bespoke search engine optimisation services that accentuate your brand and complement your wider marketing strategy are the best way to cultivate new visitors and get better online exposure. At SEO Consult, we will outline a strategy that will give you prominence for key terms on search engines such as Google, Yahoo! and Bing, whilst being transparent enough to accommodate your voice SEO Consult is a leading Search Engine Optimisation agency in the UK and worldwide. Since 2003 SEO Consult has been practicing Search Engine Optimisation techniques for 100 s of businesses worldwide.SEO Consult is a trading sub domain of Click Consult, the SEO Consult website was created to create a website dedicated to the topic we love so much, Search Engine Optimisation.With more than 60 Search Engine Marketing professionals and offices in Cheshire and London, SEO Consult leads the way in the Search Engine Optimisation industry.SEO Consult pride ourselves on service and results, our company structure of Account managers & SEO Programmers ensure that every account SEO Consult manages is managed to ensure the balance of expectations and results are maintained through the project duration Search Engine Optimisation (Optimization if you're Stateside) or SEO is a process by which internal and external aspects of a web site are adjusted to gain high search engine returns on key word and key phrase searches. Search returns are sometimes referred to as organic or natural.The majority of web traffic is driven by the major commercial search engines: Google, Yahoo and MSN. Google attracts approximately 60% of worldwide searches at 37 billion, with Yahoo (8.5 billion) and Microsoft (2.2 billion). A number of country-specific search engine companies have also become prominent in their own territories; for example Baidu in China, Guruji in India, Yandex in Russia.High placements invariably lead to sites receiving an increase in traffic. 78% of users abandoning their search if the first 3 pages don't provide an answer to their question high search engine placements are essential. 28% don't even consider scrolling past the 2nd page of results. High traffic can be converted to revenue through sales, advertising revenue, referrals, votes or whatever call to action is invoked on landing pages. Smart, professional Search Engine Optimisation yielding high organic returns (70% of search engine users prefer organic search returns to sponsored links or PPC) can deliver extremely powerful results.Anyone promising  guaranteed top results ,  submission to thousands of search engines and directories ,  instant results ,  permanent top positions  or such like, most likely doesn't know what they're doing and are worth avoiding
+
==Before Starting==
 +
If you have previously attempted installing Catalyst, remove any leftover files by following the [[#Removing_Catalyst.2Ffglrx| Removing the Driver]] section.  
 +
 
  
 
== Installing from Debian Repository ==
 
== Installing from Debian Repository ==
Line 38: Line 69:
 
This package contains both the 32-bit and 64-bit driver.
 
This package contains both the 32-bit and 64-bit driver.
 
  $ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
 
  $ cd ~/; mkdir catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
  $ wget <nowiki>http://www2.ati.com/drivers/linux/amd-driver-installer-</nowiki>{{Catalystdashversion}}-x86.x86_64.run
+
  $ wget <nowiki>http://www2.ati.com/drivers/linux/amd-</nowiki>{{Catalystdashversion}}-linux-x86.x86_64.zip
  $ chmod +x amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run
+
$ unzip amd-{{Catalystdashversion}}-linux-x86.x86_64.zip
 +
  $ chmod +x amd-{{Catalystdashversion}}-linux-x86.x86_64.run
  
 
===Create .deb packages.===
 
===Create .deb packages.===
You can run <code>./amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --listpkg</code> to get a list of all the potential packages
+
You can run <code>./amd-{{Catalystdashversion}}-linux-x86.x86_64.run --listpkg</code> to get a list of all the potential packages
  
 
For Debian systems, <package> will be one of the following:   
 
For Debian systems, <package> will be one of the following:   
 
Debian/sid  Debian/unstable Debian/etch Debian/stable Debian/lenny Debian/testing  Debian/experimental  
 
Debian/sid  Debian/unstable Debian/etch Debian/stable Debian/lenny Debian/testing  Debian/experimental  
  $ fakeroot sh amd-driver-installer-{{Catalystdashversion}}-x86.x86_64.run --buildpkg <package>
+
  $ fakeroot sh amd-{{Catalystdashversion}}-linux-x86.x86_64.run --buildpkg <package>
  
 
===''Install .debs.''===
 
===''Install .debs.''===
 
  $ sudo dpkg -i fglrx*.deb
 
  $ sudo dpkg -i fglrx*.deb
  
== Wheezy Installation (current as of June 22, 2012) ==
+
== Wheezy Installation (current as of May 3, 2013) ==
  
 
Wheezy upgraded from xserver 1.11 to 1.12 on May 20, 2012.  AMD has not updated their driver to work with this version of xserver.  So, you have two options:
 
Wheezy upgraded from xserver 1.11 to 1.12 on May 20, 2012.  AMD has not updated their driver to work with this version of xserver.  So, you have two options:
  
1) Downgrade from xserver 1.12 (Tested, and works on 6/22/12 on Debian Wheezy kernel 3.2.0-1-amd64)
+
1) Downgrade from xserver 1.12 (Tested, and works on Debian Wheezy kernel 3.2.0-4-amd64 (05/03/13) and on Debian Wheezy kernel 3.2.0-1-amd64 (6/22/12) )
  
 
Link to instructions (this should be copied over to this wiki for posterity):
 
Link to instructions (this should be copied over to this wiki for posterity):
 
   https://www.linuxquestions.org/questions/linux-hardware-18/how-do-i-get-my-fglrx-driver-back-946102/#post4684285.
 
   https://www.linuxquestions.org/questions/linux-hardware-18/how-do-i-get-my-fglrx-driver-back-946102/#post4684285.
  
Notes:
+
Note 1:
 
In the linked directions they use fglrx version 12.4.  At the time of making this edit beta version 12.6 also works just fine.  If you want to run the bleeding edge, it can be found here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English   
 
In the linked directions they use fglrx version 12.4.  At the time of making this edit beta version 12.6 also works just fine.  If you want to run the bleeding edge, it can be found here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English   
 
With the 12.6 beta version you will get a watermark in the lower right hand corner.  After you have everything working properly run this script: http://www.areyoueye.net/scripts/watermark_nix.sh  It will get rid of that water mark.
 
With the 12.6 beta version you will get a watermark in the lower right hand corner.  After you have everything working properly run this script: http://www.areyoueye.net/scripts/watermark_nix.sh  It will get rid of that water mark.
  
 +
Note 2:
 +
fglrx version 13.4 works just fine except changing the brighntess because it stays full all the time. Installing this driver will not show up the watermark
  
 
2) Patch libpciaccess (I have no first hand knowledge of this working but others swear by it)
 
2) Patch libpciaccess (I have no first hand knowledge of this working but others swear by it)
Line 218: Line 252:
 
  $ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
 
  $ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
  
=Catalyst 11.9 and Debian Squeeze x86_64 (October 2011)=
+
=Debian Squeeze x86_64 and AMD A Series=
Version 11.9 will not install on Debian Squeeze with Kernel >= 3.1. To fix and install proceed as follows.
+
First uninstall all versions of fglrx you can find, see above. (!!)
+
 
+
Download the driver and extract it thusly:
+
$ sudo ./ati-driver-installer-11-9-x86.x86_64.run --keep
+
Enter the newly created directory (will be named fglrx-install.XXXXXX).
+
Use a hexeditor to find bytes starting at A6B0 with the values <nowiki>e8 53 90 ff ff</nowiki> and replace them with <nowiki>90 90 90 90 90</nowiki>.
+
This replaces a faulty free-op with 5 no-ops and fixes the exception thrown by "setup.data/bin/x86_64/setup".
+
Read up on this at <nowiki>http://disbauxes.upc.es/?p=2964</nowiki> .
+
 
+
Now the kernel-build-environment for the 3.1 kernel is currently missing in the repositories. To get around that type:
+
$ sudo aptitude install linux-source-3.1.0-rc7
+
$ cd /usr/src;tar -xjf linux-source-3.1.0-rc7;ln -s linux-source-3.1.0-rc7 linux;cd linux;
+
You may need to append an "-amd64" (or similar) to the localversion of the source to have its version-string match the one of the running kernel.
+
To do so open .config in the current dir with an editor and search for "LOCALVERSION", set that var to "-amd64" or similar.
+
Configure the kernel using
+
$ sudo make oldconfig
+
and build it using
+
$ make-kpkg --initrd --append-to-version="-myversion" kernel_image kernel_headers modules_image
+
You may not need to rebuild the whole kernel, installing its headers may be enough,
+
but i wanted a fresh kernel with a few custom options.
+
Install your kernel (or just the headers) from the .deb-files that were created by make-kpkg in the directory above.
+
 
+
After this return to the directory where you extracted the driver to and type:
+
$ sudo ./amd-installer.sh 8.892 --install --force
+
 
+
To load the driver type:
+
$ sudo modprobe fglrx
+
 
+
=Debian Squeeze x86_64 and AMD A Series (June 2012)=
+
  
 
First install Kernel 3.2 from squeeze-backports.
 
First install Kernel 3.2 from squeeze-backports.
 
Add backports to your sources.list
 
Add backports to your sources.list
 
Add this line
 
Add this line
  deb http://backports.debian.org/debian-backports squeeze-backports main
+
  deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free
  
 
to your sources.list (or add a new file to /etc/apt/sources.list.d/)
 
to your sources.list (or add a new file to /etc/apt/sources.list.d/)
Line 267: Line 271:
  
 
  $ sudo apt-get -t squeeze-backports install fglrx-glx-ia32
 
  $ sudo apt-get -t squeeze-backports install fglrx-glx-ia32
 +
 +
 +
== Problems with multiple cards and multiple monitors ==
 +
 +
When encountering problems under the following circumstances:
 +
 +
1. Multiple monitors on one card AND a monitor attached to VGA port.
 +
2. More than one card.
 +
 +
...you may encounter problems that the resolution of the first monitor on the first card (usually identified as "CRT-1") may (a) not be recognized by manufacturer/model and instead the "Default Monitor" setting be used, and (b) therefore the resolution be set to a different resolution (e.g. 1600x1200) no matter what the xorg.conf file says.
 +
 +
If this happens, check if the log file '''/var/log/Xorg.0.log''' contains an entry like this one:
 +
 +
'''(II) fglrx(0): Cannot get EDID information for CRT1'''
 +
 +
...which may be followed later with:
 +
 +
'''(II) fglrx(0): Output CRT1 connected'''
 +
 +
'''(II) fglrx(0): Using user preference for initial modes'''
 +
 +
'''(II) fglrx(0): Output CRT1 using initial mode 1600x1200'''
 +
 +
The reason for this behavior seems to be either a timing problem during Xorg initialization (EDID info for CRT-1 not received quickly enough) or a problem with a dcc probe itself. A possible work-around is to not use the VGA connector (CRT-1) on the first card at all and use only the DVI and HDMI port (possibly with a HDMI-to-DVI adapter cable) and the problem disappears immediately (monitor gets recognized immediately and correct resolution is being used).
 +
 +
To avoid confusion with the Xorg configuration, you may want to delete '''/etc/X11/xorg.conf''' file and use the following command to have it generated (assuming 2 monitors per card):
 +
 +
'''  prompt$ aticonfig --initial --adapter=all --heads=2'''
 +
 +
This will create a complete and correct configuration file (you may want to change layout later) even if a VGA monitor is attached to the first card but that VGA monitor will not be recognized upon reboot.
 +
  
 
[[Category:Distributions]]
 
[[Category:Distributions]]

Revision as of 19:42, 5 July 2013

Contents

Read Me First

Which cards are no longer supported by ATI Catalyst? The ATI Radeon 9500-9800, Xpress200-1250, 690G, 740G, X300-X2500 (including Mobility RadeonHD 2300, since it is really a DirectX 9 part). See the complete list here. If your card is on that list, you are limited to open-source drivers on Debian Squeeze/6.0 (and later). If you really need the proprietary Catalyst/fglrx driver, you will have to use Debian Lenny/5.0.x and install Catalyst 9-3.

ATTENTION RADEON USERS

NOTE: If you enter your card information on AMD/ATI's driver page, it will offer you the Catalyst 9-3 driver to download. However, the Catalyst 9-3 driver doesn't support X servers past 1.5, and it will not work with Debian versions later than Lenny/5.0.x! !!!SO BE CAREFUL!!! If you tried to install Catalyst on a system with one of these cards, see the 'Removing the Driver' section to restore the default/pre-installed drivers.

Read Me Second :SLEEP mode in Debian/testing kernel 3.2.0

amd-driver-installer-catalyst-12.10-x86.x86_64.run breaks sleeping mode(notebook hangs up after awaking and reboot without logging anything ). I suppose it is because atievetsd not working correctly. So i first install last fglrx-atieventsd packet and over it amd-driver-installer-catalyst-12.10-x86.x86_64.run. ( Or first amd-driver-installer-catalyst-12.10-x86.x86_64.run and then manualy copy rest conf files from fglrx-atieventsd without overwriting.) Then start atieventsd : "service fglrx-atieventsd restart" and put this command in autorun files.

Next step - check /var/syslog if there would be "atieventsd[3141]: Unable to bind control socket to /var/run/atieventsd.socket: Permission denied " - then it need be run by root.

After this sleeping mode become work correctly but only sometimes. Research is to be continued. Good news is that many 3d games are well playing with sound on wine-1.5.6.

UPDATE: It seems it works correctly. Clean install amd-driver-installer-catalyst-12.10-x86.x86_64.run on Debian/testing kernel 3.2.0 i386. But after upgrading libxi6 to stable version (apt-get install -t stable libxi6). Old version have made problems with wine games , something like "malloc() corruption memory" and segfault. New version amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run and fglrx-driver_12-6+point-1_i386.deb i havenot test.


Installation

The open-source ati/radeon driver should already be installed and used as the default. See Debian Open Source Drivers. This guide focuses on installing the proprietary ATI driver (fglrx/Catalyst).

Before Starting

If you have previously attempted installing Catalyst, remove any leftover files by following the Removing the Driver section.


Installing from Debian Repository

NOTE: This no longer works on Wheezy/testing or Sid after upgrade to Xserver 1.12. Unfortunately fglrx/Catalyst trigger segfaults in Xorg newer than 1.11.x, and the driver was removed from Wheezy and Sid.

Fglrx is non-free software, so it is located in the non-free repository. If you do not have non-free enabled, you can do so like this: http://serverfault.com/questions/240920/how-do-i-enable-non-free-packages-on-debian

$ sudo apt-get remove --purge xserver-xorg-video-radeon
$ sudo apt-get install fglrx-driver fglrx-control fglrx-glx fglrx-atieventsd fglrx-modules-dkms

If you are using 64-bit Debian, install the 32-bit fglrx libraries for use with 32-bit programs.

$ sudo apt-get install fglrx-glx-ia32

The Debian community provides information on its wiki pages here and here.

Installing Manually

This can not work at all. please refer the Discussion for details....

This method uses the latest Catalyst driver downloaded from AMD/ATI's site.

Prerequisite Packages

Install the prerequisite packages (names are based on Debian sid, older Debians may be different):

$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 module-assistant dh-modaliases

If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" before proceeding!

$ sudo apt-get install ia32-libs

Download the latest Catalyst package.

This package contains both the 32-bit and 64-bit driver.

$ cd ~/; mkdir catalyst13.12; cd catalyst13.12/
$ wget http://www2.ati.com/drivers/linux/amd-catalyst-13.4-linux-x86.x86_64.zip
$ unzip amd-catalyst-13.4-linux-x86.x86_64.zip
$ chmod +x amd-catalyst-13.4-linux-x86.x86_64.run

Create .deb packages.

You can run ./amd-catalyst-13.4-linux-x86.x86_64.run --listpkg to get a list of all the potential packages

For Debian systems, <package> will be one of the following: Debian/sid Debian/unstable Debian/etch Debian/stable Debian/lenny Debian/testing Debian/experimental

$ fakeroot sh amd-catalyst-13.4-linux-x86.x86_64.run --buildpkg <package>

Install .debs.

$ sudo dpkg -i fglrx*.deb

Wheezy Installation (current as of May 3, 2013)

Wheezy upgraded from xserver 1.11 to 1.12 on May 20, 2012. AMD has not updated their driver to work with this version of xserver. So, you have two options:

1) Downgrade from xserver 1.12 (Tested, and works on Debian Wheezy kernel 3.2.0-4-amd64 (05/03/13) and on Debian Wheezy kernel 3.2.0-1-amd64 (6/22/12) )

Link to instructions (this should be copied over to this wiki for posterity):

 https://www.linuxquestions.org/questions/linux-hardware-18/how-do-i-get-my-fglrx-driver-back-946102/#post4684285.

Note 1: In the linked directions they use fglrx version 12.4. At the time of making this edit beta version 12.6 also works just fine. If you want to run the bleeding edge, it can be found here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx?type=2.4.1&product=2.4.1.3.42&lang=English With the 12.6 beta version you will get a watermark in the lower right hand corner. After you have everything working properly run this script: http://www.areyoueye.net/scripts/watermark_nix.sh It will get rid of that water mark.

Note 2: fglrx version 13.4 works just fine except changing the brighntess because it stays full all the time. Installing this driver will not show up the watermark

2) Patch libpciaccess (I have no first hand knowledge of this working but others swear by it)

This will get you the latest and greatest xserver and fglrx working together.

Read this: http://ati.cchtml.com/show_bug.cgi?id=522 Apply this patch: http://pastebin.com/swpDj4FD

Post Install

Generate a new /etc/X11/xorg.conf file

Unfortunately, there is no sure way to generate the ATI version of the Xorg.conf file. It is entirely dependent on your configuration. The following subsections will attempt to address possible (and tested) variations for their respective configurations.

Generic Config

This will work for most people:

$ sudo amdconfig --initial -f

If you are using dual head, that is to say, two _different_ desktops on two monitors, do this:

$ sudo amdconfig --initial=dual-head -f

Most people with two or more monitors will want instead one large desktop; to do this you may have to specify your monitors individually in the xorg.conf file and tell the driver to use a larger desktop size (big enough to contain both monitors) then use xrandr to configure the monitor arrangement.

Minimal Config

A very basic /etc/X11/xorg.conf file might be what you need if you have a new card that's not fully supported by amdconfig. Here follows the entirety of a minimal xorg.conf file for the Radeon 6870:

Section "Device"
 Identifier "ATI radeon 6870"
 Driver "fglrx"
EndSection

X2/Dual GPU Cards

If you have an X2 card (e.g. 4870X2 or 5970), use... !!Do not use for two separate cards in crossfire!!

$ sudo amdconfig --initial -f --adapter=all

Dual/Multi Monitors

A post at http://phoronix.com/forums/showthread.php?t=18553 suggested to do the following to use a dual monitor display (also known as "Big Desktop"):

$ sudo amdconfig --initial -f
$ sudo amdconfig --set-pcs-str="DDX,EnableRandR12,FALSE"

However the information is dated 2009 and now believed to be obsolete.

For multiple monitors, instead try specifying all monitors in your xorg.conf file. Use the following as a starting point:

 Section "ServerLayout"
       Identifier       "amdconfig Layout"
       Screen        0  "amdconfig-Screen[0]-0" 0 0
 EndSection
 
 Section "Module"
 EndSection
 
 Section "Monitor"
       Identifier       "0-DFP6"
       Option           "DPMS"          "true"
       Option           "PreferredMode" "1920x1080"
 EndSection
 
 Section "Monitor"
       Identifier       "0-CRT1"
       Option           "DPMS"          "true"
       Option           "PreferredMode" "1280x1024"
 EndSection
 
 Section "Device"
       Identifier       "amdconfig-Device[0]-0"
       Driver           "fglrx"
       BusID            "PCI:1:0:0"
       Option           "Monitor-DFP6"  "0-DFP6"
       Option           "Monitor-CRT1"  "0-CRT1"
 EndSection
 
 Section "Screen"
       Identifier       "amdconfig-Screen[0]-0"
       Device           "amdconfig-Device[0]-0"
       Monitor          "0-DFP6"
       DefaultDepth     24
 
       SubSection "Display"
           Viewport     0 0
           Depth        24
           # Big Desktop: 1920+1280=3200, max(1080,1024)=1080
           Virtual      3200 1080
       EndSubSection
 
 EndSection

After starting X successfully, use xrandr to check the maximum screen size is large enough for your combined desktop:

$ xrandr
Screen 0: minimum 320 x 200, current 3200 x 1080, maximum 3200 x 1080

And positioning of connected monitors:

DFP1 disconnected (normal left inverted right x axis y axis)
DFP2 disconnected (normal left inverted right x axis y axis)
DFP3 disconnected (normal left inverted right x axis y axis)
DFP4 disconnected (normal left inverted right x axis y axis)
DFP5 disconnected (normal left inverted right x axis y axis)
DFP6 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm
[modes elided]
CRT1 connected 1280x1024+1920+56 (normal left inverted right x axis y axis) 338mm x 270mm

Use xrandr (or in KDE, krandrtray) to reposition your monitors within your screen.

Force use of the new xorg.conf (if necessary)

Some people find that changes to xorg.conf don't get used by the driver. To force the ATI driver to adopt changes made to xorg.conf, use the following command:

$ sudo amdconfig --input=/etc/X11/xorg.conf --tls=1

Test your installation

NOTE: if you don't reboot first, fglrxinfo gives an error message. Reboot the computer and type

$ fglrxinfo

into the terminal. If the vendor string contains ATI, you have installed the driver successfully. Using fglrxinfo on a system with Catalyst 11-4 and a RadeonHD 4250 returns:

display: :0.0  screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 4200 Series (This line may be different depending on what graphics card you are using.)
OpenGL version string: 3.3.10665 Compatibility Profile Context (This line may be different depending on what graphics card and 
Catalyst version you are using.)

Now, try:

$ fgl_glxgears

If you experience issues or a hang, you may need to disable fast TLS.

$ sudo amdconfig --tls=0

Hardware Video Decode Acceleration (EXPERIMENTAL)

This is confirmed to work for newer RadeonHD GPU's (those with UVD2). If you have a RadeonHD 4000 series or newer, you have UVD2. To see the complete list: http://en.wikipedia.org/wiki/Unified_Video_Decoder#UVD_enabled_GPUs

Debian wheezy/7.0 and Later

$ sudo apt-get install xvba-va-driver

Updating Catalyst/fglrx

DO NOT try to install a new version over an old one. Follow the Removing the Driver section below to remove your existing driver.

Removing Catalyst/fglrx

The uninstall script in the first command will only exist if you downloaded the drivers and installed them directly (rather than building packages as this guide does). Skip the first command if it does not exist.

$ sudo sh /usr/share/ati/fglrx-uninstall.sh
$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev* xorg-driver-fglrx

If you plan on using open-source drivers, you will need to reinstall some packages because Catalyst overwrites or diverts some key 3D libraries with proprietary versions. For more information on this issue, see this Ubuntu wiki page

$ sudo apt-get remove --purge xserver-xorg-video-ati xserver-xorg-video-radeon
$ sudo apt-get install xserver-xorg-video-ati
$ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
$ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

Debian Squeeze x86_64 and AMD A Series

First install Kernel 3.2 from squeeze-backports. Add backports to your sources.list Add this line

deb http://backports.debian.org/debian-backports squeeze-backports main contrib non-free

to your sources.list (or add a new file to /etc/apt/sources.list.d/)

$ sudo apt-get update
$ sudo apt-get -t squeeze-backports install linux-image-3.2.0-0.bpo.2-amd64
$ sudo reboot
$ sudo apt-get remove --purge xserver-xorg-video-radeon
$ sudo apt-get -t squeeze-backports install fglrx-driver fglrx-control fglrx-glx fglrx-atieventsd fglrx-modules-dkms

If you are using 64-bit Debian, install the 32-bit fglrx libraries for use with 32-bit programs.

$ sudo apt-get -t squeeze-backports install fglrx-glx-ia32


Problems with multiple cards and multiple monitors

When encountering problems under the following circumstances:

1. Multiple monitors on one card AND a monitor attached to VGA port. 2. More than one card.

...you may encounter problems that the resolution of the first monitor on the first card (usually identified as "CRT-1") may (a) not be recognized by manufacturer/model and instead the "Default Monitor" setting be used, and (b) therefore the resolution be set to a different resolution (e.g. 1600x1200) no matter what the xorg.conf file says.

If this happens, check if the log file /var/log/Xorg.0.log contains an entry like this one:

(II) fglrx(0): Cannot get EDID information for CRT1

...which may be followed later with:

(II) fglrx(0): Output CRT1 connected

(II) fglrx(0): Using user preference for initial modes

(II) fglrx(0): Output CRT1 using initial mode 1600x1200

The reason for this behavior seems to be either a timing problem during Xorg initialization (EDID info for CRT-1 not received quickly enough) or a problem with a dcc probe itself. A possible work-around is to not use the VGA connector (CRT-1) on the first card at all and use only the DVI and HDMI port (possibly with a HDMI-to-DVI adapter cable) and the problem disappears immediately (monitor gets recognized immediately and correct resolution is being used).

To avoid confusion with the Xorg configuration, you may want to delete /etc/X11/xorg.conf file and use the following command to have it generated (assuming 2 monitors per card):

prompt$ aticonfig --initial --adapter=all --heads=2

This will create a complete and correct configuration file (you may want to change layout later) even if a VGA monitor is attached to the first card but that VGA monitor will not be recognized upon reboot.