ThinkWiki - User contributions [en]

Talk:Script for theft alarm using HDAPS

2009-04-24T04:43:27Z

Defiant: /* New Sox Version? */

Wonderful idea! And works perfectly on my T43p, scared the cat away. ;)

--[[User:Spiney|spiney]] 20:35, 12 Nov 2005 (CET)
----

Good, so it's at least a cat deterrant! A friend of mine had a nasty incident involving a laptop and a cat...
BTW, I'm the author (identifed by IP address again due the usual ThinkWiki autologin flakiness).

--[[User:Thinker|Thinker]] 20:52, 12 Nov 2005 (CET)
----
I had to tweak the line that reads the position file. My position file has - numbers in it for some reason, so:
m/^$-(\d+),-(\d+)$$/ or die "Can't parse $pos_file content\n";

After that change it works great.
It scared the dogs away here. ;)
--[[User:nirik|nirik]] 21:24, 12 Nov 2005 (CET)
----

Fixed. Which ThinkPad model, BTW?

--[[User:Thinker|Thinker]] 21:44, 12 Nov 2005 (CET)
----
Cool. Excellent. ;)

T42p here.

--[[User:Nirik|Nirik]] 21:45, 12 Nov 2005 (CET)
----

I love it! Great contributions, Thinker!

Of course, it is more proof-of-concept tough, as a thief can simply hit the "mute" button, or carry an old headphone plug with the actual headphones chopped off and stuff this quickly into the audio out jack. Don't leave your laptop unattended :) :)

--[[User:Gsmenden|Gsmenden]] 18:06, 28 Nov 2005 (CET)
----

Thanks! About muting, I'm not sure the mute button will work (I reset the mixer volumes every second), but the thief can certainly power off, or suspend, or pull out the AC and battery. But my hope is that the casual, uninformed laptop-snatcher will trigger the alarm for at least a few seconds, and if you're just down the hall or there are other people nearby, that's probably enough to save your laptop. Not as good as a real lock+alarm, but better than nothing, and pretty convenient when autoactivated by the screensaver (<tt>$use_kde=1</tt>).

--[[User:Thinker|Thinker]] 01:40, 29 Nov 2005 (CET)
----

someone asked if it's possible to watch out for gnome-screensaver.
- it is, using dbus-monitor (like explained on the gnome-screensaver faq page).

the following perl script

my $cmd = "dbus-monitor --session \"type='signal',interface='org.gnome.ScreenSaver',member='SessionIdleChanged'\"";

open (IN,"-|", "$cmd");

while (<IN>) {
if (m/^\s+boolean true/) {
print "screensaver is now active";
} elsif (m/^\s+boolean false/) {
print "screensaver is now inactive";
}
}

will print when gnome-screensaver goes active

The ugly part is

1. You can only find out once gnome-screensaver is going active or inactive, but not if it's active when the scripts is started.

2. I don't really know how to check if there is new output in <IN>, because something like my $cmdline=<IN>; will hang until there is new output (like when the screensaver is going (in)active).

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

==Usefulness for head parking==
Works great. Maybe we can the script for testing the disk park patches by Jon Escombe <lists@dresco.co.uk>
-- [[User:Ozi23]]
----

You can use it for testing, but note that the specific algorithm used in this script (threshold on standard deviation of samples during last second) is optimized for the theft deterrent situation. It is highly unsuitable for the head parking application, since it reacts too slowly -- by the it will recognize the movement, the disk heads will have already crashed. For head parking you'd need a low-latency algorithm, and preferably an in-kernel implementation to allow frequeny low-overhead polling, reduce latencies, and avoid accidentally spinning the disk ''up'' when loading or swapping in userspace stuff needed to spin the disk ''down''.

--[[User:Thinker|Thinker]] 20:20, 14 Nov 2005 (CET)
----

It's even worse that I thought. Check out the [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/aps2mst.pdf IBM white paper] - there's barely enough time to park the head, so in the Windows driver they're using some pretty fancy learning algorithm to deduce when movement deviates from "normal", to decide when to redefine "normal".

--[[User:Thinker|Thinker]] 19:08, 22 Nov 2005 (CET)
----

Good news every one .....
Just kidding. I've found the hdapsd package which acts as a deamon for the hdaps and uses the kernel patch by Jon Escombe. I havent tested it but some people
were able to get the protection system work. It seems to depend on the firmware of the harddrive. Its in early stage so be carefull.

http://lwn.net/Articles/154923/ (kernel patch)
http://bugs.gentoo.org/show_bug.cgi?id=100167 (hdapsd)

----

== Minor modifications ==

tp-theft.pl v0.33 is working fine here, but I have modified some parts:
* I made a change for kdesktop_lock since it is located in /usr/kde/<kde-version>/bin/ here (Gentoo-specific)
* I removed the check wether kdesktop is running. I start tp-theft.pl via inittab which will be up before I have logged in

-- satmd, 2005-12-25

What's Gentoo's way of finding out the KDE path? I suppose
my $bin = `which kdesktop_lock`;
won't work from an initscript because the PATH is not set up yet.

--[[User:Thinker|Thinker]] 23:38, 25 Dec 2005 (CET)

With Gentoo
/usr/bin/env kde-config --exec-prefix --expandvars
returns /usr/kde/3.5 . That looks general useable to me.
I do not use an initscript, but inittab
... with initscripts one could easily source /etc/profile or something.

-- satmd, 2005-12-25

Will an inittab script find <tt>kde-config</tt>, which is probably in {{path|/usr/kde/<kde-version>/bin/}} too? And if so, won't <tt>which kdedesktop_lock</tt> also work?

--[[User:Thinker|Thinker]] 00:56, 26 Dec 2005 (CET)

Did not work - both of them. Keeping my hardcoded value.
-- satmd, 2005-12-26 06:09 CET

== Is there a way do make something like this work on Windows? ==

see topic.

----
theoretically speaking yes, since the accelerometer must be readable in windows too.

But I doubt there is an easy way to find out how to read it.

You might want to decompile the ibm hdaps active protection script to find out.

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

== Debian/Ubuntu libsox dependencies ==

Just a little Debian/Ubuntu heads-up:

If you get this error:

''sox soxio: Can't open output file `/dev/dsp': unknown file type `ossdsp'''

...then try installing '''libsox-fmt-oss'''. This fixed the problem for me, on Debian Etch. I based this info off of an Ubuntu forum post... different problem, but the same error message:
http://ubuntuforums.org/showthread.php?t=740612

--[[User:ashank|Andy Shank]] 14:38, 13 Oct 2008 (MST)
----

== New Sox Version? ==

I got this error

''sox formats: no handler for given file type `nul'''

with current sox 14.2.0 in Debian unstable.

Replacing ''-t nul /dev/null'' with ''-t'' fixed it for me.
I'm not changing the script because I guess the majority is still using older sox.

--[[User:Defiant|Defiant]] 18:25, 23 April 2009 (UTC)

Talk:Script for theft alarm using HDAPS

2009-04-24T04:42:53Z

Defiant: /* New Sox Version? */

Wonderful idea! And works perfectly on my T43p, scared the cat away. ;)

--[[User:Spiney|spiney]] 20:35, 12 Nov 2005 (CET)
----

Good, so it's at least a cat deterrant! A friend of mine had a nasty incident involving a laptop and a cat...
BTW, I'm the author (identifed by IP address again due the usual ThinkWiki autologin flakiness).

--[[User:Thinker|Thinker]] 20:52, 12 Nov 2005 (CET)
----
I had to tweak the line that reads the position file. My position file has - numbers in it for some reason, so:
m/^$-(\d+),-(\d+)$$/ or die "Can't parse $pos_file content\n";

After that change it works great.
It scared the dogs away here. ;)
--[[User:nirik|nirik]] 21:24, 12 Nov 2005 (CET)
----

Fixed. Which ThinkPad model, BTW?

--[[User:Thinker|Thinker]] 21:44, 12 Nov 2005 (CET)
----
Cool. Excellent. ;)

T42p here.

--[[User:Nirik|Nirik]] 21:45, 12 Nov 2005 (CET)
----

I love it! Great contributions, Thinker!

Of course, it is more proof-of-concept tough, as a thief can simply hit the "mute" button, or carry an old headphone plug with the actual headphones chopped off and stuff this quickly into the audio out jack. Don't leave your laptop unattended :) :)

--[[User:Gsmenden|Gsmenden]] 18:06, 28 Nov 2005 (CET)
----

Thanks! About muting, I'm not sure the mute button will work (I reset the mixer volumes every second), but the thief can certainly power off, or suspend, or pull out the AC and battery. But my hope is that the casual, uninformed laptop-snatcher will trigger the alarm for at least a few seconds, and if you're just down the hall or there are other people nearby, that's probably enough to save your laptop. Not as good as a real lock+alarm, but better than nothing, and pretty convenient when autoactivated by the screensaver (<tt>$use_kde=1</tt>).

--[[User:Thinker|Thinker]] 01:40, 29 Nov 2005 (CET)
----

someone asked if it's possible to watch out for gnome-screensaver.
- it is, using dbus-monitor (like explained on the gnome-screensaver faq page).

the following perl script

my $cmd = "dbus-monitor --session \"type='signal',interface='org.gnome.ScreenSaver',member='SessionIdleChanged'\"";

open (IN,"-|", "$cmd");

while (<IN>) {
if (m/^\s+boolean true/) {
print "screensaver is now active";
} elsif (m/^\s+boolean false/) {
print "screensaver is now inactive";
}
}

will print when gnome-screensaver goes active

The ugly part is

1. You can only find out once gnome-screensaver is going active or inactive, but not if it's active when the scripts is started.

2. I don't really know how to check if there is new output in <IN>, because something like my $cmdline=<IN>; will hang until there is new output (like when the screensaver is going (in)active).

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

==Usefulness for head parking==
Works great. Maybe we can the script for testing the disk park patches by Jon Escombe <lists@dresco.co.uk>
-- [[User:Ozi23]]
----

You can use it for testing, but note that the specific algorithm used in this script (threshold on standard deviation of samples during last second) is optimized for the theft deterrent situation. It is highly unsuitable for the head parking application, since it reacts too slowly -- by the it will recognize the movement, the disk heads will have already crashed. For head parking you'd need a low-latency algorithm, and preferably an in-kernel implementation to allow frequeny low-overhead polling, reduce latencies, and avoid accidentally spinning the disk ''up'' when loading or swapping in userspace stuff needed to spin the disk ''down''.

--[[User:Thinker|Thinker]] 20:20, 14 Nov 2005 (CET)
----

It's even worse that I thought. Check out the [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/aps2mst.pdf IBM white paper] - there's barely enough time to park the head, so in the Windows driver they're using some pretty fancy learning algorithm to deduce when movement deviates from "normal", to decide when to redefine "normal".

--[[User:Thinker|Thinker]] 19:08, 22 Nov 2005 (CET)
----

Good news every one .....
Just kidding. I've found the hdapsd package which acts as a deamon for the hdaps and uses the kernel patch by Jon Escombe. I havent tested it but some people
were able to get the protection system work. It seems to depend on the firmware of the harddrive. Its in early stage so be carefull.

http://lwn.net/Articles/154923/ (kernel patch)
http://bugs.gentoo.org/show_bug.cgi?id=100167 (hdapsd)

----

== Minor modifications ==

tp-theft.pl v0.33 is working fine here, but I have modified some parts:
* I made a change for kdesktop_lock since it is located in /usr/kde/<kde-version>/bin/ here (Gentoo-specific)
* I removed the check wether kdesktop is running. I start tp-theft.pl via inittab which will be up before I have logged in

-- satmd, 2005-12-25

What's Gentoo's way of finding out the KDE path? I suppose
my $bin = `which kdesktop_lock`;
won't work from an initscript because the PATH is not set up yet.

--[[User:Thinker|Thinker]] 23:38, 25 Dec 2005 (CET)

With Gentoo
/usr/bin/env kde-config --exec-prefix --expandvars
returns /usr/kde/3.5 . That looks general useable to me.
I do not use an initscript, but inittab
... with initscripts one could easily source /etc/profile or something.

-- satmd, 2005-12-25

Will an inittab script find <tt>kde-config</tt>, which is probably in {{path|/usr/kde/<kde-version>/bin/}} too? And if so, won't <tt>which kdedesktop_lock</tt> also work?

--[[User:Thinker|Thinker]] 00:56, 26 Dec 2005 (CET)

Did not work - both of them. Keeping my hardcoded value.
-- satmd, 2005-12-26 06:09 CET

== Is there a way do make something like this work on Windows? ==

see topic.

----
theoretically speaking yes, since the accelerometer must be readable in windows too.

But I doubt there is an easy way to find out how to read it.

You might want to decompile the ibm hdaps active protection script to find out.

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

== Debian/Ubuntu libsox dependencies ==

Just a little Debian/Ubuntu heads-up:

If you get this error:

''sox soxio: Can't open output file `/dev/dsp': unknown file type `ossdsp'''

...then try installing '''libsox-fmt-oss'''. This fixed the problem for me, on Debian Etch. I based this info off of an Ubuntu forum post... different problem, but the same error message:
http://ubuntuforums.org/showthread.php?t=740612

--[[User:ashank|Andy Shank]] 14:38, 13 Oct 2008 (MST)
----

== New Sox Version? ==

I got this error

''sox formats: no handler for given file type `nul'''

with current sox 14.2.0 in Debian unstable.

Replacing ''-t nul /dev/null'' with ''-t'' fixed it for me.
I'm not changing the script because I think the majority is still using older sox.

--[[User:Defiant|Defiant]] 18:25, 23 April 2009 (UTC)

Talk:Script for theft alarm using HDAPS

2009-04-23T18:25:40Z

Defiant: sox error: no handler for given file type nul

Wonderful idea! And works perfectly on my T43p, scared the cat away. ;)

--[[User:Spiney|spiney]] 20:35, 12 Nov 2005 (CET)
----

Good, so it's at least a cat deterrant! A friend of mine had a nasty incident involving a laptop and a cat...
BTW, I'm the author (identifed by IP address again due the usual ThinkWiki autologin flakiness).

--[[User:Thinker|Thinker]] 20:52, 12 Nov 2005 (CET)
----
I had to tweak the line that reads the position file. My position file has - numbers in it for some reason, so:
m/^$-(\d+),-(\d+)$$/ or die "Can't parse $pos_file content\n";

After that change it works great.
It scared the dogs away here. ;)
--[[User:nirik|nirik]] 21:24, 12 Nov 2005 (CET)
----

Fixed. Which ThinkPad model, BTW?

--[[User:Thinker|Thinker]] 21:44, 12 Nov 2005 (CET)
----
Cool. Excellent. ;)

T42p here.

--[[User:Nirik|Nirik]] 21:45, 12 Nov 2005 (CET)
----

I love it! Great contributions, Thinker!

Of course, it is more proof-of-concept tough, as a thief can simply hit the "mute" button, or carry an old headphone plug with the actual headphones chopped off and stuff this quickly into the audio out jack. Don't leave your laptop unattended :) :)

--[[User:Gsmenden|Gsmenden]] 18:06, 28 Nov 2005 (CET)
----

Thanks! About muting, I'm not sure the mute button will work (I reset the mixer volumes every second), but the thief can certainly power off, or suspend, or pull out the AC and battery. But my hope is that the casual, uninformed laptop-snatcher will trigger the alarm for at least a few seconds, and if you're just down the hall or there are other people nearby, that's probably enough to save your laptop. Not as good as a real lock+alarm, but better than nothing, and pretty convenient when autoactivated by the screensaver (<tt>$use_kde=1</tt>).

--[[User:Thinker|Thinker]] 01:40, 29 Nov 2005 (CET)
----

someone asked if it's possible to watch out for gnome-screensaver.
- it is, using dbus-monitor (like explained on the gnome-screensaver faq page).

the following perl script

my $cmd = "dbus-monitor --session \"type='signal',interface='org.gnome.ScreenSaver',member='SessionIdleChanged'\"";

open (IN,"-|", "$cmd");

while (<IN>) {
if (m/^\s+boolean true/) {
print "screensaver is now active";
} elsif (m/^\s+boolean false/) {
print "screensaver is now inactive";
}
}

will print when gnome-screensaver goes active

The ugly part is

1. You can only find out once gnome-screensaver is going active or inactive, but not if it's active when the scripts is started.

2. I don't really know how to check if there is new output in <IN>, because something like my $cmdline=<IN>; will hang until there is new output (like when the screensaver is going (in)active).

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

==Usefulness for head parking==
Works great. Maybe we can the script for testing the disk park patches by Jon Escombe <lists@dresco.co.uk>
-- [[User:Ozi23]]
----

You can use it for testing, but note that the specific algorithm used in this script (threshold on standard deviation of samples during last second) is optimized for the theft deterrent situation. It is highly unsuitable for the head parking application, since it reacts too slowly -- by the it will recognize the movement, the disk heads will have already crashed. For head parking you'd need a low-latency algorithm, and preferably an in-kernel implementation to allow frequeny low-overhead polling, reduce latencies, and avoid accidentally spinning the disk ''up'' when loading or swapping in userspace stuff needed to spin the disk ''down''.

--[[User:Thinker|Thinker]] 20:20, 14 Nov 2005 (CET)
----

It's even worse that I thought. Check out the [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/aps2mst.pdf IBM white paper] - there's barely enough time to park the head, so in the Windows driver they're using some pretty fancy learning algorithm to deduce when movement deviates from "normal", to decide when to redefine "normal".

--[[User:Thinker|Thinker]] 19:08, 22 Nov 2005 (CET)
----

Good news every one .....
Just kidding. I've found the hdapsd package which acts as a deamon for the hdaps and uses the kernel patch by Jon Escombe. I havent tested it but some people
were able to get the protection system work. It seems to depend on the firmware of the harddrive. Its in early stage so be carefull.

http://lwn.net/Articles/154923/ (kernel patch)
http://bugs.gentoo.org/show_bug.cgi?id=100167 (hdapsd)

----

== Minor modifications ==

tp-theft.pl v0.33 is working fine here, but I have modified some parts:
* I made a change for kdesktop_lock since it is located in /usr/kde/<kde-version>/bin/ here (Gentoo-specific)
* I removed the check wether kdesktop is running. I start tp-theft.pl via inittab which will be up before I have logged in

-- satmd, 2005-12-25

What's Gentoo's way of finding out the KDE path? I suppose
my $bin = `which kdesktop_lock`;
won't work from an initscript because the PATH is not set up yet.

--[[User:Thinker|Thinker]] 23:38, 25 Dec 2005 (CET)

With Gentoo
/usr/bin/env kde-config --exec-prefix --expandvars
returns /usr/kde/3.5 . That looks general useable to me.
I do not use an initscript, but inittab
... with initscripts one could easily source /etc/profile or something.

-- satmd, 2005-12-25

Will an inittab script find <tt>kde-config</tt>, which is probably in {{path|/usr/kde/<kde-version>/bin/}} too? And if so, won't <tt>which kdedesktop_lock</tt> also work?

--[[User:Thinker|Thinker]] 00:56, 26 Dec 2005 (CET)

Did not work - both of them. Keeping my hardcoded value.
-- satmd, 2005-12-26 06:09 CET

== Is there a way do make something like this work on Windows? ==

see topic.

----
theoretically speaking yes, since the accelerometer must be readable in windows too.

But I doubt there is an easy way to find out how to read it.

You might want to decompile the ibm hdaps active protection script to find out.

--[[User:Mcgiver|Mcgiver]] 20:35, 12 Nov 2005 (CET)
----

== Debian/Ubuntu libsox dependencies ==

Just a little Debian/Ubuntu heads-up:

If you get this error:

''sox soxio: Can't open output file `/dev/dsp': unknown file type `ossdsp'''

...then try installing '''libsox-fmt-oss'''. This fixed the problem for me, on Debian Etch. I based this info off of an Ubuntu forum post... different problem, but the same error message:
http://ubuntuforums.org/showthread.php?t=740612

--[[User:ashank|Andy Shank]] 14:38, 13 Oct 2008 (MST)
----

== New Sox Version? ==

I got this error

