root/lm-sensors/trunk/doc/lm_sensors-FAQ.html @ 4197

Revision 4197, 110.4 KB (checked in by khali, 8 years ago)

Delete the icspll driver. It was rather useless, not built by default,
supposedly dangerous, and has nothing to do with sensors.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1<html lang="en">
2<head>
3<title>Sensors FAQ for lm_sensors version 2.18</title>
4<meta http-equiv="Content-Type" content="text/html">
5<meta name="description" content="Sensors FAQ for lm_sensors version 2.18">
6<meta name="generator" content="makeinfo 4.8">
7<link title="Top" rel="top" href="#Top">
8<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
9<meta http-equiv="Content-Style-Type" content="text/css">
10<style type="text/css"><!--
11  pre.display { font-family:inherit }
12  pre.format  { font-family:inherit }
13  pre.smalldisplay { font-family:inherit; font-size:smaller }
14  pre.smallformat  { font-family:inherit; font-size:smaller }
15  pre.smallexample { font-size:smaller }
16  pre.smalllisp    { font-size:smaller }
17  span.sc    { font-variant:small-caps }
18  span.roman { font-family:serif; font-weight:normal; } 
19  span.sansserif { font-family:sans-serif; font-weight:normal; } 
20--></style>
21</head>
22<body>
23<h1 class="settitle">Sensors FAQ for lm_sensors version 2.18</h1>
24Copyright (C) 1998 - 2005<br>
25Frodo Looijaard,<br>
26Philip Edelbrock,<br>
27Mark D. Studebaker<br>
28and<br>
29Jean Delvare<br>
30
31   <div class="shortcontents">
32<h2>Short Contents</h2>
33<ul>
34<li><a href="#toc_Top">lm_sensors</a></li>
35<li><a href="#toc_Overview">1 PC and Sensor Overview</a></li>
36<li><a href="#toc_Basics">2 Sensor and Bus Basics</a></li>
37<li><a href="#toc_Installation">3 Installation and Management</a></li>
38<li><a href="#toc_Problems">4 Problems</a></li>
39<li><a href="#toc_Help">5 How to Ask for Help</a></li>
40<li><a href="#toc_Contribute">6 How to Contribute</a></li>
41<li><a href="#toc_Document-Revisions">Appendix A Revision History of This Document</a></li>
42</ul>
43</div>
44
45   <div class="contents">
46<h2>Table of Contents</h2>
47<ul>
48<li><a name="toc_Top" href="#Top">lm_sensors</a>
49<li><a name="toc_Overview" href="#Overview">1 PC and Sensor Overview</a>
50<ul>
51<li><a href="#Section-1_002e1">1.1 What sensors are available on my PC?</a>
52<li><a href="#Section-1_002e2">1.2 What can a sensor chip like the "LM78" do?</a>
53<li><a href="#Section-1_002e3">1.3 Where do I find out more about any of these chips?</a>
54</li></ul>
55<li><a name="toc_Basics" href="#Basics">2 Sensor and Bus Basics</a>
56<ul>
57<li><a href="#Section-2_002e1">2.1 How are these sensors read?</a>
58<li><a href="#Section-2_002e2">2.2 What is the SMBus? And the I2C bus?</a>
59<li><a href="#Section-2_002e3">2.3 I don't have an ISA bus!</a>
60<li><a href="#Section-2_002e4">2.4 What sensors do processors have?</a>
61<li><a href="#Section-2_002e5">2.5 How often are the sensor values updated?</a>
62<li><a href="#Section-2_002e6">2.6 How are alarms triggered?</a>
63</li></ul>
64<li><a name="toc_Installation" href="#Installation">3 Installation and Management</a>
65<ul>
66<li><a href="#Section-3_002e1">3.1 Why so many modules, and how do I cope with them?</a>
67<li><a href="#Section-3_002e2">3.2 How do I know which chips I own?</a>
68<ul>
69<li><a href="#Section-3_002e2">3.2.1 What chips are on motherboard XYZ?</a>
70<li><a href="#Section-3_002e2">3.2.2 Do you support motherboard XYZ?</a>
71<li><a href="#Section-3_002e2">3.2.3 Do you support chip XYZ?</a>
72<li><a href="#Section-3_002e2">3.2.4 Anybody working on a driver for chip XYZ?</a>
73</li></ul>
74<li><a href="#Section-3_002e3">3.3 Which modules should I insert?</a>
75<li><a href="#Section-3_002e4">3.4 Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>?</a>
76<ul>
77<li><a href="#Section-3_002e4">3.4.1 The labels for the voltage and temperature readings in <samp><span class="command">sensors</span></samp> are incorrect!</a>
78<li><a href="#Section-3_002e4">3.4.2 The min and max for the readings in <samp><span class="command">sensors</span></samp> are incorrect!</a>
79<li><a href="#Section-3_002e4">3.4.3 The min and max settings in <samp><span class="file">/etc/sensors.conf</span></samp> didn't take effect!</a>
80<li><a href="#Section-3_002e4">3.4.4 One sensor isn't hooked up on my board!</a>
81<li><a href="#Section-3_002e4">3.4.5 I need help with <samp><span class="file">sensors.conf</span></samp>!</a>
82<li><a href="#Section-3_002e4">3.4.6 Do you have a database of <samp><span class="file">sensors.conf</span></samp> entries for specific boards?</a>
83</li></ul>
84<li><a href="#Section-3_002e5">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</a>
85<li><a href="#Section-3_002e6">3.6 I get all kinds of weird compilation errors?</a>
86<ul>
87<li><a href="#Section-3_002e6">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</a>
88</li></ul>
89<li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a>
90<li><a href="#Section-3_002e8">3.8 <samp><span class="command">make install</span></samp> fails on Mandrake kernels</a>
91<li><a href="#Section-3_002e9">3.9 I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules (Red Hat especially)</a>
92<li><a href="#Section-3_002e10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a>
93</li></ul>
94<li><a name="toc_Problems" href="#Problems">4 Problems</a>
95<ul>
96<li><a href="#Section-4_002e1">4.1 My fans report exactly half/double their values compared to the BIOS?</a>
97<ul>
98<li><a href="#Section-4_002e1">4.1.1 Fans sometimes/always read 0!!</a>
99<li><a href="#Section-4_002e1">4.1.2 I doubled the fan divisor and the fan still reads 7000!</a>
100</li></ul>
101<li><a href="#Section-4_002e2">4.2 Why do my two LM75's report "-48 degrees"?</a>
102<li><a href="#Section-4_002e3">4.3 Why do I have two Vcore readings, I have only one processor!</a>
103<li><a href="#Section-4_002e4">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</a>
104<li><a href="#Section-4_002e5">4.5 My voltage readings seem to drift a bit. Is something wrong?</a>
105<li><a href="#Section-4_002e6">4.6 Some measurements are way out of range. What happened?</a>
106<ul>
107<li><a href="#Section-4_002e6">4.6.1 -5V and -12V readings are way out of range!</a>
108</li></ul>
109<li><a href="#Section-4_002e7">4.7 What are VID lines? Why is the VID reading wrong?</a>
110<li><a href="#Section-4_002e8">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</a>
111<li><a href="#Section-4_002e9">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</a>
112<li><a href="#Section-4_002e10">4.10 Can I be alerted when an ALARM occurs?</a>
113<li><a href="#Section-4_002e11">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</a>
114<li><a href="#Section-4_002e12">4.12 My BIOS reports a much higher CPU temperature than your modules!</a>
115<li><a href="#Section-4_002e13">4.13 I try to read the raw <samp><span class="file">/proc</span></samp> files, but the values are strange?!?</a>
116<li><a href="#Section-4_002e14">4.14 How do I set new limits?</a>
117<ul>
118<li><a href="#Section-4_002e14">4.14.1 I set new limits and it didn't work?</a>
119</li></ul>
120<li><a href="#Section-4_002e15">4.15 Some sensors are doubly detected?</a>
121<li><a href="#Section-4_002e16">4.16 I ran sensors-detect, but now I get very strange readings?!?</a>
122<li><a href="#Section-4_002e17">4.17 Bad readings from particular chips</a>
123<ul>
124<li><a href="#Section-4_002e17">4.17.1 Bad readings from the AS99127F!</a>
125<li><a href="#Section-4_002e17">4.17.2 Bad readings from the VIA 686A!</a>
126<li><a href="#Section-4_002e17">4.17.3 Bad readings from the MTP008!</a>
127<li><a href="#Section-4_002e17">4.17.4 Bad temperature readings from the SIS5595!</a>
128<li><a href="#Section-4_002e17">4.17.5 Bad readings from a w8378[12]d!</a>
129<li><a href="#Section-4_002e17">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</a>
130<li><a href="#Section-4_002e17">4.17.7 Bad readings from LM75!</a>
131<li><a href="#Section-4_002e17">4.17.8 Bad readings from LM78!</a>
132<li><a href="#Section-4_002e17">4.17.9 Bad readings from LM80!</a>
133</li></ul>
134<li><a href="#Section-4_002e18">4.18 How do I configure two chips (LM87) differently?</a>
135<li><a href="#Section-4_002e19">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</a>
136<ul>
137<li><a href="#Section-4_002e19">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</a>
138</li></ul>
139<li><a href="#Section-4_002e20">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</a>
140<li><a href="#Section-4_002e21">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</a>
141<li><a href="#Section-4_002e22">4.22 Sensors output is not correct!</a>
142<li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a>
143<ul>
144<li><a href="#Section-4_002e23">4.23.1 What is at I2C address 0x69?</a>
145<li><a href="#Section-4_002e23">4.23.2 What is at I2C addresses 0x50 - 0x57?</a>
146<li><a href="#Section-4_002e23">4.23.3 What is at I2C addresses 0x30 - 0x37?</a>
147</li></ul>
148<li><a href="#Section-4_002e24">4.24 Sensors-detect doesn't work at all</a>
149<ul>
150<li><a href="#Section-4_002e24">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</a>
151<li><a href="#Section-4_002e24">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</a>
152<li><a href="#Section-4_002e24">4.24.3 Sensors-detect doesn't find any sensors!</a>
153</li></ul>
154<li><a href="#Section-4_002e25">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</a>
155<li><a href="#Section-4_002e26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a>
156<li><a href="#Section-4_002e27">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</a>
157<li><a href="#Section-4_002e28">4.28 Sensors doesn't find any sensors, just eeproms.</a>
158<li><a href="#Section-4_002e29">4.29 Inserting modules hangs my board</a>
159<li><a href="#Section-4_002e30">4.30 Inserting modules slows down my board</a>
160<li><a href="#Section-4_002e31">4.31 Problems on particular motherboards</a>
161<ul>
162<li><a href="#Section-4_002e31">4.31.1 Asus P4B</a>
163<li><a href="#Section-4_002e31">4.31.2 Tyan 2460, 2462</a>
164<li><a href="#Section-4_002e31">4.31.3 Tyan 2466</a>
165<li><a href="#Section-4_002e31">4.31.4 Tyan 2688</a>
166</li></ul>
167<li><a href="#Section-4_002e32">4.32 Problems on particular systems</a>
168<li><a href="#Section-4_002e33">4.33 Problems on 2.6 kernels</a>
169<ul>
170<li><a href="#Section-4_002e33">4.33.1 i2c-viapro and via686a</a>
171<li><a href="#Section-4_002e33">4.33.2 Where are my EEPROMs?</a>
172</li></ul>
173</li></ul>
174<li><a name="toc_Help" href="#Help">5 How to Ask for Help</a>
175<ul>
176<li><a href="#Section-5_002e1">5.1 What to send us when asking for help</a>
177<li><a href="#Section-5_002e2">5.2 What to do if a module won't insert?</a>
178<li><a href="#Section-5_002e3">5.3 What to do if it inserts, but nothing happens?</a>
179<li><a href="#Section-5_002e4">5.4 What to do if I read only bogus information?</a>
180<li><a href="#Section-5_002e5">5.5 What to do if you have other problems?</a>
181<li><a href="#Section-5_002e6">5.6 What if it just works like a charm?</a>
182<li><a href="#Section-5_002e7">5.7 How do I update a ticket?</a>
183<li><a href="#Section-5_002e8">5.8 How do I follow up on a ticket?</a>
184<li><a href="#Section-5_002e9">5.9 Why did you decide not to support undocumented chips?</a>
185</li></ul>
186<li><a name="toc_Contribute" href="#Contribute">6 How to Contribute</a>
187<ul>
188<li><a href="#Section-6_002e1">6.1 How to write a driver</a>
189<li><a href="#Section-6_002e2">6.2 How to get SVN access</a>
190<li><a href="#Section-6_002e3">6.3 How to donate hardware to the project</a>
191<li><a href="#Section-6_002e4">6.4 How to join the project mailing lists</a>
192<li><a href="#Section-6_002e5">6.5 How to access mailing list archives</a>
193<li><a href="#Section-6_002e6">6.6 How to submit a patch</a>
194<li><a href="#Section-6_002e7">6.7 How to REALLY help</a>
195<li><a href="#Section-6_002e8">6.8 How to get release announcements</a>
196</li></ul>
197<li><a name="toc_Document-Revisions" href="#Document-Revisions">Appendix A Revision History of This Document</a>
198</li></ul>
199</div>
200
201<div class="node">
202<p><hr>
203<a name="Top"></a>
204Next:&nbsp;<a rel="next" accesskey="n" href="#Overview">Overview</a>,
205Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>
206
207</div>
208
209<h2 class="unnumbered">lm_sensors</h2>
210
211<p>The lm_sensors package includes a collection of modules for general SMBus
212access and hardware monitoring.  NOTE: this requires special support which
213is not in standard 2.2-vintage kernels.
214
215<ul class="menu">
216<li><a accesskey="1" href="#Overview">Overview</a>:                 PC and Sensor Overview
217<li><a accesskey="2" href="#Basics">Basics</a>:                   Sensor and Bus Basics
218<li><a accesskey="3" href="#Installation">Installation</a>:             Installation and Management
219<li><a accesskey="4" href="#Problems">Problems</a>:                 Problems
220<li><a accesskey="5" href="#Help">Help</a>:                     How to Ask for Help
221<li><a accesskey="6" href="#Contribute">Contribute</a>:               How to Contribute
222<li><a accesskey="7" href="#Document-Revisions">Document Revisions</a>:       Revision History of This Document
223</ul>
224
225<div class="node">
226<p><hr>
227<a name="Overview"></a>
228Next:&nbsp;<a rel="next" accesskey="n" href="#Basics">Basics</a>,
229Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
230Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
231
232</div>
233
234<h2 class="chapter">1 PC and Sensor Overview</h2>
235
236<ul class="menu">
237<li><a accesskey="1" href="#Section-1_002e1">Section 1.1</a>:              What sensors are available on my PC?
238<li><a accesskey="2" href="#Section-1_002e2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?
239<li><a accesskey="3" href="#Section-1_002e3">Section 1.3</a>:              Where do I find out more about any of these chips?
240</ul>
241
242<div class="node">
243<p><hr>
244<a name="Section-1.1"></a>
245<a name="Section-1_002e1"></a>
246Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e2">Section 1.2</a>,
247Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
248
249</div>
250
251<h3 class="section">1.1 What sensors are available on my PC?</h3>
252
253<p>Most PC's built since late 1997 now come with a
254hardware health monitoring chip. This chip may be accessed via the
255ISA bus or the SMBus, depending on the motherboard.
256
257   <p>Some motherboard chipsets, notably the Via 686 and the SiS 5595,
258contain hardware monitor functions.
259
260   <p>This FAQ frequently refers to the "LM78". This chip has been
261obsoleted by National Semiconductor. Most motherboards today contain
262a chip with similar functions.
263
264<div class="node">
265<p><hr>
266<a name="Section-1.2"></a>
267<a name="Section-1_002e2"></a>
268Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e3">Section 1.3</a>,
269Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e1">Section 1.1</a>,
270Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
271
272</div>
273
274<h3 class="section">1.2 What can a sensor chip like the "LM78" do?</h3>
275
276<p>The LM78 is a chip made by National Semiconductor which can monitor 7
277voltages (5 positive, 2 negative) from 0 to 4.08V.  The inputs are usually in
278series with voltage dividers which lower the +/- 12V and +/- 5V supplies to
279measurable range.  Therefore, the readings for such inputs need to be
280re-scaled appropriately by software.
281
282   <p>The LM78 also has 3 fan speed monitoring inputs, an internal
283temperature sensor, a chassis intrusion sensor, and a couple maskable interrupt
284inputs.  The LM78 can also relay the processor's (P6 or Pent II) VID lines
285which are hardwired and used to indicate to the power regulator (usually on
286the mainboard close to the processor socket/slot) what voltage to supply to
287the processor.
288
289   <p>The LM78 can be interfaced to a system via the ISA bus and/or the
290SMBus.
291
292   <p>Most other sensor chips have comparable functionality. Each supported
293chip is documented in the <samp><span class="file">doc/chips</span></samp> directory.
294
295<div class="node">
296<p><hr>
297<a name="Section-1.3"></a>
298<a name="Section-1_002e3"></a>
299Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e2">Section 1.2</a>,
300Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a>
301
302</div>
303
304<h3 class="section">1.3 Where do I find out more about any of these chips?</h3>
305
306<p>Most semiconductor companies have comprehensive documentation,
307including complete datasheets, on their websites. Analog Devices,
308Dallas Semiconductor, Maxim, and National Semiconductor have the widest selection
309of sensor chips. Their websites are:
310
311     <ul>
312  <li><a href="http://www.analog.com">http://www.analog.com</a>
313  <li><a href="http://www.dalsemi.com">http://www.dalsemi.com</a>
314  <li><a href="http://www.maxim-ic.com">http://www.maxim-ic.com</a>
315  <li><a href="http://www.national.com">http://www.national.com</a>
316</ul>
317
318   <p>Please see the file <a href="http://www.lm-sensors.org/wiki/UsefulLinks">http://www.lm-sensors.org/wiki/UsefulLinks</a>
319for links to other companies' websites.
320
321<div class="node">
322<p><hr>
323<a name="Basics"></a>
324Next:&nbsp;<a rel="next" accesskey="n" href="#Installation">Installation</a>,
325Previous:&nbsp;<a rel="previous" accesskey="p" href="#Overview">Overview</a>,
326Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
327
328</div>
329
330<h2 class="chapter">2 Sensor and Bus Basics</h2>
331
332<ul class="menu">
333<li><a accesskey="1" href="#Section-2_002e1">Section 2.1</a>:              What sensors are available on my PC?
334<li><a accesskey="2" href="#Section-2_002e2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?
335<li><a accesskey="3" href="#Section-2_002e3">Section 2.3</a>:              Where do I find out more about any of these chips?
336<li><a accesskey="4" href="#Section-2_002e4">Section 2.4</a>:              What sensors are available on my PC?
337<li><a accesskey="5" href="#Section-2_002e5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?
338<li><a accesskey="6" href="#Section-2_002e6">Section 2.6</a>:              Where do I find out more about any of these chips?
339</ul>
340
341<div class="node">
342<p><hr>
343<a name="Section-2.1"></a>
344<a name="Section-2_002e1"></a>
345Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e2">Section 2.2</a>,
346Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
347
348</div>
349
350<h3 class="section">2.1 How are these sensors read?</h3>
351
352<p>Sensor chips reside on either the ISA bus, the SMBus, or both.
353See the file <samp><span class="file">doc/chips/SUMMARY</span></samp> in our package for a list.
354
355   <p>To communicate with chips on the ISA bus, the software uses
356simple I/O reads and writes.
357
358   <p>To communicate with chips on the SMBus, the software must
359use an SMBus interface device, explained below.
360
361<div class="node">
362<p><hr>
363<a name="Section-2.2"></a>
364<a name="Section-2_002e2"></a>
365Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e3">Section 2.3</a>,
366Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e1">Section 2.1</a>,
367Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
368
369</div>
370
371<h3 class="section">2.2 What is the SMBus? And the I2C bus?</h3>
372
373<p>The SMBus is the "System Management Bus".  More specifically, it is a
3742-wire, low-speed serial communication bus used for basic health monitoring
375and hardware management. It is a specific implementation of the more
376general I2C (pronunciation: I-squared-C) bus. In fact, both I2C devices
377and SMBus devices may be connected to the same (I2C) bus.
378
379   <p>The SMBus (or I2C bus) starts at the host controller, used for
380starting transactions on the SMBus.  From the host interface, the
381devices communicated with are the <dfn>slave</dfn> devices.  Each slave device has a
382unique 7-bit address which the host uses to refer to that device.
383
384   <p>For each supported SMBus host, there is a separate kernel module
385which implements the communication protocol with the host. Some SMBus hosts
386really operate on the SMBus level; these hosts can not cope with pure I2C
387devices. Other hosts are in fact I2C hosts: in this case, we implement
388the SMBus protocol in terms of I2C operations. But these hosts can also
389talk to pure I2C devices.
390
391<div class="node">
392<p><hr>
393<a name="Section-2.3"></a>
394<a name="Section-2_002e3"></a>
395Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e4">Section 2.4</a>,
396Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e2">Section 2.2</a>,
397Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
398
399</div>
400
401<h3 class="section">2.3 I don't have an ISA bus!</h3>
402
403<p>We promise, you do, even if you don't have any old ISA slots.
404The "ISA Bus" exists in your computer even if you don't have ISA slots;
405it is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF)
406where many "legacy" functions, such as keyboard and interrupt controllers,
407are found. It isn't necessarily a separate physical bus.
408See the file <samp><span class="file">/proc/ioports</span></samp> for a list of devices living on
409the "ISA Bus" in your system. If you don't like the term "ISA Bus"
410think "I/O Space".
411
412<div class="node">
413<p><hr>
414<a name="Section-2.4"></a>
415<a name="Section-2_002e4"></a>
416Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e5">Section 2.5</a>,
417Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e3">Section 2.3</a>,
418Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
419
420</div>
421
422<h3 class="section">2.4 What sensors do processors have?</h3>
423
424<p>Most new processors contain a thermal diode on the die itself.
425The electical properties of all diodes and transistors vary
426slightly with temperature. The thermal diode is exceptionally accurate
427because it is directly on the die. Newer temperature sensor chips,
428like the Analog Devices ADM1021 and clones, and the Winbond chips,
429have circuitry for measuring the the electrical properties of
430an external diode and converting this data to a temperature.
431Any sensor chip listed in <samp><span class="file">doc/chips/SUMMARY</span></samp> in our package which
432has support for more than one temperature supports external temperature sensing.
433
434   <p>Older motherboards and processors without this feature generally use
435an LM75 placed close to the processor. This is much less accurate.
436
437   <p>The Pentium 2 'boxed' processor usually has an LM75 very close to the
438base of the box. It can be read through the SMBus to report the approximate
439temperature of the processor.  The processor also contains an internal
440temperature sensor (of low accuracy) used as a fail-safe to disable the
441processor in case it gets much too hot (usually around 130 degrees C).  And,
442the Pentium 2 also has a hard-wired signal (VID lines) on it's SEC (single
443edge connector) which indicates what power supply is required to operate the
444processor.
445
446   <p>The P6 (Pentium-Pro) may have an LM75 in or just under the socket.
447P6's also have VID lines.
448
449   <p>Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have
450LM75's under the sockets (depends on the mainboard, and how 'modern' the
451mainboard is).
452
453   <p>The P2 Xeon was the first Intel processor to include the SMBus
454interface on the P2 Xeon SEC.
455
456<div class="node">
457<p><hr>
458<a name="Section-2.5"></a>
459<a name="Section-2_002e5"></a>
460Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e6">Section 2.6</a>,
461Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e4">Section 2.4</a>,
462Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
463
464</div>
465
466<h3 class="section">2.5 How often are the sensor values updated?</h3>
467
468<p>The LM78, and most other sensor chips like it, reads its sensors one
469by one. A complete scanning sweep will take about 1.5 seconds. The LM78 stops
470readings sensors if you try to access it, so if you access it very often
471(by reading sensor values; writing new limits is safe) it will not find the
472time to update its sensor values at all! Fortunately, the kernel module takes
473care not to do this, and only reads new values each 1.5 seconds. If you
474read the values again, you will get the 'old' values again.
475
476<div class="node">
477<p><hr>
478<a name="Section-2.6"></a>
479<a name="Section-2_002e6"></a>
480Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e5">Section 2.5</a>,
481Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a>
482
483</div>
484
485<h3 class="section">2.6 How are alarms triggered?</h3>
486
487<p>It is possible to monitor each sensor and have an alarm go off if
488it crosses some pre-determined limits.  There are two sorts of interrupts
489which can be generated by sensor chips if this happens (it depends a bit on
490the actual chip if both are supported; the LM80, for example, has only
491IRQ interrupts): IRQ interrupts and SMI interrupts.  IRQ stands for
492Interrupt Request and are the interrupt lines you can find in <samp><span class="file">/proc/interrupts</span></samp>.
493SMI stands for System Management Interrupt, and is a special interrupt which
494puts the processor in a secure environment independent of any other things
495running.  SMI is currently not supported by the Linux kernel.  IRQs are
496supported, of course.
497
498   <p>Even if no interrupt is generated, some bits in a status register
499will be set until the register is read the next time. If the alarm condition
500persists after that, the bits will be set on the next scanning sweep, etc.
501
502   <p>Most drivers in our package do not support interrupts at this time.
503
504<div class="node">
505<p><hr>
506<a name="Installation"></a>
507Next:&nbsp;<a rel="next" accesskey="n" href="#Problems">Problems</a>,
508Previous:&nbsp;<a rel="previous" accesskey="p" href="#Basics">Basics</a>,
509Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
510
511</div>
512
513<h2 class="chapter">3 Installation and Management</h2>
514
515<ul class="menu">
516<li><a accesskey="1" href="#Section-3_002e1">Section 3.1</a>:      Why so many modules, and how do I cope with them?
517<li><a accesskey="2" href="#Section-3_002e2">Section 3.2</a>:      How do I know which chips I own?
518<li><a accesskey="3" href="#Section-3_002e3">Section 3.3</a>:      Which modules should I insert?
519<li><a accesskey="4" href="#Section-3_002e4">Section 3.4</a>:      Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>?
520<li><a accesskey="5" href="#Section-3_002e5">Section 3.5</a>:      What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings
521<li><a accesskey="6" href="#Section-3_002e6">Section 3.6</a>:      I get all kinds of weird compilation errors?
522<li><a accesskey="7" href="#Section-3_002e7">Section 3.7</a>:      It still does not compile or patch!
523<li><a accesskey="8" href="#Section-3_002e8">Section 3.8</a>:      <samp><span class="command">make install</span></samp> fails on Mandrake kernels
524<li><a accesskey="9" href="#Section-3_002e9">Section 3.9</a>:      I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules
525<li><a href="#Section-3_002e10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
526</ul>
527
528<div class="node">
529<p><hr>
530<a name="Section-3.1"></a>
531<a name="Section-3_002e1"></a>
532Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e2">Section 3.2</a>,
533Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
534
535</div>
536
537<h3 class="section">3.1 Why so many modules, and how do I cope with them?</h3>
538
539<p>We tried to make this package as modular as possible. This makes it
540easy to add new drivers, and unused drivers will take no precious kernel
541space. On the other hand, it can be a bit confusing at first.
542
543   <p>Here are two simple guidelines:
544     <ul>
545  <li>Run <samp><span class="command">sensors-detect</span></samp> and do what it tells you.
546  <li>Always use <samp><span class="command">modprobe</span></samp>, not <samp><span class="command">insmod</span></samp>.
547</ul>
548
549   <p>Further information is in <samp><span class="file">doc/modules</span></samp>.
550
551   <p><a name="How-do-I-know-which-chips-I-own"></a>
552<div class="node">
553<p><hr>
554<a name="Section-3.2"></a>
555<a name="Section-3_002e2"></a>
556Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e3">Section 3.3</a>,
557Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e1">Section 3.1</a>,
558Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
559
560</div>
561
562<h3 class="section">3.2 How do I know which chips I own?</h3>
563
564<p>We have an excellent program that scans all your hardware.
565It is called <samp><span class="file">sensors-detect</span></samp> and is installed in <samp><span class="file">/usr/local/sbin</span></samp>
566by <samp><span class="command">make install</span></samp>. Just execute this script, and it will tell you.
567
568   <p>Chip detection in the drivers is fairly good. That means that it is
569usually harmless to insert more chip drivers than you need. However, this
570can still lead to problems, so we do not recommend it.
571
572   <p>If sensors-detect didn't find any sensors, either you don't have
573any, or the ones you have, we don't support. (Look at your motherboard
574for candidates, then see <a href="#Help">Help</a>)
575
576   <p><a name="Section-3_002e2_002e1"></a>
577
578<h4 class="subsection">3.2.1 What chips are on motherboard XYZ?</h4>
579
580<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong>
581
582   <p>We have no idea. Here is what you should do:
583     <ol type=1 start=1>
584  <li>Run sensors-detect.
585        </ol>
586
587   <p>If that doesn't work:
588     <ol type=1 start=2>
589<li>Look at your motherboard.
590<li>Check the manufacturer's website or ask their support
591<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website and the
592<a href="http://www.lm-sensors.org/wiki/UsefulLinks">"links"</a>
593page on <a href="http://www.lm-sensors.org">our website</a> some good cross-references.
594        </ol>
595
596   <p><a name="Section-3_002e2_002e2"></a>
597
598<h4 class="subsection">3.2.2 Do you support motherboard XYZ?</h4>
599
600<p>We don't support boards, we support chips. See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.
601
602   <p><a name="Section-3_002e2_002e3"></a>
603
604<h4 class="subsection">3.2.3 Do you support chip XYZ?</h4>
605
606<p>This we have good answers for.
607     <ul>
608<li>Sorted by Manufacturer:   <samp><span class="file">README</span></samp>
609<li>Sorted by Manufacturer:   <a href="http://www.lm-sensors.org/wiki/Devices">http://www.lm-sensors.org/wiki/Devices</a>
610<li>Sorted by Sensor Driver:  <samp><span class="file">doc/chips/SUMMARY</span></samp>
611</ul>
612
613   <p><a name="Section-3_002e2_002e4"></a>
614
615<h4 class="subsection">3.2.4 Anybody working on a driver for chip XYZ?</h4>
616
617<p>Newest Driver Status: <a href="http://www.lm-sensors.org/wiki/Devices">http://www.lm-sensors.org/wiki/Devices</a>
618
619<div class="node">
620<p><hr>
621<a name="Section-3.3"></a>
622<a name="Section-3_002e3"></a>
623Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e4">Section 3.4</a>,
624Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e2">Section 3.2</a>,
625Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
626
627</div>
628
629<h3 class="section">3.3 Which modules should I insert?</h3>
630
631<p><samp><span class="command">sensors-detect</span></samp> will tell you. Take the <samp><span class="command">modprobe</span></samp> lines it
632recommends and paste them into the appropriate <samp><span class="file">/etc/rc.d/xxxx</span></samp> file
633to be executed at startup.
634
635   <p>You need one module for each sensor chip and bus adapter you own;
636if there are sensor chips on the ISA bus, you also need <samp><span class="file">i2c-isa.o</span></samp>.
637for each type of chip you own. That's all. On my computer, I could use the
638following lines:
639     <ul>
640<li><samp><span class="command">modprobe i2c-isa</span></samp>
641<li><samp><span class="command">modprobe i2c-piix4</span></samp>
642<li><samp><span class="command">modprobe lm78</span></samp>
643<li><samp><span class="command">modprobe lm75</span></samp>
644<li><samp><span class="command">modprobe i2c-dev</span></samp>
645<li><samp><span class="command">sensors -s</span></samp>
646</ul>
647
648<div class="node">
649<p><hr>
650<a name="Section-3.4"></a>
651<a name="Section-3_002e4"></a>
652Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e5">Section 3.5</a>,
653Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e3">Section 3.3</a>,
654Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
655
656</div>
657
658<h3 class="section">3.4 Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>?</h3>
659
660<p>Yes, for any applications that use <samp><span class="file">libsensors,</span></samp> including the
661<samp><span class="command">sensors</span></samp> application included in our package.
662It tells libsensors how to translate the values the chip
663measures to real-world values. This is especially important for voltage
664inputs. The default configuration file should usually do the trick.
665It is automatically installed as <samp><span class="file">/etc/sensors.conf</span></samp>, but it will not
666overwrite any existing file with that name.
667
668   <p><a name="Section-3_002e4_002e1"></a>
669
670<h4 class="subsection">3.4.1 The labels for the voltage and temperature readings in <samp><span class="command">sensors</span></samp> are incorrect!</h4>
671
672<p>Every motherboard is different. You can customize the labels
673in the file <samp><span class="file">/etc/sensors.conf</span></samp>. That's why it exists!
674The default labelling (in <samp><span class="file">lib/chips.c</span></samp> and <samp><span class="file">/etc/sensors.conf</span></samp>) is just
675a template.
676
677   <p><a name="Section-3_002e4_002e2"></a>
678
679<h4 class="subsection">3.4.2 The min and max for the readings in <samp><span class="command">sensors</span></samp> are incorrect!</h4>
680
681<p>You can customize them in the file <samp><span class="file">/etc/sensors.conf</span></samp>. See above.
682
683   <p><a name="Section-3_002e4_002e3"></a>
684
685<h4 class="subsection">3.4.3 The min and max settings in <samp><span class="file">/etc/sensors.conf</span></samp> didn't take effect!</h4>
686
687<p>You forgot to run <samp><span class="command">sensors -s</span></samp>. See above.
688
689   <p><a name="Section-3_002e4_002e4"></a>
690
691<h4 class="subsection">3.4.4 One sensor isn't hooked up on my board!</h4>
692
693<p>Use an <samp><span class="command">ignore</span></samp> line in <samp><span class="file">/etc/sensors.conf</span></samp> so it isn't
694displayed in <samp><span class="command">sensors</span></samp>.
695
696   <p><a name="Section-3_002e4_002e5"></a>
697
698<h4 class="subsection">3.4.5 I need help with <samp><span class="file">sensors.conf</span></samp>!</h4>
699
700<p>There is detailed help at the top of that file.
701
702   <p><a name="Section-3_002e4_002e6"></a>
703
704<h4 class="subsection">3.4.6 Do you have a database of <samp><span class="file">sensors.conf</span></samp> entries for specific boards?</h4>
705
706<p>No. Good idea though. If you would like to set one up on your website
707send us mail and we will set up a link to it.
708
709<div class="node">
710<p><hr>
711<a name="Section-3.5"></a>
712<a name="Section-3_002e5"></a>
713Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e6">Section 3.6</a>,
714Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e4">Section 3.4</a>,
715Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
716
717</div>
718
719<h3 class="section">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</h3>
720
721<p>Don't worry about them. The dependency files (which tell which
722files should be recompiled when certain files change) are created
723dynamically. They are not distributed with the package. The <samp><span class="command">make</span></samp> program
724notices they are not there, and warns about that - and the first thing
725it will do is generate them. So all is well.
726
727<div class="node">
728<p><hr>
729<a name="Section-3.6"></a>
730<a name="Section-3_002e6"></a>
731Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e7">Section 3.7</a>,
732Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e5">Section 3.5</a>,
733Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
734
735</div>
736
737<h3 class="section">3.6 I get all kinds of weird compilation errors?</h3>
738
739<p>Check that the correct i2c header files are used. Depending on
740how you installed, they should be under either <samp><span class="file">/usr/local/include</span></samp> or
741<samp><span class="file">/usr/src/linux*/include</span></samp>. Try to edit the <samp><span class="file">Makefile</span></samp> for the other setting.
742
743   <p><a name="Section-3_002e6_002e1"></a>
744
745<h4 class="subsection">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</h4>
746
747     <ul>
748<li>See <a href="#Section-3_002e6">I get all kinds of weird compilation errors</a>, also try <samp><span class="command">make clean</span></samp> in <samp><span class="file">lm_sensors</span></samp>.
749<li>If that doesn't work, try <samp><span class="command">make clean</span></samp> in <samp><span class="file">i2c</span></samp>.
750<li>If that doesn't work, try <samp><span class="command">make clean</span></samp> in the kernel.
751<li>Also make sure <samp><span class="file">/usr/include/linux</span></samp> points to <samp><span class="file">/usr/src/linux/include/linux</span></samp>.
752</ul>
753
754<div class="node">
755<p><hr>
756<a name="Section-3.7"></a>
757<a name="Section-3_002e7"></a>
758Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e8">Section 3.8</a>,
759Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e6">Section 3.6</a>,
760Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
761
762</div>
763
764<h3 class="section">3.7 It still does not compile or patch!</h3>
765
766<p>Have you installed the matching version of the i2c package? Remember,
767compilation is not enough, you also need to install it for the header
768files to be found!
769
770   <p>If you want to patch the kernel, you will have to apply the i2c
771patches first!
772
773<div class="node">
774<p><hr>
775<a name="Section-3.8"></a>
776<a name="Section-3_002e8"></a>
777Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e9">Section 3.9</a>,
778Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e7">Section 3.7</a>,
779Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
780
781</div>
782
783<h3 class="section">3.8 <samp><span class="command">make install</span></samp> fails on Mandrake kernels</h3>
784
785<p>Mandrake uses a non-standard <samp><span class="file">version.h</span></samp> file which confuses our <samp><span class="file">Makefile</span></samp>.
786Edit our <samp><span class="file">Makefile</span></samp> on the <code>MODDIR :=</code> line to hard-code the module directory.
787
788<div class="node">
789<p><hr>
790<a name="Section-3.9"></a>
791<a name="Section-3_002e9"></a>
792Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e10">Section 3.10</a>,
793Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e8">Section 3.8</a>,
794Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
795
796</div>
797
798<h3 class="section">3.9 I get unresolved symbols when I <samp><span class="command">modprobe</span></samp> modules (Red Hat especially)</h3>
799
800<p>Example:
801<pre class="example">     *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o
802     i2c_bit_add_bus_R8c3bc60e
803     i2c_bit_del_bus_R92b18f49
804</pre>
805   <p>You can also run <samp><span class="command">depmod -a -e</span></samp> to see all unresolved symbols.
806
807   <p>These are module versioning problems. Generally you did not compile
808against the kernel you are running. Sometimes the Red Hat source you
809have is not for the kernel you are running.
810You must compile our package against the source for the kernel you
811are running with something like <samp><span class="command">make LINUX=/usr/src/linux-2.4.14</span></samp>.
812
813   <p>Try the following to be sure:
814
815     <ul>
816<li><samp><span class="command">nm --extern MODULE.o</span></samp>
817Filter out the kernel symbols, like <code>kmalloc</code>, <code>printk</code> etc. and note the
818number code behind them, like <code>printk_R1b7d4074</code>. If there is no numeric
819code after them, note this too.
820<li><samp><span class="command">grep SYMBOL /proc/ksyms</span></samp>
821Substitute SYMBOL by the basename of the symbols above, like <code>kmalloc</code>,
822<code>printk</code> etc. Note the number code behind them, or the lack thereof.
823<li>Compare both sets of symbols. Are they the same? If so, the problem
824lies somewhere else. Are they different? If so, you have a module
825versioning problem.
826</ul>
827
828<div class="node">
829<p><hr>
830<a name="Section-3.10"></a>
831<a name="Section-3_002e10"></a>
832Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e9">Section 3.9</a>,
833Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a>
834
835</div>
836
837<h3 class="section">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3>
838
839<p>In some versions of Redhat, an RPM is included to provide i2c support.
840However, this RPM does not place the header files in the kernel directory
841structure.  When you update kernels, they may persist.  To get rid of
842these obsolete header files, at a command prompt:
843
844     <ol type=1 start=1>
845<li><samp><span class="command">rpm -qa | grep i2c</span></samp>
846<li>Look for <samp><span class="file">kernel-i2c,</span></samp> or a similar rpm in the output
847<li>&lt;as root&gt;
848<samp><span class="command">rpm -ev kernel-i2c</span></samp> (or the name of the similar package)
849If this complains about dependencies, you can try adding
850<samp><span class="command">--nodeps</span></samp>, but this *MAY* break something else.  Not likely,
851as you have upgraded kernels, and nothing should be using the
852old i2c stuff anymore anyway.  Just don't use it with abandon.
853<li>Try (in the build directory of <samp><span class="file">lm_sensors)</span></samp>
854     <pre class="example">          <samp><span class="command">make clean</span></samp>
855          <samp><span class="command">make</span></samp>
856     </pre>
857     <li><em>If</em> you still have problems, you may have to replace the include
858paths in the <samp><span class="file">.c/.h</span></samp> files with absolute paths to the header files.
859More of a workaround than a real fix, but at least you can get it
860to work.
861        </ol>
862
863<div class="node">
864<p><hr>
865<a name="Problems"></a>
866Next:&nbsp;<a rel="next" accesskey="n" href="#Help">Help</a>,
867Previous:&nbsp;<a rel="previous" accesskey="p" href="#Installation">Installation</a>,
868Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
869
870</div>
871
872<h2 class="chapter">4 Problems</h2>
873
874<ul class="menu">
875<li><a accesskey="1" href="#Section-4_002e1">Section 4.1</a>:          My fans report exactly half/double their values?
876<li><a accesskey="2" href="#Section-4_002e2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?
877<li><a accesskey="3" href="#Section-4_002e3">Section 4.3</a>:          Why do I have two Vcore readings?
878<li><a accesskey="4" href="#Section-4_002e4">Section 4.4</a>:          How do those ALARMS work?
879<li><a accesskey="5" href="#Section-4_002e5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?
880<li><a accesskey="6" href="#Section-4_002e6">Section 4.6</a>:          Some measurements are way out of range. What happened?
881<li><a accesskey="7" href="#Section-4_002e7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?
882<li><a accesskey="8" href="#Section-4_002e8">Section 4.8</a>:          Sensor are only updated each second or so. Why?
883<li><a accesskey="9" href="#Section-4_002e9">Section 4.9</a>:          It takes a second before reading sensor results. Why?
884<li><a href="#Section-4_002e10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?
885<li><a href="#Section-4_002e11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?
886<li><a href="#Section-4_002e12">Section 4.12</a>:         My BIOS reports a higher CPU temperature than you!
887<li><a href="#Section-4_002e13">Section 4.13</a>:         I read strange values from the raw <samp><span class="file">/proc</span></samp> files!
888<li><a href="#Section-4_002e14">Section 4.14</a>:         How do I set new limits?
889<li><a href="#Section-4_002e15">Section 4.15</a>:         Some sensors are doubly detected?
890<li><a href="#Section-4_002e16">Section 4.16</a>:         I ran sensors-detect, but now I get strange readings?!
891<li><a href="#Section-4_002e17">Section 4.17</a>:         Bad readings from particular chips
892<li><a href="#Section-4_002e18">Section 4.18</a>:         How do I configure two chips (LM87) differently?
893<li><a href="#Section-4_002e19">Section 4.19</a>:         Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!
894<li><a href="#Section-4_002e20">Section 4.20</a>:         Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'
895<li><a href="#Section-4_002e21">Section 4.21</a>:         Sensors says `<samp><span class="samp">No sensors found!</span></samp>'
896<li><a href="#Section-4_002e22">Section 4.22</a>:         Sensors output is not correct!
897<li><a href="#Section-4_002e23">Section 4.23</a>:         What is at I2C address XXX?
898<li><a href="#Section-4_002e24">Section 4.24</a>:         Sensors-detect doesn't work at all
899<li><a href="#Section-4_002e25">Section 4.25</a>:         Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'
900<li><a href="#Section-4_002e26">Section 4.26</a>:         Sensors only gives the name, adapter, and algorithm!
901<li><a href="#Section-4_002e27">Section 4.27</a>:         Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'
902<li><a href="#Section-4_002e28">Section 4.28</a>:         Sensors doesn't find any sensors, just eeproms.
903<li><a href="#Section-4_002e29">Section 4.29</a>:         Inserting modules hangs my board
904<li><a href="#Section-4_002e30">Section 4.30</a>:         Inserting modules slows down my board
905<li><a href="#Section-4_002e31">Section 4.31</a>:         Problems on particular motherboards
906<li><a href="#Section-4_002e32">Section 4.32</a>:         Problems on particular systems
907<li><a href="#Section-4_002e33">Section 4.33</a>:         Problems on 2.6 kernels
908</ul>
909
910<div class="node">
911<p><hr>
912<a name="Section-4.1"></a>
913<a name="Section-4_002e1"></a>
914Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e2">Section 4.2</a>,
915Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
916
917</div>
918
919<h3 class="section">4.1 My fans report exactly half/double their values compared to the BIOS?</h3>
920
921<p>The problem with much of the sensor data is that it is impossible to
922properly interpret some of the readings without knowing what the hardware
923configuration is.  Some fans report one 'tick' each rotation, some report
924two 'ticks' each rotation. It is easy to resolve this through the
925configuration file <samp><span class="file">/etc/sensors.conf</span></samp>:
926
927<pre class="example">     chip lm78-*             # Or whatever chip this relates to
928     compute fan1 2*@,@/2    # This will double the fan1 reading
929                             # -- or --
930     compute fan1 @/2,2*@    # This will halve the fan1 reading
931</pre>
932   <p>See <samp><span class="file">doc/fan-divisors</span></samp> in our package for further information.
933
934   <p><a name="Fans-sometimes_002falways-read-0_0021"></a>
935
936<h4 class="subsection">4.1.1 Fans sometimes/always read 0!!</h4>
937
938<p>You may not have a three-wire fan, which is required.
939
940   <p>You may need to increase the 'fan divisor'. See <samp><span class="file">doc/fan-divisors</span></samp>
941in our package for further information.
942
943   <p><a name="I-doubled-the-fan-divisor-and-the-fan-still-reads-7000"></a>
944
945<h4 class="subsection">4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4>
946
947<p>Believe it or not, doubling the 'fan divisor' will not halve
948the fan reading. You have to add a compute line in <samp><span class="file">/etc/sensors.conf</span></samp>.
949See <a href="#Section-4_002e1">My fans report exactly half/double their values compared to the BIOS</a>,
950and see <samp><span class="file">doc/fan-divisors</span></samp> in our package for further information.
951
952<div class="node">
953<p><hr>
954<a name="Section-4.2"></a>
955<a name="Section-4_002e2"></a>
956Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e3">Section 4.3</a>,
957Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e1">Section 4.1</a>,
958Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
959
960</div>
961
962<h3 class="section">4.2 Why do my two LM75's report "-48 degrees"?</h3>
963
964<p>For starters, those aren't LM75's.  Your mainboard actually has the
965Winbond W83781D which emulates two LM75's, but many systems which use the
966Winbond chip (such as the Asus P2B) don't have the thermo-resisters connected
967to the chip resulting in these strange -48 degree readings.
968
969   <p>In upcoming versions, you will be able to disable non-interesting
970readings.
971
972<div class="node">
973<p><hr>
974<a name="Section-4.3"></a>
975<a name="Section-4_002e3"></a>
976Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e4">Section 4.4</a>,
977Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e2">Section 4.2</a>,
978Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
979
980</div>
981
982<h3 class="section">4.3 Why do I have two Vcore readings, I have only one processor!</h3>
983
984<p>The LM78 has seven voltage sensors. The default way of
985connecting them is used in the configuration file. This includes a VCore2,
986even if you do not have one. You can easily edit the configuration file
987to give it another name, or make this reading disappear using
988an <samp><span class="command">ignore</span></samp> line.
989
990   <p>Note that Vcore2 is often the same as Vcore on motherboards which
991only support one processor. Another possibility is that Vcore2 is not
992connected at all and will not have a valid reading at all.
993A third possibility, is that Vcore2 monitors something
994else, so you should not be too surprised if the values are completely
995different.
996
997<div class="node">
998<p><hr>
999<a name="Section-4.4"></a>
1000<a name="Section-4_002e4"></a>
1001Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e5">Section 4.5</a>,
1002Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e3">Section 4.3</a>,
1003Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1004
1005</div>
1006
1007<h3 class="section">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3>
1008
1009<p>The ALARM indications in <samp><span class="command">sensors</span></samp> are those reported by the
1010sensor chip itself. They are NOT calculated by <samp><span class="command">sensors</span></samp>. <samp><span class="command">sensors</span></samp>
1011simply reads the ALARM bits and reports them.
1012
1013   <p>An ALARM will go off when a minimum or maximum limit is crossed.
1014The ALARM is then latched - that is, it will stay there until the
1015chip's registers are next accessed - which will be the next time
1016you read these values, but not within (usually) 1.5 seconds since the last
1017update.
1018
1019   <p>Reading the registers clears the ALARMS, unless the current
1020value is still out of range.
1021
1022   <p>The purpose of this scheme is to tell you if there has been
1023a problem and report it to the user. Voltage or temperature spikes
1024get detected without having to read the sensor chip hundreds of times
1025a second. The implemetation details depend a bit on the kind of chip.
1026See the specific chip documentation in <samp><span class="file">doc/chips</span></samp> and the
1027chip datasheet for more information.
1028
1029<div class="node">
1030<p><hr>
1031<a name="Section-4.5"></a>
1032<a name="Section-4_002e5"></a>
1033Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e6">Section 4.6</a>,
1034Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e4">Section 4.4</a>,
1035Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1036
1037</div>
1038
1039<h3 class="section">4.5 My voltage readings seem to drift a bit. Is something wrong?</h3>
1040
1041<p>No, probably not. If your motherboard heats up a bit, the sensed
1042voltages will drift a bit. If your power supply is loaded (because a disk
1043gets going, for example), the voltages may get a bit lower. Heavy
1044processor activity, in particular, dramatically increases core voltage
1045supply load which will often cause variation in the other supplies.
1046As long as they stay within a sensible range (say 5% of the nominal value
1047for CPU core voltages, and 10% for other voltages), there is no
1048reason to worry.
1049
1050<div class="node">
1051<p><hr>
1052<a name="Section-4.6"></a>
1053<a name="Section-4_002e6"></a>
1054Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e7">Section 4.7</a>,
1055Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e5">Section 4.5</a>,
1056Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1057
1058</div>
1059
1060<h3 class="section">4.6 Some measurements are way out of range. What happened?</h3>
1061
1062<p>Each module tries to set limits to sensible values on initialization,
1063but a module does not know how a chip is actually connected. This is
1064described in the configuration file, which is not read by kernel modules.
1065So limits can be strange, if the chip is connected in a non-standard way.
1066
1067   <p>Readings can also be strange; there are several reasons for this.
1068Temperature sensors, for example, can simply not be present, even though
1069the chip supports them. Also, it can be that the input is used in a
1070non-standard way. You can use the configuration file to describe how this
1071measurement should be interpreted; see the comments the example file for
1072more information.
1073
1074   <p><a name="g_t_002d5V-and-_002d12V-readings-are-way-out-of-range_0021"></a>
1075
1076<h4 class="subsection">4.6.1 -5V and -12V readings are way out of range!</h4>
1077
1078<p>It's very frequent that negative voltage lines are not wired because
1079motherboard manufacturers don't think they're worth monitoring
1080(they are mostly unused these days). You can just add
1081<samp><span class="command">ignore inN</span></samp> lines to <samp><span class="file">/etc/sensors.conf</span></samp> to hide them.
1082
1083   <p>Another possibility is that these lines are used to monitor different
1084voltages. Only the motherboard manufacturer can tell for sure. Taking
1085a look at what voltage values the BIOS displays may provide valuable
1086hints though.
1087
1088<div class="node">
1089<p><hr>
1090<a name="Section-4.7"></a>
1091<a name="Section-4_002e7"></a>
1092Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e8">Section 4.8</a>,
1093Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e6">Section 4.6</a>,
1094Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1095
1096</div>
1097
1098<h3 class="section">4.7 What are VID lines? Why is the VID reading wrong?</h3>
1099
1100<p>These describe the core voltage for your processor. They are
1101supported for most processors, however they are not always
1102correctly connected to the sensor chip, so the readings may be invalid.
1103A reading of 0V, +3.5V or +2.05V is especially suspect.
1104If this is the case, add a line <samp><span class="command">ignore vid</span></samp> to <samp><span class="file">/etc/sensors.conf</span></samp>,
1105and change the min and max settings for the Processor Core voltage
1106(often in0_min and in0_max) in that file so that they don't depend on vid.
1107
1108   <p>The CPU nominal voltage is computed from VID lines according to a formula
1109that depends on the CPU type. Most chips that report a VID value can be
1110configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4
1111and Athlon). You chose which one you want through <samp><span class="file">/etc/sensors.conf</span></samp>.
1112See <samp><span class="file">doc/vid</span></samp> for more information.
1113
1114<div class="node">
1115<p><hr>
1116<a name="Section-4.8"></a>
1117<a name="Section-4_002e8"></a>
1118Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e9">Section 4.9</a>,
1119Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e7">Section 4.7</a>,
1120Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1121
1122</div>
1123
1124<h3 class="section">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3>
1125
1126<p>If we would read the registers more often, it would not find the
1127time to update them. So we only update our readings once each 1.5 seconds
1128(the actual delay is chip-specific; for some chips, it may not be needed
1129at all).
1130
1131<div class="node">
1132<p><hr>
1133<a name="Section-4.9"></a>
1134<a name="Section-4_002e9"></a>
1135Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e10">Section 4.10</a>,
1136Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e8">Section 4.8</a>,
1137Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1138
1139</div>
1140
1141<h3 class="section">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3>
1142
1143<p>ISA bus access is fast, but SMBus access is really slow. If you have
1144a lot of sensors, it just takes a lot of time to access them. Fortunately,
1145this has almost no impact on the system as a whole, as another job can run
1146while we are waiting for the transaction to finish.
1147
1148<div class="node">
1149<p><hr>
1150<a name="Section-4.10"></a>
1151<a name="Section-4_002e10"></a>
1152Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e11">Section 4.11</a>,
1153Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e9">Section 4.9</a>,
1154Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1155
1156</div>
1157
1158<h3 class="section">4.10 Can I be alerted when an ALARM occurs?</h3>
1159
1160<p>No, you can't; and it may well be never supported.
1161
1162   <p>Almost no mainboard we have encountered have actually connected the
1163IRQ-out pin of sensor chips. That means that we could enable IRQ reporting, but
1164nothing would happen. Also, even if a motherboard has it connected, it is
1165unclear what interrupt number would be triggered. And IRQ lines are a scarce
1166facility, which means that almost nobody would be able to use it anyway.
1167
1168   <p>The SMI interrupt is only available on a few types of chips. It is
1169really a very obscure way to handle interrupts, and supporting it under Linux
1170might be quite hard to do.
1171
1172   <p>Your best bet would be to poll the alarm file with a user-land daemon
1173which alerts you if an alarm is raised. I am not aware of any program which
1174does the job, though you might want to examine one of the graphical monitor
1175programs under X, see <a href="http://www.lm-sensors.org/wiki/UsefulLinks">http://www.lm-sensors.org/wiki/UsefulLinks</a> for addresses.
1176
1177<div class="node">
1178<p><hr>
1179<a name="Section-4.11"></a>
1180<a name="Section-4_002e11"></a>
1181Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e12">Section 4.12</a>,
1182Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e10">Section 4.10</a>,
1183Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1184
1185</div>
1186
1187<h3 class="section">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3>
1188
1189<p>Some chips which mainboard makers connect to the SMBus are not SMBus
1190devices.  An example is the 91xx clock generator chips.  When read, these
1191devices can lock up the SMBus until the next hard reboot.  This is because
1192they have a similar serial interface (like the I2C), but don't conform to
1193Intel's SMBus standard.
1194
1195   <p>Why did they connect these devices to the SMBus if they aren't
1196compatible?  Good question! :')  Actually, these devices may support being
1197written to, but lock things up when they are read.
1198
1199<div class="node">
1200<p><hr>
1201<a name="Section-4.12"></a>
1202<a name="Section-4_002e12"></a>
1203Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e13">Section 4.13</a>,
1204Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e11">Section 4.11</a>,
1205Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1206
1207</div>
1208
1209<h3 class="section">4.12 My BIOS reports a much higher CPU temperature than your modules!</h3>
1210
1211<p>We display the actual temperature of the sensor. This may not be the
1212temperature you are interested in, though.  If a sensor should measure
1213the CPU temperature, it must be in thermal contact with it.  In practice,
1214it may be just somewhere nearby. Your BIOS may correct for this (by adding,
1215for example, thirty degrees to the measured temperature).  The correction
1216factor is regrettably different for each mainboard, so we can not do this
1217in the module itself. You can do it through the configuration file, though:
1218
1219<pre class="example">     chip lm75-*-49                      # Or whatever chip this relates to
1220     label temp "Processor"
1221     compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula
1222</pre>
1223   <p>However, the offset you are introducing might not be necessary. If you
1224tried to have Linux idle temperature and BIOS "idle" temperature match,
1225you may be misguided.
1226We have a Supermicro (370DLE) motherboard and we know
1227that its BIOS has a closed, almost undelayed while(1) loop that
1228keeps the CPU busy all the time. Linux reads 26 degrees idle, BIOS reads
122938 degrees. Linux at full load is in the 35-40 degrees range so this
1230makes sense.
1231
1232<div class="node">
1233<p><hr>
1234<a name="Section-4.13"></a>
1235<a name="Section-4_002e13"></a>
1236Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e14">Section 4.14</a>,
1237Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e12">Section 4.12</a>,
1238Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1239
1240</div>
1241
1242<h3 class="section">4.13 I try to read the raw <samp><span class="file">/proc</span></samp> files, but the values are strange?!?</h3>
1243
1244<p>Remember, these values do not take the configuration file
1245<samp><span class="file">compute</span></samp> lines in account. This is especially obvious for voltage readings
1246(usually called in? or vin?). Use a program linked to libsensors (like
1247the provided <samp><span class="command">sensors</span></samp> program) instead.
1248
1249<div class="node">
1250<p><hr>
1251<a name="Section-4.14"></a>
1252<a name="Section-4_002e14"></a>
1253Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e15">Section 4.15</a>,
1254Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e13">Section 4.13</a>,
1255Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1256
1257</div>
1258
1259<h3 class="section">4.14 How do I set new limits?</h3>
1260
1261<p>Change the limit values in <samp><span class="file">/etc/sensors.conf</span></samp> and then run
1262<samp><span class="command">sensors -s</span></samp>.
1263
1264   <p><a name="I-set-new-limits-and-it-didnt-work"></a>
1265
1266<h4 class="subsection">4.14.1 I set new limits and it didn't work?</h4>
1267
1268<p>You forgot to run <samp><span class="command">sensors -s</span></samp>. Put it in a <samp><span class="file">/etc/rc.d/...</span></samp> file
1269after the modprobe lines to run at startup.
1270
1271<div class="node">
1272<p><hr>
1273<a name="Section-4.15"></a>
1274<a name="Section-4_002e15"></a>
1275Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e16">Section 4.16</a>,
1276Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e14">Section 4.14</a>,
1277Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1278
1279</div>
1280
1281<h3 class="section">4.15 Some sensors are doubly detected?</h3>
1282
1283<p>Yes, this is still a problem. It is partially solved by alias detection
1284and confidence values in sensors-detect, but it is really tough.
1285
1286   <p>Double detections can be caused by two things:
1287sensors can be detected to both the ISA and the SMBus (and if you have
1288loaded the approprate adapter drivers, it will be detected on both), and
1289some chips simulate other chips (the Winbond W83781D simulates LM75 chips
1290on the SMBus, for example). Remove the offending adapter or chip driver, or
1291run sensors-detect and add the <samp><span class="command">ignore=</span></samp> modprobe parameters it suggests.
1292
1293<div class="node">
1294<p><hr>
1295<a name="Section-4.16"></a>
1296<a name="Section-4_002e16"></a>
1297Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e17">Section 4.17</a>,
1298Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e15">Section 4.15</a>,
1299Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1300
1301</div>
1302
1303<h3 class="section">4.16 I ran sensors-detect, but now I get very strange readings?!?</h3>
1304
1305<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards
1306which connect a clock chip to the SMBus. Unfortunately, this clock chip
1307hangs the PIIX4 if it is read (it is an I2C device, but not SMBus compatible).
1308We have found no way of solving this, except for rebooting your computer.
1309Next time when you run sensors-detect, you may want to exclude addresses
13100x69 and/or 0x6a, by entering <kbd>s</kbd> when you are asked whether you want to
1311scan the PIIX4.
1312
1313<div class="node">
1314<p><hr>
1315<a name="Section-4.17"></a>
1316<a name="Section-4_002e17"></a>
1317Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e18">Section 4.18</a>,
1318Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e16">Section 4.16</a>,
1319Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1320
1321</div>
1322
1323<h3 class="section">4.17 Bad readings from particular chips</h3>
1324
1325<p>See below for some particularly troublesome chips.
1326Also be sure and check <samp><span class="file">doc/chips/xxxxx</span></samp> for the particular driver.
1327
1328   <p><a name="Bad-readings-from-the-AS99127F"></a>
1329
1330<h4 class="subsection">4.17.1 Bad readings from the AS99127F!</h4>
1331
1332<p>The Asus AS99127F is a modified version of the Winbond W83781D.
1333Asus will not release a datasheet. The driver was developed by tedious
1334experimentation. We've done the best we can. If you want to make adjustments
1335to the readings please edit <samp><span class="file">/etc/sensors.conf.</span></samp> Please don't ask us to
1336fix the driver. Ask Asus to release a datasheet.
1337
1338   <p><a name="Bad-readings-from-the-VIA-686A"></a>
1339
1340<h4 class="subsection">4.17.2 Bad readings from the VIA 686A!</h4>
1341
1342<p>The Via 686A datasheet is incomplete.
1343Via will not release details. The driver was developed by tedious
1344experimentation. We've done the best we can. If you want to make adjustments
1345to the readings please edit <samp><span class="file">/etc/sensors.conf.</span></samp> Please don't ask us to
1346fix the driver. Ask Via to release a better datasheet.
1347Also, don't forget to <samp><span class="command">modprobe i2c-isa</span></samp>.
1348
1349   <p><a name="Bad-readings-from-the-MTP008"></a>
1350
1351<h4 class="subsection">4.17.3 Bad readings from the MTP008!</h4>
1352
1353<p>The MTP008 has programmable temperature sensor types.
1354If your sensor type does not match the default, you will have to change it.
1355See <samp><span class="file">doc/chips/mtp008</span></samp> for details.
1356Also, MTP008 chips seem to randomly refuse to respond, for
1357unknown reasons. You can see this as 'XX' entries in i2cdump.
1358
1359   <p><a name="Bad-temperature-readings-from-the-SIS5595"></a>
1360
1361<h4 class="subsection">4.17.4 Bad temperature readings from the SIS5595!</h4>
1362
1363<p>This chip can use multiple thermistor types and there are also
1364two different versions of the chip. We are trying to get the driver
1365working better and develop formulas for different thermistors
1366but we aren't there yet. Sorry.
1367Also, many times the chip isn't really a sis5595 but it was
1368misidentified. We are working on improving that too.
1369
1370   <p><a name="Bad-readings-from-a-w8378_005b12_005dd"></a>
1371
1372<h4 class="subsection">4.17.5 Bad readings from a w8378[12]d!</h4>
1373
1374<p>Do you own an ASUS motherboard?  Perhaps your chip is being
1375misidentified.  Look on the motherboard (or at
1376<a href="http://mbm.livewiredev.com">http://mbm.livewiredev.com</a>) for a 'Winbond' or Asus chip.
1377Often the real device is an Asus as99127f. If so, the driver can be
1378forced to recognize the as99127f with
1379<samp><span class="command">force_as99127f=BUS,0x2d</span></samp> where <code>BUS</code> is your i2c bus number.
1380Cat /proc/bus/i2c to see a list of bus numbers.
1381Read the w83781d module documentation (<samp><span class="file">doc/chips/w83781d</span></samp>)
1382for more details.
1383
1384   <p><a name="Bus-hangs-on-Ali-1543-on-Asus-P5A-boards"></a>
1385
1386<h4 class="subsection">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4>
1387
1388<p>The SMBus tends to hang on this board and it seems to get worse
1389at higher temperatures. Use ISA accesses to reliably use the w83781d
1390monitor chip on this board and use the <samp><span class="command">ignore=1,0x2d</span></samp> or similar option
1391to the w83781d module to prevent i2c accesses.
1392
1393   <p><a name="Bad-readings-from-LM75"></a>
1394
1395<h4 class="subsection">4.17.7 Bad readings from LM75!</h4>
1396
1397<p>The LM75 detection is poor and other hardware is often misdetected
1398as an LM75. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.
1399
1400   <p><a name="Bad-readings-from-LM78"></a>
1401
1402<h4 class="subsection">4.17.8 Bad readings from LM78!</h4>
1403
1404<p>The LM78 is no longer manufactured by National Semiconductor.
1405You probably don't have a real LM78 but something similar that we
1406do not recogize or support. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.
1407
1408   <p><a name="Bad-readings-from-LM80"></a>
1409
1410<h4 class="subsection">4.17.9 Bad readings from LM80!</h4>
1411
1412<p>The LM80 detection is poor and other hardware is often misdetected
1413as an LM80. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.
1414
1415<div class="node">
1416<p><hr>
1417<a name="Section-4.18"></a>
1418<a name="Section-4_002e18"></a>
1419Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e19">Section 4.19</a>,
1420Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e17">Section 4.17</a>,
1421Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1422
1423</div>
1424
1425<h3 class="section">4.18 How do I configure two chips (LM87) differently?</h3>
1426
1427<p>There is a SuperMicro board with two LM87's on it that are
1428not hooked up in the same way, so they need different defaults.
1429For example, both CPU temperatures go to one LM87.
1430
1431   <p>Make two different sections in <samp><span class="file">/etc/sensors.conf</span></samp> as follows:
1432<pre class="example">     chip "lm87-i2c-*-2c"
1433         put configuration for the chip at 0x2c here
1434     chip "lm87-i2c-*-2d"
1435         put configuration for the chip at 0x2d here
1436</pre>
1437   <p>There is a commented example in <samp><span class="file">sensors.conf.eg</span></samp> which should
1438be helpful.
1439
1440<div class="node">
1441<p><hr>
1442<a name="Section-4.19"></a>
1443<a name="Section-4_002e19"></a>
1444Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e20">Section 4.20</a>,
1445Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e18">Section 4.18</a>,
1446Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1447
1448</div>
1449
1450<h3 class="section">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</h3>
1451
1452<p>If the problem is a PCI device is not present in <samp><span class="command">lspci</span></samp>, the solution
1453is complex. For the ALI M7101 device, there is a solution which uses the
14542.4 kernel's <samp><span class="command">hotplug</span></samp> facility. See <samp><span class="file">prog/hotplug</span></samp> in our package.
1455For other PCI devices, you can try to modify
1456the m7101 solution in <samp><span class="file">prog/hotplug</span></samp>.
1457
1458   <p>If dmesg says `<samp><span class="samp">try force_addr</span></samp>', see below. Other drivers generally do not
1459support the force_addr parameter. Sorry. Check the documentation
1460for your driver in <samp><span class="file">doc/[chips,busses]</span></samp> and if we don't support it
1461you can send us your request.
1462
1463   <p><a name="Dmesg-says-use-force_005faddr_003d0xaddr_0021-What-address-do-I-use"></a>
1464
1465<h4 class="subsection">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</h4>
1466
1467<p>If the problem is a PCI device whose base address is not set,
1468you may be able to set the address with a force parameter. The via686a
1469and sis5595 chip drivers, and some bus drivers, support the command line
1470<samp><span class="command">modprobe via686a force_addr=0xADDRESS</span></samp> where ADDRESS
1471is the I/O address. You must select an address that is not in use.
1472<samp><span class="command">cat <samp>/proc/ioports</samp></span></samp> to check (carefully) for conflicts. A high number like
14730xf000 is generally safe.
1474
1475<div class="node">
1476<p><hr>
1477<a name="Section-4.20"></a>
1478<a name="Section-4_002e20"></a>
1479Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e21">Section 4.21</a>,
1480Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e19">Section 4.19</a>,
1481Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1482
1483</div>
1484
1485<h3 class="section">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</h3>
1486
1487     <ul>
1488<li>Linux 2.6
1489          <ul>
1490<li>Did you <samp><span class="command">modprobe i2c_sensor</span></samp>? Check <samp><span class="command">lsmod</span></samp>.
1491<li>Do you have sysfs support in your kernel and <samp><span class="file">/sys</span></samp> mounted (is <samp><span class="file">/sys</span></samp> there and populated)?
1492Create /sys with <samp><span class="command">mkdir /sys</span></samp> if needed. Then add the following line to <samp><span class="file">/etc/fstab</span></samp>:
1493          <pre class="example">               sys              /sys             sysfs       default          0   0</pre>
1494          <p>and <samp><span class="command">mount /sys</span></samp>.
1495</ul>
1496     <li>Linux 2.4
1497          <ul>
1498<li>Did you <samp><span class="command">modprobe i2c-proc</span></samp>? Check <samp><span class="command">lsmod</span></samp>.
1499<li>Do you have procfs support in your kernel and <samp><span class="file">/proc</span></samp> mounted (is <samp><span class="file">/proc</span></samp> there and populated)?
1500Create /proc with <samp><span class="command">mkdir /proc</span></samp> if needed. Then add the following line to <samp><span class="file">/etc/fstab</span></samp>:
1501          <pre class="example">               proc             /proc            proc        defaults         0   0</pre>
1502          <p>and <samp><span class="command">mount /proc</span></samp>.
1503</ul>
1504     <li>If you did <samp><span class="command">sensors -s</span></samp>, did you run it as root?
1505</ul>
1506
1507<div class="node">
1508<p><hr>
1509<a name="Section-4.21"></a>
1510<a name="Section-4_002e21"></a>
1511Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e22">Section 4.22</a>,
1512Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e20">Section 4.20</a>,
1513Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1514
1515</div>
1516
1517<h3 class="section">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</h3>
1518
1519     <ul>
1520<li>Did <samp><span class="command">sensors-detect</span></samp> find sensors? (If not see <a href="#Sensors_002ddetect-doesnt-find-any-sensors">Sensors-detect doesnt find any sensors</a>)
1521<li>Did you do what <samp><span class="command">sensors-detect</span></samp> said?
1522<li>Did you <samp><span class="command">modprobe</span></samp> your sensor modules?
1523<li>Did you <samp><span class="command">modprobe</span></samp> your I2C adapter modules?
1524<li>Did you <samp><span class="command">modprobe i2c-isa</span></samp> if you have ISA sensor chips?
1525<li>Check <samp><span class="command">lsmod</span></samp>.
1526</ul>
1527
1528<div class="node">
1529<p><hr>
1530<a name="Section-4.22"></a>
1531<a name="Section-4_002e22"></a>
1532Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e23">Section 4.23</a>,
1533Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e21">Section 4.21</a>,
1534Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1535
1536</div>
1537
1538<h3 class="section">4.22 Sensors output is not correct!</h3>
1539
1540<p>What specifically is the trouble?
1541     <ul>
1542<li>Labels: See <a href="#Section-3_002e4_002e1">The labels for the voltage and temperature readings in sensors are incorrect</a>.
1543<li>Min/max readings: See <a href="#Section-3_002e4_002e2">The min and max for the readings in sensors are incorrect</a>, and See <a href="#Section-3_002e4_002e3">The min and max settings didnt take effect</a>.
1544<li>AS99127F: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.
1545<li>Via 686A: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.
1546<li>Other specific chips: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.
1547<li>No output for a particular sensors chip: See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>.
1548<li>No output at all: See <a href="#Section-4_002e21">Sensors says No sensors found</a>, See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>.
1549<li>Completely bad output for a particular sensor chip: See <a href="#Section-5_002e4">What to do if I read only bogus information</a>.
1550<li>One particular sensor readings:
1551          <ul>
1552<li>Maybe it isn't hooked up? - tell 'sensors' to ignore it. See <a href="#Section-3_002e4_002e4">One sensor isnt hooked up on my board</a>.
1553<li>Maybe it is hooked up differently on your motherboard? - adjust <samp><span class="file">sensors.conf</span></samp> calculation.
1554</ul>
1555     </ul>
1556
1557<div class="node">
1558<p><hr>
1559<a name="Section-4.23"></a>
1560<a name="Section-4_002e23"></a>
1561Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e24">Section 4.24</a>,
1562Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e22">Section 4.22</a>,
1563Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1564
1565</div>
1566
1567<h3 class="section">4.23 What is at I2C address XXX?</h3>
1568
1569<p>In general, we don't know. Start by running <samp><span class="command">sensors-detect</span></samp>.
1570If it doesn't recognize it, try running <samp><span class="command">i2cdump</span></samp>. A partial list
1571of manufacturers' IDs are at the bottom of <samp><span class="file">doc/chips/SUMMARY</span></samp>.
1572
1573   <p><a name="What-is-at-I2C-address-0x69"></a>
1574
1575<h4 class="subsection">4.23.1 What is at I2C address 0x69?</h4>
1576
1577<p>A clock chip. Often, accessing these clock chips in the wrong
1578way will instantly crash your computer. Sensors-detect carefully
1579avoids these chips, and you should do too.  You have been warned.
1580
1581   <p><a name="What-is-at-I2C-addresses-0x50-_002d-0x57"></a>
1582
1583<h4 class="subsection">4.23.2 What is at I2C addresses 0x50 - 0x57?</h4>
1584
1585<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to
1586look at some basic data in <samp><span class="command">sensors</span></samp> or use the program
1587<samp><span class="command">prog/eeprom/decode-dimms.pl</span></samp> to get more information than you ever wanted.
1588
1589   <p><a name="What-is-at-I2C-addresses-0x30-_002d-0x37"></a>
1590
1591<h4 class="subsection">4.23.3 What is at I2C addresses 0x30 - 0x37?</h4>
1592
1593<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs
1594at addresses 0x50 - 0x57. They are the 'software write-protect'
1595registers of the SDRAM Serial Presence Detect EEPROMs.
1596If you try and
1597do a <samp><span class="command">i2cdump</span></samp> on them to read the location, you won't get anything,
1598because they contain a single write-only register.
1599This register can be used to permanently
1600write-protect the contents of the eeprom.
1601
1602<div class="node">
1603<p><hr>
1604<a name="Section-4.24"></a>
1605<a name="Section-4_002e24"></a>
1606Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e25">Section 4.25</a>,
1607Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e23">Section 4.23</a>,
1608Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1609
1610</div>
1611
1612<h3 class="section">4.24 Sensors-detect doesn't work at all</h3>
1613
1614<p>It could be many things. What was the problem? See <a href="#Section-4_002e31">Problems on particular motherboards</a>.
1615
1616   <p><a name="Sensors_002ddetect-says-_0022Couldnt-open-_002fproc_002fbus_002fi2c_003f_0021_003f_0022"></a>
1617
1618<h4 class="subsection">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4>
1619
1620<p>You don't have i2c support in your kernel, or the i2c-core module
1621was not loaded and you did not run sensors-detect as root.
1622
1623   <p><a name="Sensors_002ddetect-says-_0022Cant-open-_002fdev_002fi2c_005b_002d_002f_005d0_0022"></a>
1624
1625<h4 class="subsection">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4>
1626
1627<p>Your <samp><span class="file">/dev/i2c-0,</span></samp> <samp><span class="file">/dev/i2c0</span></samp>, or <samp><span class="file">/dev/i2c/0</span></samp> files do not exist
1628or you did not run <samp><span class="command">sensors-detect</span></samp> as root.
1629Run the script <samp><span class="command">prog/mkdev/mkdev.sh</span></samp> to create the <samp><span class="file">/dev/i2c-x</span></samp> files.
1630Run <samp><span class="command">devfs</span></samp> in the kernel to get the <samp><span class="file">/dev/i2c/x</span></samp> files.
1631
1632   <p><a name="Sensors_002ddetect-doesnt-find-any-sensors"></a>
1633
1634<h4 class="subsection">4.24.3 Sensors-detect doesn't find any sensors!</h4>
1635
1636<p>Either
1637     <ol type=1 start=1>
1638<li>The board doesn't have any sensors.
1639<li>We don't support the sensors on the board.
1640<li>The sensors it has are on an I2C bus connected to an I2C bus adapter that we don't support.
1641<li>You don't have the latest version of lm_sensors.
1642        </ol>
1643
1644   <p>But in any case you should figure out what is on the board:
1645     <ol type=1 start=1>
1646<li>Look at your motherboard.
1647<li>Check the manufacturer's website.
1648<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website.
1649        </ol>
1650
1651   <p>When you know what chips you have, check the
1652<a href="http://www.lm-sensors.org/wiki/Devices">Driver Status</a> web page to
1653see if support has been added for your chip in a later release or in SVN.
1654
1655<div class="node">
1656<p><hr>
1657<a name="Section-4.25"></a>
1658<a name="Section-4_002e25"></a>
1659Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e26">Section 4.26</a>,
1660Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e24">Section 4.24</a>,
1661Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1662
1663</div>
1664
1665<h3 class="section">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</h3>
1666
1667<p>These are errors from the libsensors library in
1668reading the <samp><span class="file">/etc/sensors.conf</span></samp> configuration file. Go to that line
1669number and fix it. If you have a parse error, perhaps you have
1670to put the feature name in double quotes.
1671
1672<div class="node">
1673<p><hr>
1674<a name="Section-4.26"></a>
1675<a name="Section-4_002e26"></a>
1676Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e27">Section 4.27</a>,
1677Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e25">Section 4.25</a>,
1678Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1679
1680</div>
1681
1682<h3 class="section">4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3>
1683
1684<p>If <samp><span class="command">sensors</span></samp> only says this, for example, and doesn't
1685provide any actual data at all:
1686
1687<pre class="example">     it87-isa-0290
1688     Adapter: ISA adapter
1689     Algorithm: ISA algorithm
1690</pre>
1691   <p>Your chip is not currently supported by <samp><span class="command">sensors</span></samp> and so all it
1692does is print out that information. Get the latest release
1693and be sure you are running the <samp><span class="command">sensors</span></samp> program it installed
1694and not some older <samp><span class="command">sensors</span></samp>.
1695
1696<div class="node">
1697<p><hr>
1698<a name="Section-4.27"></a>
1699<a name="Section-4_002e27"></a>
1700Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e28">Section 4.28</a>,
1701Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e26">Section 4.26</a>,
1702Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1703
1704</div>
1705
1706<h3 class="section">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</h3>
1707
1708     <ul>
1709<li>(Linux 2.6) Make sure you are using one of the
1710<a href="http://www.lm-sensors.org/wiki/Kernel2.6">recommended kernel/lm_sensors combination</a>.
1711<li>You have a <samp><span class="file">libsensors</span></samp>/<samp><span class="command">sensors</span></samp> mismatch.
1712<samp><span class="command">sensors</span></samp> is unable to
1713get a data entry from <samp><span class="file">libsensors</span></samp>. You probably have an
1714old <samp><span class="file">libsensors</span></samp> in your <samp><span class="file">/etc/ld.so.conf</span></samp> path.
1715Make sure you did (as root) a <samp><span class="command">make install</span></samp> (Linux 2.4) or
1716<samp><span class="command">make user_install</span></samp> (Linux 2.6) followed by a <samp><span class="command">ldconfig</span></samp>.
1717Then check the output of <samp><span class="command">ldconfig -v | grep libsensors</span></samp> to
1718verify that there is only ONE <samp><span class="file">libsensors</span></samp> entry and that it matches
1719the <samp><span class="file">libsensors</span></samp> that was built in the <samp><span class="file">lib/</span></samp> directory in <samp><span class="file">lm_sensors2</span></samp>.
1720</ul>
1721
1722<div class="node">
1723<p><hr>
1724<a name="Section-4.28"></a>
1725<a name="Section-4_002e28"></a>
1726Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e29">Section 4.29</a>,
1727Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e27">Section 4.27</a>,
1728Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1729
1730</div>
1731
1732<h3 class="section">4.28 Sensors doesn't find any sensors, just eeproms.</h3>
1733
1734<p>See <a href="#Section-4_002e24">Sensors-detect doesnt work at all</a>, if <samp><span class="command">sensors-detect</span></samp> failed to find any sensors.
1735
1736   <p>If <samp><span class="command">sensors-detect</span></samp> did find sensors, did you insert your modules? For chips on the ISA
1737bus, did you insert i2c-isa?
1738
1739   <p>See <a href="#Section-5_002e2">What to do if a module wont insert</a>, if the modules didn't insert,
1740also <a href="#Section-4_002e21">Sensors says No sensors found</a>.
1741
1742<div class="node">
1743<p><hr>
1744<a name="Section-4.29"></a>
1745<a name="Section-4_002e29"></a>
1746Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e30">Section 4.30</a>,
1747Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e28">Section 4.28</a>,
1748Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1749
1750</div>
1751
1752<h3 class="section">4.29 Inserting modules hangs my board</h3>
1753
1754<p>There are several possible causes:
1755     <ol type=1 start=1>
1756<li>Bus driver problems. Insert the bus driver first, before you have inserted any chip drivers, to verify.
1757<li>Wrong chip driver. Verify that you have a chip supported by the chip driver, see <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.
1758<li>The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS.  Try the parameter <samp><span class="command">init=0</span></samp> for the w83781d driver; this is the only driver supporting this parameter.
1759<li>Some chips on the bus don't like to be probed at all.  After inserting the bus driver (but not the chip drivers), run <samp><span class="command">i2cdetect</span></samp> on the bus, then <samp><span class="command">i2cdump</span></samp> on each address responding to <samp><span class="command">i2cdetect</span></samp>. This may find the culprit.  Do not <samp><span class="command">i2cdump address 0x69</span></samp>, the clock chip.
1760<li>The chip driver is incorrectly finding a second chip on the bus and is accessing it. For example, with the Tyan 2688 with a w83781d at 0x29, use <samp><span class="command">modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f</span></samp> to prevent access to other addresses. (<samp><span class="command">init=0</span></samp> also req'd for the Tyan 2688).
1761        </ol>
1762
1763<div class="node">
1764<p><hr>
1765<a name="Section-4.30"></a>
1766<a name="Section-4_002e30"></a>
1767Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e31">Section 4.31</a>,
1768Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e29">Section 4.29</a>,
1769Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1770
1771</div>
1772
1773<h3 class="section">4.30 Inserting modules slows down my board</h3>
1774
1775<p>Generally this is caused by an overtemperature alarm output from
1776the sensor chip. This triggers hardware on the board which
1777automatically slows down the CPU clock. Be sure that your
1778temperature limits are above the temperature reading. Put
1779the new limits in <samp><span class="file">/etc/sensors.conf</span></samp> and run <samp><span class="command">sensors -s</span></samp>.
1780
1781<div class="node">
1782<p><hr>
1783<a name="Section-4.31"></a>
1784<a name="Section-4_002e31"></a>
1785Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e32">Section 4.32</a>,
1786Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e30">Section 4.30</a>,
1787Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1788
1789</div>
1790
1791<h3 class="section">4.31 Problems on particular motherboards</h3>
1792
1793<p>The following boards have unique problems and solutions.
1794
1795   <p><a name="Asus-P4B"></a>
1796
1797<h4 class="subsection">4.31.1 Asus P4B</h4>
1798
1799<p>See <samp><span class="file">prog/hotplug/README.p4b</span></samp> if your SMBus master is not found.
1800
1801   <p><a name="Tyan-2460-2462"></a>
1802
1803<h4 class="subsection">4.31.2 Tyan 2460, 2462</h4>
1804
1805<p>See support tickets 805, 765, 781, 812, 813, and 867 for information.
1806
1807   <p><a name="Tyan-2466"></a>
1808
1809<h4 class="subsection">4.31.3 Tyan 2466</h4>
1810
1811<p>See support tickets 941, 840, and 841 for information.
1812
1813   <p><a name="Tyan-2688"></a>
1814
1815<h4 class="subsection">4.31.4 Tyan 2688</h4>
1816
1817<p>For board hangs, see support ticket 721 for information.
1818Also <a href="#Section-4_002e29">Inserting modules hangs my board</a>.
1819
1820<div class="node">
1821<p><hr>
1822<a name="Section-4.32"></a>
1823<a name="Section-4_002e32"></a>
1824Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e33">Section 4.33</a>,
1825Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e31">Section 4.31</a>,
1826Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1827
1828</div>
1829
1830<h3 class="section">4.32 Problems on particular systems</h3>
1831
1832<p>For IBM systems, see <samp><span class="file">README.thinkpad</span></samp>.
1833
1834<div class="node">
1835<p><hr>
1836<a name="Section-4.33"></a>
1837<a name="Section-4_002e33"></a>
1838Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e32">Section 4.32</a>,
1839Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a>
1840
1841</div>
1842
1843<h3 class="section">4.33 Problems on 2.6 kernels</h3>
1844
1845<p>Not all drivers have been ported to 2.6. If your favorite driver is not
1846in 2.6, the reason is that nobody has ported it, or the ported code did
1847not get a proper review yet.
1848If you would like to port the driver, see the file
1849Documentation/i2c/porting-clients in the 2.6 kernel tree for help,
1850then send us the ported driver when you are done.
1851
1852<h4 class="subsection">4.33.1 i2c-viapro and via686a</h4>
1853
1854<p>Until kernel 2.6.11, there was a PCI resource conflict between
1855i2c-viapro (the SMBus driver for VIA bridges) and via686a (the integrated
1856sensors driver for VIA bridges). This caused the second loaded driver to
1857silently fail working. So do not load both i2c-viapro and via686a together
1858unless you have a recent kernel.
1859
1860<h4 class="subsection">4.33.2 Where are my EEPROMs?</h4>
1861
1862<p>The 2.6.14-rc1 kernel introduced the hwmon class, which groups all
1863hardware monitoring drivers in a logical way. The goal was to help
1864libsensors grab the relevant sensors information in /sys. In particular:
1865     <ul>
1866<li>libsensors will no more need to know about the underlying bus types
1867(I2C/SMBus, ISA or other);
1868<li>libsensors will no more list non-hardware monitoring chips.
1869</ul>
1870   This explains why EEPROMs are no more displayed by <samp><span class="command">sensors</span></samp>:
1871they are no hardware monitoring chips. The medium term plan is to drop
1872eeprom support for all Linux 2.6 kernels, as it didn't fit well in
1873the library code in the first place.
1874
1875   <p>Note that you can still obtain information about your EEPROMs by using
1876the dedicated perl scripts in <samp><span class="file">prog/eeprom</span></samp>: <samp><span class="command">ddcmon</span></samp>,
1877<samp><span class="command">decode-dimms.pl</span></samp>, <samp><span class="command">decode-edid.pl</span></samp> and
1878<samp><span class="command">decode-vaio.pl</span></samp>.
1879
1880<div class="node">
1881<p><hr>
1882<a name="Help"></a>
1883Next:&nbsp;<a rel="next" accesskey="n" href="#Contribute">Contribute</a>,
1884Previous:&nbsp;<a rel="previous" accesskey="p" href="#Problems">Problems</a>,
1885Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
1886
1887</div>
1888
1889<h2 class="chapter">5 How to Ask for Help</h2>
1890
1891<ul class="menu">
1892<li><a accesskey="1" href="#Section-5_002e1">Section 5.1</a>:   What to send us when asking for help
1893<li><a accesskey="2" href="#Section-5_002e2">Section 5.2</a>:   What to do if a module won't insert?
1894<li><a accesskey="3" href="#Section-5_002e3">Section 5.3</a>:   What to do if it inserts, but nothing happens?
1895<li><a accesskey="4" href="#Section-5_002e4">Section 5.4</a>:   What to do if I read only bogus information?
1896<li><a accesskey="5" href="#Section-5_002e5">Section 5.5</a>:   What to do if you have other problems?
1897<li><a accesskey="6" href="#Section-5_002e6">Section 5.6</a>:   What if it just works like a charm?
1898<li><a accesskey="7" href="#Section-5_002e7">Section 5.7</a>:   How do I update a ticket?
1899<li><a accesskey="8" href="#Section-5_002e8">Section 5.8</a>:   How do I follow up on a ticket?
1900<li><a accesskey="9" href="#Section-5_002e9">Section 5.9</a>:   Why did you decide not to support undocumented chips?
1901</ul>
1902
1903<div class="node">
1904<p><hr>
1905<a name="Section-5.1"></a>
1906<a name="Section-5_002e1"></a>
1907Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e2">Section 5.2</a>,
1908Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
1909
1910</div>
1911
1912<h3 class="section">5.1 What to send us when asking for help</h3>
1913
1914<p>We are always willing to answer questions if things don't work out.
1915Post your question to our <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">discussion list</a>,
1916and not the individual authors,
1917unless you have something private to say.
1918
1919   <p>Instead of using email, you can also use the web-based support
1920area, at <a href="http://www.lm-sensors.org/wiki/FeedbackAndSupport">http://www.lm-sensors.org/wiki/FeedbackAndSupport</a>. You will be helped
1921just as fast, and others may profit from the answer too. You will be
1922emailed automatically when your question has been answered.
1923
1924   <p>Here's what you should send us:
1925
1926     <ul>
1927<li>The dmesg or syslog output if applicable
1928<li>The output of (as root) <samp><span class="command">prog/detect/sensors-detect</span></samp>
1929<li>The output of <samp><span class="command">lsmod</span></samp>
1930<li>If a PCI chip problem:
1931          <ul>
1932<li>The output of <samp><span class="command">lspci -n</span></samp>
1933</ul>
1934     <li>If an I2C sensor chip problem:
1935          <ul>
1936<li>The output of (as root) <samp><span class="command">prog/detect/i2cdetect X</span></samp>
1937where X = the bus number (run <samp><span class="command">i2cdetect</span></samp> with no arguments to list the busses)
1938(please send this only if it's not all `<samp><span class="samp">XX</span></samp>')
1939<li>The output of (as root) <samp><span class="command">prog/dump/i2cdump X 0xXX</span></samp>
1940where XX = the address of each chip you see in the output of <samp><span class="command">i2cdetect</span></samp>. (run once for each chip)
1941(please send this only if it's not all `<samp><span class="samp">ff</span></samp>')
1942</ul>
1943     <li>If an ISA sensor chip problem:
1944          <ul>
1945<li>The output of (as root) <samp><span class="command">prog/dump/isadump 0x295 0x296</span></samp> (only if it's not all `<samp><span class="samp">XX</span></samp>')
1946</ul>
1947     <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard)
1948<li>Motherboard type
1949<li>Sensors version
1950<li>Kernel version
1951</ul>
1952
1953<div class="node">
1954<p><hr>
1955<a name="Section-5.2"></a>
1956<a name="Section-5_002e2"></a>
1957Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e3">Section 5.3</a>,
1958Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e1">Section 5.1</a>,
1959Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
1960
1961</div>
1962
1963<h3 class="section">5.2 What to do if a module won't insert?</h3>
1964
1965<p>Did you use <samp><span class="command">modprobe</span></samp> instead of <samp><span class="command">insmod</span></samp>??? Don't use insmod.
1966
1967   <p>Were there unresolved symbols? Did you run <samp><span class="command">depmod -a</span></samp>? Run
1968<samp><span class="command">depmod -a -e</span></samp> to see where the symbol problem is.
1969
1970   <p>ALWAYS inspect the output of <samp><span class="command">dmesg</span></samp>. That's where the error
1971messages come out!!! Don't rely on the generic message from <samp><span class="command">modprobe</span></samp>.
1972If you still can't figure it out, send us the information
1973listed above.
1974
1975<div class="node">
1976<p><hr>
1977<a name="Section-5.3"></a>
1978<a name="Section-5_002e3"></a>
1979Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e4">Section 5.4</a>,
1980Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e2">Section 5.2</a>,
1981Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
1982
1983</div>
1984
1985<h3 class="section">5.3 What to do if it inserts, but nothing happens?</h3>
1986
1987<p>For an ISA sensor chip, did you also <samp><span class="command">modprobe i2c-isa</span></samp>? It must be inserted.
1988
1989   <p>For an I2C sensor chip, did you also <samp><span class="command">modprobe i2c-xxx</span></samp> where xxx is your
1990I2C bus adapter? It must be inserted.
1991
1992   <p>Always inspect the output of <samp><span class="command">dmesg</span></samp>. That's where the error
1993messages come out. If you still can't figure it out, send us the information
1994listed above.
1995
1996<div class="node">
1997<p><hr>
1998<a name="Section-5.4"></a>
1999<a name="Section-5_002e4"></a>
2000Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e5">Section 5.5</a>,
2001Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e3">Section 5.3</a>,
2002Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2003
2004</div>
2005
2006<h3 class="section">5.4 What to do if I read only bogus information?</h3>
2007
2008<p>It may be that this was a mis-detection: the chip may not be
2009present. If you are convinced there is something wrong, verify that you
2010indeed have the devices on your motherboard that you think you do.
2011Look at the motherboard and make sure. If you are still stuck,
2012please send us the usual information (see <a href="#Help">Help</a>)
2013
2014<div class="node">
2015<p><hr>
2016<a name="Section-5.5"></a>
2017<a name="Section-5_002e5"></a>
2018Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e6">Section 5.6</a>,
2019Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e4">Section 5.4</a>,
2020Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2021
2022</div>
2023
2024<h3 class="section">5.5 What to do if you have other problems?</h3>
2025
2026<p>Again, send the output listed above.
2027
2028<div class="node">
2029<p><hr>
2030<a name="Section-5.6"></a>
2031<a name="Section-5_002e6"></a>
2032Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e7">Section 5.7</a>,
2033Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e5">Section 5.5</a>,
2034Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2035
2036</div>
2037
2038<h3 class="section">5.6 What if it just works like a charm?</h3>
2039
2040<p>Drop us a mail if you feel like it, mentioning the mainboard and
2041detected chip type. That way, we have some positive feedback, too!
2042
2043<div class="node">
2044<p><hr>
2045<a name="Section-5.7"></a>
2046<a name="Section-5_002e7"></a>
2047Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e8">Section 5.8</a>,
2048Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e6">Section 5.6</a>,
2049Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2050
2051</div>
2052
2053<h3 class="section">5.7 How do I update a ticket?</h3>
2054
2055<p>You can't. Only developers can. Follow up by emailing us
2056and reference your ticket number
2057in the subject. Please don't enter a new ticket with
2058follow-up information, email us instead. Thanks.
2059
2060<div class="node">
2061<p><hr>
2062<a name="Section-5.8"></a>
2063<a name="Section-5_002e8"></a>
2064Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e9">Section 5.9</a>,
2065Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e7">Section 5.7</a>,
2066Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2067
2068</div>
2069
2070<h3 class="section">5.8 How do I follow up on a ticket?</h3>
2071
2072<p>Follow up by emailing us
2073and reference your ticket number in the subject.
2074
2075<div class="node">
2076<p><hr>
2077<a name="Section-5.9"></a>
2078<a name="Section-5_002e9"></a>
2079Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e8">Section 5.8</a>,
2080Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a>
2081
2082</div>
2083
2084<h3 class="section">5.9 Why did you decide not to support undocumented chips?</h3>
2085
2086<p>There are several reasons why we are generally not interested in writing
2087drivers for undocumented chips:
2088
2089     <ul>
2090<li>Writing a driver without a datasheet is much harder, as you have to
2091guess most things. Remember that, most of the time, we write drivers for fun
2092and for free, so there is no reason we would write a driver in conditions
2093that promise more pain than fun.
2094<li>If we hit a problem, we are certain never to get any support from the
2095chip manufacturer. This means that we may spend days on code which will
2096finally never work.
2097<li>There are several chips out there which are fully documented and lack
2098a driver. This is natural for us to give these the priority when we
2099finally have some spare time to spend on driver coding.
2100<li>Hardware monitoring chips are not toys. Misprogramming them can
2101result in data loss or hardware breakage. This is obviously more likely
2102to happen with undocumented chips. This is a responsability we do not
2103want to endorse (the GPL is pretty clear than we are not legally
2104liable, but still).
2105</ul>
2106
2107   <p>There are also several reasons why we do not want to support such drivers,
2108even if they were written by other people:
2109
2110     <ul>
2111<li>Problems are much more likely to happen with such drivers.
2112This means increased needs of support. User support if very
2113time-consuming and we are usually short of time.
2114<li>Support should be done by the driver author (as only him/her knows
2115the driver and chip) but in the reality of facts, people will always ask
2116us for help if the driver is part of our package. Redirecting all user
2117requests to the driver's author manually is boring.
2118<li>The lack of datasheet usually results in an original driver which
2119works relatively fine for its author, but will happen not to work
2120completely for other users. This means that the driver will need many
2121more additions and fixes than other drivers do, resulting in an increased
2122maitainance workload, which we can hardly afford. Of course this too should
2123be handled by the original driver author, but we never know whether he/she
2124will actually do the work.
2125</ul>
2126
2127   <p>Lastly, there are other considerations, some of which are deliberately
2128political:
2129
2130     <ul>
2131<li>We do not want to trick hardware buyers into thinking that a chip is
2132fully supported under Linux when in fact it is only partly supported by a
2133driver which was written without a datasheet. Clearly stating that such
2134chips are not supported makes it much easier for anyone who really needs
2135fully working hardware monitoring under Linux to avoid motherboards with
2136these partly supported chips.
2137<li>Drivers written without a datasheet are a pain for developers and
2138users, but are a complete win for the manufacturers of these chips:
2139they don't have to write the driver, they don't have to help us,
2140they don't have to support the users, and they still sell their
2141hardware. We do not want to encourage such a selfish behavior.
2142</ul>
2143
2144   <p>That being said, authors of such drivers can still submit their code to
2145the Linux kernel folks for inclusion into Linux 2.6. Their driver may be
2146accepted there, under conditions.
2147
2148   <p>If such a driver is ever accepted into the Linux 2.6 tree, and someone
2149provides a patch to libsensors and/or sensors to add support for this
2150driver, we will apply it. This generic code is unlikely to cause trouble.
2151
2152<div class="node">
2153<p><hr>
2154<a name="Contribute"></a>
2155Next:&nbsp;<a rel="next" accesskey="n" href="#Document-Revisions">Document Revisions</a>,
2156Previous:&nbsp;<a rel="previous" accesskey="p" href="#Help">Help</a>,
2157Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
2158
2159</div>
2160
2161<h2 class="chapter">6 How to Contribute</h2>
2162
2163<ul class="menu">
2164<li><a accesskey="1" href="#Section-6_002e1">Section 6.1</a>:   How to write a driver
2165<li><a accesskey="2" href="#Section-6_002e2">Section 6.2</a>:   How to get SVN access
2166<li><a accesskey="3" href="#Section-6_002e3">Section 6.3</a>:   How to donate hardware to the project
2167<li><a accesskey="4" href="#Section-6_002e4">Section 6.4</a>:   How to join the project mailing list
2168<li><a accesskey="5" href="#Section-6_002e5">Section 6.5</a>:   How to access mailing list archives
2169<li><a accesskey="6" href="#Section-6_002e6">Section 6.6</a>:   How to submit a patch
2170<li><a accesskey="7" href="#Section-6_002e7">Section 6.7</a>:   How to REALLY help
2171<li><a accesskey="8" href="#Section-6_002e8">Section 6.8</a>:   How to get release announcements
2172</ul>
2173
2174<div class="node">
2175<p><hr>
2176<a name="Section-6.1"></a>
2177<a name="Section-6_002e1"></a>
2178Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e2">Section 6.2</a>,
2179Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2180
2181</div>
2182
2183<h3 class="section">6.1 How to write a driver</h3>
2184
2185<p>See <samp><span class="file">doc/developers/new_drivers</span></samp> in our package for instructions.
2186
2187<div class="node">
2188<p><hr>
2189<a name="Section-6.2"></a>
2190<a name="Section-6_002e2"></a>
2191Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e3">Section 6.3</a>,
2192Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e1">Section 6.1</a>,
2193Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2194
2195</div>
2196
2197<h3 class="section">6.2 How to get SVN access</h3>
2198
2199<p>For anonymous SVN read access, see the instructions on our
2200<a href="http://www.lm-sensors.org/wiki/Download">download page</a>.
2201
2202   <p>For write access, please contact us.
2203
2204<div class="node">
2205<p><hr>
2206<a name="Section-6.3"></a>
2207<a name="Section-6_002e3"></a>
2208Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e4">Section 6.4</a>,
2209Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e2">Section 6.2</a>,
2210Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2211
2212</div>
2213
2214<h3 class="section">6.3 How to donate hardware to the project</h3>
2215
2216<p><a href="http://www.lm-sensors.org/wiki/FeedbackAndSupport">Contact us</a>.
2217
2218<div class="node">
2219<p><hr>
2220<a name="Section-6.4"></a>
2221<a name="Section-6_002e4"></a>
2222Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e5">Section 6.5</a>,
2223Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e3">Section 6.3</a>,
2224Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2225
2226</div>
2227
2228<h3 class="section">6.4 How to join the project mailing lists</h3>
2229
2230<p>There are two lists you can subscribe to:
2231
2232     <ul>
2233<li>A <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">general discussion list</a>,
2234meant for both development and user support. You do not need to be subscribed to post.
2235<li>A <a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors-commit">CVS commits list</a>,
2236for watching the changes made to the CVS repositories. This list is read-only.
2237</ul>
2238
2239<div class="node">
2240<p><hr>
2241<a name="Section-6.5"></a>
2242<a name="Section-6_002e5"></a>
2243Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e6">Section 6.6</a>,
2244Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e4">Section 6.4</a>,
2245Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2246
2247</div>
2248
2249<h3 class="section">6.5 How to access mailing list archives</h3>
2250
2251<p>The primary mailing list archive is at:
2252<a href="http://lists.lm-sensors.org/pipermail/lm-sensors/">http://lists.lm-sensors.org/pipermail/lm-sensors/</a>.
2253It contains messages since October 28, 2001.
2254
2255   <p>There is another mailing list archive at:
2256<a href="http://news.gmane.org/gmane.linux.drivers.sensors">http://news.gmane.org/gmane.linux.drivers.sensors</a>.
2257It contains messages since December 31, 2004.
2258This archive may also be accessed via a news reader:
2259<a href="nntp://news.gmane.org/gmane.linux.drivers.sensors">nntp://news.gmane.org/gmane.linux.drivers.sensors</a>
2260and RSS:
2261<a href="http://rss.gmane.org/gmane.linux.drivers.sensors">http://rss.gmane.org/gmane.linux.drivers.sensors</a>.
2262
2263   <p>And last there is a legacy archive at:
2264<a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a>.
2265It contains messages from October 28, 2001 through May 16, 2005.
2266
2267<div class="node">
2268<p><hr>
2269<a name="Section-6.6"></a>
2270<a name="Section-6_002e6"></a>
2271Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e7">Section 6.7</a>,
2272Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e5">Section 6.5</a>,
2273Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2274
2275</div>
2276
2277<h3 class="section">6.6 How to submit a patch</h3>
2278
2279<p>Check out the latest from CVS, then copy the directory to another
2280directory, and make your changes. Generate the diff with
2281<samp><span class="command">diff -u2 -r DIR1 DIR2</span></samp>. Or you can generate the diff in CVS with
2282<samp><span class="command">cvs diff -u2</span></samp>. Send us the patch in an email and tell us what it does.
2283
2284<div class="node">
2285<p><hr>
2286<a name="Section-6.7"></a>
2287<a name="Section-6_002e7"></a>
2288Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e8">Section 6.8</a>,
2289Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e6">Section 6.6</a>,
2290Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2291
2292</div>
2293
2294<h3 class="section">6.7 How to REALLY help</h3>
2295
2296<p>Believe it or not, what we really need help with are:
2297     <ul>
2298<li>Answering email
2299<li>Answering support tickets
2300<li>Porting drivers to Linux 2.6
2301<li>Creating a sensors.conf database
2302<li>Reviewing patches
2303</ul>
2304
2305   <p>If you are willing to help, simply join our
2306<a href="http://lists.lm-sensors.org/mailman/listinfo/lm-sensors">discussion list</a>,
2307and we'll help you help us.
2308
2309<div class="node">
2310<p><hr>
2311<a name="Section-6.8"></a>
2312<a name="Section-6_002e8"></a>
2313Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e7">Section 6.7</a>,
2314Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a>
2315
2316</div>
2317
2318<h3 class="section">6.8 How to get release announcements</h3>
2319
2320<p>We don't have a separate release announcement mailing list;
2321however, we put all our releases on freshmeat: <a href="http://freshmeat.net">http://freshmeat.net</a>
2322and you can register on our freshmeat project page  <a href="http://freshmeat.net/projects/lm_sensors">http://freshmeat.net/projects/lm_sensors</a>
2323to 'subscribe to new releases' and then freshmeat
2324will email you announcement.
2325
2326<div class="node">
2327<p><hr>
2328<a name="Document-Revisions"></a>
2329Previous:&nbsp;<a rel="previous" accesskey="p" href="#Contribute">Contribute</a>,
2330Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
2331
2332</div>
2333
2334<h2 class="appendix">Appendix A Revision History of This Document</h2>
2335
2336     <ul>
2337<li>Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
2338<li>Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips),
2339        removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
2340<li>Rev 2.16 (JD) Added 4.33.2, 2005-09-06
2341<li>Rev 2.15 (JD) Updates, including mailing-list change, 2005-05-21
2342<li>Rev 2.14 (MDS) Updated 4.12, 2004-11-26
2343<li>Rev 2.13 (JD) Added 4.6.1, updated 4.7, 2004-06-23
2344<li>Rev 2.12 (JD) Updated 4.27, 2004-04-11
2345<li>Rev 2.11 (JD) Various updates, 2004-01-18
2346<li>Rev 2.10 (MDS) Various updates, 2004-01-03
2347<li>Rev 2.9 (CP) Converted to Gnu texinfo format, 2002-09-10
2348<li>Rev 2.8 (MDS) Minor updates 2002-07-10, released with lm_sensors 2.6.4
2349<li>Rev 2.7 (MDS) Minor updates 2002-04-25
2350<li>Rev 2.6 (MDS) Minor updates 2002-01-15, released with lm_sensors 2.6.3
2351<li>Rev 2.5 (MDS) Minor updates 2001-11-11, released with lm_sensors 2.6.2
2352<li>Rev 2.4 (MDS) Minor updates 2001-07-22
2353<li>Rev 2.3 (MDS) General update, 2001-02-24, released with lm_sensors 2.6.0.
2354<li>Rev 2.2 (Frodo) Corrections for lm_sensors 2.4, 1999-09-20
2355<li>Rev 2.1 (Frodo) Corrections for lm_sensors 2.2, 1999-01-12
2356<li>Rev 2.0 (Frodo) Major revision for lm_sensors 2.1, 1998-12-29
2357<li>Rev 1.10 (Frodo) Modified 3.8, updated some other things, 1998-09-24
2358<li>Rev 1.9 (Frodo) Added 3.15, 1998-09-06
2359<li>Rev 1.8 (Frodo) Added 3.14, 1998-09-05
2360<li>Rev 1.7 (Phil) Added 3.13 and some other minor changes, 1998-09-01
2361<li>Rev 1.6 (Frodo) Added 4, 4.1, 4.2, 4.3, 4.4, 4.5, 1998-09-01
2362<li>Rev 1.5 (Frodo) Added 2.3, 2.4, 3.9, 3.10, 3.11, 1998-08-26
2363<li>Rev 1.4 (Frodo) Added some more Winbond information, and 3.5-3.8, 1998-08-17
2364<li>Rev 1.3 (Phil) Added info on the Winbond chip, 1998-08-16
2365<li>Rev 1.2 (Frodo) Adapation, 1998-08-10
2366<li>Rev 1.1 (Phil) Modifications, 1998-08-09
2367<li>Rev 1.0 (Phil) First version, 1998-08-03
2368</ul>
2369
2370</body></html>
2371
Note: See TracBrowser for help on using the browser.