ThinkWiki - User contributions [en]

List of DMI IDs

2006-10-26T23:36:47Z

Pohl446: /* X series */

{| 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"
|-
! Model
! <tt>system-<br />manufa<br />cturer</tt>
! <tt>system-<br />product-<br />name</tt>
! <tt>system-<br />version</tt>
! <tt>baseboard-<br />manufa<br />cturer</tt>
! <tt>baseboard-<br />product-<br />name</tt>
! <tt>baseboard-<br />version</tt>
! <tt>chassis-<br />manufa<br />cturer</tt>
! <tt>chassis-<br />version</tt>
! <tt>bios-<br />vendor</tt>
! <tt>bios-<br />version</tt>
! <tt>bios-<br />release-<br />date</tt>
! Embedded controller
! Notes
|-
! colspan=14 style="text-align:center;background:#efefef;" |
====Numbered series====
|-
| {{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
||
||
|-
! 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
||
||
|-
| {{A22p}} 2629-USG
|| IBM || 2629USG || Not Available || IBM || 2629USG || Not Available || IBM || Not Available || IBM || KYET36WW (1.09a) || 10/17/2002
||
|| {{WARN|Outdated BIOS}}
|-
| {{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}} 2653H6U
|| IBM || 2653H6U || Not Available || IBM || 2653H6U || Not Available || IBM || Not Available || IBM || 1GET31WW (1.03 ) || 07/23/2002
||
|| {{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
||
|| {{WARN|Outdated BIOS}}
|-
| {{R40}} 2681-HSG
|| IBM || 2681HSG || Not Available || IBM || 2681HSG || Not Available || IBM || Not Available || IBM || 1OET61WW (1.27 ) || 06/29/2006
||
|| {{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}} 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
||
|| {{WARN|Outdated BIOS}}
|-
|{{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>
||
|-
|{{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}} 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>
|| {{NOTE|Weird system version, this bug is known fixed in latest BIOS}}
|-
| {{R52}} 1846-AQG
|| IBM || 1846AQG || ThinkPad R52 || IBM || 1846AQG || Not Available || IBM || Not Available || IBM || 76ET65WW (1.25 ) || 05/18/2006
|| <nowiki> 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>
|| {{NOTE|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}} 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-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>
||
|-
! 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;" |

====T series====
|-
| {{T20}} 2647-UC2
|| IBM || 2647UC2 || Not Available || IBM || 2647UC2 || Not Available || IBM || Not Available || IBM || IYET45WW (1.08a) || 12/21/1999
||
|| {{WARN|Very outdated BIOS}}
|-
| {{T21}} 2647-8AU
|| IBM || 26478AU || Not Available || IBM || 26478AU || Not Available || IBM || Not Available || IBM || KZET34WW (1.16 ) || 04/28/2004
||
||
|-
| {{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-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
||
|| {{NOTE|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>
||
|-
| {{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
||
|| {{NOTE|Missing EC string, this bug is known to be fixed in latest BIOS}}
|-
| {{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-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
||
|| {{NOTE|Missing EC string, this bug is known to be fixed in latest BIOS}}
|-
| {{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-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}} 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-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-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>
|| {{NOTE|User reports this is really a 2669-CEU with 1GB RAM + BlueTooth, and not a 2669-WE5 (unverified if this makes sense)}}
|-
| {{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}} 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>
||
|-
| {{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>
||
|-
| {{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-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-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}} 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 || 79ET65WW (1.09a) || 07/27/2006
|| <nowiki>Handle 0x0026, DMI type 11, 5 bytes String 1: IBM ThinkPad Embedded Controller -[79HT48WW-1.05b ]-</nowiki>
||
|-
! colspan=14 style="text-align:center;background:#efefef;" |

====X series====
|-
| {{X20}} 266231G
|| IBM || 266231G || Not Available || IBM || 266231G || Not Available || IBM || Not Available || IBM || IZET9DWW (2.25 ) || 04/17/2003
||
||
|-
| {{X23}} 2662EBG
|| IBM || 2662EBG || Not Available || IBM || 2662EBG || Not Available || IBM || Not Available || IBM || 1DET70WW (1.32 ) || 06/10/2003
|| <nowiki></nowiki> ||
|-
| {{X24}} 2662-MPU
|| IBM || 62MPUFX || Not Available || IBM || 62MPUFX || Not Available || IBM || Not Available || IBM || 1DET67WW (1.29 ) || 12/18/2002
||
||
|-
| {{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>
||
|-
| {{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>
||
|-
| {{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>
||
|-
| {{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>
||
|-
| {{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>
||
|-
! 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>
||
|-
| {{Z60m}} 2529-FKG
|| IBM || 2529FKG || ThinkPad Z60m || IBM || 2529FKG || Not Available || IBM || Not Available || IBM || 77ET42WW (1.05 ) || 11/19/2005
|| String 1: IBM ThinkPad Embedded Controller -[77HT28WW-1.02 ]-
||
|-
| {{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>
||
|-
| {{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}} 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> ||
|-
| {{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>
||
|-
| {{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> ||
|}
</div>

==Adding entries==

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

where the two data lines are genereated 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` "; 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>

While at it, you may also want to 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
* [[ibm-acpi]] driver quirk list (in unofficial patches)

How to make use of IrDA

2006-05-27T21:11:31Z

Pohl446: /* {{Debian}} Sarge/Etch kernel config */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
The purpose of this document is to get the [[IrDA]] hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.
</div>
|}

== Serial IR (SIR) ==
SIR is limited to serial datarates up to 115.2Kb/s

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines
alias tty-ldisc-11 irtty-sir
alias char-major-161 ircomm-tty

== Fast IR (FIR) ==
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps

The chips FIR mode first needs to be activated using the ISA PnP or BIOS method.

{{HINT|Regardless of which method you use, you will still have to set the dongle_id and run setserial as shown further below}}
=== ISA PnP support for nsc-ircc ===
Starting with the 2.6.17-rc1 kernel, the nsc-ircc driver has ISA PnP support, and seperate patching is no longer required.

If you have an older 2.6 kernel, here are some patches, that allow the loading of the driver without the below BIOS change.<br />
* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12.diff 2.6.12 patch (applies cleanly to 2.6.12 through 2.6.15)]
* patches as part of 2.6.17-rc1: [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1931 nsc-ircc.c]and [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1932 nsc-ircc.h]

ISA PnP support seems '''necessary''' in some cases (e.g., ThinkPad {{T43}} and kernel 2.6.14 and 2.6.15).

=== Changing BIOS settings ===
For older kernels (prior to 2.6.17-rc1), the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing {{key|F1}} when prompted.
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port, and ensure the proper resources are set (typically: IO 0x2f8 and IRQ 3). Be sure to save the changes, and then Exit.

{{NOTE|Changing these BIOS settings does not affect Windows 2000 or XP operating systems, but may cause resource issues in older windows versions, or other legacy operating systems.}}

{{WARN|If you change the BIOS settings for IO, IRQ or DMA of the IrDA port, remember to do so accordingly on all examples in this page when applying them to your ThinkPad.}}

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

The install line is a work-around for the 8250 serial driver taking over the device, and may not be needed in certain distributions.

==== {{Gentoo}} kernel config ====
Edit / Create {{path|/etc/modules.d/nsc-irrc}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3

Edit {{path|/etc/modules.autoload.d/kernel-2.6}} and add the following lines

nsc-ircc

If you have serial support build in the kernel, switch it to a module and add it after nsc-ircc to advoid io base and irq conflict. For kernel 2.4, same as 2.6 changing the path to modules.autoload.d/kernel-2.4.

==== {{Debian}} Sarge/Etch kernel config ====
Install irda-utils and set it up for serial port emulation. Edit {{path|/etc/modprobe.d/irda-utils}} and add/change the following lines:

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3

Edit / create {{path|/etc/modules.conf}} and add the following line before any references to 8250*, if any:

nsc-ircc

Make sure that module-init-tools has a chance to iterate over {{path|/etc/modules.conf}} before udev does the initial pci hotplug (this is a problem at least in Debian Sarge, when using backported udev packages):

{{cmdroot|cp /etc/rcS.d/S20module-init-tools /etc/rcS.d/S03module-init-tools}}

Note that at S03, module-init-tools cannot run depmod for you, so either do it manually before you reboot into a new kernel, or reboot twice to get it to work right. This is also the reason for using cp instead of mv.

If you have the regular serial port drivers as modules, that's it. Otherwise, try adding the install line described in the Linux 2.6 kernel config section, above, or compile them as modules instead of built-in.

== Known problems ==
* If the FIR mode is not activated, attempts to load the <tt>nsc-ircc</tt> module will result in an error in syslog of "Wrong chip version ff".
* After suspend the <tt>nsc-ircc</tt> module needs to be manually reloaded
* If module reloading does not work after a suspend, try reactivating the IrDA port as well:
rmmod nsc_ircc
echo disable > /sys/devices/pnp0/00\:0d/resources
echo activate > /sys/devices/pnp0/00\:0d/resources
modprobe nsc_ircc
:The value <tt>pnp0/00\:0d</tt> can vary - look for a resources file containing the appropriate irq/dma/io values, e.g., using {{cmdroot|grep 0x2f8 /sys/devices/pnp*/*/resources}} .
{{NOTE|The power management issues should be resolved starting with the 2.6.17-rc1 kernel.}}

== Some other things you might want to do with IrDA ==
* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}
* set the connection speed to 4Mbit in FIR mode:
:{{cmdroot|echo 4000000 > /proc/sys/net/irda/max_baud_rate}}

==LIRC and IrDA==
Usually, IrDA port's are not compatible with LIRC, but you may have luck using lirc_sir.

If loading the <tt>lirc_sir</tt> module shows something like the following in {{cmdroot|dmesg}} output, you are lucky and can use LIRC with the IrDA port to remote control your ThinkPad.
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.

== External Sources ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control] (External)

How to make use of IrDA

2006-05-27T20:56:08Z

Pohl446: /* {{Debian}} Sarge/Etch kernel config */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
The purpose of this document is to get the [[IrDA]] hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.
</div>
|}

== Serial IR (SIR) ==
SIR is limited to serial datarates up to 115.2Kb/s

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines
alias tty-ldisc-11 irtty-sir
alias char-major-161 ircomm-tty

== Fast IR (FIR) ==
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps

The chips FIR mode first needs to be activated using the ISA PnP or BIOS method.

{{HINT|Regardless of which method you use, you will still have to set the dongle_id and run setserial as shown further below}}
=== ISA PnP support for nsc-ircc ===
Starting with the 2.6.17-rc1 kernel, the nsc-ircc driver has ISA PnP support, and seperate patching is no longer required.

If you have an older 2.6 kernel, here are some patches, that allow the loading of the driver without the below BIOS change.<br />
* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12.diff 2.6.12 patch (applies cleanly to 2.6.12 through 2.6.15)]
* patches as part of 2.6.17-rc1: [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1931 nsc-ircc.c]and [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1932 nsc-ircc.h]

ISA PnP support seems '''necessary''' in some cases (e.g., ThinkPad {{T43}} and kernel 2.6.14 and 2.6.15).

=== Changing BIOS settings ===
For older kernels (prior to 2.6.17-rc1), the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing {{key|F1}} when prompted.
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port, and ensure the proper resources are set (typically: IO 0x2f8 and IRQ 3). Be sure to save the changes, and then Exit.

{{NOTE|Changing these BIOS settings does not affect Windows 2000 or XP operating systems, but may cause resource issues in older windows versions, or other legacy operating systems.}}

{{WARN|If you change the BIOS settings for IO, IRQ or DMA of the IrDA port, remember to do so accordingly on all examples in this page when applying them to your ThinkPad.}}

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

The install line is a work-around for the 8250 serial driver taking over the device, and may not be needed in certain distributions.

==== {{Gentoo}} kernel config ====
Edit / Create {{path|/etc/modules.d/nsc-irrc}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3

Edit {{path|/etc/modules.autoload.d/kernel-2.6}} and add the following lines

nsc-ircc

If you have serial support build in the kernel, switch it to a module and add it after nsc-ircc to advoid io base and irq conflict. For kernel 2.4, same as 2.6 changing the path to modules.autoload.d/kernel-2.4.

==== {{Debian}} Sarge/Etch kernel config ====
Install irda-utils and set it up for serial port emulation. Edit {{path|/etc/modprobe.d/irda-utils}} and add/change the following lines:

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /sbin/modprobe --ignore-install nsc-ircc && echo 4000000 > /proc/sys/net/irda/max_baud_rate

Edit / create {{path|/etc/modules.conf}} and add the following line before any references to 8250*, if any:

nsc-ircc

Make sure that module-init-tools has a chance to iterate over {{path|/etc/modules.conf}} before udev does the initial pci hotplug (this is a problem at least in Debian Sarge, when using backported udev packages):

{{cmdroot|cp /etc/rcS.d/S20module-init-tools /etc/rcS.d/S03module-init-tools}}

Note that at S03, module-init-tools cannot run depmod for you, so either do it manually before you reboot into a new kernel, or reboot twice to get it to work right. This is also the reason for using cp instead of mv.

If you have the regular serial port drivers as modules, that's it. Otherwise, try adding the install line described in the Linux 2.6 kernel config section, above, or compile them as modules instead of built-in.

== Known problems ==
* If the FIR mode is not activated, attempts to load the <tt>nsc-ircc</tt> module will result in an error in syslog of "Wrong chip version ff".
* After suspend the <tt>nsc-ircc</tt> module needs to be manually reloaded
* If module reloading does not work after a suspend, try reactivating the IrDA port as well:
rmmod nsc_ircc
echo disable > /sys/devices/pnp0/00\:0d/resources
echo activate > /sys/devices/pnp0/00\:0d/resources
modprobe nsc_ircc
:The value <tt>pnp0/00\:0d</tt> can vary - look for a resources file containing the appropriate irq/dma/io values, e.g., using {{cmdroot|grep 0x2f8 /sys/devices/pnp*/*/resources}} .
{{NOTE|The power management issues should be resolved starting with the 2.6.17-rc1 kernel.}}

== Some other things you might want to do with IrDA ==
* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}
* set the connection speed to 4Mbit in FIR mode:
:{{cmdroot|echo 4000000 > /proc/sys/net/irda/max_baud_rate}}

==LIRC and IrDA==
Usually, IrDA port's are not compatible with LIRC, but you may have luck using lirc_sir.

If loading the <tt>lirc_sir</tt> module shows something like the following in {{cmdroot|dmesg}} output, you are lucky and can use LIRC with the IrDA port to remote control your ThinkPad.
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.

== External Sources ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control] (External)

How to make use of IrDA

2006-05-27T20:54:43Z

Pohl446: /* {{Debian}} Sarge/Etch kernel config */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
The purpose of this document is to get the [[IrDA]] hardware in your ThinkPad operational, setting up communication to other devices is not covered. However, the external links section can prove useful for this.
</div>
|}

== Serial IR (SIR) ==
SIR is limited to serial datarates up to 115.2Kb/s

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines
alias tty-ldisc-11 irtty
alias char-major-161 ircomm-tty

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines
alias tty-ldisc-11 irtty-sir
alias char-major-161 ircomm-tty

== Fast IR (FIR) ==
FIR is the preferred mode of IrDA operation and operates at a bandwidth of 4 Mbps

The chips FIR mode first needs to be activated using the ISA PnP or BIOS method.

{{HINT|Regardless of which method you use, you will still have to set the dongle_id and run setserial as shown further below}}
=== ISA PnP support for nsc-ircc ===
Starting with the 2.6.17-rc1 kernel, the nsc-ircc driver has ISA PnP support, and seperate patching is no longer required.

If you have an older 2.6 kernel, here are some patches, that allow the loading of the driver without the below BIOS change.<br />
* [http://steffenpingel.de/patches/nsc-ircc-pnp.diff 2.6.10 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12-rc6.diff 2.6.12-rc6 patch]
* [http://shamrock.dyndns.org/~ln/linux/nsc-ircc-pnp.2.6.12.diff 2.6.12 patch (applies cleanly to 2.6.12 through 2.6.15)]
* patches as part of 2.6.17-rc1: [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1931 nsc-ircc.c]and [http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.16-git15.bz2;z=1932 nsc-ircc.h]

ISA PnP support seems '''necessary''' in some cases (e.g., ThinkPad {{T43}} and kernel 2.6.14 and 2.6.15).

=== Changing BIOS settings ===
For older kernels (prior to 2.6.17-rc1), the easiest way to activate FIR mode is by entering BIOS setup during boot-up by pressing {{key|F1}} when prompted.
Then, selecting 'Config' followed by 'Infrared' will allow you to control the IrDA operation. Here you will need to select the option to Enable the infra-red port, and ensure the proper resources are set (typically: IO 0x2f8 and IRQ 3). Be sure to save the changes, and then Exit.

{{NOTE|Changing these BIOS settings does not affect Windows 2000 or XP operating systems, but may cause resource issues in older windows versions, or other legacy operating systems.}}

{{WARN|If you change the BIOS settings for IO, IRQ or DMA of the IrDA port, remember to do so accordingly on all examples in this page when applying them to your ThinkPad.}}

===Kernel configuration===
==== Linux 2.4 kernel config ====
Edit {{path|/etc/modules.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
pre-install nsc-ircc setserial /dev/ttyS1 uart none port 0 irq 0

==== Linux 2.6 kernel config ====
Edit {{path|/etc/modprobe.conf}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc

The install line is a work-around for the 8250 serial driver taking over the device, and may not be needed in certain distributions.

==== {{Gentoo}} kernel config ====
Edit / Create {{path|/etc/modules.d/nsc-irrc}} and add the following lines

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3

Edit {{path|/etc/modules.autoload.d/kernel-2.6}} and add the following lines

nsc-ircc

If you have serial support build in the kernel, switch it to a module and add it after nsc-ircc to advoid io base and irq conflict. For kernel 2.4, same as 2.6 changing the path to modules.autoload.d/kernel-2.4.

==== {{Debian}} Sarge/Etch kernel config ====
Install irda-utils and set it up for serial port emulation. Edit {{path|/etc/modprobe.d/irda-utils}} and add/change the following lines:

alias irda0 nsc-ircc
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3
install nsc-ircc /sbin/modprobe --ignore-install nsc-ircc && echo 4000000 > /proc/sys/net/irda/max_baud_rate

Edit / create {{path|/etc/modules.conf}} and add the following line before any references to 8250*, if any:

nsc-ircc

Make sure that module-init-tools has a chance to iterate over {{path|/etc/modules.conf}} before udev does the initial pci hotplug (this is a problem at least in Debian Sarge, when using backported udev packages):

{{cmdroot|cp /etc/rcS.d/S20module-init-tools /etc/rcS.d/S03module-init-tools}}

Note that at S03, module-init-tools cannot run depmod for you, so either do it manually before you reboot into a new kernel, or reboot twice to get it to work right. This is also the reason for using cp instead of mv.

If you have the regular serial port drivers as modules, that's it. Otherwise, try adding the install line described in the Linux 2.6 kernel config section, above, or compile them as modules instead of built-in.

== Known problems ==
* If the FIR mode is not activated, attempts to load the <tt>nsc-ircc</tt> module will result in an error in syslog of "Wrong chip version ff".
* After suspend the <tt>nsc-ircc</tt> module needs to be manually reloaded
* If module reloading does not work after a suspend, try reactivating the IrDA port as well:
rmmod nsc_ircc
echo disable > /sys/devices/pnp0/00\:0d/resources
echo activate > /sys/devices/pnp0/00\:0d/resources
modprobe nsc_ircc
:The value <tt>pnp0/00\:0d</tt> can vary - look for a resources file containing the appropriate irq/dma/io values, e.g., using {{cmdroot|grep 0x2f8 /sys/devices/pnp*/*/resources}} .
{{NOTE|The power management issues should be resolved starting with the 2.6.17-rc1 kernel.}}

== Some other things you might want to do with IrDA ==
* add fast PPP support:
:{{cmdroot|modprobe irnet}}
* if needed, limit further the size of the transmit window
:{{cmdroot|echo 1 > /proc/sys/net/irda/max_tx_window}}
* set the connection speed to 4Mbit in FIR mode:
:{{cmdroot|echo 4000000 > /proc/sys/net/irda/max_baud_rate}}

==LIRC and IrDA==
Usually, IrDA port's are not compatible with LIRC, but you may have luck using lirc_sir.

If loading the <tt>lirc_sir</tt> module shows something like the following in {{cmdroot|dmesg}} output, you are lucky and can use LIRC with the IrDA port to remote control your ThinkPad.
lirc_sir: I/O port 0x02f8, IRQ 3.
lirc_sir: Installed.

== External Sources ==
*[http://irda.sourceforge.net/ Linux-IrDA Project] (External)
*[http://pcmcia-cs.sourceforge.net/ Linux PCMCIA Project] (External)
*[http://tpctl.sourceforge.net/ tpctl homepage] (External)
*[http://www.lirc.org/ Linux Infrared Remote Control] (External)

How to make use of IrDA

2006-05-27T20:04:35Z

Pohl446: /* Some other things you might want to do with IrDA */

How to make ACPI work

2004-12-19T23:16:56Z

Pohl446: /* using swsusp */

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

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

Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself. You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Basically, acpid just executes scripts residing in <tt>/etc/acpi/actions</tt>. Which script to launch at which event is configured in several files in <tt>/etc/acpi/events</tt>. See <tt>man acpid</tt> for more information on how to configure acpid. The [[ibm-acpi]] packages includes example scripts in the <tt>config</tt> folder inside the tarball. They are a good starting point to adjust them to your needs. You also might have a look at the [[Configs#ACPI | ACPI section of the Configs page]] and you can find information about the event strings ibm-acpi generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

In general it is a good idea to read the README included with the ibm-acpi source tarball.

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

Running <code>xset +dpms</code> and then <code>xset dpms force off</code> will turn off the backlight on a laptop screen.<br />
To force a screen off that is using a radeon chipset, install the [[radeontool]] package.

===Suspend to RAM (Sleep)===
ACPI Sleep and suspend-to-ram with recent 2.6.x kernels usually works fine, too.

With a 2.6.9 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding "acpi_sleep=s3_bios" to the kernel boot parameters.

However I experience some problems with the serial port of the port replicator
after the wake up from ram.

Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

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

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

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

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

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

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

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

Ideally you would do this from a script like <tt>/etc/acpi/actions/hibernate.sh</tt>. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the madwifi driver, if you happen to use it
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

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

====using SoftwareSuspend2====
Todo...

How to make ACPI work

2004-12-19T23:14:14Z

Pohl446: /* Screen blanking (Standby) */

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

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

Unfortunately, special drivers for ACPI on ThinkPads were not included with kernels prior 2.6.10. So you'll have to compile one yourself. You have the choice between [[thinkpad-acpi]] and [[ibm-acpi]], with the latter being the recommended one.

Also you'll need to install [[acpid]], if it isn't present on your system. [[acpid]] is a daemon that handles the ACPI events generated by the system. Basically, acpid just executes scripts residing in <tt>/etc/acpi/actions</tt>. Which script to launch at which event is configured in several files in <tt>/etc/acpi/events</tt>. See <tt>man acpid</tt> for more information on how to configure acpid. The [[ibm-acpi]] packages includes example scripts in the <tt>config</tt> folder inside the tarball. They are a good starting point to adjust them to your needs. You also might have a look at the [[Configs#ACPI | ACPI section of the Configs page]] and you can find information about the event strings ibm-acpi generates for certain keys at the [[How to get special keys to work#ibm-acpi_events | Special Keys HOWTO]].

In general it is a good idea to read the README included with the ibm-acpi source tarball.

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

Running <code>xset +dpms</code> and then <code>xset dpms force off</code> will turn off the backlight on a laptop screen.<br />
To force a screen off that is using a radeon chipset, install the [[radeontool]] package.

===Suspend to RAM (Sleep)===
ACPI Sleep and suspend-to-ram with recent 2.6.x kernels usually works fine, too.

With a 2.6.9 kernel, when resuming from a suspend-to-ram the display might remain black (the system is still rebootable via ctrl-alt-del). This can be fixed by adding "acpi_sleep=s3_bios" to the kernel boot parameters.

However I experience some problems with the serial port of the port replicator
after the wake up from ram.

Also, you might want to take note of the [[Problem with high power drain in ACPI sleep]].

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

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

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

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

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

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

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

Ideally you would do this from a script like <tt>/etc/acpi/actions/hibernate.sh</tt>. It has proven to be a good idea to shutdown the following processes/drivers within the script before you do the actual suspend.
*any running mysql server
*the madwifi driver, if you happen to use it
Afterwards you might want to enable them again, as well as run a script that does necessary configurations according to the ac power state.
Furthermore, the system clock is not readjusted automatically, so you will probably also want the do that from that script (i.e. by restarting your systemclock bootup script).

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

====using SoftwareSuspend2====
Todo...