ThinkWiki - User contributions [en]

ATI Mobility FireGL V5200

2009-05-01T02:44:56Z

Milli:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support have been added by the xorg driver developers and the driver is used by all majos distributions. The driver can be considered stable and fully supports Suspend-To-Disk and Suspend-To-RAM as well as XVideo acceleration in combination with composite extensions (compiz).

In addition to the radeon driver the card is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development and does not work satisfactorily on the T60p.

Recent releases of the ATI proprietary driver do not support this card anymore. Ever since ATI has been bought by AMD the specs for this card have been released to driver developers.

==== ThinkPad LCD ====

All current distributions offer full support for the 1600x1200 resolution of the screen.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===

'''The following information is outdated only relevant if you use an older distribution.
'''

Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu 8.10 (Intrepid) using RadeonHD driver ===

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed Intrepid. However, as of this writing, the version included is 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

['''Update 30-Apr-09''': Keeping pace with new development, I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.5-1~pre1_i386.deb build of v1.2.5 available]''' which seems to be more stable than 1.2.3 with recent xorg 1.5.2 updates, under which I've started having spurious hangs using xv apps and crashes on resume from suspend. v1.2.5 seems to fix these, so far...]

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== Ubuntu 9.04 (Jaunty) using RadeonHD driver ===

Version 1.2.4 of the radeonhd driver is included in the Jaunty release and should work fine.

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

ATI Mobility FireGL V5200

2009-05-01T02:38:28Z

Milli: /* Ubuntu 8.10 (Intrepid) using RadeonHD driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support have been added by the xorg driver developers and the driver is used by all majos distributions. The driver can be considered stable and fully supports Suspend-To-Disk and Suspend-To-RAM as well as XVideo acceleration in combination with composite extensions (compiz).

In addition to the radeon driver the card is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development and does not work satisfactorily on the T60p.

Recent releases of the ATI proprietary driver do not support this card anymore. Ever since ATI has been bought by AMD the specs for this card have been released to driver developers.

==== ThinkPad LCD ====

All current distributions offer full support for the 1600x1200 resolution of the screen.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===

'''The following information is outdated only relevant if you use an older distribution.
'''

Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu 8.10 (Intrepid) using RadeonHD driver ===

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed Intrepid. However, as of this writing, the version included is 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

['''Update 30-Apr-09''': Keeping pace with new development, I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.5-1~pre1_i386.deb build of v1.2.5 available]''' which seems to be more stable than 1.2.3 under which I've had spurious hangs using xv apps and crashes on resume from suspend. v1.2.5 seems to fix these, so far...]

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

ATI Mobility FireGL V5200

2008-11-06T23:17:11Z

Milli: /* Ubuntu Intrepid using RadeonHD driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support are still under development but should be available within 2008.
Ubuntu 8.04 uses this driver by default.

It is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.
There is also a Gentoo ebuild recently added to the tree (x11-drivers/xf86-video-radeonhd), which seems to be working without any problems.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu 8.10 (Intrepid) using RadeonHD driver ===

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed Intrepid. However, as of this writing, the version included is 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

ATI Mobility FireGL V5200

2008-11-06T23:15:30Z

Milli: /* Ubuntu Intrepid using RadeonHD driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support are still under development but should be available within 2008.
Ubuntu 8.04 uses this driver by default.

It is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.
There is also a Gentoo ebuild recently added to the tree (x11-drivers/xf86-video-radeonhd), which seems to be working without any problems.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu Intrepid using RadeonHD driver ===

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed the Intrepid Beta. However, as of this writing, the Beta includes version 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

ATI Mobility FireGL V5200

2008-10-15T08:23:40Z

Milli: /* Ubuntu Intrepid using RadeonHD driver */

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support are still under development but should be available within 2008.
Ubuntu 8.04 uses this driver by default.

It is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.
There is also a Gentoo ebuild recently added to the tree (x11-drivers/xf86-video-radeonhd), which seems to be working without any problems.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu Intrepid using RadeonHD driver ===

{{NOTE|Interpid is in Beta as of this writing (15-Oct-2008)}}

The RadeonHD driver is coming along and is very usable for 2D graphics, and now with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is there (XVideo extenstion works)! I have experienced no suspend/resume issues at all with this driver, so no caveats there.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed the Intrepid Beta. However, as of this writing, the Beta includes version 1.2.1 of the driver which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. DRI in the driver is still off by default. And you can choose to not include the AccelMethod option, I've just found EXA to be faster than XAA (the default).

In previous versions of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections of xorg.conf, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similar to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

