ThinkWiki - User contributions [en]

Qualcomm Gobi 2000

2011-07-20T12:38:54Z

Dag-: Added /qb switch (without I get a GUI and eventually it failed)

__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;">
=== Qualcomm Gobi 2000 ===
This is a Qualcomm WWAN Adapter that is installed in a Mini-PCI Express slot

{{NOTE|Specific versions of this card may come pre-configured for a certain carrier (AT&T, Verizon, Vodafone UK)}}

=== Features ===
* Chipset: Qualcomm Gobi 2000
* USB ID: 05c6:9204 (loader)
* USB ID: 05c6:9205 (modem)
* EV-DO/CDMA (800 & 1900Mhz)
* GSM/GPRS/EDGE (850, 900, 1800 & 1900MHz)
* HSPA/UMTS (800, 850, 900, 1900 & 2100MHz)
* GPS, AGPS
* Up to 7.2Mbps download, 5.76Mbps upload (HSPA/UMTS)
* Up to 3.1Mbps download, 1.8Mbps upload (EV-DO)
</div>
|style="vertical-align:top" |
[[image:Qualcomm_gobi_2000.jpg|thumb|Qualcomm Gobi 2000 WWAN Adapter]]
|}

== Lenovo Partnumbers ==
*ThinkPad AT&T® Gobi 2000 Broadband Option 78Y1398
*ThinkPad Gobi 2000 Broadband Option 78Y1399

== Firmware ==
The firmware for this device is not publicly downloadable. It consists of 3 files:
* amss.mbn (firmware stage 1)
* apps.mbn (firmware stage 2)
* UQCN.mbn (firmware stage 3 - includes configuration and carrier specific settings)

=== Obtaining the Firmware ===
There are two ways of obtaining the firmware files:
# From the pre-installed Lenovo Windows installation. Or from a clean Windows installation in a virtualizer that supports USB after installing the {{LNVDOCURL|DS001302|Qualcomm Gobi 2000 Wireless WAN Driver}}. The default location for the firmware files is {{path|C:\Program Files (x86)\QUALCOMM\Images\Lenovo\}}
# Using Wine to execute the {{LNVDOCURL|DS001302|Qualcomm Gobi 2000 Wireless WAN Driver}} installer that simply unpacks the real installer named GobiInstaller.msi. Then just extract[http://sysblogd.wordpress.com/2008/05/10/howto-extract-all-files-from-microsoft-installer-files-msi-rather-than-to-install-the-package/] the firmware images from the MSI file by {{cmduser|wine msiexec /a ~/.wine/drive_c/DRIVERS/WWANQL/Driver/GobiInstaller.msi /qb TARGETDIR<nowiki>=</nowiki>C:\\DRIVERS\\GOBI}}.
{{HINT|For enabling GPS, you will need a Windows installation with the Qualcomm Gobi 2000 Wireless WAN Driver installed, anyhow.}}

=== Choosing the Right Firmware ===

The firmware images are located in 11 directories. In general, each "officially" supported carrier has its own directory, as depicted in table "Firmware Images". The revision can be found in every file. The amms and apps files have the same revision and this one is reported by the {{cmd|AT I|}} command. The internal name of the UQCN file shows whether the firmware is for UMTS or CDMA2000. If your UMTS carrier is not listed, the default firmware and the generic UMTS firmware should work as their revisions match. The table "Non-listed Carrier Compatibility" summarizes the experiences of the Talk page.

{| {{prettytable}}
|+Firmware Images (Version 1.1.170/2.0.7.3 Released 2010/10/28)
! Dir !! Carrier !! Image !! MD5 message digest !! Revision !! Internal UQCN name
|-
| 0 || Vodafone || UQCN.mbn || 25ebf8314ed23394d23fb30ec4d73bf8 || D1025-UQCNABFD-2011 || 02-umts_vod-01024-011
|-
| 1 || Verizon
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
06f76ed398458dad7b91c2d99a85a0a7 
88a60ed745d75fb1b92c539574ecc972 
2dccbd125ddd2cb327309ba75c6054d2
|
D1055-STUTDSVD-3580 
D1055-STUTDSVD-3580 
D1055-STUTDSVD-3580
| 02-c2k_vzw-00256-018
|-
| 2 || AT&T || UQCN.mbn || 1743cbe6de3172d6a35ff183c2716445 || D1025-UQCNASDD-2016 || 02-umts_att_noxtra-00768-144
|-
| 3 || Sprint
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
d25f247cbe0fa481378d9f92c65c3e5e 
46fcb2423c31fd96e4645a90956264d2 
0ac877ed109f3c28d844b08f55c56185
|
D1055-STUTCSFD-3710 
D1055-STUTCSFD-3710 
D1055-UQCNCSFD-2015
| 02-c2k_sprint-00512-015
|-
| 4 || T-Mobile || UQCN.mbn || b0f5df651b34601bc21e3d8fcb064b19 || D1025-UQCNABLD-2011 || 02-umts_tmo_noxtra-01280-139
|-
| 6 || Generic UMTS || UQCN.mbn || bdf27325ebb63251c1310cd3a8f7bab6 || D1025-STUTABGD-3600 || 02-umts_gen-02304-018
|-
| 7 || Telefónica || UQCN.mbn || a1b941dd4c24e4f6542916c3e1e4634d || D1025-UQCNABHD-2012 || 02-umts_tellfon_nogps-03073-012
|-
| 8 || Telecom Italia || UQCN.mbn || 2f2a1b2b7f81735f0b8e4ea15c72b10b || D1025-UQCNABID-2011 || 02-umts_telital_noxtra-03584-139
|-
| 9 || Orange
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
00c612a8a827dbef746f514e939fa77d 
7d12b38ec6851bef5039b74bffffd423 
735db64a57802e252ca4ff05d06b2f10
|
D1025-STUTABOD-3601 
D1025-STUTABOD-3601 
D1025-STUTABOD-3601
| 02-umts_orange-02816-012
|-
| 12 || DoCoMo
|
amss.mbn 
apps.mbn 
UQCN.mbn
|
4d6203bf9fe8ae1af439d4d163e91596 
385a22740f80c0d00f8acdd9ad637032 
e868df00bfa88596d588a52f872ff703
|
D1025-STUTABED-3587 
D1025-STUTABED-3587 
D1025-UQCNABED-2009
| 02-umts_doco-03328-009
|-
| UMTS || Default Firmware
|
amss.mbn 
apps.mbn
|
80fcfbb41a7d4331d4b7145972f5f3c4 
00cbd411048cdadc3e4caf0d89d14fca
|
D1025-STUTABGD-3600 
D1025-STUTABGD-3600
|-
|}

{| {{prettytable}}
|+Non-listed Carrier Compatibility
! Dir !! Image !! Works with
|-
| 0 || Vodafone || E-Plus Germany
|-
| 1 || Verizon ||
|-
| 2 || AT&T ||
|-
| 3 || Sprint ||
|-
| 4 || T-Mobile ||
|-
| 6 || Generic UMTS || O2 UK? O2 Germany Mobitel Slovenia
|-
| 7 || Telefónica ||
|-
| 8 || Telecom Italia ||
|-
| 9 || Orange ||
|-
| 12 || DoCoMo ||
|-
| UMTS || Default Firmware || UMTS unlocked, O2 UK? O2 Germany E-Plus Germany
|-
|}

=== Loading the Firmware ===
The firmware for this device must be loaded prior to using the device. It persists in the memory of the device until the next cold boot. Then, it has to be loaded again. The firmware can be loaded automatically via udev using the gobi_loader application[http://www.codon.org.uk/~mjg59/gobi_loader/]. This application expects the firmware image files (amss.mbn, apps.mbn, and UQCN.mbn) in {{path|/lib/firmware/gobi/}}. Thus, create this directory as root, when it does not exist, and copy the appropriate firmware files into the directory. The previous section helps you to obtain the correct files.

Technically, the firmware loading interface is exposed over USB as id 05c6:9204 which can be accessed as a character (ttyUSB) device under Linux using the qcserial driver. After successfully loading the firmware, the device switches to the USB id 05c6:9205 and exposes three character devices (ttyUSB).

== Modem ==
After the firmware is loaded, the modem is exposed over USB as id 05c6:9205 which can be accessed as a character (ttyUSB) device. Normal dial-up software can be used to create a 3G connection.

== GPS ==
Since kernel 2.6.37, or with a small kernel patch (submitted upstream: [http://marc.info/?l=linux-kernel&m=128534473802312&w=2]), two additional serial ports are available:
Diagnostics Monitor and NMEA GPS. The three serial ports are:
# /dev/ttyUSB0 -> Diagnostics
# /dev/ttyUSB1 -> 3G Modem
# /dev/ttyUSB2 -> NMEA GPS port

There is a PPA for the qcserial module for Ubuntu 10.10 which uses DKMS: [https://launchpad.net/~dveeden/+archive/thinkpad-fixes ppa:dveeden/thinkpad-fixes].

If you have another serial USB device activated before the Gobi the ttyUSB-numbers will certainly change.

The Diagnostics Monitor uses Qualcomm's DM protocol; I used libqcdm (ModemManager) to talk to it, found it working, but at least DM commands 12 and 64 are not implemented on my device (Thinkpad x100e).

The GPS port and how to enable it has been confirmed now in the Gobi 3000 source code at: https://www.codeaurora.org/patches/quic/gobi/ Enable/disable GPS with:
echo "\$GPS_START" > /dev/ttyUSB2
# use GPS
echo "\$GPS_STOP" > /dev/ttyUSB2

{{NOTE|Preconditions: this has only been tested with and without a 3G SIM card attached to the device and the firmware successfully loaded. It is not necessary though to be connected via 3G to be able to use GPS.
Also before you can use "$GPS_START/$GPS_STOP" feature, "Auto tracking" has to be enabled in the Options of the {{LNVDOCURL|DS015017|ThinkVantage GPS}} Windows application. The ThinkVantage GPS Windows application works with a clean Windows installation in a virtualizer that supports USB. However, it requires the {{LNVDOCURL|DS001302|Qualcomm Gobi 2000 Wireless WAN Driver}} to be installed.
You will need to enable it only once.}}

To verify if the device is in the right mode use gpscat
$ gpscat /dev/ttyUSB2
6,,,,26,,,,13,,,*70
$GPGSV,4,2,16,14,,,,25,,,,08,,,,09,,,*7B
$GPGSV,4,3,16,32,,,,24,,,,,11,,,*73

You could use gpsctl to verify if gpsd detected the device correctly:
$ gpsctl
gpsctl: /dev/ttyUSB2 identified as Generic NMEA at 9600

Detection can take a few minutes.

If gpsd didn't detect the serial port the use the following line:
sudo /lib/udev/gpsd.hotplug add /dev/ttyUSB2

Use xgps or cgps to verify if the GPS has a fix. If it does have a fix you could use [http://www.tangogps.org TangoGPS] or any other GPS tool which uses gpsd.

To use GPS for time synchronization add the following lines to /etc/ntp.conf:
server 127.127.28.0 minpoll 4 prefer
fudge 127.127.28.0 time1 0.183 refid NMEA

The 0.183 is for [http://en.wikipedia.org/wiki/NMEA_0183 NMEA 0183]

If it works it will look like this:
# ntpq -c peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*SHM(0) .NMEA. 0 l 15 16 317 0.000 -49.965 5.312

== Carrier specific configurations ==
Each device is intended to be used with a specific carrier, and is shipped with firmware to support that carrier. Notebooks are often also shipped with a pre-installed SIM. Other carriers may work by loading a different firmware version. The 'generic UMTS' stage 3 firmware is known to with with O2, an unsupported UK carrier. See above for a list of known firmware files.

{{NOTE|It may be illegal or a breach of contract in various countries to bypass a carrier lock}}

== Troubleshooting ==

Some users have experienced the modem entering a strange state in which it refuses any attempt of loading the firmware.
There seem to be at least two ways to reset the modem to get it working as normally again:

1) try to disable WWAN in BIOS and boot your computer.
Then shut down it, and enable WWAN again. OR:

2) remove the AC adapter as well as the battery pack and then hold the power button for some time (approx 30 sec. - 1 min.).
Then insert the battery again and boot as usual.

See discussion page (22 - 23 January 2011) for further details.
--[[User:stman|stman]] 10:10, 23 January 2011 (UTC)

== Links ==
* [http://www.gobianywhere.com/sites/default/files/gobi2000_overview.pdf Gobi 2000 Product Sheet]
* [http://mail.cdmwireless.com/gobi2000/docs/AT_Command_Set_Gobi.pdf AT Command Set in Gobi]
* [http://mail.cdmwireless.com/gobi2000/docs/Gobi_Connection_Manager_FAQ.pdf Gobi Connection Manager FAQ]

== ThinkPads this device may be found in ==
'''AT&T service contract may be required'''
* {{Edge 14"}}, {{Edge 15"}}
* {{T410}}, {{T410s}}, {{T510}}
* {{W510}}
* {{X100e}}

'''Verizon service contract may be required'''
* {{Edge 14"}}, {{Edge 15"}}
* {{L412}}, {{L512}}
* {{T410}}, {{T410s}}, {{T410si}}, {{T510}}
* {{X201}}, {{X201 Tablet}}

'''Gobi 2000 WWAN upgradable'''
{{NOTE|not every ThinkPad listed here can actually be upgraded}}
* {{Edge 13"}}
* {{T410}}, {{T410s}}, {{T410si}}, {{T510}}
* {{W510}}
* {{X100e}}, {{X201}}, {{X201 Tablet}}

BIOS Upgrade

2010-11-08T12:05:04Z

Dag-: Added X201 with BIOS 1.22 using syslinux 4.03

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is meant to describe ways to update the BIOS on a ThinkPad that only runs Linux for users that don't have ready access to Windows. If you have Windows on your ThinkPad you can just boot into it and follow instructions on the Lenovo website.

Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by Lenovo. However there are work arounds.

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems.

'''Proceed at your own risk!'''}}
|}

= Downloading New Firmware =
{{WARN|Flashing the wrong firmware for your hardware may cause permanent damage to your ThinkPad. It is up to you to confirm that the firmware you are using is correct.}}

A list of links to firmware downloads can be found at [[BIOS Upgrade Downloads]] for most Thinkpad models. You can also check the Lenovo Support website's [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-MATRIX|ThinkPad driver matrix].

Lenovo provides firmware upgrades in a variety of packages:
* Diskette
* Non-diskette
* Linux diskette
* BIOS Utility
* Bootable CD

Not every type of package is available for every model.

The ''BIOS Utility'' and ''Bootable CD'' packages combine the BIOS and ECP firmwares. For the other packages, there is one for each firmware.
{| align="right" style="width:20em;"
| {{HELP|Can an image be extracted from a "Linux diskette" .exe file?}}
|}

The ''Linux diskette'' is just the ''Diskette'' package that runs on Linux instead of Windows/DOS. It's unknown if a boot image can be extracted from it.

You may need to try different packages to find the one from which you can extract a boot image.

== Two Firmwares: BIOS and ECP ==
{{WARN|Flashing incompatible firmwares, or flashing them in the wrong order, may cause permanent damage to your ThinkPad.}}

It is important to understand that Thinkpads from IBM have two separate firmwares: the BIOS, and the Embedded Controller Program (ECP).

A given BIOS version will require a certain version of the ECP. You must read the Lenovo website and/or .txt files to confirm which BIOS is compatible with which ECP, and '''the order in which to update them'''.

=== Update Order ===

The IBM documentation is sometimes unclear about the order in which these two firmwares should be updated. When in doubt (i.e. IBM didn't provide specific instructions for your model or a particular firmware update), '''update the ECP first, and then the BIOS'''. Also, make sure to do the two updates '''immediately one after the other'''.

The EC firmware is usually much better at backwards compatibility than the BIOS.

(Updaters for newer models take care of both BIOS and EC, and use automatically whatever sequence is needed, so you don't have to worry about it.)

== Installed Firmware ==
You can check the current BIOS and ECP versions on your ThinkPad by using '''dmidecode'''. For example:

{{cmdroot|dmidecode -s bios-version}}

1RETDRWW (3.23 )

{{cmdroot|dmidecode -t 11}}

# dmidecode 2.9
SMBIOS 2.33 present.
Handle 0x0029, DMI type 11, 5 bytes
OEM Strings
String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-

Showing BIOS version 3.23 (1RETDRWW) and ECP version 3.04 (1RHT71WW).

===DMI IDs===
Please consider updating the [[List of DMI IDs]] before (and after) updating your BIOS.

= Updating Firmware =

There are two basic steps to updating the firmware (either the BIOS or the ECP) on a ThinkPad not running Windows:
# Extract a bootable update image
# Boot from that image

== Extracting an update image ==
{{WARN|Though this process has been successfully tested on many versions of .exe files found on IBMs website, that doesn't mean it will work for all of them. '''Proceed at your own risk'''. Consult the testing tables farther down of this page to see other users' experience with your model Thinkpad.}}
{{NOTE|These EXE unpack procedures no longer work on more recent downloads, as Lenovo has changed the packaging format. You may still be able to unpack them using wine, or alternatively an actual (virtual) Windows machine.}}
Older .exe installers from Lenovo mostly appear to be just a wrapper license program around Windows .cab files (see [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program [http://freshmeat.net/projects/cabextract/ '''cabextract'''] you can expand these .cab files directly. For example, if you downloaded {{path|1iuj13us.exe}} from Lenovo:

:{{cmduser|cabextract 1iuj13us.exe}}

Extracting cabinet: 1iuj13us.exe
extracting 1IUJ13US.IMG
extracting BIOSUPTP.EXE
extracting DOBOOT.EXE
extracting DOSBOOT.COM
extracting DOSBOOT.SYS
extracting DOSBOOT.VXD
extracting DOSBOOT2.COM
extracting ECTLUPTP.EXE
extracting EFLASHAS.SYS
extracting HDFWUPTP.EXE
extracting IBMTPI.XML
All done, no errors.

The file we want is '''FILENAME.IMG''', with "FILENAME" being the .exe. you downloaded. E.g., {{path|1IUJ13US.IMG}}.

(If this does not work for the Non-diskette .exe, try it on the Diskette .exe. It's reported, for example, that the Non-diskette .exe for BIOS version 3.23 for the T41p was not extractable, but the Diskette .exe worked perfectly, with {{cmduser|cabextract}} delivering a .IMG file.)

==== Testing the Image ====

You can test that FILENAME.IMG is really a floppy image by running:

{{cmdroot|mkdir /tmp/mntfloppy}}

{{cmdroot|mount -o loop FILENAME.IMG /tmp/mntfloppy}}

If a '''ls''' command on the image returns what looks like a DOS floppy, and no read errors were displayed, you have a pretty good chance that the image is usable. For example:

{{cmdroot|ls /tmp/mntfloppy}}
$0195000.FL1 069580.PAT 06d2.HSH IBMDOS.COM TPCHKS.EXE
0691.HSH 06D0.PAT 06d6.HSH LOGO.BAT UPDTFLSH.EXE
0691.PAT 06D1.PAT 06d8.HSH LOGO.SCR UPDTMN.EXE
0694.HSH 06D2.PAT CHKBMP.EXE PHLASH16.EXE USERINT.EXE
0694.PAT 06D6.PAT COMMAND.COM PREPARE.EXE UTILINFO.EXE
0695.HSH 06D8.PAT CONFIG.SYS PROD.dat lcreflsh.bat
0695.PAT 06d0.HSH FLASH2.EXE QKFLASH.EXE
069580.HSH 06d1.HSH IBMBIO.COM README.TXT

Unmount the image after you are done testing:

{{cmdroot|umount /tmp/mntfloppy}}

== Booting from update image ==
Now that you have a bootable image for the correct update for you hardware, you need to do is boot from that image to install the update.

There are different ways to do that:
* [[#Booting from a CD|Boot from a CD]]
* [[#Booting_using_GRUB|Boot from the image, using GRUB]]
* [[#Booting_from_a_floppy|Boot from a floppy]]
* [[#Booting_from_a_USB_Flash_drive|Boot from a USB Flash drive]]

=== Booting from a CD ===
{| align="right" style="width:40em;"
|{{HINT|If there is a ''Bootable CD'' image available, e.g., FILENAME.iso, just download that, instead of mucking around with image files.}}
|}
If you are going to update the firmware by booting from a CD, you need to turn FILENAME.IMG that you extracted above into an .iso file.

The [http://en.wikipedia.org/wiki/El_Torito_%28CD-ROM_standard%29 El Torito Bootable CD Specification] is a wonderful thing. Thanks to it, a bootable CD can be made with a bootable floppy image in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the '''mkisofs''' tool{{footnote|1}}. Run a command as follows:

{{cmdroot|genisoimage -b 1WUJ25US.IMG -c boot.catalog -o bootcd.iso 1WUJ25US.IMG}} #or older mkisofs

Where *.IMG is the name of the image file extracted above. This creates a CD with one file on it and marks that file as the boot image.

You can now burn the {{path|bootcd.iso}} to a CD in your favorite CD-burning program.
{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Boot from the CD to update your firmware. Remember to have [[BIOS_Upgrade#Two_Firmwares:_BIOS_and_ECP|both BIOS and ECP firmware boot-CDs]] ready, as needed, and use them in the [[#Proper_Order|proper order]].

== Updating without battery or with dead battery ==

This is a last-resort approach. Use this only if everything else fails.

The BIOS updater may refuse to update a BIOS without a battery, or if the battery charge is too low. In that case, extract the disk image with cabextract as per instructions above and dd it to an usb stick. (This will destroy the data on it, of course.) Acquire a pure DOS boot cd such as Windows 98 recovery CD and boot that.

Use F8 to abort the boot sequence of a windows 98 boot CD. If you need CD-ROM support, load CD-related things but say no to everything else. In particular, avoid loading himem.sys and doskey, as the presence of either program causes Phoenix bios flash tool phlash16.exe to abort.

Change to the volume where flash2.exe and other tools are installed, and execute "flash2.exe /u". This should bypass the battery check and perform the flashing. If that doesn't work, check if the update disk contains a tool called "phlash16.exe". This can be used directly to flash the image, and the invocation is typically "phlash16 /exit $01c80000.fl1".

This method won't work for the Thinkpad {{560X}} (and likely other older models). Since the 560X is a bit older, it won't be a big surprise if the battery is dead as a dodo. Here's how to update the bios in this case: download the spsdi833 bios update and create the update floppy. If you have trouble creating this disk, [http://rapidshare.com/files/413598837/spsdi833-bios-560X.zip.html download an archive with the files] and put them on a floppy. Don't worry about making it bootable. Also, you will need a DOS bootdisk. A Windows 98 bootdisk will be fine. Boot the system with the W98 bootdisk, do not load CD-rom support. Remove the W98 bootdisk and put the disk with the BIOS update in the drive. If you would now run UPDTFLSH you would get the battery message, so don't do that. If you open UPDTFLSH.exe with a text editor, you would find some lines about UPDTROM. UPDTROM is the actual flash tool, but you can't simply run it just like that. Run the following:

*updtrom /np /prep1
*updtrom /np /prep2
*updtrom /np /prep3
*updtrom /np /romcmp /romflsh /prep4
*updtrom /np /h8flsh /h8img /model

Yes, you need to run updtrom five times. Hold your breath and reboot the machine. It's done.

Perhaps not all these lines are necessary, but to be sure I ran them all, and this worked for me. So I suggest you do the same. This could probably be done from the harddisk as well, but I did not test that.

== Successful tests ==

{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
| {{600E}} 2645-4AU ||
* George Tellalov <gtellalov_dontspamme@bigfoot.com>. BIOS 1.16 from spsdin36.exe worked perfectly with the method bootable cd from floppy image. I highly recommend this upgrade because it made my ibm-acpi module load (it wouldn't load before) and fixed some suspend to ram problems. Here's the [http://george.tellalov.info/bios_upgrade_600e_spsdin36.iso cd image] I used. Use at your own risk. You can send me a chocolate if it works for you ;)
|-
| {{600E}} 2645-5bU ||
* Mike Vincent<matchstc-putobvioushere.com>. Bios 1.16 from spsdin36.exe and then to the boot cd worked great for me. Thought I had bricked it three separate times using a "real" floppy! Each from different diskettes .The updater would start, give me the "going to take30 seconds" speech...and then access the HD for 10 minutes. Each time it would reboot fine. Did the cd as described above...worked great first time. Perhaps 10 year old seldom used floppy disc drives have some challenges?
|-
| {{600X}} 2645 ||
* Jonathan Byrne <jonathan@RemoveThisToMailMe.yamame.org>. BIOS 1.11 from spsuit55.exe worked perfectly using cabextract/CD method.
|-
| {{600X}} 2645 ||
* Andy Barnes <andy@RemoveThisToMailMe.itchypaws.co.uk>. As per Jonathan above, extracted BIOS 1.11 from spsuit55.exe using cabextract, created a CD boot image and burnt to CD. Worked flawlessly - thanks to everyone who contributed to this article!
|-
| {{A20p}} 2629-6VU ||
* Chris Pickett http://www.sable.mcgill.ca/~cpicke/. BIOS 1.11 flashed fine with cabextract/CD method.
|-
| {{A21e}} 2628-JXU ||
* Amit Gurdasani <gurdasani at yahoo dot com>. BIOS 1.13 flashed fine with cabextract/CD method. Alarmingly, after the BIOS update, the laptop beeped but did not shut down as was indicated onscreen -- that was frozen on the "do not shut down the laptop" screen. On power down and up again, the BIOS setup showed the newer BIOS image running, and Linux booted up fine. Linux ACPI didn't complain about the BIOS being too old either.
|-
| {{A31p}} 2653 ||
* Matthias Meinke largeeddy@gmx.at, BIOS 1.09 1NET15WW flashed fine with cabextract/CD method.
|-
| {{A31}} 2652 ||
* [[User:Wnoise|Aaron Denney]], BIOS 1.13 flashed fine with cabextract/CD method. The cabextract/CD method also worked for BIOS 1.10.
|-
| {{R30}} ||
* Jarrod, 30 August 2007, Thinkpad R30 Type 2656-E0M. BIOS updated to 1.40 (1CETF0WW) using floppy disk/mkisofs/cdrecord. Worked fine, no problems.
|-
| {{R31}} ||
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
* Sebastian Sauer (with cabextract/CD method)
|-
| {{R40}} ||
* Matthew Lambie, http://lambie.org
* Antti S. Lankila, update to 1.27 via direct use of phlash16.exe against a BIOS image. Normal method did not work because the battery is dead.
|-
| {{R50}} 1836-3SU ||
* jlbartos <jlbartos at hotmail dot com>
|-
| {{R50e}} 1834-PTG ||
* item <item at freemail dot hu> : successfully finished with cabextract/CD method for "1wuj25us.exe" (BIOS version 1WET90WW (2.10), Release Date: 2006/12/22)
* Christos Nouskas <nouskas at gmail dot com>: upgraded to BIOS version 1WET90WW (2.10) and EC version 1VHT28WW (1.04) using GRUB (BIOS first / EC second)
|-
| {{R51}} 1829 ||
* Robert Uhl <rob dot uhl at gmx dot de>, Jellby <jellby at yahoo dot com>
|-
| {{R51}} 1830-RM7 ||
* Will Parker <stardotstar at sourcepoint dot com dot au> successfully flashed 3.20 using existing 3.04 ECP and retained custom boot splash.
|-
| {{R51}} 2887 ||
* Ingo van Lil <inguin at gmx dot de>
|-
| {{R52}} 1858 ||
* Stuart McCord <stuart dot mccord at gmail dot com> flashed both BIOS and ECP using cabextract, BIOS flashed first as on IBM website
|-
| {{T20}} ||
* Franz Hassels <fhassel at suse dot com>
|-
| {{T22}} ||
* Daniel Maier <nusse teamidiot de>
* Mathias Behrle (with cabextract/CD method, Version 1.07 => 1.12) --[[User:Mathiasb|Mathiasb]] 11:58, 14 December 2006 (CET)
* Bob Skaroff (cabextract/CD), 1.06 => 1.12
* Leo Butler (cabextract/CD), 1.11 => 1.12
|-
| {{T23}} ||
* Bart Snapp <snapp at uiuc dot edu> Note: I followed IBM's instructions to flash the BIOS '''first''' and the Embedded Controller '''second'''.
* Moy Easwaran: BIOS 1.18 / EC 1.06a via cabextract and CD-boot. The BIOS-update exe generated errors in Windows 2000.
* Joe Renes: BIOS 1.18 / EC 1.06a on 2006-03-20 via cabextract and CD-boot. Piece of cake.
* Raphael Errani: BIOS 1.20 / EC 1.06a on 2006-11-06 via cabextract and CD-boot (using mkisofs). Worked without errors. 1st Bios, 2nd EC
* Myron Getman: BIOS 1.20 / EC 1.06a on 9/10/08 via cabextract --> k3b --> CD-boot. Worked like a charm. First BIOS update with Linux!
* Leo Butler: BIOS 1.13 / EC 1.04 to 1.20/1.06a via cabextract and syslinux/memdisk boot through grub. Worked like a charm and no wasted CD.
|-
| {{T30}} ||
* Martin GÃ¼hring <guehring at gmail.com> BIOS 2.10 via cabextract the Non-Diskette BIOS -> mkisofs '''in the directory the exe was extracted''' to generate the iso -> burn the iso -> boot the CD
|-
| {{T40}} ||
* Sean Dague, http://dague.net
* Justin Mason, http://jmason.org
* Ivanhoe (Bios 3.19)
* Alessandro Raulino (roger_2) EC 3.04 & BIOS 3.23 flashed with cabextract/CD method
* Nick Jenkins, using BIOS 3.23 with the '''Non-diskette updater + cabextract method''', then [[#Creating_a_Bootable_CD_from_a_Floppy_Image|created a bootable CD from the cabextracted .IMG file]], then boot that ISO, and it worked great!
* xyz: BIOS 3.23 & EC 3.04 flashed with cabextract/CD method. No problem.
|-
| {{T40p}} ||
* Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
* Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
* paper, BIOS 3.23 (1RETDRWW) flashed fine with cabextract/genisoimage method.
|-
| {{T41}} ||
* Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
* Ernesto HernÃ¡ndez-Novich (Bios 3.19 / CP 3.04) < emhn at usb dot ve >
* [http://maebmij.org James Ballantine] (Bios 3.21 / CP 3.04) using nondisk/cabextract/CDRW
* Vladimir Pycha (to Bios 3.23 / EC 3.04, from Bios 3.20 / EC 3.04) using nondisk/cabextract/CDRW. Booted with external USB optical drive (I have internal drive broken) - at the beginning of the boot sequence press PAUSE, then wait several seconds, then ENTER, then F12 and select the drive. Without pressing PAUSE I am not able to boot from USB optical/hard drive as the drive does not show in the F12 boot list menu.
|-
| {{T41p}} ||
* Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| {{T42}} 2373-JXG ||
* magarzo <mdr.magarzo at gmail.com> (BIOS v.3.23 / Embedded Controller v.3.04 / both with cabextract to non-diskette v. plus Bootable CD)
|-
| {{T42}} ||
* Dan (BIOS 3.20 / EC 3.04, cabextract/CD method) <tronic171 at evilphb.org>
* Hirosh Dabui <hirosh@dabui.de>
|-
| {{T42p}} ||
* Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>, Hirosh Dabui <hirosh@dabui.de>
|-
| {{T43}} 1871-W34 ||
* Florian Boucault <florian at boucault dot ath dot cx> (Version: Bios 1.23 / Embedded Controller 1.03)
|-
| {{T43}} 1871-4AG ||
* [http://blog.martinmcdowell.com/about/contact Martin McDowell] 28-Feb-2010
* BIOS 70ET62WW (1.22) to 70ET69WW (1.29),
* ECP 70HT26WW (1.03) to 70HT28WW (1.05)
Both successfully upgraded from CD Image made from the instructions on this website.
|-
| {{T43}} 2886 ||
* Till Heikamp <t dot heikamp at geniusbytes dot com> (Bios 1.22 to 1.29, Embedded Controller 1.03 to 1.06)
|-
| {{T43}} ||
* Conrad Rentsch <Conrad dot Rentsch at t-online dot de> (Version: Bios 1.29 / Embedded Controller 1.06)
* Tom Heady <tom-thinkwiki.org@punch.net>
|-
| {{T60}} ||
* 1951 Roman Komkov <roman at komkov dot org dot ru> (Bios 1.07 to 2.13) Successfully upgraded from CD Image
* 8744-HCG Konstantin Khorenko <horenko at mail dot ru> (Bios 1.06 to 1.18) Successfully upgraded from CD Image
|-
| {{T61}} ||
* Kai Weber <kai.weber at glorybox dot org> (Bios 1.06 to 1.26) Successfully upgraded from CD Image
|-
| {{X20}} ||
* Neil Caunt <retardis at gmail dot com>
|-
| {{X21}} ||
* Patrick Leickner <ranma at web dot de>, (BIOS 2.21->2.25 / EC 1.31->1.36) via non-disk/cabextract/mkisofs/cdrecord
|-
| {{X22}} ||
* David Emery <dave at skiddlydee dot com>, (EC 1.30, BIOS 1.32 using non-disk/cabextract/CD method)
|-
| {{X23}} ||
* Nils Faerber <nils dot faerber at kernelconcepts dot de> (Embedded Controller 1.30, BIOS 1.32 with cabextract/CD method)
|-
| {{X30}} ||
* Hella Breitkopf, [http://www.unixwitch.de/ www] (Embedded Controller 1.04, BIOS 1.07 with cabextract/CD method)
* William Roe <willroe at gmail dot com> (Embedded Controller 1.06, BIOS 1.09 - cabextract/mkisofs/wodim)
|-
| {{X31}} ||
* Grzegorz KuÅ›nierz <koniu at sheket dot org> (Embedded Controller 1.08, BIOS 3.01 with cabextract/CD method)
|-
| {{X31}} ||
* Paul Litwack <paullitwack at gmail dot com> (Embedded Controller 1.08, BIOS 3.02 with cabextract/unetbootin method)
cabextract & unetbootin are staight foward(toggle floppy image instead of iso image in unetbootin dialog)
No problems with update software.
x31 has to be cajoled into booting from usb. Boot hangs when pendrive is present. Hit the key to bring up the boot menu.
Unplug the pendrive. Let the boot menu come up. Plug in the pendrive. Select the pendrive in the boot menu and it boots.
|-
| {{X40}} ||
* Robbie Stone <robbie@serendipity.cx>
* Andy Shevchenko <andy.shevchenko@gmail.com> (Fine by cabextract/CD method)
|-
| {{Z60m}} ||
* [[User:Morle|Morle]] 01:09, 17 Nov 2007 (CEST), (Embedded Controller 1.18 and Bios 1.24 with cabextract/CD method)
|}

==== Unsuccessful tests ====
{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
|<pre> </pre> 
|
|}

=== Booting using GRUB ===
{|
| style="width:75%" | {{WARN|Many have warned '''not''' to use the SYSLINUX image-loader '''memdisk''' to boot firmware update images.}}
| style="font-size:80%" | {{HELP|Who are these "many"? Link to a discussion?}}
|}
Once the bootable image, FILENAME.IMG, is extracted from the .exe, it can be booted directly through GRUB without the need of burning a CD, using the [http://syslinux.zytor.com/ SYSLINUX] image-loader '''[http://syslinux.zytor.com/memdisk.php memdisk]'''.

Locate the '''memdisk''' file from the syslinux package. You can search for it with '''find''':

{{cmdroot|find /usr -name memdisk}} #or just use "dlocate memdisk" or "locate memdisk" if these programs are installed

If {{path|/usr/.../memdisk}} is not present, syslinux is not installed. You will need to install it to boot a .IMG from GRUB.

Copy both the '''FILENAME.IMG''' and '''memdisk''' files into {{path|/boot}} directory. For example:

{{cmdroot|cp ./FILENAME.IMG /usr/share/syslinux/memdisk /boot/}}

Open {{path|/boot/grub/menu.lst}} in your favourite editor. '''Copy''' the active section into a '''new section''', and edit the new section:
{| border="1" cellspacing="0" cellpadding="2"
! Parameter
! Instructions
! Example
|-
| ''title'' || Pick a name for the new section. This will show up in the GRUB boot menu. || <tt>title IBM ECP Update</tt>
|-
| ''root'' || Do not change. This is the partition containing the {{path|/boot}} directory || <tt>root (hd0,0)</tt>
|-
| ''kernel'' || '''/boot/memdisk''' will allow you to boot an image file. || <tt>kernel /boot/memdisk</tt>
|-
| ''initrd'' || This is the name of the firmware-updater image file, e.g., 1IUJ13US.IMG || <tt>initrd /boot/1IUJ13US.IMG</tt>
|}

Do '''not''' modify the original section in {{path|/boot/grub/menu.lst}}, or you might not be able to boot back to the operating system.

If you have [[#Two_Firmwares:_BIOS_and_ECP|two firmware updates to do]], you will need a section for each firmware's FILENAME.IMG in {{path|/boot/grub/menu.lst}}.

{{NOTE|If both BIOS and ECP are to be updated, be sure to update them in the [[#Proper_Order|proper order]].}}

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Reboot your computer, entering the GRUB menu and selecting ''IBM BIOS Update'', or whatever you named the new section in {{path|/boot/grub/menu.lst}}.

==== GRUB2 ====
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :
menuentry "My BIOS Upgrade" {
set root=(hd0,0) #should match the others in your grub.cfg
linux16 /boot/memdisk
initrd16 /boot/1WUJ25US.IMG #or whatever yours is
}

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{R30}} 2656-64G || v.1.40 || || [[User:english.voodoo|Yuri Spirin]] ||
|-
| {{R40}} 2723 || 1OHJ11WW.IMG || 1PUJ25US.IMG || [[User:qunying|Qunying]] || memdisk from syslinux 3.70 (slackware 12.1)
|-
| {{R50e}} 1834NV1 || 1WUJ25US.IMG || || [[User:Jidanni|Jidanni]] || memdisk from syslinux-common 2:3.84+dfsg-1 (Debian), grub2 (1.96+20080724-16)
|-
| {{R51}} 2888 || || || ||
|-
| {{T23}} 2647 || 1AUJ20US.IMG || 1AHJ06US.IMG || [[User:cthon|cthon]] || memdisk from syslinux 4.02-1 (arch linux)
|-
| {{T40}} 2373 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:Euphoria|Euphoria]] || memdisk from syslinux 1:3.31-4 (Debian package version)
|-
| {{T40}} 2373 || 1RHJ10U2.IMG (3.04, 2004-11-15) || 1RUJ37US.IMG (3.23, 2007-07-03) || [[User:Morphics|Morphics]] || cabextract and memdisk from syslinux 3:1.36-4ubuntu5
|-
| {{T41}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Tonko|Tonko]] || Fedora 12
|-
| {{T41p}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Deggel|Deggel]] || cabextract and memdisk from syslinux 3.71 on gentoo
|-
| {{T41p}} 2373 || || || [[User:MrStaticVoid|James Lee]] ||
|-
| {{T42}} 2373 || 1RUJ37US.IMG || || [[User:Secsaba|Simon Csaba Endre]] || Ubuntu 10.04 Pre-update versions: BIOS v3.21 / ECP v3.04 After-update versions: BIOS v3.23 / ECP v3.04
|-
| {{T42p}} 2374 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:aderigs|Achim Derigs]] || Debian GNU/Linux sid, works with `linux16 ...' and `initrd16 ...' only
|-
| {{X31}} 2673-CBU || || || [[User:JanTopinski|Jan Topinski]] ||
|-
| {{X31}} 2672-CXU || || || [[User:TheAnarcat|TheAnarcat]] ||
|-
| {{X31}} 2672-JBU || 3.02 1QUJ19US.IMG || 1.08 1QUJ08US.IMG || [[User:twbxf4|twbxf4]] || worked flawlessly
|-
| {{X31}} 2673-58G || || || [[User:FaUl|FaUl]] ||
|-
| {{X31}} 2672-PG9 || || || [[User:Starox|Starox]] || a big moment between starting update and the updating window
|-
| {{X31}} 2672-PG9 || v3.02 1QUJ19US.IMG || v1.08 1QHJ08US.IMG || [[User:TeeLittle|TeeLittle]] || Apr 10, 2010: Using Debian 5.0 "Lenny" + package syslinux-common (Version: 2:3.71+dfsg-5). Pre-update versions: BIOS v2.11 / ECP v1.03
|-
| {{X40}} 2371 || 2.07 1uuj21us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Jakob Truelsen]] || Worked on two X40-2371
|-
| {{X40}} 2386 || 2.08 1uuj22us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Galen Seitz]] || memdisk from syslinux 3.61
|}
(More successful grub tests are scattered in the previous table too.)

==== Unsuccessful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! style="width:10em;" | BIOS
! ECP
! Tested by
! Notes
|-
| {{R32}} 2658-NWU || 2.16 1MUD23US.IMG || n/a || [[User:Millman12345|Mike Millman]] || Boots into the BIOS flashing program just fine, but when it comes time to start the update process, the system hangs completely. Luckily, it hangs before it actually modifies anything... A hard reboot got me back into a working system. I would not recommend this route!
|-
| {{R52e}} 1846-CGL || 1.29 76UJ28UD.IMG || 1.01 || [[User:Lacyc3|Laszlo Takacs]] || Boots into BIOS flashing program but it hangs up before the upgrade process. I used memdisk from syslinux-4.01.
|-
| {{T43}} 2668-F7G || 1.29 1YUJ18US.IMG || || [[User:Maus3273|Maus3273]] || I got into the bios program, but the machine never restarts after initiating the upgrade.
|-
| {{X41}} 2525-FAG || 2.09 74UJ15US || || [[User:Ukleinek|Uwe Kleine-König]] || booted fine (Debian syslinux 2:3.71+dfsg-5), but didn't succeed to write, just hang at "Don't restart or remove diskette etc. pp" (not bricked). Worked fine via CD method.
|-
| {{X41}} 2525-F8G || 2.06 74UJ12US.IMG 2.07 74UJ13US.IMG 2.09 74UJ15US.IMG || || [[User:ladoga|Lauri Koponen]] || hangs while initializing the actual BIOS flashing process ECP: 1.02 74HJ03US.IMG works
|-
|}

==== GRUB2 boot cd image ====
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :
menuentry
menuentry "My BIOS Upgrade" {
set root=(hd0,0) #should match the others in your grub.cfg
linux16 /boot/memdisk iso raw
initrd16 /boot/1WUJ25US.iso #or whatever yours is
}

This works for official iso images from ibm website.

On newer versions of Ubuntu grub.cfg is generated - add the entry to ''/etc/grub.d/40_custom'' then run <code>sudo update-grub</code>.

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{X100e}} 2876-55G || 6xuj05uc.iso || || [[User:nikel]] ||
|-
| {{Edge}} || 1.17 6yuj04uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 1.13 6duj40uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 3.14 6duj41uc.iso || 1.06 || [[User:dag-|Dag Wieers]] || Using memdisk from syslinux 4.01
|-
| {{X201}} 3626-A14 || 1.15 6quj05uc.iso || 1.09 6quj05uc.iso || [[User:Alexander List|Alexander List]] || memdisk from syslinux 3.86
|-
| {{Edge 13"}} 0197-6GG || 1.18 6yuj05uc.iso || || [[User:fethio]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{Edge 13"}} 0197-34Q || 1.18 6yuj05uc.iso || || [[User:Kapil]] || Current memdisk from syslinux debian version 2:4.01+dfsg-1
|-
| {{X200s}} || 3.15 6duj42uc.iso || || [[User:lawnjam]] || Memdisk 4.02 worked, the one provided by Ubuntu 10.04 did not.
|-
| {{X201}} || 1.22 6quj08uc.iso || 1.11 || [[User:dag-|Dag Wieers]] || Using memdisk from syslinux 4.03
|-
|}

=== Booting from a Floppy ===
{{WARN|Using a floppy disk '''is NOT recommended'''.}}

This is how IBM/Lenovo intended it. Use their .exe files to create a bootable floppy with the flash update on it. Boot from the floppy and there you go.

So, why is it not recommended?
# If something goes wrong, your ThinkPad may be permanently damaged
# Floppy disk drives are not reliable
# Floppy disks are not reliable
# It only works with /dev/fd0, meaning it won't work with a USB floppy

So, even though Lenovo is now offering "Linux diskette" updaters, that will create a bootable floppy under Linux, using a floppy is still not recommended. Besides, many people don't even ''have'' a floppy drive on their ThinkPad.

If you really want to do it with a floppy, some tips:
* Use a clean (in the physical sense) floppy drive
* Use new floppies
* Test floppies for errors before starting update process
* Have multiple copies of the update disks ready--if one should fail, replace it with a copy
* Should DOS complain of a read error, '''only''' respond wth "Retry"

{{NOTE|Should the system encounter a disk read error during the flash process, and you select "Abort", your system could be permanently damaged.}}

=== Booting from a USB Flash drive ===
{{HELP|Has anyone tested booting a firmware update image from a USB flash drive? Perhaps using [http://unetbootin.sourceforge.net/ UNetbootin]?}}
Unetbootin 422 worked with the image files unpacked with cabextract on my x31.

==== Using GRUB for DOS ====

[http://grub4dos.sourceforge.net/wiki/ grub4dos] is a GNU GRUB fork with interesting features. One of them is the ability to boot ISO images directly off USB flash drives. Contrary to the name, GRUB for DOS works fine on Linux. Follow these steps:
* Download the latest grub4dos package at http://download.gna.org/grub4dos/
* Unpack
* Insert your FAT-32 formatted pendrive
* Run <code>sudo ./bootlace.com /dev/sdX</code>, where /dev/sdX is the device name assigned to your pendrive. This creates grub4dos boot sector in MBR of the flash drive. Be very careful not to overwrite your hard drive!
* Copy the files <code>grldr</code> and <code>menu.lst</code> to the root directory of your pendrive.
* Likewise, copy the Thinkpad BIOS ISO image (e.g. <code>7uuj43uc.iso</code>).
* Edit <code>menu.lst</code> on the pendrive and include the following section (of course putting the appropriate ISO image name):
<pre>
title thinkpad-bios
map (hd0,0)/7uuj43uc.iso (hd32)
map --hook
chainloader (hd32)
boot
</pre>
* Reboot and press F12 to select booting from USB.
* If all went well, you should be able to boot the Thinkpad's ISO image and flash the BIOS. I tested it successfully on T400. [[User:Wanted|Wanted]] 20:23, 16 July 2010 (UTC)

== Booting from a Network Boot Image ==
BIOS, ECP, CD/DVD and Harddisk firmware disks can be booted over the network with [http://syslinux.zytor.com/pxe.php PXELINX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package. This requires that you have a DHCP and tftp server configured and setup properly on your network, and is probably not for the faint of heart.

Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks from the IBM website cannot be booted directly as such.

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates. On the {{X22}}, it worked with ECP 1.30 but '''not''' with BIOS 1.32

=After updating=
Lenovo recommends reseting your BIOS settings to their factory defaults after a firmware update.

==DMI IDs==
Please consider updating the [[List of DMI IDs]] after updating your BIOS.

= Special Cases =
* In one case, see ([[APM setup on a type 2379 ThinkPad T40]]), it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.

== Updating Thinkpad X Series ==
The special update instructions for {{X_Series}} Thinkpads are quite long. You can find them at the page [[BIOS_Upgrade/X_Series]].

----

{{footnotes|
# For lots of detail on making and burning .iso files, see The Linux Documentation Project (tldp.org): [http://tldp.org/HOWTO/CD-Writing-HOWTO-3.html#ss3.1 3.1 Writing CD-ROMs (pure data)].
}}

List of DMI IDs

2010-07-13T11:39:57Z

Dag-: /* DMI ID database */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page maintains a database of [http://en.wikipedia.org/wiki/Desktop_Management_Interface DMI] information which can be used to identify ThinkPad models. It is intended as an aid for driver development.
{{HELP|We need more information about older models, especially those released before 2004. Please [[#Adding_entries|add your model]] to the database.}}
{{NOTE|If your ThinkPad is not using the [[BIOS Upgrade Downloads|latest BIOS]], and you would be willing to [[BIOS Upgrade|upgrade your BIOS]], please add your ThinkPad to this table twice: '''before''' and '''after''' the BIOS upgrade. This information helps us a great deal, so your contribution would be very appreciated.}}
|}

==DMI ID database==

<div style="font-size: 80%">
{| border="1" cellspacing="0" cellpadding="2" style="text-align:center"
|-
! Model
! <tt>system- manufa cturer</tt>
! <tt>system- product- name</tt>
! <tt>system- version</tt>
! <tt>baseboard- manufa cturer</tt>
! <tt>baseboard- product- name</tt>
! <tt>base board- version</tt>
! <tt>chassis- manufa cturer</tt>
! <tt>chassis- version</tt>
! <tt>bios- vendor</tt>
! <tt>bios- version</tt>
! <tt>bios- release- date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====Numbered series====
|-
| {{240X}} 2609-61U
|| IBM || 260961U || Not Available || IBM || 2609BS1 || Not Available || IBM || Not Available || IBM || 1.03.09 || 12/21/1999
||
||
|-
| {{570}} 2644-1AU
|| IBM || 26441AU || Not Available || IBM || 26441AU || Not Available || IBM || Not Available || IBM || IMET65WW || 11/11/99
||
||
|-
| {{570E}} 2644-5AU
|| IBM || 26445AU || Not Available || IBM || 26445AU || Not Available || IBM || Not Available || IBM || IUET25WW || 12/11/1999
||
||
|-
| {{600E}} 2645-5AU
|| IBM || 26455AU || Not Available || IBM || 26455AU || Not Available || IBM || Not Available || IBM || INET36WW || 11/20/1999
||
||
|-
| {{600X}} 2645-5FU
|| IBM || 26455FU || Not Available || IBM || 26455FU || Not Available || IBM || Not Available || IBM || INET55WW || 11/30/1999
||
||
|-
| {{600X}} 2645-8EU
|| IBM || 26458EU || Not Available || IBM || 26458EU || Not Available || IBM || Not Available || IBM || ITET54WW || 11/30/1999
||
||
|-
| {{600X}} 2645-8EU
|| IBM || 26458EU || Not Available || IBM || 26458EU || Not Available || IBM || Not Available || IBM || ITET48WW || 11/30/1999
||
||POST/BIOS Version 1.13 old prior to upgrade
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====A series====
|-
| {{A21m}} 2628-FSG
|| IBM || 2628FSG || Not Available || IBM || 2628FSG || Not Available || IBM || Not Available || IBM || KXET24WW (1.02b) || 12/19/2000
||
||
|-
| {{A21m}} 2628-FSG
|| IBM || 2628FSG || Not Available || IBM || 2628FSG || Not Available || IBM || Not Available || IBM || KXET36WW (1.09 ) || 05/08/2003
||
||
|-
| {{A21m}} 2628-GTU
|| IBM || 2628GTU || Not Available || IBM || 2628GTU || Not Available || IBM || Not Available || IBM || KXET29WW (1.03d) || 03/21/2001
||
||
|-
| {{A22e}} 2655-KG1
|| IBM || 2655KG1 || Not Available || IBM || 2655KG1 || Not Available || IBM || Not Available || IBM || 10ET23WW (1.04 ) || 09/05/2001
||
||
|-
| {{A22e}} 2655-KG1
|| IBM || 2655KG1 || Not Available || IBM || 2655KG1 || Not Available || IBM || Not Available || IBM || 10ET26WW (1.07 ) || 06/13/2003
|| <nowiki></nowiki>
||
|-
| {{A22p}} 2629-USG
|| IBM || 2629USG || Not Available || IBM || 2629USG || Not Available || IBM || Not Available || IBM || KYET36WW (1.09a) || 10/17/2002
||
|| {{T-WARN|Outdated BIOS}}
|-
| {{A22p}} 2629-A2G
|| IBM || 2629A2G || Not Available || IBM || 2629A2G || Not Available || IBM || Not Available || IBM || KYET38WW (1.11 ) || 05/20/2004
|| <nowiki></nowiki>
||
|-
| {{A31}} 2652-PBU
|| IBM || 2652PBU || Not Available || IBM || 2652PBU || Not Available || IBM || Not Available || IBM || 1NET15WW (1.09 ) || 04/06/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1NHT04WW-1.01 ]-</nowiki>
||
|-
| {{A31p}} 2653-RNG
|| IBM || 2653RNG || Not Available || IBM || 2653RNG || Not Available || IBM || Not Available || IBM || 1NET16WW (1.10 ) || 10/19/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1NHT08WW-1.05 ]-</nowiki>
||
|-
| {{A31p}} 2653-H6U
|| IBM || 2653H6U || Not Available || IBM || 2653H6U || Not Available || IBM || Not Available || IBM || 1GET31WW (1.03 ) || 07/23/2002
||
|| {{T-WARN|Missing EC string, extremely outdated BIOS}}{{HELP|We need a report to know if the latest BIOS fixes the missing EC string}}
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====G series====
|-
| {{G41}} 2881-75M
|| IBM || 288175M || ThinkPad G41 || IBM || 288175M || Not Available || IBM || Not Available || IBM || 1XET47WW (1.06 ) || 01/14/2005
||
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====R series====
|-
| {{R40}} 2681-5UU
|| IBM || 26815UU || Not Available || IBM || 26815UU || Not Available || IBM || Not Available || IBM || 1OET57WW (1.23 ) || 03/23/2005
||
|| {{T-WARN|Outdated BIOS}}
|-
| {{R40}} 2681-HSG
|| IBM || 2681HSG || Not Available || IBM || 2681HSG || Not Available || IBM || Not Available || IBM || 1OET61WW (1.27 ) || 06/29/2006
||
|| {{T-WARN|Outdated BIOS}}
|-
| {{R40}} 2722-B3G
|| IBM || 2722B3G || Not Available || IBM || 2722B3G || Not Available || IBM || Not Available || IBM || 1PET62WW (1.30 ) || 09/29/2005
||
||
|-
| {{R40}} 2722-BDG
|| IBM || 2722BDG || Not Available || IBM || 2722BDG || Not Available || IBM || Not Available || IBM || 1PET65WW (1.33 ) || 06/29/2006
|| <nowiki></nowiki>
||
|-
| {{R40}} 2722-C4U
|| IBM || 2722CU4 || Not Available || IBM || 2722CU4 || Not Available || IBM || Not Available || IBM || 1PET46WW (1.14 ) || 07/15/2003
|| 1OHT37WW (1.09) 05/26/03
|| {{T-WARN|Outdated BIOS}}
|-
| {{R40}} 2722-C4U
|| IBM || 2722CU4 || Not Available || IBM || 2722CU4 || Not Available || IBM || Not Available || IBM || 1PET65WW (1.33 ) || 06/29/2006
|| 1OHT42WW (1.14) 05/23/05
||
|-
| {{R40}} 2897-B4U
|| IBM || 2897B4U || Not Available || IBM || 2897B4U || Not Available || IBM || Not Available || IBM || 1PET52WW (1.20 ) || 03/03/2004
||
||
|-
| {{R40e}} 2684-L8G
|| IBM || 2897B4U || Not Available || IBM || 2897B4U || Not Available || IBM || Not Available || IBM || 1SET62WW (1.30 ) || 07/09/2004
||
|| {{T-WARN|Outdated BIOS}}
|-
| {{R40e}} 2684-L8G
|| IBM || 2684L8G || Not Available || IBM || 2684L8G || Not Available || IBM || Not Available || IBM || 1SET70WW (1.38 ) || 11/15/2005
||
||
|-
| {{R50}} 1829-7QG
|| IBM || 0123456 || ThinkPad R50 || IBM || 0123456 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
|{{R50e}} 1834-JAG
|| IBM || 1834JAG || ThinkPad R50e || IBM || 1834JAG || Not Available || IBM || Not Available || IBM || 1WET82WW (2.02 ) || 02/21/2005
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
||
|-
|{{R50e}}
|| IBM || 1834S5G || ThinkPad R50e || IBM || 1834S5G || Not Available || IBM || Not Available || IBM || 1WET86WW (2.06 ) || 11/15/2005
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
|| {{T-WARN|Outdated BIOS}}
|-
|{{R50e}}
|| IBM || 1834S5G || ThinkPad R50e || IBM || 1834S5G || Not Available || IBM || Not Available || IBM || 1WET90WW (2.10 ) || 12/08/2006
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
||
|-
|{{R50p}} 1832-2AG
|| IBM || 18322AG || ThinkPad R50p || IBM || 18322AG || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1RHT66WW-3.00a ]-</nowiki>
||
|-
| {{R51}} 1829-DRG
|| IBM || 1829DRG || ThinkPad R51 || IBM || 1829DRG || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT66WW-3.00a ]-</nowiki>
||
|-
| {{R51}} 1829-9MG
|| IBM || 18299MG || ThinkPad R51 || IBM || 18299MG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 1829-L7G
|| IBM || 1829L7G || ThinkPad R51 || IBM || 1829L7G || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT70WW-3.03 ]-</nowiki>
||
|-
| {{R51}} [[1830-DG4]]
|| IBM || 1830DG4 || ThinkPad R51 || IBM || 1830DG4 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} [[1830-DG4]]
|| IBM || 1830DG4 || ThinkPad R51 || IBM || 1830DG4 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 1836-GEU
|| IBM || 1836GEU || ThinkPad R51 || IBM || 1836GEU || Not Available || IBM || Not Available || IBM || 1RETDLWW (3.17 ) || 07/27/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes. String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{R51}} 2883-ELU
|| IBM || 2883ELU || ThinkPad R51 || IBM || 2883ELU || Not Available || IBM || Not Available || IBM || 1VET69WW (1.27 ) || 03/03/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1VHT28WW-1.04 ]-</nowiki>
||
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad H || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
|| Weird system version, this bug is known fixed in latest BIOS
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52p || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET68WW (1.28 ) || 11/15/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52p || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET69WW (1.29 ) || 12/06/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1847-CTO
|| IBM || 1847W15 || ThinkPad R52 || IBM || 1847W15 || Not Available || IBM || Not Available || IBM || 76ET69WW (1.29 ) || 12/06/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1847-W62
|| IBM || 1847W62 || ThinkPad . || IBM || 1847W62 || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
|| Weird system version, this bug is known fixed in latest BIOS
|-
| {{R52}} 1847-W62
|| IBM || 1847W62 || ThinkPad R52 || IBM || 1847W62 || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1858-6MM
|| IBM || 18586MM || ThinkPad R52 || IBM || 18586MM || Not Available || IBM || Not Available || IBM || 70ET40WW (1.04 ) || 06/02/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{R52}} 1858-6SM
|| IBM || 18586SM || ThinkPad R52 || IBM || 18586SM || Not Available || IBM || Not Available || IBM || 70ET57WW (1.17 ) || 07/15/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{R52}} 1846-4CG
|| IBM || 18464CG || ThinkPad R52 || IBM || 18464CG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT15WW-1.05 ]-</nowiki>
||
|-
| {{R52}} 1846-4CG
|| IBM || 18464CG || ThinkPad R52 || IBM || 18464CG || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[76HT16WW-1.06 ]-</nowiki>
||
|-
| {{R52}} 1846-B5G
|| IBM || 1846B5G || ThinkPad H || IBM || 1846B5G || Not Available || IBM || Not Available || IBM || 76ET58WW (1.18 ) || 07/19/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[76HT14WW-1.04 ]-</nowiki>
||
|-
| {{R60e}} 0657-4TG
|| LENOVO || 06574TG || ThinkPad R60e || LENOVO || 06574TG || Not Available || LENOVO || Not Available || LENOVO || 7EET18WW (1.04 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7EHT13WW-1.05 ]-</nowiki>
||
|-
| {{R60}} 9456-6FG
|| LENOVO || 94566FG || ThinkPad R60 || LENOVO || 94566FG || Not Available || LENOVO || Not Available || LENOVO || 7CET50WW (1.05 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT19WW-1.07 ]-</nowiki>
||
|-
| {{R60}} 9456-6FG
|| LENOVO || 94566FG || ThinkPad R60 || LENOVO || 94566FG || Not Available || LENOVO || Not Available || LENOVO || 7CETB7WW (2.07 ) || 11/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-54G
|| LENOVO || 946154G || ThinkPad R60 || LENOVO || 946154G || Not Available || LENOVO || Not Available || LENOVO || 7CET50WW (1.05 ) || 07/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT19WW-1.07 ]-</nowiki>
||
|-
| {{R60}} 9461-54G
|| LENOVO || 946154G || ThinkPad R60 || LENOVO || 946154G || Not Available || LENOVO || Not Available || LENOVO || 7CETC1WW (2.11 ) || 01/09/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
|| With this bios version the brightness control buttons don't work for kernel < 2.6.20
|-
| {{R60}} 9461-54G
|| LENOVO || 946154G || ThinkPad R60 || LENOVO || 946154G || Not Available || LENOVO || Not Available || LENOVO || 7CET49WW (1.04 ) || 05/11/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT16WW-1.04 ]-</nowiki>
||
|-
| {{R60}} 9460MR2
|| LENOVO || 9460MR2 || ThinkPad R60 || LENOVO || 9460MR2 || Not Available || LENOVO || Not Available || LENOVO || 7CETC6WW (2.16 ) || 04/18/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-DXG
|| LENOVO || 9461DXG || ThinkPad R60 || LENOVO || 9461DXG || Not Available || LENOVO || Not Available || LENOVO || 7CETB6WW (2.06 ) || 10/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R60}} 9461-DXG
|| LENOVO || 9461DXG || ThinkPad R60 || LENOVO || 9461DXG || Not Available || LENOVO || Not Available || LENOVO || 7CETD2WW (2.22 ) || 05/28/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT22WW-1.10 ]-</nowiki>
||
|-
| {{R60}} 9462-GAG
|| LENOVO || 9462GAG || ThinkPad R60 || LENOVO || 9462GAG || Not Available || LENOVO || Not Available || LENOVO || 7CETB5WW (2.05 ) || 10/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7CHT21WW-1.09 ]-</nowiki>
||
|-
| {{R61}} 8918-5QG
|| LENOVO || 89185QG || ThinkPad R61 || LENOVO || 89185QG || Not Available || LENOVO || Not Available || LENOVO || 7KETA7WW (2.07 ) || 12/06/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8919-W4P
|| LENOVO || 8919W4P || ThinkPad R61 || LENOVO || 8919W4P || Not Available || LENOVO || Not Available || LENOVO || 7KET76WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
|| According to the sticker on the bottom of the notebook as well as according to Lenovo web it is 8919-CTO subtype
|-
| {{R61}} 8919-W6X
|| LENOVO || 8919W6X || ThinkPad R61 || LENOVO || 8919W6X || Not Available || LENOVO || Not Available || LENOVO || 7KET71WW (1.21 ) || 08/22/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{R61}} 8919-W6X
|| LENOVO || 8919W6X || ThinkPad R61 || LENOVO || 8919W6X || Not Available || LENOVO || Not Available || LENOVO || 7KETB9WW (2.19 ) || 06/05/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8919-DFG
|| LENOVO || 8918DFG || ThinkPad R61 || LENOVO || 8918DFG || Not Available || LENOVO || Not Available || LENOVO || 7KETA9WW (2.09 ) || 12/27/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 8943-DMG
|| LENOVO || 8943DMG || ThinkPad R61 || LENOVO || 8943DMG || Not Available || LENOVO || Not Available || LENOVO || 7QET34WW (1.16 ) || 03/24/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7QHT15WW-1.00 ]-</nowiki>
||
|-
| {{R61}} 7732-4TG
|| LENOVO || 77324TG || ThinkPad R61 || LENOVO || 77324TG || Not Available || LENOVO || Not Available || LENOVO || 7LET51WW (1.21 ) || 08/22/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{R61}} 7732-4TG
|| LENOVO || 77324TG || ThinkPad R61 || LENOVO || 77324TG || Not Available || LENOVO || Not Available || LENOVO || 7LETC5WW (2.25 ) || 11/14/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7732-NEG
|| LENOVO || 7732NEG || ThinkPad R61 || LENOVO || 7732NEG || Not Available || LENOVO || Not Available || LENOVO || 7LETB6WW (2.16 ) || 04/16/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7732-NEG
|| LENOVO || 7732NEG || ThinkPad R61 || LENOVO || 7732NEG || Not Available || LENOVO || Not Available || LENOVO || 7LETC5WW (2.25 ) || 11/14/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7732-NEG
|| LENOVO || 7732NEG || ThinkPad R61 || LENOVO || 7732NEG || Not Available || LENOVO || Not Available || LENOVO || 7LETC6WW (2.26 ) || 05/11/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7733-1ES
|| LENOVO || 77331ES || ThinkPad R61 || LENOVO || 77331ES || Not Available || LENOVO || Not Available || LENOVO || 7LETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7733-1ES
|| LENOVO || 77331ES || ThinkPad R61 || LENOVO || 77331ES || Not Available || LENOVO || Not Available || LENOVO || 7LETB4WW (2.14 ) || 03/24/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61}} 7733-A82
|| LENOVO || 7733A82 || ThinkPad R61/R61i || LENOVO || 7733A82 || Not Available || LENOVO || Not Available || LENOVO || 7LETC5WW (2.25 ) || 11/14/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
|| Intel graphics, 14.1" WXGA, Atheros wireless
|-
| {{R61i}} 7732-A12
|| LENOVO || 7732A12 || ThinkPad R61i || LENOVO || 7732A12 || Not Available || LENOVO || Not Available || LENOVO || 7KET76WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
|| Prior to Flashing
|-
| {{R61i}} 7732-A12
|| LENOVO || 7732A12 || ThinkPad R61i || LENOVO || 7732A12 || Not Available || LENOVO || Not Available || LENOVO || 7KETC8WW (2.28) || 05/26/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
|| Post Flashing
|-
| {{R61i}} 7650-D7G
|| LENOVO || 7650D7G || ThinkPad R61e || LENOVO || 7650D7G || Not Available || LENOVO || Not Available || LENOVO || 7PETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R61e}} 7650-E6G
|| LENOVO || 7650E6G || ThinkPad R61e || LENOVO || 7650E6G || Not Available || LENOVO || Not Available || LENOVO || 7PETB2WW (2.12 ) || 02/20/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{R400}} 7439-A85
|| LENOVO || 7439A85 || ThinkPad R400 || LENOVO || 7439A85 || Not Available || LENOVO || Not Available || LENOVO || 7UET45WW (1.15 ) || 09/08/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{R400}} 7443-TPA
|| LENOVO || 7443TPA || ThinkPad R400 || LENOVO || 7443TPA || Not Available || LENOVO || Not Available || LENOVO || 7UET49WW (1.19 ) || 10/17/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{R400}} 7443-TPA
|| LENOVO || 7443TPA || ThinkPad R400 || LENOVO || 7443TPA || Not Available || LENOVO || Not Available || LENOVO || 7UET50WW (1.20 ) || 10/30/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====S series====
|-
| {{s30}} 2639-4WJ
|| IBM || 26394WJ || Not Available || IBM || 2609BS1 || Not Available || IBM || Not Available || IBM || 18ET45WW (1.45) || 07/10/2001
|| <nowiki></nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====SL series====
|-
| {SL410} 2842-7PU || LENOVO || 28427PU || ThinkPad SL410 || LENOVO || 28427PU || Not Available || LENOVO || Not Available || LENOVO || 6JET69WW (1.27 ) || 11/30/2009
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6JHT54WW-1.174000]-</nowiki>
||
|-
| {{SL500}} 2746-3ZG || LENOVO || 27463ZG || ThinkPad SL500 || LENOVO || BOXSTER || 6AET 42WW || LENOVO || 6AET 42WW || LENOVO || 6AET42WW || 08/04/2008
|| <nowiki></nowiki>
|| {{T-WARN|IdeaPad EC and BIOS. This is an IdeaPad in disguise.}}
|-
| {{SL500}} 2746-4CG || LENOVO || 27464CG || ThinkPad SL500 || LENOVO || BOXSTER || 6AET 41WW || LENOVO || 6AET 41WW || LENOVO || 6AET41WW || 07/10/2008
|| <nowiki></nowiki>
|| {{T-WARN|IdeaPad EC and BIOS. This is an IdeaPad in disguise.}}
|-
| {{SL500}} 2764-EAG || LENOVO || 2746EAG || ThinkPad SL || LENOVO || 2746EAG || 6AET 58WW || LENOVO || 6AET 58WW || LENOVO || 6AET58WW || 05/29/2009
|| <nowiki></nowiki>
||
|-
| {{SL510}} 2847-7MG
|| LENOVO || 28477MG || ThinkPad SL510 || LENOVO || ? || not available || LENOVO || not available || LENOVO || 6JET72WW (1.30 ) || 01/26/2010
|| Handle 0x0018, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[6JHT57WW-1.177000]-
|| {{T-WARN|IdeaPad EC and BIOS.}}
|-
| {{SL400}} 2743-Rk3
|| LENOVO || 2743RK3 || ThinkPad SL || LENOVO || 2743RK3 || LENOVO 6AET59WW || LENOVO || LENOVO 6AET59WW || LENOVO || 6AET59WW || 08/26/2009
|| <nowiki></nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====T series====
|-
| {{T20}} 2647-UC2
|| IBM || 2647UC2 || Not Available || IBM || 2647UC2 || Not Available || IBM || Not Available || IBM || IYET45WW (1.08a) || 12/21/1999
||
|| {{T-WARN|Very outdated BIOS}}
|-
| {{T21}} 2647-8AG
|| IBM || 26478AG || Not Available || IBM || 26478AG || Not Available || IBM || Not Available || IBM || KZET22WW (1.04a) || 01/19/2001
||
||
|-
| {{T21}} 2647-9AU
|| IBM || 26479AU || Not Available || IBM || 26479AU || Not Available || IBM || Not Available || IBM || KZET33WW (1.15 ) || 03/28/2003
||
||
|-
| {{T21}} 2647-8AG
|| IBM || 26478AG || Not Available || IBM || 26478AG || Not Available || IBM || Not Available || IBM || KZET34WW (1.16 ) || 04/28/2004
||
||
|-
| {{T21}} 2647-8AU
|| IBM || 26478AU || Not Available || IBM || 26478AU || Not Available || IBM || Not Available || IBM || KZET34WW (1.16 ) || 04/28/2004
||
||
|-
| {{T21}} 2647-8GG
|| IBM || 26478GG || Not Available || IBM || 26478GG || Not Available || IBM || Not Available || IBM || 16ET29WW (1.09 ) || 02/28/2002
||
||
|-
| {{T22}} 2647-4EG
|| IBM || 26474EG || Not Available || IBM || 26474EG || Not Available || IBM || Not Available || IBM || 16ET31WW (1.11 ) || 03/20/2003
||
||
|-
| {{T22}} 2647-8EU
|| IBM || 26478EU || Not Available || IBM || 26478EU || Not Available || IBM || Not Available || IBM || 16ET32WW (1.12 ) || 04/27/2004
||
||
|-
| {{T23}} 2647
|| IBM || 2647 || Not Available || IBM || 2647 || Not Available || IBM || Not Available || IBM || 1AET56WW (1.13) || 07/23/2002
||
|| Manufactured in Greenock, Scotland
|-
| {{T23}} 2647
|| IBM || 2647 || Not Available || IBM || 2647 || Not Available || IBM || Not Available || IBM || 1AET64WW (1.20) || 07/23/2002
|| <nowiki>As above. Handle 0x0024, DMI type 11, 5 bytes OEM Strings String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a]-
</nowiki>
||
|-
| {{T23}} 2647-4MG
|| IBM || 26474MG || Not Available || IBM || 26474MG || Not Available || IBM || Not Available || IBM || 1AET58WW (1.14a) || 09/11/2002
|| <nowiki></nowiki>
||
|-
| {{T23}} 2647-4MG
|| IBM || 26474MG || Not Available || IBM || 26474MG || Not Available || IBM || Not Available || IBM || 1AET64WW (1.20 ) || 10/18/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-</nowiki>
||
|-
| {{T23}} 2647-4NU
|| IBM || 26474NU || Not Available || IBM || 26474NU || Not Available || IBM || Not Available || IBM || 1AET62WW (1.18 ) || 07/06/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-</nowiki>
||
|-
| {{T23}} 2647-8MG
|| IBM || 26478MG || Not Available || IBM || 26478MG || Not Available || IBM || Not Available || IBM || 1AET56WW (1.13 ) || 07/02/2002
||
|| Missing EC string, this bug is known to be fixed in latest BIOS
|-
| {{T23}} 2647-8MG
|| IBM || 26478MG || Not Available || IBM || 26478MG || Not Available || IBM || Not Available || IBM || 1AET62WW (1.18 ) || 07/06/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a]-</nowiki>
||
|-
| {{T23}} 2648-DG1
|| IBM || 2648DG1 || Not Available || IBM || 2648DG1 || Not Available || IBM || Not Available || IBM || 1AET61WW (1.17 ) || 05/29/2003
|| <nowiki></nowiki>
||
|-
| {{T23}} 2648-DG1
|| IBM || 2648DG1 || Not Available || IBM || 2648DG1 || Not Available || IBM || Not Available || IBM || 1AET64WW (1.20 ) || 10/18/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1AHT23WW-1.06a ]-</nowiki>
||
|-
| {{T30}} 2366-21U
|| IBM || 236621U || Not Available || IBM || 236621U || Not Available || IBM || Not Available || IBM || 1IET71WW (2.10 ) || 06/16/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1IHT20WW-1.07 ]-</nowiki>
||
|-
| {{T30}} 2366-82U
|| IBM || 236682U || Not Available || IBM || 236682U || Not Available || IBM || Not Available || IBM || 1IET69WW (2.08 ) || 06/11/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1IHT19WW-1.06]-</nowiki>
||
|-
| {{T30}} 2366-85G
|| IBM || 236685G || Not Available || IBM || 236685G || Not Available || IBM || Not Available || IBM || 1IET69WW (2.08 ) || 06/11/2004
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1IHT18WW-1.05 ]-</nowiki>
||
|-
| {{T30}} 2366-GU1
|| IBM || 2366GU1 || Not Available || IBM || 2366GU1 || Not Available || IBM || Not Available || IBM || 1IET69WW (2.08 ) || 06/11/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1IHT19WW-1.06 ]-</nowiki>
||
|-
| {{T30}} 2366-JBU
|| IBM || 2366JBU || Not Available || IBM || 2366JBU || Not Available || IBM || Not Available || IBM || 1IET71WW (2.10 ) || 06/16/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1IHT20WW-1.07 ]-</nowiki>
||
|-
| {{T40}} 2378-D2U
|| IBM || 2378D2U || ThinkPad T40 || IBM || 2378D2U || Not Available || IBM || Not Available || IBM || 1RETC2WW (3.03 ) || 04/07/2004
||
|| Missing EC string, this bug is known to be fixed in latest BIOS
|-
| {{T40}} 2373-42G
|| IBM || 237342G || ThinkPad T40 || IBM || 237342G || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
|| [[ATI Mobility Radeon 7500]]
||
|-
| {{T40}} 2373-NG5
|| IBM || 2373NG5 || ThinkPad T40 || IBM || 2373NG5 || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T40}} 2373-NG5
|| IBM || 2373NG5 || ThinkPad T40 || IBM || 2373NG5 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T40p}} 2373-G1G
|| IBM || 2373G1G || ThinkPad T40p || IBM || 2373G1G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-9FG
|| IBM || 23739FG || ThinkPad T41 || IBM || 23739FG || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-W63
|| IBM || 2373W63 || ThinkPad T41 || IBM || 2373W63 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-XNX
|| IBM || 2373XNX || ThinkPad T41 || IBM || 2373XNX || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-2FG
|| IBM || 23732FG || ThinkPad T41 || IBM || 23732FG || Not Available || IBM || Not Available || IBM || 1RET84WW (2.11 ) || 10/30/2003
||
|| Missing EC string, this bug is known to be fixed in latest BIOS
|-
| {{T41}} 2373-7FG
|| IBM || 23737FG || ThinkPad T41 || IBM || 23737FG || Not Available || IBM || Not Available || IBM || 1RET87WW (2.14 ) || 01/26/2004
||
||
|-
| {{T41}} 2373-7FG
|| IBM || 23737FG || ThinkPad T41 || IBM || 23737FG || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
|| After upgrade from BIOS v. 2.14
|-
| {{T41}} 2373-TG5
|| IBM || 2373TG5 || ThinkPad T41 || IBM || 2373TG5 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2374-312
|| IBM || 2374312 || ThinkPad T41 || IBM || 2374312 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2379-DJU
|| IBM || 2379DJU || ThinkPad T41 || IBM || 2379DJU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-A10
|| IBM || 2373A10 || ThinkPad T41 || IBM || 2373A10 || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41}} 2373-A10
|| IBM || 2373A10 || ThinkPad T41 || IBM || 2373A10 || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
|| After upgrade from BIOS v. 3.20
|-
| {{T41p}} 2373-GHG
|| IBM || 2373GHG || ThinkPad T41p || IBM || 2373GHG || Not Available || IBM || Not Available || IBM || 1RETDIWW (3.14 ) || 01/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41p}} 2373-GEG
|| IBM || 2373GEG || ThinkPad T41p || IBM || 2373GEG || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki> Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T41p}} 2373-GJJ
|| IBM || 2373GJJ || ThinkPad T41p || IBM || 2373GJJ || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-FWG
|| IBM || 2373FWG || ThinkPad T42 || IBM || 2373FWG || Not Available || IBM || Not Available || IBM || 1RETDHWW (3.13 ) || 10/29/2004
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-JTU
|| IBM || 2373JTU || ThinkPad T42 || IBM || 2373JTU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-M1G
|| IBM || 2373M1G || ThinkPad T42 || IBM || 2373M1G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-VJA
|| IBM || 2373VJA || ThinkPad T42 || IBM || 2373VJA || Not Available || IBM || Not Available || IBM || 1RETDRWW (3.23 ) || 06/18/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2373-F2G
|| IBM || 2373F2G || ThinkPad T42 || IBM || 2373F2G || Not Available || IBM || Not Available || IBM || 1RETDIWW (3.14 ) || 01/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2374-4WU
|| IBM || 23744WU || ThinkPad T42 || IBM || 23744WU || Not Available || IBM || Not Available || IBM || 1RETDNWW (3.19 ) || 10/13/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2374-WEH
|| IBM || 2374WEH || ThinkPad T42 || IBM || 2374WEH || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42}} 2378-FVU
|| IBM || 2378FVU || ThinkPad T42 || IBM || 2378FVU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-A64
|| IBM || 2373A64 || ThinkPad T42p || IBM || 2373A64 || Not Available || IBM || Not Available || IBM || 1RETDIWW (3.14 ) || 01/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byteString 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-KXU
|| IBM || 2373KXU || ThinkPad T42p || IBM || 2373KXU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-KUU
|| IBM || 2373KUU || ThinkPad T42p || IBM || 2373KUU || Not Available || IBM || Not Available || IBM || 1RETDMWW (3.18 ) || 09/15/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2373-GYG
|| IBM || 2373GYG || ThinkPad T42p || IBM || 2373GYG || Not Available || IBM || Not Available || IBM || 1RETDOWW (3.20 ) || 02/27/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2374-CP5
|| IBM || 2374CP5 || ThinkPad T42p || IBM || 2374CP5 || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2379-DYU
|| IBM || 2379DYU || ThinkPad T42p || IBM || 2379DYU || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T42p}} 2372-Q2G
|| IBM || 2373Q2G || ThinkPad T42p || IBM || 2373Q2G || Not Available || IBM || Not Available || IBM || 1RETDPWW (3.21 ) || 06/02/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-</nowiki>
||
|-
| {{T43}} 1871-4AG
|| IBM || 18714AG || ThinkPad T43 || IBM || 18714AG || Not Available || IBM || Not Available || IBM || 70ET64WW (1.24 ) || 02/13/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT27WW-1.04 ]-</nowiki>
||
|-
| {{T43}} 1871-4AG
|| IBM || 18714AG || ThinkPad T43 || IBM || 18714AG || Not Available || IBM || Not Available || IBM || 70ET62WW (1.22 ) || 05/29/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03]-</nowiki>
||
|-
| {{T43}} 1871-4AG
|| IBM || 18714AG || ThinkPad T43 || IBM || 18714AG || Not Available || IBM || Not Available || IBM || 70ET69WW (1.29 ) || 05/29/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT28WW-1.05]-</nowiki>
||
|-
| {{T43}} 1871-F1G
|| IBM || 1871F1G || ThinkPad T43 || IBM || 1871F1G || Not Available || IBM || Not Available || IBM || 70ET61WW (1.21 ) || 11/01/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[70HT26WW-1.03 ]-</nowiki>
||
|-
| {{T43}} 2686-DGU
|| IBM || 2686DGU || ThinkPad T43 || IBM || 2686DGU || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]-</nowiki>
||
|-
| {{T43}} 2669-WE5
|| IBM || 2669WE5 || ThinkPad T43 || IBM || 2669WE5 || Not Available || IBM || Not Available || IBM || 1YET56WW (1.21 ) || 07/06/2005
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
|| User reports this is really a 2669-CEU with 1GB RAM + BlueTooth, and not a 2669-WE5 (unverified if this makes sense)
|-
| {{T43}} 2668-WEW
|| IBM || 2668WEW || ThinkPad T43 || IBM || 2668WEW || Not Available || IBM || Not Available || IBM || 1YET56WW (1.21 ) || 07/06/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43}} 2668-WSY
|| IBM || 2668WSY || ThinkPad T43 || IBM || 2668WSY || Not Available || IBM || Not Available || IBM || 1YET62WW (1.27 ) || 05/18/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT29WW-1.06 ]-</nowiki>
||
|-
| {{T43}} 2668-74G
|| IBM || 266874G || ThinkPad T43 || IBM || 266874G || Not Available || IBM || Not Available || IBM || 1YET57WW (1.22 ) || 07/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43p}} 2668-G2G
|| IBM || 2668G2G || ThinkPad T43p || IBM || 2668G2G || Not Available || IBM || Not Available || IBM || 1YET47WW (1.08 ) || 06/09/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43p}} 2668-H1G
|| IBM || 2668H1G || ThinkPad T43p || IBM || 2668H1G || Not Available || IBM || Not Available || IBM || 1YET45WW (1.06a) || 06/02/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43p}} 2687-D5U
|| IBM || 2687D5U || ThinkPad T43p || IBM || 2687D5U || Not Available || IBM || Not Available || IBM || 1YET59WW (1.24 ) || 11/07/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T43p}} 2668-F8G
|| IBM || 2668F8G || ThinkPad T43p || IBM || 2668F8G || Not Available || IBM || Not Available || IBM || 1YET57WW (1.22 ) || 07/20/2005
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1YHT26WW-1.03 ]-</nowiki>
||
|-
| {{T60}} 1951-24G
|| LENOVO || 195124G || ThinkPad T60 || LENOVO || 195124G || Not Available || LENOVO || Not Available || LENOVO || 79ET65WW (1.09a) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60}} 1952-W5R
|| LENOVO || 1952W5R || ThinkPad T60 || LENOVO || 1952W5R || Not Available || LENOVO || Not Available || LENOVO || 79ET61WW (1.06 ) || 05/24/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60}} 1952-W5R
|| LENOVO || 1952W5R || ThinkPad T60 || LENOVO || 1952W5R || Not Available || LENOVO || Not Available || LENOVO || 79ETD2WW (2.12 ) || 04/12/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2007-49G
|| LENOVO || 200749G || ThinkPad T60 || LENOVO || 200749G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60}} 2007-77G
|| LENOVO || 200777G || ThinkPad T60 || LENOVO || 200777G || Not Available || LENOVO || Not Available || LENOVO || 79ETD1WW (2.11 ) || 03/15/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2007-FSG
|| LENOVO || 2007FSG || ThinkPad T60 || LENOVO || 2007FSG || Not Available || LENOVO || Not Available || LENOVO || 79ET66WW (1.10 ) || 08/02/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60}} 1951-CA2
|| LENOVO || 1951CA2 || ThinkPad T60 || LENOVO || 1951CA2 || Not Available || LENOVO || Not Available || LENOVO || 79ETD9WW (2.19 ) || 09/19/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2623-D6U
|| LENOVO || 2623D6U || ThinkPad T60 || LENOVO || 2623D6U || Not Available || LENOVO || Not Available || LENOVO || 79ET56WW (1.02 ) || 02/28/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT42WW-1.01 ]-</nowiki>
||
|-
| {{T60}} 2007-63G
|| LENOVO || 200763G || ThinkPad T60 || LENOVO || 200763G || Not Available || LENOVO || Not Available || LENOVO || 79ET65WW (1.09a) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60}} 2007-63G
|| LENOVO || 200763G || ThinkPad T60 || LENOVO || 200763G || Not Available || LENOVO || Not Available || LENOVO || 79ETE5WW (2.25 ) || 08/27/2009
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 2007-BF3
|| LENOVO || 2007BF3 || ThinkPad T60 || LENOVO || 2007BF3 || Not Available || LENOVO || Not Available || LENOVO || 79ETD7WW (2.17 ) || 08/23/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 8744-HCG
|| LENOVO || 8744HCG || ThinkPad T60 || LENOVO || 8744HCG || Not Available || LENOVO || Not Available || LENOVO || 7IET25WW (1.06 ) || 03/15/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 8744-HCG
|| LENOVO || 8744HCG || ThinkPad T60 || LENOVO || 8744HCG || Not Available || LENOVO || Not Available || LENOVO || 7IET37WW (1.18 ) || 04/01/2010
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60}} 1951-CZ1
|| LENOVO || 1951CZ1 || ThinkPad T60 || LENOVO || 1951CZ1 || Not Available || LENOVO || Not Available || LENOVO || 79ETE3WW (2.23 ) || 09/12/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2007-83U
|| LENOVO || 200783U || ThinkPad T60p || LENOVO || 200783U || Not Available || LENOVO || Not Available || LENOVO || 79ET60WW (1.05a) || 04/18/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[79HT43WW-1.02 ]-</nowiki>
||
|-
| {{T60p}} 2007-93G
|| LENOVO || 200793G || ThinkPad T60p || LENOVO || 200793G || Not Available || LENOVO || Not Available || LENOVO || 79ET62WW (1.07 ) || 06/12/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[79HT45WW-1.04 ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ET66WW (1.10 ) || 08/02/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ET67WW (1.11 ) || 08/29/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2007-93U
|| LENOVO || 200793U || ThinkPad T60p || LENOVO || 200793U || Not Available || LENOVO || Not Available || LENOVO || 79ETC3WW (2.03 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2007-ZK4
|| LENOVO || 2007ZK4 || ThinkPad T60p || LENOVO || 2007ZK4 || Not Available || LENOVO || Not Available || LENOVO || 79ETD3WW (2.13 ) || 04/30/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T60p}} 2613-ESU
|| LENOVO || 2613ESU || ThinkPad T60p || LENOVO || 2613ESU || Not Available || LENOVO || Not Available || LENOVO || 79ET67WW (1.11 ) || 08/29/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
| {{T60p}} 2623-DDU
|| LENOVO || 2623DDU || ThinkPad T60p || LENOVO || 2623DDU || Not Available || LENOVO || Not Available || LENOVO || 79ETC3WW (2.03 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[79HT50WW-1.07 ]-</nowiki>
||
|-
| {{T61}} 6457-W2C
|| LENOVO || 6457W2C || ThinkPad T61 || LENOVO || 6457W2C || Not Available || LENOVO || Not Available || LENOVO || 7LETB0WW (2.10 ) || 01/21/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 6460-EBG
|| LENOVO || 6460EBG || ThinkPad T61 || LENOVO || 6460EBG || Not Available || LENOVO || Not Available || LENOVO || 7LETB7WW (2.17 ) || 04/25/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 6460-EBG
| LENOVO || 6460EBG || ThinkPad T61 || LENOVO || 6460EBG || Not Available || LENOVO || Not Available || LENOVO || 7LETC4WW (2.24 ) || 08/15/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 6465-CTO
|| LENOVO || 6465CTO || ThinkPad T61 || LENOVO || 6465CTO || Not Available || LENOVO || Not Available || LENOVO || 7LETB2WW (2.12 ) || 02/20/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 6466-9MG
|| LENOVO || 64669MG || ThinkPad T61 || LENOVO || 64669MG || Not Available || LENOVO || Not Available || LENOVO || 7LETC7WW (2.27 ) || 04/08/2010
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 7659-W13
|| LENOVO || 7659W13 || ThinkPad T61 || LENOVO || 7659W13 || Not Available || LENOVO || Not Available || LENOVO || 7LET44WW (1.14 ) || 06/27/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61}} 7659-W13
|| LENOVO || 7659W13 || ThinkPad T61 || LENOVO || 7659W13 || Not Available || LENOVO || Not Available || LENOVO || 7LETC6WW (2.26 ) || 05/11/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 7662-XDU
|| LENOVO || 7662XDU || ThinkPad T61 || LENOVO || 7662XDU || 7662XDU|| LENOVO || Not Available || LENOVO || 7LET37WW (1.07 ) || 04/17/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7KHT19WW-1.03 ]-</nowiki>
|| {{T-WARN|BIOS and EC firmware have different IDs}}
|-
| {{T61}} 7661-A56
|| LENOVO || 7661A56 || ThinkPad T61 || LENOVO || 7661A56 || Not Available || LENOVO || Not Available || LENOVO || 7LET39WW (1.09 ) || 05/14/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT21WW-1.05 ]-</nowiki>
||
|-
| {{T61}} 8895-WFD
|| LENOVO || 8895WFD || ThinkPad T61 || LENOVO || 8895WFJ || Not Available || LENOVO || Not Available || LENOVO || 7LETC5WW (2.25 ) || 11/14/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61}} 8897-CTO
|| LENOVO || 8897CTO || ThinkPad T61 || LENOVO || 8897CTO || Not Available || LENOVO || Not Available || LENOVO || 7LET52WW (1.22 ) || 08/27/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61}} 8897-CTO
|| LENOVO || 8897CTO || ThinkPad T61 || LENOVO || 8897CTO || Not Available || LENOVO || Not Available || LENOVO || 7LET56WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61p}} 6457-B64
|| LENOVO || 6457B64 || ThinkPad T61p || LENOVO || 6457B64 || Not Available || LENOVO || Not Available || LENOVO || 7LETC1WW (2.21 ) || 07/01/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T61p}} 6459-A12
|| LENOVO || 6459A12 || ThinkPad T61p || LENOVO || 6459A12 || Not Available || LENOVO || Not Available || LENOVO || 7LET56WW (1.26 ) || 10/18/2007
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT22WW-1.06 ]-</nowiki>
||
|-
| {{T61p}} 6459-CTO
|| LENOVO || 6459CTO || ThinkPad T61p || LENOVO || 6459CTO || Not Available || LENOVO || Not Available || LENOVO || 7LETC6WW (2.26 ) || 05/11/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7KHT24WW-1.08 ]-</nowiki>
||
|-
| {{T400}} 6474-1EG
|| LENOVO || 64741EG || ThinkPad T400 || LENOVO || 64741EG || Not Available || LENOVO || Not Available || LENOVO || 7UET48WW (1.18 ) || 10/09/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01
]-</nowiki>
||
|-
| {{T400}} 6474-19G
|| LENOVO || 647419G || ThinkPad T400 || LENOVO || 647419G || Not Available || LENOVO || Not Available || LENOVO || 7UET61WW (2.07 ) || 02/13/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{T400}} 6475-FM4
|| LENOVO || 6475FM4 || ThinkPad T400 || LENOVO || 6475FM4 || Not Available || LENOVO || Not Available || LENOVO || 7UET43WW (1.13 ) || 08/19/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
|| Before BIOS update
|-
| {{T400}} 6475-FM4
|| LENOVO || 6475FM4 || ThinkPad T400 || LENOVO || 6475FM4 || Not Available || LENOVO || Not Available || LENOVO || 7UET64WW (2.12 ) || 03/13/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
|| After BIOS update
|-
| {{T400s}} 2801-CTO
|| LENOVO || 2801CTO || ThinkPad T400s || LENOVO || 2801CTO || Not Available || LENOVO || Not Available || LENOVO || 6HET21WW (1.06 ) || 07/27/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6HHT13WW-1.01]-</nowiki>
||
|-
| {{T400s}} 2815-2SG
|| LENOVO || 28152SG || ThinkPad T400s || LENOVO || 28152SG || Not Available || LENOVO || Not Available || LENOVO || 6HET17WW (1.02 ) || 05/18/2009 No code specified for -e.
||
||
|-
| {{T410}} 2522-AT6
|| LENOVO || 2522AT6 || ThinkPad T410 || LENOVO || 2522AT6 || Not Available || LENOVO || Not Available || LENOVO || 6IET65WW (1.25 ) || 06/07/2010
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6IHT35WW-1.10 ]-</nowiki>
||
|-
| {{T410s}} 2912-39G
|| LENOVO || 291239G || ThinkPad T410s || LENOVO || 291239G || Not Available || LENOVO || Not Available || LENOVO || 6UET27WW (1.05 ) || 01/14/2010
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6UHT24WW-1.05 ]-</nowiki>
||
|-
| {{T500}} 2055-A81
|| LENOVO || 2055A81 || ThinkPad T500 || LENOVO || 2055A81 || Not Available || LENOVO || Not Available || LENOVO || 6FET46WW (1.16 ) || 09/24/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{T500}} 2055-A81
|| LENOVO || 2055A81 || ThinkPad T500 || LENOVO || 2055A81 || Not Available || LENOVO || Not Available || LENOVO || 6FET50WW (1.20 ) || 10/30/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{T500}} 2055-45G
|| LENOVO || 205545G || ThinkPad T500 || LENOVO || 205545G || Not Available || LENOVO || Not Available || LENOVO || 6FET49WW (1.19 ) || 10/17/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{T500}} 2242-CTO
|| LENOVO || 2242CTO || ThinkPad T500 || LENOVO || 2242CTO || Not Available || LENOVO || Not Available || LENOVO || 6FET66WW (2.16 ) || 04/22/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT12WW-1.01 ]-</nowiki>
||
|-
| {{T510}} 4313-CTO
|| LENOVO || 4313CTO || ThinkPad T510 || LENOVO || 4313CTO || Not Available || LENOVO || Not Available || LENOVO || 6MET42WW (1.05 ) || 12/22/2009
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6MHT32WW-1.07 ]-</nowiki>
||
|-
| {{T510}} 4313-CTO
|| LENOVO || 4313CTO || ThinkPad T510 || LENOVO || 4313CTO || Not Available || LENOVO || Not Available || LENOVO || 6MET49WW (1.12 ) || 02/22/2010
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6MHT33WW-1.08 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====W series====
|-
| {{W500}} 4061-AW9
|| LENOVO || 4061AW9 || ThinkPad W500 || LENOVO || 4061AW9 || Not Available || LENOVO || Not Available || LENOVO || 6FET79WW (3.09 ) || 10/02/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7VHT14WW-1.03 ]-</nowiki>
||
|-
| {{W510}} 4319-3CG
|| LENOVO || 43193CG || ThinkPad W510 || LENOVO || 43193CG || Not Available || LENOVO || Not Available || LENOVO || 6NET46WW (1.09 ) || 01/20/2010
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6MHT31WW-1.06 ]-</nowiki>
||
|-
| {{W700}} 2757-CTO
|| LENOVO || 2757CTO || ThinkPad W700 || LENOVO || 2757CTO || Not Available || LENOVO || Not Available || LENOVO || 7ZETA8WW (2.08 ) || 09/24/2009
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7ZHT22WW-1.05 ]-</nowiki>
||
|-
| {{W700}} 2757-CTO
|| LENOVO || 2757CTO || ThinkPad W700 || LENOVO || 2757CTO || Not Available || LENOVO || Not Available || LENOVO || 7ZETB1WW (2.11 ) || 03/12/2010
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7ZHT24WW-1.07 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====X series====
|-
| {{X20}} 2662-31G
|| IBM || 266231G || Not Available || IBM || 266231G || Not Available || IBM || Not Available || IBM || IZET9DWW (2.25 ) || 04/17/2003
||
||
|-
| {{X20}} 2662-32G
|| IBM || 266232G || Not Available || IBM || 266232G || Not Available || IBM || Not Available || IBM || IZET9AWW (2.22 ) || 09/11/2002
||
||
|-
| {{X22}} 2662-95U
|| IBM || 266295U || Not Available || IBM || 266295U || Not Available || IBM || Not Available || IBM || 1DET70WW (1.32 ) || 06/10/2003
||
||
|-
| {{X23}} 2662-EBG
|| IBM || 2662EBG || Not Available || IBM || 2662EBG || Not Available || IBM || Not Available || IBM || 1DET70WW (1.32 ) || 06/10/2003
||
||
|-
| {{X24}} 2662-MPU
|| IBM || 62MPUFX || Not Available || IBM || 62MPUFX || Not Available || IBM || Not Available || IBM || 1DET67WW (1.29 ) || 12/18/2002
||
||
|-
| {{X30}} 2672-42G
|| IBM || 267242G || Not Available || IBM || 267242G || Not Available || IBM || Not Available || IBM || 1KET42WW (1.03 ) || 12/02/2002
|| <nowiki></nowiki>
||
|-
| {{X30}} 2672-42G
|| IBM || 267242G || Not Available || IBM || 267242G || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
|| {{X30}} 2672-4BU
|| IBM || 26724BU || Not Available || IBM || 26724BU || Not Available || IBM || Not Available || IBM || 1KET44WW (1.05 ) || 05/30/2003
|| <nowiki></nowiki>
||
|-
| {{X30}} 2672-4HU
|| IBM || 26724HU || Not Available || IBM || 26724HU || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
| {{X30}} 2672-PG3
|| IBM || 2672PG3 || Not Available || IBM || 2672PG3 || Not Available || IBM || Not Available || IBM || 1KET48WW (1.09 ) || 06/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1KHT18WW-1.06 ]-</nowiki>
||
|-
| {{X31}} 2672-C2G
|| IBM || 2672C2G || Not Available || IBM || 2672C2G || Not Available || IBM || Not Available || IBM || 1QET36WW (1.04a) || 06/30/2003
|| <nowiki></nowiki>
||
|-
| {{X31}} 2672-C2G
|| IBM || 2672C2G || ThinkPad X31 || IBM || 2672C2G || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2672-CEG
|| IBM || 2672CEG || Not Available || IBM || 2672CEG || Not Available || IBM || Not Available || IBM || 1QET36WW (1.04a) || 06/30/2003
|| <nowiki></nowiki>
||
|-
| {{X31}} 2672-CEG
|| IBM || 2672CEG || ThinkPad X31 || IBM || 2672CEG || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2672-JXU
|| IBM || 2672JXU || ThinkPad X31 || IBM || 2672JXU || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2672-FG2
|| IBM || 2672FG2 || ThinkPad X31 || IBM || 2672FG2 || Not Available || IBM || Not Available || IBM || 1QET73WW (2.11 ) || 02/13/2004
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT16WW-1.03 ]-</nowiki>
||
|-
| {{X31}} 2672-FG2
|| IBM || 2672FG2 || ThinkPad X31 || IBM || 2672FG2 || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2672-PG9 (before update)
|| IBM || 2672PG9 || ThinkPad X31 || IBM || 2672PG9 || Not Available || IBM || Not Available || IBM || 1QET73WW (2.11 ) || 02/13/2004
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT16WW-1.03 ]-</nowiki>
||
|-
| {{X31}} 2672-PG9 (after update)
|| IBM || 2672PG9 || ThinkPad X31 || IBM || 2672PG9 || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X31}} 2673-C2G
|| IBM || 2673C2G || ThinkPad X31 || IBM || 2673C2G || Not Available || IBM || Not Available || IBM || 1QET65WW (2.03 ) || 10/10/2003
|| <nowiki></nowiki>
||
|-
| {{X31}} 2673-C2G
|| IBM || 2673C2G || ThinkPad X31 || IBM || 2673C2G || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X32}} 2884-A3U
|| IBM || 2884A3U || ThinkPad X32 || IBM || 2884A3U || Not Available || IBM || Not Available || IBM || 1QET94WW (3.00d) || 01/23/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT22WW-1.07b ]-</nowiki>
||
|-
| {{X32}} 2672-M3G
|| IBM || 2672M3G || ThinkPad X32 || IBM || 2672M3G || Not Available || IBM || Not Available || IBM || 1QET94WW (3.00d) || 01/23/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT22WW-1.07b ]-</nowiki>
||
|-
| {{X32}} 2673-M4U
|| IBM || 2673M4U || ThinkPad X32 || IBM || 2673M4U || Not Available || IBM || Not Available || IBM || 1QET97WW (3.02 ) || 09/22/2005
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1QHT23WW-1.08 ]-</nowiki>
||
|-
| {{X40}} 2386-7JG
|| IBM || 23717JG || ThinkPad X40 || IBM || 23717JG || Not Available || IBM || Not Available || IBM || 1UETD1WW (2.06 ) || 03/01/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTB2WW-1.62 ]-</nowiki>
||
|-
| {{X40}} 2386-H4G
|| IBM || 2386H4G || ThinkPad X40 || IBM || 2386H4G || Not Available || IBM || Not Available || IBM || 1UET92WW (1.42 ) || 09/16/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[1UHT82WW-1.32 ]-</nowiki>
||
|-
| {{X40}} 2371-8NG
|| IBM || 23718NG || ThinkPad X40 || IBM || 23718NG || Not Available || IBM || Not Available || IBM || 1UETB7WW (1.67 ) || 07/15/2005
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHT58WW-1.12 ]-</nowiki>
||
|-
| {{X40}} 2371-Y29
|| IBM || 2371Y29 || ThinkPad X40 || IBM || 2371Y29 || Not Available || IBM || Not Available || IBM || 1UETD3WW (2.08 ) || 12/21/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTA6WW-1.56 ]-</nowiki>
||
|-
| {{X40}} 2371-W9F
|| IBM || 2371W9F || ThinkPad X40 || IBM || 2371W9F || Not Available || IBM || Not Available || IBM || 1UETC8WW (2.03 ) || 09/28/2005
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTB2WW-1.62 ]-</nowiki>
||
|-
| {{X40}} 2371-W9F
|| IBM || 2371W9F || ThinkPad X40 || IBM || 2371W9F || Not Available || IBM || Not Available || IBM || 1UETD3WW (2.08 ) || 12/21/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTB2WW-1.62 ]-</nowiki>
||
|-
| {{X40}} 2371-Y1Y
|| IBM || 2371Y1Y || ThinkPad X40 || IBM || 2371Y1Y || Not Available || IBM || Not Available || IBM || 1UET93WW (1.43 ) || 10/13/2004
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHT82WW-1.32 ]-</nowiki>
||
|-
| {{X40}} 2371-Y1Y
|| IBM || 2371Y1Y || ThinkPad X40 || IBM || 2371Y1Y || Not Available || IBM || Not Available || IBM || 1UETD3WW (2.08 ) || 12/21/2006
|| <nowiki>Handle 0x0024, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[1UHTB2WW-1.62 ]-</nowiki>
||
|-
| {{X41}} 2525-65G
|| IBM || 252565G || ThinkPad X41 || IBM || 252565G || Not Available || IBM || Not Available || IBM || 74ET63WW (2.08 ) || 10/17/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[74HT25WW-1.00 ]-</nowiki>
||
|-
| {{X41}} 2525-FAG
|| IBM || 2525FAG || ThinkPad X41 || IBM || 2525FAG || Not Available || IBM || Not Available || IBM || 74ET61WW (2.06 ) || 03/14/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[74HT26WW-1.01 ]-</nowiki>
||
|-
| {{X41}} 2525-FAG
|| IBM || 2525FAG || ThinkPad X41 || IBM || 2525FAG || Not Available || IBM || Not Available || IBM || 74ET64WW (2.09 ) || 12/14/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[74HT27WW-1.02 ]-</nowiki>
||
|-
| {{X41}} 2525-HU1
|| IBM || 2525HU1 || ThinkPad X41 || IBM || 2525HU1 || Not Available || IBM || Not Available || IBM || 74ET48WW (1.17a) || 06/07/2005
|| <nowiki>Handle 0x0025, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[74HT25WW-1.00 ]-</nowiki>
||
|-
| {{X41t}} 1866-CRG
|| IBM || 1866CRG || ThinkPad X41 Tablet || IBM || 1866CRG || Not Available || IBM || Not Available || IBM || 75ET60WW (2.06 ) || 12/19/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[75HT19WW-1.01 ]-</nowiki>
||
|-
| {{X41t}} 1866-CTO
|| IBM || 1866CTO || ThinkPad X41 Tablet || IBM || 1866CTO || Not Available || IBM || Not Available || IBM || 75ET60WW (2.06 ) || 12/19/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[75HT20WW-1.02 ]-</nowiki>
||
|-
| {{X41t}} 1866-WSF
|| IBM || 1866WSF || ThinkPad X41 Tablet || IBM || 1866WSF || Not Available || IBM || Not Available || IBM || 75ET57WW (2.03 ) || 06/14/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[75HT20WW-1.02 ]-</nowiki>
||
|-
| {{X41t}} 1869-CLG
|| IBM || 1869CLG || ThinkPad X41 Tablet || IBM || 1869CLG || Not Available || IBM || Not Available || IBM || 75ET56WW (2.02 ) || 03/14/2006
|| <nowiki>Handle 0x0025, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[75HT19WW-1.01 ]-</nowiki>
||
|-
| {{X60}} 1709-47U
|| LENOVO || 170947U || ThinkPad X60 || LENOVO || 170947U || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki>
||
|-
| {{X60}} 1709-GDJ
|| LENOVO || 1709GDJ || ThinkPad X60 || LENOVO || 1709GDJ || Not Available || LENOVO || Not Available || LENOVO || 7BETC2WW (2.03 ) || 10/16/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT36WW-1.09 ]-</nowiki>
||
|-
| {{X60}} 1706-B69
|| LENOVO || 1706B69 || ThinkPad X60 || LENOVO || 1706B69 || Not Available || LENOVO || Not Available || LENOVO || 7BETC8WW (2.09 ) || 03/14/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT37WW-1.10 ]-</nowiki>
||
|-
| {{X60}} 1706-GMG
|| LENOVO || 1706GMG || ThinkPad X60 || LENOVO || 1706GMG || Not Available || LENOVO || Not Available || LENOVO || 7BETC4WW (2.05 ) || 11/17/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT37WW-1.10 ]-</nowiki>
||
|-
| {{X60}} 1706-GMG
|| LENOVO || 1706GMG || ThinkPad X60 || LENOVO || 1706GMG || Not Available || LENOVO || Not Available || LENOVO || 7BETD7WW (2.18 ) || 11/20/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60s}} 1702-55G
|| LENOVO || 170255G || ThinkPad X60s || LENOVO || 170255G || Not Available || LENOVO || Not Available || LENOVO || 7BET44WW (1.04 ) || 03/13/2006
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[7BHT29WW-1.02 ]-</nowiki>
||
|-
| {{X60s}} 1702-5FG
|| LENOVO || 17025FG || ThinkPad X60s || LENOVO || 17025FG || Not Available || LENOVO || Not Available || LENOVO || 7BET49WW (1.09 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT34WW-1.07 ]-</nowiki>
||
|-
| {{X60s}} 1704-56G
|| LENOVO || 170456G || ThinkPad X60s || LENOVO || 170456G || Not Available || LENOVO || Not Available || LENOVO || 7BET43WW (1.03 ) || 02/13/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7BHT28WW-1.01 ]-</nowiki>
||
|-
| {{X60s}} 1704-56G
|| LENOVO || 1704-56G || ThinkPad X60s || LENOVO || 170456G || Not Available || LENOVO || Not Available || LENOVO || 7BETD5WW (2.16 ) || 03/31/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60s}} 1704-5UG
|| LENOVO || 17045UG || ThinkPad X60s || LENOVO || 17045UG || Not Available || LENOVO || Not Available || LENOVO || 7BETD2WW (2.13 ) || 08/10/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60s}} 1704-5UG
|| LENOVO || 17045UG || ThinkPad X60s || LENOVO || 17045UG || Not Available || LENOVO || Not Available || LENOVO || 7BETD3WW (2.14 ) || 10/04/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60s}} 1704-5UG
|| LENOVO || 17045UG || ThinkPad X60s || LENOVO || 17045UG || Not Available || LENOVO || Not Available || LENOVO || 7BETD7WW (2.18 ) || 11/20/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7BHT40WW-1.13 ]-</nowiki>
||
|-
| {{X60t}} 6365-CTO
|| LENOVO || 6365CTO || ThinkPad X60 Tablet || LENOVO || 6365CTO || Not Available || LENOVO || Not Available || LENOVO || 7JET25WW (1.10 ) || 08/17/2007
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT13WW-1.04 ]-</nowiki>
||
|-
| {{X60t}} 6363-J3G
|| LENOVO || 6363J3G || ThinkPad X60 Tablet || LENOVO || 6363J3G || Not Available || LENOVO || Not Available || LENOVO || 7JET28WW (1.13 ) || 03/31/2008
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT13WW-1.04 ]-</nowiki>
|| A mean bitch to set up, nothing really worked out of the box :(
|-
| {{X60t}} 6363A7G
|| LENOVO || 6363A7G || ThinkPad X60 Tablet || LENOVO || 6363A7G || Not Available || LENOVO || Not Available || LENOVO || 7JET19WW (1.04 ) || 12/14/2006
|| <nowiki>Handle 0x0023, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7JHT12WW-1.03 ]-</nowiki>
||
|-
| {{X61}} 7675-4KU
|| LENOVO || 76754KU || ThinkPad X61 || LENOVO || 76754KU || Not Available || LENOVO || Not Available || LENOVO || 7NET30WW (1.11 ) || 11/15/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT24WW-1.02 ]-</nowiki>
||
|-
| {{X61}} 7675-7KU
|| LENOVO || 76757KU || ThinkPad X61 || LENOVO || 76757KU || Not Available || LENOVO || Not Available || LENOVO || 7NETB1WW (2.11 ) || 03/24/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 bytes IBM ThinkPad Embedded Controller -[7MHT25WW-1.03 ]-</nowiki>
||
|-
| {{X61s}} 7668-CTO
|| LENOVO || 7668CTO || ThinkPad X61s || LENOVO || 7668CTO || Not Available || LENOVO || Not Available || LENOVO || 7NET25WW (1.06 ) || 07/02/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT24WW-1.02 ]-</nowiki>
||
|-
| {{X61s}} 7669-29G
|| LENOVO || 766929G || ThinkPad X61s || LENOVO || 766929G || Not Available || LENOVO || Not Available || LENOVO || 7NET21WW (1.02 ) || 04/23/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT23WW-1.01 ]-</nowiki>
||
|-
| {{X61s}} 7669-29G
|| LENOVO || 766929G || ThinkPad X61s || LENOVO || 766929G || Not Available || LENOVO || Not Available || LENOVO || 7NETB9WW (2.19 ) || 11/27/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT25WW-1.03 ]-</nowiki>
||
|-
| {{X61s}} 7667-34G
|| LENOVO || 766734G || ThinkPad X61s || LENOVO || 766734G || Not Available || LENOVO || Not Available || LENOVO || 7NETB9WW (2.19 ) || 11/27/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7MHT25WW-1.03 ]-</nowiki>
||
|-
| {{X61t}} 7762-95G
|| LENOVO || 776295G || ThinkPad X61 Tablet || LENOVO || 776295G || Not Available || LENOVO || Not Available || LENOVO || 7SET22WW (1.08 ) || 11/15/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X61t}} 7762-95G
|| LENOVO || 776295G || ThinkPad X61 Tablet || LENOVO || 776295G || Not Available || LENOVO || Not Available || LENOVO || 7SET36WW (1.22 ) || 11/27/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X61t}} 7762-98U
|| LENOVO || 776298U || ThinkPad X61 Tablet || LENOVO || 776298U || Not Available || LENOVO || Not Available || LENOVO || 7SET34WW (1.20 ) || 07/29/2008
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X61t}} 7764-CTO
|| LENOVO || 7764CTO || ThinkPad X61 Tablet || LENOVO || 7764CTO || Not Available || LENOVO || Not Available || LENOVO || 7SET18WW (1.04 ) || 07/03/2007
|| <nowiki>Handle 0x001F, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7RHT16WW-1.02 ]-</nowiki>
||
|-
| {{X100e}} 2876-27G
|| LENOVO || 287627G || ThinkPad X100e || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6XET21WW (1.04 ) || 12/18/2009
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT20WW-1.165000]-</nowiki>
||
|-
| {{X100e}} 3508-4UG
|| LENOVO || 35084UG || ThinkPad X100e || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6XET36WW (1.20a) || 03/12/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT36WW-1.176000]-</nowiki>
||
|-
| {{X100e}} 2876-W1U
|| LENOVO || 2876W1U || ThinkPad X100e || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6XET36WW (1.20a) || 03/12/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT36WW-1.176000]-</nowiki>
||
|-
| {{X100e}} 2876-55G
|| LENOVO || 287655G || ThinkPad X100e || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6XET33WW (1.12 ) || 02/11/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT31WW-1.171000]-</nowiki>
||
|-
| {{X100e}} 2876-55G
|| LENOVO || 287655G || ThinkPad X100e || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6XET36WW (1.20a) || 03/12/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT36WW-1.176000]-</nowiki>
||
|-
| {{X100e}} L625 (Dual-Core) 3508-5EG
|| LENOVO || 35085EG || ThinkPad X100e || LENOVO || 35085EG || Not Available || LENOVO || Not Available || LENOVO || 6XET38WW (1.22 ) || 04/09/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT38WW-1.178000]-</nowiki>
||
|-
| {{X100e}} L625 (Dual-Core) 3508-5EG
|| LENOVO || 35085EG || ThinkPad X100e || LENOVO || 35085EG || Not Available || LENOVO || Not Available || LENOVO || 6XET39WW (1.23 ) || 04/30/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT39WW-1.179000]-</nowiki>
||
|-
| {{X100e}} L625 (Dual-Core) 3508-5EG
|| LENOVO || 35085EG || ThinkPad X100e || LENOVO || 35085EG || Not Available || LENOVO || Not Available || LENOVO || 6XET41WW (1.25 ) || 06/02/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6XHT40WW-1.180000]-</nowiki>
||
|-
| {{X200}} 7454-CTO
|| LENOVO || 7454CTO || ThinkPad X200 || LENOVO || 7454CTO || Not Available || LENOVO || Not Available || LENOVO || 6DET38WW (2.02 ) || 12/19/2008
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT21WW-1.03 ]-</nowiki>
||
|-
| {{X200}} 7454-CTO
|| LENOVO || 7454CTO || ThinkPad X200 || LENOVO || 7454CTO || Not Available || LENOVO || Not Available || LENOVO || 6DET40WW (2.04 ) || 02/13/2009
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT22WW-1.04 ]-</nowiki>
||
|-
| {{X200}} 7458-E46
|| LENOVO || 7458E46 || ThinkPad X200 || LENOVO || 7458E46 || Not Available || LENOVO || Not Available || LENOVO || 7XET57WW (3.07 ) || 08/13/2009
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT22WW-1.04 ]-</nowiki>
||
|-
| {{X200s}} 7466-3SG
|| LENOVO || 74663SG || ThinkPad X200s || LENOVO || 74663SG || Not Available || LENOVO || Not Available || LENOVO || 6DET64WW (3.14 ) || 06/23/2010
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT24WW-1.06 ]-</nowiki>
|-
| {{X200s}}
|| LENOVO || 74695HG || ThinkPad X200s || LENOVO || 74695HG || Not Available || LENOVO || Not Available || LENOVO || 6DET33WW (1.10 ) || 10/27/2008
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT21WW-1.03 ]-</nowiki>
||
|-
| {{X200s}}
|| LENOVO || 7469WDR || ThinkPad X200s || LENOVO || 7469WDR || Not Available || LENOVO || Not Available || LENOVO || 6DET44WW (2.08 ) || 04/22/2009
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7XHT22WW-1.04 ]-</nowiki>
||
|-
| {{X200 Tablet}} 7449-F9U
|| LENOVO || 7449F9U || ThinkPad X200 Tablet || LENOVO || 7449F9U || Not Available || LENOVO || Not Available || LENOVO || 7WET24WW (1.02 ) || 09/09/2008
|| <nowiki>Handle 0x001D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7WHT14WW-1.01 ]-</nowiki>
||
|-
| {{X201 Tablet}} 3093-3YG
|| LENOVO || 30933YG || ThinkPad X201 Tablet || LENOVO || 30933YG || Not Available || LENOVO || Not Available || LENOVO || 6QET45WW (1.15 ) || 04/26/2010
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6SHT28WW-1.09 ]-</nowiki>
||
|-
| {{X201i}} 3249-CTO
|| LENOVO || 3249CTO || ThinkPad X201 || LENOVO || 3249CTO || Not Available || LENOVO || Not Available || LENOVO || 6QET45WW (1.15 ) || 04/26/2010
|| <nowiki>Handle 0x0027, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6QHT28WW-1.09 ]-</nowiki>
||
|-
| {{X300}} 6478-14G
|| LENOVO || 647814G || ThinkPad X300 || LENOVO || 647814G || Not Available || LENOVO || Not Available || LENOVO || 7TET23WW (1.00d) || 01/17/2008
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT15WW-1.00c ]-</nowiki>
||
|-
| {{X300}} 6478-18M
|| LENOVO || 647818M || ThinkPad X300 || LENOVO || 647818M || Not Available || LENOVO || Not Available || LENOVO || 7TET26WW (1.02a) || 02/27/2008
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT15WW-1.00c ]-</nowiki>
||
|-
| {{X300}} 6477-17G
|| LENOVO || 647717G || ThinkPad X300 || LENOVO || 647717G || Not Available || LENOVO || Not Available || LENOVO || 7TET33WW (1.07 ) ||
07/02/2008
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT15WW-1.00c ]-</nowiki>
||
|-
| {{X300}} 6477-17G
|| LENOVO || 647717G || ThinkPad X300 || LENOVO || 647717G || Not Available || LENOVO || Not Available || LENOVO || 7TET35WW (1.09 ) || 01/20/2009
|| <nowiki>Handle 0x0022, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7THT16WW-1.01 ]-</nowiki>
||
|-
| {{X301}} 2777-CTO
|| LENOVO || 2777CTO || ThinkPad X301 || LENOVO || 2777CTO || Not Available || LENOVO || Not Available || LENOVO || 6EET19WW (1.00g) || 07/30/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6EHT07WW-1.00b ]-</nowiki>
||
|-
| {{X301}} 2777-CTO
|| LENOVO || 2777CTO || ThinkPad X301 || LENOVO || 2777CTO || Not Available || LENOVO || Not Available || LENOVO || 6EET21WW (1.02 ) || 10/09/2008
|| <nowiki>Handle 0x0028, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6EHT09WW-1.02 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====Z series====
|-
| {{Z60t}} 2511-FEU
|| IBM || 2511FEU || ThinkPad Z60t || IBM || 2511FEU || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki> String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki>
||
|-
| {{Z60t}} 2511-FFG
|| IBM || 2511FFG || ThinkPad Z60t || IBM || 2511FFG || Not Available || IBM || Not Available || IBM || 77ET64WW (1.24 ) || 02/27/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT57WW-1.17 ]-</nowiki>
||
|-
| {{Z60m}} 2529-ETG
|| IBM || 2529ETG || ThinkPad Z60m || IBM || 2529ETG || Not Available || IBM || Not Available || IBM || 77ET59WW (1.19 ) || 04/24/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[77HT54WW-1.14 ]-</nowiki>
||
|-
| {{Z60m}} 2529-ETG
|| IBM || 2529ETG || ThinkPad Z60m || IBM || 2529ETG || Not Available || IBM || Not Available || IBM || 77ET64WW (1.24 ) || 02/27/2007
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT58WW-1.18 ]-</nowiki>
||
|-
| {{Z60m}} 2529-FBG
|| IBM || 2529FBG || ThinkPad Z60m || IBM || 2529FBG || Not Available || IBM || Not Available || IBM || 77ET62WW (1.22 ) || 11/21/2006
|| <nowiki>Handle 0x0029, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[77HT58WW-1.18 ]-</nowiki>
||
|-
| {{Z60m}} 2529-FKG
|| IBM || 2529FKG || ThinkPad Z60m || IBM || 2529FKG || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-</nowiki>
||
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET48WW (1.08 ) || 05/26/2006
|| <nowiki>String 1: IBM ThinkPad Embedded Controller -[7FHT21WW-1.03 ]-</nowiki>
||
|-
| {{Z61m}} 9452-8QG
|| LENOVO || 94528QG || ThinkPad Z61m || LENOVO || 94528QG || Not Available || LENOVO || Not Available || LENOVO || 7FETA4WW (2.22 ) || 10/19/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9450-H9G
|| LENOVO || 9450H9G || ThinkPad Z61m || LENOVO || 9450H9G || Not Available || LENOVO || Not Available || LENOVO || 7FETA7WW (2.25 ) || 06/03/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9452-W5Q
|| LENOVO || 9452W5Q || ThinkPad Z61m || LENOVO || 9452W5Q || Not Available || LENOVO || Not Available || LENOVO || 7FETA6WW (2.24 ) || 03/13/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9543-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61m}} 9543-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET93WW (2.11 ) || 11/10/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61m}} 9453-A11
|| LENOVO || 9453A11 || ThinkPad Z61m || LENOVO || 9453A11 || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61p}} 9453-A12
|| LENOVO || 9453A12 || ThinkPad Z61p || LENOVO || 9453A12 || Not Available || LENOVO || Not Available || LENOVO || 7FET45WW (1.05 ) || 04/20/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[7FHT19WW-1.01 ]-</nowiki>
||
|-
| {{Z61p}} 9450-3AU
|| LENOVO || 94503AU || ThinkPad Z61p || LENOVO || 94503AU || Not Available || LENOVO || Not Available || LENOVO || 7FET53WW (1.13 ) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT23WW-1.05 ]-</nowiki>
||
|-
| {{Z61t}} 9440-2CU
|| LENOVO || 94402CU || ThinkPad Z61t || LENOVO || 94402CU || Not Available || LENOVO || Not Available || LENOVO || 7FET50WW (1.10 ) || 06/20/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT22WW-1.04 ]-</nowiki>
||
|-
| {{Z61t}} 9443-4GG
|| LENOVO || 94434GG || ThinkPad Z61t || LENOVO || 94434GG || Not Available || LENOVO || Not Available || LENOVO || 7FET96WW (2.14 ) || 12/25/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FET91WW (2.09 ) || 11/01/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FET99WW (2.17 ) || 04/17/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FETA0WW (2.18 ) || 05/17/2007
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FETA7WW (2.25 ) || 06/03/2008
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
| {{Z61t}} 9440-CTO
|| LENOVO || 9440CTO || ThinkPad Z61t || LENOVO || 9440CTO || Not Available || LENOVO || Not Available || LENOVO || 7FETA9WW (2.27 ) || 08/26/2009
|| <nowiki>Handle 0x0026, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[7FHT26WW-1.08 ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====Lenovo 3000 series====
|-
| [[:Category:Lenovo 3000| Lenovo 3000]] N200 TY2BAFR
|| LENOVO || 0769BAG || 3000 N200 || LENOVO || IEL10 || Reference || No Enclosure || N/A || LENOVO || 68ET24WW || 08/15/2007
|| <pre> </pre> 
|| {{T-WARN|Non-ThinkPad EC firmware and BIOS}}
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====Edge series====
|-
| ThinkPad Edge 13 AMD L325
|| LENOVO || 01976GG || ThinkPad Edge 13"IAL# || LENOVO || INVALID || Not Available || LENOVO || Not Available || LENOVO || 6ZET25WW (1.12 ) || 01/15/2010
|| <nowiki>Handle 0x000D, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6ZHT19WW-1.164000]-</nowiki>
||
|-
| ThinkPad Edge 13,3" NUD2EGE
|| LENOVO || 01962EG || ThinkPad Edge 13"IAL# || LENOVO || 01962EG || Not Available || LENOVO || Not Available || LENOVO || 6YET25WW (1.10 ) || 01/15/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6YHT19WW-1.164000]-</nowiki>
||
|-
|| ThinkPad Edge 13,3" NUD2EGE
|| LENOVO || 01962EG || ThinkPad Edge || LENOVO || 01962EG || Not Available || LENOVO || Not Available || LENOVO || 6YET29WW (1.12 ) || 03/05/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6YHT21WW-1.166000]-</nowiki>
||
|-
|| ThinkPad Edge 13,3" Intel
|| LENOVO || 0196CTO || ThinkPad Edge || LENOVO || 0196CTO || Not Available || LENOVO || Not Available || LENOVO || 6YET30WW (1.13 ) || 04/29/2010
|| <nowiki>Handle 0x0018, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[6YHT23WW-1.168000]-</nowiki>
||
|-
|| ThinkPad Edge 14" NVP3YRT
|| LENOVO || 05783YG || ThinkPad Edge || LENOVO || 05783YG || Not Available || LENOVO || Not Available || LENOVO || 80ET29WW (1.06 ) || 03/24/2010
|| <nowiki>Handle 0x0019, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[80HT22WW-1.166000]-</nowiki>
||
|-
|| ThinkPad Edge 15" NVL7VGE
|| LENOVO || 03017VG || ThinkPad Edge || LENOVO || 03017VG || Not Available || LENOVO || Not Available || LENOVO || 80ET36WW (1.13 ) || 06/04/2010
|| <nowiki>Handle 0x0019, DMI type 11, 5 byte String 1: IBM ThinkPad Embedded Controller -[80HT29WW-1.173000]-</nowiki>
||
|-
|}
</div>

==Adding entries==

Click the "Edit" link on the appropriate series above and add an entry of the following form:
:<tt>| </tt>description of your model
:data line 1
:data line 2
:<tt>||</tt>
:<tt>|-</tt>

where the two data lines are generated by the following <tt>bash</tt> command:

<pre>
for X in system-{manufacturer,product-name,version} \
baseboard-{manufacturer,product-name,version} \
chassis-{manufacturer,version} bios-{vendor,version,release-date}; do \
echo -n "|| `sudo /usr/sbin/dmidecode -s $X` " \
| perl -pe 's/\n/\\n/' ; done; \
sudo /usr/sbin/dmidecode | perl -0777 -ne \
'm/\n(.*).\n.*\n(.*Embedded Cont.*)\n/i; print "\n|| <nowiki><</nowiki>nowiki>$1$2</nowiki>\n"'
</pre>

If you can, please also test [[tp_smapi]] and update its [[tp_smapi#Model-specific_status|model-specific status table]].

==Software using ThinkPad DMI IDs==
* [[HDAPS]] driver whitelist
* [[tp_smapi]] driver whitelist
* [[thinkpad-acpi]] driver quirk list

BIOS Upgrade

2010-07-13T11:36:02Z

Dag-: Added another successful X201s update

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
This page is meant to describe ways to update the BIOS on a ThinkPad that only runs Linux for users that don't have ready access to Windows. If you have Windows on your ThinkPad you can just boot into it and follow instructions on the Lenovo website.

Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by Lenovo. However there are work arounds.

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems.

'''Proceed at your own risk!'''}}
|}

= Downloading New Firmware =
{{WARN|Flashing the wrong firmware for your hardware may cause permanent damage to your ThinkPad. It is up to you to confirm that the firmware you are using is correct.}}

A list of links to firmware downloads can be found at [[BIOS Upgrade Downloads]] for most Thinkpad models. You can also check the Lenovo Support website's [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=TPAD-MATRIX|ThinkPad driver matrix].

Lenovo provides firmware upgrades in a variety of packages:
* Diskette
* Non-diskette
* Linux diskette
* BIOS Utility
* Bootable CD

Not every type of package is available for every model.

The ''BIOS Utility'' and ''Bootable CD'' packages combine the BIOS and ECP firmwares. For the other packages, there is one for each firmware.
{| align="right" style="width:20em;"
| {{HELP|Can an image be extracted from a "Linux diskette" .exe file?}}
|}

The ''Linux diskette'' is just the ''Diskette'' package that runs on Linux instead of Windows/DOS. It's unknown if a boot image can be extracted from it.

You may need to try different packages to find the one from which you can extract a boot image.

== Two Firmwares: BIOS and ECP ==
{{WARN|Flashing incompatible firmwares, or flashing them in the wrong order, may cause permanent damage to your ThinkPad.}}

It is important to understand that Thinkpads from IBM have two separate firmwares: the BIOS, and the Embedded Controller Program (ECP).

A given BIOS version will require a certain version of the ECP. You must read the Lenovo website and/or .txt files to confirm which BIOS is compatible with which ECP, and '''the order in which to update them'''.

=== Update Order ===

The IBM documentation is sometimes unclear about the order in which these two firmwares should be updated. When in doubt (i.e. IBM didn't provide specific instructions for your model or a particular firmware update), '''update the ECP first, and then the BIOS'''. Also, make sure to do the two updates '''immediately one after the other'''.

The EC firmware is usually much better at backwards compatibility than the BIOS.

(Updaters for newer models take care of both BIOS and EC, and use automatically whatever sequence is needed, so you don't have to worry about it.)

== Installed Firmware ==
You can check the current BIOS and ECP versions on your ThinkPad by using '''dmidecode'''. For example:

{{cmdroot|dmidecode -s bios-version}}

1RETDRWW (3.23 )

{{cmdroot|dmidecode -t 11}}

# dmidecode 2.9
SMBIOS 2.33 present.
Handle 0x0029, DMI type 11, 5 bytes
OEM Strings
String 1: IBM ThinkPad Embedded Controller -[1RHT71WW-3.04 ]-

Showing BIOS version 3.23 (1RETDRWW) and ECP version 3.04 (1RHT71WW).

===DMI IDs===
Please consider updating the [[List of DMI IDs]] before (and after) updating your BIOS.

= Updating Firmware =

There are two basic steps to updating the firmware (either the BIOS or the ECP) on a ThinkPad not running Windows:
# Extract a bootable update image
# Boot from that image

== Extracting an update image ==
{{WARN|Though this process has been successfully tested on many versions of .exe files found on IBMs website, that doesn't mean it will work for all of them. '''Proceed at your own risk'''. Consult the testing tables farther down of this page to see other users' experience with your model Thinkpad.}}
The various .exe installers from Lenovo all appear to be just a wrapper license program around Windows .cab files (see [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program [http://freshmeat.net/projects/cabextract/ '''cabextract'''] you can expand these .cab files directly. For example, if you downloaded {{path|1iuj13us.exe}} from Lenovo:

:{{cmduser|cabextract 1iuj13us.exe}}

Extracting cabinet: 1iuj13us.exe
extracting 1IUJ13US.IMG
extracting BIOSUPTP.EXE
extracting DOBOOT.EXE
extracting DOSBOOT.COM
extracting DOSBOOT.SYS
extracting DOSBOOT.VXD
extracting DOSBOOT2.COM
extracting ECTLUPTP.EXE
extracting EFLASHAS.SYS
extracting HDFWUPTP.EXE
extracting IBMTPI.XML
All done, no errors.

The file we want is '''FILENAME.IMG''', with "FILENAME" being the .exe. you downloaded. E.g., {{path|1IUJ13US.IMG}}.

(If this does not work for the Non-diskette .exe, try it on the Diskette .exe. It's reported, for example, that the Non-diskette .exe for BIOS version 3.23 for the T41p was not extractable, but the Diskette .exe worked perfectly, with {{cmduser|cabextract}} delivering a .IMG file.)

==== Testing the Image ====

You can test that FILENAME.IMG is really a floppy image by running:

{{cmdroot|mkdir /tmp/mntfloppy}}

{{cmdroot|mount -o loop FILENAME.IMG /tmp/mntfloppy}}

If a '''ls''' command on the image returns what looks like a DOS floppy, and no read errors were displayed, you have a pretty good chance that the image is usable. For example:

{{cmdroot|ls /tmp/mntfloppy}}
$0195000.FL1 069580.PAT 06d2.HSH IBMDOS.COM TPCHKS.EXE
0691.HSH 06D0.PAT 06d6.HSH LOGO.BAT UPDTFLSH.EXE
0691.PAT 06D1.PAT 06d8.HSH LOGO.SCR UPDTMN.EXE
0694.HSH 06D2.PAT CHKBMP.EXE PHLASH16.EXE USERINT.EXE
0694.PAT 06D6.PAT COMMAND.COM PREPARE.EXE UTILINFO.EXE
0695.HSH 06D8.PAT CONFIG.SYS PROD.dat lcreflsh.bat
0695.PAT 06d0.HSH FLASH2.EXE QKFLASH.EXE
069580.HSH 06d1.HSH IBMBIO.COM README.TXT

Unmount the image after you are done testing:

{{cmdroot|umount /tmp/mntfloppy}}

== Booting from update image ==
Now that you have a bootable image for the correct update for you hardware, you need to do is boot from that image to install the update.

There are different ways to do that:
* [[#Booting from a CD|Boot from a CD]]
* [[#Booting_using_GRUB|Boot from the image, using GRUB]]
* [[#Booting_from_a_floppy|Boot from a floppy]]
* [[#Booting_from_a_USB_Flash_drive|Boot from a USB Flash drive]]

=== Booting from a CD ===
{| align="right" style="width:40em;"
|{{HINT|If there is a ''Bootable CD'' image available, e.g., FILENAME.iso, just download that, instead of mucking around with image files.}}
|}
If you are going to update the firmware by booting from a CD, you need to turn FILENAME.IMG that you extracted above into an .iso file.

The [http://en.wikipedia.org/wiki/El_Torito_%28CD-ROM_standard%29 El Torito Bootable CD Specification] is a wonderful thing. Thanks to it, a bootable CD can be made with a bootable floppy image in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.

It is very easy to create such a bootable CD ISO image in Linux using the '''mkisofs''' tool{{footnote|1}}. Run a command as follows:

{{cmdroot|genisoimage -b 1WUJ25US.IMG -c boot.catalog -o bootcd.iso 1WUJ25US.IMG}} #or older mkisofs

Where *.IMG is the name of the image file extracted above. This creates a CD with one file on it and marks that file as the boot image.

You can now burn the {{path|bootcd.iso}} to a CD in your favorite CD-burning program.
{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Boot from the CD to update your firmware. Remember to have [[BIOS_Upgrade#Two_Firmwares:_BIOS_and_ECP|both BIOS and ECP firmware boot-CDs]] ready, as needed, and use them in the [[#Proper_Order|proper order]].

== Updating without battery or with dead battery ==

This is a last-resort approach. Use this only if everything else fails.

The BIOS updater may refuse to update a BIOS without a battery, or if the battery charge is too low. In that case, extract the disk image with cabextract as per instructions above and dd it to an usb stick. (This will destroy the data on it, of course.) Acquire a pure DOS boot cd such as Windows 98 recovery CD and boot that.

Use F8 to abort the boot sequence of a windows 98 boot CD. If you need CD-ROM support, load CD-related things but say no to everything else. In particular, avoid loading himem.sys and doskey, as the presence of either program causes Phoenix bios flash tool phlash16.exe to abort.

Change to the volume where flash2.exe and other tools are installed, and execute "flash2.exe /u". This should bypass the battery check and perform the flashing. If that doesn't work, check if the update disk contains a tool called "phlash16.exe". This can be used directly to flash the image, and the invocation is typically "phlash16 /exit $01c80000.fl1".

== Successful tests ==

{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
| {{600E}} 2645-4AU ||
* George Tellalov <gtellalov_dontspamme@bigfoot.com>. BIOS 1.16 from spsdin36.exe worked perfectly with the method bootable cd from floppy image. I highly recommend this upgrade because it made my ibm-acpi module load (it wouldn't load before) and fixed some suspend to ram problems. Here's the [http://george.tellalov.info/bios_upgrade_600e_spsdin36.iso cd image] I used. Use at your own risk. You can send me a chocolate if it works for you ;)
|-
| {{600E}} 2645-5bU ||
* Mike Vincent<matchstc-putobvioushere.com>. Bios 1.16 from spsdin36.exe and then to the boot cd worked great for me. Thought I had bricked it three separate times using a "real" floppy! Each from different diskettes .The updater would start, give me the "going to take30 seconds" speech...and then access the HD for 10 minutes. Each time it would reboot fine. Did the cd as described above...worked great first time. Perhaps 10 year old seldom used floppy disc drives have some challenges?
|-
| {{600X}} 2645 ||
* Jonathan Byrne <jonathan@RemoveThisToMailMe.yamame.org>. BIOS 1.11 from spsuit55.exe worked perfectly using cabextract/CD method.
|-
| {{600X}} 2645 ||
* Andy Barnes <andy@RemoveThisToMailMe.itchypaws.co.uk>. As per Jonathan above, extracted BIOS 1.11 from spsuit55.exe using cabextract, created a CD boot image and burnt to CD. Worked flawlessly - thanks to everyone who contributed to this article!
|-
| {{A20p}} 2629-6VU ||
* Chris Pickett http://www.sable.mcgill.ca/~cpicke/. BIOS 1.11 flashed fine with cabextract/CD method.
|-
| {{A21e}} 2628-JXU ||
* Amit Gurdasani <gurdasani at yahoo dot com>. BIOS 1.13 flashed fine with cabextract/CD method. Alarmingly, after the BIOS update, the laptop beeped but did not shut down as was indicated onscreen -- that was frozen on the "do not shut down the laptop" screen. On power down and up again, the BIOS setup showed the newer BIOS image running, and Linux booted up fine. Linux ACPI didn't complain about the BIOS being too old either.
|-
| {{A31p}} 2653 ||
* Matthias Meinke largeeddy@gmx.at, BIOS 1.09 1NET15WW flashed fine with cabextract/CD method.
|-
| {{A31}} 2652 ||
* [[User:Wnoise|Aaron Denney]], BIOS 1.13 flashed fine with cabextract/CD method. The cabextract/CD method also worked for BIOS 1.10.
|-
| {{R30}} ||
* Jarrod, 30 August 2007, Thinkpad R30 Type 2656-E0M. BIOS updated to 1.40 (1CETF0WW) using floppy disk/mkisofs/cdrecord. Worked fine, no problems.
|-
| {{R31}} ||
* [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]
* Sebastian Sauer (with cabextract/CD method)
|-
| {{R40}} ||
* Matthew Lambie, http://lambie.org
* Antti S. Lankila, update to 1.27 via direct use of phlash16.exe against a BIOS image. Normal method did not work because the battery is dead.
|-
| {{R50}} 1836-3SU ||
* jlbartos <jlbartos at hotmail dot com>
|-
| {{R50e}} 1834-PTG ||
* item <item at freemail dot hu> : successfully finished with cabextract/CD method for "1wuj25us.exe" (BIOS version 1WET90WW (2.10), Release Date: 2006/12/22)
* Christos Nouskas <nouskas at gmail dot com>: upgraded to BIOS version 1WET90WW (2.10) and EC version 1VHT28WW (1.04) using GRUB (BIOS first / EC second)
|-
| {{R51}} 1829 ||
* Robert Uhl <rob dot uhl at gmx dot de>, Jellby <jellby at yahoo dot com>
|-
| {{R51}} 1830-RM7 ||
* Will Parker <stardotstar at sourcepoint dot com dot au> successfully flashed 3.20 using existing 3.04 ECP and retained custom boot splash.
|-
| {{R51}} 2887 ||
* Ingo van Lil <inguin at gmx dot de>
|-
| {{R52}} 1858 ||
* Stuart McCord <stuart dot mccord at gmail dot com> flashed both BIOS and ECP using cabextract, BIOS flashed first as on IBM website
|-
| {{T20}} ||
* Franz Hassels <fhassel at suse dot com>
|-
| {{T22}} ||
* Daniel Maier <nusse teamidiot de>
* Mathias Behrle (with cabextract/CD method, Version 1.07 => 1.12) --[[User:Mathiasb|Mathiasb]] 11:58, 14 December 2006 (CET)
* Bob Skaroff (cabextract/CD), 1.06 => 1.12
* Leo Butler (cabextract/CD), 1.11 => 1.12
|-
| {{T23}} ||
* Bart Snapp <snapp at uiuc dot edu> Note: I followed IBM's instructions to flash the BIOS '''first''' and the Embedded Controller '''second'''.
* Moy Easwaran: BIOS 1.18 / EC 1.06a via cabextract and CD-boot. The BIOS-update exe generated errors in Windows 2000.
* Joe Renes: BIOS 1.18 / EC 1.06a on 2006-03-20 via cabextract and CD-boot. Piece of cake.
* Raphael Errani: BIOS 1.20 / EC 1.06a on 2006-11-06 via cabextract and CD-boot (using mkisofs). Worked without errors. 1st Bios, 2nd EC
* Myron Getman: BIOS 1.20 / EC 1.06a on 9/10/08 via cabextract --> k3b --> CD-boot. Worked like a charm. First BIOS update with Linux!
* Leo Butler: BIOS 1.13 / EC 1.04 to 1.20/1.06a via cabextract and syslinux/memdisk boot through grub. Worked like a charm and no wasted CD.
|-
| {{T30}} ||
* Martin GÃ¼hring <guehring at gmail.com> BIOS 2.10 via cabextract the Non-Diskette BIOS -> mkisofs '''in the directory the exe was extracted''' to generate the iso -> burn the iso -> boot the CD
|-
| {{T40}} ||
* Sean Dague, http://dague.net
* Justin Mason, http://jmason.org
* Ivanhoe (Bios 3.19)
* Alessandro Raulino (roger_2) EC 3.04 & BIOS 3.23 flashed with cabextract/CD method
* Nick Jenkins, using BIOS 3.23 with the '''Non-diskette updater + cabextract method''', then [[#Creating_a_Bootable_CD_from_a_Floppy_Image|created a bootable CD from the cabextracted .IMG file]], then boot that ISO, and it worked great!
* xyz: BIOS 3.23 & EC 3.04 flashed with cabextract/CD method. No problem.
|-
| {{T40p}} ||
* Lukas KrÃ¤henbÃ¼hl, ismo at pop dot agri dot ch
* Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method
|-
| {{T41}} ||
* Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu>
* Ernesto HernÃ¡ndez-Novich (Bios 3.19 / CP 3.04) < emhn at usb dot ve >
* [http://maebmij.org James Ballantine] (Bios 3.21 / CP 3.04) using nondisk/cabextract/CDRW
* Vladimir Pycha (to Bios 3.23 / EC 3.04, from Bios 3.20 / EC 3.04) using nondisk/cabextract/CDRW. Booted with external USB optical drive (I have internal drive broken) - at the beginning of the boot sequence press PAUSE, then wait several seconds, then ENTER, then F12 and select the drive. Without pressing PAUSE I am not able to boot from USB optical/hard drive as the drive does not show in the F12 boot list menu.
|-
| {{T41p}} ||
* Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)
|-
| {{T42}} 2373-JXG ||
* magarzo <mdr.magarzo at gmail.com> (BIOS v.3.23 / Embedded Controller v.3.04 / both with cabextract to non-diskette v. plus Bootable CD)
|-
| {{T42}} ||
* Dan (BIOS 3.20 / EC 3.04, cabextract/CD method) <tronic171 at evilphb.org>
* Hirosh Dabui <hirosh@dabui.de>
|-
| {{T42p}} ||
* Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de>, Hirosh Dabui <hirosh@dabui.de>
|-
| {{T43}} 1871-W34 ||
* Florian Boucault <florian at boucault dot ath dot cx> (Version: Bios 1.23 / Embedded Controller 1.03)
|-
| {{T43}} 1871-4AG ||
* [http://blog.martinmcdowell.com/about/contact Martin McDowell] 28-Feb-2010
* BIOS 70ET62WW (1.22) to 70ET69WW (1.29),
* ECP 70HT26WW (1.03) to 70HT28WW (1.05)
Both successfully upgraded from CD Image made from the instructions on this website.
|-
| {{T43}} 2886 ||
* Till Heikamp <t dot heikamp at geniusbytes dot com> (Bios 1.22 to 1.29, Embedded Controller 1.03 to 1.06)
|-
| {{T43}} ||
* Conrad Rentsch <Conrad dot Rentsch at t-online dot de> (Version: Bios 1.29 / Embedded Controller 1.06)
* Tom Heady <tom-thinkwiki.org@punch.net>
|-
| {{T60}} ||
* 1951 Roman Komkov <roman at komkov dot org dot ru> (Bios 1.07 to 2.13) Successfully upgraded from CD Image
* 8744-HCG Konstantin Khorenko <horenko at mail dot ru> (Bios 1.06 to 1.18) Successfully upgraded from CD Image
|-
| {{T61}} ||
* Kai Weber <kai.weber at glorybox dot org> (Bios 1.06 to 1.26) Successfully upgraded from CD Image
|-
| {{X20}} ||
* Neil Caunt <retardis at gmail dot com>
|-
| {{X21}} ||
* Patrick Leickner <ranma at web dot de>, (BIOS 2.21->2.25 / EC 1.31->1.36) via non-disk/cabextract/mkisofs/cdrecord
|-
| {{X22}} ||
* David Emery <dave at skiddlydee dot com>, (EC 1.30, BIOS 1.32 using non-disk/cabextract/CD method)
|-
| {{X23}} ||
* Nils Faerber <nils dot faerber at kernelconcepts dot de> (Embedded Controller 1.30, BIOS 1.32 with cabextract/CD method)
|-
| {{X30}} ||
* Hella Breitkopf, [http://www.unixwitch.de/ www] (Embedded Controller 1.04, BIOS 1.07 with cabextract/CD method)
* William Roe <willroe at gmail dot com> (Embedded Controller 1.06, BIOS 1.09 - cabextract/mkisofs/wodim)
|-
| {{X31}} ||
* Grzegorz KuÅ›nierz <koniu at sheket dot org> (Embedded Controller 1.08, BIOS 3.01 with cabextract/CD method)
|-
| {{X31}} ||
* Paul Litwack <paullitwack at gmail dot com> (Embedded Controller 1.08, BIOS 3.02 with cabextract/unetbootin method)
cabextract & unetbootin are staight foward(toggle floppy image instead of iso image in unetbootin dialog)
No problems with update software.
x31 has to be cajoled into booting from usb. Boot hangs when pendrive is present. Hit the key to bring up the boot menu.
Unplug the pendrive. Let the boot menu come up. Plug in the pendrive. Select the pendrive in the boot menu and it boots.
|-
| {{X40}} ||
* Robbie Stone <robbie@serendipity.cx>
* Andy Shevchenko <andy.shevchenko@gmail.com> (Fine by cabextract/CD method)
|-
| {{Z60m}} ||
* [[User:Morle|Morle]] 01:09, 17 Nov 2007 (CEST), (Embedded Controller 1.18 and Bios 1.24 with cabextract/CD method)
|}

==== Unsuccessful tests ====
{| border="1" cellspacing="0" cellpadding="2" style="font-size:80%; vertical-align:top;"
! Model
! Tested by, and comments
|-
|<pre> </pre> 
|
|}

=== Booting using GRUB ===
{|
| style="width:75%" | {{WARN|Many have warned '''not''' to use the SYSLINUX image-loader '''memdisk''' to boot firmware update images.}}
| style="font-size:80%" | {{HELP|Who are these "many"? Link to a discussion?}}
|}
Once the bootable image, FILENAME.IMG, is extracted from the .exe, it can be booted directly through GRUB without the need of burning a CD, using the [http://syslinux.zytor.com/ SYSLINUX] image-loader '''[http://syslinux.zytor.com/memdisk.php memdisk]'''.

Locate the '''memdisk''' file from the syslinux package. You can search for it with '''find''':

{{cmdroot|find /usr -name memdisk}} #or just use "dlocate memdisk" or "locate memdisk" if these programs are installed

If {{path|/usr/.../memdisk}} is not present, syslinux is not installed. You will need to install it to boot a .IMG from GRUB.

Copy both the '''FILENAME.IMG''' and '''memdisk''' files into {{path|/boot}} directory. For example:

{{cmdroot|cp ./FILENAME.IMG /usr/share/syslinux/memdisk /boot/}}

Open {{path|/boot/grub/menu.lst}} in your favourite editor. '''Copy''' the active section into a '''new section''', and edit the new section:
{| border="1" cellspacing="0" cellpadding="2"
! Parameter
! Instructions
! Example
|-
| ''title'' || Pick a name for the new section. This will show up in the GRUB boot menu. || <tt>title IBM ECP Update</tt>
|-
| ''root'' || Do not change. This is the partition containing the {{path|/boot}} directory || <tt>root (hd0,0)</tt>
|-
| ''kernel'' || '''/boot/memdisk''' will allow you to boot an image file. || <tt>kernel /boot/memdisk</tt>
|-
| ''initrd'' || This is the name of the firmware-updater image file, e.g., 1IUJ13US.IMG || <tt>initrd /boot/1IUJ13US.IMG</tt>
|}

Do '''not''' modify the original section in {{path|/boot/grub/menu.lst}}, or you might not be able to boot back to the operating system.

If you have [[#Two_Firmwares:_BIOS_and_ECP|two firmware updates to do]], you will need a section for each firmware's FILENAME.IMG in {{path|/boot/grub/menu.lst}}.

{{NOTE|If both BIOS and ECP are to be updated, be sure to update them in the [[#Proper_Order|proper order]].}}

{{WARN|By following any of the instructions here you are accepting the '''very real risk''' of turning your ThinkPad into a big expensive paper weight, as a firmware update gone wrong can create unfix-able problems. '''Proceed at your own risk!'''}}

Reboot your computer, entering the GRUB menu and selecting ''IBM BIOS Update'', or whatever you named the new section in {{path|/boot/grub/menu.lst}}.

==== GRUB2 ====
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :
menuentry "My BIOS Upgrade" {
set root=(hd0,0) #should match the others in your grub.cfg
linux /boot/memdisk
initrd /boot/1WUJ25US.IMG #or whatever yours is
}

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{R30}} 2656-64G || v.1.40 || || [[User:english.voodoo|Yuri Spirin]] ||
|-
| {{R40}} 2723 || 1OHJ11WW.IMG || 1PUJ25US.IMG || [[User:qunying|Qunying]] || memdisk from syslinux 3.70 (slackware 12.1)
|-
| {{R50e}} 1834NV1 || 1WUJ25US.IMG || || [[User:Jidanni|Jidanni]] || memdisk from syslinux-common 2:3.84+dfsg-1 (Debian), grub2 (1.96+20080724-16)
|-
| {{R51}} 2888 || || || ||
|-
| {{T40}} 2373 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:Euphoria|Euphoria]] || memdisk from syslinux 1:3.31-4 (Debian package version)
|-
| {{T40}} 2373 || 1RHJ10U2.IMG (3.04, 2004-11-15) || 1RUJ37US.IMG (3.23, 2007-07-03) || [[User:Morphics|Morphics]] || cabextract and memdisk from syslinux 3:1.36-4ubuntu5
|-
| {{T41}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Tonko|Tonko]] || Fedora 12
|-
| {{T41p}} 2373 || 1RUJ37US.IMG (3.23, 2007-07-03) || || [[User:Deggel|Deggel]] || cabextract and memdisk from syslinux 3.71 on gentoo
|-
| {{T41p}} 2373 || || || [[User:MrStaticVoid|James Lee]] ||
|-
| {{T42p}} 2374 || 1RUJ37US.IMG || 1RHJ10U2.IMG || [[User:aderigs|Achim Derigs]] || Debian GNU/Linux sid, works with `linux16 ...' and `initrd16 ...' only
|-
| {{X31}} 2673-CBU || || || [[User:JanTopinski|Jan Topinski]] ||
|-
| {{X31}} 2672-CXU || || || [[User:TheAnarcat|TheAnarcat]] ||
|-
| {{X31}} 2673-58G || || || [[User:FaUl|FaUl]] ||
|-
| {{X31}} 2672-PG9 || || || [[User:Starox|Starox]] || a big moment between starting update and the updating window
|-
| {{X31}} 2672-PG9 || v3.02 1QUJ19US.IMG || v1.08 1QHJ08US.IMG || [[User:TeeLittle|TeeLittle]] || Apr 10, 2010: Using Debian 5.0 "Lenny" + package syslinux-common (Version: 2:3.71+dfsg-5). Pre-update versions: BIOS v2.11 / ECP v1.03
|-
| {{X40}} 2371 || 2.07 1uuj21us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Jakob Truelsen]] || Worked on two X40-2371
|-
| {{X40}} 2386 || 2.08 1uuj22us.exe || 1.62 1uhj10us.exe || [[User:Antialize|Galen Seitz]] || memdisk from syslinux 3.61
|}
(More successful grub tests are scattered in the previous table too.)

==== Unsuccessful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! style="width:10em;" | BIOS
! ECP
! Tested by
! Notes
|-
| {{R32}} 2658-NWU || 2.16 1MUD23US.IMG || n/a || [[User:Millman12345|Mike Millman]] || Boots into the BIOS flashing program just fine, but when it comes time to start the update process, the system hangs completely. Luckily, it hangs before it actually modifies anything... A hard reboot got me back into a working system. I would not recommend this route!
|-
| {{T43}} 2668-F7G || 1.29 1YUJ18US.IMG || || [[User:Maus3273|Maus3273]] || I got into the bios program, but the machine never restarts after initiating the upgrade.
|-
| {{X41}} 2525-FAG || 2.09 74UJ15US || || [[User:Ukleinek|Uwe Kleine-König]] || booted fine (Debian syslinux 2:3.71+dfsg-5), but didn't succeed to write, just hang at "Don't restart or remove diskette etc. pp" (not bricked). Worked fine via CD method.
|-
| {{X41}} 2525-F8G || 2.06 74UJ12US.IMG 2.07 74UJ13US.IMG 2.09 74UJ15US.IMG || || [[User:ladoga|Lauri Koponen]] || hangs while initializing the actual BIOS flashing process ECP: 1.02 74HJ03US.IMG works
|-
|}

==== GRUB2 boot cd image ====
With grub2, one would ''append'' the following to ''/boot/grub/grub.cfg'' :
menuentry
menuentry "My BIOS Upgrade" {
set root=(hd0,0) #should match the others in your grub.cfg
linux16 /boot/memdisk iso raw
initrd16 /boot/1WUJ25US.iso #or whatever yours is
}

This work for official iso images from ibm website.

==== Successful tests ====
{|border="1" cellspacing="0" cellpadding="2" style="font-size: 80%"
|-
! Model
! BIOS
! ECP
! Tested by
! Notes
|-
| {{X100e}} 2876-55G || 6xuj05uc.iso || || [[User:nikel]] ||
|-
| {{Edge}} || 1.17 6yuj04uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 1.13 6duj40uc.iso || || [[User:theBro]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|-
| {{X200s}} || 3.14 6duj41uc.iso || 1.06 || [[User:dag-|Dag Wieers]] || Using memdisk from syslinux 4.01
|-
| {{X201}} 3626-A14 || 1.15 6quj05uc.iso || 1.09 6quj05uc.iso || [[User:Alexander List|Alexander List]] || memdisk from syslinux 3.86
|-
| {{Edge 13}} 0197-6GG || 1.18 6yuj05uc.iso || || [[User:fethio]] || Current memdisk from syslinux worked (5/2010), the one provided by Ubuntu 9.10 did not.
|}

=== Booting from a Floppy ===
{{WARN|Using a floppy disk '''is NOT recommended'''.}}

This is how IBM/Lenovo intended it. Use their .exe files to create a bootable floppy with the flash update on it. Boot from the floppy and there you go.

So, why is it not recommended?
# If something goes wrong, your ThinkPad may be permanently damaged
# Floppy disk drives are not reliable
# Floppy disks are not reliable
# It only works with /dev/fd0, meaning it won't work with a USB floppy

So, even though Lenovo is now offering "Linux diskette" updaters, that will create a bootable floppy under Linux, using a floppy is still not recommended. Besides, many people don't even ''have'' a floppy drive on their ThinkPad.

If you really want to do it with a floppy, some tips:
* Use a clean (in the physical sense) floppy drive
* Use new floppies
* Test floppies for errors before starting update process
* Have multiple copies of the update disks ready--if one should fail, replace it with a copy
* Should DOS complain of a read error, '''only''' respond wth "Retry"

{{NOTE|Should the system encounter a disk read error during the flash process, and you select "Abort", your system could be permanently damaged.}}

=== Booting from a USB Flash drive ===
{{HELP|Has anyone tested booting a firmware update image from a USB flash drive? Perhaps using [http://unetbootin.sourceforge.net/ UNetbootin]?}}
Unetbootin 422 worked with the image files unpacked with cabextract on my x31.
== Booting from a Network Boot Image ==
BIOS, ECP, CD/DVD and Harddisk firmware disks can be booted over the network with [http://syslinux.zytor.com/pxe.php PXELINX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package. This requires that you have a DHCP and tftp server configured and setup properly on your network, and is probably not for the faint of heart.

Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks from the IBM website cannot be booted directly as such.

This worked on the {{R31}}, {{X22}}, {{T21}}, {{T30}} and {{T41p}} with various firmware updates. On the {{X22}}, it worked with ECP 1.30 but '''not''' with BIOS 1.32

=After updating=
Lenovo recommends reseting your BIOS settings to their factory defaults after a firmware update.

==DMI IDs==
Please consider updating the [[List of DMI IDs]] after updating your BIOS.

= Special Cases =
* In one case, see ([[APM setup on a type 2379 ThinkPad T40]]), it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.

== Updating Thinkpad X Series ==
The special update instructions for {{X_Series}} Thinkpads are quite long. You can find them at the page [[BIOS_Upgrade/X_Series]].

----

{{footnotes|
# For lots of detail on making and burning .iso files, see The Linux Documentation Project (tldp.org): [http://tldp.org/HOWTO/CD-Writing-HOWTO-3.html#ss3.1 3.1 Writing CD-ROMs (pure data)].
}}

How to measure power consumption

2010-06-15T07:03:11Z

Dag-: Added Dstat command-line to track power usage

==Direct measurement during operation==
To monitor the laptop's power consumption while it is running, unplug the AC power and run:
:{{cmdroot|watch -n1 'cat /proc/acpi/battery/BAT0/*'}}

This requires ACPI to be enabled. The value given is (roughly) an averge over the last minute.

Alternatively, load the [[tp_smapi]] module and run the following with AC power unplugged:
:{{cmdroot|watch -n1 'cat /sys/devices/platform/smapi/BAT0/power_now'}}
or
:{{cmdroot|watch -n1 'cat /sys/devices/platform/smapi/BAT0/power_avg'}}

The former provides the instantaneous power draw, and the latter is (roughly) an average over the last minute. It's OK to use [[tp_smapi]]'s <tt>force_discharge</tt> function instead of physically disconnecting AC power.

Note that running on battery power may activate power-saving mechanisms, so unless you take care to deactivate them this does not reflect power consumption under AC power.

Dstat is another way to track your laptop's power consumption, run the following with AC power unplugged to relate power usage (in Watts) and battery information:

[dag@moria ~]$ dstat --time --power --battery --battery-remain 10
----system---- power batt remai
time |usage|bat0| bat0
15-06 08:53:55|0.000| 94| 4h29
15-06 08:54:05|15.74| 94| 4h30
15-06 08:54:15|15.56| 94| 4h30
15-06 08:54:25|15.52| 94| 4h30
15-06 08:54:35|15.60| 93| 4h29

==Measurement script==
See [[Script_for_monitoring_power_consumption]].

==Measurement for synthetic workloads==
Use the [http://bltk.sourceforge.net Battery Life Tool Kit] tool.

==Measurement during suspend==
To measure power consumption while the laptop is suspended, use the [[ACPI sleep power drain test script]].

==Hardware-measurement on line or ac-adapter==
The best (imho) method to measure power consumption is to measure the power drawn by the laptop from the ac-adapter or the power drawn by the ac-adapter itself by a wattmeter. If you want to measure drawn only by the laptop itself, you'll have to build a little adapter.

==See also==
For reducing power consumption, see [[How to reduce power consumption]].

How to reduce power consumption

2010-04-29T04:03:55Z

Dag-: Added options for newer dstat

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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==
===Enabling Power Management===
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.

===Disabling I/O Ports===
The BIOS (at least version 3.11 on {{X200}}) can also be used to disable I/O ports, like PCMCIA/CardBus. Although this requires a reboot to change settings, using the BIOS rather than a configuration file will survive distribution changes and may make it easier to remember how to re-enable a port. Disabling these devices can reduce power consumption by several watts.

==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 depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}, {{X31}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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 (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

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,relatime / # and so on for all mounted fs
</code>

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
See man mount(8).

Use laptop_mode to reduce disk usage by delaying and grouping 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>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
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>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /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 5 minutes 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. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuration.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add 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/*/power/autosuspend; do echo 1 > $i; done
for i in /sys/bus/usb/devices/*/power/level; do echo auto > $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>

==PCMCIA/CardBus==
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>

===Intel HD Audio===

If you have Intel HD audio as your onboard sound controller, substitute the following for the last line in the above sequence:

<code>
echo Y > /sys/module/snd_hda_intel/parameters/power_save_controller
</code>

You also may wish to decrease the sound poweroff timeout to something shorter, like 1 second after last playback:

<code>
echo 1 > /sys/module/snd_hda_intel/parameters/power_save
</code>

===Additional Tweaks===

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

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
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>dstat -t -c --power --top-cpu --top-io --top-bio --top-latency --top-cputime</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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2009-05-24T16:57:53Z

Dag-: Add also power usage module

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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 depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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 (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

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,relatime / # and so on for all mounted fs
</code>

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
See man mount(8).

Use laptop_mode to reduce disk usage by delaying and grouping 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>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
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>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /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. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add 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>

==PCMCIA/CardBus==
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).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
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>dstat -t -c -M topcpu,topio,topbio,power</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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2009-05-24T16:55:42Z

Dag-: Added topio so people are not confused

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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 depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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 (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

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,relatime / # and so on for all mounted fs
</code>

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
See man mount(8).

Use laptop_mode to reduce disk usage by delaying and grouping 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>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
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>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /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. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add 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>

==PCMCIA/CardBus==
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).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
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>dstat -t -cd -M topcpu,topio,topbio</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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2009-05-24T16:54:52Z

Dag-: Fixed 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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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 depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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 (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

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,relatime / # and so on for all mounted fs
</code>

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
See man mount(8).

Use laptop_mode to reduce disk usage by delaying and grouping 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>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
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>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /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. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add 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>

==PCMCIA/CardBus==
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).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
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>dstat -t -cd -M topcpu,topbio</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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

How to reduce power consumption

2009-05-24T16:54:13Z

Dag-: Added dstat as a way to monitor I/O

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.lesswatts.org/projects/powertop/known.php tips & tricks]
and an informative [http://www.lesswatts.org/projects/powertop/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 depreciated as of kernel 2.6.24, use CONFIG_X86_ACPI_CPUFREQ
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 ICH5 or later (cf. lspci output), as in most modern Thinkpads, 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>

{{WARN|The ICH4 does have an HPET, but it is disabled for a good reason: Intel didn't test/validade it! Use of the ICH4 HPET is '''not''' recommended}}

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

On modern ThinkPads the HPET timer is automatically detected and enabled. On certain older machines hpet=force is required such as on the following machines:
* {{T30}}, {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}
* {{X22}}, {{X23}}, {{X24}}, {{X30}}

{{HELP|please add your ThinkPad to the above list, if <nowiki>hpet=force</nowiki> was required}}

===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 (AN needs also support in hal to be used).
See: http://www.kernel.org/pub/linux/kernel/people/kristen/patches/SATA/alpm/

As of now (2.6.24-rc8), the linux kernel doesn't support PCI Express power
management (aka PCIe ASPM, aka PCIe LPM). Shaohua Li from Intel submited a
patch on LKML (http://lkml.org/lkml/2008/1/17/544 ) though, and reported it
to reduce power consumption by 1.3 watts for a system with three PCIe links.

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,relatime / # and so on for all mounted fs
</code>

(On older kernels you may need to use <tt>noatime</tt> instead of <tt>relatime</tt>.)

Also consider merely using a larger value for
commit=nrsec
Sync all data and metadata every nrsec seconds. The default value is 5 seconds.
See man mount(8).

Use laptop_mode to reduce disk usage by delaying and grouping 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>

====SATA Link Power Management====
On kernels 2.6.24 and new this enables SATA Link Power Management:
<code>
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>

Disable it by replacing <code>min_power</code> with <code>max_performance</code>.

On Hardy Heron with a 2.6.24-16 kernel, a suspend/resume cycle is much quicker if you disable SATA Link Power Management before initiating the suspend. As of Intrepid Ibex and kernel 2.6.27, this should be fixed. ([https://bugs.launchpad.net/linux/+bug/234047 Launchpad bug 234047], [http://bugzilla.kernel.org/show_bug.cgi?id=10817 Kernel bug 10817])

====Laptop Mode Tools====

The [http://samwel.tk/laptop_mode/ Laptop Mode Tools] utility implements many of the above power-saving measures from disks, and some others.

===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 --device /dev/scd0 # or whatever your CD drive is
</code>

start polling again when on ac:
<code>
hal-disable-polling --enable-polling --device /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. To enable it by default, you must add the line
<code>
options usbcore autosuspend=1
</code>
to your <tt>/etc/modprobe.conf</tt> or add it to (and create if necessary) the file <tt>/etc/modprobe.d/usbcore</tt> depending on how your distribution organises modprobe configuratoin.

If on the other hand, you have <tt>usbcore</tt> built into your kernel, you can add 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>

==PCMCIA/CardBus==
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).

See also [[How to enable audio codec power saving]].

==Wireless Interface==
===intel wireless===
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>dstat -t -cd -m topcpu,topbio</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:X61]] [[Category:X61s]] [[Category:Z60m]] [[Category:Z60t]] [[Category:Z61t]] [[Category:Z61e]] [[Category:TransNote]]

Talk:BIOS update without optical disk

2009-05-24T13:52:46Z

Dag-: /* Freeze when booting from USB drive */

== Freeze when booting from USB drive ==
I attempted a BIOS upgrade on a ThinkPad X200'''s''' using the steps described on this page. Since no Linux is installed on the ThinkPad (only Vista 64-bit), I used a USB drive I prepared on another computer. The drive was formatted as plain FAT and contains nothing but ''GRUB'', the ''memdisk'' executable and the image extracted with ''isobar''. The laptop boots fine from the USB drive, ''GRUB'' loads and runs ''memdisk'', which takes over and prints some debug information about memory addresses, disk layout and interrupts. Finally the following lines appear:

Loading boot sector... booting...
Lenovo Group Limited

Starting PC DOS...

Unfortunately, nothing happens after that. I attempted this with BIOS 3.01 (''6duj30uc.iso'') and BIOS 2.06 (''6duj08uc.iso'', the exact one used in the instructions). ''GRUB'' and ''syslinux'' are both up to date, obtained from the repositories of the recently released Ubuntu 9.04. I also tried the ''isobar32.exe'' from the ''OMIBAR32'' package on the ''SHSUCD'' website, again to no avail (however, the resulting images had a different checksum).
Any ideas?
--[[User:Nor|Nor]] 21:26, 15 May 2009 (UTC)

I also had no luck booting memdisk from a USB stick (may be because of the way memdisk works: it hijacks the HD-access interrupt in BIOS. But no-emulation boot of syslinux from a USB stick works OK). As for the different checksums for isobar32.exe and isobar-for-linux -- the images also have different sizes. I found and fixed a bug in the original isobar32.exe that might potentially corrupt the image (instead of "offset"+"size of the first partition" it dumps only "size of the first partition", so if there is a useful info in the last 32 sectors or so -- isobar32.exe will loose it). For now, I would suggest you

* boot from a linux "live-CD", e.g [http://sysresccd.org/ sysresccd] (of course, the whole point is that you dont have an optical drive, but you can easily make a bootable USB stick out of it. Since it uses no-emulation syslinux, it will boot OK).
* backup (with dd if=/dev/sda) the first 100Mb of your internal harddisk to an external disk (e.g. to the USB stick you are booting from)
* run "fdisk /dev/sda", delete all partitions, make a new primary partition /dev/sda1 of size 50Mb, format it in ext2 and mount to /media/sda1
* install grub, memdisk and bios.img you've extracted with isobar to /media/sda1
* reboot and update the BIOS
* reboot from the linux "live-CD" and restore your first 100Mb (with dd of=/dev/sda)

P.S. hypothetically, it could be done in a little simpler way (just dd=bios.img of=/dev/sda, bypassing installation of grub & memdisk), but in my testings it it gave "Missing operating system" error.

--[[User:newhren|newhren]] 14:22, 16 May 2009 (UTC)

I have found the same problem where memdisk fails to boot an image, whereas qemu has no problem to boot memdisk+image. Other people have reported the same problem with other systems (and this issue is known since at least 2004, but unresolved). I have had success reports from a T400 user, as well as the original author on a X200.

It was believed to be caused by a buggy BIOS, however the X200 and the X200s use the same BIOS. (And even the BIOS on a T400 is not completely different). We also ruled out the memdisk build, so it is related to either a BIOS setting or the hardware configuration of the system.

We need more people with success stories and fail stories to find the root-cause of this problem. It certainly is a bug in memdisk triggered by 'something', we just have to find what that 'something' is in order to fix it. (Or someone has to send such a device to the syslinux/memdisk developer so he can debug this issue :-))

More information from:

http://syslinux.zytor.com/archives/2009-May/012508.html

and (many) older reports:

http://syslinux.zytor.com/archives/2004-January/002999.html
http://syslinux.zytor.com/archives/2004-October/004099.html

--[[User:dag-|dag-]] 15:39, 24 May 2009 (CET)

Talk:BIOS update without optical disk

2009-05-24T13:52:13Z

Dag-: /* Freeze when booting from USB drive */

Talk:BIOS update without optical disk

2009-05-24T13:49:17Z

Dag-: /* Freeze when booting from USB drive */

Category:T20

2008-12-24T20:54:40Z

Dag-:

{| 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;">
=== ThinkPad T20 ===
This page gives an overview of all ThinkPad T20 related topics.
==== Standard Features ====
* [[Intel Mobile Pentium III]] 650, 700 or 750 MHz CPU
* [[S3 Savage IX8]] with 8MB
** 13.3" TFT display with 1024x768 resolution
** 14.1" TFT display with 1024x768 resolution
* 128MB [[PC-100]] memory standard (max 512MB)
* 6, 12 or 20GB HDD
* [[CS4624|CS4624B]]/[[CS4297|CS4297A]] Audio controller
* [[UltraBay|UltraBay 2000]] with one of the following:
** CD-ROM drive
** DVD-ROM drive
* [[MiniPCI slot]] with one of the following:
** [[Mini-PCI Modem card]]
** [[Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]
** [[3Com 10/100 Ethernet Mini-PCI Adapter with 56K Modem]]
* (2) Type II [[CardBus slot|CardBus slots]] or (1) type III
</div>
|style="vertical-align:top" |
[[image:ThinkPadT20.jpg|ThinkPad T20]]
|}

==Resources==
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/62p9631.pdf T20, T21, T22, T23 - Hardware Maintenance Manual (April 2002)] (2,902,595 Bytes)
* [http://tldp.org/linuxfocus/English/December2004/article359.shtml Hibernate an IBM Thinkpad T20 laptop (Linuxfocus.org article)] or [http://tldp.org/linuxfocus/English/Archives/lf-2004_12-0359.pdf pdf version] (ca. 590KB)
* CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/IBM/Thinkpad-T20

[[Category:T Series]]

Category:T42p

2008-12-24T20:53:10Z

Dag-:

{| width="100%"
|style="vertical-align:top" |
[[image:ThinkPadT40.jpg|ThinkPad T42p]]
|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;">
=== ThinkPad T42p ===
This pages gives an overview of all ThinkPad T42p related topics.

Machine Type: 2373, 2374, 2378. 2379
==== Standard Features ====
* [[Intel Pentium M (Dothan)]] 1.7 1.8, 2.0 or 2.1GHz CPU
* [[ATI Mobility FireGL T2]] with 128MB or
* [[ATI Mobility Radeon 9600]] with 64MB
** 14.1" TFT display with 1400x1050 resolution
** 15.0" TFT display with 1600x1200 resolution
* 512MB or 1GB [[PC2700]] memory standard (max 2GB)
* One of the following HDD:
** 20 GB @ 4200 RPM
** 60 GB @ 5400 RPM
** 60 GB @ 7200 RPM
** 80 GB @ 5400 RPM
* [[AD1981B]] AC'97 Audio controller
* Intel 10/100/1000 Ethernet
* [[UltraBay|UltraBay Slim]] with one of the following:
** DVD-ROM/CD-RW Combo
** DVD-RW
* [[CDC slot]] with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth III with 56K Modem (BMDC-2)]]
* [[MiniPCI slot]] with one of the following:
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter]]
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
** [[Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter]]
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
* (2) Type II [[CardBus slot|CardBus slots]] or (1) type III
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Active Protection System|IBM Active Protection System]]
* [[Integrated Fingerprint Reader]] on select systems
</div>
|}

== Hardware Maintenance Manual ==
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/13n6243.pdf ThinkPad T40/p, T41/p, T42, T42p - Hardware Maintenance Manual (April 2004)] (5,391,719 Bytes)

== Resources ==
* CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/IBM/Thinkpad-T42p

[[Category:T Series]]

Category:T43

2008-12-24T20:50:19Z

Dag-:

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

This pages gives an overview of all ThinkPad T43 related topics.

== Machine Type ==
* 1871
* 1872
* 1875
* 1876 (Intel Graphics)
* 2668
* 2669
* 2686
* 2687 (ATI Graphics)

== Standard Features ==
* [[Intel Pentium M (Dothan)]] 1.6, 1.73, 1.86, 2.0, 2.13 or 2.26 GHz CPU
* One of the following chipsets and graphics adapters:
** [[Intel 915GM]] northbridge with integrated [[Intel Graphics Media Accelerator 900]] [http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-58317#vid (not capable of DVI output)] using shared system RAM
** [[Intel 915PM]] northbridge and an [[ATI Mobility Radeon X300]] with 64MB on-chip dedicated RAM. Supports DVI output through a dock or port replicator.
* [[Intel 82801FBM]] ICH6-M southbridge
* One of the following displays:
** 14.1" TFT display with 1024x768 resolution
** 14.1" TFT display with 1400x1050 resolution
** 15.0" TFT display with 1024x768 resolution
** 15.0" TFT display with 1400x1050 resolution
* 256 or 512MB [[PC2-4200]] memory standard, 2GB max
* 40, 60 or 80GB PATA HDD{{footnote|1}}
* [[AD1981B]] AC'97 Audio controller
* [[Ethernet Controllers|Broadcom 10/100/1000 Ethernet]]
* [[UltraBay|UltraBay Slim]] with one of the following:
** DVD-ROM
** DVD-ROM/CD-RW Combo
** DVD±RW
* [[CDC slot]] with one of the following:
** [[IBM Integrated 56K Modem (MDC-2)]]
** [[IBM Integrated Bluetooth IV with 56K Modem (BMDC-3)]]
* [[MiniPCI slot]] with one of the following:
** none (empty)
** [[IBM 11a/b/g Wireless LAN Mini PCI Adapter II]]
** [[Intel PRO/Wireless 2200BG Mini-PCI Adapter]]
** [[Intel PRO/Wireless 2915ABG Mini-PCI Adapter]]
* [[CardBus slot]] (Type 2)
* [[ExpressCard slot|ExpressCard/54 slot]]
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Active Protection System|IBM Active Protection System]]
* [[Integrated Fingerprint Reader]] on select systems
* [[UltraNav]] (TrackPoint / Touchpad combo)
</div>
|style="vertical-align:top" |
[[Image:ThinkpadT43P.JPG|ThinkPad T43]]
|}
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58837 ThinkPad T43 - Hardware Maintenance Manual (for 1xxxx models)]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58791 ThinkPad T43/p - Hardware Maintenance Manual (for 2xxxx models)]
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58597 ThinkPad T43/p - Software and Device Drivers]
* [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tabook.pdf tabook] - detailed hardware specifications for every sub-model
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-50233 ThinkPad T40/p, T41/p, T42/p, T43/p - Hardware removal and installation] (instructions and '''movies''' for all major components)
* [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-58719 Common service parts - ThinkPad T43/p]
* [http://www-306.ibm.com/common/ssi/fcgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS105-209 "ThinkPad T43 machine type 18xx models do not support DVI monitors"] (referring to use of DVI port on replicators/docks with these models)

==Photos==
{{gallery_start}}
{{thumb|T43-2668-open-above.jpg|T43-2668, open, view from above}}
{{thumb|T43-2668-open-GPU.jpg|T43-2668, open, view towards GPU}}
{{thumb|T43p-82801FBM.jpg|T43-26xx, open, view of southbridge and GPU}}
{{thumb|T43p-H8S2161.jpg|T43-26xx, open, view of embedded controller (under PC Card / Express Card assembly)}}
{{thumb|T43-1871_keyboard_removed.jpg|T43-1871, keyboard removed, view from above}}
{{gallery_end}}

=== External links ===
* at [http://www.emtec.com/zzstuff/T43-2668.zip emtec.com]
* at [http://hcs.harvard.edu/~gsmenden/t43pfan.JPG hcs.harvard.edu/~gsmenden]
* at [http://digi.mop.com/1/54/80/29551.html digi.mop.com]
* 1871-15J at [http://www.aichi.to/~thinkpad/tpt43/ aichi.to]
* [http://linuxfocus.org/~guido/gentoo-tpt43p/cooling/ Guido's cooling system for the T43p]
* Fan replacement at [http://www.ezit.com.cn/art/1561/20051216/394649_1.html ezit.com.cn] or [http://www.gog.com.cn/jq/j0501/ca917198.htm www.gog.com.cn]

=== Resources ===
CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/IBM/Thinkpad-T43

{{footnotes|
#While the physical disk is PATA (IDE), it is accessed through a SATA controller and a SATA-to-PATA bridge. It thus appears as a SATA device to the operating system, which causes some [[Problems with SATA and Linux|problems under Linux]]. The SATA-to-PATA bridge also necessitates drive firmware changes, causing a [[Problem with non-ThinkPad hard disks|problem with non-ThinkPad hard disks]].
}}

[[Category:T Series]]

Category:R61i

2008-12-24T20:47:38Z

Dag-:

I'm using Ubuntu 8.04 (Hardy Heron) on my Lenovo ThinkPad R61i. These are the hardware specific details of my installation.
Some of my problems are not listed here as they vanished with a kernel upgrade. Actually I use the vanilla 2.6.24(-17-generic) kernel.

==lspci==
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
15:00.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ba)
15:00.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21)
15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)
15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 11)
15:00.5 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 11)

==Hard disk issues==
The disk does approx. 25 load cycles per minute. This could be too much. I guess this is related to a Linux/disk firmware [http://www.gablog.eu/online/node/53 bug].

==Updateing the BIOS==
I had to update the BIOS prior installing Linux as a stand alone operating system because only the win32 update utility worked, the bootable FreeDOS CD-image failed to boot:

cdr101 not ready reading drive c.

==ACPI issues==
ACPI still remain an issue for Linux. The kernel code is made of spaghetti, full of legacy parts and crappy worksforme code.

=== Suspend, hibernate, resume===
The current ACPI code is a reason for all sorts of problems around [http://brainstorm.ubuntu.com/idea/94/ suspend, hibernate and resume], but luckily it works pretty stable for this model.

===Hotkeys===
All the hotkeys at the top work well. But the multimedia keys at the bottom (zoom,prev,play/pause,stop on space,left,down,right,up) do not work at all. They not even generate a kernel event, neither ACPI nor keyboard.

===Hotswap drivebay===
I don't have a second device, but the hotswap function obviously wouldn't work: ejecting the optical driver from the bay results in a kernel hang (no oops, no dump, just freeze). Not working at all, if no device is present at boot time, otherwise it should work.

===Docking station===
Couldn't test it, but the [http://ibm-acpi.sourceforge.net/ thinkpad_acpi] [http://ibm-acpi.sourceforge.net/README documentation] states that it should work, but only if a docking station is present at the boot time.

==Fingerprint reader==
Does not work. Lenovo replaced the TouchStrip fingerprint module (long used in ThinkPads by IBM) with one from UPEK. According to lsusb:
Manufacturer TouchStrip
Model Fingerprint Sensor
Bus usb
Type Vendor Specific Class
Id 147e
Info2 2016

The fingerprint reader libthinkfinger won't work! UPEK claims to have an [http://www.upek.com/solutions/pc_and_networking/sdks/linux/ driver], but it failed to build for me. It uses proprietary code, and requires to use a scarce authentication model.

==Trackpoint and touchpad==
Works fine. You need to add
Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SHMConfig" "on"
EndSection
to xorg.conf to be able to configure it's characteristics in more detail. I prefer gsynaptics to disable tap clicking and enable a horizontal scroll.

==Firewire==
Not tested.

==USB==
Fast and flawless.

==Gigabit LAN==
Fast and flawless.

==Bluetooth==
Works well. To turn it on/off separately from the wifi (that can be done by Fn+F5), I use this script mapped to the blue 'ThinkVantage' button on the top:
#!/bin/bash
cat /proc/acpi/ibm/bluetooth | awk '{ print $2 }' | while read line;
do
if [ $line == "enabled" ]; then
echo disable > /proc/acpi/ibm/bluetooth
else
echo enable > /proc/acpi/ibm/bluetooth
fi
break
done

==Wifi==
It is surprisingly stable and reliable. Although the LED for wirless activity does not work.

==Video==

===Internal TFT===
Good image quality, stable open source driver. Ubuntu has a patch for the X.org driver to get hardware overlay for XVideo working with compiz enabled. Additional tweaks are required to get compiz working, although some effects are utterly slow. Use this in xorg.conf:
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "AccelMethod" "EXA"
Option "ExaNoComposite" "false"
Option "TexturedVideo" "false"
Option "MigrationHeuristic" "greedy"
EndSection
And add this to /etc/environment:
LIBXCB_ALLOW_SLOPPY_LOCK=1
INTEL_BATCH="1"

===External VGA===
A little more problematic. Compiz gets too slow to remain usable on two monitors. This can't be because of the Intel chip, as rendering a simple cube with textures can't require hardcore 3D acceleration.
Also GL screensavers result usually in a black monitor (no hang, just no console at all).
I had to extend xorg.conf to get an appropriate virtual screen to fit both the internal and external displays in.
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
DefaultDepth 24
SubSection "Display"
Depth 24
# no DRI above this
Virtual 2048 2048
EndSubSection
EndSection
xrandr works well for configuring the displays and managing the modes. The hotkey on the keyboard switches to clone mode. I prefer a more sophisticated control using [http://www.gablog.eu/online/node/67 this] script.

===S-VIDEO out===
I don't know whether it is working or not, but it is not listed in xrandr.

==Cardreader==
Works flawless and out of the box.

==Sound==
Sound quality is good until PCM volume is below 75%. The internal microphone does not work at all. All the external microphones I used produced a horrible recording quality. Some voice recording programs failed to work or recorded silence. This is a big issue for me.

==HDAPS==
[http://www.thinkwiki.org/wiki/HDAPS HDAPS] should protect the hard disk in case of falling/dropping/hitting the laptop by parking the heads in case of unusual acceleration patterns. That's right, ThinkPads ship with an acceleration meter.

With the newest kernel the measuring works. hdaps-gl displays the orientation of the laptop in space. I submitted a kernel patch (for drivers/hwmon/hdaps.c) to lkml to reverse an axis:
@@ -515,6 +515,7 @@ static struct dmi_system_id __initdata h
HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R50"),
HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R51"),
HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad R52"),
+ HDAPS_DMI_MATCH_INVERT("LENOVO", "ThinkPad R61i"),
HDAPS_DMI_MATCH_INVERT("IBM", "ThinkPad T41p"),
HDAPS_DMI_MATCH_NORMAL("IBM", "ThinkPad T41"),
HDAPS_DMI_MATCH_INVERT("IBM", "ThinkPad T42p"),
Or you can simply add invert=1 to the module parameters of hdaps_ec.

Please note, that protection will not work! It [http://www.thinkwiki.org/wiki/HDAPS#Kernel_patch seems] that the kernel does not apply any protection, it just makes the measured valued available to userspace. More worse, there is no userspace or kernel tool available to do the parking (yet).

==Battery==
According to powertop there are 100-300 wakeups-from-idle per seconds. This seems very high. Power usage is between 15 and 22 watts. On batteries I enabled laptop-mode, dim the backlight and if not needed, I use the RF kill switch.
# cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 56160 mWh
last full capacity: 53240 mWh
battery technology: rechargeable
design voltage: 10800 mV
design capacity warning: 2662 mWh
design capacity low: 200 mWh
capacity granularity 1: 1 mWh
capacity granularity 2: 1 mWh
model number: 42T4504
serial number: 42054
battery type: LION
OEM info: SANYO
After half a year of heavy usage I have the above capacity and a runtime of 2,5-3 hours on batteries.

==Modem==
Who cares?

==PCMCIA, CardBus==
Not tested.

==Kernel options==
Do NOT add irqpoll to the kernel options as it will cause a severe nondeterministic behaviour.

= Resources =
CentOS install: http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-R61i

Category:R61i

2008-12-24T20:46:39Z

Dag-: /* lcpsi */

Category:X60

2008-12-24T20:44:32Z

Dag-: /* ThinkPad X60 */

{| 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;">
=== ThinkPad X60 ===
This pages gives an overview of all ThinkPad X60 related topics.

==== Standard Features ====
* One of the following processors:
** [[Intel Core Duo (Yonah)]] 1.66 or 1.83 GHz
** [[Intel Core Solo (Yonah)]] 1.66 GHz
** [[Intel Core 2 Duo (Merom)]] 1.66/1.83 GHz (2MB Cache) or 2.0 GHz (4MB Cache)
* [[Intel Graphics Media Accelerator 950]]
** 12.1" TFT display with 1024x768 resolution
* 512 or 1024 MB [[PC2-5300]] memory standard
* 40, 60, 80 100 or 120 GB SATA 2.5" HDD
* [[Active Protection System|IBM Active Protection System]]
* [[AD1981HD]] HD Audio 1.0 controller
* [[Ethernet Controllers#Intel Gigabit (10/100/1000)|Intel Gigabit Ethernet Controller]]
* [[MiniPCI Express slot]] with one of the following:
** [[Intel PRO/Wireless 3945ABG Mini-PCI Express Adapter]]
** Thinkpad 11a/b/g Mini-PCI Express Adapter
** Thinkpad 11/a/b/g/n Mini-PCI Express Adapter
* [[Embedded Security Subsystem|IBM Embedded Security Subsystem 2.0]]
* [[Integrated Fingerprint Reader]] in some models
* [[SD Card slot]] with IO support
* [[CardBus slot]] (Type 2)
* Firewire (IEEE1394)
</div>
|style="vertical-align:top" |
[[Image:ThinkPadX60.jpg|ThinkPad X60]]
|}

==== Hardware Maintenance Manual ====
* [ftp://ftp.software.ibm.com/pc/pccbbs/mobiles_pdf/42x3550_01.pdf ThinkPad X60, X60s, X61, X61s - Hardware Maintenance Manual (Released on 6 Aug 2007)] (10,088,308 Bytes)

==== Resources ====
* CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-X60

==== Reviews ====
* [http://www.notebookreview.com/default.asp?newsID=3173&review=lenovo+thinkpad+x60], 2006-01-05

[[Category:X Series]]

Category:X200s

2008-12-24T20:42:11Z

Dag-: /* Resources */

{| width="100%"
|style="vertical-align:top" |
=== ThinkPad X200s ===
This page gives an overview of all ThinkPad X200s related topics.

<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
==== Standard Features ====
* One of the following processors:
** Intel Core2 Duo processor SU9300 (1.2GHz, 3MB L2, 800MHz FSB)
** Intel Core2 Duo processor SL9300 (1.6Ghz, 1Ghz FSB)
** Intel Core2 Duo processor SL9400 (1.8Ghz, 1Ghz FSB)
* Onboard Graphics
** Intel Graphics Media Accelerator 4500MHD
* One of the following screens
** 1440x900 12.1" (LED backlight) 250 nit
** 1280x800 12.1" (CCFL backlight) 200 nit
* Memory
** Support for up to 4GB DDR3-RAM PC3-8500
* Card Reader (SD,SDHC,MMC,MS & MS Pro) Some configurations with SD-card slot only.
* Network
** Wired
*** Intel Gigabit Ethernet Controller (82567LM)
** Wireless
*** (MiniPCI Express slot 1) (Intel WiFi Link 5300AGN)
*** Bluetooth
*** UWB
* Other Options
** Ultrabase
** Fingerprint Gadget
** Intel Turbo Memory 2GB
** Audio (Conexant Azalia Audio Codec)
* Battery Sizes - 4 cell, 6 cell, 9 cell (sticks out the back)

==== Resources ====
Debian sid install: http://larsgg.spaces.live.com/blog/cns!2019B2D8CDA6ED!748.entry

Arch Linux install: http://itgen.blogspot.com/2008/12/installing-arch-linux-on-lenovo.html

CentOS 5 install: http://wiki.centos.org/HowTos/Laptops/Lenovo/Thinkpad-X200s

==== Reviews ====
http://forum.thinkpads.com/viewtopic.php?t=67851

[[Category:X Series]]