''sox formats: no handler for given file type `nul'''

with current sox 14.2.0 in Debian unstable.

Replacing ''-t nul /dev/null'' with ''-t'' fixed it for me.
I'm not changing the script because I think the majority is still using older sox.

[[User:Defiant|Defiant]] 18:25, 23 April 2009 (UTC)

How to hotswap Ultrabay devices

2008-06-28T11:40:52Z

Defiant: /* Details */ added T43

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

==Which driver?==
Since this may be confusing for SATA thinkpad owners, which are likely all the same for now, you have two busses and drivers: one SATA bus which works with the AHCI driver and one IDE bus for the ultrabay for which you should pick ata_piix (not piix/CONFIG_BLK_DEV_PIIX). See below for hotswapping.

==Choosing the right driver: new style <tt>ata_piix</tt> vs old style <tt>piix/ide-disk</tt>==
For ICH5,6,7,8, systems, whether you have an older IDE only thinkpad, or a newer thinkpad like the T/Z61p, there is one SATA bus for the system hard drive and an IDE bus for the ultrabay (even if your ultrabay happens to have a SATA drive, as it'll be seen as an IDE device), you'll have two drivers to chose from for your ultrabay: the old IDE/piix+ide-disk driver, and the newer PATA (=IDE) support of the newer ata_piix driver. 
<tt>piix+ide-disk</tt> are part of the old original IDE driver and your ultrabay device will show up as <tt>/dev/hda</tt>. <tt>ata-piix</tt> is the new SATA/PATA (=IDE) driver that will cause your ultrabay Hard Drive to show up as <tt>/dev/sda</tt> and your CD-Rom as <tt>/dev/sr0</tt>

The two things to know are: 1) you want to use ata_piix and 2) if you build piix in (CONFIG_BLK_DEV_PIIX enabled), or load it as a module, it'll take over the IDE bus and prevent ATA_PIIX from seeing your ultrabay. You don't want that.

The longer details are: 
You don't want the piix+ide-disk combo because even as modules, you will not be able to unload piix to reset the bus if there are issues swapping devices (with ata_piix, even if you forget to unregister a drive before removing it, you can unload the module and reload it to reset the bus after the fact if you have a newer thinkpad with a separate AHCI/SATA bus for the boot drive).

As for hotswap, with piix+ide-disk, you can read the section below, but after more than one day of trying on 2.6.22.15 (as piix+ide-disk was taking over my IDE bus, and stopping me from using ata_piix before I removed it), I was not able to get hotswapping to work with piix+ide-disk (lt_hotswap would not even build on 2.6.22.15).

hotswap just works with ata_pixx on 2.6.22, and reportedly with anything newer than 2.6.18, so you want to get rid of piix+ide-disk.
There are several ways to do that:
* if piix is built in your kernel (CONFIG_BLK_DEV_PIIX):
** rebuild your kernel with CONFIG_BLK_DEV_PIIX turned off.
** if you don't want to rebuild your kernel, try disabling the IDE bus grabbing by that driver with <tt>ide0=noprobe hda=noprobe hdb=noprobe</tt> in your grub/lilo config (adjust the drive letters as appropriate, but note that this did not work for me on 2.6.22.15: the drive didn't show up on the piix bus, but it didn't show up on the ata_piix bus either).
* if piix is built in as a module
** you can move out the module in {{path|/lib/modules/ver/kernel/drivers/ide/pci/piix.ko}} and reboot.
** or build a new kernel, again with CONFIG_BLK_DEV_PIIX turned off.
** or add <tt>options ide_core options="ide0=noprobe hda=noprobe hdb=noprobe"</tt> to your modprobe.conf is supposed to work too (but didn't work on 2.6.22.15, see comment above)

Then, continue this document to see how to do hotswap with ata_piix (if you are lucky enough to have a newer SATA thinkpad where the ata_piix driver only runs the ultrabay, and you have a separate bus and ahci driver for your main drive, it is recommended to have ata_piix as a module (<tt>CONFIG_ATA_PIIX=m</tt>) so that you can unload/reload it if your bus gets in a bad state after a failed hotswap)

==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 the following laptops, with bus the following ID
**ThinkPad {{T30}}
**ThinkPad {{T43}}, {{T43p}}
**ThinkPad {{R52}}
**ThinkPad {{T60}} ID=4
**ThinkPad {{T61}} ID=0
**ThinkPad {{Z61p}} ID=4 (0-3:ahci, 5-6: ata_piix)
ID will typically be 1 if you only have an IDE bus (0 is boot drive, 1 is ultrabay), and it'll be 4 if you have a SATA bus your system boots from (ID 0-3) and an IDE bus for your ultrabay (ID 4-5). 
Note that even on a given laptop model the ID can vary depending on whether your kernel has drivers that configure your boot drive is using the old style IDE driver (which doesn't add IDs before your ultrabay), or whether your boot drive is using the new style driver (which adds IDs before your ultrabay)

Hotplug just works with kernels newer than 2.6.18 ( or older kernels that were patched to support <tt>ata_piix</tt> hotplug (don't try it otherwise!)) 
First, it is recommended you find the right SCSI ID for your drive to hotswap and unregister it before removing it (this works with all recent mainline kernels):
{{cmdroot|echo 1 > /sys/class/scsi_device/$ID:0:0:0/device/delete}}
{{cmdroot|echo eject > /proc/acpi/ibm/bay}}
The drive can now be ejected (without this, your IDE bus may complain if you just yank a drive, but you can usually recover by unloading/reloading the ata_piix module on a SATA laptop if your main drive is not on the ata_piix bus)

You can then issue the following after inserting an UltraBay drive to rescan the port:
{{cmdroot|echo 0 0 0 > /sys/class/scsi_host/host$ID/scan}}
The inserted drive should now be recognized by the kernel, and appropriate {{path|/dev/*}} entries created automatically (e.g., by <tt>udev</tt>).

Ted T'so has also written this hotswap patch, which may or may not be needed for you, see [http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg04716.html hotswap patch] and report back

===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_insert}} 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_eject}} 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 /sys/devices/platform/bay.0 ]; then
echo 1 > /sys/devices/platform/bay.0/eject
elif [ -e /proc/acpi/ibm/bay ]; then
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-insert}}:
<pre>
event=ibm/bay MSTR 00000001 00000000
action=/usr/local/sbin/ultrabay_insert
</pre>

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

Restart <tt>acpid</tt>.

===using the generic bay driver and udev===

Starting from kernel 2.6.23-rc3, it's possible to use the generic <tt>bay</tt> driver in combination with udev to hotswap. Please check if CONFIG_ACPI_BAY is enabled (module or built-in) in your kernel configuration.

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
<pre>
ENV{BAY_EVENT}=="3", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_eject"
ENV{BAY_EVENT}=="1", KERNEL=="bay.0", ACTION=="change", SUBSYSTEM=="platform", RUN+="/usr/local/sbin/ultrabay_insert"
</pre>

===using libata-acpi and udev===

Starting from kernel 2.6.26-rc5, it's possible to use <tt>libata-acpi</tt> in combination with udev to hotswap. Please check if CONFIG_ATA_ACPI is enabled in your kernel configuration.

For 2.6.25, you need two patches which can be easily backported ([http://article.gmane.org/gmane.linux.acpi.devel/31159],[http://article.gmane.org/gmane.linux.acpi.devel/31369]).

Create {{path|/etc/udev/rules.d/ibm-ultrabay.rules}}:
<pre>
ENV{BAY_EVENT}=="3", ACTION=="change", SUBSYSTEM=="scsi", RUN+="/usr/local/sbin/ultrabay_eject"
</pre>

===Model-specific notes===
See the table above for a list of ata_piix supported laptops and the bus ID to use.

===HAL support===

{{NOTE| Starting from HAL 0.5.11, you need to replace "storage.physical_device" with "info.parent".}}

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_0_scsi_device_lun0">
<merge key="storage.hotpluggable" type="bool">true</merge>
</match>
</match>

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

The string "8086_2653" may need to be changed to match your ThinkPad model; see below.

====Details====

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

# PHYSDEV=/org/freedesktop/Hal/devices/pci_8086_2653_scsi_host_0_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_0_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_0_scsi_device_lun0

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

{| border=1
|+ Known South Bridge PCI IDs
! ID !! ThinkPad model !! South Bridge chip
|-
| 8086_248a || 2366-83U (T30) || Intel 82801CAM IDE U100 (rev 2)
|-
| 8086_2653 || 2525FAG (X41, T43) || Intel 82801FBM (ICH6-M)
|-
| 8086_24ca || 237358U (T40), 2373KXU (T42p) || Intel 82801DBM (ICH4-M)
|-
| 8086_27c4 || X60 || Intel 82801GBM (ICH7 Family)
|-
| 8086_27df || Z61p, T60, T60p || Intel 82801GBM/GHM (ICH7 Family)
|-
| 8086_2850 || T61p || Intel 82801H (ICH8 Family)
|}

==When using the <tt>ide-disk</tt> driver==
The following applies if you use the <tt>ide-disk</tt> driver for the UltraBay device. 
Note that essentially, you shouldn't be using this driver, and use ata_piix instead unless you're running an older kernel where ata_piix won't work for you

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]]. Note that lt_hotswap doesn't seem to even build on recent (at 2.6.22 or newer, although it probably broke before 2.6.22) and on newer kernels, you should not build/load the old IDE PIIX (CONFIG_BLK_DEV_PIIX) and use the natively hotswapping ata_piix (CONFIG_ATA_PIIX) as explained on the top of this page.

[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 (if loaded with the auto_eject=1 option) 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). With the [[lt_hotswap]] kernel module loaded, run: {{cmdroot|modprobe -r ide_cd && modprobe -r cdrom && echo "MSTR eject" > /proc/acpi/lths}}

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

==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]]
[[Category:HOWTOs]]

HDAPS

2008-02-14T06:56:44Z

Defiant: /* Kernel patch */ 2.6.24 fix

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
=== HDAPS - IBM Active Protection System Linux Driver ===
This is the Linux driver for monitoring the accelerometer known as [[Active Protection System|IBM Active Protection System]].

The driver only enables reading of the acceleration data. It does '''not''' perform [[#Harddisk Protection|automatic disk head parking]]. But there are already some other useful [[#Applications|applications]] for HDAPS, using the {{path|/sys}} interface it provides.

{{WARN|There are two versions of the hdaps driver, one in the Linux kernel mainline, and another provided by [[tp_smapi]]. '''Use of the tp_smapi version of hdaps is strongly recommended by the current hdaps developers.'''}}
|}

=== Features ===
*provides accelerometer values via sysfs
*provides a joystick type input device

=== Project Homepage / Availability ===
*[http://hdaps.sourceforge.net/ Project Homepage]
*The driver is included in the 2.6-mm series of kernels since August, 26th 2005.
*The driver is now in the mainline (2.6.14).
*The [[tp_smapi]] package contains some patches to this driver. These are necessary for some recent models, and recommended for all.

=== Status ===
A driver is included in recent Linux kernels and is actively maintained, but it is very inferior to the driver in tp_smapi (which provides its own hdaps module).

=== How to install the driver ===
Recent Linux kernels include the <tt>hdaps</tt> driver. However, the driver in the mainline Linux kernel has two problems with recent models:
* It doesn't whitelist them (you have to edit hdaps_init() in drivers/hwmon/hdaps.c to include a line like <tt>HDAPS_DMI_MATCH_LENOVO("ThinkPad T60")</tt>)
* It doesn't work reliably, e.g., it may read out constant values (0,0). See [http://sourceforge.net/mailarchive/message.php?msg_id=15350314 here].

To solve both problems, install the modified hdaps that is bundled with [[tp_smapi]].

=== Harddisk Protection ===
As mentioned above, the hdaps kernel driver is only responsible for reading the accelerometer data and exporting it through the sysfs interface. In order to use this information to protect the disk, some additional steps are required.

See [[How to protect the harddisk through APS]].

=== Input device support ===
The hdaps driver in the lastest kernels (2.6.14 and later?) also exports a joystick type input device, which can be used by games.

=== Applications ===
====Disk head parking====
You will need the kernel patch and userspace daemon. The GUI monitoring is optional.

See [[How to protect the harddisk through APS]] for more information.

===== Kernel patch =====
Apply these using 'patch -p1 -l < hdaps_xx.patch'.
* New interface
**[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1094 disk-protect patch for kernel 2.6.24-rc3] — may cause system locks (see [http://marc.info/?l=linux-thinkpad&m=120259594519907 here], [http://marc.info/?l=linux-thinkpad&m=120259929023300 here] and try [http://sourceforge.net/mailarchive/attachment.php?list_name=hdaps-devel&message_id=87bq6l2ihm.fsf@denkblock.local&counter=1 this fix])
**[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1092 disk-protect patch for 2.6.23.8] + [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1113 error check fix]
**[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1077 disk-protect patch for 2.6.22.9 and 2.6.23-rc9]
**[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993 disk-protect patch for 2.6.20-rc6]
* Old interface
**[http://www.nabble.com/attachment/9047418/0/hdaps_protect-2.6.20.patch.bz2 Latest sata/ide disk protection patch for 2.6.20]
**[http://article.gmane.org/gmane.linux.kernel/470413 Latest sata/ide disk protection patch for 2.6.19-rc6]
**[http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch Latest sata/ide disk protection patch for 2.6.18.3]
**[http://exitzero.de/t41p-configs/hdaps_protect-2.6.17.1-20060625.patch Untested patch for 2.6.17.1]: see [http://thread.gmane.org/gmane.linux.drivers.hdaps.devel/708/focus=708]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/03-hdaps_protect-20060430-for-2.6.17-tj.patch Latest sata/ide disk protection patch for use with the libata hotplug 2.6.17.4 patches] - See [[How_to_hotswap_UltraBay_devices]]
**[http://whoopie.gmxhome.de/linux/patches/2.6.16-tj/05-hdaps_protect-20060430-for-2.6.16-tj.patch Latest sata/ide disk protection patch for use with the libata hotplug 2.6.16.16 patches] - See [[How_to_hotswap_UltraBay_devices]]
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060430.patch Latest sata/ide disk protection patch for 2.6.16]
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060118.patch sata/ide disk protection patch for 2.6.15]
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.15.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.15 ([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.14.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.14 ([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://lwn.net/Articles/154923/ disk park patch] <tt>an experimental patch for parking the disk (Linux 2.6.14 for 2.6.15 see below)</tt>

===== Userspace daemon =====
*[http://www.dresco.co.uk/hdaps/hdapsd-20070524.c Recommended version]
*[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1045 Reduced power version] - reduces timer interrupts, as measured by [[PowerTOP]]. This leads to lower power consumption on [[tickless kernel|tickless kernels]]. Interrupt reduction requires the <tt>hdaps</tt> kernel module from [[tp_smapi]] 0.32 or newer, and a [http://article.gmane.org/gmane.linux.drivers.hdaps.devel/1040 udev rule].
*[ftp://rohrmoser-engineering.de/pub Modified adaptive algorithm version] - uses a different (and potentially better) algorithm for the adaptive sensivity threshold.

===== GUI monitoring =====
*[http://roy.marples.name/node/269 khdapmonitor] KDE System Tray Monitor
*[http://www.dresco.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz gnome-hdaps-applet] visual display of disk protection status in gnome panel

====Security & safety====
*[[Script for theft alarm using HDAPS]]

====Tilt monitoring====
*[http://www.mulliner.org/collin/gkibm-acpi.php gkhdaps] <tt>a GKrellM applet displaying tilt data</tt>
*[http://rlove.org/log/2005082203.html gnome-tilt] <tt>a gnome applet showing tilt data</tt>

====Visualisation of ThinkPad orientation====
*[http://rlove.org/log/2005082401.html hdaps-gl] <tt>a little app animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 hdapsgl-applet] <tt> a GNOME applet animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 wmadhps] <tt>a WindowMaker DockApp animating a 3D-ThinkPad</tt>
*[http://www.cs.cmu.edu/~ecc/gyro.tar.gz OpenGL gyroscope hack] <tt>keeps your display levelled when tilting the ThinkPad</tt>

====Games====
*[http://icculus.org/neverball/ Neverball] is quite fun with HDAPS. (You'll need to have the HDAPS joystick device)
*Turn your ThinkPad into a Jedi Weapon (hey, it [http://isnoop.net/blog/2006/05/20/macsaber-turn-your-mac-into-a-jedi-weapon works for Mac laptops])

====Other====

*[http://blog.micampe.it/articles/2006/06/04/here-comes-the-smackpad smack.py] - switch workspace by smacking your laptop, inspired by the [http://blog.medallia.com/2006/05/smacbook_pro.html SmackBook] (uses EWMH)
**an [http://weblogs.mozillazine.org/gerv/archives/2006/09/stablilised_smackpad.html improved version] adds stabilization (by comparing smacks to previous ones, uses EWMH)
**another [http://pberndt.com/Programme/Linux/pyhdaps/index.html approach] adds stabilization (by requiring a certain type of value deflection, uses xmacroplay)
**[http://www.gnome.org/~fherrera/gtollina.c GTollina] is another smack program for use with compiz (video [http://www.gnome.org/~fherrera/blog/gtollina.html here]).
*[http://blog.odonnell.nu/61.html xmms-smack.py] - move through your xmms playlist by smacking, based on the two smack scripts above.
*[http://www-128.ibm.com/developerworks/linux/library/l-knockage.html?ca=dgr-lnxw02aKnockBasedCommands KnockBasedCommands] - Execute commands by tapping your laptop.
*[http://people.ksp.sk/~mic/?menu=32&file=rotate.py rotate.py] - rotate desktop by turning your laptop

=== Interesting links related to this project ===
* [https://lists.sourceforge.net/lists/listinfo/hdaps-devel HDAPS mailinglist and its archive]
* #hdaps channel on irc.freenode.org
* [https://sourceforge.net/projects/hdaps/ hdaps projects] overview of userspace programs using hdaps
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-HDFIRM IBM ThinkPads hardware drive firmware site]
* [http://www.paul.sladen.org/thinkpad-r31/accelerometer.html http://www.paul.sladen.org/thinkpad-r31/accelerometer/]
* http://bugs.gentoo.org/show_bug.cgi?id=119845 Gentoo ebuild for hdaps driver and daemon including a initscript*
* http://bugs.gentoo.org/show_bug.cgi?id=137345 Gentoo ebuild for gkhdaps gkrell plugin
* http://bugs.gentoo.org/show_bug.cgi?id=137350 Gentoo ebuild for hdaps-gl application
* http://bugs.gentoo.org/show_bug.cgi?id=137351 Gentoo ebuild for gnome hdapsgl-applet
* http://bugs.gentoo.org/show_bug.cgi?id=137352 Gentoo ebuild for gnome tilt application
* http://bugs.gentoo.org/show_bug.cgi?id=137353 Gentoo ebuild for wmhdaps
* [http://lenovoblogs.com/insidethebox/?p=71 Why the ThinkPad accelerometer is only 2D] - explanation by Lenovo

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Drivers]] [[Category:Z61m]]

How to control fan speed

2007-07-11T13:59:28Z

Defiant: /* Automated control scripts */ ibm_acpi to thinkpad_acpi rename

This page discusses methods for controlling the system fan.

==For Linux==
===Using a patched kernel===
{{WARN|This patch is superceded by the patches in [[ibm-acpi]] [[Git]] repository or [http://ibm-acpi.sourceforge.net ibm-acpi.sf.net] releases}}
{{NOTE|Advanced fan control through ibm-acpi has been merged in Linux 2.6.20-rc2 mainline, so users of 2.6.20 won't need to patch their kernels to get the '''fan level''' functionality anymore}}

The [[Patch for controlling fan speed]] provides a convenient interface via {{path|/proc/acpi/ibm/fan}}.

Manual speed control can be done through the [[patch for controlling fan speed]]:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: auto
speed: 4219
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

'''#echo level 2 > /proc/acpi/ibm/fan'''

'''#cat /proc/acpi/ibm/fan'''
status: enabled
level: 2
speed: 3142
commands: enable, disable, level <level>
(<level> is 0-7, auto or disengaged)

===Using a stock kernel===

If you have the [[ibm-acpi]] module loaded with <tt>experimental=1</tt>, you can control the fan without patching the kernel by directly writing to the relevant embedded controller register using {{path|/proc/acpi/ibm/ecdump}}.

For example:

{{cmdroot|echo 0x2F 0x00 > /proc/acpi/ibm/ecdump}} (fan off)

{{cmdroot|echo 0x2F 0x02 > /proc/acpi/ibm/ecdump}} (low speed)

{{cmdroot|echo 0x2F 0x04 > /proc/acpi/ibm/ecdump}} (medium speed)

{{cmdroot|echo 0x2F 0x07 > /proc/acpi/ibm/ecdump}} (maximum speed)

{{cmdroot|echo 0x2F 0x80 > /proc/acpi/ibm/ecdump}} (automatic - default)

{{cmdroot|echo 0x2F 0x40 > /proc/acpi/ibm/ecdump}} (disengaged)

See the specifications below for the meaning of these modes.

===On/off control using stock kernel===

If you only wish to turn the fan on and off (with automatic control when it's on), you can use the following.

When loading [[ibm-acpi]] v0.11 with experimental switch ({{cmdroot|1=modprobe ibm_acpi experimental=1}}), it is possible to read and write the status of fan:

'''#cat /proc/acpi/ibm/fan'''
status: enabled
speed: 3580
commands: enable, disable

'''#echo disable > /proc/acpi/ibm/fan'''

'''cat /proc/acpi/ibm/fan'''
status: disabled
speed: 0
commands: enable, disable

When off, the fan will then '''never''' wake up. It is advised to use an automated control script to reduce the chance of hardware damage.

===Automated control scripts===

An [[ACPI fan control script#Variable speed control scripts|ACPI fan control script]] can be used to override the firmware's fan algorithm with gentler, quieter version. It monitors the laptop's [[thermal sensors]] and sets the fan speed accordingly, according to customizable thresholds. For the default behavior, simply save the [[ACPI fan control script#Variable speed control scripts|script]] as {{path|tp-fancontrol}} and run; note that this script requires you to modprobe the thinkpad_acpi module as "modprobe thinkpad_acpi fan_control=1" 
{{cmdroot|./tp-fancontrol}}

==For Windows==

Shimodax's ThinkPad fan control tool offers similar functionality (see [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com). Source and binaries are available through the [http://sourceforge.net/projects/tp4xfancontrol "Tp4xFanControl"] project on SourceForge.

==Hardware specs==

The following hardware behavior was discovered experimentally by [[User:Thinker|Thinker]] and neither provided by nor confirmed by IBM/Lenovo. The following description may be inaccurate and may vary by model (see list of models above). The terminology probably does not match the one used by IBM/Lenovo engineers.

{{NOTE|Information on other models is included in the [[ibm-acpi]] [[Git]] version.}}

ACPI DSDT register HFSP (8 bits, offset 0x2F in the <tt>EmbeddedController</tt> address space, accessed through the standard EC interface at IO ports 0x62 and 0x66) is read/writable and has the following meaning:

Bits 7 6 5 4 3 2 1 0
---------------
Value 1 0 * * * * * * - automatic
* 1 * * * * * * - disengaged
0 0 N N N N N N - manual (0..63; 0=disable fan, 1=min, ..., 7=max)

Changing modes may not be immediate on all ThinkPads. Later ThinkPad models seem to take at least 5s to start responding to a fan mode change, for example.

After boot, the HFSP register may not reflect the true state of the EC (on some models it reads 0x07 even though the EC is actually in automatic mode).

=== Fan Tachometer ===

The embedded controller registers 0x84 (LSB), 0x85 (MSB) are the main fan tachometer, and report fan speed in RPM in everything since the {{A31}} and maybe a little earlier. Not much is know about the tachometer in earlier models, or even whether they had one or not.

=== Automatic mode ===
In ''automatic'' mode, the embedded controller sets the fan speed automatically according to system temperatures and some unknown algorithm.

Note that the ACPI DSDT may supplement this in some models. The {{X40}}, for example, changes the profile of speeds the automatic mode should use depending on battery status.

=== Manual mode ===

In ''manual'' mode, the fan level is forced to the given value and the EC will auto-regulate the fan to maintain at a (roughly) constant RPM, which is model-dependent. Manual speed levels 8-63 yield the same behavior as level 7, and the the ACPI DSDT uses level 7 for the emergency mode it enters upon critical CPU/GPU temperature, so apparently 7 is the real maximum level.

=== Disengaged (full-speed) mode ===

In ''disengaged'' mode, the embedded controller does not monitor the fan speed. It "disengages" the closed-loop control function that keeps track of fan speed, and uses an open-loop control function that ramps up the fan to its maximum speed (100% duty-cycle). The end speed is not stable, but it is often much faster than the maximum speed manual and automatic modes would set the fan to.

Most newer ThinkPads take quite a while (in excess of one minute) to fully enter disengaged mode. Exiting it is much faster. The {{A31}} acts differently, and switches to disengaged mode as fast as it switches to other modes.

For some reason, the embedded controller may stop updating the tachometer registers while entering or exiting disengaged mode in some ThinkPad firmware versions (hence the EC tachometer registers will not be updated on these models while entering/exiting disengaged mode). Once it arrives at maximum speed, or once it gets back at closed-loop cruise speed, the embedded controller starts updating the tachometer registers again. Later T models such as the {{T43}} have this problem, while the {{A31}} does not.

{{HINT|Apparently the [[Problem with fan noise|pulsing fan noise]] experienced by some users can be cured by repeatedly running 2-4 seconds of manual control followed by 0.5-1 seconds of disengaged mode. The pulse occurs when the the embedded controller computes the fan speed and adjusts the fan voltage adaptively every few seconds (~4.8sec for the ThinkPad T43); the aforementioned mode switching doesn't give it a chance to do so. One of the [[ACPI fan control script#Variable speed control scripts|ACPI fan control scripts]] implements this solution.}}

==Supported models==

The above was successfully tested on the following models:

* ThinkPad {{A31}} (fan levels RPM: 0 = off, 1-2 = ~3280-3380 (!), 3-5 = ~3200, 6-7 = ~3380, "disengaged" = ~4000 (see NOTE above))
* ThinkPad {{R50}} (highest manual level is 3; disengage mode works and reaches much higher RPM)
* ThinkPad {{R50p}} (disengaged mode works at ~5100)
* ThinkPad {{R51}} (fan levels RPM: 0 = off, 1-2 = ~3150, 3-5 = ~3350, 6 = ~3750, disengaged = ~5100)
* ThinkPad {{R51e}} (fan levels RPM: 0 = off, 1-2 = ~3300, 3-5 = ~3800, 6 = ~4150, disengaged = ~5100)
* ThinkPad {{R52}} (fan levels RPM: 0 = off, 1-2 = ~3350, 3-5 = ~3650, 6 = ~4250, disengaged = ~5245)
* ThinkPad {{R60}}
* ThinkPad {{T22}}
* ThinkPad {{T23}} (low speed = ~2200, medium and maximum speed = ~4800; disengaged mode works at ~5800)
* ThinkPad {{T30}}
* ThinkPad {{T40}} (fan levels RPM: 1-2 = ~2950, 3-5 = ~3600, 6-7 = ~4050)
* ThinkPad {{T41}}, {{T41p}} (fan levels RPM: 1-2 = ~2980, 3-5 = ~3500, 6-7 = ~4050; disengaged mode works at ~5100)
* ThinkPad {{T42}}, {{T42p}} (fan levels RPM: 1-2 = ~2900, 3-5 = ~3700, 6-7 = ~4700; disengaged mode works at ~5200)
* ThinkPad {{T43}}, {{T43p}} (fan levels RPM: 1-2 = ~3300, 3-5 = ~4100, 6-7 = ~4700; disengaged mode works at ~6450)
* ThinkPad {{T60}} (fan levels RPM: 1-2 = 3000-3100, 3-5 = ~3600, 6-7 = ~4500; disengaged mode works at ~5500)
* ThinkPad {{X30}} (level 0 = off, low = ~3900, medium = ~4200, maximum = ~4650, disengaged = ~5900)
* ThinkPad {{X31}} (fan levels RPM: 0 = off, 1-2 = ~2850, 3-5 = ~3450, 6 = ~4050, 7 = ~4150; disengaged mode works at ~4975)
* ThinkPad {{X40}}
* ThinkPad {{X41}}
* ThinkPad {{X41T}}
* ThinkPad {{X60}}
* ThinkPad {{Z60t}}, {{Z60m}} (fan levels RPM: 1-2 = ~1700, 3-5 = ~2800, 6-7 = ~3500)
* ThinkPad {{Z61m}}
* Thinkpad {{Z61p}} (fan levels 0-7, auto, disengaged; enable, disable; watchdog (untested))
Probably other models are supported too (please update this page if you confirm this; maintain some ordering too).

==Models using a different interface==

The following models also work, use a different access method which supported (only) via the {{path|/proc/acpi/ibm/fan}} of [[ibm-acpi]]. No need for patching.

* ThinkPad {{600E}}, {{600X}}, {{770E}}, {{770X}} (these use a different fan control interface)

==Unsupported models==

* ThinkPad {{560}} (these models don't have a fan)

Fan control scripts

2007-07-11T13:58:22Z

Defiant: /* Comprehensive <tt>bash</tt> script with fine control over fan speed */ Linux 2.6.22 needs fan_control=1

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page provides several scripts for controlling the ThinkPad's system fan according the its [[thermal sensors]] (overriding the embedded controller), in order to reduce [[problem with fan noise|fan noise]] and decrease [[how to reduce power consumption|power consumption]].

{{WARN|These scripts rely on undocumented hardware features and override nominal hardware behavior. They may thus cause arbitrary damage to your laptop or data. Watch your temperatures!}}
|}

==Variable speed control scripts==
The following scripts sets the fan speed according to the system's [[thermal sensors]]. In addition, they include a hack for preventing the annoying fan pulsing that occurs on some systems. Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.

===Comprehensive <tt>bash</tt> script with fine control over fan speed===
This script works with any recent Linux kernel (2.6.14 and higher). It requires the [[ibm-acpi]] module to be loaded with the <tt>experimental=1</tt> module parameter (e.g., {{cmdroot|1=modprobe ibm_acpi experimental=1}}).

In Linux 2.6.22 and higher you need to pass fan_control=1 to the module thinkpad_acpi (e.g., {{cmdroot|1=modprobe thinkpad_acpi fan_control=1}})

The code lets you define a temperature range for each [[thermal sensors|thermal sensor]]. The script computes the fan level needed by each sensor based on the configured range, and then sets the the actual fan level to the slowest that will satisfy all sensors (plus some hysteresis to avoid fluctiations). It also includes a workaround for the [[Problem with fan noise|pulsing noise]] problem. The scipt provides an (optional) daemon mode and logging to syslog. The method of controlling fan speed is documented [[How to control fan speed|here]].

The system hard disk temperature is monitored as well, using the hard disk's internal sensor. This works only on certain Hitachi disks and requires kernel >= 2.6.19-rc1 or the ide driver, since it uses a [[Thermal Sensors#Hitachi_harddisks_SENSE_CONDITION_temperature_sensor|non-standard method]] for reading the temperature without causing a head unload or spinup.

The code:
* {{CodeRef|tp-fancontrol}}

Current options:

Usage: ./tp-fancontrol [OPTION]...

Available options:
-s N Shift up the min temperature thresholds by N degrees
(positive for quieter, negative for cooler).
Max temperature thresholds are not affected.
-S N Shift up the max temperature thresholds by N degrees
(positive for quieter, negative for cooler). DANGEROUS.
-t Test mode
-q Quiet mode
-d Daemon mode, go into background (implies -q)
-l Log to syslog
-k Kill already-running daemon
-u Tell already-running daemon that the system is being suspended
-p Pid file location for daemon mode
{{WARN|The list of temperature ranges used in this script is much more liberal than the rules used by the embedded controller firmware, and is derived mostly from anecdotal evidence, hunches and wishful thinking. It is also model-specific - see [[thermal sensors]].}}

====init script for the comprehensive script====

This is optional. It assumes that the above <tt>tp-fancontrol</tt> script is saved at {{path|/usr/bin/tp-fancontrol}}.
* Init script: {{CodeRef|tp-fancontrol.init}} (save as {{path|/etc/init.d/tp-fancontrol}})
* Init script (Debian): {{CodeRef|tp-fancontrol.init.debian}} (save as {{path|/etc/init.d/tp-fancontrol}})
* Configuration file for init script: {{CodeRef|tp-fancontrol.conf}} (save as {{path|/etc/tp-fancontrol.conf}})

===Simple <tt>bash</tt> script with fine control over fan speed (requires kernel patch)===
The following is a simpler patch (without extra features like daemon mode and logging). It requires the [[patch for controlling fan speed]] or a recent kernel (>=2.6.19).

{{CodeRef|tp-fancontrol-basic}}

==Fan enable/disable scripts==
The following scripts were written before it was known [[patch for controlling fan speed|how to control the fan speed]], so they only toggle between fan disabled and default (noisy) fan behavior. In some models, they also do not monitor all available [[thermal sensors]].

===<tt>sh</tt> script example===
{{CodeRef|fan-enable-basic}}

===<tt>sh</tt> script with more features===
{{CodeRef|fan-enable-extended}}

===<tt>sh</tt> script with extra safety functionality===
ibm_acpi usually works well. But to rely on it completely, this script provides some extra safety functionality:
# It catches various signals and turns the fan on before it quits.
# It turns off the fan under very strict conditions, leaving it on when unexpected errors occur.

{{CodeRef|fan-enable-safe}}

==Init scripts==

===Init script example===

{{CodeRef|fan-enable.init}}

===Init script example for gentoo===
Assume one of the above control scripts is {{path|/usr/sbin/ibm-fancontrold}}, for gentoo use the following init script in /etc/init.d/ibm-fancontrol.
Copy the script to {{path|/etc/init.d/ibm-fancontrol}}, then do

# rc-update add ibm-fancontrol default

This will add the init script to the default runlevel.

{{CodeRef|ibm-fancontrol.init}}

===Init script example for rh/fedora===
Assume one of the above control scripts is {{path|/sbin/tp-fancontrold}},
copy the script to {{path|/etc/init.d/tp-fancontrol}}, then do

# chkconfig --add tp-fancontrol

This will add the init script to the default runlevel.

{{CodeRef|tp-fancontrol-fc.init}}

You'd have to install also "kernel-module-ibm-acpi" package.

==Other==

===fanctrld===
[http://log.does-not-exist.org/archives/2005/08/13/2043_t_43_fan_control_daemon.html fanctrld] is a daemon (written in C) that controls the Thinkpad's fan. The basic approach is to monitor both temperature and fan speed. The fan is enabled when a certain temperature is exceeded, and disabled when the BIOS slows down the fan below a certain speed.

==Ideas for improvement==
* Use the [[HDAPS]] sensor to automatically lower the temperature thresholds when the laptop is moving. Prolonged movement usually happens when the laptop is on the user's lap (see [[Problem with hot surfaces]] for implications), or when in a moving vehicle where fan noise is typically overshadowed by vehicle noise.
* Use a [http://en.wikipedia.org/wiki/PID_controller PID controller] feedback loop instead of simple thresholds.
* Monitor the UltraBay disk temperature too.

==See also==
* [[How to control fan speed]]
* Shimodax's ThinkPad fan control tool for a Windows offers functionality similar to these scripts; see the [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com.
* Yury Polyanskiy has a [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030697.html kernel patch] for automatic fan control in kernelspace (only enable/disable based on maximum temperature).

[[Category:Scripts]]

Fan control scripts

2007-07-11T13:54:39Z

Defiant: /* Simple <tt>bash</tt> script with fine control over fan speed (requires kernel patch) no patch needed for recent kernels */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page provides several scripts for controlling the ThinkPad's system fan according the its [[thermal sensors]] (overriding the embedded controller), in order to reduce [[problem with fan noise|fan noise]] and decrease [[how to reduce power consumption|power consumption]].

{{WARN|These scripts rely on undocumented hardware features and override nominal hardware behavior. They may thus cause arbitrary damage to your laptop or data. Watch your temperatures!}}
|}

==Variable speed control scripts==
The following scripts sets the fan speed according to the system's [[thermal sensors]]. In addition, they include a hack for preventing the annoying fan pulsing that occurs on some systems. Note that the fan levels, thresholds and anti-pulsing hacks are system-specific, so you may need to adjust them.

===Comprehensive <tt>bash</tt> script with fine control over fan speed===
This script works with any recent Linux kernel (2.6.14 and higher). It requires the [[ibm-acpi]] module to be loaded with the <tt>experimental=1</tt> module parameter (e.g., {{cmdroot|1=modprobe ibm_acpi experimental=1}}).

The code lets you define a temperature range for each [[thermal sensors|thermal sensor]]. The script computes the fan level needed by each sensor based on the configured range, and then sets the the actual fan level to the slowest that will satisfy all sensors (plus some hysteresis to avoid fluctiations). It also includes a workaround for the [[Problem with fan noise|pulsing noise]] problem. The scipt provides an (optional) daemon mode and logging to syslog. The method of controlling fan speed is documented [[How to control fan speed|here]].

The system hard disk temperature is monitored as well, using the hard disk's internal sensor. This works only on certain Hitachi disks and requires kernel >= 2.6.19-rc1 or the ide driver, since it uses a [[Thermal Sensors#Hitachi_harddisks_SENSE_CONDITION_temperature_sensor|non-standard method]] for reading the temperature without causing a head unload or spinup.

The code:
* {{CodeRef|tp-fancontrol}}

Current options:

Usage: ./tp-fancontrol [OPTION]...

Available options:
-s N Shift up the min temperature thresholds by N degrees
(positive for quieter, negative for cooler).
Max temperature thresholds are not affected.
-S N Shift up the max temperature thresholds by N degrees
(positive for quieter, negative for cooler). DANGEROUS.
-t Test mode
-q Quiet mode
-d Daemon mode, go into background (implies -q)
-l Log to syslog
-k Kill already-running daemon
-u Tell already-running daemon that the system is being suspended
-p Pid file location for daemon mode
{{WARN|The list of temperature ranges used in this script is much more liberal than the rules used by the embedded controller firmware, and is derived mostly from anecdotal evidence, hunches and wishful thinking. It is also model-specific - see [[thermal sensors]].}}

====init script for the comprehensive script====

This is optional. It assumes that the above <tt>tp-fancontrol</tt> script is saved at {{path|/usr/bin/tp-fancontrol}}.
* Init script: {{CodeRef|tp-fancontrol.init}} (save as {{path|/etc/init.d/tp-fancontrol}})
* Init script (Debian): {{CodeRef|tp-fancontrol.init.debian}} (save as {{path|/etc/init.d/tp-fancontrol}})
* Configuration file for init script: {{CodeRef|tp-fancontrol.conf}} (save as {{path|/etc/tp-fancontrol.conf}})

===Simple <tt>bash</tt> script with fine control over fan speed (requires kernel patch)===
The following is a simpler patch (without extra features like daemon mode and logging). It requires the [[patch for controlling fan speed]] or a recent kernel (>=2.6.19).

{{CodeRef|tp-fancontrol-basic}}

==Fan enable/disable scripts==
The following scripts were written before it was known [[patch for controlling fan speed|how to control the fan speed]], so they only toggle between fan disabled and default (noisy) fan behavior. In some models, they also do not monitor all available [[thermal sensors]].

===<tt>sh</tt> script example===
{{CodeRef|fan-enable-basic}}

===<tt>sh</tt> script with more features===
{{CodeRef|fan-enable-extended}}

===<tt>sh</tt> script with extra safety functionality===
ibm_acpi usually works well. But to rely on it completely, this script provides some extra safety functionality:
# It catches various signals and turns the fan on before it quits.
# It turns off the fan under very strict conditions, leaving it on when unexpected errors occur.

{{CodeRef|fan-enable-safe}}

==Init scripts==

===Init script example===

{{CodeRef|fan-enable.init}}

===Init script example for gentoo===
Assume one of the above control scripts is {{path|/usr/sbin/ibm-fancontrold}}, for gentoo use the following init script in /etc/init.d/ibm-fancontrol.
Copy the script to {{path|/etc/init.d/ibm-fancontrol}}, then do

# rc-update add ibm-fancontrol default

This will add the init script to the default runlevel.

{{CodeRef|ibm-fancontrol.init}}

===Init script example for rh/fedora===
Assume one of the above control scripts is {{path|/sbin/tp-fancontrold}},
copy the script to {{path|/etc/init.d/tp-fancontrol}}, then do

# chkconfig --add tp-fancontrol

This will add the init script to the default runlevel.

{{CodeRef|tp-fancontrol-fc.init}}

You'd have to install also "kernel-module-ibm-acpi" package.

==Other==

===fanctrld===
[http://log.does-not-exist.org/archives/2005/08/13/2043_t_43_fan_control_daemon.html fanctrld] is a daemon (written in C) that controls the Thinkpad's fan. The basic approach is to monitor both temperature and fan speed. The fan is enabled when a certain temperature is exceeded, and disabled when the BIOS slows down the fan below a certain speed.

==Ideas for improvement==
* Use the [[HDAPS]] sensor to automatically lower the temperature thresholds when the laptop is moving. Prolonged movement usually happens when the laptop is on the user's lap (see [[Problem with hot surfaces]] for implications), or when in a moving vehicle where fan noise is typically overshadowed by vehicle noise.
* Use a [http://en.wikipedia.org/wiki/PID_controller PID controller] feedback loop instead of simple thresholds.
* Monitor the UltraBay disk temperature too.

==See also==
* [[How to control fan speed]]
* Shimodax's ThinkPad fan control tool for a Windows offers functionality similar to these scripts; see the [http://forum.thinkpads.com/viewtopic.php?t=17715 forum discussion] at thinkpads.com.
* Yury Polyanskiy has a [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030697.html kernel patch] for automatic fan control in kernelspace (only enable/disable based on maximum temperature).

[[Category:Scripts]]

Talk:Idle consumptions

2007-04-28T11:02:33Z

Defiant: How to measure?

How did you measure? - I just checked the value after 2 minutes in idle.
Any better ideas? Maybe a script with min/avg/max values over a time period?

[[User:Defiant|Defiant]] 13:02, 28 April 2007 (CEST)

Idle consumptions

2007-04-28T10:57:18Z

Defiant: T43-1871

This page reports the minimal consumptions of Thinkpads when idle. This means, in principle: minimum brightness, CPU and GPU at lowest speed, no wifi, hard drive spun down, no pcmcia cards inserted (see details of each entry).

This kind of information has several uses: comparing one's consumption with other that of other people's setups, knowing which model to use as a gateway/file server, etc.

{| border="1" cellspacing="0" cellpadding="2"

! Model !! OS !! Remarks !! consumption
|----
|{{600E}} PIII/450 || Archlinux 0.8/xfce || || 8W
|----
|{{T41p}}||Ubuntu 7.04|| Undervolted, fglrx, no dri || 8.3W
|----
|{{T43}} (1871)||Debian (Linux 2.6.21, fluxbox)|| DRI, alsa (power_save=1), with usb, no networking || 10.1W (12.0W with HD)
|----
|{{T43}} (2669)||Gentoo (2.6.20-gentoo-r5)|| Undervolted, fglrx (powerstate=1), DRI, no alsa, no usb modules, no networking || 12.7W

HDAPS

2007-04-26T08:10:18Z

Defiant: /* Disk head parking */ 2.6.21

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
=== HDAPS - IBM Active Protection System Linux Driver ===
This is the Linux driver for monitoring the accelerometer known as [[Active Protection System|IBM Active Protection System]].

The driver only enables reading of the acceleration data. It does '''not''' perform [[#Harddisk Protection|automatic disk head parking]]. But there are already some other useful [[#Applications|applications]] for HDAPS, using the {{path|/sys}} interface it provides.

{{WARN|There are two versions of the hdaps driver, one in the Linux kernel mainline, and another provided by [[tp_smapi]]. '''Use of the tp_smapi version of hdaps is strongly recommended by the current hdaps developers.'''}}
|}

=== Features ===
*provides accelerometer values via sysfs
*provides a joystick type input device

=== Project Homepage / Availability ===
*[http://hdaps.sourceforge.net/ Project Homepage]
*The driver is included in the 2.6-mm series of kernels since August, 26th 2005.
*The driver is now in the mainline (2.6.14).
*The [[tp_smapi]] package contains some patches to this driver. These are necessary for some recent models, and recommended for all.

=== Status ===
A driver is included in recent Linux kernels and is actively maintained, but it is very inferior to the driver in tp_smapi.

=== How to install the driver ===
If you are using a version of the Linux kernel < 2.6.14, please upgrade. I struggled long and hard to get the driver working with an old version of the kernel, and it was a mess. I gave up, upgraded my kernel, and one recompile later, HDAPS was working.

For 2.6.18 kernel, T60 users have to edit hdaps_init() in drivers/hwmon/hdaps.c to include a HDAPS_DMI_MATCH_LENOVO("ThinkPad T60") line.

Install the tp_smapi module if you experience problems with hdaps always reading out constant values of (0,0) [http://sourceforge.net/mailarchive/message.php?msg_id=15350314 refer]

=== Harddisk Protection ===
As mentioned above, the hdaps kernel driver is only responsible for reading the accelerometer data and exporting it through the sysfs interface. In order to use this information to protect the disk, some additional steps are required.

See [[How to protect the harddisk through APS]].

=== Input device support ===
The hdaps driver in the lastest kernels (2.6.14 and later?) also exports a joystick type input device, which can be used by games.

=== Applications ===
====Disk head parking====
You will need the kernel patch and userspace daemon. The GUI monitoring is optional.
* Kernel patch (apply using 'patch -p1 -l < hdaps_xx.patch')
**[http://lwn.net/Articles/154923/ disk park patch] <tt>an experimental patch for parking the disk (Linux 2.6.14 for 2.6.15 see below)</tt>
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.14.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.14 *([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://jenster.dyndns.org/files/blk_freeze-01-nodetection-for-2.6.15.patch disk park patch adapted for the t41p model] <tt> kernel 2.6.15 *([http://sourceforge.net/mailarchive/message.php?msg_id=13214288 capability detection disabled], no libata support)</tt>
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060118.patch sata/ide disk protection patch for 2.6.15]
**[http://www.dresco.co.uk/hdaps/hdaps_protect.20060430.patch Latest sata/ide disk protection patch for 2.6.16]
**[http://whoopie.gmxhome.de/linux/patches/2.6.16-tj/05-hdaps_protect-20060430-for-2.6.16-tj.patch Latest sata/ide disk protection patch for use with the libata hotplug 2.6.16.16 patches] - See [[How_to_hotswap_UltraBay_devices]]
**[http://whoopie.gmxhome.de/linux/patches/2.6.17.14-tj/03-hdaps_protect-20060430-for-2.6.17-tj.patch Latest sata/ide disk protection patch for use with the libata hotplug 2.6.17.4 patches] - See [[How_to_hotswap_UltraBay_devices]]
**[http://exitzero.de/t41p-configs/hdaps_protect-2.6.17.1-20060625.patch Untested patch for 2.6.17.1]: see [http://thread.gmane.org/gmane.linux.drivers.hdaps.devel/708/focus=708]
**[http://www.dresco.co.uk/hdaps/hdaps_protect-2.6.18.3-2.patch Latest sata/ide disk protection patch for 2.6.18.3]
**[http://article.gmane.org/gmane.linux.kernel/470413 Latest sata/ide disk protection patch for 2.6.19-rc6]
**[http://article.gmane.org/gmane.linux.drivers.hdaps.devel/993 Latest sata/ide disk protection patch for 2.6.20.x and 2.6.21]
*Userspace daemon
**[http://www.dresco.co.uk/hdaps/hdapsd-20060409.c userspace parking daemon]
**[ftp://rohrmoser-engineering.de/pub/ hdapsd-<date>.c is an improved version of the daemon, which computes an adaptive sensivity threshold]
*GUI monitoring
**[http://roy.marples.name/node/269 khdapmonitor] KDE System Tray Monitor
**[http://www.dresco.co.uk/hdaps/gnome-hdaps-applet-20060120.tar.gz gnome-hdaps-applet] visual display of disk protection status in gnome panel
See [[How to protect the harddisk through APS]] for more information.

====Security & safety====
*[[Script for theft alarm using HDAPS]]

====Tilt monitoring====
*[http://www.mulliner.org/collin/gkibm-acpi.php gkhdaps] <tt>a GKrellM applet displaying tilt data</tt>
*[http://rlove.org/log/2005082203.html gnome-tilt] <tt>a gnome applet showing tilt data</tt>

====Visualisation (of ThinkPad orientation)====
*[http://rlove.org/log/2005082401.html hdaps-gl] <tt>a little app animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 hdapsgl-applet] <tt> a GNOME applet animating a 3D-ThinkPad</tt>
*[https://sourceforge.net/project/showfiles.php?group_id=138242 wmadhps] <tt>a WindowMaker DockApp animating a 3D-ThinkPad</tt>
*[http://www.cs.cmu.edu/~ecc/gyro.tar.gz OpenGL gyroscope hack] <tt>keeps your display levelled when tilting the ThinkPad</tt>

====Games====
*[http://icculus.org/neverball/ Neverball] is quite fun with HDAPS. (You'll need to have the HDAPS joystick device)
*Turn your ThinkPad into a Jedi Weapon (hey, it [http://isnoop.net/blog/2006/05/20/macsaber-turn-your-mac-into-a-jedi-weapon works for Mac laptops])

====Other====

*[http://blog.micampe.it/articles/2006/06/04/here-comes-the-smackpad smack.py] - switch workspace by smacking your laptop, inspired by the [http://blog.medallia.com/2006/05/smacbook_pro.html SmackBook] (uses EWMH)
**an [http://weblogs.mozillazine.org/gerv/archives/2006/09/stablilised_smackpad.html improved version] adds stabilization (by comparing smacks to previous ones, uses EWMH)
**another [http://pberndt.com/Programme/Linux/pyhdaps/index.html approach] adds stabilization (by requiring a certain type of value deflection, uses xmacroplay)
**[http://www.gnome.org/~fherrera/gtollina.c GTollina] is another smack program for use with compiz (video [http://www.gnome.org/~fherrera/blog/gtollina.html here]).
*[http://blog.odonnell.nu/61.html xmms-smack.py] - move through your xmms playlist by smacking, based on the two smack scripts above.
*[http://www-128.ibm.com/developerworks/linux/library/l-knockage.html?ca=dgr-lnxw02aKnockBasedCommands KnockBasedCommands] - Execute commands by tapping your laptop.

=== Interesting links related to this project ===
* [https://lists.sourceforge.net/lists/listinfo/hdaps-devel HDAPS mailinglist and its archive]
* #hdaps channel on irc.freenode.org
* [https://sourceforge.net/projects/hdaps/ hdaps projects] overview of userspace programs using hdaps
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-HDFIRM IBM ThinkPads hardware drive firmware site]
* [http://www.paul.sladen.org/thinkpad-r31/accelerometer.html http://www.paul.sladen.org/thinkpad-r31/accelerometer/]
* http://bugs.gentoo.org/show_bug.cgi?id=119845 Gentoo ebuild for hdaps driver and daemon including a initscript*
* http://bugs.gentoo.org/show_bug.cgi?id=137345 Gentoo ebuild for gkhdaps gkrell plugin
* http://bugs.gentoo.org/show_bug.cgi?id=137350 Gentoo ebuild for hdaps-gl application
* http://bugs.gentoo.org/show_bug.cgi?id=137351 Gentoo ebuild for gnome hdapsgl-applet
* http://bugs.gentoo.org/show_bug.cgi?id=137352 Gentoo ebuild for gnome tilt application
* http://bugs.gentoo.org/show_bug.cgi?id=137353 Gentoo ebuild for wmhdaps

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Drivers]] [[Category:Z61m]]

Template:ThinkWiki News

2007-04-26T08:09:00Z

Defiant: 2.6.21

26.04.2007: Linux 2.6.21 has been released including [http://lwn.net/Articles/223185/ Dynticks and Clockevents]

13.04.2007: New user creation disabled temporarily due to spam bots corrupting pages.

15.03.2007: Please help build the brand new [http://www.vaiowiki.org/ vaiowiki.org]!

21.02.2007: According to an [http://www.michaellarabel.com/index.php?k=blog&i=56 unverified blogpost], a group of people led by Jerome Glisse begun to work on an open-source driver for the R500 series. Those chips are common in newer ThinkPads.

31.12.2006: [[ibm-acpi]] 0.13-20061231 stable release patches for Linux 2.6.18 and 2.6.19 available at the [http://ibm-acpi.sf.net ibm-acpi sourceforge page]

22.12.2006: [[ibm-acpi]] 0.13 merged into Linux 2.6.20-rc2, adding [[How to control fan speed|advanced fan control]]

Intel Graphics Media Accelerator 900

2007-04-19T07:42:57Z

Defiant: /* SVideo port */ Clone Mode doesn't seem to work with TV

__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;">
=== Intel Graphics Media Accelerator 900 ===
This is an Intel video adapter

=== Features ===
* Integrated into the following chipsets:
** [[Intel 910GML]]
** [[Intel 915GM]]
* PCI ID: 8086:2592
* Uses up to 128MB of main memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
This chip is supported by the 'i810' driver as part of the X.Org distribution

For '''DRI-Support''', you may have to install the latest Drivers from [http://dri.freedesktop.org/snapshots/ DRI Snapshot] you need following files: 
''common-<CurrentVersion>-linux.i386.tar.bz2 
i915-<CurrentVersion>-linux.tar.bz2'' 
Extract both in the same Directory and run install.sh 
After that restart your X-Server and enjoy OpenGL-Support ;-)



At least on a T43, you also want to add acpi_sleep=s3_bios to the kernel command line (edit your LILO or GRUB configuration file to do that), in order to make sure that Xorg continues to work after a suspend/resume cycle.



For those who is using Gentoo with xorg-x11-6.8.2 and can't get i810 driver working: you can emerge xorg-x11-6.9.0 (unmask it first) and everything will work out of the box (tested with kernel 2.6.15-gentoo-r1).



'''Warning:''' Debian users, do not install the DRI Snapshot, it will overwrite several files in several packages and cause you all manner of grief. (not if you build whole Xorg release, for example 6.9.0 which includes DRI and then install it to '/usr/local' - which is the default location if you install with 'make install') If you're using Stable with xorg from sarge-backports (at backports.org), you can install all the required files from that repository, Etch (Testing/Unstable) users can install from the Testing/Unstable repositories at debian.org



'''Debian success story''':It is wise to choose relatively fresh kernel version (2.6.17.13 works for sure). It will contain driver module '''i915'''. For DRI to work there should be 4 kernel modules: agpgart, intel_agp, drm and i915. There also must be fresh xorg graphic driver (i810). Xorg 6.9.0 is fresh enough (in older version, namely XFree 4.3 everything compiles with no problems, but after starting X enviroment screen gets black although you can hear sounds). While building Xorg don't 'make install', use checkinstall instead: 'checkinstall --showinstall=yes -D "make install"'. Detailed instructions for setting up and troubleshooting DRI can be found at: [http://dri.freedesktop.org/wiki/DriTroubleshooting http://dri.freedesktop.org/wiki/DriTroubleshooting] and [http://dri.sourceforge.net/doc/DRIuserguide.html http://dri.sourceforge.net/doc/DRIuserguide.html]. Remember to set bus mastering. To check whether DRI is running use 'glxinfo'.


=== Linux Intel driver ===
You can find Linux drivers for this card on [http://www.intel.com/support/graphics/linux/index.htm Intel's site]. The site offers much information about how to install this card on many distributions, mainly Red Hat and SuSe. The "Intel" driver above is just a snapshot of the Xorg/XFree86 driver.

The display now (Fedora Core 5 - xorg-x11-server-Xorg-1.0.1-9.fc5.1.1) works perfectly using X.Org driver. All you need to do is change xorg.conf frequencies in the monitor section like this:

HorizSync 31.5-90
VertRefresh 50-90

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

==== External VGA port ====
Works well in clone mode at least. Dualhead is supported.

/etc/X11/xorg.conf
Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Option "Clone" "true"
EndSection

Now you can enable|disable vga out with i810switch crt on|off

Now you can turn on/off the TV-Out by executing the commands
:{{cmdroot|echo "crt_enable" > /proc/acpi/ibm/video}}
or
:{{cmdroot|echo "crt_disable" > /proc/acpi/ibm/video}}
Or toggle between them with
:{{cmdroot|echo "video_switch" > /proc/acpi/ibm/video}}

==== SVideo port ====
See above, but use
Option "MonitorLayout" "TV"

This will only use the TV. At least on a T43 clone mode doesn't work with TV so you should setup a special Server Layout for TV.
Switching to PAL mode is [https://bugs.freedesktop.org/show_bug.cgi?id=2782 not yet supported].

Example setup:
Section "Device"
Identifier "IGM 900 TVout"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "TV
EndSection

Section "Monitor"
Identifier "PAL TV"
HorizSync 30-68
VertRefresh 50-120
Mode "720x576"
DotClock 42.601
HTimings 720 760 832 944
VTimings 576 577 580 602
Flags "-HSync" "-VSync"
EndMode
EndSection

Section "Screen"
Identifier "TV Screen"
Device "IGM 900 TVout"
Monitor "PAL TV"
DefaultDepth 24
DefaultFbbpp 32
Subsection "Display"
Depth 24
FbBpp 32
Modes "720x576"
EndSubsection
EndSection

Put the next Section below all other Layouts, else it will become the default!
Section "ServerLayout"
Identifier "TV"
Screen "TV Screen"
InputDevice "Generic Keyboard" # edit these lines to your needs
InputDevice "IBM Trackpoint"
InputDevice "Synaptics Touchpad"
EndSection

You can now use the TV on tty8 by executing
:{{cmdroot|startx :1 -- -layout TV}}

{{HINT|If you want to use all 3 Displays together, try "CRT+TV,LFP" as value for MonitorLayout.}}


==== Problems with high resolution video playback ====
If you get this error, because you eg try to play HDTV on 1024x768
X11 error: BadAlloc (insufficient resources for operation)
try the following option:
Option "LinearAlloc" "6144"

==== Setting up two screens ====
If you have an external monitor, and you want to use both your internal LCD display and your external monitor, you'll have to make some changes in the default /etc/X11/xorg.conf. With the changes below, your X uses both monitors, and you can move your mouse pointer from one screen to the other, let some of your applications run on one screen, and the other applications run on the other. Unfortunately, you can't move the application from one screen to the other. If someone knows how to achieve that, I would appreciate a posting here.

Step 1: Define two devices.

Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Screen 0
EndSection

Section "Device"
Identifier "Intel Corporation Intel Default Card External"
Driver "i810"
BusID "PCI:0:2:0"
Option "Display" "CRT"
Option "MonitorLayout" "CRT,LFP"
Screen 1
EndSection

Step 2: Define two monitors. The first one is your external monitor and the second one is your internal LCD. '''You must adapt the values for HorizSync, VertRefresh and the Display Size for your external monitor!''' The examples below work for a Samsung Samtron 94B.

Section "Monitor"
Identifier "External Monitor"
HorizSync 30-81
VertRefresh 56-75
DisplaySize 372 301
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 31.5-90
VertRefresh 50-90
Option "DPMS"
EndSection

Step 3: Define two screens. '''Again, check the values for the second screen, they must fit to your external monitor!'''

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Intel Default Card"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "External Screen"
Device "Intel Corporation Intel Default Card External"
Monitor "External Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Step 4: Define the server layout. Define the position of your internal LCD screen (my X41 is LeftOf my external screen)

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "External Screen"
Screen 1 "Default Screen" LeftOf "External Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection

{{HINT|Of course you must have a proper Section "Files", a Section "Modules", a Section "InputDevice" with Identifier "Generic Keyboard", a Section "InputDevice" with Identifier "Configured Mouse", a Section "InputDevice" with Identifier "Generic Mouse" before you define the devices, and a Section "DRI" after the ServerLayout definition. }}

==== DVI port ====
DVI could theoretically be supported if a TMDS transmitter where hooked up to one of the pipes, which is NOT the case on any ThinkPad.

=== Linux kernel Framebuffer driver ===
This chip will work with either the 'vesa' or 'intelfb' driver as part of any recent 2.4 or 2.6 kernel.

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{X41}}, {{X41T}}
* {{Z60m}}, {{Z60t}}

[[Category:Components]]

Intel Graphics Media Accelerator 900

2007-04-19T06:49:50Z

Defiant: clone mode

__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;">
=== Intel Graphics Media Accelerator 900 ===
This is an Intel video adapter

=== Features ===
* Integrated into the following chipsets:
** [[Intel 910GML]]
** [[Intel 915GM]]
* PCI ID: 8086:2592
* Uses up to 128MB of main memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
This chip is supported by the 'i810' driver as part of the X.Org distribution

For '''DRI-Support''', you may have to install the latest Drivers from [http://dri.freedesktop.org/snapshots/ DRI Snapshot] you need following files: 
''common-<CurrentVersion>-linux.i386.tar.bz2 
i915-<CurrentVersion>-linux.tar.bz2'' 
Extract both in the same Directory and run install.sh 
After that restart your X-Server and enjoy OpenGL-Support ;-)



At least on a T43, you also want to add acpi_sleep=s3_bios to the kernel command line (edit your LILO or GRUB configuration file to do that), in order to make sure that Xorg continues to work after a suspend/resume cycle.



For those who is using Gentoo with xorg-x11-6.8.2 and can't get i810 driver working: you can emerge xorg-x11-6.9.0 (unmask it first) and everything will work out of the box (tested with kernel 2.6.15-gentoo-r1).



'''Warning:''' Debian users, do not install the DRI Snapshot, it will overwrite several files in several packages and cause you all manner of grief. (not if you build whole Xorg release, for example 6.9.0 which includes DRI and then install it to '/usr/local' - which is the default location if you install with 'make install') If you're using Stable with xorg from sarge-backports (at backports.org), you can install all the required files from that repository, Etch (Testing/Unstable) users can install from the Testing/Unstable repositories at debian.org



'''Debian success story''':It is wise to choose relatively fresh kernel version (2.6.17.13 works for sure). It will contain driver module '''i915'''. For DRI to work there should be 4 kernel modules: agpgart, intel_agp, drm and i915. There also must be fresh xorg graphic driver (i810). Xorg 6.9.0 is fresh enough (in older version, namely XFree 4.3 everything compiles with no problems, but after starting X enviroment screen gets black although you can hear sounds). While building Xorg don't 'make install', use checkinstall instead: 'checkinstall --showinstall=yes -D "make install"'. Detailed instructions for setting up and troubleshooting DRI can be found at: [http://dri.freedesktop.org/wiki/DriTroubleshooting http://dri.freedesktop.org/wiki/DriTroubleshooting] and [http://dri.sourceforge.net/doc/DRIuserguide.html http://dri.sourceforge.net/doc/DRIuserguide.html]. Remember to set bus mastering. To check whether DRI is running use 'glxinfo'.


=== Linux Intel driver ===
You can find Linux drivers for this card on [http://www.intel.com/support/graphics/linux/index.htm Intel's site]. The site offers much information about how to install this card on many distributions, mainly Red Hat and SuSe. The "Intel" driver above is just a snapshot of the Xorg/XFree86 driver.

The display now (Fedora Core 5 - xorg-x11-server-Xorg-1.0.1-9.fc5.1.1) works perfectly using X.Org driver. All you need to do is change xorg.conf frequencies in the monitor section like this:

HorizSync 31.5-90
VertRefresh 50-90

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

==== External VGA port ====
Works well in clone mode at least. Dualhead is supported.

/etc/X11/xorg.conf
Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Option "Clone" "true"
EndSection

Now you can enable|disable vga out with i810switch crt on|off

Now you can turn on/off the TV-Out by executing the commands
:{{cmdroot|echo "crt_enable" > /proc/acpi/ibm/video}}
or
:{{cmdroot|echo "crt_disable" > /proc/acpi/ibm/video}}
Or toggle between them with
:{{cmdroot|echo "video_switch" > /proc/acpi/ibm/video}}

==== SVideo port ====
See above, but use
Option "MonitorLayout" "TV,LFP"

This is known to work on a T43.
{{HINT|Of course you can also use all 3, that makes "CRT+TV,LFP".}}


==== Problems with high resolution video playback ====
If you get this error, because you eg try to play HDTV on 1024x768
X11 error: BadAlloc (insufficient resources for operation)
try the following option:
Option "LinearAlloc" "6144"

==== Setting up two screens ====
If you have an external monitor, and you want to use both your internal LCD display and your external monitor, you'll have to make some changes in the default /etc/X11/xorg.conf. With the changes below, your X uses both monitors, and you can move your mouse pointer from one screen to the other, let some of your applications run on one screen, and the other applications run on the other. Unfortunately, you can't move the application from one screen to the other. If someone knows how to achieve that, I would appreciate a posting here.

Step 1: Define two devices.

Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Screen 0
EndSection

Section "Device"
Identifier "Intel Corporation Intel Default Card External"
Driver "i810"
BusID "PCI:0:2:0"
Option "Display" "CRT"
Option "MonitorLayout" "CRT,LFP"
Screen 1
EndSection

Step 2: Define two monitors. The first one is your external monitor and the second one is your internal LCD. '''You must adapt the values for HorizSync, VertRefresh and the Display Size for your external monitor!''' The examples below work for a Samsung Samtron 94B.

Section "Monitor"
Identifier "External Monitor"
HorizSync 30-81
VertRefresh 56-75
DisplaySize 372 301
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 31.5-90
VertRefresh 50-90
Option "DPMS"
EndSection

Step 3: Define two screens. '''Again, check the values for the second screen, they must fit to your external monitor!'''

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Intel Default Card"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "External Screen"
Device "Intel Corporation Intel Default Card External"
Monitor "External Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Step 4: Define the server layout. Define the position of your internal LCD screen (my X41 is LeftOf my external screen)

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "External Screen"
Screen 1 "Default Screen" LeftOf "External Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection

{{HINT|Of course you must have a proper Section "Files", a Section "Modules", a Section "InputDevice" with Identifier "Generic Keyboard", a Section "InputDevice" with Identifier "Configured Mouse", a Section "InputDevice" with Identifier "Generic Mouse" before you define the devices, and a Section "DRI" after the ServerLayout definition. }}

==== DVI port ====
DVI could theoretically be supported if a TMDS transmitter where hooked up to one of the pipes, which is NOT the case on any ThinkPad.

=== Linux kernel Framebuffer driver ===
This chip will work with either the 'vesa' or 'intelfb' driver as part of any recent 2.4 or 2.6 kernel.

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{X41}}, {{X41T}}
* {{Z60m}}, {{Z60t}}

[[Category:Components]]

Category:Code

2007-04-12T09:30:02Z

Defiant: Undo corruption

Pieces of textual sourcecode (shell scripts, Perl scripts, C programs, patches etc.) of non-trivial length should be placed in dedicated articles called <tt>Code/''foo''</tt>.

The article page (<tt>Code/''foo''</tt>) itself should contain only the raw source file, '''without any Wiki markup'''.

The article's discussion page (<tt>Talk:Code/''foo''</tt>) should use the <tt>CodeHeader</tt> template to provide the file's metadata. Follow this example:

<div style="background-color: #E0E0E0">
<tt><nowiki>{{</nowiki>CodeHeader|</tt> 
<tt>|filename=foo</tt>  (''filename this should be saved as, preferably the same as the <tt>foo</tt> in <tt>Code/foo</tt>'') 
<tt>|context=<nowiki>[[</nowiki></tt>''primary page were code is introduced''<tt><nowiki>]]</nowiki></tt> 
<tt>|author=<nowiki>[[</nowiki>User:</tt>''Yourself''<tt>|</tt>''Yourself''<tt>]]</tt> 
<tt>|license=GPL v2 or higher, or GFDL v1.2 or higher </tt>'' (preferably keep both. ThinkWiki default license is GFDL v1.2)'' 
<tt><nowiki>}}</nowiki></tt>
</div>

See the pages in this categories for examples.

When referencing the code, always use this template:

<div style="background-color: #E0E0E0">
<tt><nowiki>{{CodeRef|</nowiki>''foo''<nowiki>}}</nowiki></tt>
</div>

2378-RTU

2007-04-12T09:29:15Z

Defiant: Undo corruption

= IBM ThinkPad T42 2378-RTU Specifications =

Official IBM/Lenovo link: http://www-307.ibm.com/pc/support/site.wss/quickPath.do?quickPathEntry=2378rtu&sitestyle=lenovo

== CPU and Memory ==
{|
|Processor Manufacturer || Intel
|-
|Processor Class || (Pentium M Dothan)
|-
|Processor Name || Intel Pentium M 735
|-
|Processor Speed || 1.7 GHz
|-
|Installed Memory || 256 MB
|-
|Maximum Memory || 2 GB
|-
|Memory Technology || DDR 333 SDRAM
|-
|Cache Size || 2 MB
|}
== Storage ==
{|
|Hard Drive Model || HTS726060M9AT00
|-
|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 Radeon MOBILITY 9600
|-
|Graphics Memory || 64 MB
|-
|Included Video Card || Graphics card - AGP 4x (unsure)
|-
|Resolution || 1400 x 1050 pixels
|-
|Max. External Resolution || 2048 x 1536 pixels
|}

== Battery ==
Battery is chosen at order time and not shipped installed. Both 9-cell and 6-cell varieties exist.
{|
|Battery Model || 6 cell
|-
|Battery Life || 4.5 hour(s)
|-
|Battery Type || Lithium ion
|}

== Communications and Networking ==
{|
|Bluetooth || No
|-
|Modem Speed || 56 Kbps
|-
|Network LAN || Intel PRO/1000 MT (uses e1000 driver)
|-
|Network WLAN || Intel PRO/Wireless 2200BG MiniPCI card (uses [[ipw2200]] driver)
|}

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

== 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 Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
|-
|Weight || around 4 or 5 pounds (not measured yet)
|-
|Also known as || ...
|-
|Manufacturer Part No. || 2378RTU
|-
|Dimension || 1.2 in x 12.2 in x 10.9 in (HxWxD) (approximate; not measured yet)
|}

[[Category:T42]]

Installing Kubuntu 6.10 on a ThinkPad X60

2007-04-12T04:54:32Z

Defiant: Undo corruption

[[Image:Kubuntu_logo.png||right]]
[[Image:ThinkPadX60.jpg||right]]

= Installation of Kubuntu 6.10 on a ThinkPad X60s (model 1709-K3U) =

'''Series:''' {{X60}}

'''Model:''' [[1709-K3U]] ([http://www-307.ibm.com/pc/support/site.wss/product.do?template=/product.do?template=%2Fproductpage%2Flandingpages%2FproductPageLandingPage.vm&sitestyle=lenovo&brandind=10&familyind=290550&machineind=295859&modelind=334762&partnumberind=0&subcategoryind=0&doctypeind=8&doccategoryind=0&operatingsystemind=52305&validate=true IBM support page])

'''Operating system:''' [[:Category:Kubuntu|Kubuntu 6.10 Edgy Eft, Desktop Edition]]

== Summary ==

=== What works after installation ===

* Detection of both CPU cores ([[Intel Core 2 Duo]])
* [[How to make use of Dynamic Frequency Scaling|CPU frequency scaling]]
* Graphics detection and acceleration ([[Intel Graphics Media Accelerator 950]])
** Beryl/AIGLX works after installing with [http://www.biodesign.com.ar/blog/?p=23 this guide].
* Audio support ([[AD1981HD]])
* Gigabit ethernet ([[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]])
* [[SD Card slot|Integrated SD card reader]]
* IBM ThinkPad ACPI Extras driver ([[ibm-acpi]])
* [[USB Port|USB 2.0]] ports
* [[TrackPoint]] detection
** See [[How to configure the TrackPoint]]

=== What needs to be fixed ===

* [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter|Intel PRO/Wireless 3945ABG]] '''([[#Intel PRO/Wireless 3945ABG|Fixed]])'''
* Suspend to RAM / Sleep -> seems to work when putting sata into "compatibility" mode in the bios.
* Suspend to HDD / Hibernate
* [[Intel Graphics Media Accelerator 950#External VGA port|External VGA port]] '''([[#External VGA port|Partially fixed]])'''
* Hard drive protection ([[Active Protection System|IBM Active Protection System]]) '''([[#Hard drive protection|Partially fixed]])'''

=== What has not yet been tested ===

* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[CardBus slot|CardBus slot (Type 2)]]
* Firewire (IEEE1394) port
* Modem
* [[IrDA|Infrared port]]
* Special keys

==== Not included with this model ====
* [[How to setup Bluetooth|Bluetooth]]
* [[Integrated Fingerprint Reader]]

=== Annoyances ===

* Battery life

== Installation ==

{{Todo|no cd-rom issue, methods, document my own}}

== Fixes after installation ==

=== Intel PRO/Wireless 3945ABG ===

Ubuntu Guide now covers this issue:
[http://ubuntuguide.org/wiki/Ubuntu_Edgy#How_to_get_ipw3945_and_wep.2Fwpa_to_work ''How to get ipw3945 and wep/wpa to work'']

=== External VGA port ===

Ubuntu's auto-configured [http://www.die.net/doc/linux/man/man5/xorg.conf.5.html {{path|xorg.conf}}] doesn't use the X60's external VGA port by default. This means that either another configuration utility must be used, or {{path|xorg.conf}} must be edited by hand. So far I haven't had any luck with Kubuntu's ''System Settings'' utility, so here I'm looking at direct changes to {{path|xorg.conf}}.

==== Auto-configured xorg.conf for reference ====

This only activates the X60's LCD, and does not use the external VGA port.

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
FontPath "/usr/share/fonts/X11/misc"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizScrollDelta" "0"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "Intel Corporation Mobile Integrated Graphics Controller"
Driver "i810"
BusID "PCI:0:2:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile Integrated Graphics Controller"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"uses
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

Section "DRI"
Mode 0666
EndSection

==== Cloned display ====

{{Todo|description, xorg.conf example}}

==== Extended workspace ====

{{Todo|description of issue}}

=== Hard drive protection ===

{{Todo|working detection, issue of protection}}

[[Category:X60]]
[[Category:Kubuntu]]

Code/tp-fancontrol.init

2007-04-12T04:53:44Z

Defiant: Undo corruption

#! /bin/sh
### BEGIN INIT INFO
# Provides: tp-fancontrol
# Default-Start: 2 3 4 5
# Default-Stop: S 0 1 6
### END INIT INFO
# Copyright (c) 2006 Ronald Aigner <ra3@os.inf.tu-dresden.de>

set -e

DAEMON=/usr/bin/tp-fancontrol
NAME=tp-fancontrol
DAEMONUSER=root
PIDDIR=/var/run
PIDFILE=$PIDDIR/tp-fancontrol.pid
DESC="Thinkpad CPU fan control"

test -x $DAEMON || exit 0

# source config file; edit that file to configure this script
TEMP_SHIFT=0
LOG_SYSLOG=1
QUIET=1
if [ -e /etc/tp-fancontrol.conf ]; then
. /etc/tp-fancontrol.conf
fi

start_it()
{
PARAMS=-d
if [ -e $PIDFILE ]; then
echo "$DESC already running. Stop first."
exit 1
fi
if [ "$TEMP_SHIFT" != "0" ]; then
PARAMS=$PARAMS" -s $TEMP_SHIFT"
fi
if [ "$LOG_SYSLOG" = "1" ]; then
PARAMS=$PARAMS" -l"
else
if [ "$QUIET" = "1" ]; then
PARAMS=$PARAMS" -q"
fi
fi
PARAMS=$PARAMS" -p $PIDFILE"

echo -n "Starting $DESC: $NAME ... "
$DAEMON $PARAMS
if [ "$?" = "0" ]; then
echo "Success."
else
echo "Error while starting: $?"
fi
}

stop_it()
{
if [ -e $PIDFILE ]; then
echo -n "Stopping $DESC ... "
$DAEMON -k
if [ "$?" = "0" ]; then
echo "Success."
else
echo "Error while stopping: $?"
fi
else
echo "$DESC not running."
fi
}

restart_it()
{
if [ -e $PIDFILE ]; then
stop_it
sleep 2
fi
start_it
}

case "$1" in
start)
start_it
;;
stop)
stop_it
;;
reload|force-reload|restart)
restart_it
;;
*)
echo "Usage: /etc/init.d/$NAME {start|stop|reload|restart|force-reload}" >&2
exit 1
;;
esac

exit 0

Hitachi Travelstar 5K100

2007-04-12T04:53:39Z

Defiant: Undo corruption

__TOC__

This is a family of 5400RPM 2.5" hard disks manufactured by Hitachi. They are available in various sizes, and in both PATA (ATA-6) and SATA interfaces. Only the ATA-6 disks were shipped with ThinkPads though.

{| border="1" cellspacing="0" cellpadding="2" width="50%"
|+PATA (ATA-6) interface models:
! Model !! Size
|-
|HTS541010G9AT00 || 100GB
|-
|HTS541080G9AT00 || 80GB
|-
|HTS541060G9AT00 || 60GB
|-
|HTS541040G9AT00 || 40GB
|-
|HTS541030G9AT00 || 30GB
|-
|HTS541020G9AT00 || 20GB
|}

{| border="1" cellspacing="0" cellpadding="2" width="50%"
|+SATA-I interface models:
! Model !! Size
|-
|HTS541010G9SA00 || 100GB
|-
|HTS541080G9SA00 || 80GB
|-
|HTS541060G9SA00 || 60GB
|-
|HTS541040G9SA00 || 40GB
|-
|HTS541030G9SA00 || 30GB
|-
|HTS541020G9SA00 || 20GB
|}

==Documentation==

* [http://www.hitachigst.com/hdd/support/5k100/5k100_ov.htm Overview]
* [http://www.hitachigst.com/hdd/support/5k100/5k100.htm General specifications]
* [http://www.hitachigst.com/tech/techlib.nsf/techdocs/98F75D1B2B25C42F86256EBC0065A2F9/$file/T5K100_sp.pdf Detailed specifications (ATA-6 models)]
* [http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_5K100 Technical documents]

==Models shipped with this disk==
* {{T43}}, {{T43p}}
* ThinkPad {{R52}}
* Thinkpad {{Z61m}}

==Firmware==

On some ThinkPad models, you must buy the IBM-branded version of this drive, since the Hitachi-branded version has an incompatible and unupgradable firmware (see [[Problem with non-ThinkPad hard disks]]).

==See also==
* [[Harddisk Drives]]

User:Ajbarr

2007-04-12T04:53:36Z

Defiant: Undo corruption

=Who I Am & Why you should care=

My name is Andrew Barr and I maintain the following ThinkPad bits for Debian/Ubuntu:

* [http://www.oakcourt.dyndns.org/projects/khdapsmon khdapsmon] -- KDE system tray applet that I wrote to replicate the basic functionality of the Windows HDAPS monitor.

I can be reached at username andrew.james.barr on Google's Gmail if something is wrong with one of the things listed above.

=Latest News=

===2006.04.16===

Happy Easter! at my ThinkPad Debian repository, there are a few new packages:

* gnome-hdaps-applet -- GNOME equivilant of my khdapsmon.
* kernel-patch-tpsmapi
* tpsmapi-utils -- init script for tp_smapi.

Also the hdapsd daemon has a new version.

===2007.01.19===

Please don't use my Debian repo any more. Most of the software there is terribly out of date and now Apache returns '410 Gone' for that URI.

2662-MQG

2007-04-12T04:53:32Z

Defiant: Undo corruption

= IBM ThinkPad X24 2662-MQG Specifications =

== CPU, Chipset and Memory ==
{|
|Processor Manufacturer || Intel
|-
|Processor Class || Intel Mobile Pentium III-M
|-
|Processor Speed || 1133 MHz
|-
|Cache Size || 512 kB
|-
|Chipset || Intel 830MP, ICH3-M
|-
|Installed Memory || 128 MB (soldered on board)
|-
|Maximum Memory || 640 MB (128 M on board, 512 M in the SO-DIMM slot)
|-
|Memory Technology || single channel PC133 SDR-SDRAM

|}

== Storage ==
{|
|Hard Drive Model || IBM Travelstar 40GN IC25N030ATCS04-0, 4200 rpm 2.5" Ultra-ATA/100
|-
|Hard Drive Capacity || 30 GB
|-
|Included Drives || optional in UltraBase X2: 3.5" FDD, LG HL-DT-STDVD-ROM GDR8081N DVD-ROM/DVD-RAM reader
|}

== Display and Graphics ==
{|
|Display Size || 12.1 inch
|-
|Display Type || TFT active matrix
|-
|Display Resolution || 1024 x 768 pixels
|-
|Max. External Resolution || 2048 x 1536 pixels
|-
|Graphics Processor || ATI MOBILITY Radeon M6 (AGP 4x)
|-
|Video Memory || 8 MB
|}

== Battery ==
{|
|Battery Model || 6 cell
|-
|Battery Life || 3.0 hour(s)
|-
|Battery Type || Lithium ion
|}

== Communications and Networking ==
{|
|Bluetooth || No
|-
|Modem Speed || V.90 LT Winmodem 56k 0449144F
|-
|Network LAN || Intel Pro/100 VE (EDC in CDC slot) 10Base-T/100Base-TX Ethernet
|-
|Network WLAN || No
|}

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

== Connectors ==
{|
|Audio || 1 x microphone - input - mini-phone mono 3.5 mm , 1 x audio - line-out/headphones - mini-phone stereo 3.5 mm, 1 x audio - line-in - mini-phone stereo 3.5 mm
|-
|Modem || 1 x modem - phone line - RJ-11
|-
|Network || 1 x network - Ethernet 10Base-T/100Base-TX - RJ-45
|-
|PC Card || 1 x CardBus slot Type II
|-
|USB || 2 x USB - 4 pin USB Type A
|-
|Video || 1 x VGA - 15 pin HD D-Sub (HD-15)
|-
|CF-Card || 1 x Compact Flash Card Reader
|-
|IR || 1 x infrared - IrDA
|-
|UltraPort || 1x IBM UltraPort (integrated proprietary USB 1.1)
|-
|via optional UltraBase X2 || Serial Port (DB9-M), Parallel Port (DB25-F), Combined PS/2 Port Mouse + Keyboard
|}

== General Product Info ==
{|
|Input Devices || Keyboard, TrackPoint
|-
|Included Sound Card || Intel 82801CAM (ICH3-M) AC'97 Audio Controller
|-
|Weight || 3.6 lbs
|-
|Also known as || ...
|-
|Manufacturer Part No. ||
|-
|Dimension || 1.2 in x 11.0 in x 8.9 in (HxWxD)
|}

[[Category:X24]]

Automatically reduce brightness

2007-04-11T05:01:03Z

Defiant: Undo corruption

== The idea ==
When watching someone working with an iBook I noticed that the brightness automatically faded to the lowest level after a few seconds of inactivity. I think that this is a simple way to save power. I wrote a c-daemon which uses the XScreenSaver extension to check whether the user is active. If he is not, it lowers the brightness to a specific level. When he is active again, the brightness is reset to the previous level.

== Prerequisites ==
A recent kernel with IBM ACPI extensions. (You should have a file called {{path|/proc/acpi/ibm/brightness}})

== Installation ==
# Download the [http://pberndt.com/Programme/Linux/brightd/_download/brightd.tar.bz2 brightness control daemon]
# Unpack it and chdir into the {{path|brightd}} directory
# Call {{cmduser|make}}
# Move the {{path|brightd}} executable into a directory like {{path|/usr/local/bin}}
# Put {{cmduser|brightd -d}} into your {{path|~/.Xsession}} (or another distro-specific startup script)
# Change the permissions of {{path|/proc/acpi/ibm/brightness}} so that your user can write to that file

See the README for more detailled instructions and command line parameters.

== Example installation for Gentoo linux and XFCE4 ==
$ wget -o /dev/null -O brightd.tar.bz2 "http://pberndt.com/Programme/Linux/brightd/_download/brightd.tar.bz2?ct=raw&sub=att"
$ tar xjf brightd.tar.bz2
$ cd brightd/
$ make
gcc -lX11 -lXss -o brightd brightd.c
$ cp brightd /usr/local/bin/
$ cd /etc/xdg/xfce4
$ vi xinitrc
73Gi
/usr/local/bin/brightd -s 5 -w 2 -d
<escape>:x
$ cd /etc/init.d/
$ cat > permissions
start() {
ebegin "Setting permissions on /proc"

chmod g+w /proc/acpi/ibm/brightness
chgrp wheel /proc/acpi/ibm/brightness

eend $?
}
$ chmod a+x permissions
$ rc-update add permissions boot
$ ./permissions start

Done. Restart X to see it working.

Talk:ThinkPad series

2007-04-11T05:00:35Z

Defiant: Undo corruption

The following is the text of the page as we had it for a long time. I changed it, however, copying information found on [[Wikipedia:ThinkPad]], since this makes more sense to me. The information below was outdated anyway and can easily be found on the Lenovo ThinkPad page.

AKW, i think you introduced this page. If we want to keep the information, we should find a new place for it. as far as I'm concerned, we can just put it to {{path|/dev/null}}. ;-)

[[User:Wyrfel|Wyrfel]] 22:10, 23 January 2006 (CET)
----
'''Note: The information on this page is provided by [http://www-132.ibm.com/webapp/wcs/stores/servlet/CategoryDisplay?lang=en_US&catalogId=-840&categoryId=2035724&cgmenbr=1&langId=-1&cgrfnbr=2035724&cntrfnbr=1&storeId=1&cntry=840 IBM/Lenovo] for commercial reasons.

== Thinkpad Z Series ==
Stylish Notebooks for Work and Life
# IntelÂ® CentrinoTM Mobile Technology for outstanding wireless performance (select models)
# Choice of 14" (Z60t) or 15.4" (Z60m) widescreen models
# ATI Discrete Graphics (select models)
# Titanium Special Edition Cover (select models)
# MaxBright Screen Display (select models)
# Travel weight starting at 4.1 lb and less than 1.1" thin
# Integrated Fingerprint Reader for security made simple (select models)
# Integrated ThinkPad 11a/b/g Wi-FiÂ® wireless (select models)
# Airbag-like ThinkVantageTM Active Protection System

== ThinkPad R Series ==
Mainstream performance and features
# IntelÂ® CentrinoTM Mobile Technology for outstanding wireless performance (select models)
# Travel weight starting at 5.8 lb and less than 1" thin
# 14.1' and 15' TFT displays available
# Standard battery life up to 6 hours (select models)
# Airbag-like Active Protection System to help protect your hard drive (select models)
# Integrated 11a/b/g Wi-FiÂ® wireless (select models)
# ThinkPad R50e models with 15' TFT displays available at attractive entry prices
# Built-in data backup and protection

== ThinkPad T Series ==
Perfect balance of performance and portability
# IntelÂ® CentrinoTM Mobile Technology for outstanding wireless performance (select models)
# 14.1' TFT display models with travel weights starting at 4.5 lb and less than 1" thin
# 15' TFT display models with travel weights starting at 5.3 lb and less than 1" thin
# Standard battery life up to 7 hours (select models)
# Airbag-like Active Protection System to help protect your hard drive
# Data backup and protection (requires software download on select models)
# Integrated ThinkPad 11a/b or 11a/b/g Wi-FiÂ® wireless (select models)
# ISV-certified mobile workstation models available

== ThinkPad X Series Tablet ==
Ultimate mobility in a tablet ultraportable
# IntelÂ® CentrinoTM Mobile Technology for outstanding wireless performance (select models)
# Integrated Fingerprint Reader for security made simple (select models)
# Tablet Digitizer Pen for on-screen handwriting
# 180Â° Rotating Screen for improved visibility
# Starting at 3.5 lb and less than 1.14" thin
# Long standard battery life up to 6.3 hours (select models)
# Integrated Intel or ThinkPad 11a/b/g Wi-FiÂ® wireless (select models)
# Airbag-like Active Protection System
# Built-in data backup and protection
# Supports optional ThinkPad X4 Dock for easy expansion

== ThinkPad X Series ==
Ultimate mobility in a versatile ultraportable
# IntelÂ® CentrinoTM Mobile Technology for outstanding wireless performance (select models)
# Starting at 2.7 lb and less than 1" thin
# Long standard battery life up to 7.5 hours (select models)
# Integrated Intel or ThinkPad 11a/b/g Wi-FiÂ® wireless (select models)
# Airbag-like Active Protection System
# Built-in data backup and protection
# Supports optional ThinkPad UltraBase for easy expansion

== ThinkPad G Series ==
Powerful desktop replacements
# Select models are available with IntelÂ® PentiumÂ® 4 Processors with Hyperthreading Technology
# NVIDIA GeForce FX Go5200 graphics (select models)
# Travel weight starting at 7.7 lb and less than 1" thin
# Up to 15' SXGA+ TFT display
# Ergonomic EasyPivot base and ComfortSlant keyboard
# Built-in data backup and protection
# Integrated ThinkPad 11a/b or 11a/b/g Wi-FiÂ® wireless (select models)
----

Talk:Installing Ubuntu 5.10 on a ThinkPad R50e

2007-04-11T04:59:47Z

Defiant: Undo corruption

== dual head with Xinerama on R50e ==
I managed to have Ubuntu with dual screen & xinerama work properly after a few attempts. However, the solution is not very polished yet and I need to swap my xorg.confs around (with a script) and restart the X server (logout, ctrl-alt-backspace) each time I go from single screen to dual screen or the opposite. Which is why I don't post on the main R50e page.

Here is my dual screen xorg.conf for those interested, used on Dapper 6.06 TLS. I plug the external screen before bootup, this might have an impact on wether it works.

stripped of "Files" and "InputDevice" sections

Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "Device"
Identifier "I855 A"
Driver "i810"
BusID "PCI:0:2:0"
Option "VBERestore" "yes"
# Option "DevicePresence" "yes"
# Option "CheckDevices" "yes"
Option "MonitorLayout" "CRT,LFP"
Option "Clone" "no"
Screen 0
EndSection

Section "Device"
Identifier "I855 B"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Option "Clone" "no"
# Option "UseSSE" "no"
Screen 1
EndSection

Section "Monitor"
Identifier "Lid monitor"
Option "DPMS"
VertRefresh 56.3-60.0
EndSection

Section "Monitor"
Identifier "External monitor"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "I855 B"
Monitor "Lid monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
EndSection

Section "Screen"
Identifier "Secondary Screen"
Device "I855 A"
Monitor "External monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x1024"
EndSubSection
# Option "NoInt10" "true"
EndSection

Section "ServerLayout"
Identifier "Standard"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Synaptics Touchpad"
EndSection

Section "ServerLayout"
Identifier "Multihead"
Screen "Secondary Screen"
Screen "Default Screen" Above "Secondary Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Synaptics Touchpad"
Option "Xinerama" "true"
EndSection

Section "ServerFlags"
Option "DefaultServerLayout" "Multihead"
EndSection

Section "DRI"
Mode 0666
EndSection

Intel Graphics Media Accelerator 900

2007-04-05T11:01:07Z

Defiant:

__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;">
=== Intel Graphics Media Accelerator 900 ===
This is an Intel video adapter

=== Features ===
* Integrated into the following chipsets:
** [[Intel 910GML]]
** [[Intel 915GM]]
* PCI ID: 8086:2592
* Uses up to 128MB of main memory
</div>
|style="vertical-align:top" |
|}

=== Linux X.Org driver ===
This chip is supported by the 'i810' driver as part of the X.Org distribution

For '''DRI-Support''', you may have to install the latest Drivers from [http://dri.freedesktop.org/snapshots/ DRI Snapshot] you need following files: 
''common-<CurrentVersion>-linux.i386.tar.bz2 
i915-<CurrentVersion>-linux.tar.bz2'' 
Extract both in the same Directory and run install.sh 
After that restart your X-Server and enjoy OpenGL-Support ;-)



At least on a T43, you also want to add acpi_sleep=s3_bios to the kernel command line (edit your LILO or GRUB configuration file to do that), in order to make sure that Xorg continues to work after a suspend/resume cycle.



For those who is using Gentoo with xorg-x11-6.8.2 and can't get i810 driver working: you can emerge xorg-x11-6.9.0 (unmask it first) and everything will work out of the box (tested with kernel 2.6.15-gentoo-r1).



'''Warning:''' Debian users, do not install the DRI Snapshot, it will overwrite several files in several packages and cause you all manner of grief. (not if you build whole Xorg release, for example 6.9.0 which includes DRI and then install it to '/usr/local' - which is the default location if you install with 'make install') If you're using Stable with xorg from sarge-backports (at backports.org), you can install all the required files from that repository, Etch (Testing/Unstable) users can install from the Testing/Unstable repositories at debian.org



'''Debian success story''':It is wise to choose relatively fresh kernel version (2.6.17.13 works for sure). It will contain driver module '''i915'''. For DRI to work there should be 4 kernel modules: agpgart, intel_agp, drm and i915. There also must be fresh xorg graphic driver (i810). Xorg 6.9.0 is fresh enough (in older version, namely XFree 4.3 everything compiles with no problems, but after starting X enviroment screen gets black although you can hear sounds). While building Xorg don't 'make install', use checkinstall instead: 'checkinstall --showinstall=yes -D "make install"'. Detailed instructions for setting up and troubleshooting DRI can be found at: [http://dri.freedesktop.org/wiki/DriTroubleshooting http://dri.freedesktop.org/wiki/DriTroubleshooting] and [http://dri.sourceforge.net/doc/DRIuserguide.html http://dri.sourceforge.net/doc/DRIuserguide.html]. Remember to set bus mastering. To check whether DRI is running use 'glxinfo'.


=== Linux Intel driver ===
You can find Linux drivers for this card on [http://www.intel.com/support/graphics/linux/index.htm Intel's site]. The site offers much information about how to install this card on many distributions, mainly Red Hat and SuSe. The "Intel" driver above is just a snapshot of the Xorg/XFree86 driver.

The display now (Fedora Core 5 - xorg-x11-server-Xorg-1.0.1-9.fc5.1.1) works perfectly using X.Org driver. All you need to do is change xorg.conf frequencies in the monitor section like this:

HorizSync 31.5-90
VertRefresh 50-90

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

==== External VGA port ====
Works well in clone mode at least. Dualhead is supported.

/etc/X11/xorg.conf
Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP,CRT+LFP"
Option "Clone" "true"
EndSection

Now you can enable|disable vga out with i810switch crt on|off

==== SVideo port ====
See above, but use
Option "MonitorLayout" "TV,LFP,TV+LFP"

Now you can turn on/off the TV-Out by executing the commands
:{{cmdroot|echo "dvi_enable" > /proc/acpi/ibm/video}}
or
:{{cmdroot|echo "dvi_disable" > /proc/acpi/ibm/video}}
Or toggle between them with
:{{cmdroot|echo "video_switch" > /proc/acpi/ibm/video}}

This is known to work on a T43.
{{HINT|Of course you can also use all 3, that makes "LFP,LFP+CRT,LFP+TV".}}


==== Problems with high resolution video playback ====
If you get this error, because you eg try to play HDTV on 1024x768
X11 error: BadAlloc (insufficient resources for operation)
try the following option:
Option "LinearAlloc" "6144"

==== Setting up two screens ====
If you have an external monitor, and you want to use both your internal LCD display and your external monitor, you'll have to make some changes in the default /etc/X11/xorg.conf. With the changes below, your X uses both monitors, and you can move your mouse pointer from one screen to the other, let some of your applications run on one screen, and the other applications run on the other. Unfortunately, you can't move the application from one screen to the other. If someone knows how to achieve that, I would appreciate a posting here.

Step 1: Define two devices.

Section "Device"
Identifier "Intel Corporation Intel Default Card"
Driver "i810"
BusID "PCI:0:2:0"
Option "MonitorLayout" "CRT,LFP"
Screen 0
EndSection

Section "Device"
Identifier "Intel Corporation Intel Default Card External"
Driver "i810"
BusID "PCI:0:2:0"
Option "Display" "CRT"
Option "MonitorLayout" "CRT,LFP"
Screen 1
EndSection

Step 2: Define two monitors. The first one is your external monitor and the second one is your internal LCD. '''You must adapt the values for HorizSync, VertRefresh and the Display Size for your external monitor!''' The examples below work for a Samsung Samtron 94B.

Section "Monitor"
Identifier "External Monitor"
HorizSync 30-81
VertRefresh 56-75
DisplaySize 372 301
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 31.5-90
VertRefresh 50-90
Option "DPMS"
EndSection

Step 3: Define two screens. '''Again, check the values for the second screen, they must fit to your external monitor!'''

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Intel Default Card"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "External Screen"
Device "Intel Corporation Intel Default Card External"
Monitor "External Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Step 4: Define the server layout. Define the position of your internal LCD screen (my X41 is LeftOf my external screen)

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "External Screen"
Screen 1 "Default Screen" LeftOf "External Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Generic Mouse"
EndSection

{{HINT|Of course you must have a proper Section "Files", a Section "Modules", a Section "InputDevice" with Identifier "Generic Keyboard", a Section "InputDevice" with Identifier "Configured Mouse", a Section "InputDevice" with Identifier "Generic Mouse" before you define the devices, and a Section "DRI" after the ServerLayout definition. }}

==== DVI port ====
DVI could theoretically be supported if a TMDS transmitter where hooked up to one of the pipes, which is NOT the case on any ThinkPad.

=== Linux kernel Framebuffer driver ===
This chip will work with either the 'vesa' or 'intelfb' driver as part of any recent 2.4 or 2.6 kernel.

=== ThinkPads this chip may be found in ===
* {{R52}}
* {{T43}}
* {{X41}}, {{X41T}}
* {{Z60m}}, {{Z60t}}

[[Category:Components]]

Talk:Installation instructions for the ThinkPad 770E

2007-02-25T09:51:17Z

Defiant: reverted to last spam free version

2668-C2U

2007-02-25T09:51:15Z

Defiant: reverted to last spam free version

= IBM ThinkPad T43 2668-C2U Specifications =

== CPU and Memory ==
{|
|Processor Manufacturer || Intel
|-
|Processor Class || (Pentium M Dothan)
|-
|Processor Name || Intel Pentium M 760
|-
|Processor Speed || 2.0 GHz
|-
|Installed Memory || 512 MB
|-
|Maximum Memory || 2 GB
|-
|Memory Technology || DDR2 SDRAM - 533 MHz
|-
|Cache Size || 2 MB
|}
== Storage ==
{|
|Hard Drive Model || Hitachi HTS541080G9AT00
|-
|Hard Drive Capacity || 80 GB
|-
|Included Drives || CD-RW / DVD Combo Drive
|}

== Display and Graphics ==
{|
|Display Size || 14.1 inch
|-
|Display Type || TFT active matrix
|-
|Graphics Processor || ATI MOBILITY RADEON X300
|-
|Graphics Memory || 64 MB
|-
|Included Video Card || Graphics card - PCI Express x16
|-
|Resolution ||1400 x 1050 pixels
|-
|Max. External Resolution || 2048 x 1536 pixels
|}

== Battery ==
{|
|Battery Model || 6 cell
|-
|Battery Life || 4 hour(s)
|-
|Battery Type || Lithium ion
|}

== Communications and Networking ==
{|
|Bluetooth || No
|-
|Modem Speed || 56 Kbps
|-
|Network LAN || Broadcom BCM5751M Gigabit Ethernet
|-
|Network WLAN || Intel PRO/Wireless 2915ABG MiniPCI card
|}

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

== 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 82801FB (ICH6) rev. 03
|-
|Weight || 5,1 lbs
|-
|Also known as || ...
|-
|Manufacturer Part No. || 2668C2U
|-
|Dimension || 1.2 in x 12.2 in x 10 in (HxWxD)
|}

[[Category:T43]]

Talk:TI PCI1410

2007-02-25T09:51:13Z

Defiant: reverted to last spam free version

Talk:Intel 82371EB

2007-02-25T09:51:09Z

Defiant: reverted to last spam free version

Talk:Intel 440ZXM

2007-02-23T06:37:47Z

Defiant: reverted to last spam free version

Category:Suse

2007-02-23T06:37:43Z

Defiant: reverted to last spam free version

ThinkPad

2007-02-23T06:37:39Z

Defiant: reverted to last spam free version

==About the name "ThinkPad"==
Until 1992 IBM used to refer to their products only by numbers. This was true also for the notebooks manufactured until then and the tradition of those numbers has survived in the form of the type-and-model numbers with which every specific IBM product is still referenced much more precisely than by its common name.

Rumor has it that IBM first intended to give the designation "ThinkPad" to their pen based computer 2521, which became the IBM [[:Category:700T | ThinkPad 700T]]. But then they decided to extend the use of the name to their notebook computers and hence the first ThinkPads hitting the market in 1992 were the [[:Category:300 | ThinkPad 300]], [[:Category:700 | ThinkPad 700]], [[:Category:700C | ThinkPad 700C]] and the mentioned TabletPC [[:Category:700T | ThinkPad 700T]].

The ThinkPad name itself was inspired by leather-bound pocket notepads issued to all IBM employees with the corporate motto 'Think' embossed on the cover. The combination of '''Think''' and Note'''Pad''' lead to the name '''ThinkPad'''. IBM's corporate naming team was initially against using the ThinkPad name since all previous IBM computers were referred to by model numbers rather than names. However, the popularity of the ThinkPad brand with the press convinced IBM to retain the name.

[[Category:Models]] [[Category:Glossary]]

How to protect the harddisk through APS

2007-02-03T09:20:25Z

Defiant: /* Getting the files */ Defiant hdapsd package in unstable

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page tells you how to make the [[Active Protection System]] work under Linux to protect your harddrive from damage in case of a notebook drop or other kind of impact while it is running.

Specific instructions for {{Fedora}} can be found [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]].

== How APS works in Linux ==
APS in Linux consists of four components on the software side:
* The [[HDAPS]] driver (included in recent kernels). It exports a sysfs interface providing the acceleration values.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdaps_protect</tt>] disk protection kernel patch, which exports a sysfs interface that enables an ide or sata disk to be protected by a userspace process.
* The [http://www.dresco.co.uk/hdaps/ <tt>hdapsd</tt>] disk protection userspace daemon. It monitors the acceleration values through the HDAPS interface and automatically initiates disk protection through the hdaps_protect interface - given that the movement exceeds a user specified threshold.
* Optional: the [http://roy.marples.name/node/269 khdapsmonitor KDE System Tray applet] or [http://www.oakcourt.dyndns.org/projects/khdapsmon/ <tt>khdapsmon</tt> KDE System Tray applet] or the [http://www.dresco.co.uk/hdaps/ <tt>gnome-hdaps-applet</tt>]. These applets provide a visual indication of the disk protection status and also a graphical interface for adjusting configuration options for <tt>hdapsd</tt>.
|}

==Installation==
As mentioned above, the hdaps kernel driver found in recent kernels is only responsible for reading the accelerometer data and exporting it through the sysfs interface.

In order to use this information to protect the disk, some additional steps are required.

* Download and build the latest hdaps_protect disk protection kernel patches.
* Enable the drivers in the kernel (requires kernel rebuild).
* Download, build and configure the hdapsd userspace daemon.
* Download and build one of the applets to get a real-time representation of the disk protection status.

===Getting the files===
{| border="1" cellspacing="0" cellpadding="2"
! Latest Sources
|
*<tt>hdaps_protect</tt>, <tt>hdapsd</tt> and the <tt>gnome-hdaps-applet</tt>: http://www.dresco.co.uk/hdaps
*<tt>khdapsmon</tt>: http://www.oakcourt.dyndns.org/projects/khdapsmon/
|-
! {{Debian}}
|
*<tt>hdapsd</tt> package: http://packages.debian.org/unstable/misc/hdapsd
|-
! {{Fedora}}
| see instructions [[Installing_Fedora_Core_5_on_a_ThinkPad_X41_Tablet#Harddrive_Active_Protection_System_.28HDAPS.29|here]]
*kernel RPM packages including <tt>hdaps_protect</tt>: http://www.dresco.co.uk/hdaps/
*kernel RPM packages including <tt>hdaps_protect</tt> and [[Software Suspend 2]]: *http://mhensler.de/swsusp/download/yum/development/fc5/ (build 2084_2 and up)
|-
! {{Gentoo}}
|
*<tt>hdapsd</tt> ebuild: http://bugs.gentoo.org/show_bug.cgi?id=119845
*<tt>khdapsmon</tt> ebuild: http://bugs.gentoo.org/show_bug.cgi?id=124175
|}

=== Adding kernel support ===
A kernel patch is required for disk head parking and queue freezing.

==== Manually patching and compiling a kernel ====
As root, do:
:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|patch -p1 < ~/hdaps_protect.20060409.patch}}
:{{cmdroot|make clean}}
:{{cmdroot|make}}
:{{cmdroot|make modules_install}}

=== Installing hdapsd ===
==== Manual compilation from source ====
* Download the <tt>hdapsd</tt> sources (see above)
* Compile using {{cmdroot|gcc -o hdapsd hdapsd-*.c}}
* Run {{cmdroot|./hdapsd -d sda -s 12 -a}} (replace <tt>sda</tt> with your hard disk device; run {{cmdroot|./hdapsd}} without arguments for help)

==== Gentoo ====
{{Gentoo}} users can try the ebuild attached to [http://bugs.gentoo.org/show_bug.cgi?id=119845 gentoo bug 119845].
{{NOTE|1=hdapsd was added to the official portage tree on the 26th June 2006.}}
*Add hdapsd support in your kernel: device drivers -> hardware monitoring -> ... (you need it as a module if you want to use tp_smapi and hdaps, see [[Tp_smapi]])
*Download the ebuild, use same ebuild date as the kernel-patch.
*Make known the portage an extern ebuild path and add the following line to {{path|/etc/make.conf}}:
PORTDIR_OVERLAY="/usr/local/portage/" (or any other location)
*Create directory {{path|/usr/local/portage}} and {{path|/usr/local/portage/app-laptop/}}
*Copy the downloaded ebuild to {{path|/usr/local/portage/app-laptop}} ({{path|/usr/local/portage/app-laptop/hdapsd}} should now exists)
*Make portage known the new ebuild and creat digist with:
:{{cmdroot|ebuild /usr/local/portage/app-laptop/hdapsd/hdapsd-20060326.ebuild digest}}
*Optional: Copy source file to portage distfiles (if no internet connection is available):
:{{cmdroot|cp hdapsd-20060326.c /usr/portage/distfiles}}
*Accept the x86 keyword for this package: {{cmdroot|echo "app-laptop/hdapsd ~x86" >> /etc/portage/package.keywords}}
*Install hdapsd with: {{cmdroot|emerge hdapsd}}.
*Edit {{path|/etc/conf.d/hdapsd}} (change your harddrive if neccessary: mine is sda, and change the value from 5, 5 is to sensitive, 12 is a good value in my opinion).
*start deamon with: {{cmdroot|/etc/init.d/hdapsd start}}
*Optional: add to default runlevel: {{cmdroot|rc-update add hdapsd default, rc-update add hdapsd battery}}
Write an eMail to abartel[Ã¤d]htwm.de, if you want to get my hdapsd-20060326.ebuild and please upload it.

=== Building an applet ===
====hdaps-gl====
*Make sure you have installed hdaps [and loaded] and ?opengl?
*Download <tt>hdaps-gl-0.0.5</tt> from the web.
*Extract files to {{path|/opt/hdaps-gl}}.
*{{cmdroot|make}}
*Start the applet: {{cmdroot|./hdaps-gl}}

====khdapsmon====
This application uses GNU autotools, so building it is the same as any other autotooled program:
*extract the source somewhere and change to that directory,
*run {{cmdroot|./configure && make && make install}}.
See [[#Getting the files|above]] for Debian packages and a Gentoo ebuild.

==Troubleshooting==
See the [[Problem with APS harddisk parking]] page for troubleshooting APS issues.
{{NOTE|1=If you use [[tp_smapi]], remember to include the option <tt>HDAPS=1</tt> when [[Tp_smapi#Installation|installing tp_smapi]]. Also, you might need to build the hdaps driver as module.}}

==Further Information==
*Additonal information and support is available through the [[Mailinglists#HDAPS Developers Mailinglist|hdaps-devel]] mailinglist and its archive.

[[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61m]]

Talk:Installation instructions for the ThinkPad A21m

2007-01-27T13:25:45Z

Defiant: Revert vandalism caused by this number

Installing Ubuntu 6.06 on a ThinkPad T43

2007-01-27T13:25:40Z

Defiant: Revert vandalism caused by this number

Installation Log of {{Ubuntu}} 6.06 on a {{T43}}

__TOC__

==Overview==
Worked right out of the box
* 1400*1050 resolution
* Battery Management
* Ultra Nav (Trackpoint and synaptic touchpad)
* WLAN (Atheros, IBM 11a/b/g Wireless LAN Mini PCI Adapter II)
* Hibernate and Standby
* Fn keys (switch between monitors untested)
* Audio Keys
* ThinkLight

Was easy or required some work
* easy ubuntu (includes skype and some codecs)
* middle key of Ultra Nav (Trackpoint)
* ATI 3D Acceleration (Mobility Radeon X300)
* Xgl / Compiz

Still TODO
* Fingerprint reader
* Forward/Backward keys, Access IBM Key

Untested
* Bluetooth (light indicates working)
* Modem
* IrDA
* TV out, VGA out

Failed / still requires work
* Active Protection System (solved 'out of the box' in edgy)

==Installation==

===Recovery copy of data===

Before installing a new OS you should create a security copy of your old system. As the IBM Rescue and Recovery tool quit with an error message I used the Ubuntu live CD, mounted and cd'ed into my external hard drive and ran the following command:

$ cmduser|sudo dd if=/dev/sda1 | gzip | dd of=./sda1.img

where /dev/sda1 is the device with my windows partition and sda1.img the gzipped security copy.
In case of problems one can now restore lost information using

$ sudo dd if=./sda1.img | gzip -d | dd of=/dev/sda1

After creating the recovery copy we are ready to resize the existing windows partition. This article assumes you want to keep your IBM Rescue and Recovery Partition, shrink in size, but keep your windows partition and create a new partition for Dapper Drake.

===Resizing Partitions===

Probably the best choice is now to boot from the alternate CD (read [http://gawrysiak.org/corvus/?p=4] to know why) and use it to resize the existing NTFS partition. Unfortionately in my case it didn't work. So I booted the Live CD, but gparted and parted refused to resize my Windows, too. If the same happens to you, use the example [http://crashrecovery.org/CrashRecoveryKit/iso/2.4.21/HOWTO.ntfs.html here] to know how to resize it "manually" using ntfsresize and fdisk.

After resizing your windows partition you should reboot window to check everything's in order. It probably will run checkdisk and reboot two times - according to experieces you can read in the web, you should better let windows do that.

===Installation of Ubuntu===

Now it's the time to install Ubuntu. I used the alternate CD for that because I chose to install grub into the Linux partition and not into the Master Boot Record ([http://gawrysiak.org/corvus/?p=4 read why]). The graphical LiveCD installer automatically installs grub to the MBR. If you want to use grub in the MBR read [[Rescue and Recovery]]. There is a description of what you have to do in order to still be able to use the IBM R'n'R partition.

* remember that you're installing GRUB to an '''sda''' mount, not an hda mount like the GRUB installer will prompt you for what you should enter after you tell GRUB not to install in the MBR will be something like this:

/dev/sda3

After the installation is finshed it will reboot your system. Now windows should start. In my case it didn't, but playing around, booting into the R'n'R partition, starting PC Doctor and doing some Diagnostics (no changes) somehow and surprisingly made windows boot again.

To boot you freshly installed Linux you have to reboot the LiveCD one last time. Use

$ sudo dd if=/dev/sda5 of=ubuntu.img bs=512 count=1

to copy the first block of grub into an image file and use e.g. an usb flash drive to transfer it to your newly booted windows. Copy paste the image to C:\ and add the following line to your C:\boot.ini:

C:\ubuntu.img="Ubuntu Dapper Drake"

At the next restart the windows boot manager should now welcome you with the choice to boot windows or ubuntu. Choose ubuntu to (finally ;-) boot your newly installed linux for the first time.

==Configuration==

===Easyubuntu===

[http://easyubuntu.freecontrib.org/ Easyubuntu] is a helpful tool to install Skype, codecs, ATi 3D drivers and further things that can make your live easier.

===Keyboard Layout===

My T43 has a German keyboard layout. Most worked just fine, but some keys (in my case the "at" and the "tilde" among others) just didn't. If the same happens to you, just go to the Gnome System Preferences menu and choose the right layout for your keyboard (probably named after your language and something like eliminate-dead-keys or no-dead-keys)

===3D Acceleration and Xgl/Compiz===

If you have an ATI Radeon X300, use [http://wiki.cchtml.com/index.php/Ubuntu_Dapper_Installation_Guide this explanation] to make your hardware 3d acceleration work.

To test if it works type

$ glxinfo | grep rendering

The answer should be: "direct rendering: Yes". If it says "No", you don't have 3D acceleration.

If you want to install Xgl/Compiz like me, [http://www.compiz.net/viewtopic.php?id=389 here] is a great installation help for ATI cards (use way two.)

If you have another card you might find a good explanation [http://ubuntuforums.org/showthread.php?t=148351 here].

===3D Acceleration using open-source radeon driver and AIGLX/Beryl===
From my experience it was better to use "radeon" driver, the open source one, on top of "drm" driver,
also part of the kernel, instead of fglrx. I get direct rendering and similar performance---maybe fglrx
driver gives 50-100 more fps. The most annoying thing about fglrx driver is that it can cause hard locks
every now and then and your suspend doesn't work properly...believe me I tried the ones that the Thinkwiki
says supposed to work.

$ glxinfo | grep rendering
direct rendering: Yes
OpenGL renderer string: Mesa DRI R300 20060815 TCL

Use the directions in the previous section to install fglrx driver, library. (I just installed them from shell
rather than making them into packages, I found the uninstall script in /usr/share/fglrx to work properly).
FYI, I used the version 8.26.18-x86.

If you don't get rendering use ''LIBGL_DEBUG=verbose glxinfo'' to diagnose the problem. The most common problem
is that xorg looks for DRI library files in ''/usr/X11R6/lib/dri'', which didn't exist for me. A simple way to
solve this is creating a symlink to where those files are located (/usr/lib/dri/):
$ cd /usr/X11R6/lib/
$ ln -s /usr/lib/dri/ .

Open your ''/etc/modules'' file and add these lines and comment 'fglrx' if there is any:
intel-agp
drm
radeon

Also, from my experience, it was better to use '''AIGLX''' than Xgl and '''Beryl''' instead of Compiz
in terms of performance and integration---things like suspend and hibernate. And you can use nice
start/shutdown scripts to disable beryl-manager since it can cause hang when you resume from suspension.
For more information about suspend/resume scripts, [http://ubuntuforums.org/showthread.php?p=1656484 here].
For more information about installing aiglx and beryl, see [http://wiki.beryl-project.org/index.php/Install/Ubuntu/Dapper/AiGLX here]).

ATI X300 is pretty pitiful though...I get around ~570 average FPS when running AIGLX/beryl
$ glxgears
2850 frames in 5.0 seconds = 569.997 FPS
2925 frames in 5.0 seconds = 584.925 FPS
2904 frames in 5.0 seconds = 580.741 FPS
2923 frames in 5.0 seconds = 584.524 FPS...
With metacity (default Gnome window manager) I get around slightly over 1000 FPS
$ glxgears
5073 frames in 5.0 seconds = 1014.423 FPS
5073 frames in 5.0 seconds = 1014.531 FPS
5252 frames in 5.0 seconds = 1049.326 FPS
5803 frames in 5.0 seconds = 1160.502 FPS...

If anyone know how to get rid of the weird warning, I would really appreciate it:
libGL warning: 3D driver claims to not support visual 0x4b
Seems to be a unresolved bug: [https://bugs.freedesktop.org/show_bug.cgi?id=6624 freedesktop]

I added the following options under ati Device section of ''/etc/X11/xorg.conf''
Option "EnablePageFlip" "True"
Option "ColorTiling" "True"
Then after that the performance boosted by quite a bit:
7026 frames in 5.0 seconds = 1405.147 FPS
7058 frames in 5.0 seconds = 1411.493 FPS
7062 frames in 5.0 seconds = 1412.393 FPS...

===Active Protection System===

See end of this chapter if you have ubuntu edgy eft.

The T43 has a great system to protect your hard disk, the Active Protection System APS. [[How to protect the harddisk through APS]] describes how you can use it.

{{WARN|Only follow these instructions if you know what you are doing!}}

If you didn't until now you will have to install make, libc, gcc, ... Best is you use

$ sudo apt-get install build-essentials

Determine your kernel version using

$ uname -a

You should see somthing like

Linux ibm 2.6.15-26-386 #1 PREEMPT Thu Aug 3 02:52:00 UTC 2006 i686 GNU/Linux

Install the kernel sources "linux-source" e.g. using Synaptic.
Download the right kernel patch from [[HDAPS#Applications]] according to your kernel version and system (I chose "sata/ide disk protection patch for 2.6.15")
adapt following steps to your needs:

$ cd /usr/src/
$ sudo su
# bunzip2 linux-source-2.6.15.tar.bz2
# tar -xf linux-source-2.6.15.tar
# cd linux-source-2.6.15
# patch -p1 -l < /home/silvan/hdaps_protect.20060118.patch

You should see several lines with the word "suceeded". If you see many "failed" instead you probably chose the wrong patch for your kernel. You can use the --dry-run option to try it out first. If you get errors in the following steps you should better stop unless you know what you are doing.

# make clean
# make oldconfig # use old config, ask for new items, only
# make clean
# make # takes quite a long time, several minutes
# make modules
# make modules_install

Afterwards use the debian sources mentioned in [[How to protect the harddisk through APS]] to install the user space deamon hdapsd and the gnome applet gnome-hdaps-applet, e.g. using Synaptic.

If this worked for you, you can find some nice applications at [[HDAPS#Applications]] which make use of the APS.

{{HELP|For me unfortunately it didn't work as making the patched kernel failed. Please update ths section if you have different experiences and a better, more detailed working explanation.}}

{{NOTE|After I updated to edgy eft hdaps works without further work: edgy comes with hdaps built in. You can check if it is working by installing hdaps-utils

# sudo apt-get install hdaps-utils

and calling

# hdaps-gl

for a nice 3D show. If it is not, load the kernel module using

# sudo modprobe hdaps

and it should work. But if you want to use hdaps for disk protection, you have to recompile your kernel in edgy, too. Follow this post for an howto:

}}
[http://ubuntuforums.org/showthread.php?t=122863 Howto for edgy]

===Track Point Middle Key Scrolling===

In my case the track point worked out of the box, but the middle mouse button for scrolling did not. [[How to configure the TrackPoint]] explains how to solve this. The steps you need to follow are in section "Using the X server (kernel 2.6.11+)".
However you don't need to follow the steps in "EmulateWheelTimeout temporarily broken (-> fix for Ubuntu Dapper)" as this is fixed already if you have all your packages up-to-date.

Follow the instructions in the sections "Configure firefox for using trackpoint horizontal scrolling" and "Configure Opera for using trackpoint horizontal scrolling" as well, if you are using one of the two browsers.

===Fingerprint Reader===
{{Todo|Needs editing}}
Look at [[How to enable the fingerprint reader]] if you want to use your fingerprint reader.

===Forward / Backward Keys, Access IBM===
{{Todo|Needs editing}}
You'll find more here: [[How to get special keys to work]]

===IrDA===
{{Todo|Needs editing}}
Find information here: [[How to make use of IrDA]]

===VGA out ===
{{Todo|Needs editing}}
I didn't try it, but it looks easy: [http://help.nceas.ucsb.edu/index.php/Enable_vga_out_on_ATI_Thinkpads How to enable VGA out]

==References==
* [http://gawrysiak.org/corvus/?p=4 Dapper Drake on T42]

==External Sources==
* This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)].

Hope this helped somehow :-)
tec

Talk:Installing Fedora Core 6 on a ThinkPad T42

2007-01-27T13:25:36Z

Defiant: Revert vandalism caused by this number

Talk:Backing up the preloaded OS

2007-01-27T13:25:32Z

Defiant: Revert vandalism caused by this number

Maintenance

2007-01-21T10:29:23Z

Defiant: /* External sources updated ibm link */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Battery treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*avoid deep discharges except when resetting fuel gague or reconditioning a battery; partial dis-/recharges are better for the battery lifetime (note: fuel gauge will slowly get inaccurate over time)
*remove battery when on AC (due to heat)
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full, unless you will need its full capacity soon; keep it on the 30%-85% charged range
*keep notebook off while charging due to heat
*fully discharge, then fully charge battery when needed to recalibrate fuel gauge; newer battery pack models require this less often, old ones might need it as often as every 30 cycles
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but '''do not freeze''' them. 10-15C is recommended
|}

===Battery health===
Batteries, especially of the modern Li-Ion type, wear out quicker when they hold a large charge or are subject to higher temperatures (see above).

If you use your laptop at a desk, reduce battery wear by maintaining an appropriate charge level. When possible, remove Li-ion batteries while operating from AC as the notebook gets hot enough inside for that to damage the battery in the long run, even if charging is stopped.

On recent ThinkPads, charging thresholds can be configured in the bundled software. Under Linux, this is supported on recent models by the [[tp_smapi]] driver (and even without <tt>tp_smapi</tt>, if you have a dual-boot setup, you can set the thresholds under Windows and they will be remembered as long as you don't power off your machine with AC disconnected; suspend to RAM is OK). Have a look at [[How to use UltraBay batteries]].

If you have spare Li-ion battery packs, store them at 40% charge in a cool place (15C being a recommended temperature, do not let the batteries freeze). If storing inside a refrigerator, beware of humidity, and be careful with cold spots that can easily freeze the battery if anything goes wrong.

===The problem with 600 series batteries===
ThinkPad 600 power management causes batteries to die before they should. Read more about this on the [[Problem with ThinkPad 600 batteries|associated problem page]].

===Reviving batteries===
Some people experience sudden drops in their batteries capacity.

A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS".
The program is downloadable from IBMs support site as three floppy disk images. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] from the T22 floppy images. For newer ThinkPads there is an official [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-56222 bootable CD image].

===See also===
* [[Battery safety]]

===External sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=PFAN-3QNQJN IBM Support - Extending battery life]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-51038 IBM Support - Battery troubleshooting]
* [http://www.pc.ibm.com/ww/thinkpad/batterylife/ IBM Benchmark]
* [http://batteryuniversity.com Battery University]
* [http://www.batteryuniversity.com/parttwo-34.htm BatteryUniversitys info about prolonging lithium ion batteries]
* [http://www.buchmann.ca/Chap10-page6.asp prolonging lithium ion batteries in Buchmanns Battery FAQ]

==Cleaning the Display==
If you discover markings that look like they originate from the TrackPoint or keyboard, or for information on how to avoid these, look at [[Problem with key and trackpoint markings on the display|this page]].

===External Sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-4A2P54 Lenovo Support - LCD care and cleaning instructions]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-52190 IBM Support - System cleaning instructions]

==Cleaning the Interior==
{{WARN|The following instructions are not appropriate for all ThinkPad models. Please consult the hardware maintenance guide or on-line disassembly instructions for your model.}}
Most ThinkPad models (particularly the A-series and the T-series) tend to accumulate a lot of interior dust which they draw from their ventilation fan. A good dusting every few months is advised. The procedure is as follows.

===ThinkPad T4x series===
See IBM's keyboard removal [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-46515 instructions] and [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-50227 movie].

===ThinkPad T6x series===
See IBM's keyboard removal
[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-62800 instructions] and
[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-63912 movie].

===Other models (which?)===
#Unplug the computer.
#Remove the battery.
#Turn the ThinkPad over and find two to three screws with upraised double-arrows pointing to them.
#Unscrew these screws and set them aside.
#Press the silver area underneath where the battery used to be. The front of the keyboard will pop up.
#Turn the ThinkPad right side up and gently remove the keyboard, pulling it toward you.
#There is one connector between the ThinkPad and the keyboard. Disconnect it, and set the keyboard aside.
#If there is a small black plastic separator under the keyboard, remove it and set it aside.
#The fan should be visible in the upper left. That entire area will likely be dusty. With a can of compressed air (and ''only'' with a can of compressed air), dust that area and the surrounding area.
#Replace the small black plastic separator, then reconnect the keyboard.
#Slide the keyboard back into place, then press down on the Fn and right-arrow keys until it pops into place.
#Replace the keyboard screws and battery.

==Dealing with spilling accidents==
#Don't panic.
#Don't flip or tilt the computer to prevent the liquid from spreading all over the inside of the case.
#Shut down the OS and turn off the power:
##Unplug the computer.
##Remove the battery.
#Tilt the computer so that everything that leaked into the case can flow out the same way.
#Allow the computer to dry before switching it on again.
#For minor accidents this might already be sufficient. For major flooding you should either bring the computer to a dealer who knows how to open and clean it from inside. Or you can read the Hardware Maintenance Manual, open, clean, and dry the computer yourself.

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca (link broken as of 2006-09-18, the article is still available via [http://web.archive.org/web/20050221034011/http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 web.archive.org]).

==Harddisk Backup / Upgrade==
*[[How to copy a Linux installation]]
*[[Harddrive Upgrade|How to upgrade your Thinkpad hard drive]]
*[[How to copy a Windows installation]]
===External Sources===
*[http://gamma.nic.fi/~point/win2copy.htm Guide on copying Windows 2000/XP to another partition]

==Recovering BIOS passwords==
Password recovery procedure for IBM ThinkPads
using R24RF08 and IBMpass

'''1. Introduction.'''

The IBM ThinkPad uses a small eeprom ([[AT24RF08|ATMEL 24RF08]]) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is also stored in this eeprom.
The 24RF08 is not an ordinary eeprom: it features read protection, which the BIOS uses to lock down
access to the eeprom contents. Also, the password is written in a special scan code, which needs to
be translated to ASCII to be of any use.

To recover the password, one can use two different programs: R24RF08 (eeprom reader) and IBMpass
(password revealer) available at [http://www.allservice.ro http://www.allservice.ro]. Diagrams are included in the reader kit.

Models for which R24RF08 and IBMpass are enough to recover the password: 240, 240X, 390E, 390X, 570, 570E,
600e, 600X, 770Z, A20m, A21e, A21m, a22m, A30, A30p, A31, A31p, G40, G41, R30, R31, R32, R40, R50, R51,
Transnote, T20, T21, T22, T23, T30, T40, T40p, T41, T41p, T42, T42p, X20, X21, X22, X23, X24, X30, X31, X40, X41.

ThinkPads featuring TPCA technology (i.e. a [[Tpm|TPM trusted platform module chip]]), especially T4x, X3x, X4x need the W24RF08 eeprom writer program to complete the password recovery procedure, if the passphrase function is enabled in BIOS setup.

Other models such as the 380XD or 600 use 24C01 or 93C46 eeproms, which can be read without special tools.
The method is the same like for the models based on 24RF08, only the software to dump the eeprom is different.

Newer T43/T43p, R52, R60, T60/p, X60 and Z60 ThinkPads can be unlocked using PC8394 programming tools that consist in RPC8394 and WPC8394 (reader and writer for TPM chips). The software is available as well on [http://www.allservice.ro http://www.allservice.ro]. IBMpass 2.0 works for any TP model without exceptions.

'''2. Locating the ATMEL 24RF08 eeprom. Soldering.'''

No need to unsolder the 24RF08 eeprom, just solder 3 wires to SDA, SCL and GND pins of the
eeprom. There are two eeprom layouts (see interface schematics described bellow), corresponding to 8 pin or 14 pin eeproms. Locate the eeprom first according to your model (E.g. T20-23 and T30 have the eeprom underneath TP, and can be accessed by removing the RAM modules cover, no need to dismantle the laptop.) and solder the wires using a soldering iron with a fine tip. Also, you can use 0.15 -0.20 mm enamel coated wires or similar small diameter insulated wires. These wires will be connected later to the interface.
Tip: You can use clips to connect the wires or you can solder on the PCB traces leading to the
eeprom pins. Once again, be careful and double, triple check the soldering if necessary till you are positively sure you have done the right job. In case of applying too much solder, use flux-impregnated copper-braid "desoldering wick" - this works exceptionally well.

'''3. Choose and build the interface.'''

Since version 2.0, R24RF08 and W24RF08 (eeprom writer) are compatible with a wide range of eeprom programmers. By default, both programs set the COM port signals to use direct logic level to access I2C bus. We provide here 2 schematics that are relevant for direct logic signals and for inverse logic signals (simple-i2cprog.pdf and driven-i2cprog.pdf). Also, depending of the interface you build, you can invert the logics for SDA-In, SDA-Out, and SCL COM port signals by some command line parameters described later in this document.
a) The file simple-i2cprog.pdf contains the schematic diagram of a simple interface (known as SIPROG)based on 2 zeners and 2 resistors. This is a classic, easy to build circuit and works with soldered or unsoldered eeproms. The purpose of the 2 zeners is to convert RS232 levels (+/- 5V) to TTL levels, needed by the eeprom. It uses direct logic signals to I2C eeprom and is powered by the COM port. However, this interface works with in-system eeproms but is dependant on COM port current and eeprom bus impedance. R24RF08 works natively with this circuit, no need to change the lines signals with command line parameters. This circuit works pretty well with almost all ThinkPads series.
b) The second interface is described in driven-i2cprog.pdf. The circuit uses MAX 232 as a RS232 to TTL driver and its main purpose is to work with soldered eeproms. The advantage of MAX232 is the TTL outputs that are more reliable and more powerful when work with soldered, in-system eeproms (dependency free from the COM port current). Due of the internal inverters of MAX232 the interface responds to an inverse signal logic level. R24RF08 needs /x, /d, /i switches to be specified in the command line.

What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

Note that the "standard" serial port programmer probably won't work with a USB-Serial adapter, but requires the full nominal voltage of a hardware serial port. [Example: the A22p's serial port works fine here.]

'''4. Dump the EEPROM:'''

Prepare your technician PC by connecting the interface to the COM1 port (donâ€™t connect the wires to eeprom yet). Turn on the ThinkPad and press F1 to enter BIOS Setup. When you are prompted for the password and thereâ€™s no other activity like HDD access or so, connect the wires (GND first!, SDA, SCL) to the corresponding wires from the interface (attached before to COM1) and execute R24RF08:

-for SI-PROG interface (as described in 3.a above):
r24rf08.exe <filename.ext>. where filename.ext is the file where eeprom content will be stored.
Example: r24rf08 mytp.bin

-for MAX232 driven I2C interface (as described in 3.b above):
r24rf08.exe <filename.ext> /x /d /i. where /x /d /i are command line parameters (switches) for this kind of interface.
Example: r24rf08 mytp2.bin /x /d /i

Use exactly the instructed switches to avoid possible damages to your eeprom data!
The file should be created in the same folder. Finally, disconnect the wires (GND last!) and turn off the ThinkPad by pressing on/off switch.

Dump the EEPROM data at least twice, and do a bytewise compare with `cmp`. Both files should be identical, and 1024 bytes long. Otherwise, you probably have a serial port problem.

Note: the r24rf08.exe program automatically sets the serial port parameters. It also works fine with Wine under Linux - provided that a symlink (com1) exists in the .wine/dos_devices directory, and points to the /dev/ttySX for the actual serial port.

'''5. Reveal the password.'''

Now, you have the .bin file but you need to dump in scan code to retrieve the password. IBMpass 2.0 Lite is a free tool that will do the job. Just open the eeprom dump youâ€™ve created before and search for 0x330, 0x340 lines. The password is located on 0x338 (and 0x340 depending on model) in scan code. For 24C01 eeproms the password is located at 0x38, 0x40. If the password won't work for the very first time then your eeprom may use newer IBM scancodes. In this case switch to alternate scan codes to find it. For those who want quick answers the recommended version is IBMpass 1.1. Usage for IBMpass 1.1 (command line only):

ibmpass mytp.bin â€“ use â€œ/aâ€ switch to see in alternate scan code if needed:
ibmpass mytp.bin /a

For some old models like 570 or 770Z you need to execute the eeprom patcher first. This will reset the read protection on the password offset. To do that just execute patcher.exe before the reading operation, without rebooting the laptop:

-for SI-PROG:
patcher.exe , then immediately
r24rf08.exe <filename.ext>

-for Driven-I2C (Max232) you must insert the switches:
patcher.exe /x /d /i, then immediately
r24rf08.exe <filename.ext> /x /d /i

W24RF08, the writer version, has included the complete APP reset operation you donâ€™t need to use patcher.

Moreover, there are a new encrypting algos used with some new security chips (AT97SC3201, AT97SC3203) that are very secured. The password is not in scancode and in some cases not even in the eeprom. To unlock the machine, the dump should suffer some changes and the eeprom must be reprogrammed using W24RF08. This operation works for all IBM TCG/TCPA secured laptops w/o exceptions.

Remember, use 3 wires from the interface and 3 wires from eeprom! Connect them after your
ThinkPad is powered and disconnect them right after you read the content, before you switch off the laptop.

'''6. Password format'''

The thinkpad power-on/supervisor passwords are a maximum of 7 characters, and are NOT case-sensitive. The allowed characters are restricted to A-Z, 0-9, semicolon, _, - (and perhaps a few others).

===External Sources===
* [http://www.allservice.ro R24RF08/W24RF08, PC8394 programming tools & IBMpass author's webpage.]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-59377 IBM Support - Lost or forgotten password]
* [http://www.allservice.ro/forum/viewforum.php?f=12 Full Service of all ThinkPad models including free password recovery]
* [http://sodoityourself.com/hacking-ibm-thinkpad-bios-password/ A tutorial on how to do this]

Pre-Installation steps

2007-01-11T07:54:50Z

Defiant: Revert vandalism caused by this number

==Backup/Rescue CD Set==
The preinstalled WinXP on most modern Thinkpads comes with a software to create rescue discs. It can be found in the "Access IBM" section of the Windows menu. I recommend to create a set of rescue discs before you repartition the drive. When you create the rescue discs, use a CD-R for the first volume (it's only 280 Megs) and then DVD-R. Otherwise you will end up with seven CD-Rs.
Alternatively IBM [[Ordering_Recovery_CDs|offers]] shipment of a pack of rescue disks if you call the support hotline. Or try to create the rescue CDs [[Backing_up_the_preloaded_OS|on your own]].

The copy of Windows that came with your machine cannot be legally transferred to any other machine. Leave the license sticker intact for when the machine is sold, or if you just have to dual boot.

==Resizing your Windows Partition==
If you want to keep your WinXP partition and you do not want to shell out lots of money for PartitionMagic, you can use [http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize.html ntfsresize]. I recommend booting {{Kanotix}} or {{Knoppix}}, getting it online and using the latest version to be found at the ntfsresize link because the CD linuxes tend to come with slightly out-dated versions. Be sure not to forget to resize your Windows partition (e.g. with cfdisk) AFTER having resized ntfs and TAKE CARE not to make the partition smaller than you made the ntfs. If you like it safe and smooth you can also take a look at the program "qtparted" which reportedly takes care of ntfsresize and partition table changing in one go and allows you to adjust partition sizes in a GUI. But I have not tested this software personally.

'''Please be carefull before taking the following steps. I suggest that you should create rescue and product recovery CDs (6 CDS will be required) before going for the following so that if anything goes wrong you can go back to the factory setting using those CDs.'''

==Moving the Recovery partition using a Linux rescue system==
On newer models (i.e. the T43) the preinstalled HDD has two partitions; the first one containing the OS and second one having the rescue files used to boot the machine when {{ibmkey|Access IBM|#495988}} button is pressed before Windows XP takes control of the laptop. One can use his Linux distros boot CD (usually the first CD) to boot into rescue mode and shift the rescue partition from the end of the HDD to somewhere in between leaving required space for Windows. This can be done in following steps:

===Creating a temporary rescue partition===
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the 1st partition ({{path|/dev/sda1}}).
* Create a partion {{path|/dev/sda3}} immediately before the rescue partition ({{path|/dev/sda2}}) with exactly the same number of cylinders as the rescue partition.
* Save the partition table and quit fdisk. Reboot.
{{HINT|To be on the safe side, reboot the machine everytime the partition table is modified and saved using fdisk from linux rescue mode.}}
* rawcopy the contents of {{path|/dev/sda2}} to {{path|/dev/sda3}} with
:{{cmdroot|1=dd if=/dev/sda2 of=/dev/sda3}}

===Creating the rescue partition in its final position===
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the rescue partiton {{path|/dev/sda2}} (we just backed it up to {{path|/dev/sda3}}).
* Create a partion {{path|/dev/sda2}} immediately after the space you want to leave for Windows. Note that this new partition again should have exactly the same number of cylinders as the rescue partition (now {{path|/dev/sda3}}).
* Save the partition table and quit fdisk. Reboot.
* rawcopy the contents of {{path|/dev/sda3}} to the newly created {{path|/dev/sda2}}:
:{{cmdroot|1=dd if=/dev/sda3 of=/dev/sda2}}
* Run {{cmdroot|fdisk /dev/sda}}.
* Delete the temporary rescue partiton {{path|/dev/sda3}} (we just copied it to {{path|/dev/sda2}})
* Save the partition table and quit fdisk.
* Reboot the machine and press {{ibmkey|Access IBM|#495988}} Button to restore the Windows XP from the rescue partition. Windows XP will occupy only the space available before the new rescue partition.

Once Windows XP is recovered follow the standard mechanism for installing Linux in the available free space at the end of the HDD. If you have created Rescue and Product Recovery CDs, then the Rescue Partition also can be deleted at this stage to make more room for your Linux installation.

= Alternative Method: Dual Booting and retaining ThinkVantage Utility =

Note: T60 2913 with 60 GB drive

The key here is to find a bootable CD version of Linux that has the PartEd package on it (preferrably with qtparted also). I used SystemRescueCd (http://www.sysresccd.org/Main_Page). I've read people say to defrag Windows, but according to the PartEd website, the PartEd resize command (http://www.gnu.org/software/parted/manual/parted.html#resize) will take care of all that. Now boot with the SystemRescueCd and when you get the prompt, press F2. This will list available images. I used fb1024, because I wanted to use qtparted (graphical, fb1024 is framebuffer at 1024x768 vs fb800 is framebuffer at 800x600, etc), not parted (commandline).

What I saw was a 3 partition device sda. Only touch the NTFS partition (sda1 on mine, should be on yours if it is factory settings). You do not want to move the VFAT at the end of the device nor touch that little section (sda-1) at the beginning. I resized sda1 (NTFS) down to 20 GB, what you should see is the the New Size + the Free Space After = Old Size of sda1. Click the commit under the file menu to write the changes. That's it.

I then rebooted with Fedora Core 5 disk 1 and used Anaconda and its utilities to partition the free space to be a 20 GB mount point "/", a 512 MB swap, and a 10 GB vfat, these could have been done using qtparted, or pretty much any distro's install. The swap and vfat were shown inside a logical partition. I set up GRUB in the MBR and clicked the GRUB advanced setup checkbox. This allowed me to add entries, in addition to Linux, for GRUB. I added the NTFS (Windows) partition and the VFAT (ThinkVantage partition, not the 10 GB I created, cuz that would be silly).

The results are: on boot, the post screen tells you to press the ThinkVantage button and....it does nothing, but once GRUB starts, press the key GRUB tells you to which shows the boot list, and there you have Linux, Windows, and ThinkVantage. I tried it and I can boot into all 3. When you first boot into Windows, you may get a chkdisk (I did), but it should be fine.

A word of warning. Be careful, I've heard some people say GRUB in the MBR while dual booting WinXP can result in false positives from virus software, but I didn't have that issue. Also, be very careful about the resize of the NTFS partition with qtparted. Any change in the placement of the start of the pre-existing partitions, and all bets are off. I'm just saying this because I don't know what might happen if Windows isn't where it wants to be. Also I think the placement of the ThinkVantage utility on the disk is very important from my reading. However, since pressing the ThinkVantage at POST doesn't do anything, I may have screwed that up, but with GRUB pointing at that VFAT, I can still get to the ThinkVantage utilities, so I'm happy.

[[Category:Windows]]

Talk:2378-R4U

2007-01-11T07:54:47Z

Defiant: Revert vandalism caused by this number

Talk:Installing Ubuntu 6.06 on a ThinkPad T43

2007-01-11T07:54:44Z

Defiant: Revert vandalism caused by this number

Talk:Killme

2007-01-11T07:54:40Z

Defiant: Revert vandalism caused by this number

Talk:ES1946

2007-01-06T12:55:50Z

Defiant: Revert vandalism caused by this number

Maintenance

2007-01-06T12:55:45Z

Defiant: Revert vandalism caused by this number

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Here you can find general hints about keeping your ThinkPad in good shape. Look at your [[:Category:Models|models category page]] for IBMs official maintenance guide for that model.
|}
==Battery treatment==
{| border=1 cellspacing=0 cellpadding=2 style="vertical-align:top;"
|+Battery life expanding guide
|- style="background:#efefef;white-space:nowrap;"
! style="background:#ffdead;" | Battery Type !! NiCd !! NiMH !! Lithium ion
|- style="vertical-align:top;"
! style="background:#ffdead;" | General
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*always do complete discharge/charge cycles
*avoid exposing the battery (or notebook) to excessive heat
|
*avoid deep discharges except when resetting fuel gague or reconditioning a battery; partial dis-/recharges are better for the battery lifetime (note: fuel gauge will slowly get inaccurate over time)
*remove battery when on AC (due to heat)
*avoid exposing the battery (or notebook) to excessive heat
|- style="vertical-align:top;"
! style="background:#ffdead;" | Charging
|
*discharge before charging
|
*discharge before charging
|
*avoid charging if battery is nearly full, unless you will need its full capacity soon; keep it on the 30%-85% charged range
*keep notebook off while charging due to heat
*fully discharge, then fully charge battery when needed to recalibrate fuel gauge; newer battery pack models require this less often, old ones might need it as often as every 30 cycles
|- style="vertical-align:top;"
! style="background:#ffdead;" | Storage
|
*almost discharged
*cool and dry
|
*almost discharged
*cool and dry
|
*never fully charged or discharged, ideally at about 40%
*cool and dry, but '''do not freeze''' them. 10-15C is recommended
|}

===Battery health===
Batteries, especially of the modern Li-Ion type, wear out quicker when they hold a large charge or are subject to higher temperatures (see above).

If you use your laptop at a desk, reduce battery wear by maintaining an appropriate charge level. When possible, remove Li-ion batteries while operating from AC as the notebook gets hot enough inside for that to damage the battery in the long run, even if charging is stopped.

On recent ThinkPads, charging thresholds can be configured in the bundled software. Under Linux, this is supported on recent models by the [[tp_smapi]] driver (and even without <tt>tp_smapi</tt>, if you have a dual-boot setup, you can set the thresholds under Windows and they will be remembered as long as you don't power off your machine with AC disconnected; suspend to RAM is OK). Have a look at [[How to use UltraBay batteries]].

If you have spare Li-ion battery packs, store them at 40% charge in a cool place (15C being a recommended temperature, do not let the batteries freeze). If storing inside a refrigerator, beware of humidity, and be careful with cold spots that can easily freeze the battery if anything goes wrong.

===The problem with 600 series batteries===
ThinkPad 600 power management causes batteries to die before they should. Read more about this on the [[Problem with ThinkPad 600 batteries|associated problem page]].

===Reviving batteries===
Some people experience sudden drops in their batteries capacity.

A way to get these batteries back to full capacity is to run the "Battery Rundown" function of IBMs "PC Doctor for DOS".
The program is downloadable from IBMs support site as three floppy disk images. For those who do not have a floppy, David Smith prepared a [http://www.mypchelp.com/~dsmith/ibmutil/ibm_t22_pcdiag.iso bootable CD image] from the T22 floppy images. For newer ThinkPads there is an official [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-56222 bootable CD image].

===See also===
* [[Battery safety]]

===External sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-50944 IBM Support - Extending battery life]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-51038 IBM Support - Battery troubleshooting]
* [http://www.pc.ibm.com/ww/thinkpad/batterylife/ IBM Benchmark]
* [http://batteryuniversity.com Battery University]
* [http://www.batteryuniversity.com/parttwo-34.htm BatteryUniversitys info about prolonging lithium ion batteries]
* [http://www.buchmann.ca/Chap10-page6.asp prolonging lithium ion batteries in Buchmanns Battery FAQ]

==Cleaning the Display==
If you discover markings that look like they originate from the TrackPoint or keyboard, or for information on how to avoid these, look at [[Problem with key and trackpoint markings on the display|this page]].

===External Sources===
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-4A2P54 Lenovo Support - LCD care and cleaning instructions]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-52190 IBM Support - System cleaning instructions]

==Cleaning the Interior==
{{WARN|The following instructions are not appropriate for all ThinkPad models. Please consult the hardware maintenance guide or on-line disassembly instructions for your model.}}
Most ThinkPad models (particularly the A-series and the T-series) tend to accumulate a lot of interior dust which they draw from their ventilation fan. A good dusting every few months is advised. The procedure is as follows.

===ThinkPad T4x series===
See IBM's keyboard removal [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-46515 instructions] and [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-50227 movie].

===ThinkPad T6x series===
See IBM's keyboard removal
[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-62800 instructions] and
[http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-63912 movie].

===Other models (which?)===
#Unplug the computer.
#Remove the battery.
#Turn the ThinkPad over and find two to three screws with upraised double-arrows pointing to them.
#Unscrew these screws and set them aside.
#Press the silver area underneath where the battery used to be. The front of the keyboard will pop up.
#Turn the ThinkPad right side up and gently remove the keyboard, pulling it toward you.
#There is one connector between the ThinkPad and the keyboard. Disconnect it, and set the keyboard aside.
#If there is a small black plastic separator under the keyboard, remove it and set it aside.
#The fan should be visible in the upper left. That entire area will likely be dusty. With a can of compressed air (and ''only'' with a can of compressed air), dust that area and the surrounding area.
#Replace the small black plastic separator, then reconnect the keyboard.
#Slide the keyboard back into place, then press down on the Fn and right-arrow keys until it pops into place.
#Replace the keyboard screws and battery.

==Dealing with spilling accidents==
#Don't panic.
#Don't flip or tilt the computer to prevent the liquid from spreading all over the inside of the case.
#Shut down the OS and turn off the power:
##Unplug the computer.
##Remove the battery.
#Tilt the computer so that everything that leaked into the case can flow out the same way.
#Allow the computer to dry before switching it on again.
#For minor accidents this might already be sufficient. For major flooding you should either bring the computer to a dealer who knows how to open and clean it from inside. Or you can read the Hardware Maintenance Manual, open, clean, and dry the computer yourself.

See also [http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 Act quickly, carefully if you spill on laptops] on MoneySense.ca (link broken as of 2006-09-18, the article is still available via [http://web.archive.org/web/20050221034011/http://www.moneysense.ca/spending/technology/columnist.jsp?content=986628 web.archive.org]).

==Harddisk Backup / Upgrade==
*[[How to copy a Linux installation]]
*[[Harddrive Upgrade|How to upgrade your Thinkpad hard drive]]
*[[How to copy a Windows installation]]
===External Sources===
*[http://gamma.nic.fi/~point/win2copy.htm Guide on copying Windows 2000/XP to another partition]

==Recovering BIOS passwords==
Password recovery procedure for IBM ThinkPads
using R24RF08 and IBMpass

'''1. Introduction.'''

The IBM ThinkPad uses a small eeprom ([[AT24RF08|ATMEL 24RF08]]) to store different OEM
issues like serial number, UUID, etc. The supervisor password (SVP) is also stored in this eeprom.
The 24RF08 is not an ordinary eeprom: it features read protection, which the BIOS uses to lock down
access to the eeprom contents. Also, the password is written in a special scan code, which needs to
be translated to ASCII to be of any use.

To recover the password, one can use two different programs: R24RF08 (eeprom reader) and IBMpass
(password revealer) available at [http://www.allservice.ro http://www.allservice.ro]. Diagrams are included in the reader kit.

Models for which R24RF08 and IBMpass are enough to recover the password: 240, 240X, 390E, 390X, 570, 570E,
600e, 600X, 770Z, A20m, A21e, A21m, a22m, A30, A30p, A31, A31p, G40, G41, R30, R31, R32, R40, R50, R51,
Transnote, T20, T21, T22, T23, T30, T40, T40p, T41, T41p, T42, T42p, X20, X21, X22, X23, X24, X30, X31, X40, X41.

ThinkPads featuring TPCA technology (i.e. a [[Tpm|TPM trusted platform module chip]]), especially T4x, X3x, X4x need the W24RF08 eeprom writer program to complete the password recovery procedure, if the passphrase function is enabled in BIOS setup.

Other models such as the 380XD or 600 use 24C01 or 93C46 eeproms, which can be read without special tools.
The method is the same like for the models based on 24RF08, only the software to dump the eeprom is different.

Newer T43/T43p, R52, R60, T60/p, X60 and Z60 ThinkPads can be unlocked using PC8394 programming tools that consist in RPC8394 and WPC8394 (reader and writer for TPM chips). The software is available as well on [http://www.allservice.ro http://www.allservice.ro]. IBMpass 2.0 works for any TP model without exceptions.

'''2. Locating the ATMEL 24RF08 eeprom. Soldering.'''

No need to unsolder the 24RF08 eeprom, just solder 3 wires to SDA, SCL and GND pins of the
eeprom. There are two eeprom layouts (see interface schematics described bellow), orresponding to 8 pin or 14 pin eeproms. Locate the eeprom first according to your model (E.g. T20-23 and T30 have the eeprom underneath TP, and can be accessed by removing the RAM modules cover, no need to dismantle the laptop.) and solder the wires using a soldering iron with a fine tip. Also, you can use 0.15 -0.20 mm enamel coated wires or similar small diameter insulated wires. These wires will be connected later to the interface.
Tip: You can use clips to connect the wires or you can solder on the PCB traces leading to the
eeprom pins. Once again, be careful and double, triple check the soldering if necessary till you are positively sure you have done the right job.

'''3. Choose and build the interface.'''

Since version 2.0, R24RF08 and W24RF08(eeprom writer) are compatible with a wide range of eeprom programmers. By default, both programs set the COM port signals to use direct logic level to access I2C bus. We provide here 2 schematics that are relevant for direct logic signals and for inverse logic signals (simple-i2cprog.pdf and driven-i2cprog.pdf). Also, depending of the interface you build, you can invert the logics for SDA-In, SDA-Out, and SCL COM port signals by some command line parameters described later in this document.
a) The file simple-i2cprog.pdf contains the schematic diagram of a simple interface (known as SIPROG)based on 2 zeners and 2 resistors. This is a classic, easy to build circuit and works with soldered or unsoldered eeproms. The purpose of the 2 zeners is to convert RS232 levels (+/- 5V) to TTL levels, needed by the eeprom. It uses direct logic signals to I2C eeprom and is powered by the COM port. However, this interface works with in-system eeproms but is dependant on COM port current and eeprom bus impedance. R24RF08 works natively with this circuit, no need to change the lines signals with command line parameters. This circuit works pretty well with almost all ThinkPads series.
b) The second interface is described in driven-i2cprog.pdf. The circuit uses MAX 232 as a RS232 to TTL driver and its main purpose is to work with soldered eeproms. The advantage of MAX232 is the TTL outputs that are more reliable and more powerful when work with soldered, in-system eeproms (dependency free from the COM port current). Due of the internal inverters of MAX232 the interface responds to an inverse signal logic level. R24RF08 needs /x, /d, /i switches to be specified in the command line.

What these switches mean:
/x - invert serial clock, also known as SCL;
/d - invert serial data output, also known as SDA-Out;
/i - invert serial data input, also known as SDA-In.
All those can be used in any combination to meet any interface specification.

'''4. How is it working:'''

Prepare your technician PC by connecting the interface to the COM1 port (donâ€™t connect the wires to eeprom yet). Turn on the ThinkPad and press F1 to enter BIOS Setup. When you are prompted for the password and thereâ€™s no other activity like HDD access or so, connect the wires (GND first!, SDA, SCL) to the corresponding wires from the interface (attached before to COM1) and execute R24RF08:

-for SI-PROG interface (as described in 3.a above):
r24rf08.exe <filename.ext>. where filename.ext is the file where eeprom content will be stored.
Example: r24rf08 mytp.bin

-for MAX232 driven I2C interface (as described in 3.b above):
r24rf08.exe <filename.ext> /x /d /i. where /x /d /i are command line parameters (switches) for this kind of interface.
Example: r24rf08 mytp2.bin /x /d /i

Use exactly the instructed switches to avoid possible damages to your eeprom data!
The file should be created in the same folder. Finally, disconnect the wires (GND last!) and turn off the ThinkPad by pressing on/off switch.

'''5. Reveal the password.'''

Now, you have the .bin file but you need to dump in scan code to retrieve the password. IBMpass 2.0 Lite is a free tool that will do the job. Just open the eeprom dump youâ€™ve created before and search for 0x330, 0x340 lines. The password is located on 0x338 (and 0x340 depending on model) in scan code. For 24C01 eeproms the password is located at 0x38, 0x40. If the password won't work for the very first time then your eeprom may use newer IBM scancodes. In this case switch to alternate scan codes to find it. For those who want quick answers the recommended version is IBMpass 1.1. Usage for IBMpass 1.1 (command line only):

ibmpass mytp.bin â€“ use â€œ/aâ€ switch to see in alternate scan code if needed:
ibmpass mytp.bin /a

For some old models like 570 or 770Z you need to execute the eeprom patcher first. This will reset the read protection on the password offset. To do that just execute patcher.exe before the reading operation, without rebooting the laptop:

-for SI-PROG:
patcher.exe , then immediately
r24rf08.exe <filename.ext>

-for Driven-I2C (Max232) you must insert the switches:
patcher.exe /x /d /i, then immediately
r24rf08.exe <filename.ext> /x /d /i

W24RF08, the writer version, has included the complete APP reset operation you donâ€™t need to use patcher.

Moreover, there are a new encrypting algos used with some new security chips (AT97SC3201, AT97SC3203) that are very secured. The password is not in scancode and in some cases not even in the eeprom. To unlock the machine, the dump should suffer some changes and the eeprom must be reprogrammed using W24RF08. This operation works for all IBM TCG/TCPA secured laptops w/o exceptions.

Remember, use 3 wires from the interface and 3 wires from eeprom! Connect them after your
ThinkPad is powered and disconnect them right after you read the content, before you switch off the laptop.

===External Sources===
* [http://www.allservice.ro R24RF08/W24RF08, PC8394 programming tools & IBMpass author's webpage.]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=ibm&lndocid=MIGR-59377 IBM Support - Lost or forgotten password]
* [http://www.allservice.ro/forum/viewforum.php?f=12 Full Service of all ThinkPad models including free password recovery]

Talk:Neomagic NMA2

2007-01-06T12:55:41Z

Defiant: Revert vandalism caused by this number

Talk:Links

2007-01-06T12:55:34Z

Defiant: Revert vandalism caused by this number

Talk:Problem with e1000: EEPROM Checksum Is Not Valid

2007-01-06T12:55:30Z

Defiant: Revert vandalism caused by this number

Talk:Tpb

2007-01-06T12:55:26Z

Defiant: Revert vandalism caused by this number

Talk:2647-8AG

2007-01-06T12:55:22Z

Defiant: Revert vandalism caused by this number

Installing Ubuntu 6.10 on a ThinkPad X41 Tablet

2007-01-06T12:55:19Z

Defiant: Revert vandalism caused by this number

This document describes the process of (installing and?) configuring [https://wiki.ubuntu.com/EdgyEft Ubuntu Edgy Eft] (final release expected October 2006) on a Lenovo ThinkPad X41 Tablet. With whatever relevance it may have, the particular model number used in testing was an 1869CSU. Keep in mind that at this document's inception 6.10 is a development version of the Ubuntu Linux OS.

== Success Chart ==

{| border="1" cellpadding="5" cellspacing="0"
|-
|colspan=2| '''Item''' || '''Working'''
|-
|rowspan=2|Installation
| Network Installation ||class="diff-addedline"| Yes
|-
| USB Installation ||class="diff-addedline"| Yes (CD)
|-
|rowspan=4|Display
| Laptop Screen ||class="diff-addedline"| Yes
|-
| CRT / Projector ||class="diff-context"| Unknown
|-
| Screen Rotation ||class="diff-addedline"| Yes
|-
| Stylus ||class="diff-addedline"| Yes
|-
|rowspan=2|Power Management
| Software Suspend (hibernate) ||class="diff-context"| Unknown
|-
| Suspend to Memory (ACPI sleep) ||class="diff-addedline"| Yes
|-
|colspan=2| Audio ||class="diff-addedline"| Yes
|-
|rowspan=2| Wireless || 802.11b/g ||class="diff-addedline"| Yes
|-
| Bluetooth ||class="diff-context"| Unknown
|-
|rowspan=2|Extra Buttons || Keyboard Section ||class="diff-context"| Unknown
|-
| Tablet buttons ||class="diff-context"| Unknown
|-
|colspan=2| Fingerprint Scanner ||class="diff-context"| Unknown
|-
|colspan=2| Harddisk Active Protection ||class="diff-addedline"| Yes
|}

= Pre-Installation Notes =

== Tablet Screen Rotation (updated i810 drivers) ==

This edition of Ubuntu (Edgy) has XRandR enabled i810 drivers, which allow you to rotate your screen orientation on the fly. The command <tt>xrandr -o [orientation]</tt> will rotate your screen to your liking. For more information about the <tt>xrandr</tt> command, refer to the man file (<tt>man xrandr</tt>).

== Wireless Support ==

Wireless seems to be supported flawlessly in terms of drivers, though I'm not sure how well the built-in Network Manager works. I use the <tt>iwconfig</tt> command to manage my wireless, as I have a need to create pseudo-"profiles", and in this document I will describe this alternative process.

== Fingerprint Reader Support ==

Honestly, I care very little about the fingerprint functionality. Its only real use seems to be for gksu-type logins while the tablet is swiveled down, which doesn't occur often in my setup. If someone wants to explore/expound, please do, but I won't include any details about the fingerprint reader in this document.

== Terminology Used ==

For those of you new to Linux, I'll try to detail a few terms I use with little explanation:
* Xorg configuration -- the display configuration file, residing in <tt>/etc/X11/xorg.conf</tt>
* Execute a command -- press Alt-F2, then type <tt>gnome-terminal</tt> into the prompt and press enter -- this is a terminal into which you input said commands

= Installation Notes =

== Booting With NetBOOT ==

To boot over NetBOOT I fisrt went into the BIOS and change the boot settings so that PXE was first on the list. Then I set my desktop to be a DHCP server (dhcp3-server) and configured it using this site [http://wiki.koeln.ccc.de/index.php/Ubuntu_PXE_Install Ubuntu_PXE_Install] and installed tftpd-hpa

Then I downloaded the [http://archive.ubuntu.com/ubuntu/dists/dapper/main/installer-i386/current/images/netboot/netboot.tar.gz Dapper netboot archive] (I tried the testing edgy but it would not run on my X41 as of 9/9/06)

Then I assigned my desktop a static IP in the range I set my DHCP server up for and plugged my laptop into it with a cross over cable and rebooted.

The X41 received an IP and then connected to lftp and the same screen as the Ubuntu netboot CD has came up and I followed the instructions.

Once it was intstalled and up-to-date I ran (leave in all quotes, they are important)

<tt>sudo aptitiude update && sudo aptitude upgrade
gksudo "update-manager -c -d" </tt>

To upgrade to edgy eft

= Post-Installation Notes =

== Configuring Xorg ==

=== TrackPoint ===

Like in all ThinkPad Xorg configurations, add the following under the "Configured Mouse" device to enable TrackPoint scrolling:

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

=== Wacom Stylus ===

First install the wacom drivers with the following command:
sudo apt-get install wacom-kernel-source xserver-xorg-input-wacom wacom-tools

After doing this, I strongly suggest that you reboot your computer; however, if you're one of those people whose uptime is on the order of four years, I'm sure you'll figure out an alternative that I won't be describing here.

Next step is to check to see if <tt>/dev/wacom</tt> exists. A '<tt>ls -al /dev | grep wacom</tt>' should do the trick quite nicely. If it does exist, add the following to your Xorg configuration.

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4"
EndSection

And under the ServerLayout section add:

InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"

Some people seem to have slightly different configurations (potentially due to model differences). At any rate, if you're looking to find what serial device your stylus is, a simple '<tt>dmesg | grep ttyS</tt>' should do the trick. Be sure to append to this article if the procedure varies from model to model.

==== Suspend Fix ====

Every suspend/resume cycle drops the wacom, so create the file <tt>/etc/acpi/resume.d/20-setserial.sh</tt> and add the following (modify settings for your device if necessary):

#!/bin/bash
/bin/setserial /dev/ttyS0 port 0x0200 irq 5 autoconfig

Then, go ahead and run a:

sudo chmod +x /etc/acpi/resume.d/20-setserial.sh

You should be all set to resume with stylus support.

=== ACPI Swivel Events ===

When you swivel your tablet's LCD down or up your computer triggers what's called an ACPI event. This is an event similar to pushing the power or sleep buttons -- it's telling the OS about something that's going on with the hardware.

In Linux, ACPI event handling is bundled into a nice neat little package. First, to make sure you can hear the ACPI event when it happens, run the command '<tt>acpi_listen</tt>'. The command line will hang there until it picks up on an ACPI event that's occuring, and then it will dump it to the screen. After running acpi_listen, while it's hanging there, swivel your screen down, and then back up. You should get a result similar to this:

$ acpi_listen
ibm/hotkey HKEY 00000080 00005009
ibm/hotkey HKEY 00000080 0000500a

The first HKEY entry is your swivel-down-event identifier and the second is your swivel up. If your values differ from those displayed here, be sure to use your values instead.

Next, what we do is create new ACPI handler entries for the specified events, which we operate on in <tt>/etc/acpi/</tt>.

The <tt>/etc/acpi/</tt> folder generally contains shell files to be executed when events occur. Since there's no shell files to handle swivel events yet, we're gonna go ahead and create some. Yeah, that'd be great.

Use your favorite text editor to modify the following files (the file names are the second line with the # symbol).

#!/bin/sh
#/etc/acpi/x41tsdown.sh
echo 'Rotating screen...'
if [ "`/usr/bin/xrandr -o right -v | grep -i 'randr' | wc -l`" -ne "1" ]
then
echo '!! Something went wrong...'
export DISPLAY=":0.0"
export XAUTHORITY=/var/lib/gdm/\:0.Xauth
/bin/xset -display $DISPLAY dpms
echo 'Trying to rotate again...'
/usr/bin/xrandr -o right
fi
echo 'Rotating stylus...'
/usr/bin/xsetwacom set stylus rotate 1
echo 'Starting keyboard...'
/usr/bin/xvkbd&

#!/bin/sh
#/etc/acpi/x41tsup.sh
echo 'Unrotating screen...'
if [ "`/usr/bin/xrandr -o normal -v | grep -i 'randr' | wc -l`" -ne "1" ]
then
echo '!! Something went wrong...'
export DISPLAY=":0.0"
export XAUTHORITY=/var/lib/gdm/\:0.Xauth
/bin/xset -display $DISPLAY dpms
echo 'Trying to unrotate again...'
/usr/bin/xrandr -o normal
fi
echo 'Rotating stylus...'
/usr/bin/xsetwacom set stylus rotate 0
echo 'Killing keyboard...'
killall xvkbd

Then run:

sudo chown root.root /etc/acpi/x41tsdown.sh
sudo chmod 755 /etc/acpi/x41tsdown.sh
sudo chown root.root /etc/acpi/x41tsup.sh
sudo chmod 755 /etc/acpi/x41tsup.sh

If you'd like to edit these scripts with your favorite text editor (which, I realize, is most likely [http://www.gnu.org/fun/jokes/ed.msg.html ed]), it's fairly obvious that they're located in <tt>/etc/acpi/</tt> as <tt>x41tsdown.sh</tt> and <tt>x41tsup.sh</tt>. These commands make the shell scripts that handle the events... once we register the events. Let's do that now.

sudo cat <<EOF > /etc/acpi/events/x41t-swivel-down
# /etc/acpi/events/x41t-swivel-down
# called when tablet head swivels down
event=ibm/hotkey HKEY 00000080 00005009
action=/etc/acpi/x41tsdown.sh
EOF

sudo cat <<EOF > /etc/acpi/events/x41t-swivel-up
# /etc/acpi/events/x41t-swivel-up
# called when tablet head swivels up
event=ibm/hotkey HKEY 00000080 0000500a
action=/etc/acpi/x41tsup.sh
EOF

Now, awaken your inner ACPI daemon with the following commands:

sudo /etc/init.d/acpid force-reload
sudo /etc/init.d/acpid restart

And swivel down your LCD to make sure it works.

CAUTION: Swiveling actions while in one of your tty sessions will kill gdm!!!

To be continued...

=External Sources=
*This guide is listed at the [http://tuxmobil.org/ibm.html TuxMobil Linux laptop and notebook installation survey (IBM/Lenovo)] and the [http://tuxmobil.org/tablet_unix.html Linux on Tablet PCs and webpads survey].