Then you type "update-grub" as root to update the kernel boot params with this new info. Mode 835 is 1400x1050 at 256 color depth. There are lots of other options, use "vga=ask" instead and reboot to find out what they are for your specific screen.

Note that you can't have "splash" on this line as the splash boot screen will mess up the console so that it becomes unusable, that is, a blank screen if you switch to any console. (Other suggestions for ways to deal with the boot console welcome.)

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

ATI Mobility FireGL V5200

2008-10-15T08:15:54Z

Milli:

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">

This is an ATI video adapter

== Features ==
* Chipset: ATI M56 - Similar to Radeon X1600
* PCI ID: 1002:71c4
* PCI Express x16
* 256 MB GDDR3-SDRAM video memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
Initial support included in the stable branch of the Xorg [[radeon]] driver (2D only). XVideo acceleration and 3D support are still under development but should be available within 2008.
Ubuntu 8.04 uses this driver by default.

It is also supported by the [[radeonhd]] driver. A Debian package already exists in the experimental branch. 3d is still under development.
There is also a Gentoo ebuild recently added to the tree (x11-drivers/xf86-video-radeonhd), which seems to be working without any problems.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correctly. Changing the driver from "ati" to "vesa" in xorg.conf will start X but with a lower resolution than expected.

Full resolution can be achieved when all modelines are removed and mode 1600x1200 with depth 24 is selected.

==== External VGA port ====
Yes

==== SVideo port ====
No

==== DVI port ====
No (yes on Docking Station, working with [[fglrx]] driver

=== Proprietary ATI driver ===
Proprietary [[fglrx]] driver works since version 8.25.18, version 8.24.8 works by adding "ChipID 0x71c5" to the xorg.conf "Device" statement and fooling it into thinking it's a X1600 mobility (do this only as a last resort or if you're sure you have an older driver; it is fatal to version 8.25.18).

