Changeset 5616

Timestamp:

01/21/09 10:09:19 (4 years ago)

Author:

khali

Message:

Don't tell users to blindly run i2cdump, it is dangerous!

Location:

lm-sensors/trunk/doc

Files:

• FAQ (modified) (4 diffs)
• lm_sensors-FAQ.html (modified) (19 diffs)
• lm_sensors-FAQ.texi (modified) (1 diff)

lm-sensors/trunk/doc/FAQ

@@ -1140 +1140 @@
 
    *Note What to do if a module wont insert: Section 5.2, if the
-modules didn't insert, also *Note Sensors says No sensors found:
+modules didn't insert, also *note Sensors says No sensors found:
 Section 4.21.
 
@@ -1151 +1151 @@
 
   2. Wrong chip driver. Verify that you have a chip supported by the
-     chip driver, see *Note What chips are on motherboard XYZ: Section
+     chip driver, see *note What chips are on motherboard XYZ: Section
      3.2.1.
 
@@ -1203 +1203 @@
 ----------------
 
-For board hangs, see support ticket 721 for information.  Also *Note
+For board hangs, see support ticket 721 for information.  Also *note
 Inserting modules hangs my board: Section 4.29.
 
@@ -1279 +1279 @@
           the bus number (run `i2cdetect' with no arguments to list the
           busses) (please send this only if it's not all `XX')
-
-        * The output of (as root) `prog/dump/i2cdump X 0xXX' where XX =
-          the address of each chip you see in the output of
-          `i2cdetect'. (run once for each chip) (please send this only
-          if it's not all `ff')
 
    * If an ISA sensor chip problem:

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

@@ -4 +4 @@
 <meta http-equiv="Content-Type" content="text/html">
 <meta name="description" content="Sensors FAQ for lm_sensors version 2.18">
-<meta name="generator" content="makeinfo 4.8">
+<meta name="generator" content="makeinfo 4.11">
 <link title="Top" rel="top" href="#Top">
 <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
@@ -82 +82 @@
 <li><a href="#Section-3_002e4">3.4.6 Do you have a database of <samp><span class="file">sensors.conf</span></samp> entries for specific boards?</a>
 </li></ul>
-<li><a href="#Section-3_002e5">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</a>
+<li><a href="#Section-3_002e5">3.5 What about the &lsquo;<samp><span class="samp">No such file or directory</span></samp>&rsquo; warnings when I compile?</a>
 <li><a href="#Section-3_002e6">3.6 I get all kinds of weird compilation errors?</a>
 <ul>
-<li><a href="#Section-3_002e6">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</a>
+<li><a href="#Section-3_002e6">3.6.1 &lsquo;<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>&rsquo; - how to fix?</a>
 </li></ul>
 <li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a>
@@ -133 +133 @@
 </li></ul>
 <li><a href="#Section-4_002e18">4.18 How do I configure two chips (LM87) differently?</a>
-<li><a href="#Section-4_002e19">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</a>
+<li><a href="#Section-4_002e19">4.19 Dmesg says &lsquo;<samp><span class="samp">Upgrade BIOS</span></samp>&rsquo;! I don't want to!</a>
 <ul>
-<li><a href="#Section-4_002e19">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</a>
+<li><a href="#Section-4_002e19">4.19.1 Dmesg says &lsquo;<samp><span class="samp">use force_addr=0xaddr</span></samp>&rsquo;! What address do I use?</a>
 </li></ul>
-<li><a href="#Section-4_002e20">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</a>
-<li><a href="#Section-4_002e21">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</a>
+<li><a href="#Section-4_002e20">4.20 Sensors says &lsquo;<samp><span class="samp">Can't access procfs/sysfs file</span></samp>&rsquo;</a>
+<li><a href="#Section-4_002e21">4.21 Sensors says &lsquo;<samp><span class="samp">No sensors found!</span></samp>&rsquo;</a>
 <li><a href="#Section-4_002e22">4.22 Sensors output is not correct!</a>
 <li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a>
@@ -152 +152 @@
 <li><a href="#Section-4_002e24">4.24.3 Sensors-detect doesn't find any sensors!</a>
 </li></ul>
-<li><a href="#Section-4_002e25">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</a>
+<li><a href="#Section-4_002e25">4.25 Sensors says &lsquo;<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>&rsquo;</a>
 <li><a href="#Section-4_002e26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a>
-<li><a href="#Section-4_002e27">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</a>
+<li><a href="#Section-4_002e27">4.27 Sensors says &lsquo;<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>&rsquo;</a>
 <li><a href="#Section-4_002e28">4.28 Sensors doesn't find any sensors, just eeproms.</a>
 <li><a href="#Section-4_002e29">4.29 Inserting modules hangs my board</a>
