ThinkWiki - User contributions [en]

Sample Fn-F7 script

2008-01-06T18:14:27Z

Hypnotoad: Added reference to script using aticonfig

This guide will help you configure Fn-F7 key combination to toggle between internal, mirror, external, or both screens. This was tested on ThinkPad X60s running Fedora 8, please comment if it works or does not work for you.

Works like a charm on X61s with Xubuntu 7.10.
Working with R60e with some modifications noted below.

The script does not work when using [[fglrx]] or a version of XRandR < 1.2, because there is no dynamic display switching support then. When fglrx is used, aticonfig can be used for the switching in this [[Script for Dynamic Display Management with fglrx]].

==configuring the virtual screen size==
Add a "Virtual" statement to your /etc/X11/xorg.conf, the total resolution should be large enough to fit all your screens in the configuration you want, for example if you have 1600x1200 monitor to the left of your internal 1024x768 monitor, your total max resolution is 2624x1200 (See [[Xorg RandR 1.2]] for more details):

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 2624 1200
EndSubSection
EndSection

Restart X server at this point (i.e. logout and login).

== configuring acpi ==
Create /etc/acpi/events/thinkpad.conf:

event=ibm/hotkey HKEY 00000080 00001007
action=/usr/local/sbin/thinkpad-fn-f7

or you may (eg Ubuntu 7.10) already have /etc/acpi/events/ibm-videobtn
# /etc/acpi/events/ibm-videobtn
# This is called when the user presses the video button. It is currently
# a placeholder.
event=ibm/hotkey HKEY 00000080 00001007
action=/bin/true

in which case modify the line 'action=/bin/true' to run the script as above.

It may also be necessary to enable acpi events as per [[How to get special keys to work]] with (in root terminal)
{{cmdroot|echo enable,0x084e > /proc/acpi/ibm/hotkey}}
Note this command isn't persistent. so you will also need to add the line to /etc/rc.local to enable hotkeys at boot, and to re-enable the hotkeys after suspend to disk or RAM, create the file
/etc/acpi/resume.d/91-ibm-hotkey-enable.sh consisting of

#!/bin/bash
# enable ibm-hotkeys (specifically Fn2, Fn7)
# 12 bit mask, little end is F1 default 0x080c = F12+F4+F3
echo enable,0x084e > /proc/acpi/ibm/hotkey

ref: [[http://tilmanfrosch.de/wp/index.php/2007/05/05/howto-make-a-ubuntu-linux-on-an-ibm-t41-thinkpad-work-with-an-external-widescreen-wxga-display/ frosch.org.uk]] and [[http://ibm-acpi.sourceforge.net/README ibm-acpi.sourceforge]]

==identify output devices==
Note the names of your output devices as you will have to change EXTERNAL_OUTPUT and INTERNAL_OUTPUT to what xrandr shows, for example VGA and LVDS in this case:

$ xrandr -q
'''VGA''' connected 1600x1200+0+0 (normal left inverted right x axis y axis) 432mm x 324mm
...
'''LVDS''' connected (normal left inverted right x axis y axis)

==The bash script==
Create /usr/local/sbin/thinkpad-fn-f7, you can set EXTERNAL_LOCATION to one of: left, right, above, or below.
<bash>
#!/bin/bash

# External output may be "VGA" or "VGA-0" or "DVI-0"
EXTERNAL_OUTPUT="'''VGA'''"
INTERNAL_OUTPUT="'''LVDS'''"
EXTERNAL_LOCATION="'''left'''"

# Figure out which user and X11 display to work on
# TODO there has to be a better way to do this?
X_USER=$(w -h -s | grep ":[0-9]\W" | head -1 | awk '{print $1}')
export DISPLAY=$(w -h -s | grep ":[0-9]\W" | head -1 | awk '{print $3}')

# Switch to X user if necessary
if [ "$X_USER" != "$USER" ]; then
SU="su $X_USER -c"
fi

case "$EXTERNAL_LOCATION" in
left|LEFT)
EXTERNAL_LOCATION="--left-of $INTERNAL_OUTPUT"
;;
right|RIGHT)
EXTERNAL_LOCATION="--right-of $INTERNAL_OUTPUT"
;;
top|TOP|above|ABOVE)
EXTERNAL_LOCATION="--above $INTERNAL_OUTPUT"
;;
bottom|BOTTOM|below|BELOW)
EXTERNAL_LOCATION="--below $INTERNAL_OUTPUT"
;;
*)
EXTERNAL_LOCATION="--left-of $INTERNAL_OUTPUT"
;;
esac

# Figure out current state
INTERNAL_STATE=$($SU xrandr | grep ^$INTERNAL_OUTPUT | grep con | sed "s/.*connected //" | sed "s/(.*//")
EXTERNAL_STATE=$($SU xrandr | grep ^$EXTERNAL_OUTPUT | grep con | sed "s/.*connected //" | sed "s/(.*//")

if [ -z "$INTERNAL_STATE" ]; then
STATE="external"
elif [ -z "$EXTERNAL_STATE" ]; then
STATE="internal"
else
INTERNAL_STATE=$(echo $INTERNAL_STATE | sed "s/[0-9]*x[0-9]*//")
EXTERNAL_STATE=$(echo $EXTERNAL_STATE | sed "s/[0-9]*x[0-9]*//")
if [ "$INTERNAL_STATE" = "$EXTERNAL_STATE" ]; then
STATE="mirror"
else
STATE="both"
fi
fi

function screen_external(){
$SU "xrandr --output $INTERNAL_OUTPUT --off"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto"
}

function screen_internal(){
$SU "xrandr --output $EXTERNAL_OUTPUT --off"
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
}

function screen_mirror(){
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto --same-as $INTERNAL_OUTPUT"
}

function screen_both(){
$SU "xrandr --output $INTERNAL_OUTPUT --auto"
$SU "xrandr --output $EXTERNAL_OUTPUT --auto $EXTERNAL_LOCATION"
}

function screen_toggle(){
case "$STATE" in
internal)
screen_mirror
;;
mirror)
screen_external
;;
external)
screen_both
;;
both)
screen_internal
;;
*)
screen_internal
;;
esac
}

# What should we do?
DO="$1"
if [ -z "$DO" ]; then
if [ $(basename $0) = "thinkpad-fn-f7" ]; then
DO="toggle"
fi
fi

case "$DO" in
toggle)
screen_toggle
;;
internal)
screen_internal
;;
external)
screen_external
;;
mirror)
screen_mirror
;;
both)
screen_both
;;
status)
echo "Current Fn-F7 state is: $STATE"
echo
echo "Attached monitors:"
$SU xrandr | grep "\Wconnected" | sed "s/^/ /"
;;
*)
echo "usage: $0 <command>" >&2
echo >&2
echo " commands:" >&2
echo " status" >&2
echo " internal" >&2
echo " external" >&2
echo " mirror" >&2
echo " both" >&2
echo " toggle" >&2
echo >&2
;;
esac
</bash>

== set permissions and restart acpi ==
As root, or using sudo run the following commands,

{{cmduser|sudo chmod 755 /usr/local/sbin/thinkpad-fn-f7}}
{{cmduser|sudo service acpid restart}}
OR
{{cmduser|sudo /etc/init.d/acpid restart}}

You should be ready to go, just press Fn-F7 to try.

==Alternative script using .Xauthority rather than su ==
Use this script as an alternative
action=/usr/local/sbin/toggle-display.sh
for /etc/acpi/events/ibm-videobtn

#!/bin/bash
# usr/local/sbin/toggle-display.sh
# based on /etc/acpi/screenblank.sh (Ubuntu 7.10)
#
# . /usr/share/acpi-support/power-funcs # for getXuser
umask 022;
PATH="$PATH:/usr/bin/X11"
getXuser() {
user=`finger| grep -m1 ":$displaynum " | awk '{print $1}'`
if [ x"$user" = x"" ]; then
user=`finger| grep -m1 ":$displaynum" | awk '{print $1}'`
fi
if [ x"$user" != x"" ]; then
userhome=`getent passwd $user | cut -d: -f6`
export XAUTHORITY=$userhome/.Xauthority
else
export XAUTHORITY=""
fi
}
# end of getXuser from /usr/share/acpi-support/power-funcs
#
for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXuser;
if [ x"$XAUTHORITY" != x"" ]; then
export DISPLAY=":$displaynum"
## . /usr/share/acpi-support/screenblank.sh
/usr/local/bin/toggle.py
fi
done

Each user has an ~/.Xauthority file with one line for each X display containing a 'magic cookie' (Run {{cmduser| xauth list}} to see the contents). The Xserver reads the record in ~/.Xauthority matching its display. When an X client application starts it also looks for that record and passes the magic cookie to the server. If it matches, the connection to the Xserver is allowed. The above example runs the python script below but could run a modified version of /usr/local/sbin/thinkpad-fn-f7 without the USER, and DISPLAY detection SU commands.

== A Python Toggle script ==
This is a somewhat over-elaborate script which could be cut down when run by the /usr/local/sbin/toggle-display.sh script above. It was written to explore all the possibilities rather than economy of execution. The functions 'toggle_full', 'position', 'toggle_limited' and the OptionParser in 'main' may be omitted with suitable changes to function7. The appropriate outputs can be specified on the command line and it is not necessary to call it via acpi.
eg you can run it as {{cmduser|/usr/local/bin/toggle.py --help}}

#! /usr/bin/python
# -*- coding: utf-8 -*-
#
# stinkpad(a)blueyonder.co.uk 2007-11-26
"""Toggle internal and external displays (equivalent to ThinkPad Fn7)
Simple; cloned: on+off, on+on, off+on.
Full; as simple plus xinerama: right, below, left, above.
Limited; as full but display will overlap if virtual screen is too small.
Use 'xrandr -q' to determine output names.
Further information: http://www.thinkwiki.org/wiki/Xorg_RandR_1.2
"""
__usage__ = "usage: %prog [--help]|[[-i internal][-e external][-d displays]]"
__version__ = "toggle [djclark.eu 2007-11-26]"
#
# Output names; Intel: LVDS VGA TV TMDS-1 TMDS-2
# ATI: LVDS VGA-0 S-video DVI-0
LAPTOP = 'LVDS'
MONITOR = 'VGA'
SEQUENCE = 'simple'
#
import sys
import os
import re

# "LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm"
REGEX_OUTPUT = re.compile(r"""
(?x) # ignore whitespace
^ # start of string
(?P<output>[A-Za-z0-9\-]*)[ ] # LVDS VGA etc
(?P<connect>(dis)?connected)[ ] # dis/connected
(( # a group
(?P<width>\d+)x # either 1024x768+0+0
(?P<height>\d+)[+]
(?P<horizontal>\d+)[+]
(?P<vertical>\d+)
)|[\D]) # or not a digit
.* # ignore rest of line
""")

# "Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2624 x 1968"
REGEX_SCREEN = re.compile(r"""
(?x) # ignore whitespace
^ # start of string
Screen[ ]
(?P<screen>\d)[: ]+
minimum[ ]
(?P<minWidth>\d+)[ x]+
(?P<minHeight>\d+)[, ]+
current[ ]+
(?P<curWidth>\d+)[ x]+
(?P<curHeight>\d+)[, ]+
maximum[ ]+
(?P<maxWidth>\d+)[ x]+
(?P<maxHeight>\d+)
""")

def toggle_simple(d0, d1):
"""Toggle display states: on+off, on+on, off+on"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off',"") # switch off external
if d1['width'] is 0: # external off
return ('auto','auto',"") # both on
if d0['width'] is 0: # laptop off
return ('auto','off',"") # laptop on
return ('off','auto',"") # both on, laptop off

def toggle_full(d0, d1):
"""Toggle display states: 1+0, 1+1, 0+1, 1+E, 1+S, 1+W, 1+N"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off',"") # switch off external
place = '--%s ' + d0['output']
if d1['width'] == 0: # external off
return ('auto','auto',place%'same-as') # external on
if d0['width'] == 0: # laptop off
return ('auto','off',"") # laptop on
if d1['horizontal'] > 0: # external to right
return ('auto','auto',place%'below') # make below
if d1['vertical'] > 0: # external below
return ('auto','auto',place%'left-of') # make left
if d0['horizontal'] > 0: # external left
return ('auto','auto',place%'above') # make above
if d0['vertical'] > 0: # external above
return ('off','auto',"") # laptop off
return ('auto','auto',place%'right-of') # is same, make right

def position(orientation, da, db, screen):
"""Calculate offset position of second display"""
p = 'auto --pos %sx%s'
if orientation == 'V':
if (da['height'] + db['height']) <= screen['maxHeight']:
return p%(0, da['height'])
return p%(0, screen['maxHeight'] - db['height'])
else:
if (da['width'] + db['width']) <= screen['maxWidth']:
return p%(da['width'],0)
return p%(screen['maxWidth'] - db['width'],0)

def toggle_limited(d0, d1, sz):
"""Toggle display states (overlapped): 1+0,1+1,0+1,1+E,1+S,1+W,1+N"""
if d1['connect'] == 'disconnected': # external unplugged
return ('auto','off') # switch off external
if d1['width'] == 0: # external off
return ('auto --pos 0x0','auto --pos 0x0') # both on
if d0['width'] == 0: # laptop off
return ('auto --pos 0x0','off') # laptop on
if d1['horizontal'] > 0: # external to right
return ('auto --pos 0x0',position('V',d0,d1,sz)) # put *below
if d1['vertical'] > 0: # external below
return (position('H',d1,d0,sz),'auto --pos 0x0') # put *left
if d0['horizontal'] > 0: # external left
return (position('V',d1,d0,sz),'auto --pos 0x0') # put *above
if d0['vertical'] > 0: # external above
return ('off','auto --pos 0x0') # laptop off
return ('auto --pos 0x0',position('H',d0,d1,sz)) # both, put*right

class DisplayNameError(UnboundLocalError):
"""Internal or External Display Name not found by xrandr -q """

def function7(disp0=LAPTOP, disp1=MONITOR, seq=SEQUENCE):
"""Use xrandr to read current display state and change state"""
for line in os.popen('xrandr -q').read().splitlines():
if line.startswith(disp0,0) :
d0_state = REGEX_OUTPUT.match(line).groupdict()
elif line.startswith(disp1,0):
d1_state = REGEX_OUTPUT.match(line).groupdict()
elif line.startswith('Screen',0):
screen_size = REGEX_SCREEN.match(line).groupdict()
else:
pass
for i in ('width','height','horizontal','vertical'):
try:
d0_state[i] = int(d0_state[i])
except TypeError:
d0_state[i] = 0
except UnboundLocalError:
raise DisplayNameError, 'Internal Display: %s not found'% disp0
try:
d1_state[i] = int(d1_state[i])
except TypeError:
d1_state[i] = 0
except UnboundLocalError:
raise DisplayNameError, 'External Display: %s not found'% disp1
for i in screen_size.keys():
try:
screen_size[i] = int(screen_size[i])
except TypeError:
screen_size[i] = 0
#
toggle = toggle_simple
xrandr ='xrandr --output '+disp0+' --%s --output '+disp1+' --%s %s'
if seq == 'full':
toggle = toggle_full
if seq == 'limited':
toggle = toggle_limited
xrandr ='xrandr --output '+disp0+' --%s --output '+disp1+' --%s'
os.popen(xrandr % toggle(d0_state, d1_state, screen_size))
else:
os.popen(xrandr % toggle(d0_state, d1_state))

def main():
""" Command line options """
global LAPTOP,MONITOR,SEQUENCE
from optparse import OptionParser
p = OptionParser(usage=__usage__, version=__version__, description=__doc__)
p.set_defaults(internal=LAPTOP, external=MONITOR, displays=SEQUENCE)
p.add_option('-i','--internal', dest="internal", metavar=LAPTOP,
help="internal display")
p.add_option('-e','--external', dest="external", metavar=MONITOR,
help="external display")
p.add_option('-d','--displays', dest="displays", action="store",
choices=('simple', 'limited', 'full'), metavar=SEQUENCE,
help='simple/limited/full')
(opt, args) = p.parse_args()
try:
function7(opt.internal, opt.external, opt.displays)
except DisplayNameError, err:
print '\n'+str(err)+'\n'
print os.popen('xrandr -q').read()
#
if __name__ == '__main__': #only when run from cmd line
main()

===Python XRandR===
[[http://www.glatzor.de/blog/blog-details/article/initial-release-of-python-xrandr Python XRandR]] is a set of python bindings to xrandr. The code is currently in development and the following code though much simpler than the python code above may not work reliably.

from xrandr import xrandr
def toggle_simple():
"""Toggle display states: on+off, off+on, on+on off+off"""
screen = xrandr.get_current_screen()
outputs = screen.get_outputs()
for o in outputs:
if o.is_connected():
if o.is_active():
o.disable()
print 'disable %s'% o.name
else:
o.set_to_preferred_mode()
print 'set to preferred mode %s'% o.name
break
screen.apply_output_config()

== References ==
[[http://gitweb.freedesktop.org/?p=xorg/app/grandr.git grandr]] graphical interface to xrandr using GTK+ libraries.

[[https://edge.launchpad.net/python-xrandr python-xrandr]] Python bindings to xrandr which should enable a less clunky version of the python script above. Under development.

Script for Dynamic Display Management with fglrx

2008-01-06T18:08:51Z

Hypnotoad: /* References */

The proprietary [[fglrx]] driver from ATI allows dynamic display switching, e.g. to switch to an external display for a presentation. [[Xorg RandR 1.2]] allows the same, but sometimes the newer version is not available, or not compatible e.g. when the proprietary ATI driver needs to be used for some reasons. The current version of it does not support the dynamic switching capabilities of XRandR 1.2.

In these cases, the following switching script provides the same functionality, which you can bind to a keypress such as Fn-F7. The script uses ATI's aticonfig tool for switching, XRandR for resolution adjustment, and Xosd for displaying OSD status messages. Thus, it should work on most Linux-running laptops whith ATI graphics cards (tested with [[:Category:Ubuntu 7.04|Ubuntu 7.04]] and [[:Category:Ubuntu 7.10|Ubuntu 7.10]] on a Thinkpad [[:Category:T43|T43]]). When an external display is connected, the script switches from internal to both internal and extarnal, then to external only, and finally back to internal display only.

==The Script==
<bash>
#!/bin/bash
#
# Script to switch displays, e.g. by pressing Fn-F7 on Thinkpad Laptops.
# Uses aticonfig from the ATI fglrx driver for dynamic switching, and
# xrandr for resolution changing. OSD done with xosd.sh, which uses
# osd_cat from Xosd.
#
# Author: Armin Hornung -- www.arminhornung.de
# Date: 2008-05-01
#
# Partly based on a display switching script from SuSE 10.1
#

# path to xosd.sh, change to "echo" if not installed
xosd="/usr/local/bin/xosd.sh"

# path to xrandr
xrandr="/usr/bin/xrandr"

INTERNAL="lvds" # internal LCD of Laptop
EXTERNAL="crt1" # external monitor, CRT or TFT

# Determine X user, script usually runs as root:

getXuser() {
user=`finger| grep -m1 ":$displaynum " | awk '{print $1}'`

if [ x"$user" = x"" ]; then
user=`finger| grep -m1 ":$displaynum" | awk '{print $1}'`
fi
if [ x"$user" != x"" ]; then
userhome=`getent passwd $user | cut -d: -f6`
export XAUTHORITY=$userhome/.Xauthority
else
export XAUTHORITY=""
fi
}

for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXuser
if [ x"$XAUTHORITY" != x"" ]; then
# extract current state
export DISPLAY=":$displaynum"
_enabled_monitors=`su $user -c "aticonfig --query-monitor | grep Enabled"`
_connected_monitors=`su $user -c "aticonfig --query-monitor | grep Connected"`
fi
done

# determine if internal is active
echo "${_enabled_monitors}" | grep $INTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_internal_enabled=yes
else
_internal_enabled=no
fi

# determine if external is connected
# (LVDS always assumed to be connected)
echo "${_connected_monitors}" | grep $EXTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_external_connected=yes
else
_external_connected=no
fi

# determine if external is active
_external_enabled=no
echo "${_enabled_monitors}" | grep $EXTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_external_enabled=yes
fi

#### display switching part ####

if [ "${_internal_enabled}" = "yes" ]; then
if [ "${_external_connected}" = "yes" ]; then
if [ "${_external_enabled}" = "yes" ]; then
# switch to external only, after both enabled:
$xosd "Enabling $EXTERNAL" &
su $user -c "aticonfig --enable-monitor $EXTERNAL"
# adjust resolution back to standard:
$xrandr -s 1280x1024 -r 60
else
# switch to both enabled, after external only
$xosd "Enabling $INTERNAL & $EXTERNAL" &
su $user -c "aticonfig --enable-monitor $INTERNAL,$EXTERNAL"
# adjust resolution:
$xrandr -s 1280x1024 -r 60
fi
else
$xosd "No external display connected" &
if [ "${_external_enabled}" = "yes" ]; then
# switch back just if external display got disconnected
su $user -c "aticonfig --enable-monitor $INTERNAL"
$xrandr -s 1400x1050 -r 60
fi
fi
else
# switch back to internal only, after external enabled:
$xosd "Enabling $INTERNAL" &
su $user -c "aticonfig --enable-monitor $INTERNAL"
# adjust resolution back to standard:
$xrandr -s 1400x1050 -r 60
fi

exit 0
</bash>

==OSD==
Using the helper script below, Xosd can be used for displaying status messages.

/usr/local/bin/xosd.sh:
<bash>
#!/bin/bash
# 2006-03-09 <pille@struction.de>
#
# displays text in arguments on X screen using osd_cat (in some nicely preconfigured style)

OSD_CAT=`which osd_cat`
XOSD="${OSD_CAT} --delay=2 --age=0 --lines=2 --pos=bottom --align=center --font=-adobe-helvetica-bold-r-normal-*-*-180-*-*-p-*-*-* --colour=green --shadow=1 --offset=25 --indent=25"

# get user running X display (needed when run by script)
# XUSER=`ps -C Xsession -o user h`
XUSER="armin"

if [ "${USER}" == "${XUSER}" ]; then
echo $@ | ${XOSD}
else
echo $@ |su ${XUSER} -c "DISPLAY=${DISPLAY:-:0.0} ${XOSD}"
fi
</bash>

==Installation==
Place the switching script at /etc/acpi/ati-toggle.sh and create /usr/local/bin/xosd.sh. Finally, the script needs to be bound to the key Fn-F7 by creating or editing /etc/acpi/events/ibm-videobtn to:
<bash>
# /etc/acpi/events/ibm-videobtn
# This is called when the user presses the video button.

event=ibm/hotkey HKEY 00000080 00001007
action=/etc/acpi/ati-toggle.sh
</bash>

==References==
[http://www.arminhornung.de/index.php?section=Linux&file=ATI%20dynamic%20display%20switching&l=en http://www.arminhornung.de] - Source, has scripts available for download

[[Sample Fn-F7 script]] - A similar script using XRandR 1.2 for switching

Script for Dynamic Display Management with fglrx

2008-01-06T18:08:15Z

Hypnotoad: Article creation

The proprietary [[fglrx]] driver from ATI allows dynamic display switching, e.g. to switch to an external display for a presentation. [[Xorg RandR 1.2]] allows the same, but sometimes the newer version is not available, or not compatible e.g. when the proprietary ATI driver needs to be used for some reasons. The current version of it does not support the dynamic switching capabilities of XRandR 1.2.

In these cases, the following switching script provides the same functionality, which you can bind to a keypress such as Fn-F7. The script uses ATI's aticonfig tool for switching, XRandR for resolution adjustment, and Xosd for displaying OSD status messages. Thus, it should work on most Linux-running laptops whith ATI graphics cards (tested with [[:Category:Ubuntu 7.04|Ubuntu 7.04]] and [[:Category:Ubuntu 7.10|Ubuntu 7.10]] on a Thinkpad [[:Category:T43|T43]]). When an external display is connected, the script switches from internal to both internal and extarnal, then to external only, and finally back to internal display only.

==The Script==
<bash>
#!/bin/bash
#
# Script to switch displays, e.g. by pressing Fn-F7 on Thinkpad Laptops.
# Uses aticonfig from the ATI fglrx driver for dynamic switching, and
# xrandr for resolution changing. OSD done with xosd.sh, which uses
# osd_cat from Xosd.
#
# Author: Armin Hornung -- www.arminhornung.de
# Date: 2008-05-01
#
# Partly based on a display switching script from SuSE 10.1
#

# path to xosd.sh, change to "echo" if not installed
xosd="/usr/local/bin/xosd.sh"

# path to xrandr
xrandr="/usr/bin/xrandr"

INTERNAL="lvds" # internal LCD of Laptop
EXTERNAL="crt1" # external monitor, CRT or TFT

# Determine X user, script usually runs as root:

getXuser() {
user=`finger| grep -m1 ":$displaynum " | awk '{print $1}'`

if [ x"$user" = x"" ]; then
user=`finger| grep -m1 ":$displaynum" | awk '{print $1}'`
fi
if [ x"$user" != x"" ]; then
userhome=`getent passwd $user | cut -d: -f6`
export XAUTHORITY=$userhome/.Xauthority
else
export XAUTHORITY=""
fi
}

for x in /tmp/.X11-unix/*; do
displaynum=`echo $x | sed s#/tmp/.X11-unix/X##`
getXuser
if [ x"$XAUTHORITY" != x"" ]; then
# extract current state
export DISPLAY=":$displaynum"
_enabled_monitors=`su $user -c "aticonfig --query-monitor | grep Enabled"`
_connected_monitors=`su $user -c "aticonfig --query-monitor | grep Connected"`
fi
done

# determine if internal is active
echo "${_enabled_monitors}" | grep $INTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_internal_enabled=yes
else
_internal_enabled=no
fi

# determine if external is connected
# (LVDS always assumed to be connected)
echo "${_connected_monitors}" | grep $EXTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_external_connected=yes
else
_external_connected=no
fi

# determine if external is active
_external_enabled=no
echo "${_enabled_monitors}" | grep $EXTERNAL > /dev/null 2>&1
if [ $? -eq 0 ]; then
_external_enabled=yes
fi

#### display switching part ####

if [ "${_internal_enabled}" = "yes" ]; then
if [ "${_external_connected}" = "yes" ]; then
if [ "${_external_enabled}" = "yes" ]; then
# switch to external only, after both enabled:
$xosd "Enabling $EXTERNAL" &
su $user -c "aticonfig --enable-monitor $EXTERNAL"
# adjust resolution back to standard:
$xrandr -s 1280x1024 -r 60
else
# switch to both enabled, after external only
$xosd "Enabling $INTERNAL & $EXTERNAL" &
su $user -c "aticonfig --enable-monitor $INTERNAL,$EXTERNAL"
# adjust resolution:
$xrandr -s 1280x1024 -r 60
fi
else
$xosd "No external display connected" &
if [ "${_external_enabled}" = "yes" ]; then
# switch back just if external display got disconnected
su $user -c "aticonfig --enable-monitor $INTERNAL"
$xrandr -s 1400x1050 -r 60
fi
fi
else
# switch back to internal only, after external enabled:
$xosd "Enabling $INTERNAL" &
su $user -c "aticonfig --enable-monitor $INTERNAL"
# adjust resolution back to standard:
$xrandr -s 1400x1050 -r 60
fi

exit 0
</bash>

==OSD==
Using the helper script below, Xosd can be used for displaying status messages.

/usr/local/bin/xosd.sh:
<bash>
#!/bin/bash
# 2006-03-09 <pille@struction.de>
#
# displays text in arguments on X screen using osd_cat (in some nicely preconfigured style)

OSD_CAT=`which osd_cat`
XOSD="${OSD_CAT} --delay=2 --age=0 --lines=2 --pos=bottom --align=center --font=-adobe-helvetica-bold-r-normal-*-*-180-*-*-p-*-*-* --colour=green --shadow=1 --offset=25 --indent=25"

# get user running X display (needed when run by script)
# XUSER=`ps -C Xsession -o user h`
XUSER="armin"

if [ "${USER}" == "${XUSER}" ]; then
echo $@ | ${XOSD}
else
echo $@ |su ${XUSER} -c "DISPLAY=${DISPLAY:-:0.0} ${XOSD}"
fi
</bash>

==Installation==
Place the switching script at /etc/acpi/ati-toggle.sh and create /usr/local/bin/xosd.sh. Finally, the script needs to be bound to the key Fn-F7 by creating or editing /etc/acpi/events/ibm-videobtn to:
<bash>
# /etc/acpi/events/ibm-videobtn
# This is called when the user presses the video button.

event=ibm/hotkey HKEY 00000080 00001007
action=/etc/acpi/ati-toggle.sh
</bash>

==References==
[http://www.arminhornung.de/index.php?section=Linux&file=ATI%20dynamic%20display%20switching&l=en http://www.arminhornung.de] - Source, has scripts available for download
[[Sample Fn-F7 script]] - A similar script using XRandR 1.2 for switching

Fglrx

2008-01-06T17:51:25Z

Hypnotoad: /* Display Switching (Dynamic Display Management) */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
== ATI fglrx driver ==
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.

Also see [[R300|opensource driver]] with 3D support
|}

==Availability / Project Homepage==
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html

== Packages ==
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]

*{{Debian}}
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}
*{{Fedora}} 4 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 5 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 7 packages: http://rpm.livna.org
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.
*{{Arch Linux}}
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)
*{{Ubuntu}}
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]

== Building for Xorg 7.0==
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg

In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears

== Status ==
Current version: 7-12 (8.433) (20st December 2007).
Major changes:
* 7-12: FireGL support, fixed memory leak when running OpenGL applications, X -configure no longer results in a segmentation fault
* 7-11: new versioning scheme, kernel 2.6.23 support. Required for Xorg server 1.4, but does not support FireGL cards. So don't upgrade to Xorg 1.4 if you have one!
* 8.42.3: Composite support added enabling AIGLX and Beryl/Compiz on the desktop. Support for (most?) FireGl cards dropped (should be restored in upcoming versions)
* 8.41.7: increased OpenGL performance on some Radeon Cards, size/position TV-out adjustments work for Radeon X1900 or higher, X crash when connecting external DFP display fixed
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).

== Known problems and solutions ==
See [[Problems with fglrx]].
== User experience ==
=== Speed ===
How much is the speed gain versus the opensource drivers?

Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!

However the situation seems to be changing significantly as time goes on. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps and stable. As of October 2007 there is dramatic improvement in the open source 3d drivers in speed and stability.

=== 3D acceleration ===

According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:

Section "Module"
...
Load "GLcore"
Load "glx"
Load "dri"
...
EndSection

# Of course you need to activate the driver
Section "Device"
...
Driver "fglrx"
EndSection

Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.

With fglrx drivers prior to 8.42.3 will need to disable composite to enable 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:

Section "Extensions"
Option "Composite" "Disable" #make DRI work with fglrx.
EndSection

If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this

{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "1"
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.

You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:

Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}

=== Power saving ===
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).

