Add 4.6.1 -5V and -12V readings are way out of range!

Update 4.7 What are VID lines? Why is the VID reading wrong?


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2608 7894878c-1315-0410-8ee3-d5d059ff63e0

doc/FAQ

@@ -58,6 +58,7 @@ lm_sensors
   4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!
   4.5 My voltage readings seem to drift a bit. Is something wrong?
   4.6 Some measurements are way out of range. What happened?
+    4.6.1 -5V and -12V readings are way out of range!
   4.7 What are VID lines? Why is the VID reading wrong?
   4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?
   4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?
@@ -676,6 +677,14 @@ non-standard way. You can use the configuration file to describe how
 this measurement should be interpreted; see the comments the example
 file for more information.
 
+4.6.1 -5V and -12V readings are way out of range!
+-------------------------------------------------
+
+It's very frequent that negative voltage lines are not wired because
+motherboard manufacturers don't think they're worth monitoring (they
+are mostly unused these days). You can just add `ignore inN' lines to
+`/etc/sensors.conf' to hide them.
+
 4.7 What are VID lines? Why is the VID reading wrong?
 =====================================================
 
@@ -687,6 +696,12 @@ the sensor chip, so the readings may be invalid.  A reading of 0V,
 settings for the Processor Core voltage (often in0_min and in0_max) in
 that file so that they don't depend on vid.
 
+   The CPU nominal voltage is computed from VID lines according to a
+formula that depends on the CPU type. Most chips that report a VID
+value can be configured to use either VRM 8.2 (for Pentium III) or VRM
+9.0 (for Pentium 4 and Athlon). You chose which one you want through
+`/etc/sensors.conf'.  See `doc/vid' for more information.
+
 4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?
 =======================================================================================================
 

doc/lm_sensors-FAQ.html

@@ -102,6 +102,9 @@ and<br>
 <li><a href="#Section-4_002e4">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</a>
 <li><a href="#Section-4_002e5">4.5 My voltage readings seem to drift a bit. Is something wrong?</a>
 <li><a href="#Section-4_002e6">4.6 Some measurements are way out of range. What happened?</a>
+<ul>
+<li><a href="#Section-4_002e6">4.6.1 -5V and -12V readings are way out of range!</a>
+</li></ul>
 <li><a href="#Section-4_002e7">4.7 What are VID lines? Why is the VID reading wrong?</a>
 <li><a href="#Section-4_002e8">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</a>
 <li><a href="#Section-4_002e9">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</a>
@@ -1018,6 +1021,15 @@ non-standard way. You can use the configuration file to describe how this
 measurement should be interpreted; see the comments the example file for
 more information.
 
+   <p><a name="_002d5V-and-_002d12V-readings-are-way-out-of-range_0021"></a>
+
+<h4 class="subsection">4.6.1 -5V and -12V readings are way out of range!</h4>
+
+<p>It's very frequent that negative voltage lines are not wired because
+motherboard manufacturers don't think they're worth monitoring
+(they are mostly unused these days). You can just add
+<span class="command">ignore inN</span> lines to <span class="file">/etc/sensors.conf</span> to hide them.
+
 <div class="node">
 <p><hr>
 <a name="Section-4_002e7"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e8">Section 4.8</a>,
@@ -1036,6 +1048,12 @@ If this is the case, add a line <span class="command">ignore vid</span> to <span
 and change the min and max settings for the Processor Core voltage
 (often in0_min and in0_max) in that file so that they don't depend on vid.
 
+   <p>The CPU nominal voltage is computed from VID lines according to a formula
+that depends on the CPU type. Most chips that report a VID value can be
+configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4
+and Athlon). You chose which one you want through <span class="file">/etc/sensors.conf</span>. 
+See <span class="file">doc/vid</span> for more information.
+
 <div class="node">
 <p><hr>
 <a name="Section-4_002e8"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e9">Section 4.9</a>,

doc/lm_sensors-FAQ.texi

@@ -690,6 +690,14 @@ non-standard way. You can use the configuration file to describe how this
 measurement should be interpreted; see the comments the example file for
 more information.
 
+@anchor{-5V and -12V readings are way out of range!}
+@subsection -5V and -12V readings are way out of range!
+
+It's very frequent that negative voltage lines are not wired because
+motherboard manufacturers don't think they're worth monitoring
+(they are mostly unused these days). You can just add
+@command{ignore inN} lines to @file{/etc/sensors.conf} to hide them.
+
 
 @node Section 4.7, Section 4.8, Section 4.6, Problems
 @section What are VID lines? Why is the VID reading wrong?
@@ -702,6 +710,12 @@ If this is the case, add a line @command{ignore vid} to @file{/etc/sensors.conf}
 and change the min and max settings for the Processor Core voltage
 (often in0_min and in0_max) in that file so that they don't depend on vid.
 
+The CPU nominal voltage is computed from VID lines according to a formula
+that depends on the CPU type. Most chips that report a VID value can be
+configured to use either VRM 8.2 (for Pentium III) or VRM 9.0 (for Pentium 4
+and Athlon). You chose which one you want through @file{/etc/sensors.conf}.
+See @file{doc/vid} for more information.
+
 
 @node Section 4.8, Section 4.9, Section 4.7, Problems
 @section I read sensor values several times a second, but they are only updated only each second or so. Why?

doc/version.texi

@@ -1,3 +1,3 @@
-@set UPDATED 11 April 2004
-@set UPDATED-MONTH April 2004
-@set VERSION 2.12
+@set UPDATED 23 June 2004
+@set UPDATED-MONTH June 2004
+@set VERSION 2.13