ThinkWiki - User contributions [en]

How to hotswap the UltraBase

2010-03-01T00:46:47Z

AlanHK: /* Usage */

== Introduction ==

Here is how I set up an {{X22}} to allow hot ejection/removal of the UltraBase. See also [[How_to_hotswap_Ultrabay_devices|this related page]] for the Ultrabay. These instructions are well-tested, but ymmv.

===Features===

* Uses <tt>lt_hotswap</tt> to preserve DMA on re-insert
* Idiot-proof (somewhat)
* Scripts also work without <tt>lt_hotswap</tt> (using the older way, <tt>idectl</tt>).
* Makes use of ThinkPad beeps to inform user.

===System===

* X22 ThinkPad + UltraBase + DVD-R
* [[lt_hotswap]] version 0.3.9
* kernel-2.6.17.1
* xorg 6.9.0

==Files==

===rc.local===
First, make sure the lt_hotswap module is loaded. Add this to /etc/rc.local (or use modprobe.preload, if you prefer)
echo "Loading lt_hotswap module"
modprobe lt_hotswap hdc_dock=1

===/etc/acpi/events/lths===

Disable the existing lths script. Here is the modified /etc/acpi/events/lths:
# Call the LTHS script
event=lths.*
#action=/usr/local/sbin/lths.sh %e
action=echo "Not invoking lths.sh; this is now done by the ultrabase_eject and insert scripts instead."

===/etc/acpi/events/ultrabase_eject===

Respond to an ultrabase eject event. Here is /etc/acpi/events/ultrabase_eject
#Ultrabase eject button has been pressed
#We can be triggered by an ibm/bay event if NOT using lt_hotswap, or an lt_hotswap event if we are.
event=ibm/bay.MSTR.00000003.00000000
event=lths.MSTR.00000003.00000000
action=/etc/acpi/actions/ultrabase_eject.sh

===/etc/acpi/events/ultrabase_insert===

Respond to an ultrabase insert event. Here is /etc/acpi/events/ultrabase_insert
#Ultrabase has been re-inserted
#We can be triggered by an ibm/bay event if NOT using lt_hotswap, or an lt_hotswap event if we are.
event=ibm/bay.MSTR.00000001.00000000
event=lths.MSTR.00000001.00000000
action=/etc/acpi/actions/ultrabase_insert.sh

===/etc/acpi/actions/ultrabase_eject.sh===

This is the actual script which does the ejection. It is /etc/acpi/actions/ultrabase_eject.sh
* Note the dependency on '''cddb-id'''.
{{MoveToCode}}

#!/bin/bash
echo "syncing disks for safety"
sync

echo "Unregistering IDE interface for CDROM and preparing to eject."

#Note: the BIOS will already deal with the ultrabay LED (number 3). It will:
# * turn it on when the bay is loaded
# * turn it off when the bay is unloaded
# * blink it when it is waiting between an eject request and an eject. (Linux never takes long enough to see this!)

#What if there is a disk in the drive?
#Case 1: there is an umounted CDROM, or an AudioCD/DVD which is NOT playing.
# => It's OK to proceed.

#Case 2: there is a mounted CDROM.
# => we MUST unmount it, or give up on ejecting.
if grep hdc /proc/mounts >/dev/null; then
echo "There is a mounted filesystem on /dev/hdc. Trying to unmount it"
umount /dev/hdc
if [ $? == 0 ]; then
echo "Successfully unmounted the CDROM."
else
echo "The CDROM is busy; can't unmount. Do not try to undock."
echo 9 > /proc/acpi/ibm/beep #This is an "unhappy, warning beep"
exit 1
fi
fi

#Case 3: there is a AudioCD/DVD which is currently playing.
#How do we detect this? It could be just using cdplay (which has no associated process)
#The following methd is ugly, and it requires the cddb-id program. However, it does work.
#Assuming that we have already ruled out a mounted filesystem, then...
CDDBID=$(cddb-id /dev/hdc 2>/dev/null)
if [ -n "$CDDBID" ]; then
echo "There is a CD in the drive. Ejecting it"
eject /dev/hdc #Buglet: we don't necessarily want to eject the disk; we just want to be sure it has stopped playing.
fi

#We're now OK to proceed.
if /sbin/lsmod | grep lt_hotswap > /dev/null ; then
echo "We are using lt_hotswap"
#Eject the bay using lths.
echo -n "MSTR eject" > /proc/acpi/lths
else
echo "We are not using lt_hotswap. Do it the old way with idectl."
#Unregister IDE interface 1. This WILL cause a kernel panic if there is anything in the drive!
idectl 1 off
#Tell the thinkpad the bay is to be ejected
echo eject > /proc/acpi/ibm/bay
fi

#Beep happily
echo 6 > /proc/acpi/ibm/beep
echo "OK to undock"

===/etc/acpi/actions/ultrabase_insert.sh===

This script is called on insertion. It is /etc/acpi/actions/ultrabase_insert.sh

#!/bin/bash
echo "Ultrabase has been inserted. Re-registering IDE interface for CDROM."

if /sbin/lsmod | grep lt_hotswap > /dev/null ; then
echo "We are using lt_hotswap"
echo "Enabling DMA on /dev/hdc"
hdparm -d 1 -u 1 -c 1 /dev/hdc

#LTHS already beeps; no beep required here.
else
echo "We are not using lt_hotswap. Do it the old way with idectl."

#Register IDE interface 1
idectl 1 rescan
#Turn DMA on again. But this is probably a vain attempt; it will fail unless we are using lt_hotswap.
sleep 2
hdparm -d1 /dev/hdc || echo "WARNING: DMA cannot be re-enabled for hdc after insert. You'll have to reboot for now."

#Beep happily
echo 6 > /proc/acpi/ibm/beep
fi

echo "Redocked successfully"
echo "Note: KDE's volume manager might not work anymore with the CD/DVD drive."

==Debugging==

* The easiest way to check what is happening is:
tail -f /var/log/acpid

* Remember, after modifying anything in /etc/acpi/events, to reload the acpid rules:
killall -HUP acpid

* Note that stdout from all scripts ends up in /var/log/acpid. But to communicate a message with the user, it's best to use either the various thinkpad beeps, or perhaps the thinklight.

* Note: idectl and lt_hotswap '''really''' don't get along together. You will lock the system.

==Usage==

# Save your files; this could (possibly) crash the kernel.
# Press the "Request ejection" button, which is on the front of the ultrabase (located between CD drive and floppy).
# The thinkpad should beep happily (high-low). If so, proceed. Otherwise, if it beeps unhappily (3 very short high beeps), it was unable to unmount a busy filesystem in the optical drive. <br>Note: If you change your mind after the thinkpad has beeped happily, you should eject the laptop, and then re-insert.
# Gently pull the release handles (back left/right of the ultrabase). If it beeps unhappily (long, high), stop pulling.
# Pull the handles harder to physically eject the thinkpad.
# Later, reseat the thinkpad with a firm push.

How to hotswap the UltraBase

2010-03-01T00:46:11Z

AlanHK: /* Usage */

How to hotswap the UltraBase

2010-03-01T00:42:35Z

AlanHK: /* Usage */

== Introduction ==

Here is how I set up an {{X22}} to allow hot ejection/removal of the UltraBase. See also [[How_to_hotswap_Ultrabay_devices|this related page]] for the Ultrabay. These instructions are well-tested, but ymmv.

===Features===

* Uses <tt>lt_hotswap</tt> to preserve DMA on re-insert
* Idiot-proof (somewhat)
* Scripts also work without <tt>lt_hotswap</tt> (using the older way, <tt>idectl</tt>).
* Makes use of ThinkPad beeps to inform user.

===System===

* X22 ThinkPad + UltraBase + DVD-R
* [[lt_hotswap]] version 0.3.9
* kernel-2.6.17.1
* xorg 6.9.0

==Files==

===rc.local===
First, make sure the lt_hotswap module is loaded. Add this to /etc/rc.local (or use modprobe.preload, if you prefer)
echo "Loading lt_hotswap module"
modprobe lt_hotswap hdc_dock=1

===/etc/acpi/events/lths===

Disable the existing lths script. Here is the modified /etc/acpi/events/lths:
# Call the LTHS script
event=lths.*
#action=/usr/local/sbin/lths.sh %e
action=echo "Not invoking lths.sh; this is now done by the ultrabase_eject and insert scripts instead."

===/etc/acpi/events/ultrabase_eject===

Respond to an ultrabase eject event. Here is /etc/acpi/events/ultrabase_eject
#Ultrabase eject button has been pressed
#We can be triggered by an ibm/bay event if NOT using lt_hotswap, or an lt_hotswap event if we are.
event=ibm/bay.MSTR.00000003.00000000
event=lths.MSTR.00000003.00000000
action=/etc/acpi/actions/ultrabase_eject.sh

===/etc/acpi/events/ultrabase_insert===

Respond to an ultrabase insert event. Here is /etc/acpi/events/ultrabase_insert
#Ultrabase has been re-inserted
#We can be triggered by an ibm/bay event if NOT using lt_hotswap, or an lt_hotswap event if we are.
event=ibm/bay.MSTR.00000001.00000000
event=lths.MSTR.00000001.00000000
action=/etc/acpi/actions/ultrabase_insert.sh

===/etc/acpi/actions/ultrabase_eject.sh===

This is the actual script which does the ejection. It is /etc/acpi/actions/ultrabase_eject.sh
* Note the dependency on '''cddb-id'''.
{{MoveToCode}}

#!/bin/bash
echo "syncing disks for safety"
sync

echo "Unregistering IDE interface for CDROM and preparing to eject."

#Note: the BIOS will already deal with the ultrabay LED (number 3). It will:
# * turn it on when the bay is loaded
# * turn it off when the bay is unloaded
# * blink it when it is waiting between an eject request and an eject. (Linux never takes long enough to see this!)

#What if there is a disk in the drive?
#Case 1: there is an umounted CDROM, or an AudioCD/DVD which is NOT playing.
# => It's OK to proceed.

#Case 2: there is a mounted CDROM.
# => we MUST unmount it, or give up on ejecting.
if grep hdc /proc/mounts >/dev/null; then
echo "There is a mounted filesystem on /dev/hdc. Trying to unmount it"
umount /dev/hdc
if [ $? == 0 ]; then
echo "Successfully unmounted the CDROM."
else
echo "The CDROM is busy; can't unmount. Do not try to undock."
echo 9 > /proc/acpi/ibm/beep #This is an "unhappy, warning beep"
exit 1
fi
fi

#Case 3: there is a AudioCD/DVD which is currently playing.
#How do we detect this? It could be just using cdplay (which has no associated process)
#The following methd is ugly, and it requires the cddb-id program. However, it does work.
#Assuming that we have already ruled out a mounted filesystem, then...
CDDBID=$(cddb-id /dev/hdc 2>/dev/null)
if [ -n "$CDDBID" ]; then
echo "There is a CD in the drive. Ejecting it"
eject /dev/hdc #Buglet: we don't necessarily want to eject the disk; we just want to be sure it has stopped playing.
fi

#We're now OK to proceed.
if /sbin/lsmod | grep lt_hotswap > /dev/null ; then
echo "We are using lt_hotswap"
#Eject the bay using lths.
echo -n "MSTR eject" > /proc/acpi/lths
else
echo "We are not using lt_hotswap. Do it the old way with idectl."
#Unregister IDE interface 1. This WILL cause a kernel panic if there is anything in the drive!
idectl 1 off
#Tell the thinkpad the bay is to be ejected
echo eject > /proc/acpi/ibm/bay
fi

#Beep happily
echo 6 > /proc/acpi/ibm/beep
echo "OK to undock"

===/etc/acpi/actions/ultrabase_insert.sh===

This script is called on insertion. It is /etc/acpi/actions/ultrabase_insert.sh

#!/bin/bash
echo "Ultrabase has been inserted. Re-registering IDE interface for CDROM."

if /sbin/lsmod | grep lt_hotswap > /dev/null ; then
echo "We are using lt_hotswap"
echo "Enabling DMA on /dev/hdc"
hdparm -d 1 -u 1 -c 1 /dev/hdc

#LTHS already beeps; no beep required here.
else
echo "We are not using lt_hotswap. Do it the old way with idectl."

#Register IDE interface 1
idectl 1 rescan
#Turn DMA on again. But this is probably a vain attempt; it will fail unless we are using lt_hotswap.
sleep 2
hdparm -d1 /dev/hdc || echo "WARNING: DMA cannot be re-enabled for hdc after insert. You'll have to reboot for now."

#Beep happily
echo 6 > /proc/acpi/ibm/beep
fi

echo "Redocked successfully"
echo "Note: KDE's volume manager might not work anymore with the CD/DVD drive."

==Debugging==

* The easiest way to check what is happening is:
tail -f /var/log/acpid

* Remember, after modifying anything in /etc/acpi/events, to reload the acpid rules:
killall -HUP acpid

* Note that stdout from all scripts ends up in /var/log/acpid. But to communicate a message with the user, it's best to use either the various thinkpad beeps, or perhaps the thinklight.

* Note: idectl and lt_hotswap '''really''' don't get along together. You will lock the system.

==Usage==

# Save your files; this could (possibly) crash the kernel.
# Press the "Request ejection" button, which is on the front of the ultrabase (located between CD drive and floppy).
# The thinkpad should beep happily (high-low). If so, proceed. Otherwise, if it beeps unhappily (3 very short high beeps), it was unable to unmount a busy filesystem in the optical drive.
# Gently pull the release handles (back left/right of the ultrabase). If it beeps unhappily (long, high), stop pulling.
# Pull the handles harder to physically eject the thinkpad.
# Later, reseat the thinkpad with a firm push.

Note: If you change your mind after the thinkpad has beeped happily at (2), you should eject the laptop, and then re-insert.

Help:Editing

2010-03-01T00:39:27Z

AlanHK: /* general help */

==general help==

