summaryrefslogtreecommitdiff
path: root/README
blob: ed4b87a5f1eb4b302c737da2a705cdd9b7d500e8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
=============================================================================

     FOR QUICK INSTALLATION INSTRUCTIONS SEE THE 'QUICKSTART' FILE.
     FOR FULL INSTALLATION INSTRUCTIONS SEE THE 'INSTALL' FILE.
     FOR THE FAQ SEE THE 'doc/FAQ' or 'doc/lm_sensors-FAQ.html' FILES.

=============================================================================

OVERVIEW OF THE LM_SENSORS PACKAGE AND SUMMARY OF SUPPORTED DEVICES

           !!! THIS PACKAGE REQUIRES i2c-2.8.0 or later!!!

FOR 2.5 KERNELS, Do not attempt to compile this package.
                 Use the drivers already in the 2.5 kernel development tree.

=============================================================================

This is the completely rewritten version 2 of lm_sensors, a collection of
modules for general SMBus access and hardware monitoring.
Version 1 is now officially unsupported.

WARNING! This package will work on kernels 2.4.9 - 2.4.xx only.
Use lm_sensors-2.4.5 for 2.0 kernels.
Use lm_sensors-2.7.0 for 2.2, 2.3, and 2.4.0 - 2.4.8 kernels.
Use the drivers already in the kernel for 2.5 kernels; if you need
additional drivers in 2.5 please port and submit them to us.

WARNING! You must get the latest i2c package, i2c-2.8.0,
EVEN IF your kernel does contain i2c support!!!!!!!!!

The I2C package in existing 2.4 kernels is NOT sufficient
for compilation of this package.

ADDITIONALLY, i2c-2.8.0 is not API compatible to earlier i2c
releases due to struct changes; therefore you must NOT ENABLE
any other i2c drivers (e.g. bttv) in the kernel.
Do NOT use lm-sensors 2.8.0 or i2c-2.8.0 if you require bttv.

See the lm_sensors download page for further guidance:
  http://secure.netroedge.com/~lm78/download.html


WARNING! If you downloaded this package through our CVS archive, you walk
the cutting edge. Things may not even compile! On the other hand, you will
be the first to profit from new drivers and other changes. Have fun!

=============================================================================

At least the following I2C/SMBus adapters are supported:
  Acer Labs M1533, M1535, and M1543C
  AMD 756, 766, 768 and 8111
  AMD 8111 SMBus 2.0
  Apple Hydra (used on some PPC machines)
  DEC 21272/21274 (Tsunami/Typhoon - on Alpha boards)
  Intel I801 ICH/ICH0/ICH2/ICH3/ICH4/ICH5
  Intel PIIX4 (used in many Intel chipsets)
  Intel I810/I815 GMCH
  Intel 82443MX (440MX)
  NVidia nForce
  ServerWorks OSB4, CSB5
  SiS 5595, 630, 645, 730
  SMSC Victory66
  3Dfx Voodoo 3 and Banshee
  VIA Technologies VT82C586B, VT82C596A/B, VT82C686A/B, VT8231,
                   VT8233, VT8233A, and VT8235.


At least the following hardware sensor chips are supported:
  Analog Devices ADM1021, ADM1021A, ADM1022, ADM1023, ADM1024,
                 ADM1025, ADM1026, ADM1027 and ADM9240
                 ADT7463
  Asus AS99127F, ASB100 Bach
  Dallas Semiconductor DS75, DS1621, DS1625, DS1775, and DS1780
  Hewlett Packard Maxilife (several revisions including '99 NBA)
  Fujitsu Siemens Poseidon, Scylla
  Genesys Logic GL518SM (rev 00, 80), GL520SM, GL523SM
  Intel Xeon processor embedded sensors
  ITE IT8705F, IT8712F embedded sensors
  Maxim MAX1617 and MAX1617A
  Microchip TC1068, TCM1617, TCN75
  Myson MTP008
  National Semiconductor LM75, LM77, LM78, LM78-J, LM79,
                         LM80, LM81, LM84, LM85, LM87, and LM92
  Philips NE1617, NE1617A
  SiS 5595, 950 embedded sensors
  SMSC 47M1xx embedded sensors, EMC6D100, EMC6D101
  TI THMC10 and THMC50
  VIA Technologies VT1211 and VT82C686A/B embedded sensors
  Winbond W83781D, W83782D, W83783S, W83791D,
          W83627HF, W83627THF, and W83697HF


We also support some miscellaneous chips:
  Dallas DS1307 real time clock
  Intel Xeon processor embedded EEPROMs
  Linear Technologies LTC1710
  Philips Semiconductors PCF8574, PCF8591  
  DDC Monitor embedded EEPROMs
  SDRAM Dimms with Serial Presence Detect EEPROMs
  Smart Battery sensors
  IPMI-BMC sensors


See our New Drivers page http://www.lm-sensors.nu/~lm78/newdrivers.html
for the latest information on supported devices.


We always appreciate testers. If you own a specific monitoring
chip listed on our 'new drivers' page, and are willing to help us out,
please contact us. Even if you have no programming knowledge, you could
help us by running new modules and reporting on the results and output.
If you want to offer more substantial help, this is very welcome too, of
course.


Don't ask us whether we support a particular mainboard; we do not know.
We *do* know what hardware we support, but usually, it is easier to
install everything and run sensors-detect. It will tell you what hardware
you have (and incidentally, what corresponding drivers are needed). You
could also take a look at http://mbm.livewiredev.com/
(this lists chips found on many mainboard, but regrettable, not the adapters
on them) or http://web01.fureai.or.jp/~hirobo/project/reserch_project.html
(yes, it is japanese; you want the ninth column, and it again lists only
chips, not adapters).


SMBus, also known as System Management Bus, is a protocol for communicating
through a I2C ('I squared C') bus. Many modern mainboards have a System
Management Bus. There are a lot of devices which can be connected to a
SMBus; the most notable are modern memory chips with EEPROM memories and
chips for hardware monitoring.

Most modern mainboards incorporate some form of hardware monitoring chips.
These chips read things like chip temperatures, fan rotation speeds and
voltage levels. There are quite a few different chips which can be used
by mainboard builders for approximately the same results.

Hardware monitoring chips are often connected to the SMBus, but often they
can also be connected to the ISA bus. The modules in this package usually
support both ways of accessing them.

Because the SMBus is just a special case of the generalized I2C bus, we
can simulate the SMBus protocol on plain I2C busses. These busses are
sometimes used in other parts of your computer. If a supported chip is
attached to one of these additional busses, they can be used too.

Please read INSTALL before trying to compile and install these modules.
There is a lot of additional documentation in the doc/ subdirectory.
Amnong these is a list of supported busses and chips. Regrettably, there
are too many mainboards to keep a list of busses and chips used on them.
On the other hand, we provide a program called 'sensors-detect' which
tries to figure out what hardware is available on your system.

The developers of this package can be reached through the email address
<sensors@stimpy.netroedge.com>. Do not hesitate to mail us if you have 
questions, suggestions, problems, want to contribute, or just want to 
report it works for you. But please try to read the documentation and
FAQ before you ask any questions!

The latest version of this package can always be found on our homepage:
http://secure.netroedge.com/~lm78. Pre-release versions can be retrieved
through anonymous CVS; see doc/cvs for more information.

This whole package is copyright (c) 1998 - 2002 by Frodo Looijaard and
Philip Edelbrock, except for a few drivers written by
other people. See the individual files for more exact copyright information.  
This package may be distributed according to the GNU General Public License 
(GPL), as included in the file COPYING.

Note that at this moment, libsensors falls under the GPL, not the LGPL.
In more human language, that means it is FORBIDDEN to link any application
to the library, even to the shared version, if the application itself
does not fall under the GPL. This will probably be changed in the future.
In the meantime, you will have to contact us first if you want to do this.