The new driver 8.25.18 seems to support the card, see
https://support.ati.com/ics/support/KBAnswer.asp?questionID=1643
(successfully tested with the provided autorun installation script on OpenSuSE 10.1, T60p with 15" display).

(K)ubuntu 6.06 comes with this driver and it works out of the box. However, it seems to have problems with VT Switching (Alt+Fn). Instead of switching to a console, X resets and goes back to the log in screen (This doesn't happen when using the [[vesa]] driver). The switching issue might be resolvable by setting ENABLE_LAPTOP_MODE=true in /etc/default/acpi-support, but it doesn't seem to help on all systems.

{{NOTE|On Ubuntu 6.10 (Edgy) with 'splash' on the command line, you cannot switch to VTs. This is a Thinkpad T60. The screen remains graphical, but is very badly garbled. There is no text. X does not reset, and you can switch back to your X session. The solution is to include 'vga-791' or to remove 'splash' from the grub or lilo command line. You don't need to do both. (It's been a few days, so I don't remember where I found this...I just chanced upon this wiki page for the video card I'm trying to get working with xgl/AIGLX and Beryl).}}

Also, the pointer gets garbled sometimes in X, but this is only a minor annoyance. Dual Head (Xinerama) also works with this driver, but don't use KDE control center to enable it (use the ATi tool or edit xorg.conf manually)

I have a feeling that this card gets in the way when trying to suspend to RAM (resuming with a complete blank screen, lights are blinking, but that's it), but this can also be caused by other means.

=== Proprietary ATI driver on Ubuntu Feisty ===
I had a hard time getting resume from suspend-to-ram to work with Feisty on a Thinkpad T60p. When resuming, the screen just went black with X hanging.

It works like this:
# In <code>/etc/acpi/sleep.sh</code>, as second line, add the line <code>sudo chvt 1</code>. This forces a switch to the text console before standby.
# Likewise, in add to the very end of the file <code>/etc/acpi/resume.sh</code> the line <code>sudo chvt 7</code>.
# Finally, the perhaps most important change goes into <code>/etc/default/acpi-support</code>. Change the line <code>POST_VIDEO=true</code> to read <code>POST_VIDEO=</code>. This was the point when it started working on my system.

:'''NOTE:''' Step 3. above was the only change '''I''' needed to make. YMMV. --[[User:Brianfinley|Brian E. Finley]] 23:26, 30 March 2007 (CEST)

:'''NOTE:''' With only Step 3. above, my T60p would not even suspend when docked. Step 3. above was sufficient to make resume work for me when my laptop was not in its docking station. However, when I subsequently docked the machine I saw something I thought was banished with my upgrade to a 2.6.20 kernel: it uncermoniously powered off the instant it was docked, almost as though someone threw a hardware switch. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 12 11:18:22 EDT 2007

:'''UPDATE:''' The problems mentioned above related to docking seem to happen when I use the gnome-power-manager applet menu but not when I use the suspend function in the window that results from clicking the "Log Out Button" applet. When I use the latter, suspend-to-RAM seems to work right, consistently. I'm [https://bugs.launchpad.net/ubuntu/+bug/107674 following up with Ubuntu] on this point. --[[User:dave_abrahams|Dave Abrahams]] Thu Apr 19 11:53 GMT 2007

:'''NOTE:''' Editing <code>/etc/acpi/sleep.sh</code> and <code>/etc/acpi/resume.sh</code> is not necessary, as there is an option in <code>/etc/default/acpi-support</code> for ''that very feature'': Just set the commented out DOUBLE_CONSOLE_SWITCH=true, and it will do the console switch suggested automatically. --[[User:Webograph|Webograph]] 12:43, 29 August 2007 (UTC)

:'''NOTE:''' I also had success doing nothing more than setting <code>POST_VIDEO=false</code> (step 3). Using a T60p (2007-83U) with fglrx 8.3 (8.47.3-3~bpo40 from Debian's etch-backports) --[[User:sihde|Steve Ihde]] 31 May 2008

For completeness, here are the complete settings of this file:
<ol>
<li>ACPI_SLEEP=true</li>
<li>ACPI_HIBERNATE=true</li>
<li>ACPI_SLEEP_MODE=mem</li>
<li>MODULES=""</li>
<li>MODULE_WHITELIST=""</li>
<li>SAVE_VBE_STATE=true</li>
<li>VBE_STATE=/var/lib/acpi_support/vbestate</li>
<li>POST_VIDEO=</li>
<li>USE_DPMS=true</li>
<li># RADEON_LIGHT=true</li>
<li># DOUBLE_CONSOLE_SWITCH=true</li>
<li>HIBERNATE_MODE=shutdown</li>
<li>LOCK_SCREEN=true</li>
<li># DISABLE_DMA=true</li>
<li># RESET_DRIVE=true</li>
<li>STOP_SERVICES="mysql "</li>
<li>RESTART_IRDA=false</li>
<li>ENABLE_LAPTOP_MODE=true</li>
</ol>

Point 11 may eventually replace the chvt settings above, but I didn't try.

=== Ubuntu Hardy ===
Suspend/hibernate seems to work in Hardy with latest Catalyst driver out of box (no need to edit any conf files!). The only confusing thing is that it goes to sleep and hibernate pretty fast, but it takes a long time to resume from both, especially from hibernate. The first impression that it hangs, but it's not.

=== Linux kernel Framebuffer driver ===

Supported by the [http://dev.gentoo.org/~spock/projects/vesafb-tng/ vesafb-tng] project, but requires the boot parameter {{bootparm|video|vesafb:nocrtc}}.

Alternatively, you may use classic vesafb with {{bootparm|vga|838}} for a 1400x1050 screen with 32 bit color depth.

{{NOTE|The [[fglrx]] driver may cause distortion/corruption of the framebuffer after use at high resolutions, making the text difficult to read.}}

=== Ubuntu Intrepid using RadeonHD driver ===

{{NOTE|Interpid is in Beta as of this writing (15-Oct-2008)}}

The RadeonHD driver is coming along and is very usable for 2D graphics, and with the v1.2.3 release of the driver (not yet in the Intrepid repos), 3D support is now there (XVideo extenstion works!) I have also experienced no suspend/resume issues at all with this driver.

The package you need to install is xserver-xorg-video-radeonhd. You probably have this installed already if you've installed the Intrepid Beta. However, as of this writing, it is version 1.2.1 in the Beta which doesn't have the 3D support in it. I have a '''[http://www.acmeps.com/kernel/debs/xserver-xorg-video-radeonhd_1.2.3-1~pre1_i386.deb build of v1.2.3 available]''' (actually git commit 29cd7382, built by dropping the latest bits into the xserver-xorg-video-radeon source package and building) to use until Intrepid has updated packages.

Just a few configuration nits.

/etc/X11/xorg.conf snippet:

Section "Device"
Identifier "LCD ATI Radeon Graphics Adapter"
Driver "radeonhd"
Option "AccelMethod" "exa"
Option "DRI" "true"
BusID "PCI:1:0:0"
EndSection

You have to at least turn on DRI so the right plumbing gets hooked up for the 3D graphics. And you can choose to not use the AccelMethod of EXA, I've found it to be faster than XAA.

In previous version of the driver you had to turn off both Composite and AIGLX. It appears you no longer need to do that, so if you have those in your Extensions or ServerFlags sections, you can remove them.

There is a caveat, however, to get the kernel (2.6.27) to behave properly with a graphics console (i.e., what you get if you hit CTRL-ALT-F1). Similary to the above comment about using a framebuffer, you have to edit /boot/grub/menu.lst and change the defoptions line to something like:

# defoptions=video=vesafb vga=835

But you can't leave "splash" on this line as the splash boot screen will mess up the console so you can't use it (can't even see it). (Other suggestions for ways to deal with the boot console welcome.) Then you type "update-grub" as root to update the kernel boot params with this new info.

=== ThinkPads this chip may be found in ===
* {{T60p}}
* {{Z61p}}

[[Category:Components]]

Problems with fglrx

2007-02-15T21:26:28Z

Milli: /* Cannot switch to VT */

This page discusses issues with the ATI proprietary [[fglrx]] display driver.

== Known Troubles and Solutions ==

=== X-specific issues ===

ATI proprietary drivers version 8.21.7 and later work with x.org 6.9.

If you are running an older version (8.20.8) under Debian sid and you upgrade your xserver-xorg, apt will force you to remove any debian-packaged fglrx drivers (package fglrx-driver depends on x.org << 6.8.99). You can just download the driver from the ATI site and install after modifying the Debian packager script to allow dependencies to be satisfied by x.org 6.9, or just download 8.21.7 and install manually. See talk page for step-by-step commands.

After installing the fglrx driver, you can use module-assist to build the appropriate kernel module.

=== Kernel-specific troubles ===

Using ATI drivers <=8.21.7 with kernel >=2.6.15 needs a [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]. (see table below for detail.) If you can't compile the driver modules with 2.6.15 or later, you should apply this [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch patch] instead.

If you do not use one of these patches, you may experience peculiar lockups of X. Try {{cmduser|fglrxinfo}} - if your shell hangs at the end of this command, you may have an issue and should try the patch or upgrade.

Although unproven, there is a substantial amount of user / developer concern that the above patches prevent hard lockups but do not provide full reliability with 2.6.15 and there are larger / redisgn issues preventing compatibility. These issues have been fixed with later ATI drivers (> 8.21.7) so you can simply upgrade if you are running a more modern kernel.

=== No hardware acceleration ===

====Acceleration lost after driver update====
If you lose hardware acceleration after a driver update this can be caused by an old fglrx kernel module being loaded.

Check out {{path|1=/var/log/Xorg.0.log}} for a message like:
:<code>(WW) fglrx(0): Kernel Module version does *not* match driver.</code>
:<code>(EE) fglrx(0): incompatible kernel module detected - HW accelerated OpenGL will not work</code>

You can verify this yourself by looking at the version message some lines above. It should read something not matching the installed version like:
:<code>(II) fglrx(0): Kernel Module Version Information:</code>
:<code>(II) fglrx(0): Name: fglrx</code>
:<code>(II) fglrx(0): Version: 8.10.19</code>

The cause for this trouble might be that there resist multiple versions of the fglrx module within the kernel module search path.<br>
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}.<br>
If grep finds multiple lines you nailed down the problem. All you have to do now is to delete any versions of the module (look at the filedate) but the most current one. Then run {{cmdroot|1=depmod}} and you are done.

{{HINT|Newer versions (8.21.7) of the fglrx module seem to be installed in the <code>extra/</code> subdirectory.<br>
Older versions (8.19.10) used to be located in the <code>kernel/drivers/char/drm/</code> subdirectory.}}

====GCC 3.4====
If the ATI driver works only without the hardware acceleration, take into consideration that {{path|fglrx_dri.so}} was linked against libstdc++.so.5 which may not be present if your system uses gcc-3.4.

To fix this, compile gcc-3.3.5 and copy <tt>libstdc++.so.5*</tt> to {{path|/usr/lib}} and update the dynamic linker cache via {{cmdroot|ldconfig}}.

Or install a compat package for your favorite distro. FC4 users can do:
:{{cmdroot|yum install libstdc++.so.5}}

====radeonfb framebuffer====
Another possible cause for broken hardware acceleration (2D and 3D) is the radeonfb framebuffer: Switching to vesafb or vesafb-tng is reported to solve the problem on some systems. Also it has proven helpful to not perform {{cmdroot|modprobe fglrx}} after boot but to have the module loaded via {{path|/etc/modules.autoload/kernel2.x}} at boottime instead.

====Perpetual Mesa GLX Indirect on Debian====
If you've done everything right and you're still seeing:

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

try this:

:{{cmdroot|mkdir -p /usr/X11R6/lib/modules/dri}}
:{{cmdroot|ln -s /usr/lib/dri/fglrx_dri.so /usr/X11R6/lib/modules/dri}}

Thanks to Maciej Matysiak for the clear debug [http://lists.debian.org/debian-amd64/2006/02/msg00217.html here] and solution [http://lists.debian.org/debian-amd64/2006/02/msg00311.html here].

More generally, use LIBGL_DEBUG=verbose fglrxinfo, to see what's happening, and whether you get this:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL error: dlopen /usr/X11R6/lib/modules/dri/fglrx_dri.so failed (/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory)}}
:{{cmdresult|libGL error: unable to find driver: fglrx_dri.so}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: Mesa project: www.mesa3d.org}}
:{{cmdresult|OpenGL renderer string: Mesa GLX Indirect}}
:{{cmdresult|OpenGL version string: 1.2 (1.5 Mesa 6.4.2)}}

instead of that:
:{{cmduser|<nowiki>LIBGL_DEBUG=verbose</nowiki> fglrxinfo}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so}}
:{{cmdresult|libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)}}
:{{cmdresult|drmOpenByBusid: busid is PCI:1:0:0}}
:{{cmdresult|drmOpenDevice: minor is 0}}
:{{cmdresult|drmOpenDevice: node name is /dev/dri/card0}}
:{{cmdresult|drmOpenDevice: open result is 4, (OK)}}
:{{cmdresult|drmOpenByBusid: drmOpenMinor returns 4}}
:{{cmdresult|drmOpenByBusid: drmGetBusid reports PCI:1:0:0}}
:{{cmdresult|Can't open configuration file /home/merlin/.drirc: No such file or directory.}}
:{{cmdresult|fglrx: DPD supported.}}
:{{cmdresult|display: :0.0 screen: 0}}
:{{cmdresult|OpenGL vendor string: ATI Technologies Inc.}}
:{{cmdresult|OpenGL renderer string: MOBILITY FIREGL T2 Pentium 4 (SSE2) (FireGL) (GNU_ICD)}}
:{{cmdresult|OpenGL version string: 2.0.5879 (8.26.18)}}

I have contacted ATI to add that info by default, the mesa guys to do that in glxinfo too, as well as the debian packager to fix the debian packaging bug (2006/07/22), so hopefully the situation will improve soon

You may have to run fglrxinfo as root to get this detail rather than a useless message.

=== Softlink hell ===
The [[fglrx]] installer replaces the standard X.org OpenGL implementation (Mesa) with its own files, potentially causing collisions with the distribution's file and package management. It is best to install the driver via a package built for your distribution, which will typically include the necessary kludges to make things work. See the [[fglrx]] page for pointers.

====Discussion====
If using {{cmduser|fglrxinfo}} after installing [[fglrx]] indicates that you are still using the mesa indirect software GL renderer, you likely have some misplaced softlinks. It seems like it has to do with an apt-get upgrade that sometimes replaces these links. Anyway, go to
:{{cmdroot|cd /usr/X11R6/lib}}
and list your GL libraries and links
:{{cmdroot|ls -la *GL*}}
You should see something like the following two lines amoung others:
:{{cmdresult|libGL.so -> libGL.so.1.2}}
:{{cmdresult|libGL.so.1 -> libGL.so.1.2}}
If you see a link to a mesa library (something like {{cmdresult|... -> libGL.mesa.1.2}}), then that's your problem! Restore the softlink like this (use your actual library version, though):
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}

For some reason, this link might "break" later, giving you the software rendering once more. Even after renaming the mesa library to something like <tt>mesa.bkup</tt>, the system might still find it and link to it despite the name change. If you have to do this a lot, you could write a restoreGL script.

=====Gentoo=====
{{Gentoo}} has built in tools for managing the OpenGL symlinks. They seem to be replacing the old tool with a new one, so one of the following should work for you:
:{{cmdroot|opengl-update ati}} or
:{{cmdroot|eselect opengl set ati}}
Eselect is new, and still ~x86 (as of the end of 2005), so you may not have it yet. <tt>opengl-update</tt> is the old tried-and-true method for managing the symlinks. If <tt>opengl-update</tt> doesn't fix it for you, you should probably tell [http://bugs.gentoo.org Gentoo Bugzilla] (assuming they don't know yet).

If {{cmdroot|ldd /usr/X11R6/bin/glxinfo}} shows that your system still uses the xorg-x11 mesa libs after trying one of the above commands, i.e. a line like this:
:{{cmdresult|1=libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0x400a8000)}}
you will also need to relink {{path|libGl.so.1.2}}:
:{{cmdroot|cd /usr/lib/opengl/xorg-x11/lib/}}
:{{cmdroot|mv libGL.so.1.2 libGL.so.1.2_backup}}
:{{cmdroot|ln -s /usr/lib/libGL.so.1.2 libGL.so.1.2}}
After another restart of X {{cmduser|fglrxinfo}} should show that it's using the right libs now.

=====Debian=====

:{{cmdroot|rm /usr/lib/libGL.so*}}
:{{cmdroot|rm /usr/X11R6/lib/libGL.so*}}
:{{cmdroot|cd /usr/X11R6/lib}}
:{{cmdroot|cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .}}
:{{cmdroot|ln -s libGL.so.1.2 libGL.so.1}}
:{{cmdroot|ldconfig}}

=== Troubles using software suspend ===
When the computer resumes from suspend, X only displays a garbled image and the computer is frozen.
The problem is acknowledged in ATI's release notes and in knowledge base entry <strike>[https://support.ati.com/ics/support/KBResult.asp?searchFor=Search+Words&search.x=0&search.y=0&searchOption=id&questionID=737-218+&task=knowledge&searchTime=-1&productID=&folderID=-1&resultLimit=50 737-218]</strike> [https://support.ati.com/ics/support/KBAnswer.asp?questionID=218 737-218]. Driver version 8.19.10 has "initial support for Suspend and Resume" but is working very nicely for most people (verified on T43, T43p and T42) without vbetool.

If you are using an older version of fglrx, using [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] to save/restore the video card state before/after suspend worked for some people. If you use [[Software Suspend 2|Software Suspend 2 (suspend2)]] scripts, you can simply uncomment <tt>EnableVbetool yes</tt> in {{path|/etc/hibernate/hibernate.conf}}. Be aware though that it breaks suspend/resume for drivers beginning with version 8.19.10, so remember to disable it again when upgrading.

{| cellspacing="0" cellpadding="2" border="1"
|+ tested with the following configurations
!model!!distro||kernel!!fglrx!!PM!!success!!comments
|-
|{{T42}}||SUSE 9.3||2.6.11||8.14.13||swsusp||yes||
|-
|{{T41p}}||???||2.6.14||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch]
|-
|{{T42p}}||Debian||2.6.10||Debian packaged||suspend2||yes||
|-
|{{T43}}||Debian sid||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 (but not earlier versions!)
|-
|{{T43}}||Debian etch||2.6.14.2||8.19.10||swsusp||yes||works perfectly with 8.19.10 and without vbetool
|-
|{{T43}}||Ubuntu Breezy||2.6.12-10||8.19.10||swsusp||yes||Perfect. (Finally.)
|-
|{{T43}}||FC4||2.6.14.1||8.19.10||suspend2 2.2-rc9||yes||needs a small [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030381.html patch], requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.2||8.19.10||suspend2 2.2-rc11||yes||requires DRI disabled in {{path|xorg.conf}} (hence no 3D acceleration)
|-
|{{T43}}||FC4||2.6.14.3||8.19.10||suspend2 2.2-rc13||no||DRI enabled
|-
|{{T43}}||FC4||2.6.14.3||8.20.8||suspend2 2.2-rc13||no||DRI enabled
|-
|{{R50p}}||???||???||8.19.10||swsusp||yes||
|-
|{{T43p}}||Debian sid||2.6.14||8.19.10||Suspend to RAM||yes||without vbetool or UseDummyXServer, those two ''break'' the resume process here, with DRI enabled
|-
|{{T43p}}||Debian sid||2.6.14.3||8.20.8||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{R52}}||Debian sid||2.6.15-rc5||8.20.8||swsup||yes||both vbetool and UseDummyXServer disabled, DRI enabled, needs [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 patch]
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled - console is garbled until switching back from X
|-
|{{T43p}}||Gentoo||[http://packages.gentoo.org/ebuilds/?suspend2-sources-2.6.15-r6 2.6.15]||8.22.5||suspend2 2.2||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||swsusp||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T43}}||SUSE 10.1||2.6.16||8.25.18||Suspend to RAM||yes||without vbetool or UseDummyXServer, with DRI enabled
|-
|{{T60}}||Gentoo 2006.1||2.6.19-suspend2||8.31.5||Suspend2||yes||Everything works: 3D, suspend-to-disk, suspend-to-ram, suspend in X.org, switching to VT's at any moment. Never needed to unload any modules manually, worked immediately. Fglrx driver 8.32.5 totally broke suspend for me, so i'm sticking with 8.31.5. T60 2008-B62 model.
|-
|{{T60p}}||Kubuntu 6.06||2.6.15||8.25.18||swsusp||no||Switching to VT to suspend: no resume, X restarts; Not switching: suspend works, garbled X display on resume, later X restarts
|-
|{{T60p}}||Kubuntu 6.06 Text Mode||2.6.15||---||swsusp||yes||suspend works in textmode after rmmod fglrx.
|-
|{{T60p}}||Debian/unstable/experimental||2.6.18||8.31.5-1 (from debian experimental)||susptoram hibernate debian packages||yes||suspend and resume works with X, 3D acc., Xv overlay...
|}

=== Troubles with large RAM ===
Version 8.14.13 (and probably earlier versions) of the driver does not seem to be able to cope with large amounts of RAM: with 512 MB it works, with 1.5 GB it crashes the machine as soon as X is started. The problem is present only if the <tt>fglrx</tt> kernel module is loaded, but independently of whether {{kernelconf|CONFIG_HIGHMEM||||||}} is enabled. A workaround is to limit RAM by adding the {{bootparm|mem|864m}} kernel parameter.

Version 8.16.20 fixes the problem.

===Display switching ===
The switching between internal and external display doesn't work with fglrx versions <= 8.24.8, because the driver blocks messing around with the chipset via ACPI. If you want to use this feature (i.e. during presentations), you should use the <tt>vesa</tt> server instead (experienced with a R52, Kernel 2.6.11, xorg 6.8.2, fglrx 8.16.20). Or boot notebook with CRT connected, it will automatically detect it and display on both.

===Composite Support===
ATI has not officially supported composite windowing (alpha channel) enabling hardware acclerated translucent windows (primarily for 'eye candy.') Enabling Composite in KDE and the fglrx driver results in a very pretty desktop but unacceptably slow performance on a T43p with ATI's FireGL T2. It is still unusable in its current state (as of driver 8.25.18).

ATI promises support in the future when composite is officially supported by Xorg. Discussion of current status of drivers can be found in the Rage3d forums' (http://rage3d.com/board) Linux area.

