Context Navigation

← Previous Changeset
Next Changeset →

Changeset 2447

Timestamp:

04/18/04 02:36:56 (9 years ago)

Author:

mds

Message:

update eeprom shadow info

Location:

lm-sensors/trunk/doc

Files:

: 3 modified

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

Legend:

: Unmodified
: Added
: Removed

lm-sensors/trunk/doc/FAQ

r2435	r2447
1045	1045
1046	1046	These are often 'shadows' of your EEPROMs on your SDRAM DIMMs at
1047		addresses 0x50 - 0x57. They aren't really there. If you try and do a
1048		`i2cdump' on them you won't get anything. This is probably caused by
1049		some timing problem on your motherboard or on the DIMMs. We don't know
1050		the exact cause.
	1047	addresses 0x50 - 0x57. They are the 'software write-protect' registers
	1048	of the SDRAM Serial Presence Detect EEPROMs. If you try and do a
	1049	`i2cdump' on them to read the location, you won't get anything, because
	1050	they contain a single write-only register. This register can be used
	1051	to permanently write-protect the contents of the eeprom.
1051	1052
1052	1053	4.24 Sensors-detect doesn't work at all

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

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

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

r2435	r2447
1049	1049
1050	1050	These are often 'shadows' of your EEPROMs on your SDRAM DIMMs
1051		at addresses 0x50 - 0x57. They aren't really there. If you try and
1052		do a @command{i2cdump} on them you won't get anything. This is probably
1053		caused by some timing problem on your motherboard or on the DIMMs.
1054		We don't know the exact cause.
	1051	at addresses 0x50 - 0x57. They are the 'software write-protect'
	1052	registers of the SDRAM Serial Presence Detect EEPROMs.
	1053	If you try and
	1054	do a @command{i2cdump} on them to read the location, you won't get anything,
	1055	because they contain a single write-only register.
	1056	This register can be used to permanently
	1057	write-protect the contents of the eeprom.
1055	1058
1056	1059

Download in other formats: