Context Navigation

lm_sensors-FAQ.html @ 4865

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

Note: See TracBrowser for help on using the browser.

Context Navigation

root/lm-sensors/branches/lm-sensors-3.0.0/doc/lm_sensors-FAQ.html @ 4865

Download in other formats: