cchtml.com - User contributions [en]

Debian

2014-01-15T21:38:56Z

141.212.108.13:

= 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;" | '''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.
UPDATE new poster
13.4 is in the Debian testing repo for 5000 and above cards, 13.1 is also in the Debian repo for older cards

fglrx-driver_12-6+point-1_i386.deb is shipped with Debian stable/Wheezy and works perfectly.

= Installation =

The open-source ati/radeon driver should already be installed and used as the default.
See [[Debian Open Source|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_Catalyst.2Ffglrx| Removing the Driver]] section.

== Installing from Debian Repository ==
NOTE the note is no longer valid info Wheezy is the stable Debian now.
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 [http://wiki.debian.org/ATIProprietary here] and [http://wiki.debian.org/ATIStream 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 catalyst{{Catalystversion}}; cd catalyst{{Catalystversion}}/
$ wget <nowiki>http://www2.ati.com/drivers/linux/amd-</nowiki>{{Catalystdashversion}}-linux-x86.x86_64.zip
$ unzip amd-{{Catalystdashversion}}-linux-x86.x86_64.zip
$ chmod +x amd-{{Catalystdashversion}}-linux-x86.x86_64.run

===Create .deb packages.=== this will not work on Debian
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:
Debian/sid Debian/unstable Debian/etch Debian/stable Debian/lenny Debian/testing Debian/experimental
$ fakeroot sh amd-{{Catalystdashversion}}-linux-x86.x86_64.run --buildpkg <package>
This will not Work in Debian !

===''Install .debs.''===
$ sudo dpkg -i fglrx*.deb
== Jessie AKA TESTING ==
=== Jessie AKA TESTING Installation (November 10 2013) === current working driver in repo, that could change Jessie is testing jan 2014

fglrx was removed from the jessie repository due to incompatibilities with X.org 1.14.
However you can manually install the [http://support.amd.com/en-us/kb-articles/Pages/Latest-LINUX-Beta-Driver.aspx 13.11 beta 6] version.
Do you use debian or Just do things to feel important, there has been a working fglrx in the repo for along time and the latest one is in experimental with in a week or two
mkdir ati
cd ati
apt-get build-dep fglrx-driver
apt-get -b source fglrx-driver
dpkg -i *.deb

you must have the proper repo set in /etc/apt/sources

=== Wheezy AKA STABLE Installation (current as of May 3, 2013) === Why someone posted this I do not have any idea 12.6 was shipped with Wheezy from day one,there is nothing to downgrade or change if you stay on the stable repo ,it just works
DEBIAN IS NOT UBUNTU and those directions will not work on debian, they just confuse people so if you dont use DEBIAN dont post< Everything below this was way before may of 2013 when Wheezy was the testing distro and Squeeze was stable
current as of may 2013 and your first comment is about 2012 are you new to Linux that makes the info stone aged. I find it odd this all got added after Wheezy was released with 12.6,because I was here and posted the info,and this post wasnt here, Do you work for Nvidia?
Wheezy upgraded from xserver 1.11 to 1.12 on May 20, 2012.< you posted about something a year before LMAO<nvidia pay you for that> 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<shipped with Wheezy from day one (05/03/13)<was testing at the time Squeeze was stable 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
I find it odd this all got added after Wheezy was released with 12.6,because I was here and posted the info,and this post wasnt here, Do you work for Nvidia?

= 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 aticonfig --initial -f

If you are using dual head, that is to say, two _different_ desktops on two monitors, do this:
$ sudo aticonfig --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 aticonfig --initial -f --adapter<nowiki>=</nowiki>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 aticonfig --initial -f
$ sudo aticonfig --set-pcs-str<nowiki>=</nowiki>"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 <nowiki>xrandr</nowiki> 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 aticonfig <nowiki>--input=/etc/X11/xorg.conf --tls=1</nowiki>

==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:
<pre>
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.)
</pre>
Now, try:
$ fgl_glxgears
If you experience issues or a hang, you may need to disable fast TLS.
$ sudo aticonfig --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

Be very carefull when doing this, I wasn't paying much attention and all of a sudden aptitude decided that this package required a bunch of packages to be uninstalled(for instance a lot of tex packages, but more inconveniently GDM3...)

=Updating Catalyst/fglrx=

DO NOT try to install a new version over an old one. Follow the [[#Removing_Catalyst.2Ffglrx| 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 [https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver 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.

[[Category:Distributions]]

Troubleshooting

2008-05-21T21:14:30Z

141.212.111.119: /* Kernel Related Issues */

==Kernel Related Issues==

=== No 3D acceleration ===
If you see output that looks like this:

$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

Make sure you have enabled the fglrx driver in the file /etc/X11/xorg.conf . You have to open that file as superuser (using kwrite, gedit, vi, ...) and see:

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
...

Make sure you do not have Xinerama enabled in your xorg.conf! 3D-acceleration is not supported by fglrx in Xinerama mode.

Then try these two commands:

sudo mkdir -p /usr/X11R6/lib/modules/dri
sudo ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri
Source<ref>http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian</ref>

In Gentoo "maybe other distros, not sure" you must initiate the ATI opengl interface by typing:

eselect opengl set ati

Or you can try deleting all files from the /lib/modules/$(uname -r)/volatile folder and relinking:

<code>
sudo rm /lib/modules/$(uname -r)/volatile/* 
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</code> 

If that doesn't work confirm fglrx is loaded:

lsmod | grep fglrx

If it returns nothing then try this:

sudo depmod -ae
sudo echo fglrx >> /etc/modules
(If this returns "bash: /etc/modules: Permission denied" then sudo su first.)

If it doesn't still work, open up /etc/modprobe.d/lrm-video with an editor, and uncomment any line(s) that contains fglrx in it.

In case nothing above works, open /etc/modprobe.d/blacklist-restricted with an editor and comment any line that might contain fglrx word in it.

=== nForce 3 AGP Issues ===

For nForce3 based motherboards: if the install seems to go well, but fglrx still fails and $ fglrxinfo tells you you're still running Mesa, there may be a problem with the nVidia AGP-PCI Bridge module's compatibility with your BIOS (or vice versa, I haven't yet investigated). (Confirmed at least for ASUS K8N-E Deluxe.) A solution is to downgrade your BIOS to a previous version (see your motherboard manual/manufacturer's website for instructions). Here is a list of compatible BIOS versions (if your model is not listed here and you find a version that fixes the problem, please add it to the list so others can benefit):

(Update: March 22nd, 2007) It appears that the beta ASUS bios 1012 will also fix the problem. I had the ATI drivers installed but fglrxinfo was still reporting Mesa as the OpenGL provider. I flashed the BIOS to 1012, rebooted into Ubuntu. Problem solved.

''The 1012 bios did not work for my K8N-E deluxe mobo and my x800. Bios 1006 works great though.''

*ASUS
**K8N-E Deluxe: Version 1006
**K8N-E Deluxe: Version 1012 beta
**K8N Bios versions up 1003 to 1011, my Solution -> K8V-X (Asus with Via-Chipset) It is working really good now. (Always Problems: nForce3 Chipset)

*ASROCK
**K8Upgrade-NF3

(A little workaround for K8Upgrade-NF3 is to edit xorg.conf, in section "Devices", adding this line: Option "UseInternalAGPGART" "no")
It doesn't work with Gutsy release yet.

*GIGABYTE
**GA-K8NSC-939: Bios versions: F1, F2

=== AGP Initialization fails with amd_k7_agp module ===
With Kernel 2.6.16.x, there came a new feature called "EDAC" which creates a conflict causing amd_k7_agp not to work. This results in a
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP
Message in the error-log.

To resolve the problem, in your kernel config change
CONFIG_EDAC_AMD76X=y
to
#CONFIG_EDAC_AMD76X is not set
(just comment it out)
recompile/reinstall/reboot your kernel. Everything should work now.

=== Using realtime enabled kernels ===

Apparently the official driver doesn't support realtime enabled kernels, as installation fails to build the kernel module (see /usr/share/ati/fglrx-install.log). Correct this if I'm wrong.

=== System Crash When Starting X/FGLRX ===

Your MTRR table may not be set up properly - this is especially true for systems with 4GB of memory. To fix the crashing issue, follow the instructions in this link to properly set up the MTRR table.
http://ubantu.homelinux.com/comp/linux/index.php/Linux:troubleshooting:mtrr

==X Server Related Issues==

=== No high-resolution video modes available ===
* Versions of the fglrx driver following 7.12 had problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem; it is '''fixed''' since driver version 8.2

=== No XVideo support on 690G integrated graphic chipset ===
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
*Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.
* XVideo works with 8-1 release (version 8.45.4). You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)
* With 8-3 release (8.47.1), to get XVideo working I added ''Option "TexturedVideo" "true"'' to the xorg.conf file. It wasn't necessary to edit the /etc/ati/amdpcsdb file as described in the paragraph above; the open GL overlay can be active and it will still work.

=== System lockup on logout or switch to virtual consoles ===

If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of [http://ati.cchtml.com/show_bug.cgi?id=330 this bug]. It is likely that the problem only occurs for users with an '''Xorg version of at least 7.0'''. Probably it only affects users of '''DVI'''.

There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.

This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].
---------
Unfortunately "D-sub" users (like me) have the same problem.

=== BigDesktop (Dual screen) doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn & Gutsy.

System > Prefrences > Screen Resolution

Select the resolution that is a combination of both screen resolutions wide and your height.

If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, <code>sudo vim /etc/X11/xorg.conf</code>, and comment out the line which looks like the following:
{{Box File|/etc/X11/xorg.conf|
<pre> Option "DesktopSetup" "something"</pre>
}}

=== Computer Freezes while using fglrx (UMA and SIDEPORT) ===
If after choosing fglrx as your driver in either xorg.conf or xfree86.conf files, the computer freezes and becomes unresponsive while trying to start X this may be the solution.

Some ATI cards have the ability to run in three modes: UMA, SIDEPORT, or a combination of both. UMA mode is that one in which the video card does not use its dedicated memory, but rather uses and shares the system memory. On the other hand, SIDEPORT mode is the one in which the card uses its own dedicated memory. And finally, the third mode is a combination of the previous modes in which the card uses both the system memory and its dedicated memory.

If your computer hangs, this settings may be where the solution lies. If your computer hangs, try using either UMA by itself or a combination of both. However, if you choose the combination, make sure that the UMA one is at least 128MB. In my case, I have SIDEPORT 128MB and 128MB UMA. If I choose any less for UMA, it does not work. This is definetly not an attractive solution since it compromises your systems performance. Hopefully, this will be solved very soon.

On some systems, the BIOS screen may not offer a choice of UMA or SIDEPORT. In this case, you can try turning the amount of RAM dedicated to the video card down, from 128Mb to 64Mb for example.

=== Graphical Anomalies ===

This was experienced with an ATI Radeon X1600 Pro 512mb:

After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information. If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.

To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too). The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).

There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.

=== OpenGL framebuffer Corruption ===

This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.

When Anti-Aliasing is forced, the problem resides.

A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.

For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]

This solution not work on acer laptop with ATI Mobility Radeon HD 2400 XT.
kepfeltoltes.hu/view/080302/atisux_www.kepfeltoltes.hu_.jpg

=== Blank Screen with Xorg 1.3.0 ===
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
{{Box File|/var/log/Xorg.log|
<nowiki>
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
</nowiki>
}}

Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.

Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor
signal sometimes returnes to the internal laptop monitor.
By switching to a console or shutting down the X-server, the card switches back to vga...

My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now
work fine again with Xorg-1.3.0 .

=== Radeon GPU fan is very loud / constantly works ===
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively
even when not in 3D mode. This behaviour will cause the cards' fans to function on full
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source
"radeon" driver does not exhibit this problem.

My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it's because the temp~

It happens too with Radeon X1800 GTO and Radeon X1900 GT.

Possible solution (at least using a Mobility Radeon X1600):
<pre>aticonfig --set-powerstate=1</pre>

To find out which powerstates your Radeon supports try:
<pre>aticonfig --lsp</pre>

=== System freezes after logout with GDM or KDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm hardlocks after running X session</ref> ===

If you use GDM, which is the default Login Manager on Ubuntu, modify
<pre>sudo gedit /etc/gdm/gdm.conf</pre>

{{Box File|/etc/gdm/gdm.conf|
<nowiki>AlwaysRestartServer=true</nowiki>
}}

If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following

<pre>sudo kate /etc/kde3/kdm/kdmrc</pre>

{{Box File|/etc/kde3/kdm/kdmrc|
<nowiki>TerminateServer=true</nowiki>
}}

=== System freezes at startup of Fedora 7 after installing the driver ===

Turn off the Redhat Graphical boot from grub config:

Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.

=== System lockup on logout with catalyst 8.01 <ref>http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01</ref>===
To solve this issue you need to disable atieventsd. On ubuntu you can run:
<pre>
sudo /usr/sbin/update-rc.d -f atieventsd remove
</pre>

=== Intermittent Freezes/Lockups due to AGPv3 running at 8x ===
Try forcing X to set AGP Speed to 4x
{{Box File|/etc/X11/xorg.conf|
<pre> Option "AGPv3Mask" "0x00000002"</pre>
}}
((Would be nice to put down WHERE to change this, not just to change this. The same applies to just about every hint shown above.))

+ You add it to the "Device" section for your graphics card in /etc/X11/xorg.conf.

==References==
<references/>

[[Category:Installation Documentation]]

[[Category:NeedsUpdating]]
{{VCT}}

Troubleshooting

2008-02-29T15:55:57Z

141.212.111.119: /* System freezes at startup of Fedora 7 after installing the driver */

==Kernel Related Issues==

=== No 3D acceleration ===
If you see output that looks like this:

$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.1)

Make sure you do not have Xinerama enabled in your xorg.conf! 3D-acceleration is not supported by fglrx in Xinerama mode.

Then try these two commands:

sudo mkdir -p /usr/X11R6/lib/modules/dri
sudo ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri
Source<ref>http://www.thinkwiki.org/wiki/Problems_with_fglrx#Perpetual_Mesa_GLX_Indirect_on_Debian</ref>

In Gentoo "maybe other distros, not sure" you must initiate the ATI opengl interface by typing without quotes:
"eselect opengl set ati"

Or you can try deleting all files from the /lib/modules/$(uname -r)/volatile folder and relinking:

<code>
sudo rm /lib/modules/$(uname -r)/volatile/* 
sudo ln -s /lib/modules/$(uname -r)/misc/fglrx.ko /lib/modules/$(uname -r)/volatile/fglrx.ko
</code> 

If that doesn't work confirm fglrx is loaded:

lsmod | grep fglrx

If it returns nothing then try this:

sudo depmod -ae
sudo echo fglrx >> /etc/modules
(If this returns "bash: /etc/modules: Permission denied" then sudo su first.)

If it doesn't still work, open up /etc/modprobe.d/lrm-video with an editor, and uncomment any line(s) that contains fglrx in it.

In case nothing above works, open /etc/modprobe.d/blacklist-restricted with an editor and comment any line that might contain fglrx word in it.

=== nForce 3 AGP Issues ===

For nForce3 based motherboards: if the install seems to go well, but fglrx still fails and $ fglrxinfo tells you you're still running Mesa, there may be a problem with the nVidia AGP-PCI Bridge module's compatibility with your BIOS (or vice versa, I haven't yet investigated). (Confirmed at least for ASUS K8N-E Deluxe.) A solution is to downgrade your BIOS to a previous version (see your motherboard manual/manufacturer's website for instructions). Here is a list of compatible BIOS versions (if your model is not listed here and you find a version that fixes the problem, please add it to the list so others can benefit):

(Update: March 22nd, 2007) It appears that the beta ASUS bios 1012 will also fix the problem. I had the ATI drivers installed but fglrxinfo was still reporting Mesa as the OpenGL provider. I flashed the BIOS to 1012, rebooted into Ubuntu. Problem solved.

''The 1012 bios did not work for my K8N-E deluxe mobo and my x800. Bios 1006 works great though.''

*ASUS
**K8N-E Deluxe: Version 1006
**K8N-E Deluxe: Version 1012 beta
**K8N Bios versions up 1003 to 1011, my Solution -> K8V-X (Asus with Via-Chipset) It is working really good now. (Always Problems: nForce3 Chipset)

*ASROCK
**K8Upgrade-NF3

(A little workaround for K8Upgrade-NF3 is to edit xorg.conf, in section "Devices", adding this line: Option "UseInternalAGPGART" "no")
It doesn't work with Gutsy release yet.

*GIGABYTE
**GA-K8NSC-939: Bios versions: F1, F2

=== AGP Initialization fails with amd_k7_agp module ===
With Kernel 2.6.16.x, there came a new feature called "EDAC" which creates a conflict causing amd_k7_agp not to work. This results in a
(EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENODEV"
(EE) fglrx(0): cannot init AGP
Message in the error-log.

To resolve the problem, in your kernel config change
CONFIG_EDAC_AMD76X=y
to
#CONFIG_EDAC_AMD76X is not set
(just comment it out)
recompile/reinstall/reboot your kernel. Everything should work now.

=== Using realtime enabled kernels ===

Apparently the official driver doesn't support realtime enabled kernels, as installation fails to build the kernel module (see /usr/share/ati/fglrx-install.log). Correct this if I'm wrong.

==X Server Related Issues==

=== No high-resolution video modes available ===
* Recent versions of the fglrx driver (seen with 7.12) seem to have problems with video resolutions higher than 1280 x 1024. The modes of the xorg.conf are simply ignored, and the server starts up e.g. with a resolution 1280 x 1024 (even if this resolution is not defined in xorg.conf). This is particularly a problem on LCD displays.
* [http://ati.cchtml.com/show_bug.cgi?id=160 This bug] documents the problem.
* No known workaround.
* The bug seems to be fixed with driver version 8.1 (though I cannot fully verify this since my system locks up hard after (correctly) setting the graphics mode, SuSE 10.0 not supported anymore - [[User:Akhuettel|Akhuettel]])

=== No XVideo support on 690G integrated graphic chipset ===
*Upgrade your BIOS if you get random flicker lines and black screen with a 690G chip.
*Motherboard using the 690G IGP chipset don't have XVideo support. When you execute the "xvinfo" command you get "no adaptors present". This is the case by using the 8.39.4 FGLRX driver and whenever the "sudo aticonfig --overlay-type=Xv" command or the "sudo aticonfig --overlay-type=opengl" was used. ATI seem to know this as there list TVtime as an application unable to run on a 690G chip.
* XVideo works with 8-1 release (version 8.45.4). You need to change the defaults in /etc/ati/amdpcsdb (created by amdcccle, loaded by X on start, and saved on exit). With X shutdown, set VideoOverlay=Son, OpenGLOverlay=Soff, and Textured2D=STrue. (Don't use aticonfig or xorg.conf to set these. At this time, aticonfig and amdccle don't change these settings, and /etc/ati/amdpcsdb seems to override xorg.conf) (Verified on Asus M2A-VM with BIOS 1501)

=== System lockup on logout or switch to virtual consoles ===

If your system locks up after you logout or when you try to switch to a virtual console, this might be an instance of [http://ati.cchtml.com/show_bug.cgi?id=330 this bug]. It is likely that the problem only occurs for users with an '''Xorg version of at least 7.0'''. Probably it only affects users of '''DVI'''.

There is a workaround: Use a standard D-Sub VGA connector instead of the DVI connector.

This workaround was posted as a comment to another related bug: see [http://ati.cchtml.com/show_bug.cgi?id=239#c48 here].
---------
Unfortunately "D-sub" users (like me) have the same problem.

=== BigDesktop (Dual screen) doesn't work after GDM login screen ===

This can occur on Ubuntu Feisty Fawn & Gutsy.

System > Prefrences > Screen Resolution

Select the resolution that is a combination of both screen resolutions wide and your height.

If X crashes during login, go to a virtual console using Ctrl+Alt+F1, log in, <code>sudo vim /etc/X11/xorg.conf</code>, and comment out the line which looks like the following:
{{Box File|/etc/X11/xorg.conf|
<pre> Option "DesktopSetup" "something"</pre>
}}

=== Computer Freezes while using fglrx (UMA and SIDEPORT) ===
If after choosing fglrx as your driver in either xorg.conf or xfree86.conf files, the computer freezes and becomes unresponsive while trying to start X this may be the solution.

Some ATI cards have the ability to run in three modes: UMA, SIDEPORT, or a combination of both. UMA mode is that one in which the video card does not use its dedicated memory, but rather uses and shares the system memory. On the other hand, SIDEPORT mode is the one in which the card uses its own dedicated memory. And finally, the third mode is a combination of the previous modes in which the card uses both the system memory and its dedicated memory.

If your computer hangs, this settings may be where the solution lies. If your computer hangs, try using either UMA by itself or a combination of both. However, if you choose the combination, make sure that the UMA one is at least 128MB. In my case, I have SIDEPORT 128MB and 128MB UMA. If I choose any less for UMA, it does not work. This is definetly not an attractive solution since it compromises your systems performance. Hopefully, this will be solved very soon.

On some systems, the BIOS screen may not offer a choice of UMA or SIDEPORT. In this case, you can try turning the amount of RAM dedicated to the video card down, from 128Mb to 64Mb for example.

=== Graphical Anomalies ===

This was experienced with an ATI Radeon X1600 Pro 512mb:

After following instructions for both Method 1 and Method 2, whenever the Composite Extension is disabled, the display would be almost unusable, but the fglrxinfo command would display the correct information. If the Composite Extension is re-enabled the display would be usable, but fglrxinfo would report using mesa drivers.

To resolve the problem it maybe needed to lower the AGP Aperture setting in my BIOS to 128mb (or lower worked too). The AGP Aperture was initially set to 256mb. After setting the AGP Aperture to 128mb, everything worked perfectly; the Composite Extension is disabled, fglrxinfo reports the correct drivers, and direct rendering is enabled. Some systems may require setting the AGP Aperture to the highest setting (256mb or 512mb).

There's been a bug report regarding [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/150627 anomalies in Firefox] as well.

=== OpenGL framebuffer Corruption ===

This problem has been experienced on Thinkpads (T60p) with an ATI MOBILITY FireGL V5250 running driver versions 7.12, 8.01 and 8.02. Whenever any OpenGL application is rendered, the rendered output appears "scrambled" and unreadable. This problem is not very well documented and both glxgears and fgl_glxgears display this anomaly when testing.

When Anti-Aliasing is forced, the problem resides.

A solution (tested with 8.02 on Ubuntu Gutsy) to this problem is to open the ATI/AMD Catalyst Control Center and expand the item labeled '3D' in the options tree on the left-hand side of the window. From there, select "Anti-Aliasing" and check the box which reads: "Override application setting". Apply the settings and close the control center.

For an example of this anomaly, please see [http://i31.tinypic.com/244z9z8.png this image]

=== Blank Screen with Xorg 1.3.0 ===
If you happen to get a blank screen on X startup and you find lines similar to those in your Xorg.log:
{{Box File|/var/log/Xorg.log|
<nowiki>
2: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(swlDalHelperValidateModeFromDAL 0x549) [...]
3: /usr/lib64/xorg/modules/drivers//fglrx_drv.so [...]
4: /usr/lib64/xorg/modules/drivers//fglrx_drv.so(atiddxPreInit 0x8b3) [...]
</nowiki>
}}

Then you're probably using the ati-drivers with Xorg-1.3.0. If that's the case the only solution (known to me) is to use a version < 1.3.0.

Edit: I got the same problem after using the --add-pairmode argument of aticonfig (using Xorg 1.3.0). My ati mobility x300 seemes to try
sending the monitor signal to the vga output (even if no monitor is connected to it). After pressing [Fn]+[F8(CRT/LCD)] the monitor
signal sometimes returnes to the internal laptop monitor.
By switching to a console or shutting down the X-server, the card switches back to vga...

My solution: overwriting the file /etc/ati/amdpcsdb with /etc/ati/amdpcsdb.default (sudo cp /etc/ati/amdpcsdb.default /etc/ati/amdpcsdb)
and restore the xorg.conf (since Xorg replaces /etc/X11/xorg.conf with a failsafe config file). Then reboot the system: fglrx should now
work fine again with Xorg-1.3.0 .

=== Radeon GPU fan is very loud / constantly works ===
:See [http://ati.cchtml.com/show_bug.cgi?id=499 bug 499] for additional information.
It seems fglrx has a bug with all X800/X850 cards causing them to heat up excessively
even when not in 3D mode. This behaviour will cause the cards' fans to function on full
blast continuously. There is no known fix as of driver 8.31.05 or previous. Open source
"radeon" driver does not exhibit this problem.

My Ati 1650GT has the same problem.It was normal when I enter ubuntu for 1 or 2minutes,and than ,the fan became crazy..No doubt it's because the temp~

It happens too with Radeon X1800 GTO and Radeon X1900 GT.

Possible solution (at least using a Mobility Radeon X1600):
<pre>aticonfig --set-powerstate=1</pre>

To find out which powerstates your Radeon supports try:
<pre>aticonfig --lsp</pre>

=== System freezes after logout with GDM or KDM<ref>http://ati.cchtml.com/show_bug.cgi?id=239 Going back to gdm/kdm hardlocks after running X session</ref> ===

If you use GDM, which is the default Login Manager on Ubuntu, modify
<pre>sudo gedit /etc/gdm/gdm.conf</pre>

{{Box File|/etc/gdm/gdm.conf|
<nowiki>AlwaysRestartServer=true</nowiki>
}}

If you use KDM, which is the default Login Manager on Kubuntu, add to the [X-:*-Core] section the following

<pre>sudo kate /etc/kde3/kdm/kdmrc</pre>

{{Box File|/etc/kde3/kdm/kdmrc|
<nowiki>TerminateServer=true</nowiki>
}}

=== System freezes at startup of Fedora 7 after installing the driver ===

Turn off the Redhat Graphical boot from grub config:

Edit the grub config file located at /boot/grub/grub.conf and remove the 'rhgb' from the kernel line in order to disable the Redhat Graphical boot.

=== System lockup on logout with catalyst 8.01 <ref>http://www.phoronix.com/forums/showthread.php?t=7448&page=5 System lockup on logout with catalyst 8.01</ref>===
To solve this issue you need to disable atieventsd. On ubuntu you can run:
<pre>
sudo /usr/sbin/update-rc.d -f atieventsd remove
</pre>

==References==
<references/>

[[Category:Installation Documentation]]

[[Category:NeedsUpdating]]
{{VCT}}