root/lm-sensors/branches/lm-sensors-2.10/README.thinkpad

Revision 2733, 4.8 KB (checked in by khali, 9 years ago)

Update anti-thinkpad measures list.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1
2****  WARNING: IBM Thinkpad users should not install lm_sensors!  ****
3
4The eeprom of some IBM Thinkpads has been corrupted after installing
5lm_sensors.
6
7In our releases through 2.6.4, sensors-detect (our userspace detection script)
8corrupts the Atmel 24RF08 eeprom. We have verified this in testing.
9After the eeprom is corrupted, the checksum verification in the BIOS
10will fail and the Thinkpad will not boot.
11
12The 24RF08 is an 8K eeprom appearing at addresses 0x54 - 0x57 with
13an additional "access protection page" at address 0x5c.
14This is an unusual eeprom that contains a RFID (Radio Frequency ID)
15port for wireless access, and elaborate access protection mechanisms.
16The 24RF08 gets confused (presumably due to a state machine flaw) by
17the 'quick write 0' (*) probes our package uses for detection.
18This behavior is in violation of the I2C specification. This corruption
19mechanism has never been reported to us on any other eeprom,
20Atmel or otherwise.
21
22We made several changes in release 2.6.5 (released September 15, 2002)
23to minimize the chance of corruption.
24Later evolutions were made and the current state is:
25
261) The probing command (quick write 0) has been replaced by a different
27   command (read byte) for addresses where eeproms are known to live.
28   This should prevent corruption of 24RF08 eeproms in any system,
29   IBM or not. A similar change was made to i2cdetect as well, although
30   no corruption was ever reported using this tool.
31
322) The i2c-piix4 module (the bus driver that is used for Intel PIIX4-based
33   systems, including IBM Thinkpads) now accesses DMI information
34   in the BIOS to identify the system manufacturer. If the system
35   manufacturer is IBM, i2c-piix4 will print a message and exit.
36   As the 24RF08 is on the PIIX4 SMBus, this prevents access to
37   the 24RF08.
38
393) The sequence of probes in the eeprom module (when loaded with
40   checksum=1) has been changed so that 24RF08 eeproms will
41   not be corrupted. This *should* prevent corruption of 24RF08
42   eeproms in non-IBM systems.
43   We do not have any reports of this corruption mechanism in releases
44   2.6.4 or earlier but have verified that it can happen.
45   The ddcmon driver was changed in the same way, just in case.
46
47Even with these changes, we still DO NOT RECOMMEND INSTALLING
48lm_sensors 2.6.5 or later on IBM Thinkpads, because:
49
501) While these changes will dramatically reduce the chance of 24RF08
51   corruption, these changes have not been heavily tested.
52
532) lm_sensors won't run on most IBM systems because of these changes.
54
553) Most IBM Thinkpads contain a proprietary Embedded Controller which
56   is used to access sensors. This controller is not on the SMBus,
57   and IBM will not release the programming interface to the
58   controller. So lm_sensors isn't useful on these Thinkpads anyway.
59
60You may want to try ACPI instead, it should let you get some information
61about temperatures and fan status.
62
63As described above, our 2.6.5 release "blacklisted" all IBM systems.
64For a moment, we have been planning to refine the system detection
65so that only those models containing 24RF08's are blacklisted. After that,
66we planned to use a different approach: a "white list" of known-to-be-safe
67systems. In both cases, it would require continuous updates of a machines
68list. This would have been slow and inefficient.
69
70The latest idea is to stop using the dangerous command for EEPROM
71addresses. That way, risks of corruption are reduced to zero. This was
72already done for user-space tools, as mentioned above. Once this will
73have been tested and we are sure that there are no drawbacks, we'll
74do the same on the kernel side in Linux 2.6. The change won't occur in
75Linux 2.4 however, because it implies changes to both i2c modules and
76lm_sensors modules. It is possible to use mismatching versions of
77these modules, and when doing so, the fix would become more dangerous
78than helpful.
79
80We do not have any reports of 24RF08 eeproms on non-IBM systems.
81If there are any such systems with 24RF08 eeproms, these changes will
82reduce the chances of corruption. However, there are
83theoretical scenarios (involving multiple bus masters,
84SMP systems, or simultaneous bus access) in which 24RF08's could
85still be corrupted. If you know of any non-IBM systems which contain
86these eeproms, please contact us.
87
88
89Thanks to IBM, the Linux Thinkpad Mailing List, and Joe in Australia
90for their assistance on this issue.
91
92For more information, see:
93
94The Linux Thinkpad Mailing List
95http://www.bm-soft.com/~bm/tp_mailing.html
96
97Joe in Australia's Thinkpad Password Recovery Site
98http://www.ja.axxs.net/unlock/
99
100Atmel 24RF08 Datasheet
101http://www.atmel.com/dyn/products/product_card.asp?part_id=2370
102
103Site in the US that sells replacement AT24RF08 chips for all models
104http://www.pwcrack.com/
105
106
107(*) 'Write Quick 0' is not an actual write and should never generate
108     a write operation to an eeprom location.
Note: See TracBrowser for help on using the browser.