@@ -518 +518 @@
 <li><a accesskey="3" href="#Section-3_002e3">Section 3.3</a>:      Which modules should I insert? 
 <li><a accesskey="4" href="#Section-3_002e4">Section 3.4</a>:      Do I need the configuration file <samp><span class="file">/etc/sensors.conf</span></samp>? 
-<li><a accesskey="5" href="#Section-3_002e5">Section 3.5</a>:      What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings
+<li><a accesskey="5" href="#Section-3_002e5">Section 3.5</a>:      What about the &lsquo;<samp><span class="samp">No such file or directory</span></samp>&rsquo; warnings
 <li><a accesskey="6" href="#Section-3_002e6">Section 3.6</a>:      I get all kinds of weird compilation errors? 
 <li><a accesskey="7" href="#Section-3_002e7">Section 3.7</a>:      It still does not compile or patch! 
@@ -549 +549 @@
    <p>Further information is in <samp><span class="file">doc/modules</span></samp>.
 
-   <p><a name="How-do-I-know-which-chips-I-own"></a>
-<div class="node">
+   <p><a name="How-do-I-know-which-chips-I-own"></a><div class="node">
 <p><hr>
 <a name="Section-3.2"></a>
@@ -717 +716 @@
 </div>
 
-<h3 class="section">3.5 What about the `<samp><span class="samp">No such file or directory</span></samp>' warnings when I compile?</h3>
+<h3 class="section">3.5 What about the &lsquo;<samp><span class="samp">No such file or directory</span></samp>&rsquo; warnings when I compile?</h3>
 
 <p>Don't worry about them. The dependency files (which tell which
@@ -743 +742 @@
    <p><a name="Section-3_002e6_002e1"></a>
 
-<h4 class="subsection">3.6.1 `<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>' - how to fix?</h4>
+<h4 class="subsection">3.6.1 &lsquo;<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>&rsquo; - how to fix?</h4>
 
      <ul>
@@ -854 +853 @@
      <pre class="example">          <samp><span class="command">make clean</span></samp>
           <samp><span class="command">make</span></samp>
-     </pre>
+</pre>
      <li><em>If</em> you still have problems, you may have to replace the include
 paths in the <samp><span class="file">.c/.h</span></samp> files with absolute paths to the header files. 
@@ -891 +890 @@
 <li><a href="#Section-4_002e17">Section 4.17</a>:         Bad readings from particular chips
 <li><a href="#Section-4_002e18">Section 4.18</a>:         How do I configure two chips (LM87) differently? 
-<li><a href="#Section-4_002e19">Section 4.19</a>:         Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to! 
-<li><a href="#Section-4_002e20">Section 4.20</a>:         Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'
-<li><a href="#Section-4_002e21">Section 4.21</a>:         Sensors says `<samp><span class="samp">No sensors found!</span></samp>'
+<li><a href="#Section-4_002e19">Section 4.19</a>:         Dmesg says &lsquo;<samp><span class="samp">Upgrade BIOS</span></samp>&rsquo;! I don't want to! 
+<li><a href="#Section-4_002e20">Section 4.20</a>:         Sensors says &lsquo;<samp><span class="samp">Can't access procfs/sysfs file</span></samp>&rsquo;
+<li><a href="#Section-4_002e21">Section 4.21</a>:         Sensors says &lsquo;<samp><span class="samp">No sensors found!</span></samp>&rsquo;
 <li><a href="#Section-4_002e22">Section 4.22</a>:         Sensors output is not correct! 
 <li><a href="#Section-4_002e23">Section 4.23</a>:         What is at I2C address XXX? 
 <li><a href="#Section-4_002e24">Section 4.24</a>:         Sensors-detect doesn't work at all
-<li><a href="#Section-4_002e25">Section 4.25</a>:         Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'
+<li><a href="#Section-4_002e25">Section 4.25</a>:         Sensors says &lsquo;<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>&rsquo;
 <li><a href="#Section-4_002e26">Section 4.26</a>:         Sensors only gives the name, adapter, and algorithm! 
-<li><a href="#Section-4_002e27">Section 4.27</a>:         Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'
+<li><a href="#Section-4_002e27">Section 4.27</a>:         Sensors says &lsquo;<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>&rsquo;
 <li><a href="#Section-4_002e28">Section 4.28</a>:         Sensors doesn't find any sensors, just eeproms. 
 <li><a href="#Section-4_002e29">Section 4.29</a>:         Inserting modules hangs my board
@@ -1447 +1446 @@
 </div>
 
-<h3 class="section">4.19 Dmesg says `<samp><span class="samp">Upgrade BIOS</span></samp>'! I don't want to!</h3>
+<h3 class="section">4.19 Dmesg says &lsquo;<samp><span class="samp">Upgrade BIOS</span></samp>&rsquo;! I don't want to!</h3>
 
 <p>If the problem is a PCI device is not present in <samp><span class="command">lspci</span></samp>, the solution
@@ -1455 +1454 @@
 the m7101 solution in <samp><span class="file">prog/hotplug</span></samp>.
 
-   <p>If dmesg says `<samp><span class="samp">try force_addr</span></samp>', see below. Other drivers generally do not
+   <p>If dmesg says &lsquo;<samp><span class="samp">try force_addr</span></samp>&rsquo;, see below. Other drivers generally do not
 support the force_addr parameter. Sorry. Check the documentation
 for your driver in <samp><span class="file">doc/[chips,busses]</span></samp> and if we don't support it
@@ -1462 +1461 @@
    <p><a name="Dmesg-says-use-force_005faddr_003d0xaddr_0021-What-address-do-I-use"></a>
 
-<h4 class="subsection">4.19.1 Dmesg says `<samp><span class="samp">use force_addr=0xaddr</span></samp>'! What address do I use?</h4>
+<h4 class="subsection">4.19.1 Dmesg says &lsquo;<samp><span class="samp">use force_addr=0xaddr</span></samp>&rsquo;! What address do I use?</h4>
 
 <p>If the problem is a PCI device whose base address is not set,
@@ -1469 +1468 @@
 <samp><span class="command">modprobe via686a force_addr=0xADDRESS</span></samp> where ADDRESS
 is the I/O address. You must select an address that is not in use. 
-<samp><span class="command">cat <samp>/proc/ioports</samp></span></samp> to check (carefully) for conflicts. A high number like
+<samp><span class="command">cat </span><samp><span class="file">/proc/ioports</span></samp></samp> to check (carefully) for conflicts. A high number like
 0xf000 is generally safe.
 
@@ -1482 +1481 @@
 </div>
 
-<h3 class="section">4.20 Sensors says `<samp><span class="samp">Can't access procfs/sysfs file</span></samp>'</h3>
+<h3 class="section">4.20 Sensors says &lsquo;<samp><span class="samp">Can't access procfs/sysfs file</span></samp>&rsquo;</h3>
 
      <ul>
@@ -1514 +1513 @@
 </div>
 
-<h3 class="section">4.21 Sensors says `<samp><span class="samp">No sensors found!</span></samp>'</h3>
+<h3 class="section">4.21 Sensors says &lsquo;<samp><span class="samp">No sensors found!</span></samp>&rsquo;</h3>
 
      <ul>
@@ -1661 +1660 @@
 </div>
 
-<h3 class="section">4.25 Sensors says `<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>'</h3>
+<h3 class="section">4.25 Sensors says &lsquo;<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>&rsquo;</h3>
 
 <p>These are errors from the libsensors library in
@@ -1702 +1701 @@
 </div>
 
-<h3 class="section">4.27 Sensors says `<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>'</h3>
+<h3 class="section">4.27 Sensors says &lsquo;<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>&rsquo;</h3>
 
      <ul>
@@ -1934 +1933 @@
 <li>The output of (as root) <samp><span class="command">prog/detect/i2cdetect X</span></samp>
 where X = the bus number (run <samp><span class="command">i2cdetect</span></samp> with no arguments to list the busses)
-(please send this only if it's not all `<samp><span class="samp">XX</span></samp>')
-<li>The output of (as root) <samp><span class="command">prog/dump/i2cdump X 0xXX</span></samp>
-where XX = the address of each chip you see in the output of <samp><span class="command">i2cdetect</span></samp>. (run once for each chip)
-(please send this only if it's not all `<samp><span class="samp">ff</span></samp>')
+(please send this only if it's not all &lsquo;<samp><span class="samp">XX</span></samp>&rsquo;)
 </ul>
      <li>If an ISA sensor chip problem:
           <ul>
-<li>The output of (as root) <samp><span class="command">prog/dump/isadump 0x295 0x296</span></samp> (only if it's not all `<samp><span class="samp">XX</span></samp>')
+<li>The output of (as root) <samp><span class="command">prog/dump/isadump 0x295 0x296</span></samp> (only if it's not all &lsquo;<samp><span class="samp">XX</span></samp>&rsquo;)
 </ul>
      <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard)

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

@@ -1330 +1330 @@
 where X = the bus number (run @command{i2cdetect} with no arguments to list the busses)
 (please send this only if it's not all @samp{XX})
-@item The output of (as root) @command{prog/dump/i2cdump X 0xXX}
-where XX = the address of each chip you see in the output of @command{i2cdetect}. (run once for each chip)
-(please send this only if it's not all @samp{ff})
 @end itemize
 @item If an ISA sensor chip problem: