Context Navigation

← Previous Changeset
Next Changeset →

Changeset 2233

Timestamp:

01/18/04 19:06:43 (9 years ago)

Author:

khali

Message:

Update 4.20, as suggested in ticket #1526.

Location:

lm-sensors/trunk/doc

Files:

: 3 modified

FAQ (modified) (3 diffs)
lm_sensors-FAQ.html (modified) (68 diffs)
lm_sensors-FAQ.texi (modified) (1 diff)

Legend:

: Unmodified
: Added
: Removed

lm-sensors/trunk/doc/FAQ

r2209	r2233
	1	START-INFO-DIR-ENTRY
	2	* lm_sensors-FAQ: (lm_sensors-FAQ) The lm_sensors FAQ
	3	END-INFO-DIR-ENTRY
	4
	5	Short Contents
	6	**************
	7
	8	lm_sensors
	9	1 PC and Sensor Overview
	10	2 Sensor and Bus Basics
	11	3 Installation and Management
	12	4 Problems
	13	5 How to Ask for Help
	14	6 How to Contribute
	15	7 Version 1 Specific Questions
	16	Appendix A Revision History of This Document
	17
	18
1	19	Table of Contents
2	20	*****************
…	…
938	956	==================================================
939	957
940		* (release 2.6.0 and later) Did you `modprobe i2c-proc'? Check
941		`lsmod'.
942
943		* (release 2.5.5 and earlier) Did you 'modprobe sensors'? Check
944		'lsmod'.
	958	* (Linux 2.6) Did you `modprobe i2c_sensor'? Check `lsmod'.
	959
	960	* (Linux 2.4) Did you `modprobe i2c-proc'? Check `lsmod'.
945	961
946	962	* If you did `sensors -s', did you run it as root?
947	963
948		* Do you have `/proc' support in your kernel (is `/proc' there?)
	964	* (Linux 2.6) Do you have sysfs support in your kernel (is `/sys'
	965	there and populated)?
	966
	967	* (Linux 2.4) Do you have procfs support in your kernel (is `/proc'
	968	there and populated)?
949	969
950	970	4.21 Sensors says `No sensors found!'
…	…
1507	1527
1508	1528	* Rev 1.0 Written by Philip Edelbrock, 19980803
1509

lm-sensors/trunk/doc/lm_sensors-FAQ.html

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

lm-sensors/trunk/doc/lm_sensors-FAQ.texi

r2208	r2233
981	981
982	982	@itemize
983		@item (~~release 2.6.0 and later) Did you @command{modprobe i2c-proc~~}? Check @command{lsmod}.
984		@item (~~release 2.5.5 and earlier) Did you 'modprobe sensors'? Check 'lsmod'~~.
	983	@item (Linux 2.6) Did you @command{modprobe i2c_sensor}? Check @command{lsmod}.
	984	@item (Linux 2.4) Did you @command{modprobe i2c-proc}? Check @command{lsmod}.
985	985	@item If you did @command{sensors -s}, did you run it as root?
986		@item Do you have @file{/proc} support in your kernel (is @file{/proc} there?)
	986	@item (Linux 2.6) Do you have sysfs support in your kernel (is @file{/sys} there and populated)?
	987	@item (Linux 2.4) Do you have procfs support in your kernel (is @file{/proc} there and populated)?
987	988	@end itemize
988	989

Download in other formats: