ThinkWiki - User contributions [en]

Template:ThinkWiki News

2008-02-20T13:32:25Z

Xoby: Correct "?" symbol unsupported into URL

{|
{{News|20.02.2008|X300 design articles on [http://lenovoblogs.com/designmatters lenovo blogs] and [http://www.businessweek.com/magazine/content/08_08/b4072042350389.htm businessweek]}}
{{News|14.02.2008|Ultralight Lenovo X300 Series Thinkpad [http://gizmodo.com/346797/ultralight-lenovo-x300-series-thinkpad-leaked leaked]}}
{{News|12.02.2008|Vista UDF 2.01 media [[UDF_2.01_on_Linux|now work with Linux]]!}}
{{News|05.02.2008|Added the cool [http://recaptcha.net/plugins/mediawiki/ Recaptcha extension].}}
{{News|03.02.2008|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.1]].}}
{{News|18.01.2008|Again ThinkWiki got shiny new lightning fast [[ThinkWiki:Hardware|hardware]].}}
{{News|14.11.2007|[http://www.lesswatts.org lesswatts.org] now hosts the [http://www.lesswatts.org/projects/acpi/ Linux ACPI] project, as well as [http://www.lesswatts.org/projects/powertop/ powertop] and many other important power management projects.}}
{{News|19.10.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.0]]. We apologize for some downtime on Oct. 15th and 16th.}}
{{News|11.10.2007|The ThinkPad turns 15 years old!}}
{{News|13.06.2007|A preliminary version of the reverse-engineered R500 driver is [http://lwn.net/Articles/237920/ available].}}
{{News|06.06.2007|ThinkWiki finally runs on new [[ThinkWiki:Hardware|hardware]].}}
{{News|22.05.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.10.0]].}}
{{News|13.05.2007|Intel released [http://www.linuxpowertop.org/ PowerTOP], helps to prolong battery life.}}
|}

Template:ThinkWiki News

2008-02-20T13:26:05Z

Xoby:

{|
{{News|20.02.2008|Ultralight Lenovo X300 Series Thinkpad [http://lenovoblogs.com/designmatters/?p=201 lenovo blogs] and businessweek article [http://www.businessweek.com/magazine/content/08_08/b4072042350389.htm Building the Perfect Laptop].}}
{{News|14.02.2008|Ultralight Lenovo X300 Series Thinkpad [http://gizmodo.com/346797/ultralight-lenovo-x300-series-thinkpad-leaked leaked]}}
{{News|12.02.2008|Vista UDF 2.01 media [[UDF_2.01_on_Linux|now work with Linux]]!}}
{{News|05.02.2008|Added the cool [http://recaptcha.net/plugins/mediawiki/ Recaptcha extension].}}
{{News|03.02.2008|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.1]].}}
{{News|18.01.2008|Again ThinkWiki got shiny new lightning fast [[ThinkWiki:Hardware|hardware]].}}
{{News|14.11.2007|[http://www.lesswatts.org lesswatts.org] now hosts the [http://www.lesswatts.org/projects/acpi/ Linux ACPI] project, as well as [http://www.lesswatts.org/projects/powertop/ powertop] and many other important power management projects.}}
{{News|19.10.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.0]]. We apologize for some downtime on Oct. 15th and 16th.}}
{{News|11.10.2007|The ThinkPad turns 15 years old!}}
{{News|13.06.2007|A preliminary version of the reverse-engineered R500 driver is [http://lwn.net/Articles/237920/ available].}}
{{News|06.06.2007|ThinkWiki finally runs on new [[ThinkWiki:Hardware|hardware]].}}
{{News|22.05.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.10.0]].}}
{{News|13.05.2007|Intel released [http://www.linuxpowertop.org/ PowerTOP], helps to prolong battery life.}}
|}

Template:ThinkWiki News

2008-02-20T13:24:55Z

Xoby:

{|
{{News|20.02.2008|Ultralight Lenovo X300 Series Thinkpad [http://lenovoblogs.com/designmatters/?p=201 lenovo blogs] and businessweek article [http://www.businessweek.com/magazine/content/08_08/b4072042350389.htm Building the Perfect Laptop]}}
{{News|14.02.2008|Ultralight Lenovo X300 Series Thinkpad [http://gizmodo.com/346797/ultralight-lenovo-x300-series-thinkpad-leaked leaked]}}
{{News|12.02.2008|Vista UDF 2.01 media [[UDF_2.01_on_Linux|now work with Linux]]!}}
{{News|05.02.2008|Added the cool [http://recaptcha.net/plugins/mediawiki/ Recaptcha extension].}}
{{News|03.02.2008|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.1]].}}
{{News|18.01.2008|Again ThinkWiki got shiny new lightning fast [[ThinkWiki:Hardware|hardware]].}}
{{News|14.11.2007|[http://www.lesswatts.org lesswatts.org] now hosts the [http://www.lesswatts.org/projects/acpi/ Linux ACPI] project, as well as [http://www.lesswatts.org/projects/powertop/ powertop] and many other important power management projects.}}
{{News|19.10.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.11.0]]. We apologize for some downtime on Oct. 15th and 16th.}}
{{News|11.10.2007|The ThinkPad turns 15 years old!}}
{{News|13.06.2007|A preliminary version of the reverse-engineered R500 driver is [http://lwn.net/Articles/237920/ available].}}
{{News|06.06.2007|ThinkWiki finally runs on new [[ThinkWiki:Hardware|hardware]].}}
{{News|22.05.2007|ThinkWiki has been upgraded to [[Special:Version|MediaWiki 1.10.0]].}}
{{News|13.05.2007|Intel released [http://www.linuxpowertop.org/ PowerTOP], helps to prolong battery life.}}
|}

ThinkPad Mini-Dock

2007-11-27T07:08:15Z

Xoby: Cut internal audio while using dock audio connector

{| cellspacing="0" cellpadding="2" border="0"
| style="vertical-align:top;" | __TOC__
| 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;">
== IBM ThinkPad Mini-Dock ==
The [[ThinkPad Mini-Dock]] (Model 2878) offers a good compromise of features and price. It contains basic pass-through connections for all the notebook ports like the [[ThinkPad Port Replicator II]] does.
=== Features ===
* everything the [[ThinkPad Port Replicator II]] has
* 4 port USB 2.0 hub
* Integrated external power supply
* Integrated key-lock for securing the ThinkPad to the dock
===Pros & Cons===
* Positives: Integrated Power, Integrated 4-port USB, security
* Negatives: Price ($199 Retail)
* Compatibility: X20/30, T20/30/40, R30/50, and A20/30 series (Does not support X40/41, R40e/50e/51e, or G40/41)
* Warranty: One Year
</div>
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-45932 IBM Website for Mini-Dock]
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/92p1836.pdf ThinkPad Docking Solutions HMM (February 2003)] (248,638 Bytes)
* [ftp://ftp.software.ibm.com/pc/pccbbs/options/92p1837.pdf User's guide for the ThinkPad Port Replicator II and ThinkPad Mini-Dock] (196,180 Bytes)
|}

==4 port USB 2.0 hub==
Note that the USB provider is a hub - a few people have reported some USB peripherals (such as Palms) having problems due to it being a hub, although the majority of people do not have this problem, and the usefulness of the 4 port hub outweighs any potential downside. If you encounter problems, you can always use the USB ports on your Thinkpad to get a direct connection.
==DVI pass-through==
LCD monitors are getting larger and higher-resolution. Currently, DVI based on 165MHz TDMS transmitters can only (officially) support 1600x1200x32 at 60Hz, which is the resolution of your average 20" non-widescreen LCD. IBM's driver support for this resolution through DVI ports on docks has been inconsistent. Also in Linux you might experience [[Problem with DVI throughput|problems]] even with this resolution and IBM officially states that the pass-through DVI port only supports resolutions up to 1280x1024. Read [[Problem with DVI throughput|our page]] of information on how to solve these troubles.

Please be aware that not all Thinkpad models will support DVI output with a Dock. Apparently, all X and T models from the 20 series do not. Please add other models if you know about them to not support DVI.

== Cut internal audio while using dock audio connector ==
The internal speaker stays on even when you put an audio jack into the port replicator speaker out connector. To silence the internal speaker use the hardware mute button, which mutes both internal and connected audio and unmute through the software mixer, wich unmutes only the external audio.

== Supported ThinkPads ==
* {{A20m}}, {{A20p}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}
* {{A30}}, {{A30p}}, {{A31}}, {{A31p}}
* {{R30}}, {{R31}}, {{R32}}
* {{R40}}
* {{R50}}, {{R50p}}, {{R51}}, {{R52}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{T30}}
* {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}, {{T43}} (only models without Intel 915GM/GMS,910GML Chipset), {{T43p}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}
* {{X30}}, {{X31}}, {{X32}}

Sample Fn-F7 script

2007-11-12T22:38:41Z

Xoby: The script uses bash syntax and won't work with sh

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.

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 I have 1600x1200 monitor to the left of my internal 1024x768 monitor for a total max resolution of 2624x1200 (See [[Xorg RandR 1.2]] for more details):

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

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

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

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

Create /usr/local/sbin/thinkpad-fn-f7:

Note: you will have change EXTERNAL_OUTPUT and INTERNAL_OUTPUT to what xrandr shows, for example VGA and LVDS in this case:

$ xrandr | grep connected
'''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)

#!/bin/bash
#@ seva sevatech.com

EXTERNAL_OUTPUT="'''VGA'''"
INTERNAL_OUTPUT="'''LVDS'''"
EXTERNAL_LOCATION="'''left'''"

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

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

# Save the state to the file until we can figure it out by running xrandr
STATE_FILE=/var/lib/thinkpad/screen.state;
if [ ! -e $STATE_FILE ]; then
echo "internal" > $STATE_FILE
fi

STATE=$(cat $STATE_FILE)

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

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

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

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

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
DO=$(basename $0)
fi
if [ -z "$DO" ]; then
DO="internal"
fi

case "$DO" in
toggle|thinkpad-fn-f7)
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:"
xrandr | grep connected | 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
echo " If no command is given default is internal" >&2
;;
esac

As root, run the following commands,

{{cmdroot|mkdir -p /var/lib/thinkpad}}
{{cmdroot|echo "internal" > /var/lib/thinkpad/screen.state}}
{{cmdroot|chmod 755 /usr/local/sbin/thinkpad-fn-f7}}
{{cmdroot|service acpid restart}}

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

ATI Mobility Radeon 9600

2007-07-28T21:57:37Z

Xoby:

__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 9600 ===
This is an ATI video adapter

=== Features ===
* Chipset: ATI RV350 (M10)
* PCI ID: 1002:4c66
* AGP 4X
* 32 or 64MB DDR-SDRAM video memory
* External VGA up to: 1920x1200
</div>
|style="vertical-align:top" |
|}

=== Linux driver - OpenSource ===
This adapter is supported by recent versions of the [[radeon]] driver as found in X.Org and XFree86. The [[fglrx]] driver should also work.

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

==== External VGA port ====
Works if you setup the xorg.conf for two screens.

==== SVideo port ====
SVideo out is supported by the ati.2 driver from the [http://gatos.sourceforge.net/ GATOS project].<br/>
Read [[How to get TV-Out working on ATI graphic cards|here]] how to set it up.

==== 3D acceleration with the open source driver ====

All recent Distributions such as Fedora Core 5, *Ubuntu Dapper Drake, OpenSUSE have the r300 supported without patching. The r300 DRI driver was merged into Mesa 6.4.x. The X Window System (Xorg) 7.0 supports the r300 driver. Recent 2.6 kernels now have r300 DRM support added. This now should work out of the box if your using a recent distribution.

The old project page may be outdated now, development is now done in X.org.
:http://r300.sourceforge.net/

=== Linux driver - Proprietary ===
The [[fglrx]] driver adds 3D acceleration.

=== FreeBSD driver - open source ===
With RELENG_6 it is possible to get this card working with a reasonable level of ease. First you must apply this patch: http://people.freebsd.org/~anholt/dri/r300-drm.diff to your kernel source and compile a new kernel. I have only tested using this as a module. It works as the simple drm/radeon module. Once that is done install x11-servers/xorg-server-snap and graphics/dri-devel on top of a normal Xorg installation. With all that you SHOULD have dri working on a mobility 9600. Tested on a T42.

=== ThinkPads this chip may be found in ===
* {{T42}},{{T42p}}

[[Category:Components]]

How to get special keys to work

2007-07-28T20:47:37Z

Xoby: /* NumLock */

==Overview==
The following table gives an overview over the special keys found on ThinkPads and what is needed to make them work.
{| {{prettytable}}
! key !! standard function{{footnote|1}} !! tools supporting key{{footnote|2}} !! configurability{{footnote|3}} !! remarks
|-
| {{key|Fn}} || - || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || on release without completed key combination
|-
| {{key|Fn}}{{key|F1}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F2}} || lock screen || [[#ibm-acpi events|ibm-acpi]] || full || in models from T/X/Z 60 onwards
|-
| {{key|Fn}}{{key|F3}} || blank screen || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F4}} || suspend to ram || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|F5}} || switch bluetooth || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || in models starting from 2002
|-
| {{key|Fn}}{{key|F6}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F7}} || switch display || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F8}} || toggle display expansion || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]], [[#tpb configuration|tpb]] || additional actions ||
|-
| {{key|Fn}}{{key|F9}} || eject from dock || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full ||
|-
| {{key|Fn}}{{key|F10}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F11}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|F12}} || hibernate || [[#ibm-acpi events|ibm-acpi]], [[thinkpad-acpi]] || full || may generate ACPI event when not enabled in the ibm-acpi hotkey mask
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || brightness up || [[#ibm-acpi events|ibm-acpi]], [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|End}} || brightness down || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|PageUp}} || toggle thinklight || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{key|Fn}}{{key|Space}} || toggle zoom || [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{key|Fn}}{{key|Ins}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Del}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|Fn}}{{key|Backspace}} || - || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{key|NumLock}} || - || [[#xmodmap configuration|xmodmap]] || make working ||
|-
| {{key|Windows}} || - || [[#xmodmap configuration|xmodmap]] || remapping ||
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || help application || [[#tpb configuration|tpb]], [[KMilo]] || full ||
|-
| {{ibmkey|Home|#494949}} || open web browser || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Search|#494949}} || open search application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Mail|#494949}} || open mail application || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]], [[KMilo]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Favorites|#494949}} || open favorites || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Reload|#494949}} || reload web page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Abort|#494949}} || abort loading page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || only {{A30}}, {{A30p}}, {{A31}}, {{A31p}} and ext. keyboards
|-
| {{ibmkey|Backward|#494949}} || previous page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Forward|#494949}} || next page || [[#xmodmap configuration|xmodmap]], [[#tpb configuration|tpb]] || full || ext. keyboards and ThinkPads starting from 2002
|-
| {{ibmkey|Volume up|#494949}} || volume up || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume down|#494949}} || volume down || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Volume mute|#494949}} || mute volume || [[#tpb configuration|tpb]], [[KMilo]] || additional actions ||
|-
| {{ibmkey|Play/Pause|#494949}} || start/pause playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Down)
|-
| {{ibmkey|Stop|#494949}} || stop playback || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Up)
|-
| {{ibmkey|Next|#494949}} || play next || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Right)
|-
| {{ibmkey|Previous|#494949}} || play previous || [[#xmodmap configuration|xmodmap]] || full || {{X60s}} (Fn+Arrow Left)
|-
| {{ibmkey|Power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| Display lid || blank screen || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Ultrabay lid || announce ultrabay change || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| Dock eject || eject from dock || [[#ibm-acpi events|ibm-acpi]] || full ||
|-
| {{ibmkey|Tablet power|#494949}} || shutdown || [[#ibm-acpi events|ibm-acpi]] || full || triggered on pressing 3secs, but notebook goes off on 5sec press
|-
| {{ibmkey|Tablet orientation|#494949}} || rotates screen || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet shortcut|#494949}} || shortcut menu || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Esc|#494949}} || esc key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Enter|#494949}} || enter key || [[#mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Up|#494949}} || up key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet Down|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || down key || [[#Mapping keys with setkeycodes|setkeycodes]] || full ||
|}

==Triggering key events==
===ibm-acpi events===
Some of the following events require a {{cmdroot|echo enable,0xffff >/proc/acpi/ibm/hotkey}} in order to make acpi able to get information on them. These events can be used to [[How to configure acpid|configure acpid]].

{| {{prettytable}}
|+ events triggered by [[ibm-acpi]] for {{path|/etc/acpi/events}} files.
! key !! event
|-
| {{key|Fn}}{{key|F1}} || ibm/hotkey HKEY 00000080 00001001
|-
| {{key|Fn}}{{key|F2}} || ibm/hotkey HKEY 00000080 00001002
|-
| {{key|Fn}}{{key|F3}} || ibm/hotkey HKEY 00000080 00001003
|-
| {{key|Fn}}{{key|F4}} || ibm/hotkey HKEY 00000080 00001004
|-
| {{key|Fn}}{{key|F5}} || ibm/hotkey HKEY 00000080 00001005
|-
| {{key|Fn}}{{key|F6}} || ibm/hotkey HKEY 00000080 00001006
|-
| {{key|Fn}}{{key|F7}} || ibm/hotkey HKEY 00000080 00001007
|-
| {{key|Fn}}{{key|F8}} || ibm/hotkey HKEY 00000080 00001008
|-
| {{key|Fn}}{{key|F9}} || ibm/hotkey HKEY 00000080 00001009
|-
| {{key|Fn}}{{key|F10}} || ibm/hotkey HKEY 00000080 0000100a
|-
| {{key|Fn}}{{key|F11}} || ibm/hotkey HKEY 00000080 0000100b
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|-
| {{key|Fn}}{{key|Backspace}} || ibm/hotkey HKEY 00000080 0000100d
|-
| {{key|Fn}}{{key|Ins}} || ibm/hotkey HKEY 00000080 0000100e
|-
| {{key|Fn}}{{key|Del}} || ibm/hotkey HKEY 00000080 0000100f
|-
| {{key|Fn}}{{key|Home}}/{{key|Fn}}{{key|Pos1}} || ibm/hotkey HKEY 00000080 00001010
|-
| {{ibmkey|Power|#494949}} || button/power PWRF 00000080 xxxxxxxx
|-
| Display lid || button/lid LID 00000080 xxxxxxxx
|-
| Ultrabay eject || ibm/bay MSTR 00000003 00000000
|-
| Ultrabay inserted || ibm/bay MSTR 00000001 00000000
|-
| Dock eject || ibm/dock GDCK 00000003 00000001
|-
| Wireless switch || ibm/hotkey HKEY 00000080 00007000
|}

By disassembling and editing the DSDT, more events can be added. HKEY events are triggered by calls to the MKHQ function, e.g. <tt>\_SB.PCI0.LPC.EC.HKEY.MHKQ(0Ã—1007)</tt> will trigger "ibm/hotkey HKEY 00000080 00001007". Most of these can be found in <tt>_Qxx</tt> methods within the DSDT, which are executed on embedded controller events, e.g. _Q10 is triggered by pressing Fn-F7. You can add a call to MKHQ into an existing <tt>_Qxx</tt> method to get it recognized by ibm-acpi as well as creating new <tt>_Qxx</tt> methods, which if you're lucky will correspond to an EC event that IBM never used (e.g. A 770 will send Fn-Home/End/PgUp/PgDn to ibm-acpi if hacked in this fashion). For example, [http://www.wormnet.eu/ibm-g40/morebuttons.dsl this is a modified block of DSDT for a G40].

=== Pure ACPI events ===

A few keys can generate ACPI events of their own on certain ThinkPads, as long as they are masked off in the ibm-acpi hotkey's mask (or the hotkey feature is disabled in ibm-acpi).

If you want the ThinkPad's BIOS and ACPI methods to know about these keys being pressed, you probably want to leave them masked out from ibm-acpi, and use their non-HKEY events listed below, instead.

{| {{prettytable}}
|+ events triggered by ACPI when hotkey is masked out or disabled.
! key !! event
|-
| {{key|Fn}}{{key|F4}} || button/sleep SLPB 00000080 00000001
|-
| {{key|Fn}}{{key|F12}} || ibm/hotkey HKEY 00000080 0000100c
|}

===tpb configuration===
{| {{prettytable}}
|+ configuration keywords for [[tpb]] (to put in {{path|/etc/tpbrc}})
! key !! config keyword
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || THINKPAD
|-
| {{ibmkey|Home|#494949}} || HOME
|-
| {{ibmkey|Search|#494949}} || SEARCH
|-
| {{ibmkey|Mail|#494949}} || MAIL
|-
| {{ibmkey|Favorites|#494949}} || FAVORITES
|-
| {{ibmkey|Reload|#494949}} || RELOAD
|-
| {{ibmkey|Abort|#494949}} || ABORT
|-
| {{ibmkey|Backward|#494949}} || BACKWARD
|-
| {{ibmkey|Forward|#494949}} || FORWARD
|-
| {{key|Fn}} || FN
|-
| {{key|Fn}}{{key|Space}} || CALLBACK (zoom on/off)
|-
| {{key|Fn}}{{key|PageUp}} || CALLBACK (thinklight on/off)
|-
| {{key|Fn}}{{key|F7}} || CALLBACK (display lcd/crt/both)
|-
| {{key|Fn}}{{key|F8}} || CALLBACK (expand on/off)
|-
| {{key|Fn}}{{key|Home}} / {{key|Fn}}{{key|Pos1}} || CALLBACK (brightness <percent>)
|-
| {{key|Fn}}{{key|End}} || CALLBACK (brightness <percent>)
|-
| {{ibmkey|Volume up|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume down|#494949}} || CALLBACK (volume <percent>)
|-
| {{ibmkey|Volume mute|#494949}} || CALLBACK (mute on/off)
|}

To all parameter keywords should be assigned the full path to the executables supposed to be started on key press.
The exectable provided for the CALLBACK keyword should take the parameters given in parentheses and act according to them.
If you want to use xmodmap for the HOME, SEARCH, MAIL, FAVORITES, RELOAD, ABORT, BACKWARD, FORWARD and FN keys you should
provide a <tt>XEVENTS OFF</tt> in your {{path|/etc/tpbrc}}.
You can use an appropriate executable to [[How to inject fake keystrokes|inject fake keystrokes]].

For Debian users, tpb is started from {{path|/etc/X11/Xsession.d/90tpb}}.

'''Sound Button configuration'''

''Note: Tested on T60p with Ubuntu 6.06 LTS''

Most Thinkpads have a hardware sound mixer, thus the volumes buttons should work without configuration. However, this change is not reflected in the software mixer. tpb has a switch to enable software mixer support via OSS. The manual recommends this only for devices without a hardware mixer, but it also works for other hadware mixer enabled devices, even with the ALSA system. Just put MIXER ON in your {{path|/etc/tpbrc}} file and you can see the effect immediately in any ALSA mixer (e.g. kmix). For this to work you need write permissions to {{path|/dev/nvram}}.

''Note: Tested on X21 with Ubuntu 6.06 LTS''

On the ThinkPad X21 (and maybe some other older models) ACPI causes problems with tpb. On an X21 using acpi the volume buttons would work occasionally, and the OSD for tpb functions would rarely work. If a volume buttons was pressed too often, sometimes the computer would enter a low power (unplugged state) and would require a reboot. The solution is to use APM instead of ACPI. Instructions can be found in [[How_to_make_APM_work]].

===KMilo configuration===
The programs to be executed by [[KMilo]] are configured via the KDE Control Center (<tt>kcontrol</tt>), under <tt>System Administration --> IBM Thinkpad Laptop</tt>. Note that you can use appropriate commands to [[How to inject fake keystrokes|inject fake keystrokes]].

===xmodmap configuration===
xmodmap enables you to edit the modifier map and keymap tables that are used to translate keycodes into keysyms.
Understood? Well, basically it allows you to give the X server a dictionary for the translation of keycodes like "97" into more human readable synonyms like "Home". This way xmodmap allows you to make the special keys of your keyboard known to X applications.

To discover the keycode that a certain keypress produces, use the tool {{cmduser|xev}}

Usually you should write your keycode-keysym associations into the file {{path|~/.Xmodmap}}. This file is usually read by the X session startup scripts of your system, so that the mappings automatically get included everytime you run the X server.

The {{path|~/.Xmodmap}} lines for our purpose are in the form of
keycode <keycode> = <keysym>

Load the assocation using the command

{{cmduser|xmodmap ~/.Xmodmap}}

(some configurations do this automatically upon X startup).

The following table shows the keycodes generated by the ThinkPad special keys and sensible keysyms to assign them to.
{| {{prettytable}}
|+ keycodes and recommended keysyms
! key !! keycode !! keysym
|-
| {{ibmkey|Access IBM|#495988}} or {{ibmkey|ThinkPad|#494949}} || 159 || XF86LaunchA
|-
| {{ibmkey|Backward|#494949}} || 234 || XF86Back or F19
|-
| {{ibmkey|Forward|#494949}} || 233 || XF86Forward or F20
|-
| {{ibmkey|Play/Pause|#494949}} || 162 || XF86AudioPlay
|-
| {{ibmkey|Stop|#494949}} || 164 || XF86AudioStop
|-
| {{ibmkey|Next|#494949}} || 153 || XF86AudioNext
|-
| {{ibmkey|Previous|#494949}} || 144 || XF86AudioPrev
|-

| {{ibmkey|Home|#494949}} || 178 || XF86HomePage
|-
| {{ibmkey|Search|#494949}} || 229 || XF86Search
|-
| {{ibmkey|Mail|#494949}} || 236 || XF86Mail
|-
| {{ibmkey|Favorites|#494949}} || 230 || XF86AddFavorite or XF86Favorites
|-
| {{ibmkey|Reload|#494949}} || 231 || XF86Reload
|-
| {{ibmkey|Abort|#494949}} || 232 || XF86Stop
|-
| {{key|Fn}} || 227 || F35
|}

Note: You can also using xkeycaps(a tool graphically display and edit the X keyboard mapping) to generate proper .Xmodmap.

Note: if you are running [[tpb]] you might need to add the line <tt>XEVENTS=off</tt> into your tpbrc to stop it from grabbing the key events and allow them to get through to X instead. See [[http://www.thinkwiki.org/wiki/Tpb]] for more detailed instruction on how to use tpb and xmodmap.

Note: XF86Forward and XF86Back do not work correctly in Firefox. You may want to map them to F19 and F20 instead if you use Firefox.

=====Enabling the Windows and Menu Keys=====
On some systems the Windows and Menu keys may not be recognized. You can enable then by
making the following changes:

keycode 115 = F13
keycode 227 = F35

F13 and F35 are used for the Windows and and Menu keys respectively. Labelling keycpode 227 as "Menu" may conflict with the right-mouse-click event.

=====Using Caps Lock as Super L (Windows key)=====
You can easily use Caps Lock as Win key by adding the following in your ~/.Xmodmap:
! No Caps Lock
clear lock
! Caps Lock as Win key
add mod4 = Caps_Lock
=====NumLock=====
On the ThinkPad {{600}}, {{T20}}, {{T21}}, {{T22}}, {{T30}}, {{X20}}, {{X21}}, {{X31}}, {{T42p}}, {{T43}}, {{R51}}, {{R52}} and possibly other models, X does not recognize the keycode for {{key|NumLk}} = {{key|Shift}}+{{key|ScrLk}}. To fix this, add the following to {{path|~/.Xmodmap}} in your home directory or {{path|/etc/X11/Xmodmap}} and run <tt>xmodmap</tt>, ex: <tt>xmodmap ~/.Xmodmap</tt>:
keycode 77 = Num_Lock

===Mapping keys with setkeycodes===
You can use the setkeycodes command to remap certain keys. I.e. you can use {{cmdroot|setkeycodes 6e 109 6d 104 69 28 6b 1}} to map the Tablets Up and Down keys to the standard PageUp and PageDown keys and Tablet Escape and Enter to their respective keys.

The following table shows the keycodes generated by the ThinkPad keys.
{| {{prettytable}}
|+ keycodes
! key !! keycode
|-
| {{ibmkey|Tablet orientation|#494949}} || 0x6d
|-
| {{ibmkey|Tablet Shortcut|#494949}} || 0x6e
|-
| {{ibmkey|Tablet Esc|#494949}} || 0x6b
|-
| {{ibmkey|Tablet Enter|#494949}} || 0x69
|-
| {{ibmkey|Tablet Up|#494949}} || 0x68
|-
| {{ibmkey|Tablet Down|#494949}} || 0x6c
|-
| {{ibmkey|Tablet (unlabeled)|#494949}} || 0x67
|}

==Example Applications==
===Web Browsers===
====Firefox====

There are various ways to assign actions to the browser keys. The easiest way is to install [http://mozilla.dorando.at/keyconfig.xpi keyconfig.xpi] from http://mozilla.dorando.at, which adds a menu entry Tools->Keyconfig. Then you can assign any action you want to the F19/F20 keys (you still need to create {{path|~/.Xmodmap}} as explained above).

The remaining discussion gives you various more complicated ways to achieve the same thing.
To have firefox make use of the browser keys you need to modify one of its files{{footnote|4}}.
To do this you will first need to extract it from the {{path|browser.jar}} archive. Do...

:{{cmdroot|cd <firefox-directory>/chrome}}<br />
:{{cmdroot|unzip browser.jar}}

The file of interest is {{path|content/browser/browser.xul}}. Edit it {and don't forget to make a backup copy first}...
:{{cmdroot|vi content/browser/browser.xul}}

Look for the '''<keyset id="mainKeyset">''' section and add the following lines within...
<key id="goBackKb" keycode="VK_F19" command="Browser:Back" />
<key id="goForwardKb" keycode="VK_F20" command="Browser:Forward" />

The Command you need for Next Tab
<key id="goBackTabKb" keycode="VK_F19" oncommand="gBrowser.mTabContainer.advanceSelectedTab(-1)" />
For the Previous Tab
<key id="goForwardTabKb" keycode="VK_F20" oncommand="gBrowser.mTabContainer.advanceSelectedTab(1)" />

Now save the file and repackage the {{path|browser.jar}} archive...
:{{cmdroot|zip -rD0 browser.jar content/browser/}}

That's it.

{{HINT|For Firefox 2.0, just edit <firefox-directory>/chrome/browser/content/browser/browser.xul}}

{{HINT|Outdated: Another interesting Page on Firefox is http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ It uses different key mappings (F19 resp. F20) but a ready [http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/dqdnavkeys-1.2.xpi .xpi] is provided which is pretty comfortable. However, this xpi file does not install on Firefox 1.5. or later.}}

{{HINT|Outdated: You can also use the [http://extensionroom.mozdev.org/more-info/keyconfig keyconfig] extension to configure custom keys. This extension works with Firefox 1.5 but not with Firefox 2.0. The Command you need for Next Tab is gBrowser.mTabContainer.advanceSelectedTab(1,true); For Previous Tab its gBrowser.mTabContainer.advanceSelectedTab(-1,true); }}.

====Konqueror====
KDE allows you set key mappings for KDE applications (Go to KMenu > System > Control Center > Regional & Accessibility > Keyboard Shortcuts). By default (at least in KDE 3.5), XF86Back and XF86Forward are set as alternatives to Alt-Left and Alt-Right, and are mapped to KDE Back and Forward navigation actions.

If you use Konqueror as your only browser, you only need to set up {{path|~/.Xmodmap}} as described [[#xmodmap configuration|above]] to assign ThinkPad back/forward keys to the symbols XF86Back/XF86Forward. This also make these keys work for other KDE applications such as Quanta Plus, KPackage and so on (not all KDE applications honor this setting, e.g. KDE help system doesn't).

If you want to use Firefox, however, the above settings do not work. You will have to map ThinkPad back/forward keys to F19/F20 as described [[#Firefox|above]], and change KDE navigation key settings to use F19/F20 instead of the default.

====Opera====
However this isn't a simple configration file, you can set your browser manually.<br />
Go to <i>Tool > Settings > Mouse and keyboard > Keyboard settings > Edit > Browser Window</i>. There add F19 - Back and F20 - Forward. Now you can surf using your TP keys ;-)

===Window Managers===
====fvwm====
To get the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fvwmrc}}:
Key XF86Back A A Scroll -100000 0
Key XF86Forward A A Scroll +100000 0
If you use multiple virtual desktops, you could instead use the keys to flip between them by using GotoDesk.

====fluxbox====
To get the keys to cycle through pages in the virtual desktop, add this to your {{path|~/.fluxbox/keys}}:
None F19 :PrevWorkspace
None F20 :NextWorkspace

====pekwm configuration====
You can make the two browser keys switch workspaces in pekwm, by adding the following two lines to the {{path|~/.pekwm/keys}} file:
KeyPress = "Mod1 XF86Back" { Actions = "GoToWorkspace prev" }
KeyPress = "Mod1 XF86Forward" { Actions = "GoToWorkspace next" }

====pwm====
Another example how to use these two keys to switch between pwm tabs. These two lines should be added to {{path|~/.pwm/keys-default.conf}} or {{path|/etc/pwm/keys-default.conf}}:
kbind "Back", "switch_rot", -1
kbind "Forward", "switch_rot", 1

====IceWM====
To make IceWM cycle workspaces using the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys, change these two options in {{path|~/.icewm/preferences}} (Provided you assigned keysyms F19 and F20 with xmodmap):
# "Previous workspace" shortcut
KeySysWorkspacePrev="F19"
# "Next workspace" shortcut
KeySysWorkspaceNext="F20"

==== Gnome/metacity ====

Follow the [https://wiki.ubuntu.com/Keybindings Ubuntu guide].

===Other Uses===
====Console tools configuraton====
To make the {{ibmkey|Forward|#494949}} and {{ibmkey|Backward|#494949}} keys useful in console, add this to your keymap ({{path|/etc/console/boottime.kmap.gz}} in {{Debian}}):
keycode 158 = Decr_Console
keycode 159 = Incr_Console

Alternatively you can load this script (perhaps on system startup) to enable Backward/Forward button console (VT) switch:

#!/bin/sh
echo keycode 158 = Decr_Console | loadkeys
echo keycode 159 = Incr_Console | loadkeys

It should work with any distro.

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51537 IBMs page on configuring the ThinkPad buttons (ThinkPad, Access IBM, Mail, Search, and Home buttons) under Linux]
*[http://dqd.com/~mayoff/notes/thinkpad/dqdnavkeys/ Rob Mayoffs page on using IBM Keyboard Navigation Keys in Linux Mozilla and Firefox]
*[http://snarfed.org/space/thinkpad+keys+in+firefox Ryan Barretts blog article about using the browser keys in Firefox]
*[http://chaotika.org/~bluesceada/?page=soft&sub=thinkpad#acpibutn DennisG's help to get the ibm-acpi buttons do useful things] on a {{Z61e}} and possibly {{Z61m}}, {{Z61t}} and {{Z61p}}

{{footnotes|
#Note that the associated functionality for Fn-F* key combinations is not consistent amongst all ThinkPads. We are maintaining [[Default meanings of special keys|a table of associated meanings]].
#if there are more than one tool listed, one is sufficient
#'full' means you can completely reassign any action to be triggered by the key, 'additional actions' means you can trigger actions in addition to the standard function of the key, which can not be changed.
#Thanks go to Ryan Barrett for writing the [http://snarfed.org/space/thinkpad+keys+in+firefox little howto] on [http://snarfed.org/space/start his blog].
}}

How to silence DVD ROM

2007-02-14T10:56:55Z

Xoby:

The default setting for the DVD ROM on the T40 is very noisy.

== BIOS ==

It isn't obvious, but there's a BIOS setting under the "Power" section in which the drive can be set to silent. It is very effective.

== hdparm ==

Another solution is to use the command ''hdparm'' :
$ hdparm -E8 /dev/hdc
''-E8'' sets the speed of the cdrom drive to 8, which is silent, to reset maximum speed use ''-E0''.

==Affected Models==
*ThinkPad {{T40}}, {{T42p}}

How to silence DVD ROM

2007-02-14T10:56:08Z

Xoby:

The default setting for the DVD ROM on the T40 is very noisy.

== Bios ==

It isn't obvious, but there's a BIOS setting under the "Power" section in which the drive can be set to silent. It is very effective.

== HDPARM ==

Another solution is to use the command ''hdparm'' :
$ hdparm -E8 /dev/hdc
''-E8'' sets the speed of the cdrom drive to 8, which is silent, to reset maximum speed use ''-E0''

==Affected Models==
*ThinkPad {{T40}}

DRI options for ATI Radeon

2006-12-06T20:41:53Z

Xoby: Adds stub mark

{{stub}}
Some options can be configured at the DRI level (not by /etc/X11/Xorg.conf)
* Page at free desktop: http://dri.freedesktop.org/wiki/ATIRadeon
* DRIconf : GUI to setup the options

For a R300 (mobiliy FireGL T2) The options are :
* Performance options:
** TCL mode
** Method to limit rendering latency
** Synchronisation with vertical refresh
** Number of texture image units
** Number of texture coordinate units
** Size of command buffer
* Image Quality
* Debugging

DRI options for ATI Radeon

2006-12-06T20:40:19Z

Xoby: DRI section for ATI Radeon (please add content)

Some options can be configured at the DRI level (not by /etc/X11/Xorg.conf)
* Page at free desktop: http://dri.freedesktop.org/wiki/ATIRadeon
* DRIconf : GUI to setup the options

For a R300 (mobiliy FireGL T2) The options are :
* Performance options:
** TCL mode
** Method to limit rendering latency
** Synchronisation with vertical refresh
** Number of texture image units
** Number of texture coordinate units
** Size of command buffer
* Image Quality
* Debugging

Radeon

2006-12-06T20:35:31Z

Xoby: /* See also */

X.org includes a driver called <tt>radeon</tt> for recent ATI graphic chips (i.e., those branded "Radeon"). This driver supports 2D acceleration and some other chip features. In conjunction with a suitable DRI driver such as [[r300]], it also provides 3D acceleration.

===Supported graphic chips===
* [[ATI Mobility Radeon 7000]]
* [[ATI Mobility Radeon 7500]]
* [[ATI Mobility Radeon 9000]]
* [[ATI Mobility Radeon 9600]]
* [[ATI Mobility Radeon X300]]
* [[ATI Mobility Radeon X600]]

===See also===
* [[DRI options for ATI Radeon]]
* [[Additional options for the radeon driver]]
* [[fglrx]]

How to hotswap Ultrabay devices

2006-11-11T23:03:16Z

Xoby: /* HAL support */

The following discusses hotswap (AKA "hotplug") of devices in the [[UltraBay]].

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[ibm-acpi]] eject function.

The [[ibm-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]].

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering the device when the eject event is generated by [[ibm-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support).

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>
For more details see HAL section for ata driver.

==When using the <tt>ata_piix</tt> driver==
The following applies when using the <tt>ata_piix</tt> driver, which is necessary for many recent ThinkPad models that use an [[Intel ICH6-M]] controller. See also [[Problems with SATA and Linux]].

Mainline kernels before 2.6.18 cannot reliably recognize newly (re-)inserted UltraBay drives without a reboot. There are experimental hotplug patches against pre-2.6.18 mainline kernels [http://home-tj.org/wiki/index.php/Libata-tj-stable here].

* Available hotplug patches
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2 Patch tarball against 2.6.16.16] ([http://lwn.net/Articles/183407/ Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2 Patch tarball against 2.6.17/2.6.17.1] ([http://article.gmane.org/gmane.linux.ide/11598 Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Patch tarball against 2.6.17.4]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/00-libata-tj-2.6.17.4-20060710.patch Patch against 2.6.17.14]

* Confirmed to work on
**ThinkPad {{T43}}, {{T43p}}
**ThinkPad {{R52}}

For 2.6.18 kernels, or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!), one can issue the following after inserting an UltraBay drive to rescan the port:
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host1/scan}}
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).

You can safely shut down the drive by issuing the following (this works with all recent mainline kernels):
{{cmdroot|echo 1 > /sys/class/scsi_device/1\:0\:0\:0/device/delete}}
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}
The drive can now be ejected.

===Scripts for hotswapping===

The following scripts and [[acpid]] daemon configuration files do the following:
* Automatically unmounts the relevant filesystems and power off the UltraBay when the UltraBay eject lever is released. Screams if some filesystem can't be unmounted.
* Rescans the UltraBay port when then UltraBay eject lever is pushed back in.

They assumes you're using the <tt>ata_piix</tt> driver with an appropriate kernel (see above).

Create {{path|/usr/local/sbin/ultrabay_close}} with permissions 755:
<pre>
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan
</pre>

Create {{path|/usr/local/sbin/ultrabay_open}} with permissions 755:
<pre>
#!/bin/bash
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'
shopt -s nullglob

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block:"*`" || return 1
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ -d $ULTRABAY_SYSDIR ]; then
sync
# Unmount filesystems backed by this device
unmount_rdev `cat $ULTRABAY_SYSDIR/block\:*/dev \
$ULTRABAY_SYSDIR/block\:*/*/dev` \
|| {
echo 10 > /proc/acpi/ibm/beep; # error tone
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
fi
sync
# Turn off power to the UltraBay:
if [ -d /proc/acpi/bay ]; then
echo 1 > /proc/acpi/bay/*/eject
else
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep
</pre>

Create {{path|/etc/acpi/events/ultrabay-close}}:
<pre>
event=(ibm/bay|bay) MSTR 00000001 00000000
action=/usr/local/sbin/ultrabay_close
</pre>

Create {{path|/etc/acpi/events/ultrabay-open}}:
<pre>
event=(ibm/bay|bay) MSTR 00000003 00000000
action=/usr/local/sbin/ultrabay_open
</pre>

Restart <tt>acpid</tt>.

===HAL support===

Many programs, KDe included, rely on [[HAL]] to get notifications and information about device hotplugging. You need to tell HAL that devices connected the UltraBay port are hotpluggable. To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="scsi">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>

====Details====

By default, HAL doesn't know that UltraBay devices are hotpluggable:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
false

After creating {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as above and re-plugging the device, it will get marked correctly:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
true

The string "8086_2653" gives the PCI ID of the [[Intel 82801FBM]] southbridge. If your model has a different southbridge, or the UltraBay is attached to a different port, then you can find the appropriate <tt>storage.physical_device</tt> value by finding out the block device of the currently running UltraBay device (<tt>/dev/sdb</tt> in the following example) and then running:

# DEVICE=/dev/sdb
# UDI=`hal-find-by-property --key block.device --string $DEVICE` || echo Failed
# hal-get-property --udi $UDI --key storage.physical_device
/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0

If you have a different <tt>storage.physical_device</tt> value, please report your findings.

==Other comments==

If you are hot-swapping a hard disk on a disk tray, make sure the disk does not have a password set, otherwise it will not be recognized on reinsertion.

[[Category:Scripts]]

How to hotswap Ultrabay devices

2006-11-11T23:03:04Z

Xoby: /* HAL support */

The following discusses hotswap (AKA "hotplug") of devices in the [[UltraBay]].

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[ibm-acpi]] eject function.

The [[ibm-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]].

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering the device when the eject event is generated by [[ibm-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support).

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>
For more details see HAL section for ata driver

==When using the <tt>ata_piix</tt> driver==
The following applies when using the <tt>ata_piix</tt> driver, which is necessary for many recent ThinkPad models that use an [[Intel ICH6-M]] controller. See also [[Problems with SATA and Linux]].

Mainline kernels before 2.6.18 cannot reliably recognize newly (re-)inserted UltraBay drives without a reboot. There are experimental hotplug patches against pre-2.6.18 mainline kernels [http://home-tj.org/wiki/index.php/Libata-tj-stable here].

* Available hotplug patches
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2 Patch tarball against 2.6.16.16] ([http://lwn.net/Articles/183407/ Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2 Patch tarball against 2.6.17/2.6.17.1] ([http://article.gmane.org/gmane.linux.ide/11598 Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Patch tarball against 2.6.17.4]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/00-libata-tj-2.6.17.4-20060710.patch Patch against 2.6.17.14]

* Confirmed to work on
**ThinkPad {{T43}}, {{T43p}}
**ThinkPad {{R52}}

For 2.6.18 kernels, or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!), one can issue the following after inserting an UltraBay drive to rescan the port:
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host1/scan}}
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).

You can safely shut down the drive by issuing the following (this works with all recent mainline kernels):
{{cmdroot|echo 1 > /sys/class/scsi_device/1\:0\:0\:0/device/delete}}
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}
The drive can now be ejected.

===Scripts for hotswapping===

The following scripts and [[acpid]] daemon configuration files do the following:
* Automatically unmounts the relevant filesystems and power off the UltraBay when the UltraBay eject lever is released. Screams if some filesystem can't be unmounted.
* Rescans the UltraBay port when then UltraBay eject lever is pushed back in.

They assumes you're using the <tt>ata_piix</tt> driver with an appropriate kernel (see above).

Create {{path|/usr/local/sbin/ultrabay_close}} with permissions 755:
<pre>
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan
</pre>

Create {{path|/usr/local/sbin/ultrabay_open}} with permissions 755:
<pre>
#!/bin/bash
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'
shopt -s nullglob

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block:"*`" || return 1
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ -d $ULTRABAY_SYSDIR ]; then
sync
# Unmount filesystems backed by this device
unmount_rdev `cat $ULTRABAY_SYSDIR/block\:*/dev \
$ULTRABAY_SYSDIR/block\:*/*/dev` \
|| {
echo 10 > /proc/acpi/ibm/beep; # error tone
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
fi
sync
# Turn off power to the UltraBay:
if [ -d /proc/acpi/bay ]; then
echo 1 > /proc/acpi/bay/*/eject
else
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep
</pre>

Create {{path|/etc/acpi/events/ultrabay-close}}:
<pre>
event=(ibm/bay|bay) MSTR 00000001 00000000
action=/usr/local/sbin/ultrabay_close
</pre>

Create {{path|/etc/acpi/events/ultrabay-open}}:
<pre>
event=(ibm/bay|bay) MSTR 00000003 00000000
action=/usr/local/sbin/ultrabay_open
</pre>

Restart <tt>acpid</tt>.

===HAL support===

Many programs, KDe included, rely on [[HAL]] to get notifications and information about device hotplugging. You need to tell HAL that devices connected the UltraBay port are hotpluggable. To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="scsi">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>

====Details====

By default, HAL doesn't know that UltraBay devices are hotpluggable:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
false

After creating {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as above and re-plugging the device, it will get marked correctly:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
true

The string "8086_2653" gives the PCI ID of the [[Intel 82801FBM]] southbridge. If your model has a different southbridge, or the UltraBay is attached to a different port, then you can find the appropriate <tt>storage.physical_device</tt> value by finding out the block device of the currently running UltraBay device (<tt>/dev/sdb</tt> in the following example) and then running:

# DEVICE=/dev/sdb
# UDI=`hal-find-by-property --key block.device --string $DEVICE` || echo Failed
# hal-get-property --udi $UDI --key storage.physical_device
/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0

If you have a different <tt>storage.physical_device</tt> value, please report your findings.

==Other comments==

If you are hot-swapping a hard disk on a disk tray, make sure the disk does not have a password set, otherwise it will not be recognized on reinsertion.

[[Category:Scripts]]

How to hotswap Ultrabay devices

2006-11-11T23:02:20Z

Xoby: adds HAL config for ultrabay with ide-disk driver

The following discusses hotswap (AKA "hotplug") of devices in the [[UltraBay]].

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device.

Hotswapping is supposed to be supported as well, using either hdparm/[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] or [[lt_hotswap]] to (un)register IDE devices. The latter is the recommended method with kernels from 2.6, since it will leave DMA working. However, for recent models (R52, T43, X41, Z60 and later) no method is known to work while maintaining DMA support; see [[Problems with SATA and Linux]].

Only IDE devices (HDD's, optical drives, zip drives) require special treatment - batteries, floppies and other devices can just be pulled from the bay, provided they are not mounted or in use at the time. However, you should still power them down first using the [[ibm-acpi]] eject function.

The [[ibm-acpi]] kernel module has an eject function ({{cmdroot|echo eject > /proc/acpi/ibm/bay}}). This only manages the ACPI calls to power down the device and the bay. It does not actually unregister the device from the IDE driver. {{cmdroot|cat /proc/acpi/ibm/bay}} shows "unoccupied" unless an IDE device is present, but the eject function still works and should still be used.

To unregister the device, you can either use the [http://packages.debian.org/unstable/admin/hotswap Debian hotswap] package, or [[lt_hotswap]].

[http://packages.debian.org/unstable/admin/hotswap Debian hotswap] also allows the drive to be swapped as a normal user by default, which is useful. You should use <tt>hotswap</tt> to unregister the device and then {{cmdroot|echo eject > /proc/acpi/ibm/bay}}. However, if you use this method on a 2.6 kernel, you will lose DMA support for the reinserted drive. This is due to kernel issues. This method was reported to work on a ThinkPad {{T23}} (kernels 2.6.8.1, 2.6.14.2 and 2.6.15-arch) and {{T42}} (kernel 2.6.13), but fails on a ThinkPad {{T43}} (kernel 2.6.14.3).

[[lt_hotswap]] is now the recommended method to un- and reregister the IDE device. It installs as a kernel module and has support for automatically unregistering the device when the eject event is generated by [[ibm-acpi]]. It will leave DMA support intact. It has supported to work on a ThinkPad {{T22}} and {{T40}} and should work with many other models (but not recent models which require the <tt>ata_piix</tt> driver for disk DMA support).

===HAL support===

HAL support also can also be configured To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="ide">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_24ca_ide_1_0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>

==When using the <tt>ata_piix</tt> driver==
The following applies when using the <tt>ata_piix</tt> driver, which is necessary for many recent ThinkPad models that use an [[Intel ICH6-M]] controller. See also [[Problems with SATA and Linux]].

Mainline kernels before 2.6.18 cannot reliably recognize newly (re-)inserted UltraBay drives without a reboot. There are experimental hotplug patches against pre-2.6.18 mainline kernels [http://home-tj.org/wiki/index.php/Libata-tj-stable here].

* Available hotplug patches
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.16.16-20060512.tar.bz2 Patch tarball against 2.6.16.16] ([http://lwn.net/Articles/183407/ Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17-20060625-1.tar.bz2 Patch tarball against 2.6.17/2.6.17.1] ([http://article.gmane.org/gmane.linux.ide/11598 Announce])
**[http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.17.4-20060710.tar.bz2 Patch tarball against 2.6.17.4]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/00-libata-tj-2.6.17.4-20060710.patch Patch against 2.6.17.14]

* Confirmed to work on
**ThinkPad {{T43}}, {{T43p}}
**ThinkPad {{R52}}

For 2.6.18 kernels, or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!), one can issue the following after inserting an UltraBay drive to rescan the port:
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host1/scan}}
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).

You can safely shut down the drive by issuing the following (this works with all recent mainline kernels):
{{cmdroot|echo 1 > /sys/class/scsi_device/1\:0\:0\:0/device/delete}}
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}
The drive can now be ejected.

===Scripts for hotswapping===

The following scripts and [[acpid]] daemon configuration files do the following:
* Automatically unmounts the relevant filesystems and power off the UltraBay when the UltraBay eject lever is released. Screams if some filesystem can't be unmounted.
* Rescans the UltraBay port when then UltraBay eject lever is pushed back in.

They assumes you're using the <tt>ata_piix</tt> driver with an appropriate kernel (see above).

Create {{path|/usr/local/sbin/ultrabay_close}} with permissions 755:
<pre>
#!/bin/bash
echo 12 > /proc/acpi/ibm/beep
sync
echo 0 0 0 > /sys/class/scsi_host/host1/scan
</pre>

Create {{path|/usr/local/sbin/ultrabay_open}} with permissions 755:
<pre>
#!/bin/bash
ULTRABAY_SYSDIR='/sys/class/scsi_device/1:0:0:0/device'
shopt -s nullglob

# Umount the filesystem(s) backed by the given major:minor device(s)
unmount_rdev() { perl - "$@" <<'EOPERL' # let's do it in Perl
for $major_minor (@ARGV) {
$major_minor =~ m/^(\d+):(\d+)$/ or die;
push(@tgt_rdevs, ($1<<8)|$2);
}
# Sort by reverse length of mount point, to unmount sub-directories first
open MOUNTS,"</proc/mounts" or die "$!";
@mounts=sort { length($b->[1]) <=> length($a->[1]) } map { [ split ] } <MOUNTS>;
close MOUNTS;
foreach $m (@mounts) {
($dev,$dir)=@$m;
next unless -b $dev; $rdev=(stat($dev))[6];
next unless grep($_==$rdev, @tgt_rdevs);
system("umount","-v","$dir")==0 or $bad=1;
}
exit 1 if $bad;
EOPERL
}

# Get the UltraBay's /dev/foo block device node
ultrabay_dev_node() {
UDEV_PATH="`readlink -e "$ULTRABAY_SYSDIR/block:"*`" || return 1
UDEV_NAME="`udevinfo -q name -p $UDEV_PATH`" || return 1
echo /dev/$UDEV_NAME
}

if [ -d $ULTRABAY_SYSDIR ]; then
sync
# Unmount filesystems backed by this device
unmount_rdev `cat $ULTRABAY_SYSDIR/block\:*/dev \
$ULTRABAY_SYSDIR/block\:*/*/dev` \
|| {
echo 10 > /proc/acpi/ibm/beep; # error tone
exit 1;
}
sync
# Nicely power off the device
DEVNODE=`ultrabay_dev_node` && hdparm -Y $DEVNODE
# Let HAL+KDE notice the unmount and let the disk spin down
sleep 0.5
# Unregister this SCSI device:
sync
echo 1 > $ULTRABAY_SYSDIR/delete
fi
sync
# Turn off power to the UltraBay:
if [ -d /proc/acpi/bay ]; then
echo 1 > /proc/acpi/bay/*/eject
else
echo eject > /proc/acpi/ibm/bay
fi
# Tell the user we're OK
echo 12 > /proc/acpi/ibm/beep
</pre>

Create {{path|/etc/acpi/events/ultrabay-close}}:
<pre>
event=(ibm/bay|bay) MSTR 00000001 00000000
action=/usr/local/sbin/ultrabay_close
</pre>

Create {{path|/etc/acpi/events/ultrabay-open}}:
<pre>
event=(ibm/bay|bay) MSTR 00000003 00000000
action=/usr/local/sbin/ultrabay_open
</pre>

Restart <tt>acpid</tt>.

===HAL support===

Many programs, KDe included, rely on [[HAL]] to get notifications and information about device hotplugging. You need to tell HAL that devices connected the UltraBay port are hotpluggable. To do so, create the file {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as follows:
<pre>
<?xml version="1.0" encoding="UTF-8"?> 

<deviceinfo version="0.2">
<device>


<match key="storage.bus" string="scsi">
<match key="storage.physical_device" string="/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

</device>
</deviceinfo>
</pre>

====Details====

By default, HAL doesn't know that UltraBay devices are hotpluggable:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
false

After creating {{path|/etc/hal/fdi/information/10-ultrabay.fdi}} as above and re-plugging the device, it will get marked correctly:

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0
# UDI=`hal-find-by-property --key storage.physical_device --string $PHYSDEV` || echo Failed
# hal-get-property --udi $UDI --key block.device
/dev/sdb
# hal-get-property --udi $UDI --key storage.hotpluggable
true

The string "8086_2653" gives the PCI ID of the [[Intel 82801FBM]] southbridge. If your model has a different southbridge, or the UltraBay is attached to a different port, then you can find the appropriate <tt>storage.physical_device</tt> value by finding out the block device of the currently running UltraBay device (<tt>/dev/sdb</tt> in the following example) and then running:

# DEVICE=/dev/sdb
# UDI=`hal-find-by-property --key block.device --string $DEVICE` || echo Failed
# hal-get-property --udi $UDI --key storage.physical_device
/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_scsi_device_lun0

If you have a different <tt>storage.physical_device</tt> value, please report your findings.

==Other comments==

If you are hot-swapping a hard disk on a disk tray, make sure the disk does not have a password set, otherwise it will not be recognized on reinsertion.

[[Category:Scripts]]

Fglrx

2006-04-13T13:16:18Z

Xoby: /* Status */

== ATI fglrx driver ==
This is a binary-only driver which supports 3D acceleration.

Home page: https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=356

== Status ==
Current version: 8.24.8 (13th April 2006)

Major changes:
* 8.24.8: support for X1300, X1400, X1600, X1800 (generic and mobility) and 3D accelerated video playback on Avivo
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips
* 8.22.5: added kernel 2.6.15 support -- patch no longer required
* 8.21.7: initial OpenGL 2.0 support
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool is no longer required (tested and successful with T43p).

== Known problems and solutions ==
See [[Problems with fglrx]].

== Build from ATI source ==
To compile for Xorg 7.0.0, fake Xorg 6.9.0 by
# export X_VERSION=x690; sh ati-driver-installer-8.24.8-x86.run

In /usr/src/ATI additional sources are installed for fireglcontrol and fgl_glxgears

== 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}} packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html
** These packages have been added to Debian unstable as "fglrx-driver", so you can now apt-get them and use module-assistant to install (currently v8.20.8-1).
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, currently v8.22.5, 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.
*{{SUSE}} packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/
*{{Gentoo}} {{cmdroot|emerge x11-drivers/ati-drivers}}
*{{Fedora}} packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}
** Creating and installing a custom RPM for a custom-compiled kernel on {{Fedora}}:
# yum install ati-fglrx
# VER=8.20.8.1-0.lvn.1.4 # copy version string from output of above command
# wget http://rpm.livna.org/fedora/4/i386/SRPMS.lvn/ati-fglrx-$VER.src.rpm
# rpmbuild --rebuild --target $(uname -m) --define "ksrc /lib/modules/$(uname -r)/build" --without userland ati-fglrx-$VER.src.rpm
# rpm -Uvh --replacepkgs /usr/src/redhat/RPMS/$(uname -m)/kernel-module-fglrx-$(uname -r)-$VER.$(uname -m).rpm
*{{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)

== User experience ==
=== Speed ===
How much is the speed gain versus the opensource drivers?

- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value 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 happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')

NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "1"

Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 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.

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

== 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:
* [[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}}

[[Category:Drivers]]

Fglrx

2006-03-09T09:41:15Z

Xoby: /* Status */

== ATI fglrx driver ==
This is a binary-only driver which supports 3D acceleration.

Home page: https://support.ati.com/ics/support/default.asp?deptID=894&task=knowledge&folderID=356

== Status ==
Current version: 8.22.5 (9th February 2006)

Major changes:
* 8.23.7: support for X850 and X800, OpenGL 2.0 Enhancement, FSAA for some chips
* 8.22.5: added kernel 2.6.15 support -- patch no longer required
* 8.21.7: initial OpenGL 2.0 support
* 8.20.8: fixed resume issues, fixed compile problems with kernels 2.6.13 and 2.6.14
* 8.19.10: has added suspend / resume and dynamic GPU power management support. Using vbetool is no longer required (tested and successful with T43p).

== Known problems and solutions ==
See [[Problems with fglrx]].

== 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}} packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html
** These packages have been added to Debian unstable as "fglrx-driver", so you can now apt-get them and use module-assistant to install (currently v8.20.8-1).
** If you are on stable sarge with backport's kernel 2.6.15, download ATI's installer, currently v8.22.5, 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.
*{{SUSE}} packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/
*{{Gentoo}} {{cmdroot|emerge x11-drivers/ati-drivers}}
*{{Fedora}} packages: http://rpm.livna.org
** For stock Fedora kernels: {{cmdroot|yum install kernel-module-fglrx-$(uname -r) ati-fglrx }}
** Creating and installing a custom RPM for a custom-compiled kernel on {{Fedora}}:
# yum install ati-fglrx
# VER=8.20.8.1-0.lvn.1.4 # copy version string from output of above command
# wget http://rpm.livna.org/fedora/4/i386/SRPMS.lvn/ati-fglrx-$VER.src.rpm
# rpmbuild --rebuild --target $(uname -m) --define "ksrc /lib/modules/$(uname -r)/build" --without userland ati-fglrx-$VER.src.rpm
# rpm -Uvh --replacepkgs /usr/src/redhat/RPMS/$(uname -m)/kernel-module-fglrx-$(uname -r)-$VER.$(uname -m).rpm
*{{Arch Linux}}
** {{cmdroot|pacman -S ati-drivers}} (Userspace tools and libraries)
** {{cmdroot|pacman -S ati-drivers-arch}} (Drivers for the stock Arch Linux kernel)
** {{cmdroot|pacman -S ati-drivers-archck}} (Drivers for the ArchCK Linux kernel)
== User experience ==
=== Speed ===
How much is the speed gain versus the opensource drivers?

- On the old drivers, I've noticed appx 40% speed gain with ATI fglrx vs open source drivers. However, there are issues with freezing/garbage after suspend, garbage when resizing desktop (ctrl-alt-plus, ctrl-alt-minus), and garbage while using VMware. The current 8.14.13 has shown 400% improvement over using "radeon" or "ati" in xorg.conf. 1200FPS glxgears! (''note that glxgears isnt a benchmark tool, its so simple that its value 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 happend the opposite. Think in the car engine rpm, higher rpm in the same car usually its a faster car, change anything and its meaningless. ie: gears, truck, wheel size, etc make it useless'')

NOTE: 2D acceleration may be disabled when 3D acceleration is enabled. This comes from the Xorg.conf file the fglrx driver provides
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "1"

Just a note to the above. The 2D acceleration for that option refers to video overlay. You can use either regular Xv video overlay or make the video an opengl texture and let the OpenGL engine scale your video. It has nothing to do with 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.

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

== 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:
* [[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}}

[[Category:Drivers]]

Talk:Ipw2200

2006-01-19T10:16:56Z

Xoby: /* Reliability problems */

The ipw2000 drivers loads clean on my t42 and the interface eth1 is accessible. However,
the wireless-lan LED does not light and i cant connect. Havent figured out what this is.

== Radio Switch utility needed ==

I have the same problem.
WiFi adapter must be turned on before using. In Windows software utility is executed by Fn+F5 keys. This utility turns WiFi and/or Bluetooth adpters on/off. In Linux Fn+F5 controls only Bluetooth adapter.
Unfortunately I can not find switch utility yet (10 Sep 2005).

----

Try using the usual hotkey hooks to activate the power management features described in the article.
--[[User:Thinker|Thinker]] 04:37, 18 Nov 2005 (CET)
----

== Reliability problems ==

On a T43p ipw2200 v1.0.6 works well 95% of the time with WPA using wpa_supplicant. However it seemingly randomly causes trouble and refuses to connect (it is not the router, as non-linux devices work.) It always recovers with a killall wpa_supplicant, unloading the ipw2200 and ieee80211 modules, and reloading everything (you can even write a "netreset" script to do this for you automatically, as I have done.)

It's frustrating, because this is so un-"linux-like" to have intermittent unreliability. Usually things work 100% or 0% of the time on my linux system. Note, I have not used the 2.6.15-rc kernel version nor 1.0.8 with WPA yet, this problem might be fixed. Can anybody verify? --[[User:Gsmenden|Gsmenden]]
: Same problem here with a Linksys router and WPA, no problem with other routers ... I'll try the new kernel and ipw2200--[[User:Xoby|Xoby]] 18:35, 15 January 2006 (CET)
:: I've tried and still had problems, I also edited my wpa_supplicant file to:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
### Associate with any open access point
### Scans/ESSID changes can be done with wpa_cli
network={
ssid="myssid"
psk="mypass"
priority=1
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP CCMP
}

And successfully transfered more than 5 Gb without any problem--[[User:Xoby|Xoby]] 11:16, 19 January 2006 (CET)

Talk:Ipw2200

2006-01-15T17:35:44Z

Xoby: /* Reliability problems */

Additional options for the radeon driver

2005-10-31T21:57:29Z

Xoby: Add link to xorg doc

Options for the radeon driver are documented on the radeon(4x) man page.

==External Monitors==
You can use '''MergedFB''' to provide dualhead '''Xinerama'''-like setups. MergedFB's pseudo-Xinerama is not Xorg server's Xinerama. You don't have to enable Xorg server's Xinerama to use MergedFB's pseudo-Xinerama. However, applications compiled with Xinerama support (Gentoo users USE="xinerama") can interpret pseudo-Xinerama hints, for example, to maximize to a single monitor instead of spanning two monitors.

The folowing (partial) '''Xorg''' config will make the Radeon card use '''1024x768''' on the internal lcd display and '''1280x1024''' on the external ('''Note''': only one screen/monitor section is needed (it controls the setup of the internal monitor) even though we have two displays):
'''N.B.:''' Modes used in the ''MetaModes'' also have to be present in the ''screen'' modes section.

Section "Device"
Identifier "ATI"
Driver "radeon"
'''# accelration'''
Option "AGPMode" "4"
Option "EnablePageFlip" "on"
Option "RenderAccel" "on"
'''# enable PowerPlay features'''
Option "DynamicClocks" "on"
'''# use bios hot keys on thinkpad (aka fn+f7)'''
Option "BIOSHotkeys" "on"
'''# enable radeon specific xinerama'''
Option "MergedFB" "true"
Option "CRT2Position" "RightOf"
Option "CRT2Hsync" "50-75"
Option "CRT2VRefresh" "30-82"
Option "MetaModes" "1024x768-1280x1024"
Option "MergedNonRectangular" "true"
BusID "PCI:1:0:0"
EndSection
Section "Monitor"
Identifier "InternalLCD"
Option "DPMS"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI"
Monitor "InternalLCD"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Note: The '''CRT2''' directives always applies for the external monitore regardless of type (LCD, CRT...). The option '''MergedNonRectangular''' is needed to force the screens into two different sizes.

===External Monitors and Docking Stations/Port Replicators===
I seams that '''Xorg''' incorectly discovers the external displays when connected to a docking station/port replicator - the only solution to this problem (atleast that I know of) is to start the laptop (and boot all the way into X) prior to inserting it in the dock.

==AGP speed==

By default, the open source radeon driver forces 1x AGP speed. Quote from the developers:

tuning to the highest speed possible has caused hangs on some boxes, with no
discernable pattern, so we default to 'slow but safe' whilst giving the option
to go fast if the user wants to try it.

Higher speeds can be enabled by adding '''Option "AGPMode" "X"''' (where X is a number) in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATIdd Mobility FireGL 7800"
'''Option "AGPMode" "4"'''
EndSection

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

(**) RADEON(0): Option "AGPMode" "4"
(**) RADEON(0): Using AGP 4x mode

==AGP Fast Writes==

By default, the open source radeon driver disables AGP Fast Writes. Fast Writes can be enabled by adding '''Option "AGPFastWrite" "yes"''' in the '''Device''' section in {{path|/etc/X11/xorg.conf}}.

Section "Device"
Identifier "Videocard0"
Driver "radeon"
VendorName "IBM Thinkpad"
BoardName "ATI Mobility FireGL 7800"
'''Option "AGPFastWrite" "yes"'''
EndSection

==Dynamic Clock scaling==

Please see:

*[[How to make use of Graphics Chips Power Management features]] <tt>(save even more battery power)</tt>
*[https://bugs.freedesktop.org/show_bug.cgi?id=2187 Xorg bug] <tt>DynamicClocks may hang your machine</tt>

== Related Links ==
*[http://www.x.org/X11R6.8.2/doc/radeon.4.html xorg 6.8.2 Radeon manual page]

Talk:Problem with fan noise

2005-09-30T13:00:45Z

Xoby: Typo

== Problem with fan noise on R51 1829 L7G (ATI M9) ==

On my R51 the fan is behaving like this:

* > 45C -> fan on;
* < 38C -> fan off.

By using cpufreq + laptop_mode + Xorg DynamicClocks + WiFi power management, I get the fan stopped time to time, but only for 3 minutes time (transition from 38 C -> 45 C). The cooling down cycle is taking 20 minutes in the best case.

I knew about the 'ibm_acpi experimental=1' trick, but in my opinion this is not very useful since nobody can guarantee that a temperature greater then 45 C will not damage the laptop and in the same time the transition time is very short (the laptop gets hot fast without fan).

== Thinkpad T42 Radeon Mobility M7 ==

When Xorg is running, the fan is always on and pretty loud !
Setting DynamicClocks does not help

it's clear that the GPU is the problem on the thinkpad :

after 10minutes with the fan off
temperatures: 44 47 33 52 32 -128 24 -128

1: CPU
2: Mini PCI Module
3: HDD
4: GPU
5: Battery
6: N/A
7: Battery
8: N/A

Controlling the fan speed would be really cool !

What is the maximum temperature not to cross ?

----
Older versions of xorg (i.e. 6.7.0) don't seem to be able to use the DynamicClocks option although it's set in the xorg.conf. Search the log to find out if it's really used.

== Thinkpad R32 with Radeon Mobility M6 ==

Updating xorg-x11 from 6.7.0 to 6.8.2 and using Speedstep (with the ondemand module in this case) helped cooling the system down significantly:

* before updating the CPU was ~62 C in idle state, and got very near the critical temperature (72 C) during heavy load - I even got some freezes because of the heat ;)
* after the update the CPU is ~54 C in idle state, and still gets to about 68 C while under heavy load

The second sensor (which may be the GPU) is somehow fixed to 50 C (maybe a bug?)

The fan on the R32 is behaving like this:

* > 61 -> fan in state 2 (quite noisy)
* < 55 -> fan in state 1 (less noisy :) )

But I remember using my old SuSE distribution with kernel 2.4.16, apm and some old x11 version the fan actually stopped completely from time to time.

Concerning the maximum temperature of the CPU, I found that the critical temperature on the R32 for the CPU sensor is 72 C
(using {{cmdroot|cat /proc/acpi/thermal_zone/THM0/trip_points }} )

== Fan Control script: more save version ==

ibm_acpi works well on my R50 and R51. But to rely on it completely, I modified the script in two ways:

1. It catches verious signals and turns the fan on before it quits

2. It turns off the fan under very strict conditions, leaving it on when unexpected errors occur.

Here is my script:

#!/bin/sh

# july 2005 Erik Groeneveld, erik@cq2.nl
# More conservatiev and saver version
# It make sure the fan is on in case of errors
# and only turns it off when all temps are ok.

IBM_ACPI=/proc/acpi/ibm
THERMOMETER=$IBM_ACPI/thermal
FAN=$IBM_ACPI/fan
MAXTRIPPOINT=65
MINTRIPPOINT=60
TRIPPOINT=$MINTRIPPOINT

echo fancontrol: Thermometer: $THERMOMETER, Fan: $FAN
echo fancontrol: Current `cat $THERMOMETER`
echo fancontrol: Controlling temperatures between $MINTRIPPOINT and $MAXTRIPPOINT degrees.

# Make sure the fan is turned on when the script crashes or is killed
trap "echo enable > $FAN; exit 0" HUP KILL INT ABRT STOP QUIT SEGV TERM

while [ 1 ];
do
command=enable
temperatures=`sed s/temperatures:// < $THERMOMETER`
result=
for temp in $temperatures
do
test $temp -le $TRIPPOINT && result=$result.Ok
done
if [ "$result" = ".Ok.Ok.Ok.Ok.Ok.Ok.Ok.Ok" ]; then
command=disable
TRIPPOINT=$MAXTRIPPOINT
else
command=enable
TRIPPOINT=$MINTRIPPOINT
fi
echo $command > $FAN
# Temperature ramps up quickly, so pick this not too large:
sleep 5
done

----
I added this script to the other ones. Don't wander about my talk edits, i didn't realize i was on the talk page. [[User:Wyrfel|Wyrfel]] 01:48, 13 Aug 2005 (CEST)
----

== X41 ==

Same fan problem here on the X41. Once it starts it won't stop (unless it is _very_ cold outside). Undervolting the CPU doesn't help - still the same problem.

== Fan speed control? ==

Only the X31 and X40 have an ACPI method for controlling the FAN speed (this is why ibm_acpi provides this functionality just for these models).

What will happen if we take the "FANS" method from the [http://acpi.sourceforge.net/dsdt/view.php?id=219 X40 DSDT], paste it into a iasl-disassembled DSDT of (say) a T43, recompile it and [http://gaugusch.at/kernel.shtml tell the kernel] to use the patched DSDT? ibm_acpi will present the functionality, but it may or may not work.

--[[User:Thinker|Thinker]] 16:16, 28 Sep 2005 (CEST)

Any risk of damaging the hardware when doing this? E.g. what does occur if the system overheats - will the CPU be destroyed are does it automatically switch of? As I've just bought a new X41 I don't want to take any stupid risks - but otherwise I'd say let's try it out.

--gst Thu Sep 29 18:14:13 CEST 2005

I think Intel CPUs have some built-in thermal protection, but I'd hate to test it. And of course, any fiddling with the hardware at this level might damage it. That said, when the CPU is mostly idle it keeps a reasonable temperature even when the fan is disabled, so as long as you keep an eye on both the CPU usage meter and /proc/acpi/ibm/thermal, things should be pretty safe temperature-wise. For extra safety you can force the CPU to its lowest speed via {{path|/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq}}.
--[[User:Thinker|Thinker]] 18:33, 29 Sep 2005 (CEST)

== Further information ==

I've just found a very interesting thread regarding the same issue on HP notebooks. IMO it provides many insight information about heat/fan problems in general, the URL is: http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=853249
Especially the posts by the HP engineer "Andy Fisher" are very interesting. IBM should be able to provide the same BIOS fix as HP did (maybe I should have bought an HP notebook instead of a Thinkpad?).

I've also contacted IBM/Lenovo support via the website about the fan issue. Maybe it helps when others do this as well (especially people who bought larger quantities) so that this issue is taken serious by Lenovo. Is there already any official response to this problem?

--gst Thu Sep 29 19:40:34 CEST 2005

Two of the changes mentioned by the HP engineer make perfect sense here: raise the low trip points and make speed transition gradual. Oh, and get rid of the annoying beat pattern (a brief speed pulse every few seconds) it sometimes gets into!

But from our perspective, what would probably be best is to do the whole thing in software, providing the flexibility for personal preferences and smart decisions. The hardware would only enforce emergency override or throttle/shutdown for extreme temperatures. Then we could do cute things like having a software daemon lower the thresholds in a noisy environment (as judged using the built-in microphone) or when the laptop is on the user's lap (as judged by the built-in accelometers).

== Works fine with APM instead of ACPI? ==

On my X41 the fan starts after about 10 minutes of use and doesn't stop (until it is rather cold in my room - and even then it runs most of the time ;) A friend of mine who has a X41 too (though another model) and who does use NetBSD and APM doesn't experience this problem. He claims that the fan only comes up if the system is not idle. So either it is colder in his room, the X41 model which he has doesn't have this flaw or APM does use different tresholds than ACPI.

Buyers Guide

2005-08-31T13:07:17Z

Xoby: /* Special deals */

This page is dedicated to hints about buying used or new ThinkPad models. You can find notes about typical weaknesses of used ThinkPads here and other things you should care about when choosing a ThinkPad and where to buy it.

==Only some random notes so far==
*{{390X}} models with 15" display are said to have weak display cables that tend to break.
*{{A30}}, {{A30p}}, {{A31}}, {{A31p}} seem to have a mechanical design that can cause the motherboard to break. At least there are a significant number of reports of broken motherboards on these models.
==Build it yourself and save money==
Lenovo offers more flexibility than any other major manufacturer of laptop computers, at least that I know of. Their "configure-to-order" (CTO) offerings let you build the computer you want, without paying for anything you don't want. The basic CTO includes the mainboard and CPU, but no RAM, disk, mini-PCI cards, software, or other add-ons. You can even get a laptop in a CTO configuration.

I built my {{X32}} notebook with 1GB RAM, 60GB 5400RPM hard drive, USB DVD-ROM CD-RW drive, and 802.11a/b/g mini-PCI for a grand total of US$1,206, including tax and shipping.

Start with the complete list of [[https://www-03.ibm.com/lenovo/shop/personalpages/public/public/products/dsp_product_list.cfm products]]. Look for items that end with "CTO" or "Custom." Choose the chassis you want. Then add whatever [[http://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/Upgrades.html upgrades]] you need that only Lenovo offers (such as WiFi). Fill in the rest of the components from other, less expensive vendors.

== Special deals ==
* IBM makes huge discounts to students and teachers:
** France: [http://www.ibm.com/easyaccess/education IBM education homepage]
** switzerland: [http://www.rabais-etudiant.ch/ rabais-etudiant]

Buyers Guide

2005-08-31T13:00:51Z

Xoby: /* Build it yourself and save money */

This page is dedicated to hints about buying used or new ThinkPad models. You can find notes about typical weaknesses of used ThinkPads here and other things you should care about when choosing a ThinkPad and where to buy it.

==Only some random notes so far==
*{{390X}} models with 15" display are said to have weak display cables that tend to break.
*{{A30}}, {{A30p}}, {{A31}}, {{A31p}} seem to have a mechanical design that can cause the motherboard to break. At least there are a significant number of reports of broken motherboards on these models.
==Build it yourself and save money==
Lenovo offers more flexibility than any other major manufacturer of laptop computers, at least that I know of. Their "configure-to-order" (CTO) offerings let you build the computer you want, without paying for anything you don't want. The basic CTO includes the mainboard and CPU, but no RAM, disk, mini-PCI cards, software, or other add-ons. You can even get a laptop in a CTO configuration.

I built my {{X32}} notebook with 1GB RAM, 60GB 5400RPM hard drive, USB DVD-ROM CD-RW drive, and 802.11a/b/g mini-PCI for a grand total of US$1,206, including tax and shipping.

Start with the complete list of [[https://www-03.ibm.com/lenovo/shop/personalpages/public/public/products/dsp_product_list.cfm products]]. Look for items that end with "CTO" or "Custom." Choose the chassis you want. Then add whatever [[http://www-132.ibm.com/content/home/store_IBMPublicUSA/en_US/Upgrades.html upgrades]] you need that only Lenovo offers (such as WiFi). Fill in the rest of the components from other, less expensive vendors.

== Special deals ==
* for students IBM makes huge discounts : see www.ibm.com/easyaccess/education for France

How to build your own Ultrabay drive

2005-08-08T18:04:15Z

Xoby: /* The Limitations */

{{WARN|No warranty of any kind is given for the correctness of the following instructions. Following them can damage your machine. Proceed at your own risk.}}
{{NOTE|This article is written with UltraBay 2000 drives in mind. But should be appliable for UltraSlimBay and other kinds of UltraBay devices as well.}}
Optical [[UltraBay]] drives like CD-ROM and DVD drives or burners are usually a bit more expensive than their non-IBM counterparts. Additionally mor modern technologies are not available for discontinued [[UltraBay]] standards. A solution to this annoyance is to take a standard slim form factor notebook drive and turn it into an UltraBay drive yourself.

==The Basics==
The "big secret" about UltraBay drives is that basically they are just standard slim form factor notebook drives equipped with an UltraBay frame. This frame is just a mechanical addition with an integrated connector adapter.

As curious people found, the inner connector of an UltraBay frame is nothing more than a standard interface for such drives. Hence, it is generally possible to disassemble an old UltraBay drive and attach the frame to a newer or better one.

There are, however, some things to consider...

==The Limitations==
Even though these slim form factor drives seem to have a standard form factor at first look, it runs out that there are marginal mechanical differences. This makes it hard if at all possible to know beforehand if the UltraBay frame from your old drive will perfectly fit onto the new one. The fact that different UltraBay drives even for the same UltraBay standard have frames with different mechanical characteristics. Small differences can sometimes be adjusted my modifying parts of the frame, but this is of course not the nicest solution.

The most varying part is the Blending, which is usually not compatible even among drives of the same manufacturer. The position of the eject button, the drive LED, the emergency eject hole and the way the blending is attached to the drive all vary a lot. Do precise research before you buy anything. One solution here is to keep the original blending of the drive, since the UltraBay blending is independent from the rest of the frame. The disadvantage is an optical one: the standard blendings are usually flat whereas the UltraBay blendings usually are a bit thicker at the top and thinner at the bottom. Also, for some UltraBay standards you would have to cut out the lower right edge of the blending, since the standard drive blendings are usually rectangle shaped.

==UltraBay 2000==
The UltraBay 2000 frame consists of four parts: Blending, left wing, right wing and the back part containing the connector interface.

The left and right parts are attached with little screws in holes which are at standard positions and should usually fit among all drives. However, the actual drives show tiny variations in width, which are leveraged by the left and right parts. Hence these can be a bit thicker or thinner (fractions of 1mm). Putting a slightly thicker frame part onto a slightly thicker drive might result in an UltraBay drive that doesn't fit into the bay at all because it's just a tiny little bit to broad. This can be dealt with by i.e. sanding one of the side frame parts, but it's better if it all fits from the beginning. Also, the side frames have hatches fitting into the wholes in the back part. Among frames these hatches vary in thickness and length and hence, again, might not fit easily. Again, they can be adjusted by cutting them a bit.

{| border=1 cellspacing=0 cellpadding=2
|+ UltraBay 2000 drives and compatible alternative drives
|-
! UltraBay drive !! IBM Part-Nr. !! actual drive !! compatible drive !! needed steps to make fitting
|-
| 24x CD-ROM drive || ... || TEAC CD-224E || ... || ...
|-
| 8x DVD drive || 27L3447 || Matsushita SR-8175-M || ... || ...
|-
| 8x DVD drive || 08K9648 || Matsushita SR-8176-M || ... || ...
|}

Hardware Specifications

2005-06-22T09:50:10Z

Xoby:

==Hardware specs and information about the specific Thinkpad Models.==
* Choose a model name to to get a list of all currently available information related to this Model.
* Choose a type-and-model number to get the specs of that specific model.
* Compare the [[Thinkpad series]] (R, T, X, G), get an overview of the [[ThinkPad History]] or learn about the name [[ThinkPad]].
** For current G, R, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tabook.pdf tabook.pdf]
** For withdrawn A, G, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tawbook.pdf tawbook.pdf]
** For withdrawn R series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/trwbook.pdf trwbook.pdf]
** For withdrawn i series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tiwbook.pdf tiwbook.pdf]
** For withdrawn 200, 300, 500, 600 and 700 series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/twbook.pdf twbook.pdf]<br>
** Or try searching the IBM announcements letters [http://www.ibm.com/news/usalet/ here].

==Available Models==
{| cellspacing="0" cellpadding="5" border="1"
|- style="text-align:left;"
!Numbered!!A series!!G series!!R series!!S series!!T series!!X series!!others
|- style="text-align:left;vertical-align:top;"
|
'''[[:Category:390X | ThinkPad 390X]]'''
*[[2626-L0U]]

'''[[:Category:600X | ThinkPad 600X]]'''

'''[[:Category:700 | ThinkPad 700]]'''

'''[[:Category:770E | ThinkPad 770E]]'''
*[[9548-510]]
*[[9548-51U]]
*[[9548-52U]]

'''[[:Category:770X | ThinkPad 770X]]'''
*[[9549-7AO]]
'''[[:Category:770Z | ThinkPad 770Z]]'''

||
'''[[:Category:A20m | ThinkPad A20m]]'''

'''[[:Category:A20p | ThinkPad A20p]]'''

'''[[:Category:A21e | ThinkPad A21e]]'''

'''[[:Category:A21m | ThinkPad A21m]]'''

'''[[:Category:A21p | ThinkPad A21p]]'''

'''[[:Category:A22e | ThinkPad A22e]]'''

'''[[:Category:A22m | ThinkPad A22m]]'''

'''[[:Category:A22p | ThinkPad A22p]]'''

'''[[:Category:A30 | ThinkPad A30]]'''

'''[[:Category:A30p | ThinkPad A30p]]'''

'''[[:Category:A31 | ThinkPad A31]]'''

'''[[:Category:A31p | ThinkPad A31p]]'''

||
'''[[:Category:G40 | ThinkPad G40]]'''

'''[[:Category:G41 | ThinkPad G41]]'''

||
'''[[:Category:R30 | ThinkPad R30]]'''

'''[[:Category:R31 | ThinkPad R31]]'''

'''[[:Category:R32 | ThinkPad R32]]'''

'''[[:Category:R40 | ThinkPad R40]]'''
*[[2722-9BM]]

'''[[:Category:R40e | ThinkPad R40e]]'''

'''[[:Category:R50 | ThinkPad R50]]'''

'''[[:Category:R50p | ThinkPad R50p]]'''

'''[[:Category:R51 | ThinkPad R51]]'''
*[[1830-DG4]]

'''[[:Category:R52 | ThinkPad R52]]'''
||
'''[[:Category:S30|ThinkPad S30]]'''

'''[[:Category:S31|ThinkPad S31]]'''
||
'''[[:Category:T20|ThinkPad T20]]'''
*[[2647-44G]]

'''[[:Category:T21|ThinkPad T21]]'''
*[[2647-97G]]

'''[[:Category:T22|ThinkPad T22]]'''

'''[[:Category:T23 | ThinkPad T23]]'''
*[[2647-9RG]]
*[[2647-7G1]]

'''[[:Category:T30 | ThinkPad T30]]'''
*[[2366-52U]]
*[[2366-FBG]]
*[[2366-JBG]]
*[[2366-R7G]]

'''[[:Category:T40 | ThinkPad T40]]'''

'''[[:Category:T40p | ThinkPad T40p]]'''
*[[2372-G1U]]

'''[[:Category:T41 | ThinkPad T41]]'''

'''[[:Category:T41p | ThinkPad T41p]]'''
*[[2373-315]]
*[[2373-GEG]]
*[[2373-GGG]]
*[[2373-GHG]]

'''[[:Category:T42 | ThinkPad T42]]'''
*[[2373-6ZG]]
*[[2373-9XU]]
*[[2373-F1G]]
*[[2378-FVU]]
*[[2373-FWG]]
*[[2373-WGK]]

'''[[:Category:T42p | ThinkPad T42p]]'''
*[[2373-HTG]]
*[[2373-W6M]]
*[[2373-Y4M]]

'''[[:Category:T43 | Thinkpad T43]]'''
*[[2668-C2U]]

'''[[:Category:T43p | Thinkpad T43p]]'''
||
'''[[:Category:X20 | ThinkPad X20]]'''

'''[[:Category:X21 | ThinkPad X21]]'''
*[[2662-66U]]

'''[[:Category:X22 | ThinkPad X22]]'''
*[[2662-95U]]
*[[2662-9BU]]

'''[[:Category:X23 | ThinkPad X23]]'''

'''[[:Category:X24 | ThinkPad X24]]'''

'''[[:Category:X30 | ThinkPad X30]]'''

'''[[:Category:X31 | ThinkPad X31]]'''

'''[[:Category:X40 | ThinkPad X40]]'''

'''[[:Category:X41 | ThinkPad X41]]'''

'''[[:Category:X41 Tablet | ThinkPad X41 Tablet]]'''
||
'''[[:Category:PC110 | PC110]]'''
*[[PC110]]
'''[[:Category:TransNote|TransNote]]'''
*[[2675-61G]]
|}

[[Category:Models]]

Category:600X

2005-06-22T09:49:49Z

Xoby:

{| width="100%"
|style="vertical-align:top" |
[[image:ThinkPad600.jpg|ThinkPad 600X]]
|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;">
=== T

Category:600X

2005-06-22T09:49:27Z

Xoby:

Ibm-acpi

2005-06-22T09:48:45Z

Xoby:

== ibm-acpi - IBM ThinkPad ACPI Extras Driver ==

This is a Linux ACPI driver for the IBM ThinkPad laptops written by Borislav Deianov. It aims to support various features of these laptops which are accessible through the ACPI framework but not otherwise supported by the generic Linux ACPI drivers. As a kernel module, ibm-acpi works as a bridge to deliver information about certain hardware events like key presses or control the state of certain hardware features by software.

=== Features ===
* Fn key combinations ({{key|Fn}}{{key|F3}}, {{key|Fn}}{{key|F4}}, {{key|Fn}}{{key|F5}}, {{key|Fn}}{{key|F12}})
* Bluetooth enabling and disabling
* video output switching, video expansion control
* ThinkLight on/off
* limited docking and undocking
* UltraBay device eject
* control over several CMOS states
* control of LEDs
* beep generation
* five temperature sensors
* fan control

=== Project Homepage / Availability ===
http://ibm-acpi.sourceforge.net/

Included with the linux kernel since 2.6.10.

=== Status ===
in development, usable, very much alive

=== Packages ===
*[[:Category:Debian | Debian]] Packages: http://debian.isg.ee.ethz.ch/public/
*[[:Category:Gentoo | Gentoo]] ebuild: http://packages.gentoo.org/packages/?category=app-laptop;name=ibm-acpi

=== Application support===
* [http://www.gkrellm.net GKrellM] supports fan and thermal information

=== Interesting links related to this project ===
* [http://ibm-acpi.sf.net ibm-acpi Sourceforge project summary]
* [http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad Linux-Thinkpad Mailinglist]
* [http://acpi.sourceforge.net acpi.sourceforge.net]
* [http://www.kernel.org www.kernel.org]

[[Category:Drivers]]
[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X40]]
[[de:ibm-acpi]]

How to make ACPI work

2005-06-16T22:34:12Z

Xoby: /* Suspend to RAM (Sleep) */

==general==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.

If you prefer editing your .config file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
In general it is a good idea to read the README included with the driver.

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your XF86Config/xorg.conf.

Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

The following glitches may or may not occur in relation to suspending to RAM:
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.
* Crash on resume when using ATI proprietary drivers can be solved by using [http://freshmeat.net/projects/vbetool/ vbetool].

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* swsusp, which is in the kernel and
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

===using swsusp===
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.

To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.

In case you prefer to edit your config file directly, you should have the following three entries look like here...
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/resume_partition"
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)

You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.

To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.

Ideally you would do this from a script like <tt>/etc/acpi/actions/hibernate.sh</tt>. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.

Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:

amixer set Master mute >/dev/null 2>&1
amixer set PCM mute >/dev/null 2>&1
amixer set Master unmute >/dev/null 2>&1
amixer set PCM unmute >/dev/null 2>&1

Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.

===using SoftwareSuspend2===
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.

Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html

These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition

# Software Suspend 2
CONFIG_SOFTWARE_SUSPEND2=y
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set

Next, compile and install the kernel

In the meantime, add the following to the kernel parameters <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.

Install the hibernation script

For [[:Category:Gentoo | Gentoo]] users: emerge hibernate-script<br />
For [[:Category:Fedora_Core | Fedora Core]] users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br />
For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/

Debian users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your /etc/mkinitrd/scripts directory before creating initrd image.

Restart using the new kernel and run the script to test it out.
/usr/sbin/hibernate

[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

How to make ACPI work

2005-06-16T22:32:01Z

Xoby: /* Suspend to RAM (Sleep) */

==general==
===Kernel configuration===
First of all you'll have to enable ACPI support in your kernel (if your distro doesn't already have an ACPI enabled kernel).
To do this open your kernel config, go to <code>Power management options</code>, enable <code>Power Management support</code>, go to <code>ACPI</code> and enable the needed options. You'd most likely want to enable <code>Sleep States</code>, <code>AC Adapter</code>, <code>Battery</code>, <code>Fan</code>, <code>Processor</code> and <code>Thermal Zone</code>. Then recompile your kernel.

If you prefer editing your .config file directly, you should set at least the following variables:
CONFIG_PM=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y

===IBM specific ACPI driver===
Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10.<br />
So you'll have to compile one yourself or get it as precompiled module for your kernel.<br />
You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.<br />
If you use a post-2.6.10 kernel and you want to use [[ibm-acpi]], it is recommended to look on its projects page for a possibly newer version.<br />
In general it is a good idea to read the README included with the driver.

===ACPI daemon===
Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Read [[How to configure acpid]].

==Screen blanking (Standby)==
Make sure you have
Option "DPMS"
in the Monitor section of your XF86Config/xorg.conf.

Running {{cmd|xset +dpms}} and then {{cmd|xset dpms force off}} will turn off the backlight on a laptop screen.<br />

Note that this may not work in combination with {{cmd|echo -n "mem" > /sys/power/state}} because switching to console causes the backlight to come back on before sleeping.

==Suspend to RAM (Sleep)==
ACPI Sleep/suspend-to-ram with recent 2.6.x kernels usually works fine. Have a look at the [[How to configure acpid|acpid configuration HOWTO]]. It includes a specific example for going to sleep on lid close.

The following glitches may or may not occur in relation to suspending to RAM:
* With a 2.6.9 or 2.6.10 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding <tt>acpi_sleep=s3_bios</tt> to the kernel boot parameters. It seems this problem is solved in 2.6.11-rc1.
* When your system is equiped with a Radeon Mobility graphic controller your [[Problem with LCD backlight remaining on during ACPI sleep|LCD backlight may not turn off automatically]]. Use [[radeontool]] to switch off your backlight prior suspend in your sleep action script.
* Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].
* You may experience problems when using {{cmdroot|echo standby > /sys/power/state}} (machine goes to sleep and wakes up immediately). This can be avoided by using {{cmdroot|echo -n 3 >/proc/acpi/sleep}} to get it to sleep. This can be also happen if hotplug daemon is still running.
* Problems with the serial port of the port replicator after the wake up from ram have also been experienced.
* Crash on resume when using ATI proprietary drivers can be solved by using vbetool

==Suspend to disk (Hibernate)==
There are two drivers for this available:
* swsusp, which is in the kernel and
* [http://developer.berlios.de/projects/softwaresuspend/ SoftwareSuspend2] which is more feature rich, but not yet in the kernel, so you have to patch it in yourself
Both are reported to work fine as long as you use open-source graphic drivers. A comparison of the features can be found on [http://softwaresuspend.berlios.de/features.html this page].

Just in case you are in doubt...yes, it is safe in both cases to use the same swap partition as active swap and as suspend partition.

===using swsusp===
Software Suspend (swsusp) is included in the 2.6 kernel series. It seems like no patches for 2.4 kernels are available.

To enable it, go to <tt>Power management options</tt> and enable <tt>Power management support</tt> and <tt>Software Suspend</tt> in the kernel config menu. You'll also want to give the swap partition to suspend to in <tt>Default resume partition</tt>.

In case you prefer to edit your config file directly, you should have the following three entries look like here...
CONFIG_PM=y
CONFIG_SOFTWARE_SUSPEND=y
CONFIG_PM_STD_PARTITION="/dev/resume_partition"
...where <tt>/dev/resume_partition</tt> needs to be replaced by the swap partition you want to use for suspending. (Use {{cmdroot|fdisk -l /dev/hda}} if unsure.)

You can override the default resume partition anytime by giving <tt>resume=/dev/resume_partition</tt> as kernel boot parameter.
Also, in case you suspended, but want to boot up normally (without resuming from the saved image - loosing all data that was unsaved at suspend time), you can give the <tt>noresume</tt> kernel boot parameter.

To suspend you can either do a simple {{cmdroot|echo -n 4 > /proc/acpi/sleep}} (recommended) or use the [http://softwaresuspend.berlios.de/old-site/swsusp/sysvinit-2.76-v2-for_swsusp-v5.tar.gz patched SysVInit] and call {{cmdroot|swsusp}} or {{cmdroot|shutdown -z now}}.

Ideally you would do this from a script like <tt>/etc/acpi/actions/hibernate.sh</tt>. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the linuxant driver may require stopping in a acpi script as well. {{cmdroot|dldrstop}} does the trick.

Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

If the sound output is silent after resume, these commands might help to get sound to work again without reloading any modules:

amixer set Master mute >/dev/null 2>&1
amixer set PCM mute >/dev/null 2>&1
amixer set Master unmute >/dev/null 2>&1
amixer set PCM unmute >/dev/null 2>&1

Finally you should take note that swsusp does not set the ACPI S4 state. Instead it goes to S5. This means that the machine itself doesn't know that it was suspend rather than shutdown. Hence you can i.e. boot a parallel installed other operating system and resume your linux session later, as long as you don't touch the swap partition the image was saved to.

===using SoftwareSuspend2===
First apply Software Suspend 2 patches from http://softwaresuspend.berlios.de/ if they are not already in your kernel. I am running 2.6.11-rc4-nitro in a Thinkpad T30 2366.

Be sure to also read the http://softwaresuspend.berlios.de/HOWTO.html

These are the options for the kernel. You can change the <tt>/dev/hda5</tt> to your swap partition

# Software Suspend 2
CONFIG_SOFTWARE_SUSPEND2=y
CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y
CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y
CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y
CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y
CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda5"
# CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set
CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE=y
# CONFIG_SOFTWARE_SUSPEND_DEBUG is not set
# CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set

Next, compile and install the kernel

In the meantime, add the following to the kernel parameters <tt>resume2=swap:/dev/hda5</tt>. Again change <tt>/dev/hda5</tt> to your swap partition.

Install the hibernation script

For [[:Category:Gentoo | Gentoo]] users: emerge hibernate-script<br />
For [[:Category:Fedora_Core | Fedora Core]] users: kernel and hibernate RPMs are available at http://mhensler.de/swsusp/<br />
For all other users, check the home page for packages (deb, i386 rpm, tgz, and source rpm) from http://softwaresuspend.berlios.de/

Debian users using initrd image, make sure you copy [http://dagobah.ucc.asn.au/swsusp/2.0.0.102/swsusp-initrd.sh swsusp-initrd.sh] script to your /etc/mkinitrd/scripts directory before creating initrd image.

Restart using the new kernel and run the script to test it out.
/usr/sbin/hibernate

[[Category:570]] [[Category:570E]] [[Category:A20m]] [[Category:A20p]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]]

Installing Debian Sid (September 2004) on a ThinkPad T42p

2005-05-29T13:02:22Z

Xoby: Corrects mediaWiki tag error

==Links==
During my install of Debian Linux on my T42p I found the following Links to be very, very useful:

* [http://www.digriz.org.uk/t40p-linux/ A page with instructions for T40p.] Lots of useful info, but do not use the IRQ layout on this page for a T42p!
* Two more pages about Debian on T42p's: [http://modular.fas.harvard.edu/t42/ here] and [http://www.icemark.net/beh/misc/T42P here]
* [http://pompone.cs.ucsb.edu/~graziano/PowerPlay.html Enabling Powerplay (Radeon Power saving)] in three simple steps for debian XFree packages
* the original (closed-source) [[Fglrx | ATI drivers]] [http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html pre-packaged for debian] (to be compiled into a module deb with make-kpkg)
* An interesting [http://www.sas.upenn.edu/%7Evbraun/computing/T41/power.html Benchmark Page on Powersaving] with Windows vs Linux and APM vs ACPI
* A page documenting the first attempts to get [http://r300.sf.net/ hardware acceleration for the R300 GPU] (the one built into the T42p) running without the closed-source ATI drivers.
* another special and useful kernel module: [[Ibm-acpi | IBM-ACPI]] (since kernel versin 2.6.10 this is part of the stock kernel tree!)
* Quite some interesting add-ons for thinkpad-users, namely an extended Trackpoint driver with graphical configuration tool can be found here: [http://tpctl.sf.net tpctl home page] (unfortunately the trackpoint driver seems to be incompatible with the latest 2.6 kernels)
* [[BIOS_Upgrade | BIOS Updates]] [http://www-3.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55386 from IBM]

==First steps==
Unfortunately there are no detailed instructions here, yet. Visit the links above if you feel the present set of information is too terse for your taste.

For the first boot and maybe even the first install I recommend a recent [http://kanotix.mipooh.net/viewforum.php?f=8 Image of] [[Kanotix]] (a [[Knoppix]] descendant with lots of notebook-specific extensions built-in, so it should boot your Thinkpad with most bells and whistles right out of the box!)

Before you change or repartition your drive, visit the [[Installation steps which apply to every Thinkpad_model#Backup.2FRescue_CD_Set|Backup/Rescue-Section]].

If you want to keep your WinXP partition, take a look at the [[Installation steps which apply to every Thinkpad_model#Resizing_your_Windows_Partition|Partition-Resizing Section]].

If you compile a new kernel (recommended), you can use [http://fionn.de/config-t42p-2.6.8
this 2.6.8 kernel-configuration] as a starting point if you like. For kernel 2.6.8 you will also need to apply [http://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.8-rc3/2.6.8-rc3-mm1/broken-out/bk-cpufreq.patch this patch] and [http://gort.metaparadigm.com/cpufreq/cpufreq-speedstep-dothan-3.patch this one], too. Otherwise speedstep will not work on your Dothan CPU. I think in 2.6.9 this is fixed.

You might want to change your [[IRQ]] settings in BIOS

==Debian Packages==

The following packages are relevant to your Thinkpad installation:

====Kernel:====

* kernel-source-2.6.11 (or the latest version available)
* If you have a kernel version < 2.6.10: ibm-acpi-source (see [[Ibm-acpi | IBM-ACPI]])
* sl-modem-source (for the built-in modem)
* ipw2100-source (if you have the "simple" 802.11b WLAN option, otherwise you either need the atheros or ipw2200 drivers!)
* thinkpad-source (optional, I have yet to find a feature that thinkpad-modules offer and the more modern ibm-acpi does not)
* (optional) the closed-source [[Fglrx | ATI drivers]] [http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html pre-packaged for debian]

====Other:====

* sl-modem-daemon (modem)
* tpb (for the thinkpad buttons a nifty OSD, actually alot nicer than the WinXP one!)
* tpctl (needed to control some functions of the thinkpad kernel extensions)
* thinkpad-base
* acpid
* waproamd (automatically detects suitable wireless LANs and supports drop-in configuration)
* ifplugd (automatically detects network connections and brings up your interfaces accordingly)
* powernowd (Use this OPTIONS line in /etc/init.d/powernowd: OPTIONS="-q -m 0 -l 35 -p 500 -s 200000") and viola, there you got nice, all-automatic speedstepping.
* bluez-utils (for bluetooth)
* wireless-tools (for wlan)
* laptop-mode-tools (see [[Laptop-mode | laptop-mode]] for further information)

====DO NOT USE:====

* tleds (this package will fuck up your keyboard during network-io and tremendously slow down network throughput)

[[Category:T42p]] [[Category:Debian]]

Fglrx

2005-03-28T17:56:00Z

Xoby: /* Problems & Help */

== ATI drivers for Linux ==
Linux ATI driver for Radeon, FireGL and Mobility boards

How much is the speed gain versus the opensource drivers?

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

=== Status ===
Current version: 8.10.19 (16.02.2005)

=== Problems & Help ===

'''Driver Version 8.8.25:''' The following patch may be needed for kernels >= 2.6.10:
[http://www.rage3d.com/board/showthread.php?t=33798874 http://www.rage3d.com/board/showthread.php?t=33798874]

'''Driver Version 8.8.25:''' For kernels >= 2.6.11-rc1 try the following patch:
http://www.gehirn.org.uk/wiki/images/8.8.25-kernel-2.6.11+.patch

'''If the ATI driver works only without the hardware acceleration''', take into consideration that 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 libstdc++.so.5* to /usr/lib and update the dynamic linker cache.

'''Troubles using software suspend''' : when the computer comes back of suspend, X only displays a garbaged image and the computer is frozen. You have to install [http://www.srcf.ucam.org/~mjg59/vbetool/ vbetool] and use it to save/restore the video card state. If you use swsusp2 scripts you just have to uncomment ''"EnableVbetool yes"'' in ''/etc/hibernate/hibernate.conf''. Tested with kernel 2.6.10, Debian packaged ATI drivers and [http://www.suspend2.net swsusp2] patch on a IBM Thinkpad T42p.

=== Packages ===
*[[:Category:Debian | Debian]] Packages: http://xoomer.virgilio.it/flavio.stanchina/debian/fglrx-installer.html
*[[:Category:SuSE | SuSE]] Packages: ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/
*[[:Category:Gentoo | Gentoo]] {{cmdroot|emerge media-video/ati-drivers}}

=== Useful links ===
* [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://ati.cchtml.com/ Unofficial community ATI bugzilla] Very newly setup (!) bugzilla, which might grow to be a source for information about ATI bugs. Might then be monitored by ATI guys ([http://www.rage3d.com/board/showpost.php?p=1333438751&postcount=386], [http://www.rage3d.com/board/showpost.php?p=1333439009&postcount=390]). We will see how this develops.

[[Category:Drivers]] [[Category:Debian]] [[Category:SuSE]] [[Category:Gentoo]]

2373-WGK

2005-03-17T14:57:44Z

Xoby:

= IBM ThinkPad T42 2373-WGK Specifications =

== CPU and Memory ==
{|
|Processor Manufacturer || Intel
|-
|Processor Class || (Pentium M)
|-
|Processor Name || Intel Pentium M
|-
|Processor Speed || 1.7 GHz
|-
|Installed Memory || 512 MB
|-
|Maximum Memory || 2 GB
|-
|Memory Technology || DDR SDRAM
|-
|Cache Size || 2 Mo (L2)
|}
== Storage ==
{|
|Hard Drive Model || HTS548060M9AT00 (5400rpm)
|-
|Hard Drive Capacity || 60 GB
|-
|Included Drives || CD-RW / DVD Combo Drive
|}

== Display and Graphics ==
{|
|Display Size || 15 inch
|-
|Display Type || TFT active matrix
|-
|Graphics Processor || ATI Fire GL T2
|-
|Graphics Memory || 128 MB
|-
|Included Video Card || Graphics card - AGP 4x
|-
|Resolution ||1600 x 1200 pixels
|}

== Battery ==
{|
|Battery Model || 6 cell
|-
|Battery Cpacity || 47520 mWh
|-
|Battery Type || Lithium ion
|}

== Communications and Networking ==
{|
|Bluetooth || No
|-
|Modem Speed || 56 Kbps
|-
|Network LAN || Intel PRO/1000 MT
|-
|Network WLAN || Intel PRO/Wireless 2200BG MiniPCI card
|}

== Software ==
{|
|Shipped Operating System || Microsoft Windows XP
|}

== Connectors ==
{|
|Interface Provided ||Parallel Port, S-Video, VGA, Phone line, Headphone, Ethernet 10Base-T/100Base-TX/1000Base-T
|-
|Connectors ||2 x Hi-Speed USB - 4 pin USB Type A, 1 x parallel - IEEE 1284 (EPP/ECP) - 25 pin D-Sub (DB-25), 1 x display / video - VGA - 15 pin HD D-Sub (HD-15), 1 x infrared - IrDA, 1 x modem - phone line - RJ-11, 1 x network - Ethernet 10Base-T/100Base-TX/1000Base-T - RJ-45, 1 x display / video - S-video output - 4 pin mini-DIN, 1 x docking / port replicator, 1 x microphone - input - mini-phone mono 3.5 mm , 1 x audio - line-out/headphones - mini-phone stereo 3.5 mm
|}

== General Product Info ==
{|
|Input Devices || Keyboard, Touchpad, TrackPoint
|-
|Included Sound Card || Intel 82801DB (ICH4) rev.1
|-
|Weight || 2.2 Kg (4.9 lb)
|-
|Also known as || ...
|-
|Manufacturer Part No. || ...
|-
|Dimension || ... in (HxWxD)
|}

[[Category:T42]]

Hardware Specifications

2005-03-17T14:44:28Z

Xoby: /* Available Models */