Composite support is now supported with recent Mesa and Xorg > 7 with the open source 3d radeon drivers (if you run debian unstable, you should be all set.) It works with the [[R300]] / FireGL T2 series as found on the T43p, but noticably slows down the system. This has made rapid progress in speed with the latest few releases and kernel 2.6.18, and is finally usable with an R300 based card. Expect drivers to improve in the future, but it seems that composite does require a very fast video card and system.

===Hardlock on X logout===
Up from driver version 8.19.10 you will experience a system hard lock when logging out from X, if the session manager (kdm/gdm) is not properly configured. You have to tell the session manager to restart X.

In the kdm config file (gentoo: {{path|/usr/kde/<VERSION>/share/config/kdm/kdmrc}}) you have to add following to the section <code>[X-:*-Core]</code>:
TerminateServer=true

In the gdm config (/etc/gdm/gdm.conf) file add the following to the daemon-section:
AlwaysRestartServer=true

Information from the ATI bugtracker: http://ati.cchtml.com/show_bug.cgi?id=239

Another reason of hardlock my be using the wrong AGP driver. Make sure that you have proper drivers for your motherboard loaded before fglrx: (gentoo: {{path|/etc/modules.autoload.d/kernel-2.6}}):
intel-agp
fglrx

A common problem seems to be mistakenly using ATI Chipset drivers instead of Intel.