=== Suspending with fglrx ===

On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:

# For fglrx
ProcSetting extra_pages_allowance 20000

=== Display Switching (Dynamic Display Management) ===

Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.

To list all connected and enabled monitors:
:{{cmdroot|1=aticonfig --query-monitor}}

To switch displays:
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2

Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.

Using an [[Script for Dynamic Display Management with fglrx|ACPI script]], aticonfig can be used to switch displays on a key press.

The '''Catalyst Control Center''', which comes with the driver (at least from Livna in Fedora Core 6) can be used to do this switching. It also does various other kinds of display managements. However, the version that comes with 8.39.4 doesn't seem to handle switching into Big Desktop mode, does anyone know how to get this to work? The control center also complains a lot about rebooting, but rebooting doesn't seem to be required. Does anyone have decent documentation for the control center?

== Useful links ==
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads:
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}
* [[ATI Mobility FireGL 9000]]
** {{T40p}}
* [[ATI Mobility FireGL T2]]
** {{R50p}}
** {{T41p}}, {{T42p}}
* [[ATI Mobility FireGL V3200]]
** {{T43p}}
* [[ATI Mobility Radeon 9000]]
** {{R50}}, {{R51}}
** {{T40}}, {{T41}}, {{T42}}
* [[ATI Mobility Radeon 9600]]
** {{T42}}
* [[ATI Mobility Radeon X300]]
** {{R52}}
** {{T43}}
** {{Z60m}}
* [[ATI Mobility Radeon Xpress 200M]]
** {{R51e}}
* [[ATI Mobility Radeon X600]]
** {{Z60m}}
* [[ATI Mobility Radeon X1400]]
** {{T60}}, {{R60}}, {{Z61m}}
* [[ATI Mobility FireGL V5200]]
** {{T60p}}, {{Z61p}}

== ThinkPads that are NOT supported by fglrx==
Unsupported chips, as found in select IBM ThinkPads:
* [[ATI Mobility Radeon 7500]]
** {{R40}}
** {{T30}}
** {{T41}}
** {{T42}}

{{footnotes|
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.
}}
[[Category:Drivers]]

Fglrx

2008-01-06T17:50:54Z

Hypnotoad: /* Display Switching (Dynamic Display Management) */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
== ATI fglrx driver ==
This is a proprietary Linux binary-only driver for ATI graphic chips with support for 3D acceleration.

Also see [[R300|opensource driver]] with 3D support
|}

==Availability / Project Homepage==
Home page: http://ati.amd.com/support/drivers/linux/linux-radeon.html

== Packages ==
The ATI drivers have explicit permission for repackaging and redistribution of the Linux drivers. Many distributions are supported within the installer, and many more repackaged by external developers. Please visit the [http://wiki.cchtml.com/index.php/Category:Distributions Distribution Page at the Unofficial ATI driver Wiki]

*{{Debian}}
** These packages have been added to Debian unstable as <tt>fglrx-driver</tt>, so you can now apt-get them and use module-assistant to install.
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, let it build Debian packages and proceed as usual. There's a [http://jroller.com/page/erAck?entry=lot_day_6_2_fglrx detailed description] available.
** [http://wiki.cchtml.com/index.php/Debian_Installation_Guide Debian Howto]
*{{SUSE}} packages: http://www.suse.de/~sndirsch/ati-installer-HOWTO.html
*{{Gentoo}} {{cmdroot|emerge ati-drivers}}
*{{Fedora}} 4 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 5 packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install xorg-x11-drv-fglrx}}
** For custom-compiled kernels: see [[How to build custom packages for fglrx]]
*{{Fedora}} 7 packages: http://rpm.livna.org
** The newest version of the driver (8.39.4) is supposed to work with Fedora 7, and is available from Livna.
*{{Arch Linux}}
:{{cmdroot|pacman -S ati-fglrx}} (kernel module for 2.6.15-ARCH)
:{{cmdroot|pacman -S ati-fglrx-archck}} (kernel module for 2.6.15-archck)
:{{cmdroot|pacman -S ati-fglrx-utils}} (xorg7 stuff and tools)
*{{Ubuntu}}
**[http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide Dapper Drake Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Breezy_Installation_Guide Breezy Badger Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Edgy_Installation_Guide Edgy Eft Howto]
**[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide Feisty Fawn Howto]

== Building for Xorg 7.0==
To compile fglrx versions <= 8.24.8 for Xorg 7.0.0, fake Xorg 6.9.0 by
:{{cmdroot|1=export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run}}
Next, move the various resulting libraries and modules from /usr/X11R6 to /usr/lib/xorg

In {{path|/usr/src/ATI}} additional sources are installed for fireglcontrol and fgl_glxgears

== Status ==
Current version: 7-12 (8.433) (20st December 2007).
Major changes:
* 7-12: FireGL support, fixed memory leak when running OpenGL applications, X -configure no longer results in a segmentation fault
* 7-11: new versioning scheme, kernel 2.6.23 support. Required for Xorg server 1.4, but does not support FireGL cards. So don't upgrade to Xorg 1.4 if you have one!
* 8.42.3: Composite support added enabling AIGLX and Beryl/Compiz on the desktop. Support for (most?) FireGl cards dropped (should be restored in upcoming versions)
* 8.41.7: increased OpenGL performance on some Radeon Cards, size/position TV-out adjustments work for Radeon X1900 or higher, X crash when connecting external DFP display fixed
* 8.40.4: some new TV out control options in CCC, another (non-exciting) maintenance release (see [http://www.phoronix.com/scan.php?page=article&item=804&num=1 Phoronix])
* 8.39.4: kernel 2.6.22 support, TexturedVideo fix, aticonfig segfault fix (see 8.38.7 hotfix), to get rid of the "AMD Testing use only" logo, use [http://www.phoronix.com/forums/showpost.php?p=10641&postcount=44 this] workaround.
* 8.38.7: hotfix release for "Using aticonfig --initial segfaults destroying xorg.conf file when run in X with Vesa driver.", search for "737-28261" on the ATI website.
* 8.38.6: RedHat Enterprise Linux 5 support, Xserver crashes on moving video window between two monitors fixed, corruption when playing multiple vodeps with textured video fixed
* 8.37.6: Xorg Server 1.3 support, CCC 1.0, crash when logging off from X fixed, Xv cropping bug fixed
* 8.36.5: Kernel 2.6.20 support, CCC Beta 0.9 with localization
* 8.35.5: Beta AMD Catalyst Control Center, X-Server termination from console does not result in a blank screen. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.35.5|fglrx patches section]]).
* 8.34.8: Radeon Xpress 1250 support, X-Video on x86_64 fix, hibernation mode fix. Kernel 2.6.20 requires some patching (see [[Problems_with_fglrx#fglrx_8.34.8|fglrx patches section]]).

== Known problems and solutions ==
See [[Problems with fglrx]].
== User experience ==
=== Speed ===
How much is the speed gain versus the opensource drivers?

Compared to the old drivers, approximately 40% speed gain have been noticed with fglrx. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (via {{key|ctrl}}{{key|alt}}{{key|plus}}, {{key|ctrl}}{{key|alt}}{{key|minus}}), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using the open source radeon driver: 1200 FPS for glxgears{{footnote|1}}!

However the situation seems to be changing significantly as time goes on. With recent x11-drm-20060608 driver (gentoo) and thinkpad t42 (ati 9600) the speed is confirmed as 1900fps and stable. As of October 2007 there is dramatic improvement in the open source 3d drivers in speed and stability.

=== 3D acceleration ===

According to [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] you need these options:

Section "Module"
...
Load "GLcore"
Load "glx"
Load "dri"
...
EndSection

# Of course you need to activate the driver
Section "Device"
...
Driver "fglrx"
EndSection

Don't forget to load the module <tt>fglrx</tt> (<tt>modprobe fglrx</tt>). Under Debian the module can be placed in <tt>/etc/modules</tt>.

With fglrx drivers prior to 8.42.3 will need to disable composite to enable 3D DRI acceleration. To do this, add an extra Extensions section (if necessary) containing:

Section "Extensions"
Option "Composite" "Disable" #make DRI work with fglrx.
EndSection

If you are unsure whether you have DRI running, issue <tt>glxinfo | grep -i direct</tt> after disabling composite. Note, this

{{NOTE|1=Video overlay acceleration may be disabled when 3D acceleration is enabled. The following comment from the xorg.conf file bundled with the fglrx driver indicates that:
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "1"
However, you can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. This has nothing to do with the acceleration of 2D drawing primitives. Further, your mileage on performance may vary depending on what card you have. The open source drivers don't support newer cards, while the ATI drivers don't support older cards.

You may be able to preserve VideoOverlay acceleration if you explicitly remove the OpenGLOverlay using:

Option "VideoOverlay" "True" and Option "OpenGLOverlay" "False". See [http://xoomer.alice.it/flavio.stanchina/debian/fglrx-installer.html#configure Flavio's page] for detail.}}

=== Power saving ===
Power saving is much better than with the <tt>radeon</tt> driver, but doesn't work in dual-screen configuration (see [[How to make use of Graphics Chips Power Management features]]).

=== Suspending with fglrx ===

On a ThinkPad T42 with Kernel 2.6.19 with Software Suspend 2 and R60 with Kernel 2.6.18-suspend2-r1 (Gentoo) , the following addition to <tt>/etc/hibernate/suspend2.conf</tt> is required:

# For fglrx
ProcSetting extra_pages_allowance 20000

=== Display Switching (Dynamic Display Management) ===

Version 8.25.18 introduces a new feature: Dynamic Display Management. It allows display switching on-the-fly.

To list all connected and enabled monitors:
:{{cmdroot|1=aticonfig --query-monitor}}

To switch displays:
:{{cmdroot|1=aticonfig --enable-monitor=STRING,STRING}}, where STRING can be: none, lvds, crt1, crt2, tv, tdms1, tdms2

Only 2 displays can be enabled at the same time. Any displays that are not on the list will be disabled.

Using an [Script for Dynamic Display Management with fglrx|ACPI script], aticonfig can be used to switch displays on a key press.

The '''Catalyst Control Center''', which comes with the driver (at least from Livna in Fedora Core 6) can be used to do this switching. It also does various other kinds of display managements. However, the version that comes with 8.39.4 doesn't seem to handle switching into Big Desktop mode, does anyone know how to get this to work? The control center also complains a lot about rebooting, but rebooting doesn't seem to be required. Does anyone have decent documentation for the control center?

== Useful links ==
* [http://www.ati.com/products/catalyst/linux.html ATI Linux Driver FAQ]
* [http://www.rage3d.com/content/articles/atilinuxhowto/ ATI Radeon Linux How-To]
* [http://www.rage3d.com/board/forumdisplay.php?f=61&daysprune=30&order=asc&sort=title Rage3D Linux Discussion Forum]
* [http://www.driverheaven.net/forumdisplay.php?f=103 Radeon Driver Forum at Driverheaven]
* [http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html Gentoo ATI Radeon FAQ]
* [http://forums.gentoo.org/viewtopic-t-374745-highlight-t42+ati+dri.html Gentoo T42 ATI. DRI + xorg driver]
* [http://ati.cchtml.com/ Unofficial community ATI bugzilla] - tracks bugs in the driver. Might be monitored by ATI ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]).

== ThinkPads that may be supported ==
Supported chips, as found in select IBM ThinkPads:
{{NOTE|fglrx version 8.29.6 discontinued support for Radeon 9200 and earlier.}}
* [[ATI Mobility FireGL 9000]]
** {{T40p}}
* [[ATI Mobility FireGL T2]]
** {{R50p}}
** {{T41p}}, {{T42p}}
* [[ATI Mobility FireGL V3200]]
** {{T43p}}
* [[ATI Mobility Radeon 9000]]
** {{R50}}, {{R51}}
** {{T40}}, {{T41}}, {{T42}}
* [[ATI Mobility Radeon 9600]]
** {{T42}}
* [[ATI Mobility Radeon X300]]
** {{R52}}
** {{T43}}
** {{Z60m}}
* [[ATI Mobility Radeon Xpress 200M]]
** {{R51e}}
* [[ATI Mobility Radeon X600]]
** {{Z60m}}
* [[ATI Mobility Radeon X1400]]
** {{T60}}, {{R60}}, {{Z61m}}
* [[ATI Mobility FireGL V5200]]
** {{T60p}}, {{Z61p}}

== ThinkPads that are NOT supported by fglrx==
Unsupported chips, as found in select IBM ThinkPads:
* [[ATI Mobility Radeon 7500]]
** {{R40}}
** {{T30}}
** {{T41}}
** {{T42}}

{{footnotes|
#Note that glxgears isn't a benchmark tool, it's so simple that its FPS values is without any meaning... you can only compare glxgears using the same drivers/machine, if you change any of then you can have higher/lower values and in real life programs/games happen to have the opposite effects. Think in terms of a car engines rpms: higher rpms in the same car usually means a faster car, change anything and it's meaningless, ie: gears, truck, wheel size, etc. make it useless.
}}
[[Category:Drivers]]

Laptop-mode

2006-07-15T18:33:11Z

Hypnotoad: Note regarding suse / powersaved

An often overlooked feature in 2.4.23+ and 2.6.6+ Linux kernels is the laptop-mode. It may be activated by writing a "5" into {{path|/proc/sys/vm/laptop_mode}}. Laptop-mode, when configured correctly, can make the kernel buffer disk activities for quite a long time and keep the harddisk spun down for most of the time to save power.

There is also a set of userland tools made to automatically manage all aspects of laptop-mode configuration according to the actual mode of operation (ac/battery-status). It is called [[laptop-mode-tools]] and you can install it in debian via apt-get or download it from [http://www.xs4all.nl/~bsamwel/laptop_mode/tools here].

Almost anything you need to know about laptop-mode can be read in your Linux kernel documentation at /usr/src/linux/Documentation/laptop-mode.txt 
If you can not find this file on your laptop, then go and get yourself the latest kernel sources.

{{NOTE|The use of Laptop-mode and laptop-mode-tools is not recommended in SuSE Linux. The supplied <tt>powersaved</tt> already takes care of everything regarding power saving}}

=== Keeping the disk in the stand-by state ===

Laptop-mode is only effective if one avoids spinning up the disk for frivoulous reasons. What will spin a disk up is dependent on the HD firmware, but unfortunately most will spin up on just about every command. To add insult to injury, ATA/SATA pass-through commands are not logged through the {{path|/proc/sys/vm/block_dump}} facility, and thus invisible to tools like '''lm-profiler'''.

{{HINT|The '''lm-profiler''' tool from laptop-mode-tools can be used to list all processes doing normal disk access.}}

In systems where the HD spins up too easily, the "'''hddtemp'''" daemon will wake up the disk every minute, and must thus be disabled for power management to be effective. The "'''smartd'''" daemon is also an offender, but fortunately its default configuration issues commands to the HDs only every 30 minutes.

{{HINT|smartd can be configured to never issue commands to the disk if it is in the sleep or standby states, through the use of option "'''-n standby,q'''". The "''',q'''" is needed to supress syslog messages.}}

[[Category:Glossary]]

How to make use of Graphics Chips Power Management features

2006-07-14T17:26:38Z

Hypnotoad: /* Using the ATI proprietary driver */ atieventsd dynamic throttling

=ATI Radeon Mobility chips=

==Power saving with a framebuffer console==
In order to use the dynamic GPU clock-scaling similar to what X.org has, you need to use the radeonfb kernel module. You'll need to enable the '''CONFIG_FB_RADEON''' in your kernel configuration. If setup correctly you should see something like the following in your kernel log:
radeonfb: Dynamic Clock Power Management enabled

==Using the X.org Radeon driver==
===Activation===
The xorg X server has support for a power saving feature from ATI called PowerPlay. Xorg calls this feature DynamicClocks. It can be enabled in the server by adding '''Option "DynamicClocks" "on"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM ThinkPad"
BoardName "ATI Radeon Mobility M9"
'''Option "DynamicClocks" "on"'''
EndSection

With this option enabled, the X11 server should print ({{path|/var/log/Xorg.0.log}}):

(**) RADEON(0): Option "DynamicClocks" "on"
(II) RADEON(0): Dynamic Clock Scaling Enabled

You do not need to do anything else, it dynamically manages the power consumption itself.

{{NOTE|Enabling DynamicClocks crashes some models. If the CPU is entering one of the lower power states (C3 or lower) during Xorg startup the display may stay black. As a workaround disable DynamicClocks in Xorg and use [[Rovclock]] instead. But it does not scale the clocks to match the workload. Update 5/2/2006: Seems fixed in Xorg6.9}}

===Problem with <tt>vbetool</tt>===

When <tt>vbetool</tt> is used to restore the display state (as done by some suspend/resume scripts), the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicTools again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}.

===Problem with suspend-to-disk===

Upon resume from suspend-to-disk, the setting of <tt>DynamicClocks</tt> is forgotten and the GPU will consume more power until the next X server startup. You can manually enable DynamicClocks again by starting a blank second X server (e.g., by running {{cmdroot|X :1}}) and then exiting it via {{key|Ctrl}}{{key|Alt}}{{key|Backspace}}.

If you're using the hibernate script that's part of [[Software Suspend 2]], setting UseDummyXServer to yes in {{path|hibernate.conf}} automatically starts a second X server, hence enabling DynamicClocks again. (Remember to disable UseDummyXServer if you switch to the [[fglrx]] driver, otherwise your computer will hang upon resume.)

Note: When using the [[Synaptics TouchPad driver for X]] with the SHMConfig-Option set to true in {{path|xorg.conf}}, starting a second X server breaks the Shared Memory and the touchpad can't be configured with {{cmd|synclient|}} any longer. Starting the dummy X server with a different xorg.conf file is a solution to this, a patch can be found in the [http://bugzilla.suspend2.net/show_bug.cgi?id=138 suspend2 bugzilla].

===Debian Notes===
If your {{Debian}} doesn't have Xorg, yet, see [http://incubator.vislab.usyd.edu.au/roller/page/Steve/20040909 Installing a non-intrusive X.org server on Debian].

Sarge backports are available from [http://www.backports.org/ here] or [http://people.debian.org/~nobse/xorg-x11/ here].

You can also add the following line to your repository list:
deb http://people.debian.org/~nobse/xorg-x11/ sarge main

==Using the ATI proprietary driver==

Versions 8.19.10 and higher of the ATI [[fglrx]] driver support "PowerPlay", which "allows for the user to switch between power consumption modes".

To list available modes do:
:{{cmdroot|aticonfig --list-powerstates}}
:{{cmdresult|   core/mem     [flags]}}
:{{cmdresult|---------------}}
:{{cmdresult|1: 105/122 MHz  [low voltage]}}
:{{cmdresult|2: 209/182 MHz  [low voltage]}}
:{{cmdresult|3: 297/230 MHz  [default state]}}

(Strangely, the same ThinkPad {{T43}} with [[ATI Mobility Radeon X300]] running [[fglrx]] 8.19.10 sometimes gives other, non-sensical results, perhaps due to interaction with [[rovclock]].)

To changing the power mode on the fly:
:{{cmdroot|1=aticonfig --set-powerstate=2 --effective=now}}

With newer driver versions (8.26 and later), <tt>atieventsd</tt> should dynamically change the power state and clock, depending on thermal conditions and AC plug.

Limitations (as of [[fglrx]] 8.19.10):
* You can't set the power state in {{path|/etc/X11/xorg.conf}} .
* You can't activate power saving when using dual-head mode (e.g., LCD+CRT).

{{NOTE|[[fglrx]] power saving is not compatible with the [[Rovclock]] utility. Setting power saving mode using both [[fglrx]] and [[Rovclock]] results in an unusably slow desktop.}}

==External sources==
*[http://www.ati.com/products/pdf/powerplaywp2.pdf Marketing information from ATI]

=Other graphics chips=
No instructions are presently known for other chips.

But see [[Problem with display remaining black after resume]].

[[Category:G40]] [[Category:G41]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]]

Problem with video output switching

2006-07-12T06:18:42Z

Hypnotoad: /* Problems with ATI chipsets */ No problems with fglrx

==Affected Models==
*ThinkPad {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}}, {{T43p}}
*ThinkPad {{X23}}, {{X41}}

==Problem Description==
It is not possible, using the FN-F7 key, to switch between the LCD and the external monitor in the following way
LCD --> external Monitor--> both -->LCD
however ''cloning'' is possible for the Intel chipsets, see below.

===Problems with Intel chipsets===
Disabling the internal LCD (e.g. when using an external Monitor) doesn't seem to work reliably.

* For Xorg 7.022 one can clone the LCD display to an external monitor, adding the following lines to the Device section in the xorg.conf file:
Section "Device"
Identifier "Generic Video Card"
Driver "i810"
Option "Clone" "true"
Option "MonitorLayout" "CRT,LFP"
however you can not switch between these screens as described above, once you use FN-F7 the cloned display is lost.

* i810switch doesn't have any effect. After disabling the LCD it is still on (but the status display of i810switch claims that is is switched off).

* i855crt works see: http://stefan.desire.ch/howto/x41debian/ for details.

* With [[ibm-acpi]], {{cmdroot|echo lcd_disable >/proc/acpi/ibm/video}} works, but {{cmdroot|echo lcd_enable >/proc/acpi/ibm/video}} doesn't work - so one can't enable it anymore after disabling it. (the strange thing is that when switching to a console with {{key|ctrl}}{{key|alt}}{{key|F1}} the LCD display is used for it, so there must be some way to enable it but I can't find out how to control this in X). I've tried this with version 0.8 and version 0.11 of [[ibm-acpi]].

===Problems with ATI chipsets===
*It is a [http://bugs.freedesktop.org/show_bug.cgi?id=2000 known issue] of xorgs radeon driver that {{key|Fn}}{{key|F7}} doesn't work.

You can force the <tt>radeon</tt> driver to enable both CRT and LCD using <tt>Option "MonitorLayout" "LVDS,CRT"</tt> in the <tt>"Device"</tt> section of {{path|/etc/X11/xorg.conf}}. The analogous option for [[fglrx]] is <tt>Option "ForceMonitors" "lvds,crt1"</tt>

The {{cmdroot|radeontool light off}} and {{cmdroot|radeontool dac off}} commands will disable the LCD and CRT if they're been enabled before in the X server, but the corresponding {{cmdroot|radeontool light on}} and {{cmdroot|radeontool dac on}} will not work if the displays have were not enabled when the X server started. Also note that turing off the CRT using this command will not reduce power consumption, nor allow [[fglrx]] to enable power saving modes.

You might try the following: Hit Ctrl+Alt+F1 to switch to a console, hit Fn+F7 to switch video, hit Ctrl+Alt+F7 to switch back to X.

====fglrx-Driver====
Output switching with the Closed-Source ati-driver works: Just use {{cmdroot|aticonfig --query-monitor}} and e.g. {{cmdroot |aticonfig --enable-monitor..."}}. You can use those two commands in a script, and bind them to {{key|Fn}}{{key|F7}}

==Related Links==
*https://bugs.freedesktop.org/show_bug.cgi?id=2000

==Solutions==
None (yet).

Installation instructions for the ThinkPad T43

2006-07-09T09:47:51Z

Hypnotoad: /* Distribution-specific instructions */ Links fixed

Specific installation notes for the ThinkPad {{T43}}.

==Distribution-specific instructions==
*{{Install|Debian|/Sarge|T43}}
*{{Install|Debian|/Sid|T43}}
*{{Install|Fedora| Core 4|T43}}
*{{Install|Fedora| Core 4|T43}} (2668)
*{{Install|Fedora| Core 5|T43}} (2686)
*{{Install|Gentoo||T43}} (2668)
*{{Install|Ubuntu| 5.04|T43}} (1875)
*{{Install|Ubuntu| 5.10|T43}} (1871)
*{{Install|OpenSUSE| 10.1|T43}} (2668)

==External instructions==
* [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p Debian Linux on an IBM Thinkpad T43p]
* [http://wiki.foosel.net/linux/t43 Debian GNU/Linux Etch on an IBM ThinkPad T43]
* [http://sth.freeshell.org/t43-linux.html Gentoo on T43]
* [http://www.cs.ust.hk/~joseph/Favorites/Debian/UbuntuOnIBMThinkpadT43.html Ubuntu on IBM ThinkPad T43 (2668-HH5)]
* [http://ce.et.tudelft.nl/~zhijiangchang/index.html#useful How to make windows, linux and AcessIBM work all together]

Installing OpenSUSE 10.1 on a ThinkPad T43

2006-07-09T09:47:36Z

Hypnotoad: Installing SUSE 10.1 on a ThinkPad T43 (2668) moved to Installing OpenSUSE 10.1 on a ThinkPad T43

Most things run just fine after installation, the Rest I got working with the great articles here.

==Installation==
{{WARN| The Pre-Desktop-Area has to be protected before installation, otherwise the Recovery-System will be lost. To do so, set Predesktop-Area to "Secure" in BIOS. Additionally, it's always useful to have the Recovery-CDs burned before an installation attempt}}

The automatic shrinking of the NTFS-partition did not work during the Installation of {{SUSE}}, so I shrinked it with QtParted from a Knoppix-DVD.
To be able to boot Windows and Linux (via Grub) and the Recovery-System (with {{ibmkey|Access IBM|#495988}}), install the bootloader in the new, extended partition (usually <tt>/dev/sda</tt>).

Besides that, everything went fine, most Hardware was set up correctly: Graphics Card, Touchpad and Trackpoint, WLAN, Bluetooth, Modem (yet untested), Volume Control.

==ACPI==
Everything set up correctly, [[ibm-acpi]] ist installed, Suspend-to-RAM and Suspend-to-Disk work with the keys already assigned to them. I still miss [[RediSafe]] though, maybe I'll use [[Software Suspend 2]] some day.

==Hotkeys==
[[How to get special keys to work]] gives a general overview.

Suspend keys worked by default installation, as did {{key|Fn}}{{key|F5}} for switching Bluetooth on and off. For the remaining keys, the <tt>nvram</tt>-module was missing. So when {{path|/dev/nvram/}} is missing, you have to create it first:

{{cmdroot|mknod /dev/nvram c 10 144}}

and load it with

{{cmdroot|modprobe nvram}}

Additionally, I had to specify the module to be loaded automatically at {{path|/etc/sysconfig/kernel}}:
[...]
MODULES_LOADED_ON_BOOT="nvram"
[...]

Last, the access rights had to be corrected. To do so, search for <tt>nvram</tt> in {{path|/etc/udev/rules.d/50-udev-default.rules }} and change the entry to:
KERNEL=="nvram", NAME="%k", GROUP="nvram", MODE="660"
so the users of group nvram have access to it. Of course that group has to exist, and you need to be a member of it:

{{cmdroot|groupadd nvram}}
{{cmdroot|usermod -G nvram username}}

After a reboot, you can use either [[tpb]] or the [[KMilo]]-Plugin in KControl (System Administration -> IBM Thinkpad Laptop) to set up the keys. I liked the OSD of KMilo better. Additionally, I set the Mixer setting to "Software" (<tt>MIXER ON</tt> in tpb), so the Mixer volume and mute status matches the one in KMix.

==Fingerprint Reader==
[[How to enable the fingerprint reader]] neatly explains everything. I had to do the last steps manually, because the [[Script for enabling the fingerprint reader]] did not run till the end on Suse 10.1

==3D Acceleration==
The Standard driver did work for 2D, but with no 3D acceleration. When I added
<pre>Section "Module"
[...]
Load "glx"
[...]
EndSection</pre>
to my {{path|/etc/X11/xorg.conf}}, the 3D acceleration worked with the OpenSource driver, but now there were problems with Suspend. So I decided for the proprietary [[fglrx]]-Driver directly from Ati. Installed fine, after I created a distribution-specific rpm with the Installer.

==Extensions==
[[How_to_configure_the_TrackPoint#Scrolling | Trackpoint Scrolling]]

==External Sources==
[http://omnibus.uni-freiburg.de/~s8arhorn/index.php?section=Linux&file=Suse%2010.1%20auf%20IBM%20Thinkpad%2043 My Installation article, in German]

Installing SUSE 10.1 on a ThinkPad T43 (2668)

2006-07-09T09:47:36Z

Hypnotoad: Installing SUSE 10.1 on a ThinkPad T43 (2668) moved to Installing OpenSUSE 10.1 on a ThinkPad T43: Moved to general pagename, to fit the Installation Instructions links

#redirect [[Installing OpenSUSE 10.1 on a ThinkPad T43]]

Talk:Problem with APS harddisk parking

2006-07-08T17:47:35Z

Hypnotoad: freezes with hdapsd

What is meant with "frequent drive spin downs", or better: in which interval would the drive spin down? I also get the...

:: kernel: idedisk_issue_protect_fn(): unload support NOT reported by drive!..
:: kernel: ide_protect_queue(): head park not requested, used standby!..
:: kernel: ide_unprotect_queue(): No pending I/O, re-enabling power management..

...error every time I tilt my Laptop (only if hdapsd is running of course)
but then I can hear how the head parks and the drive spins down and comes back again.
If I don't hear this frequently, there shouln't be any problems right?

My Thinkpad:

Model: R51

HDD: Model=FUJITSU MHT2060AT, FwRev=8423

the hdd is the original shipped one so is has this capabilities.

So maybe anyone can confirm this and add the MHT2060AT drive to the "Drives which have this problem" list
----

You can check the drive's spec for the rated number of spin-ups to get concrete numbers, but what you describe means that if you work on an unstable surface (lap, train, etc.), you may kill your drive pretty quickly.

--[[User:Thinker|Thinker]] 00:36, 6 June 2006 (CEST)
----
===Random freezes===
My system randomly freezes when slightly shaken, but only from time to time and when hdapsd is active. The last messages in /var/log/messages are:
Jul 8 16:25:09 tp43 kernel: ata_scsi_issue_protect_fn(): unload support reported by drive..
Jul 8 16:25:09 tp43 kernel: scsi_protect_queue(): head parked..
Jul 8 16:25:10 tp43 kernel: scsi_unprotect_queue(): No pending I/O, re-enabling power management..
after that I need a hard reboot.

I use SuSE 10.1 with kernel 2.6.16.23 from kernel.org, patched with the hdaps-Patch for 2.6.16 (Thinkpad T43). Do I need an earlier kernel version? Anyone else with this problem?
HD-Firmware is MB41A60A, and there was no update available.

--[[User:Hypnotoad|Hypnotoad]] 19:47, 8 July 2006 (CEST)

Problem with APS harddisk parking

2006-07-08T17:15:58Z

Hypnotoad: /* supported/unsupported harddrive firmwares */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
When trying to [[How to protect the harddisk through APS|enable APS functionality]] by installing <tt>hdaps_protect</tt> and <tt>hdapsd</tt>, the following problems might occur.
|}

==Problem with unload capabilities check==
You may get the following kernel message when the disk is protected (e.g., via {{cmdroot|echo 1 > /sys/block/sda/queue/protect}}):

ata_scsi_issue_protect_fn(): unload support NOT reported..
scsi_protect_queue(): head park not requested, used standby!..

or

idedisk_issue_protect_fn(): unload support NOT reported..
ide_protect_queue(): head park not requested, used standby!..

{{WARN|Using HDAPS in the above state may cause frequent drive spin downs, thereby wearing out your hard disk.}}

If you see this, and you are sure that your drive actually does support unloading (all original drives sold with HDAPS-equipped ThinkPads do), one of the following solutions might help.

=== Drives which have this problem ===
* Hitachi HTS726060M9AT00 (7K60) on ThinkPad {{T43}}
* Fujitsu MHT2040AH (846C) on ThinkPad {{T41}}

=== Solution for kernel 2.6.16 or later ===
The <tt>hdaps_protect</tt> patch for 2.6.16 now accepts the {{bootparm|protect_method|}} module parameter to override the
parking capability detection, which accepts the following numeric values:
*<tt>0</tt>: autodetect capability
*<tt>1</tt>: "unload the head even if the drive doesn't report it has this capability"
*<tt>2</tt>: "standby even if unload is supported"

Hence, depending on your machine type, and whether the module is built into the kernel or not, you can use one of the following options:

If disk driver is built into kernel, add the following to your kernel boot parameters (e.g. {{path|/boot/grub/menu.lst}}):
libata.protect_method=1
ide-disk.protect_method=1

If disk driver is built as module, add the following to your modprobe configuration (e.g., {{path|/etc/modprobe.conf}}):
options libata protect_method=1
options ide-disk protect_method=1

In both cases, if you know whether you use <tt>ide-disk</tt> or <tt>libata</tt>, you can drop the other line.

=== Solution for kernel 2.6.15 and older ===
The following patch overrides automatic protect capability detection.
<pre>
diff -u linux-2.6.15.hdaps/drivers/ide/ide-disk.c linux-2.6.15.hdaps/drivers/ide/ide-disk.c
--- linux-2.6.15.hdaps/drivers/ide/ide-disk.c 2006-01-18 07:11:54.000000000 +0000
+++ linux-2.6.15.hdaps/drivers/ide/ide-disk.c 2006-01-18 07:11:54.000000000 +0000
@@ -869,7 +869,7 @@
else
printk(KERN_DEBUG "idedisk_issue_protect_fn(): unload support NOT reported..\n");

- return ide_protect_queue(q, (drive->id->cfsse & (1 << 13)) ? 1: 0);
+ return ide_protect_queue(q, 1);
}

int idedisk_issue_unprotect_fn(request_queue_t *q)
diff -u linux-2.6.15.hdaps/drivers/scsi/libata-scsi.c linux-2.6.15.hdaps/drivers/scsi/libata-scsi.c
--- linux-2.6.15.hdaps/drivers/scsi/libata-scsi.c 2006-01-18 07:15:31.000000000 +0000
+++ linux-2.6.15.hdaps/drivers/scsi/libata-scsi.c 2006-01-18 07:15:31.000000000 +0000
@@ -661,7 +661,7 @@
printk(KERN_DEBUG "ata_scsi_issue_protect_fn(): unload support NOT reported..\n");

/* call scsi_protect_queue, requesting either unload or standby */
- return scsi_protect_queue(q, ata_id_has_unload(dev->id) ? 1 : 0);
+ return scsi_protect_queue(q, 1);
}

static int ata_scsi_issue_unprotect_fn(request_queue_t *q)
</pre>

==Problem with Hard Drive Firmware==
In case you see a message like below in {{cmdroot|dmesg}} output after you have started the hdaps daemon,
a firmware upgrade of your harddisk might solve your problem.

ide_protect_queue(): head NOT parked!..
ide_unprotect_queue(): No pending I/O, re-enabling power management..

Go to the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62282 IBM harddrive firmware update utility page] and check if a firmware upgrade is available for your harddisk. IBM/Lenovo provides a bootdisk for easy firmware upgrade (~17MB download).

===supported/unsupported harddrive firmwares===
Use {{cmdroot| hdparm -i /dev/hda}} to get your harddisk model name and firmware version (replace <tt>/dev/hda</tt> with the actual device for your hard drive).
On newer models, you need {{cmdroot| sdparm -i /dev/sda}} because of the SATA controller.

The following line is the important one in the output:

Model=HTS726060M9AT00, FwRev=MH4O'''A6GA''', SerialNo=MRHXXXXXXXXX

The last four characters of the '''FwRev''' actually marks the firmware version.

The table lists known working / not working firmware versions with [[HDAPS]]

{| cellspacing="0" cellpadding="2" border="1"
|- style="text-align:left;"
!Drive!!firmware!!park command output
|- style="text-align:left;vertical-align:top;"
| IC25N040ATCS04-0 || CA40'''A71A''' || not parked
|- style="text-align:left;vertical-align:top;"
| IC25N040ATMR04-0 || MO2O'''AD4A''' || not parked
|- style="text-align:left;vertical-align:top;"
| IC25N040ATMR04-0 || MO2O'''ADEA''' || not parked
|- style="text-align:left;vertical-align:top;"
| HTC426040G9AT00 || 00P4'''A0B4''' || parked
|- style="text-align:left;vertical-align:top;"
| HTS548040M9AT00 || MG20'''A5BA''' || not parked
|- style="text-align:left;vertical-align:top;"
| HTS548040M9AT00 || MG20'''A5HA''' || parked
|- style="text-align:left;vertical-align:top;"
| HTS548080M9AT00 || (TBA) || parked
|- style="text-align:left;vertical-align:top;"
| HTS541060G9AT00 || MB3I'''A60A''' || parked
|- style="text-align:left;vertical-align:top;"
| HTS726060M9AT00 || MH4O'''A6GA''' || parked
|- style="text-align:left;vertical-align:top;"
| Fujitsu MHT2040AH || 846C || parked
|}

Thermal Sensors

2006-07-05T19:18:22Z

Hypnotoad: /* Utilities for viewing temperatures */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page aims to summarize known information about the locations and properties of thermal sensors on ThinkPad laptops.
|}
==Accessing the sensors==
===ACPI system temperature sensors===
The primary means of accessing the thermal sensors is through the [[ibm-acpi]] module, which provides up to 11 thermal sensors (some of which may be inactive) when loaded with the <tt>experimental=1</tt> option. Up to eight thermal sensors are exposed at {{path|/proc/acpi/ibm/thermal}}:
:{{cmdroot|cat /proc/acpi/ibm/thermal}}
:{{cmdresult|temperatures: 44 41 33 42 33 -128 30 -128}}

On some models there are three extra sensors at Embedded Controller offsets 0xC0 to 0xC2, which can be read by parsing {{path|/proc/acpi/ibm/ecdump}}:
:{{cmdroot|perl -ne 'm/^EC 0xc0: .(..) .(..) .(..) / or next; print hex($1)." ".hex($2)." ".hex($3)."\n"' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43}}

Future models might be additional extra sensors beyond those three. To see all candidates:
:{{cmdroot|perl -ne 'print join(" ",map(hex,m/\w+/g))."\n" if s/^EC 0xc0://' < /proc/acpi/ibm/ecdump}}
:{{cmdresult|40 48 43 128 128 128 128 128 0 0 0 0 0 0 0 0}}

===HDAPS temperature sensor===
The [[Active Protection System]] accelerometer also reports a temperature (but it is not certain that the sensor location is inside the HDAPS chip):
:{{cmdroot|cat /sys/bus/platform/drivers/hdaps/hdaps/temp1}}
:{{cmdresult|41}}

===Harddisks temperature sensor===
Finally, the hard disk temperature can be read through the disk's SMART interface:
:{{cmdroot|smartctl -A /dev/hda | grep Temperature}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

Or, for SATA-equipped models running a recent Linux kernel (see [[Problems with SATA and Linux]]):

:{{cmdroot|smartctl -A -d ata /dev/sda | grep Temperature}}
:{{cmdresult|194 Temperature_Celsius 0x0022 145 097 000 Old_age Always - 31}}

==Utilities for viewing temperatures==

The following utilities display the ThinkPad-specific thermal sensor readouts:
* The above shell commands.
* [http://www.kde-look.org/content/show.php?content=33257 CPU Info] is a KDE applet that can display the 8 first ACPI sensors as well as the HDAPS sensor.
* [http://www.kraus.tk/projects/IBMDoK/ IBMDoK], another KDE applet, so far only tested at the T60

==Sensor locations==
This information is model specific.

===ThinkPad {{R51}}===
The [[ibm-acpi]] documentation includes the report by Thomas Gruber:
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Mini-PCI
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery (main)
0x7D 6 Battery (device bay)
0x7E 7 Battery (main)
0x7F 8 Battery (device bay)
0xC0 none ?
0xC1 none ?
0xC2 none ?

===ThinkPad {{T40}}===
The location of one of the sensors is identified [http://forum.thinkpads.com/viewtopic.php?t=11574 here].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 System board under rear left corner of Mini-PCI module
0x7A 3 ?
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none n/a
0xC1 none n/a
0xC2 none n/a

===ThinkPad {{T43}}, {{T43p}}===
Found by Shmidoax using cooling spray to cool down components and observe the effect on the sensors.
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU
0x79 2 Between PCMCIA slot and CPU (same as HDAPS module)
0x7A 3 PCMCIA slot
0x7B 4 GPU
0x7C 5 Battery (front left)
0x7D 6 n/a
0x7E 7 Battery (rear right)
0x7F 8 n/a
0xC0 none Bus between Northbridge and DRAM
0xC1 none Southbridge (under Mini-PCI card, under touchpad)
0xC2 none Power circuitry, on underside of system board under F2 key
{{gallery_start}}
{{thumb|T43-thermal-sensors.jpg|ThinkPad T43 sensor locations}}
{{thumb|T43-2668-thermal-sensors-zoom.jpg|ThinkPad T43 sensor locations detail}}
{{thumb|T43p-H8S2161.jpg|ThinkPad T43/p 26xx Embedded Controller Renesas H8S/2161BV}}
{{gallery_end}}

===ThinkPad {{T60}}===
Found by Marco Kraus for use in [http://www.kraus.tk/projects/IBMDoK/ IBMDok].
EC offset Index in "thermal" Location (estimated)
0x78 1 CPU 0
0x79 2 HDD
0x7A 3 HDD
0x7B 4 GPU
0x7C 5 Battery
0x7D 6 n/a
0x7E 7 Battery
0x7F 8 n/a
0xC0 none ?
0xC1 none ?
0xC2 none ?

The CPU thermal sensors seem to be exposed in both {{path|/proc/acpi/thermal_zone/THM0/temperature}} and {{path|/proc/acpi/thermal_zone/THM1/temperature}}, though the latter curiously seems to exist only in this file and nowhere in {{path|/proc/acpi/ibm/ecdump}}.

Talk:Problems with fglrx

2006-06-29T19:25:00Z

Hypnotoad: /* atieventsd */

== using kernel AGP vs fglrx AGP ==

Anyone know whether this makes a performance and/or stability difference?

== 8.20.8 and later works with current Debian sid packages ==

<pre>
spiney@t43p:~$ dpkg -l xserver-xorg
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================-============================-==================
ii xserver-xorg 6.9.0.dfsg.1-2 the X.Org X server
spiney@t43p:~$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY FireGL V3200 Pentium 4 (SSE2) (FireGL) (GNU_ICD)
OpenGL version string: 1.3.5519 (X4.3.0-8.20.8)
</pre>

--[[User:Spiney|spiney]]
----

Ahh - thanks for the info. You perhaps compiled the modules for the drivers yourself and did not use the debian packaged fglrx-driver? Thus, it must be an unneeded limitation on the debian packaged driver which limits its installation... Full listing at http://packages.debian.org/unstable/x11/fglrx-driver which lists as required packages:

xserver-xorg (<< 6.8.99)
the X.Org X server
xserver-xorg (>= 6.8.0)

The first limitation (<<6.8.99) is what prevents installation. I'm sure I could force apt to install it, but I may go back to compiling the modules myself, as using fglrx 8.20.8 with kernel 2.6.15 needs a small patch to compile correctly anyway... --[[User:gsmenden|gsmenden]]

Spiney, where exactly do you have your package from? I re-build the 8.20.8-package from debian with the <<6.8.99 dependecy removed, but when I try to run X, I get
[R200Setup] X version mismatch - detected X.org 7.0.0.0, required X.org 6.8.0.0
(EE) Failed to load module "fglrx" (module requirement mismatch, 0)
Any hints? --[User:nomeata|nomeata]

I used the ati-installer (the huge download), created a Debian sid package and installed it, but got the same error. The installer seems to fetch the wrong driver version from the archive, so I extracted it with

{{cmd|./ati-driver-installer-8.20.8-i386.run --extract <sometempdir>|}}

and put the necessary files from the created {{path|<sometempdir>/x690}} subdirectory into {{path|/usr}} by hand. All IIRC, it's been some time since. :)

--[[User:Spiney|spiney]] 07:29, 11 Jan 2006 (CET)

Thanks for the pointer. This is how you get proper debian packages out of the ati-installer:
./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
cd fglrx-tmp
$editor packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
./fglrx-tmp/packages/Debian/ati-packager.sh --buildpkg sid
cd ..
sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Nomeata|Nomeata]] 00:35, 13 Jan 2006 (CET)

----

I had to do following steps :

$ ./ati-driver-installer-8.20.8-i386.run --extract fglrx-tmp
$ cd fglrx-tmp
$ ''editor'' packages/Debian/ati-packager.sh # in the line "sid|unstable) X_DIR=x680;;", put a x690 for the x680
$ ./packages/Debian/ati-packager.sh --buildpkg sid
$ cd /tmp
$ sudo dpkg -i fglrx-kernel-src_8.20.8-1_i386.deb fglrx-driver_8.20.8-1_i386.deb
--[[User:Fbianco|Fbianco]] 13:36, 26 February 2006 (CET)

----

Nice - confirmed works on my T43p running sid. From then on (or until 8.21.x comes out) you'll have to tell apt to hold back fglrx-driver package, or it will try to "update" fglrx-driver to 8.20.8-1.1 and therefore revert back to the problematic drivers.
--[[User:gsmenden|gsmenden]]
----

Thanks for the info, Nomeata, that's a lot cleaner a solution than my manual way.

--[[User:Spiney|spiney]] 08:32, 13 Jan 2006 (CET)
----

To get this working under 2.6.15 with x.org 6.9, you will also need to apply a small patch - there is a link on the main article page. After you install the fglrx-driver package with the 6.9 versioning hack above, go to
/usr/src/modules
and copy the patch here. Modify the first two lines of the patch file to take out the "build_mod" directory, e.g. first line should begin with
--- fglrx.orig/firegl_public.c
and call it with the -p0 strip option. It should patch the firegl_public.c file cleanly. You can then install as usual for your kernel (2.6.14.x or 2.6.15) using module-assistant.

Update - although X will come up in kernel 2.6.15 with the fglrx drivers patched as above, there is some strange behavior exhibited in all of X apllications - frequent hanging of applications when closing windows. Reverting back to the radeon driver in 2.6.15 solves these - so it is likely the ATI proprietary driver causing some problems.

Yet another update - fglrx 8.21.7 is out as of 1/19/2006, now supporting OpenGL 2.0, so eventually we will have beautiful complex shading / fog effects on Linux, too. It works well with X.Org 6.9 out of the box.

Unfortunately, this version gives the same problems when used (unpatched) with kernel 2.6.15 with strange lockups occasionally requiring reset of X. I have not tried this with the ~10 line patch listed on the main site, but that patch not work for me with 8.20.8. Anybody else have experience with 2.6.15 and fglrx?

Yay - new version out - 8.22.5 - works well with 2.6.15.x. Finally, running a plain-vanilla kernel on a T43p! (SATA+libata passthrough+SMART in mainline, 3d accel drivers up to date. Linux life is good.)

--[[User:gsmenden|gsmenden]] 12:39, 9 Feb 2006 (EST)
----

I don't know which patch you mean exactly (10 lines? the patch from lkml is just one line changed, no?), but I've been using 8.20.8 with 2.6.15 for quite some time (actually started with some -rc version IIRC), no lockups at all. No idea about 8.21.7 though, because I switched to 2.6.16-rc1 and can't compile the fglrx module at the moment, need to investigate the cause.

--[[User:Spiney|spiney]] 07:24, 21 January 2006 (CET)
----

Ok - strange. Yeah, the actual change is only one line, the rest is just commenting, etc. The lockups that I get are quite rare, but flightgear occasionally gives a hard lock. glxgears and fgl_glxgears work fine, netscape occasionally will hard-lock, and strangely enough issuing a shutdown command often makes the display blank and hard lock. I can't reproduce them too consistently, but these _never_ occur with the radeon driver / mesa or under 2.6.14.x.

Unfortunately vanilla 8.21.7 with kernel 2.6.15.1 (Xorg 6.9) gives the same X lockups.

--[[User:gsmenden|gsmenden]] 11:36, 21 Jan 2006 (EST)
----

I can't compile the 8.21.7 driver modules with 2.6.15.1 at all. They compile with 2.6.14.4 cleanly and 8.20.8 compile with 2.6.15.1.
What I don't understand though is, that when I let the ATI installer build debian packages, it does so without hassle, but the packages don't work.
(this is about 8.21.7 - 2.6.15.1) Also patching doesn't seem to help. It shouldn't of course.

--[[User:Rasto|Rasto]] 15:04, 23 Jan 2006 (CET)

I looked at the compile problems last night. I have no idea, how it is possible that it works for other people with 2.6.15, perhaps when you install
precompiled modules? I don't really understand how that ati-installer thing works. Anyway. This may solve the problems with 8.21.7 and 2.6.15-
it is just two minor line changes (+ the one line patch with little extra), but now it compiles. pm_register and similar were moved to linux/pm_legacy.h
in 2.6.15, so that's one problem. It also reports unknown symbol verify_area, but this should not pose a problem, as it is already obsolete and redundant.
If you feel, that the one line should be left as the separate patch, copy it somewhere else and change it. It's here [http://people.ksp.sk/~rasto/fglrx_with_2.6.15.patch], but I'll put it on the main page as well.

--[[User:Rasto|Rasto]] 18:29, 25 Jan 2006 (CET)

== Disabling the external VGA port? ==

Does anyone know how disable the VGA port ''completely'' even when a cable is attached? Fiddling around with the DesktopSetup and ForceMonitor options didn't do the trick for me, and the MonitorLayout option found in some documentation is no longer valid in the current fglrx driver.

--[[User:Spiney|spiney]] 19:42, 10 Jan 2006 (CET)
----

== Debian-specific script to switch fglrx<->radeon ==

Don't know where to put it exactly, but if someone's interested (and using Debian), I've put up a [http://linux.spiney.org/debian_gnu_linux_on_an_ibm_thinkpad_t43p_graphics_card_switching_fglrx_radeon script for easily switching graphics driver configurations]. Feedback appreciated (altho I haven't got any to the xscreensaver patch ;)), especially if someone could do something similar for other distributions (Gentoo being half-way there it seems) and incorporate it into the script.

--[[User:Spiney|spiney]] 15:25, 17 January 2006 (CET)
----

----
==Compile ATI driver???==
How can you compile a binary only distributed driver? If I'm not getting something wrong, please change the formulation of the just added info.
[[User:Wyrfel|Wyrfel]] 20:10, 25 January 2006 (CET)
----
[http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html#overview1]
"The driver as a whole is made of three main components: the driver proper, a replacement libGL and a kernel module. The driver and libGL are in the fglrx-driver package, the kernel module's source code is in the fglrx-kernel-src package."
--[[User:Dunno|Dunno]] 23:49, 13 February 2006 (CET)
----
Yepp, my fault, didn't think of the kernel part when i wrote that. [[User:Wyrfel|Wyrfel]] 02:50, 14 February 2006 (CET)
----

== On Kernel 2.6.16(_rc4-mm1) fglrx doesnÂ´t load anymore ==

Hi,

if i emerge ati-drivers 8.22.5 and try to modprobe it on Kernel 2.6.16_rc4-mm1 i get the following console output:
<pre>
FATAL: Error inserting fglrx (/lib/modules/2.6.16-rc4-mm1/video/fglrx.ko): Unknown symbol in module, or unknown parameter (see dmesg)
</pre>
my dmesg Output reads:
<pre>
fglrx: Unknown symbol inter_module_unregister
fglrx: Unknown symbol inter_module_get_request
fglrx: Unknown symbol inter_module_put
fglrx: Unknown symbol inter_module_register
</pre>
from the ati-driver wiki i know that the driver runs on 2.6.16 up to rc3. But on the mm Series it doesnt run since 2.6.15.4-mm4.

Help would be appreciated...

Thanks and Greets

Oli

----
Have a look at the (currently) last entry on http://www.rage3d.com/board/showthread.php?t=33847019, which explains how to revive the old inter_module routines. HTH

--[[User:Nephilim|Nephilim]] 19:41, 22 March 2006 (CET)

Link to the specific post: http://www.rage3d.com/board/showthread.php?p=1334242855#post1334242855
--[[User:Thinker|Thinker]] 20:00, 22 March 2006 (CET)
----
I have a t43p / Debian Sid running 2.6.16 debian kernel compile the debian way. And the fglrx modules compiled.
There are two problems that I can not seem to fix...
o If I log out of kde to kdm/ or the login, everything goes black, even Alt+Ctrl+F1 does not work. It is not locked up as Ctrl+Alt+Del does a proper restart.
o The other problem is on the second monitor the screen boundary is not right. Putting the mouse to the bottom cause a vertical blur. As long as the mouse is not at the bottom of the second screen all is well.

--[[User:Lters|Lters]] 14:35, 7 April 2006 (CEST)

Did you tell KDM to restart the X server when logging out? It is described in a link on the main article page under "Hang when logging out." I don't have two monitors so I'm not sure about your other problem...
--[[User:gsmenden|gsmenden]] 20:55, 9 April 2006 (EST)

== Suspend2 and fglrx ==

There seems to be a nice trick that allows the laptop to hibernate properly when set.
One should set this setting into the hibernate.conf file:

ProcSetting extra_pages_allowance 5000

Source: http://wiki.cchtml.com/index.php/Suspend2

--[[User:Assen|Assen]] 22:04, 3 May 2006 (CEST)

==Emacs with GUI affected==
I installed fglrx 8.20.8 on SuSE 10.0 with kernel 2.6.13 on T43 and fglrx 8.24.8 on Ubuntu 5.10 with kernel 2.6.12 on T40. On both systems, emacs works well with "-nw" option. However, in the first system, emacs doesn't respond to any key stroke when started with GUI interface, but it works well with "emacs -font fixed". In the second system, Emacs displays all characters as empty rectangles and responds to all key strokes althouth they are illegible. If I use the xorg.conf before fglrx was installed, then emacs works perfectly. I doubt that the problem is caused by the font. But it stays there even if I use the same fontpaths under section "Files".

Does anyone else have this problem? I haven't found any other X applications affected by the use of the driver.
--[[User:Bitcalc|Bitcalc]] 04:02, 30 May 2006 (CEST)

==atieventsd==
With driver version 8.25.16, I noticed a blinking of the HDD-LED every second. When viewing {{path|/var/log/messages}}, it revealed that each second, there was a message

atieventsd[3331]: Unable to bind control socket to /var/run/atieventsd.socket: Address already in use.

Anybody else with this problem? What is this atieventsd for anyways? When I kill it, the led stops blinking the there are no more messages...

--[[User:Hypnotoad|Hypnotoad]] 19:07, 21 June 2006 (CEST)

Nevermind, problem solved with the newest driver version. It was obviously a quite common bug...
--[[User:Hypnotoad|Hypnotoad]] 21:25, 29 June 2006 (CEST)

ATI Mobility Radeon X300

2006-06-28T07:36:52Z

Hypnotoad: /* With the fglrx 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;">
=== ATI Mobility Radeon X300 ===
This is an ATI video adapter

=== Features ===
* Chipset: ATI M22
* PCI ID: 1002:5460
* PCI Express x16
* 32 or 64MB GDDR1 on-chip video memory
* "HyperMemory": can use system memory for graphics processing
* "PowerPlay 4.0" technology for dynamic engine clock, memory clock and core voltage, refresh rate reduction and thermal status reporting.
</div>
|style="vertical-align:top" |
|}

See [http://www.ati.com/products/radeonx300/specs.html specifications] from ATI, as well as the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "snapshot" data sheet] (referes to the 32MB on-chip, 128MB "HyperMemory" version).

=== Linux driver ===

The X.org [[radeon]] driver works well and support most (but not all) features. ATI provides [[fglrx]], a closed-source alternative adding some functionality such as TV out and 3D acceleration.

==== 3D acceleration ====

The X.org [[radeon]] driver, in conjuction with the [[R300]] DRM driver, provides 3D acceleration. This is experimental, does not support all feature and may be unstable.

You may also use [[fglrx]], a closed-source ATI driver provided by ATI.

==== ThinkPad LCD ====
Display on the internal LCD works as long as you set the monitor settings correct.

==== External VGA port ====
There are known problems. Both the <tt>radeon</tt> and [[fglrx]] drivers turn off the switching between internal and external port.

=====With the <tt>vesa</tt> driver=====
Using the "vesa" driver built into X.org, mode switching modes. However, this loses acceleration and some capabilities.

=====With the <tt>radeon</tt> driver=====
On-the-fly swiching doesn't work. To activate both ports in clone mode with a reasonable CRT refresh rate, use the following in {{path|/etc/X11/xorg.conf}}:

Section "Device"
Identifier "Videocard0"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility X300"

Driver "radeon"
Option "DynamicClocks" "on"

Option "MergedFB" "on"
Option "MonitorLayout" "LVDS, CRT"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "50-82"
EndSection

Note that without the <tt>MonitorLayout</tt> option, if the external monitor is connected when X starts then the LCD will be deactivated and you will need to restart X.

(Tested wth Fedora Core 4 on ThinkPad {{T43}}).

See also the related discussion about [[Additional options for the radeon driver]].

=====With the [[fglrx]] driver=====
On-the-fly works with <tt>aticonfig</tt> in the newest Drivers, see [[Fglrx#Display_Switching_.28Dynamic_Display_Management.29|Display Switching]]. Additionally, to use both ports there is the possibility to either have the monitor connected during X startup, or force activation of both ports by adding
Option "ForceMonitors" "lvds,crt1"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}}. Powering the CRT port consumes 400-500mW, regardless of whether a CRT is attached.

==== S-Video port (TV-out) ====

Works with the proprietary [[fglrx]] driver (as of version 8.19.10). To activate, add
Option "ForceMonitors" "lvds,tv"
to the <tt>Device</tt> section in your {{path|/etc/X11/xorg.conf}} and restart X.

==== DVI port ====
??

=== 3D acceleration ===
OpenGL 3D acceleration is provided by the proprietary [[fglrx]] driver (when DRI is enabled). Note that performance is affected by the power saving mode.

The open source <tt>r300</tt> [[DRM]] module also aims to provide 3D acceleration. This currently requires the CVS/GIT versions of [[X.org]], [[DRM]] and [[Mesa]], and has been observed to occasionally crash (e.g., when running Google Earth or <tt>ppracer</tt>on a {{T43}}). You can [[How to compile an experimental X server|install it experimentally]] for testing.

=== Linux kernel Framebuffer driver ===

radeonfb might cause problems with hardware acceleration under X on some systems, vesafb and vesafb-tng on the other hand has been reported to work just fine.

=== Clock rates, voltage and power===
{| border="1" cellspacing="0" cellpadding="2"
|+ Clock rates, voltages and power {{footnote|1}}
! Mode !! core freq !! memory freq !! voltage !! idle !! 3DMarks (Windows, 1600x1200, LCD only)
|-
| Performance || 300 || 230 MHz || 1.15V || 2.98 W || 8.28 W
|-
| Balanced || 183 || 210 MHz || 1.00V || 1.71 W || 3.88 W
|-
| Battery || 120 || 105 MHz || 1.00V || 1.61 W || 2.74 W
|}

{| border="1" cellspacing="0" cellpadding="2"
|+ ATI drivers for Windows {{footnote|2}} and [[fglrx]]
! Mode !! core freq !! memory freq
|-
| Performance || 297.00 || 229.50
|-
| Balanced || 209.25 || 182.25
|-
| Battery || 104.63 || 121.50
|}

Experimentally, the difference between the Performance and Battery settings under Linux with the <tt>radeon</tt> driver and <tt>DynamicClocks</tt> enabled is roughly 0.3W and 3-4 degrees in GPU temperature on a ThinkPad {{T43}}. Further frequency reduction leads to display flickering or corruption.

See [[How to make use of Graphics Chips Power Management features]] for details on how to control this using [[Rovclock]], [[How to make use of Graphics Chips Power Management features|<tt>DynamicClocks</tt> option to the <tt>radeon</tt> driver]] and or the [[fglrx]] driver.

Presently the lowest idle-mode power consumption is achieved using the proprietary [[fglrx]] driver and
# aticonfig --set-powerstate=1 --effective=now

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{Z60m}}

{{footnotes|
#according to the [http://www.ati.com/products/embedded/mobilityradeonx300/M22-CSP64_Product_Snapshot.pdf "Snapshot" data sheet] (which refers to the 32MB on-chip, 128MB "HyperMemory" version)
#inspected using [http://www.pbus-167.com/chc.htm Notebook Hardware Control]
}}

[[Category:Components]]

Installing OpenSUSE 10.1 on a ThinkPad T43

2006-06-21T20:08:37Z

Hypnotoad:

Talk:Problems with fglrx

2006-06-21T17:07:50Z

Hypnotoad: atieventsd problems

Installing OpenSUSE 10.1 on a ThinkPad T43

2006-06-20T20:03:44Z

Hypnotoad: Hotkeys done

Most things run just fine after installation, the Rest I got working with the great articles here.

{{Todo|Finish article - it's not done yet!}}

==Installation==
{{WARN| The Pre-Desktop-Area has to be protected before installation, otherwise the Recovery-System will be lost. To do so, set Predesktop-Area to "Secure" in BIOS. Additionally, it's always useful to have the Recovery-CDs burned before an installation attempt}}

The automatic shrinking of the NTFS-partition did not work during the Installation of {{SUSE}}, so I shrinked it with QtParted from a Knoppix-DVD.
To be able to boot Windows and Linux (via Grub) and the Recovery-System (with {{ibmkey|Access IBM|#495988}}), install the bootloader in the new, extended partition (usually <tt>/dev/sda</tt>).

Besides that, everything went fine, most Hardware was set up correctly: Graphics Card, Touchpad and Trackpoint, WLAN, Bluetooth, Modem (yet untested), Volume Control.

==ACPI==
Everything set up correctly, [[ibm-acpi]] ist installed, Suspend-to-RAM and Suspend-to-Disk work with the keys already assigned to them. I still miss [[RediSafe]] though, maybe I'll use [[Software Suspend 2]] some day.

==Hotkeys==
[[How to get special keys to work]] gives a general overview.

Suspend keys worked by default installation, as did {{key|Fn}}{{key|F5}} for switching Bluetooth on and off. For the remaining keys, the <tt>nvram</tt>-module was missing. So when {{path|/dev/nvram/}} is missing, you have to create it first:

{{cmdroot|mknod /dev/nvram c 10 144}}

and load it with

{{cmdroot|modprobe nvram}}

Additionally, I had to specify the module to be loaded automatically at {{path|/etc/sysconfig/kernel}}:
[...]
MODULES_LOADED_ON_BOOT="nvram"
[...]

Last, the access rights had to be corrected. To do so, search for <tt>nvram</tt> in {{path|/etc/udev/rules.d/50-udev-default.rules }} and change the entry to:
KERNEL=="nvram", NAME="%k", GROUP="nvram", MODE="660"
so the users of group nvram have access to it. Of course that group has to exist, and you need to be a member of it:

{{cmdroot|groupadd nvram}}
{{cmdroot|usermod -G nvram username}}

After a reboot, you can use either [[tpb]] or the [[KMilo]]-Plugin in KControl (System Administration -> IBM Thinkpad Laptop) to set up the keys. I liked the OSD of KMilo better. Additionally, I set the Mixer setting to "Software" (<tt>MIXER ON</tt> in tpb), so the Mixer volume and mute status matches the one in KMix.

==Fingerprint Reader==
[[How to enable the fingerprint reader]] neatly explains everything. I had to do the last steps manually, because the [[Script for enabling the fingerprint reader]] did not run till the end on Suse 10.1

==3D Acceleration==
The Standard driver did work for 2D, but with no 3D acceleration. When I added
<pre>Section "Module"
[...]
Load "glx"
[...]
EndSection</pre>
to my {{path|/etc/X11/xorg.conf}}, the 3D acceleration worked with the OpenSource driver, but now there were problems with Suspend. So I decided for the proprietary [[fglrx]]-Driver directly from Ati. Installed fine, after I created a distribution-specific rpm with the Installer.

==Extensions==
[[How_to_configure_the_TrackPoint#Scrolling | Trackpoint Scrolling]]

==External Sources==
[http://omnibus.uni-freiburg.de/~s8arhorn/index.php?section=Linux&file=Suse%2010.1%20auf%20IBM%20Thinkpad%2043 My Installation article, in German]

How to configure the TrackPoint

2006-06-20T19:41:21Z

Hypnotoad: /* Using the X server (kernel 2.6.11+) */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |The [[Patch to enable advanced trackpoint configuration|kernel trackpoint driver]] is controlled by echoing values to special files. Common configuration options are outlined below.
{{NOTE|
*Starting from 2.6.13 config files for this driver are located in <tt>/sys/devices/platform/i8042/serio0/serio2</tt>. (This document uses the new locations.)
*From 2.6.11 on, they are in <tt>/sys/devices/platform/i8042/serio0</tt>.
*Prior to kernel 2.6.11, these files were located in <tt>/proc/trackpoint</tt>.
*Prior to kernel 2.6.9, these files were not files at all, but were command-line options to the psmouse module. (Note this means you must compile psmouse as a module!) See http://stephen.evanchik.com/node/16.
}}
|}

==General Configuration==
The configuration options are reflected by the files you can find in {{path|/sys/devices/platform/i8042/serio0/serio2}}. See the [[Patch to enable advanced trackpoint configuration|TrackPoint driver page]] for a complete list.
Configuration is done by echoing the appropriate values into these special files.

==Most common Features==
The most common settings are '''Press to Select''', '''sensitivity''', '''speed''' and '''scrolling'''.

===Press to Select===
Press to Select allows you to tap the control stick which will simulate a left click. You can enable this feature by typing the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

Press to Select should now be enabled. You can disable it in a similar manner:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/press_to_select}}

===Sensitivity & Speed===
Adjusting the speed and sensitivity of the TrackPoint requires echoing a value between 0 and 255 into the appropriate file. For example, for a speed of 120 and a sensitivity of 250, type the following into a terminal:

:{{cmdroot|echo -n 120 > /sys/devices/platform/i8042/serio0/serio2/speed}}
:{{cmdroot|echo -n 250 > /sys/devices/platform/i8042/serio0/serio2/sensitivity}}

Feel free to experiment with your settings until you find a combination that is comfortable.

===Scrolling===
====Using a kernel prior to 2.6.11====
The scrolling action is essentially the same as is used in the TrackPoint Windows drivers. To enable this feature, type the following in to a terminal (you may need to be root):

:{{cmdroot|echo -n 1 > /proc/trackpoint/scroll}}

Then press the middle button and push the stick up and down to scroll. Similarly, to disable scrolling:

:{{cmdroot|echo -n 0 > /proc/trackpoint/scroll}}

====Using the X server (kernel 2.6.11+)====
The scroll setting has been removed from the trackpoint driver in kernel versions 2.6.11 and above. Scroll emulation should now be handled in the X server.

The necessary functionality, known as "EmulateWheellTimeout" allowing to use button 2 for a middle click, wasn't implemented in Xorg prior to 6.9/7.0. However, there was a patch included in most distributions packages of Xorg, which was announced [http://www.mail-archive.com/devel@xfree86.org/msg03333.html here]. You can find an updated version of the package in the experimental branch of {{Debian}} or try to build the mouse driver yourself with the information in the announcement. This has successfully been tried with FC3's 6.8.2 packages.

Once this functionality is in the X.org, add these lines to your TrackPoint configuration section in {{path|/etc/X11/xorg.conf}}:

Option "EmulateWheel" "on"
Option "EmulateWheelButton" "2"

It may also be necessary to add these lines, which change axis orientation:

Option "XAxisMapping" "4 5"
Option "YAxisMapping" "6 7"

Now restart X and hold down button 2 and move the mouse to scroll, or just press and release button 2 for a middle click.

===== EmulateWheelTimeout temporarily broken =====

Unfortunately, there was a regression so that EmulateWheelTimeout was broken in X.org 6.9.0, and fixed
on March 20th, 2006.
You can see the [https://bugs.freedesktop.org/show_bug.cgi?id=5071 primary bug report] here, and also reports on the [http://qa.mandriva.com/show_bug.cgi?id=21196 Mandriva] and [http://lists.debian.org/debian-x/2006/01/msg00249.html Debian] packages.

===== Older versions of X.org =====

For older versions of Xorg or for Xfree86 ({{path|/etc/X11/XF86Config}}) try this:

Option "Emulate3Buttons" "true"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"

Now restart X and hold down button two and move the mouse for scrolling. To get a middle click, press buttons 1 and 3 simultaneously.

==Soft Transparent Mode==
If you wish to connect a special device to the external PS/2 port, you should consider using "Soft Transparent Mode" so that the TrackPoint controller does not interpret any commands sent to the external PS/2 port. You can enable soft transparent mode by typing the following in to a terminal:

:{{cmdroot|echo -n 1 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

Disabling soft transparent mode is similar:

:{{cmdroot|echo -n 0 > /sys/devices/platform/i8042/serio0/serio2/transparent}}

==Modify trackpoint parameter permanently in trackpoint.h==
If you do not want to run a script to reconfigure the trackpoint
you can change the default settings in the trackpoint header file that is located in
/usr/src/<KERNEL_VERSION>/drivers/input/mouse/trackpoint.h.

First you must convert the values (decimal numbers) you normaly echo to /sys/[...] to hex:

'''echo -e 'obase=16;<DECIMAL_NUMBER>' | bc'''

Then simply replace the default hex values in trackpoint.h, run 'make && make modules_install' to recompile and install psmouse.ko (should be compiled as module)

Example patch (speed=100, sensitivity=190, press_to_select=1):
<pre>
--- trackpoint.h.orig 2006-01-17 16:18:30.000000000 +0100
+++ trackpoint.h 2006-01-17 16:25:47.000000000 +0100
@@ -108,9 +108,9 @@
/*
* Default power on values
*/
-#define TP_DEF_SENS 0x80
+#define TP_DEF_SENS 0xBE
#define TP_DEF_INERTIA 0x06
-#define TP_DEF_SPEED 0x61
+#define TP_DEF_SPEED 0x64
#define TP_DEF_REACH 0x0A

#define TP_DEF_DRAGHYS 0xFF
@@ -123,7 +123,7 @@

/* Toggles */
#define TP_DEF_MB 0x00
-#define TP_DEF_PTSON 0x00
+#define TP_DEF_PTSON 0x01
#define TP_DEF_SKIPBACK 0x00
#define TP_DEF_EXT_DEV 0x01
</pre>

==Configure firefox for using trackpoint horizontal scrolling==
Vertical Scrolling seems to work out of the box in firefox if you followed the steps above.
Anyway, there is a problem when you doesnt scroll exactly vertical, because horizontal scrolling turns into
browser BACK/FORWARD commands.
You can avoid this by typing about:config + ENTER in the address bar of firefox.
You have to adjust the following options:

<pre>
mousewheel.horizscroll.withcontrolkey.action = 3;
mousewheel.horizscroll.withcontrolkey.numlines = 1;
mousewheel.horizscroll.withcontrolkey.sysnumlines = true;

mousewheel.horizscroll.withnokey.action = 0;
mousewheel.horizscroll.withnokey.numlines = 1;
mousewheel.horizscroll.withnokey.sysnumlines = true;

mousewheel.horizscroll.withshiftkey.action = 1;
mousewheel.horizscroll.withshiftkey.numlines = 1;
mousewheel.horizscroll.withshiftkey.sysnumlines = true;
</pre>

==Configure Opera for using trackpoint horizontal scrolling==
You'll experience the same annoying problem with the popular browser Opera. To fix this you need to edit the configfile <tt>/usr/share/opera/ini/standard_mouse.ini</tt> and comment the following lines out
<pre>
Button6 = Back
Button7 = Forward
</pre>
so they look something like that
<pre>
;Button6 = Back
;Button7 = Forward
</pre>
Remember, Button6 and Button7 do not so coincidental correspond with our X configuration we know from above:
<pre>
Option "YAxisMapping" "6 7"
</pre>

2006-05-29T11:50:16Z

Hypnotoad: /* Troubles using software suspend */

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. 
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}. 
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. 
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:

$ 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)

try this:

# mkdir -p /usr/X11R6/lib/modules/dri
# 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].

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

<pre>
# rm /usr/lib/libGL.so*
# rm /usr/X11R6/lib/libGL.so*
# cd /usr/X11R6/lib
# cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .
# ln -s libGL.so.1.2 libGL.so.1
# ldconfig
</pre>

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

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

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' (rage3d.com/board) Linux area.

There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 7.0 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.

===Hardlock on X logout===
Up from driver version 8.19.10 you will expierence 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 file add:
AlwaysRestartServer=true

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

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

Information from gentoo bugtracker: http://bugs.gentoo.org/show_bug.cgi?id=113685

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

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

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

== Other Known Problems ==

===Emacs with GUI affected===
I installed fglrx 8.20.8 on SuSE 10.0 with kernel 2.6.13 on T43 and fglrx 8.24.8 on Ubuntu 5.10 with kernel 2.6.12 on T40. On both systems, emacs works well with "-nw" option. However, in the first system, emacs doesn't respond to any key stroke when started with GUI interface, but it works well with "emacs -font fixed". In the second system, Emacs displays all characters as empty rectangles and responds to all key strokes althouth they are illegible. If I use the xorg.conf before fglrx was installed, then emacs works perfectly. I doubt that the problem is caused by the font. But it stays there even if I use the same fontpaths under section "Files".

Does anyone else have this problem? I haven't found any other X applications affected by the use of the driver.

Problems with fglrx

2006-05-29T11:47:42Z

Hypnotoad: /* Troubles using software suspend */

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. 
Go to {{path|1=/lib/modules/<your linux kernel version>/}} and type {{cmdroot|1=grep fglrx modules.dep}}. 
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. 
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:

$ 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)

try this:

# mkdir -p /usr/X11R6/lib/modules/dri
# 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].

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

<pre>
# rm /usr/lib/libGL.so*
# rm /usr/X11R6/lib/libGL.so*
# cd /usr/X11R6/lib
# cp /usr/lib/fglrx/diversions/lib/libGL.so.1.2 .
# ln -s libGL.so.1.2 libGL.so.1
# ldconfig
</pre>

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

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

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' (rage3d.com/board) Linux area.

There were some rumors that composite support was fast with the open-source 2d accelerated drivers in x.org 7.0 (as opposed to 6.8.x). Alas, trying this gives better results than the proprietary drivers, but it is still too slow to be reasonably useful.

===Hardlock on X logout===
Up from driver version 8.19.10 you will expierence 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 file add:
AlwaysRestartServer=true

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

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

Information from gentoo bugtracker: http://bugs.gentoo.org/show_bug.cgi?id=113685

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

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

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

== Other Known Problems ==

===Emacs with GUI affected===
I installed fglrx 8.20.8 on SuSE 10.0 with kernel 2.6.13 on T43 and fglrx 8.24.8 on Ubuntu 5.10 with kernel 2.6.12 on T40. On both systems, emacs works well with "-nw" option. However, in the first system, emacs doesn't respond to any key stroke when started with GUI interface, but it works well with "emacs -font fixed". In the second system, Emacs displays all characters as empty rectangles and responds to all key strokes althouth they are illegible. If I use the xorg.conf before fglrx was installed, then emacs works perfectly. I doubt that the problem is caused by the font. But it stays there even if I use the same fontpaths under section "Files".

Does anyone else have this problem? I haven't found any other X applications affected by the use of the driver.