cchtml.com - User contributions [en]

User:Akhuettel

2009-02-08T22:21:28Z

Akhuettel:

I'm a (mostly) happy user of a Linux-only (Gentoo) IBM Thinkpad T43.

Currently I'm running Compiz-Fusion 0.7.8... :-) which kind of proves that the fglrx driver works. Performance is not so great though, possibly because of the indirect rendering required. Driver version [[8.6]] works stable.

Note to ATI: please, please, please implement GLX_EXT_texture_from_pixmap!!!

Second note: Why, oh why, do newer driver ebuilds require X 1.5?!?

For more information about me,
please visit my [http://www.akhuettel.de/research/ work homepage] or my [http://www.akhuettel.de/ personal homepage].

Gentoo

2009-02-08T22:17:50Z

Akhuettel: /* General Status */

== General Status ==
* Included with Distribution
See the [http://packages2.gentoo.org/package/ati-drivers webindex of the Gentoo package repository] for stable/unstable status of the package.
It may be useful to use the keyword ~x86 ( or ~amd64 for 64 bit installations) specifically for the x11-drivers/ati-drivers package to get the newest version, since the Gentoo stable / unstable distinction does not always make much sense here.

As of now (February 2009) you may end up in dependency hell, since older ATI drivers dont compile with recent kernel sources, and newer ATI drivers require unstable X... See [[Gentoo Version Limitations]] for more info.

==Installation==
* [[Gentoo Installation Guide|Installation Guide]]

==Tips and Tricks==
* Although not supported by ATI, Compiz-Fusion does work (a bit slow though). Valuable information can be found at the following URL's:
** ... (work in progress)

==Related Resources==
* [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki]

{{VCT}}
[[Category:Distributions]]

Gentoo Version Limitations

2009-02-08T22:14:48Z

Akhuettel: New page: Here's a list of the currently rather annoying limitations of the Gentoo ati-drivers ebuilds. Will be updated as my experimenting goes along... ~~~ {| border="1" | ebuild || driver versi...

Here's a list of the currently rather annoying limitations of the Gentoo ati-drivers ebuilds. Will be updated as my experimenting goes along... [[User:Akhuettel|Akhuettel]]

{| border="1"
| ebuild || driver version || x86 || amd64 || required kernel version || required X version
|-
| 8.501 || [[8.6]] || stable || testing || <= 2.6.25-gentoo-r7 OK, does not compile with 2.6.26-gentoo-r4 || ?
|-
| 8.552-r2 || [[8.11]] || testing || testing || ? || >=x11-base/xorg-server-1.5
|}

Gentoo Installation Guide

2008-05-20T22:25:21Z

Akhuettel: /* glxinfo says "error: failed to open DRM: Operation not permitted" */ added PRE tags

Orginally found on the [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki], the GNU Free Documentation license allows me to copy/paste it here.

== Introduction ==

This guide should help you install and configure the proprietary graphics drivers from ATI. This guide applies for ALL versions of fglrx - it was made before the (rather dramatic) 8.8.25 January 05 release, but it is maintained such that all versions should work.

*Note: If you are using an ATI 7500 Mobility (or such card that isn't supported by the ati-drivers) this HOWTO will not help. Instead use the ATI kernel drivers. See also: http://forums.gentoo.org/viewtopic-p-2137276.html#2137276

== Kernel Configuration ==

Get into menuconfig (cd /usr/src/your-kernel && make menuconfig) and check the following:
{{Box Code|menuconfig|<pre>
Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading

Processor type and features --->
[*] Enable VM86 support
[*] MTRR (Memory Type Range Register) support

Device Drivers --->
Character Devices --->
<M> /dev/agpgart (AGP Support)
<M> Your_AGP_Chipset_Here
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

Graphics support --->
[ ] Support for framebuffer devices

Kernel Hacking --->
[ ] Kernel debugging
</pre>
}}
Sync your kernel menuconfig with the selected portions posted here. (note: you can compile /dev/agpgart & your agp chipset [most likely ati-agp] into the kernel if you want.)

'''Please be aware that -mm and -rc(1,2,3,4,...) kernels often break fglrx due to unexpected changes in syntax, etc. If you want to use ati-drivers, use the stock gentoo-sources or at the very least, a STABLE 2.4 or 2.6 kernel!'''

Don't forget to compile, install, and reboot into the kernel. Directions for this are beyond the scope of this file; if you need help recompiling the kernel, [http://gentoo-wiki.com/HOWTO_Compile_a_Kernel_Manually click here].

== Grabbing a Driver Set ==

For installation it will be easier to drop out of X to a command prompt. Do this using whatever command your Window Manager uses.
I use fluxbox so it's just rightclick -> fluxbox menu -> exit. For KDE or GNOME it's probably just a matter of logging out. When all else fails, hit CTL+ALT+BACKSPACE to kill the X server ungracefully. If the X server only reboots or for some reason you've disabled this hotkey, log in as root and type '''init 3''' to bring the system run level down.

There is also the possibility to stop the xdm service by entering ''/etc/init.d/xdm stop'' as root.

Thanks to portage, installing the drivers is easy. If you have not already done it recently, start by synchronising your portage tree:

emerge --sync

Getting the latest drivers will probably mean unmasking them.

echo "x11-drivers/ati-drivers ~arch" >> /etc/portage/package.keywords
echo "x11-drivers/ati-drivers-extra ~arch" >> /etc/portage/package.keywords

Replace {{Codeline|<~arch>}} with your system architecture; it's going to be either {{Codeline|~x86}} or {{Codeline|~amd64}}, the only two CPU architectures supported by the ATI driver.

Now let's install the drivers. ati-drivers-extra is a (god-awful) control panel for the driver you probably won't use; you can leave that part out if you want, but for completeness we mention it here.

su -
emerge -av ati-drivers ati-drivers-extra

The next step is switch to the ATi OpenGL subsytem:

(#opengl-update ati)
eselect opengl set ati
(very important!)(opengl-update is deprecated)
Configure X:
First, make a standard config file.

xorgconfig

For a single screen

aticonfig --initial --input=/etc/X11/xorg.conf

For a dual head, second screen is {left|right|above|below}

aticonfig --initial=dual-head --input=/etc/X11/xorg.conf --screen-layout={left|right|above|below}

Adapt input with your path to xorg's conf file

If for some reason this command doesn't work, then try manually executing from its default location:

/opt/ati/bin/aticonfig [...]

Now, let's get back into X.

startx

Open up a command prompt and run:

fglrxinfo

If the OpenGL vendor string says "ATI Technologies," then congrats! You've got the drivers working and hardware acceleration going great. If not...read on...

== Troubleshooting ==

=== Config Files ===
By default, the driver uses the Internal AGPGART. Sometimes the internal one doesn't work, and you will have to use the one provided with the kernel. Search your xorg.conf for the line that has the option "UseInternalAGPGART." Simply change the "yes" to "no."

{{Box File|xorg.conf|
Option "UseInternalAGPGART" "no"
}}

Now simply add the modules to {{Filename|/etc/modules.autoload.d/kernel-2.x}} where x is your kernel version.

Add the following (ORDER IS VERY IMPORTANT);
{{Box File|/etc/modules.autoload.d/kernel-2.x|
agpgart
intel-agp # change intel-agp to your chipset. eg: via-agp, nvidia-agp sis-agp.
fglrx
}}

Finally, run

modules-update

Then you can reboot and everything should work. If you have are having problems, check dmesg and /var/log/Xorg.0.log for more info.

=== Blank screen or monitor turning off after startx ===

Versions of ati-drivers >= 8.16.20 have an issue with this that's easily corrected by inserting:
{{Box File|xorg.conf|
Option "ForceMonitors" "notv"
}}
in the device section of xorg.conf (discussed here: http://bugs.gentoo.org/show_bug.cgi?id=103028)

Check if you have a non-DDC monitor connected via VGA/HD15 connector. If so change your xorg.conf:
{{Box File|xorg.conf|
# Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "NONE, CRT"
Option "IgnoreEDID" "off"
Option "HSync2" "30-85"
Option "VRefresh2" "50-160"
# Option "ScreenOverlap" "0"
}}
where HSync2 and VRefresh2 are your monitor parameters.

Also, try changing the MonitorLayout option. The default is "AUTO, AUTO", which is to say X will attempt to autodetect what kind of monitor you've got on the first and second display heads. This can theoretically fail (though I have never observed it). Try changing it around a bit. For example, if you have an LCD and no secondary monitor, change the line to read:

{{Box File|xorg.conf|
Option "MonitorLayout" "TMDS, NONE"
}}

if you have a CRT, simply replace "TMDS" with "CRT".

=== Crashes on startup ===
'''If you are unable to use any 3d applications and get this error instead:'''

FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!

'''Then you do not have tmpfs mounted on /dev/shm, which the driver requires.''' Make yourself sure you have tmpfs support compiled into kernel. It's under

File systems -->
Pseudo filesystems -->
[*] Virtual memory file system support (former shm fs)

To mount this, add to following line to {{filename|/etc/fstab}} (if it isn't there already):

{{Box File|/etc/fstab|
tmpfs /dev/shm tmpfs defaults 0 0
}}

Then just do a:
mount /dev/shm

If the drivers still crap out on you, or for example you get a black screen on X init, try going into your system BIOS and change graphics-related stuff around. Believe it or not, for me my 9800 gives a black screen on X init if I have the AGP Aperture set at anything other than 128MB. I don't know what causes this, and I don't care; I'm just relating to you how I overcame ''my'' problem ;)

Also, '''whenever you update your compiler''', you '''must''' recompile your kernel otherwise you won't be able to insert the fglrx module. Note that recompiling your kernel means you must also unmerge/emerge ati-drivers!

=== Duplicate symbol errors in X log ===
If you are unable to start X or X fails to load the fglrx driver and you have multiple symbol errors in your Xorg log, chances are that you have compiled X with the ''dlloader'' flag. This flag can not be used with the fglrx driver. To fix this problem, remove the dlloader flag by editing your /etc/portage/package.use file as follows:
{{Box File|/etc/portage/package.use|
x11-base/xorg-x11 -dlloader
}}
Now re-emerge the ''xorg-x11'' package and reinstall the fglrx driver.

=== Crashes on the exit of X.org / X won't shutdown ===
Perform the following if you can get the fglrx drivers working with hardware acceleration, but are suffering from a complete system crash when trying to quit X. You should boot into your system, login, then start on this. You don't need to boot into X, and shouldn't need to edit your xorg.conf file (as fglrx is already setup as the driver and working)

You've emerged the "stable" version of the ati-drivers, these are out of date -- remove them (emerge --unmerge ati-drivers), to add the most recent you should either add them to the keywords file (/etc/portage/package.keywords) or emerge your local ebuild (emerge /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.22.5.ebuild) if you're told it requires a dependency, emerge the local e-build for that, then try again. (usually eselect-opengl is required.)
Once you have the most recent ati-drivers emerged, run (eselect opengl set ati). Now you can (startx) and hopefully quit without any problems.

=== glxinfo says "error: failed to open DRM: Operation not permitted" ===
If a check with the glxinfo fails for ordinary users though works fine for root it might be related to filepermissions of the device-file.
Here is how to solve it:

Make sure that the filepermissions on the card-device allows the video-group to read and write. The common group in gentoo with X is "video". All normal users should be part of this group. Also, the device must have permissions for this group to read and write the card-device.

Check the permissions on the card-device:

<pre>
root:/#ls -lcF /dev/dri/card0
crw-rw---- 1 root root 226, 0 Oct 5 16:19 /dev/dri/card0
</pre>

It can be changed with:

<pre>
root:/dev/dri#chgrp video card0
</pre>

Check if user is part of video:

<pre>
paddlaren:~>id paddlaren
uid=1000(paddlaren) gid=1000(paddlaren) groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),80(cdrw),85(usb),100(users),35(games)
</pre>

To add a user to the video-group:

<pre>
root:~#gpasswd -a my_user video

paddlaren:~>id paddlaren
uid=1000(paddlaren) gid=1000(paddlaren) groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),27(video),80(cdrw),85(usb),100(users),35(games)
</pre>

Logoff and on to ensure that the membership of the group is known to the system.

== See Also ==

*[http://ati.cchtml.com/ ATi Unofficial Bugzilla (occasionally monitored by ATi personnel)]
*Check out user Wedge_'s excellent ATI Radeon [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html FAQ here]

[[Category:Installation Documentation]]

Gentoo Installation Guide

2008-05-20T22:06:17Z

Akhuettel: Reverted vandalism by 72.55.188.165

Orginally found on the [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki], the GNU Free Documentation license allows me to copy/paste it here.

== Introduction ==

This guide should help you install and configure the proprietary graphics drivers from ATI. This guide applies for ALL versions of fglrx - it was made before the (rather dramatic) 8.8.25 January 05 release, but it is maintained such that all versions should work.

*Note: If you are using an ATI 7500 Mobility (or such card that isn't supported by the ati-drivers) this HOWTO will not help. Instead use the ATI kernel drivers. See also: http://forums.gentoo.org/viewtopic-p-2137276.html#2137276

== Kernel Configuration ==

Get into menuconfig (cd /usr/src/your-kernel && make menuconfig) and check the following:
{{Box Code|menuconfig|<pre>
Loadable Module Support --->
[*] Enable loadable module support
[*] Module unloading

Processor type and features --->
[*] Enable VM86 support
[*] MTRR (Memory Type Range Register) support

Device Drivers --->
Character Devices --->
<M> /dev/agpgart (AGP Support)
<M> Your_AGP_Chipset_Here
[ ] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)

Graphics support --->
[ ] Support for framebuffer devices

Kernel Hacking --->
[ ] Kernel debugging
</pre>
}}
Sync your kernel menuconfig with the selected portions posted here. (note: you can compile /dev/agpgart & your agp chipset [most likely ati-agp] into the kernel if you want.)

'''Please be aware that -mm and -rc(1,2,3,4,...) kernels often break fglrx due to unexpected changes in syntax, etc. If you want to use ati-drivers, use the stock gentoo-sources or at the very least, a STABLE 2.4 or 2.6 kernel!'''

Don't forget to compile, install, and reboot into the kernel. Directions for this are beyond the scope of this file; if you need help recompiling the kernel, [http://gentoo-wiki.com/HOWTO_Compile_a_Kernel_Manually click here].

== Grabbing a Driver Set ==

For installation it will be easier to drop out of X to a command prompt. Do this using whatever command your Window Manager uses.
I use fluxbox so it's just rightclick -> fluxbox menu -> exit. For KDE or GNOME it's probably just a matter of logging out. When all else fails, hit CTL+ALT+BACKSPACE to kill the X server ungracefully. If the X server only reboots or for some reason you've disabled this hotkey, log in as root and type '''init 3''' to bring the system run level down.

There is also the possibility to stop the xdm service by entering ''/etc/init.d/xdm stop'' as root.

Thanks to portage, installing the drivers is easy. If you have not already done it recently, start by synchronising your portage tree:

emerge --sync

Getting the latest drivers will probably mean unmasking them.

echo "x11-drivers/ati-drivers ~arch" >> /etc/portage/package.keywords
echo "x11-drivers/ati-drivers-extra ~arch" >> /etc/portage/package.keywords

Replace {{Codeline|<~arch>}} with your system architecture; it's going to be either {{Codeline|~x86}} or {{Codeline|~amd64}}, the only two CPU architectures supported by the ATI driver.

Now let's install the drivers. ati-drivers-extra is a (god-awful) control panel for the driver you probably won't use; you can leave that part out if you want, but for completeness we mention it here.

su -
emerge -av ati-drivers ati-drivers-extra

The next step is switch to the ATi OpenGL subsytem:

(#opengl-update ati)
eselect opengl set ati
(very important!)(opengl-update is deprecated)
Configure X:
First, make a standard config file.

xorgconfig

For a single screen

aticonfig --initial --input=/etc/X11/xorg.conf

For a dual head, second screen is {left|right|above|below}

aticonfig --initial=dual-head --input=/etc/X11/xorg.conf --screen-layout={left|right|above|below}

Adapt input with your path to xorg's conf file

If for some reason this command doesn't work, then try manually executing from its default location:

/opt/ati/bin/aticonfig [...]

Now, let's get back into X.

startx

Open up a command prompt and run:

fglrxinfo

If the OpenGL vendor string says "ATI Technologies," then congrats! You've got the drivers working and hardware acceleration going great. If not...read on...

== Troubleshooting ==

=== Config Files ===
By default, the driver uses the Internal AGPGART. Sometimes the internal one doesn't work, and you will have to use the one provided with the kernel. Search your xorg.conf for the line that has the option "UseInternalAGPGART." Simply change the "yes" to "no."

{{Box File|xorg.conf|
Option "UseInternalAGPGART" "no"
}}

Now simply add the modules to {{Filename|/etc/modules.autoload.d/kernel-2.x}} where x is your kernel version.

Add the following (ORDER IS VERY IMPORTANT);
{{Box File|/etc/modules.autoload.d/kernel-2.x|
agpgart
intel-agp # change intel-agp to your chipset. eg: via-agp, nvidia-agp sis-agp.
fglrx
}}

Finally, run

modules-update

Then you can reboot and everything should work. If you have are having problems, check dmesg and /var/log/Xorg.0.log for more info.

=== Blank screen or monitor turning off after startx ===

Versions of ati-drivers >= 8.16.20 have an issue with this that's easily corrected by inserting:
{{Box File|xorg.conf|
Option "ForceMonitors" "notv"
}}
in the device section of xorg.conf (discussed here: http://bugs.gentoo.org/show_bug.cgi?id=103028)

Check if you have a non-DDC monitor connected via VGA/HD15 connector. If so change your xorg.conf:
{{Box File|xorg.conf|
# Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "NONE, CRT"
Option "IgnoreEDID" "off"
Option "HSync2" "30-85"
Option "VRefresh2" "50-160"
# Option "ScreenOverlap" "0"
}}
where HSync2 and VRefresh2 are your monitor parameters.

Also, try changing the MonitorLayout option. The default is "AUTO, AUTO", which is to say X will attempt to autodetect what kind of monitor you've got on the first and second display heads. This can theoretically fail (though I have never observed it). Try changing it around a bit. For example, if you have an LCD and no secondary monitor, change the line to read:

{{Box File|xorg.conf|
Option "MonitorLayout" "TMDS, NONE"
}}

if you have a CRT, simply replace "TMDS" with "CRT".

=== Crashes on startup ===
'''If you are unable to use any 3d applications and get this error instead:'''

FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!

'''Then you do not have tmpfs mounted on /dev/shm, which the driver requires.''' Make yourself sure you have tmpfs support compiled into kernel. It's under

File systems -->
Pseudo filesystems -->
[*] Virtual memory file system support (former shm fs)

To mount this, add to following line to {{filename|/etc/fstab}} (if it isn't there already):

{{Box File|/etc/fstab|
tmpfs /dev/shm tmpfs defaults 0 0
}}

Then just do a:
mount /dev/shm

If the drivers still crap out on you, or for example you get a black screen on X init, try going into your system BIOS and change graphics-related stuff around. Believe it or not, for me my 9800 gives a black screen on X init if I have the AGP Aperture set at anything other than 128MB. I don't know what causes this, and I don't care; I'm just relating to you how I overcame ''my'' problem ;)

Also, '''whenever you update your compiler''', you '''must''' recompile your kernel otherwise you won't be able to insert the fglrx module. Note that recompiling your kernel means you must also unmerge/emerge ati-drivers!

=== Duplicate symbol errors in X log ===
If you are unable to start X or X fails to load the fglrx driver and you have multiple symbol errors in your Xorg log, chances are that you have compiled X with the ''dlloader'' flag. This flag can not be used with the fglrx driver. To fix this problem, remove the dlloader flag by editing your /etc/portage/package.use file as follows:
{{Box File|/etc/portage/package.use|
x11-base/xorg-x11 -dlloader
}}
Now re-emerge the ''xorg-x11'' package and reinstall the fglrx driver.

=== Crashes on the exit of X.org / X won't shutdown ===
Perform the following if you can get the fglrx drivers working with hardware acceleration, but are suffering from a complete system crash when trying to quit X. You should boot into your system, login, then start on this. You don't need to boot into X, and shouldn't need to edit your xorg.conf file (as fglrx is already setup as the driver and working)

You've emerged the "stable" version of the ati-drivers, these are out of date -- remove them (emerge --unmerge ati-drivers), to add the most recent you should either add them to the keywords file (/etc/portage/package.keywords) or emerge your local ebuild (emerge /usr/portage/x11-drivers/ati-drivers/ati-drivers-8.22.5.ebuild) if you're told it requires a dependency, emerge the local e-build for that, then try again. (usually eselect-opengl is required.)
Once you have the most recent ati-drivers emerged, run (eselect opengl set ati). Now you can (startx) and hopefully quit without any problems.

=== glxinfo says "error: failed to open DRM: Operation not permitted" ===
If a check with the glxinfo fails for ordinary users though works fine for root it might be related to filepermissions of the device-file.
Here is how to solve it:

Make sure that the filepermissions on the card-device allows the video-group to read and write. The common group in gentoo with X is "video". All normal users should be part of this group. Also, the device must have permissions for this group to read and write the card-device.

Check the permissions on the card-device:

root:/#ls -lcF /dev/dri/card0

crw-rw---- 1 root root 226, 0 Oct 5 16:19 /dev/dri/card0

It can be changed with:

root:/dev/dri#chgrp video card0

Check if user is part of video:

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),80(cdrw),85(usb),100(users),35(games)

To add a user to the video-group:

root:~#gpasswd -a my_user video

paddlaren:~>id paddlaren

uid=1000(paddlaren) gid=1000(paddlaren)

groups=1000(paddlaren),10(wheel),11(floppy),18(audio),19(cdrom),27(video),80(cdrw),85(usb),100(users),35(games)

Logoff and on to ensure that the membership of the group is known to the system.

== See Also ==

*[http://ati.cchtml.com/ ATi Unofficial Bugzilla (occasionally monitored by ATi personnel)]
*Check out user Wedge_'s excellent ATI Radeon [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html FAQ here]

[[Category:Installation Documentation]]

Gentoo

2008-04-12T17:50:32Z

Akhuettel:

== General Status ==
* Included with Distribution
See the [http://packages2.gentoo.org/package/ati-drivers webindex of the Gentoo package repository] for stable/unstable status of the package.
It may be useful to use the keyword ~x86 specifically for the x11-drivers/ati-drivers package to get the newest version, since the Gentoo stable / unstable distinction does not always make much sense here.

==Installation==
* [[Gentoo Installation Guide|Installation Guide]]

==Tips and Tricks==
* Although not supported by ATI, Compiz-Fusion does work (a bit slow though). Valuable information can be found at the following URL's:
** ... (work in progress)

==Related Resources==
* [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo Wiki]

{{VCT}}
[[Category:Distributions]]

Troubleshooting

2008-04-10T21:00:07Z

Akhuettel: /* No high-resolution video modes available */

==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:

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 ===
* 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.))

==References==
<references/>

[[Category:Installation Documentation]]

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

User:Akhuettel

2008-04-10T20:56:26Z

Akhuettel:

I'm a (mostly) happy user of a Linux-only (Gentoo) IBM Thinkpad T43.

Currently I'm running Compiz-Fusion 0.6.1... :-) which kind of proves that the fglrx driver works. Performance is not so great though, possibly because of the indirect rendering required, and stability also remains desired. Without Compiz, just using KDE, the fglrx driver (8-3) is rock stable and fast!

Note to ATI: please, please, please implement GLX_EXT_texture_from_pixmap!!!

For more information about me,
please visit my [http://www.akhuettel.de/research/ work homepage] or my [http://www.akhuettel.de/ personal homepage].

IBM

2008-04-10T20:52:08Z

Akhuettel:

IBM has sold the PC business unit to [[Lenovo]].

===Workstations===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|Intellistation zPro
|FireGL V3100, FireGL V7100
|Works
|-
|}

===Laptops===

{|border="1" cellpadding="4"
!Model
!Graphics
!Status
!Distributions
!Notes
|-
|ThinkPad T42
|Radeon Mobility 9600
|Works
|openSUSE 10.2
|-
|ThinkPad T42
|Radeon Mobility 9600
|Works - No AIGLX Yet
|Ubuntu 7.10
|Good OpenGL, Relatively Stable
|-
|ThinkPad T43
|Radeon Mobility X300
|Works
|Gentoo (10/Apr/08)
|Good OpenGL, Compiz works
|-
|ThinkPad T43p
|MOBILITY FireGL V3200
|Works
|-
|ThinkPad T60
|Radeon Mobility X1300
|Works
|Gentoo 2007.0
|-
|ThinkPad Z61m
|Radeon Mobility X1400
|Works
|openSUSE 10.2
|Some tinkering in xorg.conf is needed
|-}

===Resources===

[http://thinkwiki.org/ ThinkWiki Community Page]

[[Category:OEMs]]

User:Akhuettel

2008-01-29T08:39:55Z

Akhuettel:

I'm a (mostly) happy user of a Linux-only (SuSE 10.0) IBM Thinkpad T43.

Recently I tried to switch from the X.org "radeon" driver to the proprietary "fglrx" driver, which induced some frustration. Giving up on this now since SuSE 10.0 and its glibc are not supported by the driver anymore. Should I sometime in the far future perform some overall linux update, I'll maybe try again. But for now...

For more information about me,
please visit my [http://www.akhuettel.de/research/ work homepage] or my [http://www.akhuettel.de/ personal homepage].

Troubleshooting

2008-01-29T08:36:56Z

Akhuettel: /* No high-resolution video modes available */

==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>

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.

*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.

=== 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].

=== 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.

=== 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.

=== 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.

=== 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 of 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.

==References==
<references/>

[[Category:Installation Documentation]]

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

Catalyst 7.12

2008-01-04T13:20:01Z

Akhuettel: /* Known Issues (according to the release notes) */

ATI Catalyst Linux 7.12 driver

Release date: 20 December, 2007

The driver contains lots of bugfixes. Finally suspend/hibernate works with SLUB.

==New Features (according to the release notes)==
*This release of the ATI Catalyst™ Linux driver introduces support for the following new operating systems:

* Red Flag DT 6.0 Support
* OpenSUSE 10.3 Support

==Resolved Issues (according to the release notes)==
* A memory leak is no longer noticed when running OpenGL applications
* Running X -configure no longer results in a segmentation fault in the fglrx driver
* fglrxinfo no longer reports OpenGL Render string: as Mesa GLX Indirect on systems containing an ATI Rialto AGP series of product

==Known Issues (according to the release notes)==
* There is no support for video playback on the second head in dual head mode. Further details can be found in topic number 737-26985
* Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578
* A black screen may be observed on some hardware when switching to the console or leaving the X window system when a Vesa framebuffer console driver is used. Further details can be found in topic number 737-30687
* Corruption may be noticed in the lower right corner of the display after the system is running for a long period of time
* Display flicker may be noticed when the gnome screen-saver starts
* Diagonal tearing may be noticed when playing a video file using a video player that utilizes the XVideo extension
* Video playback may look blocky when playing a video file using a video player that utilizes the XVideo extension
* Video Playback may display wrong colors and additional shadow images when cropping or expanding a video file using a video player that utilizes the XVideo extension
* Connecting a display device that supports 1680x1050 to a system running Linux may result in a maximum display resolution of 1280x1024 only being available
* Custom mode lines in xorg.conf may be ignored by the fglrx driver
* Building RPM packages for Mandriva may fail

Some of the issues are the same issues that have been plaguing the driver, just finally acknowledged. The one about the 1680x1050 resolution is true, accept when I tried the driver I could only get 1024x768.

Similar issues have also been observed with a Thinkpad T43; the native resolution of 1400x1050 cannot be used, and even if it is the only mode defined in xorg.conf, the display starts up with 1280x1024. ([[User:Akhuettel|Akhuettel]])

==External links==

* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-8.443.1-x86.x86_64.run Installer]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_712_linux.html Release notes]
* [https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/linux_cat712-inst.html Installer Instructions]
* [http://ati.amd.com/products/catalyst/linux.html ATI Proprietary Linux Driver FAQ]
[[Category:Releases]]

Troubleshooting

2008-01-03T13:04:07Z

Akhuettel: /* X Server 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 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>

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.

*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.

=== 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.

==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.

=== 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.

=== 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].

=== 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.

=== 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.

=== 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.

=== 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 of 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.

==References==
<references/>

[[Category:Installation Documentation]]

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

User:Akhuettel

2008-01-03T12:56:00Z

Akhuettel: New page: I'm a (mostly) happy user of a Linux-only (SuSE 10.0) IBM Thinkpad T43. Recently I switched from the X.org "radeon" driver to the proprietary "fglrx" driver, which induced some frustration...

I'm a (mostly) happy user of a Linux-only (SuSE 10.0) IBM Thinkpad T43. Recently I switched from the X.org "radeon" driver to the proprietary "fglrx" driver, which induced some frustration...

For more information about me,
please visit my [http://www.akhuettel.de/research/ work homepage] or my [http://www.akhuettel.de/ personal homepage].