Information from gentoo bugtracker: <s>[http://bugs.gentoo.org/show_bug.cgi?id=113685 113685]</s>. Fixed in 8.25.18

===Cannot switch to VT===

With usplash boot enabled, it may not be possible to switch to a VT from X (Using Alt+Fn). Tested on T60p (Mobility Fire GLV5200) on Ubuntu 6.06 / 6.10 and fglrx 8.25.18 / 8.28.8. Display may become garbled and system might freeze. Solution (testet on Ubuntu 6.10) is to either remove the "splash" kernel boot parameter or add "vga=791" parameter ("vga=794" can be used on 1400x1050 panel).

http://ati.cchtml.com/show_bug.cgi?id=37 <br>
https://launchpad.net/distros/ubuntu/+source/usplash/+bug/63558

===Flickering Display===

Some people have reported problems with their display flickering when using ati-drivers newer than 8.14.13. The problem is unclear
(possibly associated with an incorrect modeline setting) and no known solution exists except to use the open source radeon drivers.
You can follow this problem here: http://ati.cchtml.com/show_bug.cgi?id=248

===Error messages in system log===

If you find something like the following in {{path|/var/log/messages}}:

:{{cmdresult|kernel: mtrr: base(0xc0000000) is not aligned on a size(0x7ff0000) boundary}}
:{{cmdresult|kernel: [fglrx:firegl_addmap] *ERROR* mtrr allocation failed (-22)}}
:{{cmdresult|kernel: [fglrx:firegl_unlock] *ERROR* Process 5132 using kernel context 0}}

try to execute the following line and reload the fglrx module:

:{{cmdroot|1=echo "base=0xd0000000 size=0x8000000 type=write-combining" > /proc/mtrr}}

More detailed instructions can be found [http://ubuntuforums.org/showthread.php?t=115104 here].

===Hang when logging out===

A common problem is that when logging out from X, instead of gettign the KDM or GDM prompt, the system hangs.

This is discussed, including workarounds here: http://ati.cchtml.com/show_bug.cgi?id=239

===No power saving when CRT in use===

When both CRT and LCD are in use, power saving cannot be enabled.

This is reported here: http://ati.cchtml.com/show_bug.cgi?id=304

===WineX / Cedega Installs Software But Errors on Loading Games===

Some users may experience problems with certain FIREGL cards (in my case an ibm t43p laptop with a v3200 ati firegl) whereby projects such as cedega and wine refuse to work with 3d graphics, but native binaries (e.g. quake 4) work fine. A possible workaround is to add the following line in the drivers section of your /etc/X11/xorg.conf

Option "UseFastTLS" "2"

This option used to be configured with the older ati drivers when you ran "fglrxconfig". I have not yet found a way to get it to appear with "aticonfig", hence the manual insertion. This option is good for several linux distros I have tried, fedora core 5, ubuntu dapper and suse 10.1. It does not appear to effect performance on natively run programs.

===Line Appears Below Mouse Cursor===

Some users have reported seeing a line approximately 1 mouse height below the bottom edge of the cursor, which follows the mouse and appears to change color based on the image below the cursor. This has been seen to happen using fglrx without the kernel module installed (in 2D mode) and additionally on external displays or multiple X servers. To work around the problem, try disabling the DGA extension by making the following changes to your XFree86.conf or xorg.conf file. Replace (or comment-out)
Load "extmod"
with
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection

===Freeze while using OpenGL Apps===

Some OpenGL applications such as screensavers or games (SecondLife) cause freezes. The cursor still moves, but otherwise the machine is unresponsive. This is the case with Xorg 7.1 and fglrx 8.29.6 using an x1400 and other cards. The solution is to add the following options to the video Device section in xorg.conf:
Option "Capabilities" "0x00000800"
Option "KernelModuleParm" "locked-userpages=0"

== Patches ==
The following patches might be needed for certain versions of fglrx.

===fglrx 8.32.5===
* [http://whoopie.gmxhome.de/linux/patches/2.6.19/fglrx-8.32.5-for-2.6.19.patch For kernel 2.6.19]

===fglrx 8.23.7===
* For kernel 2.6.16: [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.22.5-intermodule.patch <tt>intermodule</tt> patch] and [http://mirror.espri.arizona.edu/gentoo/rsync/x11-drivers/ati-drivers/files/ati-drivers-8.23.7-noiommu.patch <tt>noiommu</tt> patch]

===fglrx 8.21.7===

* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx 8.20.8===

* [http://marc.theaimsgroup.com/?l=linux-kernel&m=113429835515001&w=2 for kernel 2.6.15]
or
* [http://www.ksp.sk/~rasto/fglrx_with_2.6.15.patch for kernels >= 2.6.15]

===fglrx (problem met at least with version 8.18.8)===
* [http://lkml.org/lkml/2005/9/22/183 for kernel >= 2.6.13 ] Missing verify_area bug

===fglrx 8.8.25 ===
* [http://www.rage3d.com/board/showthread.php?t=33798874 for kernels >= 2.6.10]
* [http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch For kernels >= 2.6.11-rc1]

===Links ===
* [http://gentoo-wiki.com/HOWTO_ATI_Drivers Gentoo HOWTO ATI]

ATI Mobility FireGL V5200

2006-04-02T05:14:16Z

Milli: /* Linux kernel Framebuffer driver */

ATI Mobility FireGL V5200

2006-04-02T05:13:54Z

Milli: /* Proprietary ATI driver */

ATI Mobility FireGL V5200

2006-04-02T05:13:11Z

Milli: /* Features */