For general help in editing please read [[Wikipedia:Wikipedia:Cheatsheet| Wikipedia's "Editing cheatsheet"]], or see [http://meta.wikimedia.org/wiki/Help:Editing MediaWiki's Help:Editing].

==ThinkWiki editing policies==

===write with other users in your mind===
When you write an article, keep the following things in mind...
*Respect others. Try sticking to a [http://en.wikipedia.org/wiki/Npov neutral point of view]. Respect the work of other writers. Respect your (potential) readers.
*ThinkWiki is not only about the newest models. Try to write in a way that is open for older, newer and future models. This especially regards the structuring of the information you provide.
*ThinkWiki is not only about your Distro. Try to make clear if something you write is valid only for your specific linux distribution.
*Even though the article is written by you, it is a piece of information others might work on later. Try to avoid personal remarks in your articles.

===naming policies for new pages===
If you create a new page, please consider the following page naming policies. This is important to keep a persistent page naming scheme and hence to ensure that ThinkWiki still works well when it has grown more complex.

Page names (the links you create to point to the page) are used as the page Title. Considering these policies has the following advantages:
*the pages will have self-explaining titles
*in Category views like the Model view the links to the pages are expressively labeled and similar pages are sorted together
*the pages are more easily found in search engines like google

====general policies====
*It is allowed and in fact wanted that you use spaces within your page titles.
*The name you choose for the page should be as specific as its content will be. In other words...it should not be possible to write another page with more general content about the topic that your page title indicates.

====specific kinds of pages====
To sort similar pages together in the Model views, we start specific pages in defined ways.
The following table shows the naming schemes for several kinds of pages...
{| border="1" cellspacing="0" cellpadding="2"
|+page naming schemes
! page type !! naming scheme !! example
|-
| Installation instructions overview for a model || Installation instructions for the <model> || Installation instructions for the ThinkPad T41p
|-
| Installation instructions for a specific distro on a model || Installing <distro> on a <model> || Installing Gentoo on a ThinkPad T41p
|-
| other HowTos || How to ... || How to get special keys to work
|-
| Problem descriptions || Problem with ... || Problem with lm-sensors
|-
| Drivers and Tools pages || <name of driver/tool> || ibm-acpi
|-
| Patches || Patch ... || Patch disabling ACPI C3
|-
| Components || <name of component as used by IBM> || IBM 11a/b/g Wireless LAN Mini PCI Adapter II
|-
| Distro pages || Category:<distro> || Category:SUSE
|-
| ThinkPad Models || Category:<Model without "ThinkPad"> || Category:T41p
|-
| Specifications || <type number-model number> || 2373-GHG
|-
|}

=== use semantic formatting ===
Please prefer semantic formatting over beauty. To help maintaining a formatting standard, you can use the following templates.
{{NOTE|
Unfortunately, nesting templates is not possible. I.e. you can't put a cmd template inside a NOTE template.
}}
<br />
{| border="1" cellspacing="0" cellpadding="2"
! syntax !! resulting output
|- style="vertical-align:top;"
| <nowiki>{{cmduser|command}}</nowiki> || {{cmduser|command}}
|- style="vertical-align:top;"
| <nowiki>{{cmdroot|command}}</nowiki> || {{cmdroot|command}}
|- style="vertical-align:top;"
| <nowiki>{{cmdgrub|command}}</nowiki> || {{cmdgrub|command}}
|- style="vertical-align:top;"
| <nowiki>{{cmdresult|shell output}}</nowiki> || {{cmdresult|shell output}}
|- style="vertical-align:top;"
| <nowiki>{{cmd|command|prefix>}}</nowiki> || {{cmd|command|prefix>}}
|- style="vertical-align:top;"
| <nowiki>{{bootparm|parameter|value}}</nowiki> || {{bootparm|parameter|value}}
|- style="vertical-align:top;"
| <nowiki>{{path|/etc/config.cfg}}</nowiki> || {{path|/etc/config.cfg}}
|-
|
#<nowiki>{{kernelconf|CONFIG_SCSI|[M]|SCSI device support|SCSI device support|Device Drivers||}}</nowiki>
#<nowiki>{{kernelconf|CONFIG_SCSI|[M]|SCSI device support||||}}</nowiki>
#<nowiki>{{kernelconf|CONFIG_SCSI|[M]|||||}}</nowiki>
#<nowiki>{{kernelconf|CONFIG_SCSI||||||}}</nowiki>
#<nowiki>{{kernelconf||[M]|SCSI device support||||}}</nowiki>

''specify the menuconfig path in reverse order and fill with empty parameters to at least a total of seven''
|
#{{kernelconf|CONFIG_SCSI|[M]|SCSI device support|SCSI device support|Device Drivers||}}
#{{kernelconf|CONFIG_SCSI|[M]|SCSI device support||||}}
#{{kernelconf|CONFIG_SCSI|[M]|||||}}
#{{kernelconf|CONFIG_SCSI||||||}}
#{{kernelconf||[M]|SCSI device support||||}}
|-
| <nowiki>{{HINT|A suggestion.}}</nowiki> || {{HINT|A suggestion.}}
|- style="vertical-align:top;"
| <nowiki>{{NOTE|Take notice!}}</nowiki> || {{NOTE|Take notice!}}
|- style="vertical-align:top;"
| <nowiki>{{WARN|Be careful!}}</nowiki> || {{WARN|Be careful!}}
|- style="vertical-align:top;"
| <nowiki>{{HELP|Request for help}}</nowiki> || {{HELP|Request for help}}
|-
| <nowiki>{{QUOTE|Master Foo|zen-devel|Your theories on the sound of one hand clapping are quite interesting.}}</nowiki> || {{QUOTE|Master Foo|zen-devel|Your theories on the sound of one hand clapping are quite interesting.}}
|-
|<nowiki>{{key|Fn}}{{key|F4}}</nowiki> || {{key|Fn}}{{key|F4}}
|-
|<nowiki>{{ibmkey|Access IBM|#495988}} = {{ibmkey|ThinkPad|#494949}}</nowiki> || {{ibmkey|Access IBM|#495988}} = {{ibmkey|ThinkPad|#494949}}
|-
|<nowiki>to be commented{{footnote|1}}</nowiki> || to be commented{{footnote|1}}
|-
|<nowiki>{{footnotes|</nowiki><br />
<nowiki>#first footnote</nowiki><br />
<nowiki>#second footnote</nowiki><br />
<nowiki>}}</nowiki>
|| {{footnotes|
#first footnote
#second footnote
}}
|}

=== Tables ===
When adding tables, you might want to use our special <nowiki>{{Cyes}}</nowiki>, <nowiki>{{Cno}}</nowiki> and <nowiki>{{Cunk}}</nowiki> tags.

{| border="1" cellspacing="0" cellpadding="2"
! Syntax !!Resulting output
|-
| <nowiki>{{Cyes}}</nowiki> || {{Cyes}}
|-
| <nowiki>{{Cno}}</nowiki> || {{Cno}}
|-
| <nowiki>{{Cpart}}</nowiki> || {{Cpart}}
|-
| <nowiki>{{Cunk}}</nowiki> || {{Cunk}}
|-
| <nowiki>{{Cunk}} (should work)</nowiki> || {{Cunk}} (should work)
|-
| <nowiki>{{Cunk|text=}} custom text</nowiki> || {{Cunk|text=}} custom text
|-
|}

=== use our Link&Categorization Templates===
To ease editing and to provide a standardized way of linking to a category and categorizing the page at the same time in that category, we introduced the following Templates. So far there are two types of these:
*Model Templates. Just write the model number surrounded by winged brackets, like i.e. <nowiki>{{T40}}</nowiki>. This will be equivalent to <nowiki>[[:Category:T40|T40]] [[Category:T40]]</nowiki>. Hence the result will be a link like this: [[:Category:T40|T40]], but at the same time, the page will be categorized under that category.
*Distribution Templates. They work the same way as Model Templates, except that for them you need to specify the Distribution name (simplest, shortest variant of it). It will create a link to that distributions category page and also categorize the page you used the template on under that category.

=== use our Editorial Templates===
{| border="1" cellspacing="0" cellpadding="2"
! syntax !! resulting output
|-
|<nowiki>{{Stub}}</nowiki><br />(Use only at the beginning of pages!)||{{Stub}}
|-
|<nowiki>{{Todo|needs editing}}</nowiki>||{{Todo|needs editing}}
|-
|<nowiki>{{Fixme|preliminary information}}</nowiki>||{{Fixme|preliminary information}}
|-
|<nowiki>{{Usage|do this and that}}</nowiki><br />(Use only at the beginning of pages!)||{{Usage|Do this and that}}
|}
'''Have fun editing!'''

Problem with unauthorized MiniPCI network card

2009-10-28T12:31:20Z

AlanHK:

==Problem Description==
Although the MiniPCI slot is an industry standard and can accept any MiniPCI adapter, the IBM BIOS is set to only allow you to boot with an 'authorized' adapter installed. Attempts to install an unsupported card will result in the following message:

1802: Unauthorized network card is plugged in - Power off and remove the miniPCI network card.

This is because the card's sub-vendor PCI-ID (which can be seen using ''lspci -v'') are checked against a [[Wikipedia:Whitelist|whitelist]] in the BIOS. IBM's reasoning for this is that the combination of MiniPCI card and the integrated antenna in the ThinkPad needs to be certified by the US FCC (Federal Communications Commission).{{footnote|1}} or similar agencies in other countries.

==Affected Models==
All machines with integrated WiFi, or machines with WiFi added

==Affected Operating Systems==
All - problem is in the BIOS

==Status==
* Workarounds exist for most affected models.

==Solutions==
It may be possible to use the computer with the unauthorized card deactivated (but not removed). Press {{key|F1}} to enter the BIOS and deactivate the WLAN card, then attempt to boot with the card disabled. This does not make the wireless card work, but it may allow you to boot the computer normally.

{{NOTE|Any of the following solutions should suffice to make the wireless card useable. You only need to perform one of them.}}

* You may can modify the BIOS whitelist to include the PCI-ID of the card you wish to use. The complete instructions for this procedure are [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].
{{WARN|It is dangerous to mess with your BIOS, you can easily make your machine unbootable, proceed with caution!}}

* A safer and better method than modifying the BIOS is modifying the PCI-ID of the wlan card to match the authorized one(why? 1.you'll risk the wireless card instead of the motherbord 2.future BIOS updates will not create any problem 3.no problem with newer laptops with different BIOS, the only reqirement is to find an ID that is already listed in the BIOS that can be easily acheived if community maintain a compatibility table). The instructions are [http://www.dagarlas.org/stuff/computing/article0001.php here]. This page is for Atheros-based cards and HP notebooks, but it applies to Thinkpads as well. It also has links on how to edit the PCI-ID on Intel Pro Wireless cards. Instruction for intel 2200/2915 cards are [http://stachon.webpark.cz/ipw-eeprom.html here] or [http://www.thinkpad-forum.de/thinkpad-hardware/zubeh%C3%B6r/44192-tutorial-nicht-ibm-wlan-karte-2200-2915-im-thinkpad/ here] (in German). The second one is much simpler because it provides an already patched and compiled ipw2200 driver required to do the job.
{{NOTE|Modifying your PCI-ID will require either a laptop without a BIOS lock or a PCI adapter for your desktop. Also, this procedure can render your card useless, but that's better than bricking your laptop.}}

* Another safer method: You can plug the wireless card into the spare WWAN slot (the second miniPCI express slot) with pin-20 taped over. It has been tested on a Thinkpad X61s and a non-IBM (unauthorized) Intel Wifi link 4965agn card, originally it gave a 1802 error, but using this trick it boots up and works without any apparent problem-- it essentially hides the card from the test in the bios, but the WWAN slot still gives the card access to the proper PCI bus, with no need to modify the computer or card. Other combinations reported to work with this method: Thinkpad X61 / Intel 3945abg (bulk).

* You can use the [[Problem with error 01C9 - More than one Ethernet devices | no-1802 and no-01C9 Linux Live CD]] without applying the no-01C9 patch. It is very convenient to use and based on the C code below.

* You can use the DOS [http://jcnp.pku.edu.cn/~shadow/1802/no-1802.com no-1802] utility, written by Tisheng Chen.{{footnote|2}} It will set a certain bit in the CMOS memory which disables the whitelist check, but it has been reported not to work on the latest machines, such as the T43 and X41

* You can compile and run (as root) the following C-code, which was written by Matthew Garrett. It was based on the code written by Vojtech Pavlik, which in turn was based on the assembly used in the no-1802 program. {{footnote|3}}

<code>
#include <stdio.h>
#include <sys/types.h>
#include <unistd.h>
#include <sys/stat.h>
#include <fcntl.h>

int main(void)
{
int fd;
unsigned char data;

fd = open("/dev/nvram", O_RDWR);
if (fd==-1) {
printf("Opening /dev/nvram failed\n");
return 1;
}
printf("Disabling WiFi whitelist check.\n");

/* BIG INFORMATIONAL WARNING */
/* The linux nvram driver doesn't give access to the first 14 bytes of
the CMOS. As a result, we seek to 0x5c rather than 0x6a. If you're
implementing this under another OS, then you'll have to go to whichever
address is appropriate for your access method */

lseek(fd, 0x5c, SEEK_SET);
read(fd, &data, 1);
printf("CMOS address 0x5c: %02x->", data);
data |= 0x80;
printf("%02x\n", data);
lseek(fd, 0x5c, SEEK_SET);
if (write(fd, &data, 1)<0) {
printf("Unable to write to /dev/nvram - hack failed\n");
close(fd);
return 2;
}
close(fd);
printf("Done.\n");
return 0;
}

</code>
{{NOTE|On the R32, T43, X41, X60, W500 and probably others, the BIOS hacks and the "no-1802" utility don't work.}}

* On the X61s (and probably others), if you tape pin 20 from the card, it works if plugged into the second (WWAN) mini-PCIE-slot.

==Successful BIOS Modifications==
{{WARN|This table is meant to give users an idea of what models have been successfully modified and how. As stated before, it is dangerous to mess with your BIOS, you can easily make your machine unbootable. Please proceed with caution!}}

The following table contains information about ThinkPad models that have been successfully modified to run an unauthorized Mini PCI card. {{footnote|4}}

{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"
! style="background:#efefef;"| Model
! style="background:#efefef;"| Type
! style="background:#efefef;"| BIOS Version
! style="background:#efefef;"| Operating System
! style="background:#efefef;"| Method
! style="background:#efefef;"| Success
|- style="background: white;"
| ThinkPad 240
| 2609-21G
| 1.18
| Damn Small Linux
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad A31
| 2652-P3M
| 1.10 (1NET16WW)
| Debian GNU/Linux Lenny (2.6.25-2-686)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad G40
| 2388-2UU
| 1.21 (2006/2/24; 1TETA6WW)
| Windows XP Home
| no-1802 DOS 6.22 floppy
! style ="color:green;"| Yes
|- style="background: white;"
| ThinkPad R31
| 2656-6FG
| 3.11 (12-01-2004)
| Windows XP Boot Disk
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white;"
| ThinkPad R31
| 2656-E4U
| 3.11 (12-01-2004)
| Windows XP Professional SP2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white;"
| ThinkPad R32
| 2656-EG1
| 2.16 (16-06-2006)
| DOS Boot Disk
| no-1802 utility
! style ="color:red;"| No
|- style="background: white;"
| ThinkPad R40
| 2656-69U
| ?
| Windows 2000 Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-F7G
| n/a
| Windows XP Pro SP2 w/ Intel 2200BG
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2682
| ?
| Debian Etch
| Matthew Garrett code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2896-J3U
| 1.24 (10-18-2005)
| Fedora Core 4
| Vojtech Pavlik code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-L7U
| 1.24 (10-18-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2722-BDG
| 1.33
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2722-DG1
| 1.26
| Ubuntu Linux 8.10 2.6.27-9
| Matthew Garrett code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40e
| 2684-LKG
| ?
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-CDG
| 1.27 (10-06-2006)
| Windows XP Pro
| no-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2722-DM2
| 1.09 (2003)
| Windows XP Pro
| no-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2723
| ?
| Slackware Linux 12
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-CFM
| 1.24 (10-17-2005)
| Gentoo & XP Pro
| no-1802 utility (boot from USB key to apply)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2724
| 1.30 (10-19-2005)
| FreeBSD 6.1-p1
| code by Matthew Garrett, compiled and run on bactrack
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2724-3XU
| 1.33 (06-29-2006)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2682
| 1.01 (2003-01-24)
| Debian GNU/Linux etch (March 2007)
| Matthew Garret's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R40
| 2722-BDG
| 1.33 (2006/6/29)
| Lunar Linux (2007/03/04)
| Matthew Garret's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R50
| 1829-7RG
| 3.21 (02-06-2006)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R50
| 1830-6FG
| 3.05a (14-05-2004)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad R50p
| 1832-2AG
| 3.19 (13-10-2005)
| Ubuntu 5.10 (kernel 2.6.12-10-686)
| Vojtech Pavlik code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad R51
| 2887-W2C
| 1.27 (03-03-2006)
| Windows XP Pro SP2
| no-1802 utility (boot from USB key to apply)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad R52
| 1849-BMU
|1.27 (09-20-2006)
| Windows XP Pro SP2
| no-1802 utility (boot from external USB floppy)
! style ="color:red;"| No
|- style="background: white; color:black;"
|ThinkPad T23
| 2647-4MU
| 1.18 (08-06-2004)
| Windows XP Pro/SP2
| no-1802 utility (W98se-bootfloppy)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T30
| 2366-68G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T30
| 2366-ES1
| 2.10
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-97G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-N6G
| 2.09 (08-08-2005)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-N6G
| 2.10 (26-06-2006)
| Windows XP Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-81U
| 2.10 (27-06-2006)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-86U
| 2.10 (27-06-2006)
| Windows XP Pro SP 2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-86G
| 2.10 (27-06-2006)
| Windows XP Pro SP 2 and Ubuntu 7.10 "Gutsy Gibbon" Intel BG2200
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-86M
| 2.05 (12-06-2003)
| Mepis 7
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-DU9
| 2.10 (27-06-2006)
| Suse Linux 10.1
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2367-RU1
| 2.01 (06-08-2002)
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T30
| 2366-81M
| 2.10 (1IET71WW)
| Debian GNU/Linux Lenny (2.6.24-1-686)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-7CU
| 3.21
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-PM1
| 3.21
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-4BG
| 3.21
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-7CU
| 3.21 (06-02-2006)
| Windows XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-75U
| 3.21 (09-12-2006)
| Fedora 6 w Intel 2915ABG
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-82U
| 3.18 (09-15-2005)
| Windows XP/ SUSE 10.1
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-8CG
| 3.05a (2004-05-14)
| Arch Linux
| No-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-8CG
| 3.15 (2005-03-29)
| Windows XP Pro SP2 w/[http://www.giga-byte.com.tw/Products/Communication/Products_Spec.aspx?ClassValue=Communication&ProductID=985&ProductName=GN-WI01GS Gigabyte GN-WI01GS]
| No-1802 LiveCD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-PU7
| 3.21 (09-12-2006)
| Windows XP Professional
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2373-42G
| 3.20 (11-05-2006)
| Windows 2000 Pro
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2374-8CG
| 3.20 (11-05-2006)
| Ubuntu 6.06 LTS w/Intel Pro Lan2200
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2374-8CU
| 3.03 (07 Apr 2004)
| Windows XP
| no-1802 utility (applied via FreeDos bootable USB stick)
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40
| 2374-DG1
| 3.21 (06-02-2006)
| Ubuntu 6.10 w/Broadcom 4306
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40p
| 2373-G1G
| 3.19 (10-13-2005)
| Debian GNU/Linux (sid)
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T40p
| 2373-G5G
| 3.21 (2006-06-02)
| Windows XP Pro SP2 / Gentoo 2007.0
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41
| 2373-1FG
| 3.21 (2007-06-18)
| Windows XP Pro SP2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41
| 2373-5G1
| 2004
| Fedora Core 6 w/Intel Pro 2915ABG a/b/g
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T41
| 2373-9HU
| n/a
| Ubuntu 6.10 w/Atheros 5212 a/b/g
| no-1802 Linux Live CD
! style="color:green;"| Yes
|- style="background: white; color:black;"
|ThinkPad T41
| 2373-2FG
| n/a
| Windows XP Pro SR2 w/ Intel 2200BG
| no-1802 utility
! style="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41p
| 2373-GEG
| BIOS Build ID: 1RETDOWW(3.20)
| Gentoo / XP pro SP2
| Matthew Garrett's code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41p
| 2374-GGU
| 3.21 (1RETDPWW) 6/2/2006
| Slackware / XP pro SP2
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T41
| 2373-K32
| BIOS Build ID: 1RETDOWW(3.20)
| CentOS 5.0 w/Atheros 5212 (CM9)
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-6UU
| Not noted
| Fedora 7 w/Atheros 5212
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-4TG
| 3.13 (1RETDHWW) (29-10-2004)
| Windows XP Pro SP2 w/ Intel PRO 2200BG
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-Y8N
| 1RETDRWW (3.23)
| openSUSE 11.1 / Intel 2915abg
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42p
| 2373-HTU
| 3.23 (1RETDRWW) (06-18-2007)
| Windows XP Pro SP2 w/ Intel 2915ABG
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-K2G
| 3.17 (07-27-2005)
| Windows XP Pro SP2 w/ Intel 2915ABG
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-M1U
| 3.13 1RETDHWW (10/29/2004)
| Fedora 7 w/ Intel PRO 2200BG
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2373-LM1
| 3.23 (1RETDRWW) (06-18-2007)
| Debian Lenny (2.6.21-2-686) w/ Intel PRO 2915ABG
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T42
| 2378-EXU
| 3.18 (09-15-2005)
| Windows XP Pro SP2
| No-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad T43
| 1871-F1G
| 1.19 (70ET59WW) (2005-09-20)
| n/a
| no-1802 Linux Live CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X22
| 2662-95G
| 1.32 (2003-06-10)
| Debian GNU/Linux testing, kernel 2.6.18-3-686
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X24
| 2662-MPG
| 1.26 (2002-05-22)
| Debian GNU/Linux 2.6.18-5
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| AR5212
| ?
| Debian Linux 2.6.18-5
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2672-41j
| 1.08 (08-09-2005)
| Gentoo Kernel 2.6.15
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2672-4XU
| 1.09
| Win XP Pro SP2
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X30
| 2673-EU2
| 1.09
| Windows XP Pro SP2
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-C2G
| 3.02 (22-09-2005)
| Debian Etch (Testing), Kernel 2.6.22-rc7
| no-1802 utility
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-PG9
| 2.04 (2003-11-10)
| Debian Etch (Testing), Kernel 2.6.21-2
| Matthew Garrett's code
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2673-C27
| 3.02 (22-09-2005)
| Ubuntu 5.10 (kernel 2.6.12-9-386)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-1UG
| 3.02 (22-09-2005)
| FreeBSD 6-STABLE
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CEG
| 3.02 (22-09-2005)
| Debian Etch (Testing), Kernel 2.6.17-2-686
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CXU
| 2.04
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-PBU
| 3.02
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-I5A
| 3.02
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-C8G
| 3.02
| Debian (kernel 2.6.16.20-386)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-CEG
| 2.11 (02/13/2004)
| Debian (kernel 2.6.18-4-686, gcc 4.1.2)
| Matthew Garrett code {{footnote|3}}
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2884-BRU
| 1.03 (1QET34WW) 2003-04-08
| Windows XP Pro SP2 w/ Intel 2915ABG
| no-1802 DOS boot CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-C2G
| ?
| Win XP Pro, w/ Gigabyte GN-WI03N-RN
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X31
| 2672-BAU
| 3.02 (1QET97WW)
| Windows Vista w/ Broadcom 43XG, Ubuntu 7.10
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X32
| 2672-58G
| 3.02
| Ubuntu 8.04
| no-1802 CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X40
| 2371-8EU
| 1.42 (2004/09/16; 1UET92WW)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X40
| 2371-8EU
| 2.08 (2006/12/25; 1UETD3WW)
| Windows XP Professional SP3, Ubuntu 8.04
| no-1802 Linux Live CD
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad X41
| 1866-6SU
| ?
| Windows XP Pro
| no-1802 DOS boot CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X41
| 2525-A2U
| 2.06 (2006/03/14; 74ET61WW)
| Windows XP Pro
| no-1802 Linux Live CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X41
| 2528-ELU
| 2.06 (2006/03/14; 74ET61WW)
| Windows XP Pro / OSX 10.4.8 / Ubuntu Edgy
| no-1802 Linux Live CD
! style ="color:red;"| No
|- style="background: white; color:black;"
| ThinkPad X60s
| 1702-3JU
| ?
| Debian Testing
| Matthew Garrett's code
! style ="color:red;"| NO (bricked)
|- style="background: white; color:black;"
| ThinkPad R40
| 2681-LUU
| 1.27 (2006-06-29; 1OET61WW)
| Windows XP Pro
| jmp1802.cmd
! style ="color:green;"| Yes
|- style="background: white; color:black;"
| ThinkPad W500
| 4061-A97
| 1.16 (2008-09-24; 6FET46WW)
| Ubuntu 8.10
| Matthew Garrett's code
! style ="color:red;"| No

|-
|}

==Problem with WiFi LED==
After getting an unauthorized card to work, you may notice that the WiFi LED found on the ThinkPad is not working. This doesn't happen with all unauthorized cards. The general cause for this is the fact that the MiniPCI standard leaves the implementation of the LED signals available on the MiniPCI connector to the card vendors. Therefore some newer WiFi cards use one of the signals originally meant for LEDs to implement the "radio kill" switch input. As a result, the LED doesn't get proper signals and fails.

====Details====
The WiFi LED found in ThinkPads is connected to following pins on the MiniPCI connector.
{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"
!style="background:#efefef;"|Pin
!style="background:#efefef;"|Signal
!style="background:#efefef;"|Description
|-style="background: white;"
|11
|LED1_GRNP
|WiFi active LED +
|-style="background: white;"
|13
|LED1_GRNN
|WiFi active LED - (older cards) / RF Silent input (newer cards)
|}
Note: The descriptions are specific to this article.

If your LED is not working, the problem could be the pin 13. Newer cards may no longer provide the necessary negative signal there to drive the LED. Before you apply any fixes, be sure to check the voltage between pin 11 and ground (can be found for example on the MiniPCI latch arms) - it should give you about 3.3V while the WiFi is active and 0V otherwise. The voltage between pin 13 and ground should measure about 2.5V. The notebook has to be running while you perform the tests so be extremely careful. All the mentioned pins are on the upper side so it's quite easy to get to them with a multimeter. If all the voltages match, your LED is fixable.

Reference:<br>
[http://members.datafast.net.au/dft0802/specs/mpci10.pdf MiniPCI Specification] (PDF, 724KB)<br>
[http://www.interfacebus.com/MiniPCI_Pinout_124Pin.html MiniPCI Pinout]

====Solution====
The solution is to connect the ground (GND) to the pin 13. However, since the new ''RF Silent input'' signal is active low, grounding the card side will tell it to turn itself off. Therefore, we have to separate pin 13 of the card from the system board and connect ground to the system board side only.

There are many ways to accomplish this. One which doesn't require any soldering is to mask pin 13 on the card with a cellophane tape and use about 3cm of thin wire to connect pin 13 of the connector to the ground. Place one end of the wire on the masked pad and insert the card into the slot. Check if the wire is centered on the pad and try pulling it (but not too hard) to see if it holds. If it comes out easily, pull the card out and repeat. If you successfully attach it, you have to connect the other end to the ground. The best place is the left MiniPCI latch arm. Bend it outside and insert the wire into the small gap between the two pieces of metal the arm is made from. Finally, make sure that the wire doesn't touch anything else and doesn't stand out too much, it must not touch the touchpad electronics when you put the palmrest back on. If in doubt, cover the wire with some insulator.

{{WARN|Do this fix ONLY if you know exactly what you are doing and at your own risk! If you're not sure about any part, don't even try it or you may damage your WiFi card and/or brick your laptop. You have been warned.}}

{{NOTE|If your card is not listed in the table below, your WiFi LED may not work for some other reason. Therefore, make sure you understood the problem described here and made all the measurements carefully. This way you will know if this apply to your card and if it can be fixed this way. Otherwise, if you're skilled enough, please try to find out why your LED doesn't work and contribute to this article.}}

====Successful WiFi LED fixes====
{| align="center" cellpadding="2" width="100%" style="border:1px; background:grey;"
! style="background:#efefef;"| Model
! style="background:#efefef;"| Type
! style="background:#efefef;"| WiFi card
! style="background:#efefef;"| Operating System
! style="background:#efefef;"| Success
! style="background:#efefef;"| Comments
|- style="background: white; color:black;"
|T41
|2374-312
|Intel PRO/Wireless 2915ABG,
Spares No: 373830-001
|Windows XP SP2,
Ubuntu 7.10
|style ="color:green;font-weight:bold;"|Yes
|The WiFi card seems to be a HP one (tip: google for spares no.). Not sure thou - received it with an already changed PCI-ID.
|- style="background: white; color:black;"
|X31
|2672-PG9
|Intel PRO/Wireless 2915ABG, Broadcom BCM4306
|Debian Sid
|style ="color:green;font-weight:bold;"|Yes
|Both cards are non-IBM ones, BIOS was patched. ipw2200 needed the {{bootparm|led|1}} option to be enabled while loading the module.
|}

==External Sources==
* Additional Information about "Unauthorised" MiniPCI adapters can be found on [http://www.srcf.ucam.org/~mjg59/thinkpad/wireless.html Matthew Garrett's website].

* Thinkpad Mini PCI Wireless [http://www.srcf.ucam.org/~mjg59/thinkpad/tables.html compatibility matrix].

* Bootable "no-1802" [http://www.command-tab.com/2006/02/26/unauthorized-wireless-cards/ CD and floppy image]

{{footnotes|
#This is explained in a [http://lkml.org/lkml/2003/6/3/162 message to the LKML] and subsequently [http://lkml.org/lkml/2003/6/9/50 clarified].
#The no-1802 tool was announced and explained in a [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2004-June/018253.html message to the Linux-Thinkpad ML].
#Vojtech Pavlik's C-code was originally posted in a [http://lkml.org/lkml/2004/6/13/69 message to the LKML]. It was based on the assembly used in the no-1802 program. Matthew Garrett [http://www.srcf.ucam.org/~mjg59/thinkpad/hacks.html rewrote] the code to provide more error checking.
#This information has been added by users. Please feel free to add systems if you have had personal success or failure.
}}

ThinkPad series

2009-09-15T23:50:13Z

AlanHK: spelling

=Current Series=
==ThinkPad R series==
Dropping the [[#ThinkPad A series|A series]], IBM introduced a mainstream budget line of ThinkPads in the R series. The RXXe series lacks some of "normal" RXX series features like stereo speakers, touchpad, hot-swappable CD/DVD drive, docking connector and some other things. They also usually feature slower CPU like Intel Celeron (but in newer models also slower Intel Core processors). ACPI functions in modern RXX-e models are just as well supported in Linux as they are for the regular RXX models.

Starting from R61, the R series ThinkPads feature the same chassis (including RollCage) as the [[#ThinkPad T series|T series]] making them virtually indistinguishable from each other.

==ThinkPad T series==
As successor of the [[#ThinkPad 600 series|600 series]], the T series became IBM mobile productivity line. Usually leading the ThinkPad range in technology, innovation and price, the T series was intended for the travelling businessman - comparatively more stylish, functional, and rugged machines; and easy to disassemble for repair or upgrades. T series ThinkPads are clad in black non-slip rubber with embedded glitter. The case lid has tabs along the edge that interlocks with depressions in the lower case when closed, to reduce case flexing.

===ThinkPad T2x series===
The ThinkPad T2x models ([[:Category:T20|T20]], [[:Category:T21|T21]], [[:Category:T22|T22]], [[:Category:T23|T23]]) were [[Intel Mobile Pentium III-M]] based, sub-5 lb (2.3 kg) class machines. These machines typically had 14.1 inch XGA screens, S3 Savage graphics chips and Cirrus Logic sound chips. The T2x series introduced the [[UltraBay|UltraBay 2000]] optical drive bay and titanium-reinforced screen lids. With the [[:Category:T23|T23]], an internal WiFi antenna became available, so WiFi miniPCI cards could be used. Also the [[:Category:T23|T23]] was the first ThinkPad featuring an [[UltraBay|UltraBay Plus]] drive and [[Embedded Security Subsystem]].

===ThinkPad T3x series===
The T3x series only saw one model, the [[:Category:T30|T30]]. Powered by a [[Intel Mobile Pentium 4-M]] and a Radeon 7500 graphics chip with 16 MB of discrete video memory, the T30 was available with 14.1 inch XGA or SXGA screens. The [[:Category:T30|T30]] introduced the [[UltraNav]] touchpad and integrated Bluetooth among ThinkPads. Other features include the [[Embedded Security Subsystem]], [[UltraBay|Ultrabay Plus]] drive, integrated Wireless LAN. The shell is titanium reinforced composite. The whole package was a bit heavier and thicker than both the T2x and the T4x series.

===ThinkPad T4x series===
Includes the [[:Category:T40|T40]], [[:Category:T41|T41]], [[:Category:T42|T42]], [[:Category:T43|T43]], and associated "p" series (for "performance"; e.g., [[:Category:T43p|T43p]]). A typical T4x weighs 2.2 kg (4.9 lb), slightly less than the [[#ThinkPad 600 series|600 series]], and features an [[Intel Pentium M (Dothan)]] Processor, a 14.1 or 15 inch LCD (XGA or SXGA+), an integrated GPU ([[Intel Graphics Media Accelerator 900]]) or a discrete GPU ([[ATI Mobility Radeon 7500]], [[ATI Mobility Radeon 9000|9000]], [[ATI Mobility Radeon X300|X300]], [[ATI Mobility FireGL 9000]], FireGL 9600, [[ATI Mobility FireGL T2| FireGL T2]] and [[ATI Mobility FireGL V3200|FireGL V3200]]), and a hard drive ranging in size from 30 to 100 GB with the [[Active Protection System]] to protect the hard drive ([[:Category:T41|T41]] and later models). "p" (mobile workstation) models are also available with a 14" SXGA+ or a 15 inch UXGA FlexView display with wide viewing angle and high density IPS technology with resolutions up to 1600x1200. These 15 inch display models weigh slightly more than their lesser brethren, with optical drive and battery, at 2.7 kg (5.9 lb). Some [[:Category:T42|T42]] and [[:Category:T43|T43]] models feature a biometric security system with [[Integrated Fingerprint Reader]].

===ThinkPad T6x series===
ThinkPad [[:Category:T60|T60]] contained the [[Intel Core Duo (Yonah)]]. It was paired with either a [[ATI Mobility Radeon X1300]] or [[ATI Mobility Radeon X1400|x1400]] or with an [[ATI Mobility FireGL V5200]] for the performance model. The [[:Category:T60|T60]] was also the first of its kind to support Wireless Wide Area Network (WWAN) out of the box if the option was selected.

The ThinkPad [[:Category:T60|T60]] refresh contained the [[Intel Core 2 Duo (Merom)]]. It gave a processing speed of up to twenty five percent faster than the [[Intel Core Duo (Yonah)|Yonah]] and introduced EM64T into the mobile realm. It was paired with either a [[ATI Mobility Radeon X1300]] or [[ATI Mobility Radeon X1400|x1400]] or with an [[ATI Mobility FireGL V5250]] for the performance model.

ThinkPad [[:Category:T61|T61]] features the Santa Rosa chipset, in addition to the existing [[Intel Core 2 Duo (Merom)]]. The designers found it prudent to move from an ATI based Mobility Radeon to NVIDIA's Quadro NVS series discrete video processors. The move also marked a more aggressive shift to the wide screen format. Introductory [[:Category:T61|T61]] models only shipped with a wide screen. In addition, the designers added a Roll Cage for the screen to decrease the likelihood of damage in the event of a fall. Finally fan blades were overhauled to decrease fan noise and temperature.

==ThinkPad X series==
===ThinkPad X2x series===
[[Intel Mobile Pentium III]] with [[ATI Rage Mobility M]] ([[:Category:X20|X20]], [[:Category:X21|X21]]) or [[Intel Mobile Pentium III-M]] with [[ATI Mobility Radeon 7000]] ([[:Category:X22|X22]], [[:Category:X23|X23]], [[:Category:X24|X24]]), sub-4 lb machines. Contained processors ranging from [[Intel Mobile Pentium III|MPIII]] 500 MHz to [[Intel Mobile Pentium III-M|PIII-M]] 1+ GHz. 12.1 inch XGA screens. Used miniPCI form factor cards, which supports modem and/or ethernet. With the [[:Category:X22|X22]] and later machines, provisions for wireless networking support are built into the chassis. [[UltraBay|UltraBay 2000]] optical drive support can be fitted via the [[UltraBase X2]] portable docking station option, and extended batteries can give the series a 5 hour running time.

===ThinkPad X3x series===
[[Intel Mobile Pentium III-M]] with [[Intel Graphics Technology]] ([[:Category:X30|X30]]) or [[Intel Pentium M (Banias)]]/[[Intel Pentium M (Dothan)|(Dothan)]] with [[ATI Mobility Radeon 7000]] ([[:Category:X31|X31]], [[:Category:X32|X32]]), 12.1 inch XGA screens, [[IrDA]], FireWire, Compact Flash card slot. No built-in optical drive. Like the X2x series [[UltraBay|UltraBay Plus]] optical drive support can be fitted via the [[UltraBase X3]] portable docking station option. As the [[UltraBase X3]] can take the same battery as the notebook, the running time can be increased to amazing 10 hours.

===ThinkPad X4x Series===
A continuation of the lightweight X series. Weighing in at 1.2 kg (2.7 lb), the lightest [[:Category:X41|X41]] is 25% lighter than its predecessor, the [[:Category:X31|X31]]. Part of the X4x series, the [[:Category:X41 Tablet|X41 Tablet]] is the first Tablet PC (convertible) ThinkPad. They also get [[UltraBay|UltraBay Slim]] optical drive support via the [[UltraBase X4]] portable docking station option, but it is not compatible with the [[:Category:X41 Tablet|X41 Tablet]].

===ThinkPad X6x Series===
Starting in 2006, the first models in X6x series were [[:Category:X60|X60]], lighter and smaller [[:Category:X60s|X60s]] and [[:Category:X60 Tablet|X60 Tablet]] (the two with slower CPU). These models featured [[:Intel_Core_Duo_(Yonah)|Intel Core]] CPUs, later Core 2.

Later, [[:Category:X61|X61]], [[:Category:X61s|X61s]] and [[:Category:X61 Tablet|X61 Tablet]] appeared. These ThinkPads are now migrated to the new Santa Rosa chipset, in addition to the existing [[:Intel_Core_2_Duo_(Merom)|Intel Core 2 (Merom)]] platform and has some design improvements. The X61 features full-blown Core 2 Duo processors, X61s and X61 Tablet can be configured only with low-voltage variants. In many benchmarks, the X61 proved, that it can be as fast as ThinkPad [[:Category:T61|T61]] with same configuration.

Unlike T61 and [[:Category:R61|R61]], the X61 series aren't available with widescreen display option.

X6x series ThinkPads fit in the [[UltraBase X6]], while X6x Tablets fit in [[X6 Tablet UltraBase]] docking stations.

=Withdrawn Series=
==ThinkPad 200 series==
The 200 series ([[:Category:220|220]], [[:Category:230|230]], [[:Category:235|235]], [[:Category:240|240]] and their various sub series) was a subnotebook series. This means they were extremely small and light crossovers between notebooks and PDAs. The series ended with the [[:Category:240X|240X]]. With the changing from the numeric to the alphanumeric naming scheme in 2000, IBM stopped developing subnotebook class ThinkPads. Only in the Asia-Pacific only [[#ThinkPad S series|S series]] did in find a rather short revival.

==ThinkPad 300 series==
The 300 series ([[:Category:300|300]], [[:Category:310|310]], [[:Category:350|350]], [[:Category:360|360]], [[:Category:365E|365E]], [[:Category:380|380]], [[:Category:385ED|385ED]], [[:Category:390|390]] and their various sub series) was a long running value series starting at the [[Intel 386|Intel 386SL-33]] going all the way to the [[Intel Mobile Pentium III]]. The ThinkPad 300 was also produced for IBM by Zenith Data Systems. They were a bit large and slower than the more full featured models but offered a less expensive ThinkPad. The successor of this series is the [[#ThinkPad R series|R series]].

==ThinkPad 500 series==
The 500 series ([[:Category:500|500]], [[:Category:510Cs|510Cs]], [[:Category:560|560]], [[:Category:570|570]] and their various sub series) were the main line of the ultraportable ThinkPads. Starting with the [[IBM 486|IBM 486BL-25 Blue Lightening]] to the [[Intel Mobile Pentium III]], these machines had only a hard disk onboard. Any other drives were either external or available in the respective [[Docking Solutions]]. The successor of the 500 series is the [[#ThinkPad X series|X series]].

==ThinkPad 600 series==
The 600 series ([[:Category:600|600]], [[:Category:600D|600D]], [[:Category:600E|600E]] and [[:Category:600X|600X]]) are the direct predecessors of the [[#ThinkPad T series|T series]], and are legendary for their portability and sturdy construction. Most 600 series models packed a 13.3 inch LCD, [[Intel Mobile Pentium II]] or [[Intel Mobile Pentium III]] processor and full sized keyboard into a package weighing roughly 2.3 kg (5 lb). The [[UltraBay|UltraSlimBay]] was introduced with the 600 series. IBM was able to create this light, fully featured machine by using lightweight but strong carbon fibre composite plastics.

==ThinkPad 700 series==
The 700 series ([[:Category:700|700]], [[:Category:701C|701C]], [[:Category:730T|730T]], [[:Category:750|750]], [[:Category:755C|755C]], [[:Category:760E|760E]], [[:Category:765D|765D]], [[:Category:770|770]] and their various sub series) were the cutting edge Intel-based ThinkPads. They featured the best screens, largest hard drives and fastest processors available at the time.

==ThinkPad 800 series==
The PowerPC ThinkPad series, (800, [[:Category:820|820]], 821, 822, 823, [[:Category:850|850]], 851, [[:Category:860|860]]) were unique in that they ran on the PowerPC architecture, and not the x86 architecture. They all used the [[IBM PowerPC 603|IBM PowerPC 603e]] CPU. The 800 may have used a 603, and it is unclear if the 800 was experimental or not. All units used SCSI 2 instead of IDE. The units are believed to have all been extremely expensive, as the [[:Category:850|850]] cost upwards of $12,000 USD. The 800 series can run Windows NT 3.5 (probably 4.0 as well), OS/2, AIX 4.14, Solaris Desktop 2.5.1 PowerPC Edition and Linux.

==ThinkPad Transnote==
The IBM [[:Category:TransNote|TransNote]] was a pen based PC in a notebook. Data could not only be entered through keyboard, TrackPoint and TouchScreen, but also through a unique paper notepad with integrated digitizer which was produced in cooperation with Cross AT. This ThinkPad expanded on IBM's previous pen based notebooks ([[:Category:360P|360P]](E), [[:Category:730T|730T]](E), and 755(P).

==ThinkPad A series==
The A series was developed as an allround productivity machine, equipped with hardware powerful enough to make it a desktop replacement. Hence it was the biggest and heaviest ThinkPad series at its time, but also had features not even found in a [[#ThinkPad T series|T series]] of the same age. The A series was dropped in favour of the [[#ThinkPad G series|G series]] and [[#ThinkPad R series|R series]].

==ThinkPad G series==
The G series consists of only two models so far, the [[:Category:G40|G40]] and [[:Category:G41|G41]]. Being large and heavy machines, equipped with powerful desktop processors, this line of ThinkPads is consequently specialised in serving as a desktop replacement.

==ThinkPad i series==
The i series introduced the [[ThinkLight]] and were also the first notebooks equipped with Wireless LAN.

==ThinkPad S series==
A subnotebook series consisting of only two models: the [[:Category:S30|S30]] and [[:Category:S31|S31]].
[[Category:Models]]

==ThinkPad Z series==
The widescreen ThinkPad build to offer the ultimate multimedia experience. Internal similar to the [[#ThinkPad T series|T series]], but they have a widescreen and are available with a Titanium Special Edition Cover on selected models. This was the first ThinkPad series completely developed by Lenovo. This series was discontinued as the [[#ThinkPad T series|T series]] are available with widescreen displays.

===ThinkPad Z60x Series===
The first widescreen ThinkPads, internal similar to the T4x series, but they are available with 14" ([[:Category:Z60t|Z60t]]) or 15.4" ([[:Category:Z60m|Z60m]]) widescreens (some with optional MaxBright-technology). Travel weight starting at 4.1 lb and they are less than 1.1" thin. They are the first ThinkPads completely developed by Lenovo.

===ThinkPad Z61x Series===
Second generation Z series, upgraded to the internal technology level of the T60 series ThinkPads.

=Adding a new series=

Please refer to [[Adding a new ThinkPad series or category to ThinkWiki]] for instructions on how to add a new ThinkPad series to ThinkWiki.

Mini-PCI Modem card

2007-12-02T06:40:48Z

AlanHK: /* IBM Partnumbers */

__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;">
=== Mini-PCI Modem card ===
This is a [[MiniPCI slot|Mini-PCI]] [[Modem Devices|Modem Adapter]] that is installed in a Mini-PCI slot.

=== Features ===
* Chipset: Ambit (formerly Lucent Microelectronics) [[Wikipedia:Softmodem|Softmodem]]
* PCI ID: 11c1:0449
</div>
|style="vertical-align:top" |
|}

=== IBM Part numbers ===
IBM FRU PN: 08K3251, 08K3252, 08K3338, 08K3383, 08K3429, 08K4852, 08K4853, 08K4855, 91P7659<br>
IBM FRU PN (390X): 10L1296<br>
IBM FRU PN (570/E): 08K3412

=== Also known (in IBM literature) as.... ===
* Mini PCI modem card (Ambit)
* Mini PCI modem card (IBM CR)
* Mini PCI modem card (M2) (IBM)
* modem card Ambit
* Mini PCI modem

=== Linux driver ===
The Linux driver from [http://www.smlink.com/ SmartLink] may work.<br>
Latest version of this driver is 2.9.10 and supports both the 2.4 and 2.6 kernels.

Otherwise try using the slightly dated [http://www.heby.de/ltmodem/ ltmodem driver for Linux].<br>
The latest version of this driver is 8.31a and supports the 2.4 kernels.
alk@tut.by has prepared a version of the driver for 2.6 kernels.

Lastly, IBM supplies an outdated version (5.95) of the ltmodem driver, with only kernel 2.2 support [http://www-3.ibm.com/pc/support/site.wss/MIGR-4VFTT3.html here].

The Fax is supported by hylafax only, as mgetty-fax requires a class 2 modem, which this one isn't.

=== ThinkPads this card may be found in ===
* {{390E}}, {{390X}}, {{570}}, {{570E}}, {{600X}}
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}, {{A21p}}, {{A22e}}, {{A22m}}, {{A22p}}
* {{T20}}, {{T21}}, {{T22}}, {{T23}}
* {{X20}}, {{X21}}, {{X22}}, {{X23}}, {{X24}}
* {{TransNote}}

[[Category:Components]]

TrackPoint

2007-12-02T06:39:19Z

AlanHK: updated links

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:Trackpoint.jpg|IBM TrackPoint]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== IBM TrackPoint ===
The TrackPoint is IBMs name for the stick that sits between the g, h and b keys of the keyboard. It is used as a pointing device and hence as an alternative to an external mouse or a touchpad. What sets it apart from devices found in notebooks of other manufacturers is that it has no moving parts. It works using a solid state strain gauge. Its tap-to-click feature, which means that you can tap the stick to do a left click instead of using the left mouse button, is also handy.
</div>
|}

==Linux Support==
The TrackPoint uses the PS/2 interface so it is supported by the standard psaux mouse input driver included in the Linux kernel.

Note that the "IMPS/2" driver of the X server is incompatible with most TrackPoints. You'll have to use "PS/2" in the protocol option of your input section if your mouse pointer always jumps to the lower left corner of the screen. This seems to be solved with the T4x generation of ThinkPads.

However, to make use of advanced features like configuring sensitivity or enabling "tap-to-click" there are different solutions available depending on the kernel you are using.
* For 2.4 type kernels it is recommended to use the [http://www.slac.stanford.edu/~strauman/pers/tp4utils/ Linux Trackpoint utilities].
* 2.6.14rc1 and newer has TrackPoint support as part of the regular PS/2 Mouse support
* For older 2.6 kernels, you can get the [[Patch to enable advanced trackpoint configuration]].

If you are using GNOME with the 2.6 kernel TrackPoint support, you might want to use [http://tpctl.sourceforge.net/configure-trackpoint.html configure-trackpoint] as a graphical frontend to it.

*Have a look at [[How to configure the TrackPoint]].

==Models featuring this Technology==
'''TrackPoint'''
*ThinkPad {{220}} <tt>(if that's what the original trackpoint is)</tt>

'''TrackPoint II'''
*{{350}}, {{350C}}, {{355}}, {{355Cs}}, {{355C}}
*{{360}}, {{360Cs}}, {{360C}}, {{360P}}, {{360CSE}}, {{360CE}}, {{360PE}}
*{{370C}}
*{{500}}, {{510Cs}}
*{{555BJ}}
*{{720}}, {{720C}}
*{{700}}, {{700C}}
*{{750}}, {{750Cs}}, {{750C}}, {{750P}}
*{{755Cs}}, {{755C}}
'''TrackPoint III'''
*{{310}}, {{310D}}, {{310E}}, {{310ED}}
*{{345CS}}, {{345C}}
*{{365CS}}, {{365C}}, {{365CSD}}, {{365CD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}
*{{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{385D}}, {{385ED}}, {{385XD}}
*{{535}}, {{535E}}, {{535X}}
*{{560}}, {{560E}}, {{560X}}
*{{701C}}, {{701CS}}
*{{755CSE}}, {{755CE}}, {{755CX}}, {{755CV}}, {{755CD}}, {{755CDV}}
*{{760L}}, {{760LD}}, {{760C}}, {{760CD}}, {{760EL}}, {{760ELD}}, {{760E}}, {{760ED}}, {{760XL}}, {{760XD}}, {{765L}}, {{765D}}
*{{820}}, {{850}}, {{860}}
'''TrackPoint IV'''
*{{240}}, {{240X}}
*{{380Z}}, {{390}}, {{390E}}, {{390X}}
*{{560Z}}, {{570}}, {{570E}}
*{{600}}, {{600E}}, {{600X}}
*{{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
*{{I Series}}
*{{A Series}}
*{{G Series}}
*{{R Series}}
*{{S30}}, {{S31}}
*{{T Series}}
*{{X Series}}
*{{Z Series}}
*{{TransNote}}

==External Sources==
*[http://web.archive.org/web/20061010223935/http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51536 IBM's page on configuring the third TrackPoint button under Linux] (Note -- link was dead on 2 Dec 2007, replaced with Wayback link)

*[http://freshmeat.net/projects/tp-scroll/?topic_id=146 Thinkpad Scroll Daemon] Use the middle mouse button on a Trackpoint keyboard for scrolling in Linux.

[[Category:Glossary]] [[Category:Components]]

TrackPoint

2007-12-02T06:24:17Z

AlanHK: /* External Sources */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;" | [[Image:Trackpoint.jpg|IBM TrackPoint]] __NOTOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== IBM TrackPoint ===
The TrackPoint is IBMs name for the stick that sits between the g, h and b keys of the keyboard. It is used as a pointing device and hence as an alternative to an external mouse or a touchpad. What sets it apart from devices found in notebooks of other manufacturers is that it has no moving parts. It works using a solid state strain gauge. Its tap-to-click feature, which means that you can tap the stick to do a left click instead of using the left mouse button, is also handy.
</div>
|}

==Linux Support==
The TrackPoint uses the PS/2 interface so it is supported by the standard psaux mouse input driver included in the Linux kernel.

Note that the "IMPS/2" driver of the X server is incompatible with most TrackPoints. You'll have to use "PS/2" in the protocol option of your input section if your mouse pointer always jumps to the lower left corner of the screen. This seems to be solved with the T4x generation of ThinkPads.

However, to make use of advanced features like configuring sensitivity or enabling "tap-to-click" there are different solutions available depending on the kernel you are using.
* For 2.4 type kernels it is recommended to use the [http://www.slac.stanford.edu/~strauman/pers/tp4utils/ Linux Trackpoint utilities].
* 2.6.14rc1 and newer has TrackPoint support as part of the regular PS/2 Mouse support
* For older 2.6 kernels, you can get the [[Patch to enable advanced trackpoint configuration]].

If you are using GNOME with the 2.6 kernel TrackPoint support, you might want to use [http://tpctl.sourceforge.net/configure-trackpoint.html configure-trackpoint] as a graphical frontend to it.

*Have a look at [[How to configure the TrackPoint]].

==Models featuring this Technology==
'''TrackPoint'''
*ThinkPad {{220}} <tt>(if that's what the original trackpoint is)</tt>

'''TrackPoint II'''
*{{350}}, {{350C}}, {{355}}, {{355Cs}}, {{355C}}
*{{360}}, {{360Cs}}, {{360C}}, {{360P}}, {{360CSE}}, {{360CE}}, {{360PE}}
*{{370C}}
*{{500}}, {{510Cs}}
*{{555BJ}}
*{{720}}, {{720C}}
*{{700}}, {{700C}}
*{{750}}, {{750Cs}}, {{750C}}, {{750P}}
*{{755Cs}}, {{755C}}
'''TrackPoint III'''
*{{310}}, {{310D}}, {{310E}}, {{310ED}}
*{{345CS}}, {{345C}}
*{{365CS}}, {{365C}}, {{365CSD}}, {{365CD}}, {{365E}}, {{365ED}}, {{365X}}, {{365XD}}
*{{380}}, {{380D}}, {{380E}}, {{380ED}}, {{380XD}}, {{385D}}, {{385ED}}, {{385XD}}
*{{535}}, {{535E}}, {{535X}}
*{{560}}, {{560E}}, {{560X}}
*{{701C}}, {{701CS}}
*{{755CSE}}, {{755CE}}, {{755CX}}, {{755CV}}, {{755CD}}, {{755CDV}}
*{{760L}}, {{760LD}}, {{760C}}, {{760CD}}, {{760EL}}, {{760ELD}}, {{760E}}, {{760ED}}, {{760XL}}, {{760XD}}, {{765L}}, {{765D}}
*{{820}}, {{850}}, {{860}}
'''TrackPoint IV'''
*{{240}}, {{240X}}
*{{380Z}}, {{390}}, {{390E}}, {{390X}}
*{{560Z}}, {{570}}, {{570E}}
*{{600}}, {{600E}}, {{600X}}
*{{770}}, {{770E}}, {{770ED}}, {{770X}}, {{770Z}}
*{{I Series}}
*{{A Series}}
*{{G Series}}
*{{R Series}}
*{{S30}}, {{S31}}
*{{T Series}}
*{{X Series}}
*{{Z Series}}
*{{TransNote}}

==External Sources==
*[http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-51536 IBM's page on configuring the third TrackPoint button under Linux]

[[Category:Glossary]] [[Category:Components]]

How to reduce power consumption

2007-12-02T06:19:06Z

AlanHK: spelling

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel.
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. And you must enable it, either a boot time
by adding this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totally avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

Same for PCMCIA/Cardbus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems insufficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

Seel also [[How to enable AC97 power saving]].

==Wireless Interface==
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2007-12-02T06:15:25Z

AlanHK: typo

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power hungry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel.
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. And you must enable it, either a boot time
by adding this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totaly avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

Same for PCMCIA/Cardbus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems unsuficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

Seel also [[How to enable AC97 power saving]].

==Wireless Interface==
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2007-12-02T06:13:16Z

AlanHK: typo

Reducing system power consumption will extend battery life, reduce system
temperature and (on some models) reduce system fan noise.
Power consumption can be greatly improved from a stock distribution configuration
to a fine tuned system. The general rules are :
* Unload drivers for unused devices (ie. USB 1.1, Yenta/PCMCIA, Wireless, IRDA, Bluetooth, ...)
* Reduce polling on devices (drives, USB subsystem, nvram, use SATA AN, ...)
* Reduce hard drive activity
* Reduce LCD brightness to the minimum you can stand
* Reduce CPU wakeups, so it can stay longer in deep power saving c-states
* Make use of every hardware devices availables power saving features (AHCI ALPM, USB autosuspend, Alsa and Wireless powersaving modes, HPET timers, ...)

==Tools==
Arjan van de Ven's [[PowerTOP]] utility
is a gold mine to improve energy efficiency, but is almost only CPU-oriented. This tool helps to easily detect
the top power offenders, both userland and kernel modules, which prevent the use of CPU power saving mechanisms and sometime suggest
fixes accordingly.
PowerTOP users collected some [http://www.linuxpowertop.org/known.php tips & tricks]
and an informative [http://www.linuxpowertop.org/faq.php faq].

Alternatively (or complementary) to PowerTOP, running <code>strace -p $(pidof yourapp)</code>
for all your favorite or background running applications while they are expected to be
idle, will show the misbehaviors.

Beside CPU wakeups, disks spins are also power hungry. To detect what make your disk spinning,

<code>
sysctl vm.block_dump=1
</code>

will list all applications causing disks wakeups on the kernel's dmesg.
Other useful tools for this purpose are blktrace, iostat and lm-profiler
(from laptop-mode-tools suite).

See also [[#Misbehaving Userland]].

==BIOS settings==
Some Thinkpad BIOS (like 2.08 BIOS on {{X40}}) offer two very lame options,
with a very misleading online help (saying "Usually not needed"). That's

<code>
CPU power management: (default disabled)
PCI bus power management: (default disabled)
</code>

You should indeed ''enable'' them, else the deepest C3 and C4 ACPI C-states
are disabled.

==CPU==
Look at:
* [[How to make use of Dynamic Frequency Scaling]]
* [[Pentium M undervolting and underclocking]]

A good thing to keep in mind is that every CPU wakeup, even if it's for
a trivial light job, reduce the time the CPU stays on a deep power
saving C-state (like C3 or C4). Therefore you should ensure your applications
stay really idle when they meant to be idle (track shorts select timeouts
in loop, etc. with [[PowerTOP]]).

Also note that manually locking the CPU in the lowest P-state (frequency)
available is '''not''' an efficient way to improve battery lifetime. This will
cause the CPU to stay longer in C0 (power angry C-state) doing hard work when
there is something to do, while it could have done this work faster by augmenting
the CPU freq, and returned back faster to a deeper, economic, C-state and to a
lower frequency (P-state).
The best is to let the kernel select the appropriates CPU frequencies by itself
with the help of in kernel CPU governors.
Have a look at [http://www.bughost.org/pipermail/power/2007-May/000166.html this explanation]
from Intel's kernel developer Arjan van de Ven.

==Kernel settings and patches==

===General settings===
The 2.6.21 kernel brought some very effective changes (like dynticks).
Later, 2.6.24-rc2 brought a lot of other power efficiency improvements.
If it's not already on your distribution and you value power efficiency,
you may think about compiling a recent kernel yourself.

Here are a few options (beside the ACPI and APM related one) that matter to
reduce power consumption or to help diagnosing consumers:

<code>
# From PowerTOP's FAQ:
CONFIG_NO_HZ
CONFIG_HIGH_RES_TIMERS
CONFIG_HPET
CONFIG_HPET_TIMER
CONFIG_CPU_FREQ_GOV_ONDEMAND
CONFIG_USB_SUSPEND
CONFIG_SND_AC97_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=3
CONFIG_TIMER_STATS
CONFIG_ACPI_BATTERY
CONFIG_CPU_FREQ_STAT
CONFIG_INOTIFY

# Not from the PowerTOP FAQ:
CONFIG_BLK_DEV_IO_TRACE
CONFIG_X86_ACPI_CPUFREQ
CONFIG_X86_SPEEDSTEP_CENTRINO
CONFIG_X86_SPEEDSTEP_ICH
CONFIG_X86_SPEEDSTEP_SMI
CONFIG_CPU_IDLE
CONFIG_CPU_IDLE_GOV_LADDER
CONFIG_CPU_IDLE_GOV_MENU
</code>

Those options are already in Fedora Core 7 and Ubuntu Gutsy (not Feisty) default i686 kernels.
PowerTOP FAQ also suggest to '''disable'''
CONFIG_IRQBALANCE and CONFIG_ACPI_DEBUG.

Also, you need to properly set APM and ACPI. Look at:
* [[Power Management]]
* [[How to make use of Power Management features]]

=== Kernel boot and module loading options ===
If you have an Intel chipset > ICH3 (cf. lspci output), as in most modern Thinpads, you should
be using the integrated HPET timer (saves about 30 CPU wake ups per second). To see if
hpet is enabled on your laptop :

<code>
grep hpet /proc/timer_list
</code>

If this does not display "Clock Event Device: hpet", then add

<code>
hpet=force
</code>

to your kernel boot options (usualy in /boot/grub/menu.lst or lilo.conf).
Note that "hpet=force" is only available by default in 2.6.24-rc2 and above
(or as a separated patch for 2.6.22 and 2.6.23, see below).

===Useful Patches===

Thomas Gleixner High Resolution Timers (hrt) patchset brings many improvements,
like the cpuidle work and Udo A. Steinberg and Venki Pallipadi "force
enable HPET" patches (non HPET timers causes about 20-40 CPU wakeups/second, but
HPET is often hidden by the BIOS due to Windows XP deficiencies). Those are
fully merged in 2.6.24-rc1 vanilla kernel.
See http://www.tglx.de/projects/hrtimers/

Kristen Carlson Accardi from Intel has a patchset to turn on "Aggressive
Link Power Management" (ALPM) for the AHCI driver (for SATA bus). Also from
Accardi, SATA Asynchronous Notification (SATA AN), alows SATA link to notify
media insertions (thus avoid hal polling the cdrom). Those patches were merged
in 2.6.24-rc2 kernel.
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

The [[HDAPS]] disk protection systems can reduce battery life.
Matthew Garrett provides [http://www.linuxpowertop.org/patches/hdaps.patch a patch]
that prevents hdaps kernel module to generate interrupts when
this feature isn't used.

===Useful sysctls===
The meaning of those settings is explained case by case on the relevant
sections of this document. But for convenience sake, we group them here too.

Note that the "ondemand" scaling governor is recommended by Intel developers
for energy efficiency: it's expected to be more efficient than the "powersave"
governor, or than userspace daemons (like cpufreq-utils, cpufreqd, powernowd...).
Look [http://www.bughost.org/pipermail/power/2007-May/000071.html here],
[http://www.bughost.org/pipermail/power/2007-May/000073.html here], or
[http://www.bughost.org/pipermail/power/2007-May/000166.html here] for a
kernel developer explanation about "ondemand" being better on modern Intel CPUs.

The "link_power_management_policy" tunable won't be available unless you
run a 2.6.24-rc2 or more kernel, or applied Kirsten patchset, have an Intel
AHCI compatible chipset, and use SATA drives.

<code>
echo 5 > /proc/sys/vm/laptop_mode
echo 0 > /proc/sys/kernel/nmi_watchdog
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > $i; done
# those sysctl's are only available if you have an AHCI compatible SATA
# controler and use kernel > 2.6.24-rc2 (or use Kristen ALPM patchset) :
echo min_power > /sys/class/scsi_host/host0/link_power_management_policy
echo min_power > /sys/class/scsi_host/host1/link_power_management_policy
</code>

If you're running a kernel older than 2.6.22 do this. Not needed for kernels 2.6.22 onward:

<code>
cd /sys/devices/system/cpu/cpu0/cpufreq
cat ondemand/sampling_rate_max > ondemand/sampling_rate
</code>

==ATA drives==
Hard drives and CDRom drives spinning is very costly. To improve battery
lifetime, you should reduce disks access (or devices polling) the more you
can.

===Hard Drives===
The files access time update, while mandated by POSIX, is causing lots of
disks access; even accessing files on disk cache may wake the ATA or USB
bus. If you don't use this feature, disable it via:

<code>
mount -o remount,noatime / # and so on for all mounted fs
</code>

The laptop_mode reduce disk usage by regrouping writes. You should enable
it, at least while on battery. See [[Laptop-mode]] for more details:

<code>
echo 5 > /proc/sys/vm/laptop_mode
</code>

The default kernel dirty page writeback frequency is very conservative. On
a laptop running on battery, one might find more appropriate to reduce it:

<code>
echo 1500 > /proc/sys/vm/dirty_writeback_centisecs
</code>

Some power saving hard drives features can be activated with hdparm (beware
that "-B 1" may reduce your drive lifetime, if you have lot of intermittent
disk activity causing lots of heads load/unloads: so reduce I/O activity first,
as explained above, in order to get longer disks idling periods).
For more details look at [[How to make use of Power Management features]] :

<code>
hdparm -B 1 -S 12 /dev/sda # and/or any other disk device
</code>

===Optical drive===
The optical drive is reported to consume power even when not accessed. See

* [[How to hotswap UltraBay devices|Eject the UltraBay optical drive]], or just turn off its power supply (i.e., run the appropriate eject script but leave the drive inserted).
* [[How to set optical drive speed|Reduce the spinning speed of the optical drive]].

The hald daemon polling tends to maintain the ATA buses out of power saving
modes, and to wakeup CDROM drive (except if you have a kernel >= 2.6.24, hal >= 0.5.10,
and SATA AN compatible devices). If you have a recent hald version, you
can stop this polling when on battery:

<code>
hal-disable-polling /dev/scd0 # or whatever your CD drive is
</code>

If your hald is not recent enough, consider suspending it when running on battery. Some moderns SATA buses and drivers supports a notification mechanism (SATA AN - Asynchronous Events Notifications) that obsolete the need for polling on modern hardware; support for this feature had been merged in Linux 2.6.24-rc1 and HAL 0.5.10.

==LCD Backlight/Brightness==
The LCD backlight is one of the very major power drain.
Reducing brightness to the lowest readable
level will save a lot of battery lifetime. Also, don't forget to configure
your screen saver to shutdown the screen backlight (rather than displaying some
eye candy), when no activity for a few minutes.

You can also let the system [[automatically reduce brightness]] after a
period of inactivity.

If you're choosing your Thinkpad laptop model, keep in mind that the screen
size affect the battery time greatly: more power needed for larger screens.

The very recent, but xorg standard way to control backlight from CLI is
using xbacklight. ie. to set backlight at half the brightness:

<code>
xbacklight -set 50
</code>

You should configure the DPMS to shutdown the screen when idle (rather than
displaying a fancy but power consuming screensaver). ie. to turn off the
display after 5mn of idling:

<code>
xset +dpms
xset dpms 0 0 300
</code>

==Graphic controllers==
All xorg Thinkpad graphics chipsets drivers (ati, radeon, fglrx, i810) have
the same bug causing very frequent CPU wakeups when DRI is activated, even
when you don't use any 3D application.
This problem is partly fixed on xorg git tree but not released as of xorg
7.2. If you value more battery than 3D, you should disable DRI: put this on
the /etc/X11/xorg.conf "Device" of you graphic controller:

<code>
Option "NoDRI"
</code>

Also be sure that DPMS is working: <code>grep DPMS /var/log/Xorg.0.log</code>
should output "DPMS enabled". If not, put <code>Option "DPMS"</code> in your config.
See the section above about how to enable dpms driven display power saving.

On recent xrandr/xorg versions, you can disable the TV output (or any other detected
as connected but not used outputs) when you're not using it: it's known to consume power.

<code>
xrandr # see all displays listed here, but that you don't actually use and disable them.
xrandr --output TV -off # for instance (if "xrandr" above listed a connected output named "TV" that you don't use)
</code>

When you don't have an external monitor plugged, disable CRT and DVI output
(for some, this can make a difference in power usage) :
<code>
echo crt_disable > /proc/acpi/ibm/video
echo dvi_disable > /proc/acpi/ibm/video
</code>

Some drivers have specials power saving mode, and/or allows underclocking the GPU. See also:
* [[How to make use of Graphics Chips Power Management features]], or with [[Rovclock]] on ATI.
* [[Problem with high power drain in ACPI sleep]]

==USB Subsystem==
The kernel support an efficient USB 2.0 power saving feature if you enabled
CONFIG_USB_SUSPEND. This may not trigger in when you have an USB device
plugged (and beside, USB devices tends to suck power on their own), so avoid
using such devices when on battery. And you must enable it, either a boot time
by adding this in the kernel boot options (ie. in grub's menu.lst):

<code>
usbcore.autosuspend=1
</code>

or at runtime, per device, with:

<code>
for i in /sys/bus/usb/devices/%s/power/autosuspend; do echo 1 > $i; done
</code>

USB 1.1 is worst. It needs polling the bus frequently, hence can't really go
in a low power mode when you enabled it, even if you don't have any device
plugged. You'd better remove it when you don't use a 1.1 device:

<code>
rmmod uhci_hcd
</code>

If you don't intend to use any device needing USB 1.1 (unfortunately, the built-in bluetooth and fingerprint-reader are USB 1.1 devices), the USB 1.1 support can also be totaly avoided. On Debian and derivatives, just do:

<code>
echo "blacklist uhci_hcd" >> /etc/modprobe.d/blacklist
</code>

Same for PCMCIA/Cardbus. Some users experiences interrupts clouds (sometime up to
several thousands interrupts/second) causing CPU wakeups, thus totally preventing
the CPU to reach lower C-states.
If you don't use PCMCIA, you may disable it the same way (unloading seems unsuficient
to restore the system properly, you have to boot without it):

<code>
echo "blacklist pcmcia" >> /etc/modprobe.d/blacklist
echo "blacklist yenta_socket" >> /etc/modprobe.d/blacklist
</code>

==Sound==
ALSA has a power saving feature that should be enabled on your kernel
(CONFIG_SND_AC97_POWER_SAVE). Note that this low power mode won't trigger in
unless you muted all sound inputs (micro, line in etc.). This feature has
to be activated with:

<code>
amixer set Line mute nocap
amixer set Mic mute nocap
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
</code>

More radical: you can unload all sound related modules when you are on
battery, or mute the sound system (echo mute > /proc/acpi/ibm/volume).

Seel also [[How to enable AC97 power saving]].

==Wireless Interface==
Wireless network consume a lot of power.
To save power, you can kill the Wi-Fi radio when it's not in use:

<code>
echo 1 > /sys/bus/pci/devices/*/rf_kill
</code>

If you need Wi-Fi, you can also reduce power consumption (at the price of
performances) by activating the power saving modes:

<code>
iwpriv eth1 set_power 5
</code>

For drivers using the new Wi-Fi kernel framework (mac80211/cfg80211),
the canonical way to do this is now:

<code>
for i in /sys/bus/pci/devices/*/power_level ; do echo 5 > $i ; done
</code>

Most drivers, like ipw2200, that don't use the new mac80211 framework place the
interfaces in aggressive scanning mode when they are not associated with any
Access Point, even when the interface is down (more info about this on Intel's
[http://www.lesswatts.org/tips/wireless.php LessWatts] website).
This behavior consumes a lot of power, even more than when the interface
is plain active and in use. But this can disabled at module's load time :

<code>
rmmod ipw2200
modprobe ipw2200 associate=0
</code>

You can fix this setting by placing the following in /etc/modprobe.d/options
(Debian/Ubuntu) or in /etc/modprobe.conf (Red Hat/Fedora):

<code>
options ipw2200 associate=0
</code>

Reducing beacon intervals on your Access Point to 1 per second will also
reduce network card interrupts, therefore power savings. This shouldn't have
negatives side effects.

See also, to activate power saving on the wireless network card:
* For [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]] and [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]], see instructions for the [[ipw2200]] driver.
* For [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]], see the [http://ipw3945.sourceforge.net/README.ipw3945 ipw3945 driver README]

==Ethernet Controler==
If you don't use Wake-on-LAN, you should disable it for your network card,
because it sucks a lot of power:

<code>
ethtool -s eth0 wol d
</code>

If you can, try to reduce useless network activity on your ethernet
segment, coming to your NIC (ie. uneeded broadcasts), those cause
interrupts and CPU wakeups.

Forcing 100Mbps full-duplex speed on a gigabit ethernet NIC can also save a lot of power (~1W) on most network workloads. This also reduces components temperature (e.g., [[Thermal Sensors|thermal sensor]] 0xC0 on the {{T43}} cools down by 5 degree between 1000Mbps and 100Mbps, and another 1 degree for 10Mbps).

<code>
ethtool -s eth0 autoneg off speed 100
</code>

Note, however, that if the network device on the other side has auto-negotiation enabled (which is very common) and you turn auto-negotiation off, the other side will assume half-duplex mode and you will experience a significant loss of performance.

==Bluetooth==
When you don't need bluetooth, disable it. Because of its radio,
bluetooth is not power friendly.

<code>
hciconfig hci0 down ; rmmod hci_usb
echo disable > /proc/acpi/ibm/bluetooth
</code>

==Modem==
When was the last time you used your analog modem? If you can't remember, you probably just don't need it. If it is on a separate module in your laptop, simply remove it. Store it in a ESD safe place (like the bag in which your last addon card or hard drive was packed), in case you should need it again. This won't save you a lot of power and weight, but why carry something around you never use.

==System Fans==
Fans consumes power when running, so you may look at the [[ACPI fan control script]].

==Misbehaving Userland==
You should avoid using Beagle, Compiz, Beryl, XMMS, gnome-power-manager
and Evolution while on battery.
Look at the PowerTOP's [http://www.linuxpowertop.org/known.php known problems]
list.

Deactivate desktop animations (blinking cursor on the terms, animated wallpapers, ...): they cause regular X (therefore kernel and CPU) wakeups.

In short, while on battery, you should stop all applications that don't really stay idle when you're not using them. This means applications that:
* Wakes up the CPU too often (by polling something, because of too short select() timeouts, ...)
* Access the disks at regular intervals
* Access an hardware bus (USB, ATA, ...) at regular intervals
To find those offenders run:
* <code>strace -p $(pidof yourapp)</code> # for all your running applications
* <code>powertop</code>
* <code>sysctl vm.block_dump=1</code> # and look at dmesg
* <code>ps aux | awk '{print$10,$11}' | sort -n</code> # will list all running softs sorted by used cpu time
Please, don't forget to fill a bug when you find such a misbehaving software.
{{NOTE|Not all software is evil, buggy or badly written. Some produce regular activity because they have to, in order to provide their intented functionality. Think twice before filling bugs about this.}}

==See Also==
* [[How to measure power consumption]]
* [[Script for monitoring power consumption]]
* Battery [[maintenance]]

==External resources==
* [http://www.free-it.de/archiv/talks_2005/paper-11017/paper-11017.html ''Current trends in Linux Kernel Power Management''], Dominik Brodowski, 2005
* [http://www.linuxpowertop.org PowerTOP] website
* [http://www.gentoo.org/doc/en/power-management-guide.xml Power Management Guide] from the Gentoo Linux documentation
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/2005-November/030478.html When/where/what for low power consumption?] (thread on Linux-Thinkpad)
* Intel's [http://www.lesswatts.org/ LessWatts] "''Saving power on Linux''" website
* ''8 hours of battery life on your lap(top)'' ([http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.odp ODP]/[http://atrey.karlin.mff.cuni.cz/~pavel/swsusp/8hours.pdf PDF]), a presentation by Pavel Machek

[[Category:600X]] [[Category:A20m]] [[Category:A20p]] [[Category:A21e]] [[Category:A21m]] [[Category:A21p]] [[Category:A22e]] [[Category:A22m]] [[Category:A22p]] [[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:i1200]] [[Category:i1300]] [[Category:i1620]] [[Category:G40]] [[Category:G41]] [[Category:R30]] [[Category:R31]] [[Category:R32]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50e]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:R60]] [[Category:R60e]] [[Category:T20]] [[Category:T21]] [[Category:T22]] [[Category:T23]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Installation on ThinkPads without CD-ROM drive

2007-12-02T06:09:31Z

AlanHK: /* Installation from the internal harddrive */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPads (e.g. the whole X series) come without a CD-ROM drive by default. Even though there are options to buy a solution like the UltraBase, a full dock or simply an external CD-ROM drive{{footnote|1}}, this is not the cheapest option and might not always be necessary. Also, with some external CD-ROMs the problem might arise that the ThinkPad is not able to boot from them. See our [[Supported Boot Devices|List of supported boot devices]] for various ThinkPads.

So the question arises how to get your system of choice onto that precious piece of hardware. This page should tell you about the possible solutions.

Since in most cases the installation base packages come on CD, you'll need a second computer, equipped with a CD-ROM drive, for all of those solutions.

Many older ThinkPads came with only a floppy drive and cannot boot from any CD drive at all. For those machines, booting from floppy is the only option. Then one can install from CD, over a network, or from the hard drive.
|}

==Installation from USB drive==
{{NOTE|Not all ThinkPads have a BIOS that [[Supported_Boot_Devices|supports USB booting]].}}

This is probably the easiest approach:
#Connect the USB drive{{footnote|2}} to the host and format it.
#Get a bootable system and all needed installation files onto the USB drive, i.e. by copying the complete filesystem from your installation CD-ROM to the USB drive. Of course if your USB drive is not big enough for that you'll have to make more sophisticated choices about what to copy and what to leave behind. Here are [http://wiki.debian.org/BootUsb some instructions] for converting a LiveCD ISO image onto a pen drive, and making it bootable.{{footnote|3}}

#Insert the USB drive into the USB port of your ThinkPad.
#Power on the ThinkPad and press F12 to get to the boot menu. For some models (X24 comes to mind) you need to go into the BIOS and change the boot sequence before USB devices are shown in the boot menu.
#Select the USB drive as boot media and boot.
#Follow the normal installation process.

It seems some ThinkPad BIOSes don't use the code on the master boot record (MBR), or at least skip it when it is blank. These systems will need an [http://www.tsden.org/ryutaroh/extipl/ Extended-IPL boot loader]. Putting this Extended-IPL boot loader onto the disk (such as <tt>sda</tt>) goes something like this:

dd if=/dev/zero of=/dev/sda bs=1 count=446
dd if=/usr/lib/extipl/aldebaran.bin of=/dev/sda

==Installation via network boot==
Thinkpads support PXE to boot off another system that is connected via [[Ethernet]]. In this case the ThinkPad acts as a network boot client, the other system as server. The idea is to boot a system on the server that the ThinkPad can boot into then by loading all required data directly from that server.

For this to work you will have to either have both the server and the ThinkPad connected in the same subnet of your LAN, or have them connected directly via a crossed Ethernet cable.

===Using Windows as a server===
To get your Thinkpad to boot over a network, you must set up a DHCP and a TFTP server. For Windows, the freeware program [http://tftpd32.jounin.net TFTPD32] does both. To set up TFTPD32, do the following:
#Create a directory that will contain the PXE boot code.
#Copy the boot code into that directory. (For a Debian Sarge install, for example, you can find code to initiate a network install under <code>debian/dists/sarge/main/installer-i386/current/images/netboot/</code> from a Debian mirror -- copy files to simulate symlinks for <code>pxelinux.0</code> and <code>pxelinux.cfg/</code>)
#Launch the TFTPD32 program.
#"Browse" to set the current directory to the directory containing the PXE boot code (i.e. the directory you created in the first step, above).
#On the DHCP server tab, set:
##<code>IP pool starting address</code> to something appropriate for your network
##<code>Size of pool</code> to a non-zero value (all you really need is 1)
##<code>Boot file</code> to the PXE boot image (for Debian, the filename is <code>pxelinux.0</code>)
##<code>WINS/DNS Server</code> to the DNS server used by your network
##<code>Default router</code> to the IP of your default gateway
##<code>Mask</code> to your network's netmask
##<code>Domain Name</code> to your network's domain
{{NOTE|Do <em>not</em> under any circumstances run the DHCP server if there are other DHCP servers on your network. There must be only one DHCP server on each network segment. You must either disable the other server or move to another network.}}

On your ThinkPad, do the following:
#Boot your Thinkpad, and press {{key|F12}} to select an alternate boot device
#Use "<code>Intel(R) Boot Agent Version 4.0.17</code>" (or similar -- on the Transnote used to make this guide, "<code>Network Boot</code>" did not work while the "<code>Boot Agent</code>" option did)

The TFTPD32 server window should show activity as the ThinkPad downloads files. Once the first stage has installed and the ThinkPad is ready to boot from its own hard drive, shut down TFTPD32 and re-enable your permanent DHCP server.

===Using [[:Category:Knoppix|Knoppix]] as a Terminal Server===
If a server system is available on the network, it can be used to set up a temporary Terminal Server. Follow these steps to set up the Terminal Server using Knoppix:
#Insert the Knoppix CD into the server and boot it up. Make sure to boot with the 2.6 kernel by giving the <code>kernel26</code> boot option.
#Once your KDE desktop is loaded, look in the K-Menu hierarchy for the link to the terminal server setup. Select this menu option.
#Launch the Terminal Server and make it use the appropriate network device.
Back at your ThinkPad, do the following:
#Power on your ThinkPad and press F12 to get to the boot menu.
#Select the ThinkPad's network adapter as the boot media.
#Reboot. The ThinkPad should now boot from the Knoppix Terminal Server directly.

===Using any Linux on the server side===
{{Todo|needs better formating, maybe a list where to find the kernel/initrd images on other distros and a hint to speed up booting}}

# TFTP Server
#* Download and install an tftp Server
#* Configure it to serve {{path|/tftpboot}}
# Get the kernel and initrd image from your distribution
#* For fedora-core they are in {{path|os/images/pxeboot}}
#* Copy both to {{path|/tftpboot/vmlinuz}} resp. {{path|/tftpboot/initrd.img}}
# [http://www.kernel.org/pub/linux/boot/syslinux/ Bootloader]
#* Download the current syslinux-X.YZ.tar.bz2 tarball
#* Copy the included pxelinux.0 to {{path|/tftpboot/pxelinux.0}}
#* Create a directory for the configuration with {{cmdroot|mkdir /tftpboot/pxelinux.cfg}}
#* Create the file {{path|/tftpboot/pxelinux.cfg/default}} with the following contents:
DEFAULT install
PROMPT 1
TIMEOUT 0
LABEL install
kernel vmlinuz
append initrd=initrd.img --
# DHCP Server
#* Download and install an DHCP Server
#* Configure it to for your Thinkpad, the following configuration assumes that the MAC-address of your Thinkpad is DE:AD:BE:EF:00:00 and should use the IP 192.168.0.2 with namesever/router/tftpserver 192.168.0.1
allow booting;
allow bootp;
host thinkpad {
hardware ethernet DE:AD:BE:EF:00:00;
fixed-address 192.168.0.2;
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
default-lease-time 28800;
filename "pxelinux.0";
next-server 192.168.0.1;
}
#* Now you can boot your thinkpad via lan

==Installation from the internal harddrive==
The idea here is to have all required files already on the internal harddrive when you power up your ThinkPad for installation, including of course a minimal system to boot up and start the installation process.

Convenient, but how do you get the files there?
*One option is to copy them via network boot (see above).
*Some Linux distributions offer ways to download the installation files from a FTP server and to choose this directory as installation source instead of a CD-ROM.
*A second way, if you already have a 'working' copy of DOS or MS Windows installed, is to start the installer from loadlin or GRUB. This is detailed [http://marc.herbert.free.fr/linux/win2linstall.html here].
*Another one is to remove the harddrive from the ThinkPad and connect it to the other machine. Again, this can be achieved in several ways:
**putting the harddrive into an UltraBay secondary HDD adapter of a second ThinkPad
**putting the harddrive into an external casing and connect it to the second machine via USB, PCMCIA or whatever
**connecting the harddrive via a 2.5" (laptop) to 3.5" (desktop) harddrive adapter

Follow one of the following instructions.

===Installing [[:Category:Windows|Windows]] 2000 or XP===
*Attach the harddrive to the host computer and install a minimal bootable DOS system i.e. by booting a Win98 Emergency Boot Disk and performing the command "SYS X:" (where X = the laptop's harddrive).
*Copy FDISK.EXE to the laptop harddrive.
*Return the harddrive to the laptop and boot to DOS. (If you have Win98 installed by default, you can skip the first two steps and simply reboot in Windows to DOS.)
*Run FDISK and set up your new Windows system partition on this laptop. (If you do not do this on the laptop, after reboot you will receive the infamous "NTLDR IS MISSING" error. This error may still occur if the partition is greater than 7.8gb in size)
*Then return the drive to the host and format the drive as FAT32. (DO NOT format as NTFS.)
*Repeat the "SYS X:" step to make the new partition bootable.
*Copy Himem.sys and Config.sys, too. Otherwise SMARTDRIVE.EXE won't run
*Get SMARTDRV.EXE from the internet and copy it to your Thinkpads harddrive.
*Also, from the Win2K or WinXP CD, copy the I386 folder to the harddrive.
*Return the laptop's harddrive to the Thinkpad one final time and boot to DOS.
*Run SMARTDRV.EXE first, then change directories to I386 and run WINNT.EXE, this will allow the installation to begin.
*During installation, choose NOT to format the destination partition, since it contains the installation files. If you want that filesystem to be NTFS you can convert it after installation from within Windows.

==Installation from Diskette==
===Installing from CD===
Many distributions have software on CD that will make a boot floppy that will allow you to install from an unbootable CD drive.

===Installing over a network===
Some distributions have a set of diskettes that will allow you to boot a machine, enable a network device and start installation over a network. For example, {{Slackware}} supports installing via an NFS mount. An unofficial add-on adds an option to install over FTP.

===Installing from floppy===
Some distributions did allow for a complete installation from diskette. As the size of distributions and the number of required diskettes has grown, and the ubiquity of optical storage increased, support for floppy installation has diminished.

However, there are still some Linux distributions that fit on as few as one diskette - with very limited functionality, of course.

==Installation from an ISO image==
Some distributions offer a way of installing directly from the downloadable ISO image, residing on your harddisk. Examples are VectorLinux 5.1 and {{SUSE}} 10. The individual distributions installation manuals will guide you through the process.

==External Sources==
*[http://www.gentoo.org/doc/en/altinstall.xml Gentoo alternative installation method HOWTO]

{{footnotes|
#External CD-ROM drives typically are connected through USB or [[PCMCIA]]. Be aware that not all of these drives are [[Supported Boot Devices|capable of booting]]. USB connected drives are more likely to be bootable on a ThinkPad than PCMCIA connected ones.
#USB drive here means any kind of USB connected bootable data storage device, including external harddisk drives, memory card readers or pendrives.
#Most USB keys are already bootable. If it won't work, use lilo to write to the USB key's MBR: See the section "Master Boot Record" [http://wiki.debian.org/BootUsb here].
}}

[[Category:TransNote]] [[Category:560]] [[Category:560E]] [[Category:560X]] [[Category:560Z]] [[Category:570]] [[Category:570E]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Knoppix]]

Installation on ThinkPads without CD-ROM drive

2007-12-02T06:07:08Z

AlanHK: spelling

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
Some ThinkPads (e.g. the whole X series) come without a CD-ROM drive by default. Even though there are options to buy a solution like the UltraBase, a full dock or simply an external CD-ROM drive{{footnote|1}}, this is not the cheapest option and might not always be necessary. Also, with some external CD-ROMs the problem might arise that the ThinkPad is not able to boot from them. See our [[Supported Boot Devices|List of supported boot devices]] for various ThinkPads.

So the question arises how to get your system of choice onto that precious piece of hardware. This page should tell you about the possible solutions.

Since in most cases the installation base packages come on CD, you'll need a second computer, equipped with a CD-ROM drive, for all of those solutions.

Many older ThinkPads came with only a floppy drive and cannot boot from any CD drive at all. For those machines, booting from floppy is the only option. Then one can install from CD, over a network, or from the hard drive.
|}

==Installation from USB drive==
{{NOTE|Not all ThinkPads have a BIOS that [[Supported_Boot_Devices|supports USB booting]].}}

This is probably the easiest approach:
#Connect the USB drive{{footnote|2}} to the host and format it.
#Get a bootable system and all needed installation files onto the USB drive, i.e. by copying the complete filesystem from your installation CD-ROM to the USB drive. Of course if your USB drive is not big enough for that you'll have to make more sophisticated choices about what to copy and what to leave behind. Here are [http://wiki.debian.org/BootUsb some instructions] for converting a LiveCD ISO image onto a pen drive, and making it bootable.{{footnote|3}}

#Insert the USB drive into the USB port of your ThinkPad.
#Power on the ThinkPad and press F12 to get to the boot menu. For some models (X24 comes to mind) you need to go into the BIOS and change the boot sequence before USB devices are shown in the boot menu.
#Select the USB drive as boot media and boot.
#Follow the normal installation process.

It seems some ThinkPad BIOSes don't use the code on the master boot record (MBR), or at least skip it when it is blank. These systems will need an [http://www.tsden.org/ryutaroh/extipl/ Extended-IPL boot loader]. Putting this Extended-IPL boot loader onto the disk (such as <tt>sda</tt>) goes something like this:

dd if=/dev/zero of=/dev/sda bs=1 count=446
dd if=/usr/lib/extipl/aldebaran.bin of=/dev/sda

==Installation via network boot==
Thinkpads support PXE to boot off another system that is connected via [[Ethernet]]. In this case the ThinkPad acts as a network boot client, the other system as server. The idea is to boot a system on the server that the ThinkPad can boot into then by loading all required data directly from that server.

For this to work you will have to either have both the server and the ThinkPad connected in the same subnet of your LAN, or have them connected directly via a crossed Ethernet cable.

===Using Windows as a server===
To get your Thinkpad to boot over a network, you must set up a DHCP and a TFTP server. For Windows, the freeware program [http://tftpd32.jounin.net TFTPD32] does both. To set up TFTPD32, do the following:
#Create a directory that will contain the PXE boot code.
#Copy the boot code into that directory. (For a Debian Sarge install, for example, you can find code to initiate a network install under <code>debian/dists/sarge/main/installer-i386/current/images/netboot/</code> from a Debian mirror -- copy files to simulate symlinks for <code>pxelinux.0</code> and <code>pxelinux.cfg/</code>)
#Launch the TFTPD32 program.
#"Browse" to set the current directory to the directory containing the PXE boot code (i.e. the directory you created in the first step, above).
#On the DHCP server tab, set:
##<code>IP pool starting address</code> to something appropriate for your network
##<code>Size of pool</code> to a non-zero value (all you really need is 1)
##<code>Boot file</code> to the PXE boot image (for Debian, the filename is <code>pxelinux.0</code>)
##<code>WINS/DNS Server</code> to the DNS server used by your network
##<code>Default router</code> to the IP of your default gateway
##<code>Mask</code> to your network's netmask
##<code>Domain Name</code> to your network's domain
{{NOTE|Do <em>not</em> under any circumstances run the DHCP server if there are other DHCP servers on your network. There must be only one DHCP server on each network segment. You must either disable the other server or move to another network.}}

On your ThinkPad, do the following:
#Boot your Thinkpad, and press {{key|F12}} to select an alternate boot device
#Use "<code>Intel(R) Boot Agent Version 4.0.17</code>" (or similar -- on the Transnote used to make this guide, "<code>Network Boot</code>" did not work while the "<code>Boot Agent</code>" option did)

The TFTPD32 server window should show activity as the ThinkPad downloads files. Once the first stage has installed and the ThinkPad is ready to boot from its own hard drive, shut down TFTPD32 and re-enable your permanent DHCP server.

===Using [[:Category:Knoppix|Knoppix]] as a Terminal Server===
If a server system is available on the network, it can be used to set up a temporary Terminal Server. Follow these steps to set up the Terminal Server using Knoppix:
#Insert the Knoppix CD into the server and boot it up. Make sure to boot with the 2.6 kernel by giving the <code>kernel26</code> boot option.
#Once your KDE desktop is loaded, look in the K-Menu hierarchy for the link to the terminal server setup. Select this menu option.
#Launch the Terminal Server and make it use the appropriate network device.
Back at your ThinkPad, do the following:
#Power on your ThinkPad and press F12 to get to the boot menu.
#Select the ThinkPad's network adapter as the boot media.
#Reboot. The ThinkPad should now boot from the Knoppix Terminal Server directly.

===Using any Linux on the server side===
{{Todo|needs better formating, maybe a list where to find the kernel/initrd images on other distros and a hint to speed up booting}}

# TFTP Server
#* Download and install an tftp Server
#* Configure it to serve {{path|/tftpboot}}
# Get the kernel and initrd image from your distribution
#* For fedora-core they are in {{path|os/images/pxeboot}}
#* Copy both to {{path|/tftpboot/vmlinuz}} resp. {{path|/tftpboot/initrd.img}}
# [http://www.kernel.org/pub/linux/boot/syslinux/ Bootloader]
#* Download the current syslinux-X.YZ.tar.bz2 tarball
#* Copy the included pxelinux.0 to {{path|/tftpboot/pxelinux.0}}
#* Create a directory for the configuration with {{cmdroot|mkdir /tftpboot/pxelinux.cfg}}
#* Create the file {{path|/tftpboot/pxelinux.cfg/default}} with the following contents:
DEFAULT install
PROMPT 1
TIMEOUT 0
LABEL install
kernel vmlinuz
append initrd=initrd.img --
# DHCP Server
#* Download and install an DHCP Server
#* Configure it to for your Thinkpad, the following configuration assumes that the MAC-address of your Thinkpad is DE:AD:BE:EF:00:00 and should use the IP 192.168.0.2 with namesever/router/tftpserver 192.168.0.1
allow booting;
allow bootp;
host thinkpad {
hardware ethernet DE:AD:BE:EF:00:00;
fixed-address 192.168.0.2;
option domain-name-servers 192.168.0.1;
option routers 192.168.0.1;
default-lease-time 28800;
filename "pxelinux.0";
next-server 192.168.0.1;
}
#* Now you can boot your thinkpad via lan

==Installation from the internal harddrive==
The idea here is to have all required files allready on the internal harddrive when you power up your ThinkPad for installation, including of course a minimal system to boot up and start the installation process.

Convenient, but how do you get the files there?
*One option is to copy them via network boot (see above).
*Some Linux distributions offer ways to download the installation files from a FTP server and to choose this directory as installation source instead of a CD-ROM.
*A second way, if you already have a 'working' copy of DOS or MS Windows installed, is to start the installer from loadlin or GRUB. This is detailed [http://marc.herbert.free.fr/linux/win2linstall.html here].
*Another one is to remove the harddrive from the ThinkPad and connect it to the other machine. Again, this can be achieved in several ways:
**putting the harddrive into an UltraBay secondary HDD adapter of a second ThinkPad
**putting the harddrive into an external casing and connect it to the second machine via USB, PCMCIA or whatever
**connecting the harddrive via a 2.5" (laptop) to 3.5" (desktop) harddrive adapter

Follow one of the following instructions.

===Installing [[:Category:Windows|Windows]] 2000 or XP===
*Attach the harddrive to the host computer and install a minimal bootable DOS system i.e. by booting a Win98 Emergency Boot Disk and performing the command "SYS X:" (where X = the laptop's harddrive).
*Copy FDISK.EXE to the laptop harddrive.
*Return the harddrive to the laptop and boot to DOS. (If you have Win98 installed by default, you can skip the first two steps and simply reboot in Windows to DOS.)
*Run FDISK and set up your new Windows system partition on this laptop. (If you do not do this on the laptop, after reboot you will receive the infamous "NTLDR IS MISSING" error. This error may still occur if the partition is greater than 7.8gb in size)
*Then return the drive to the host and format the drive as FAT32. (DO NOT format as NTFS.)
*Repeat the "SYS X:" step to make the new partition bootable.
*Copy Himem.sys and Config.sys, too. Otherwise SMARTDRIVE.EXE won't run
*Get SMARTDRV.EXE from the internet and copy it to your Thinkpads harddrive.
*Also, from the Win2K or WinXP CD, copy the I386 folder to the harddrive.
*Return the laptop's harddrive to the Thinkpad one final time and boot to DOS.
*Run SMARTDRV.EXE first, then change directories to I386 and run WINNT.EXE, this will allow the installation to begin.
*During installation, choose NOT to format the destination partition, since it contains the installation files. If you want that filesystem to be NTFS you can convert it after installation from within Windows.

==Installation from Diskette==
===Installing from CD===
Many distributions have software on CD that will make a boot floppy that will allow you to install from an unbootable CD drive.

===Installing over a network===
Some distributions have a set of diskettes that will allow you to boot a machine, enable a network device and start installation over a network. For example, {{Slackware}} supports installing via an NFS mount. An unofficial add-on adds an option to install over FTP.

===Installing from floppy===
Some distributions did allow for a complete installation from diskette. As the size of distributions and the number of required diskettes has grown, and the ubiquity of optical storage increased, support for floppy installation has diminished.

However, there are still some Linux distributions that fit on as few as one diskette - with very limited functionality, of course.

==Installation from an ISO image==
Some distributions offer a way of installing directly from the downloadable ISO image, residing on your harddisk. Examples are VectorLinux 5.1 and {{SUSE}} 10. The individual distributions installation manuals will guide you through the process.

==External Sources==
*[http://www.gentoo.org/doc/en/altinstall.xml Gentoo alternative installation method HOWTO]

{{footnotes|
#External CD-ROM drives typically are connected through USB or [[PCMCIA]]. Be aware that not all of these drives are [[Supported Boot Devices|capable of booting]]. USB connected drives are more likely to be bootable on a ThinkPad than PCMCIA connected ones.
#USB drive here means any kind of USB connected bootable data storage device, including external harddisk drives, memory card readers or pendrives.
#Most USB keys are already bootable. If it won't work, use lilo to write to the USB key's MBR: See the section "Master Boot Record" [http://wiki.debian.org/BootUsb here].
}}

[[Category:TransNote]] [[Category:560]] [[Category:560E]] [[Category:560X]] [[Category:560Z]] [[Category:570]] [[Category:570E]] [[Category:X20]] [[Category:X21]] [[Category:X22]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:Knoppix]]