diff options
author | khali <khali@7894878c-1315-0410-8ee3-d5d059ff63e0> | 2009-01-21 09:09:19 +0000 |
---|---|---|
committer | khali <khali@7894878c-1315-0410-8ee3-d5d059ff63e0> | 2009-01-21 09:09:19 +0000 |
commit | 86ed559ea482cc6a359f9d65381c66ae08a419fd (patch) | |
tree | 8b60c72e3c436542771e58775679020675ed039a | |
parent | f79ab9d0d730df298fb6b45c9c7d36219b6503c9 (diff) | |
download | lm-sensors-86ed559ea482cc6a359f9d65381c66ae08a419fd.tar.gz |
Don't tell users to blindly run i2cdump, it is dangerous!
git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@5616 7894878c-1315-0410-8ee3-d5d059ff63e0
-rw-r--r-- | doc/FAQ | 11 | ||||
-rw-r--r-- | doc/lm_sensors-FAQ.html | 62 | ||||
-rw-r--r-- | doc/lm_sensors-FAQ.texi | 3 |
3 files changed, 32 insertions, 44 deletions
@@ -1139,7 +1139,7 @@ are running the `sensors' program it installed and not some older For chips on the ISA bus, did you insert i2c-isa? *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. 4.29 Inserting modules hangs my board @@ -1150,7 +1150,7 @@ There are several possible causes: inserted any chip drivers, to verify. 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. 3. The chip driver is reinitializing the chip, which undoes critical @@ -1202,7 +1202,7 @@ See support tickets 941, 840, and 841 for information. 4.31.4 Tyan 2688 ---------------- -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. 4.32 Problems on particular systems @@ -1279,11 +1279,6 @@ will be emailed automatically when your question has been answered. 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: * The output of (as root) `prog/dump/isadump 0x295 0x296' (only if it's not all `XX') diff --git a/doc/lm_sensors-FAQ.html b/doc/lm_sensors-FAQ.html index 1e0d0c55..5527e455 100644 --- a/doc/lm_sensors-FAQ.html +++ b/doc/lm_sensors-FAQ.html @@ -3,7 +3,7 @@ <title>Sensors FAQ for lm_sensors version 2.18</title> <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"> <meta http-equiv="Content-Style-Type" content="text/css"> @@ -81,10 +81,10 @@ Jean Delvare<br> <li><a href="#Section-3_002e4">3.4.5 I need help with <samp><span class="file">sensors.conf</span></samp>!</a> <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 ‘<samp><span class="samp">No such file or directory</span></samp>’ 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 ‘<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>’ - how to fix?</a> </li></ul> <li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a> <li><a href="#Section-3_002e8">3.8 <samp><span class="command">make install</span></samp> fails on Mandrake kernels</a> @@ -132,12 +132,12 @@ Jean Delvare<br> <li><a href="#Section-4_002e17">4.17.9 Bad readings from LM80!</a> </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 ‘<samp><span class="samp">Upgrade BIOS</span></samp>’! 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 ‘<samp><span class="samp">use force_addr=0xaddr</span></samp>’! 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 ‘<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_002e22">4.22 Sensors output is not correct!</a> <li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a> <ul> @@ -151,9 +151,9 @@ Jean Delvare<br> <li><a href="#Section-4_002e24">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</a> <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 ‘<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>’</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 ‘<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>’</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> <li><a href="#Section-4_002e30">4.30 Inserting modules slows down my board</a> @@ -517,7 +517,7 @@ Up: <a rel="up" accesskey="u" href="#Top">Top</a> <li><a accesskey="2" href="#Section-3_002e2">Section 3.2</a>: How do I know which chips I own? <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 ‘<samp><span class="samp">No such file or directory</span></samp>’ 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! <li><a accesskey="8" href="#Section-3_002e8">Section 3.8</a>: <samp><span class="command">make install</span></samp> fails on Mandrake kernels @@ -548,8 +548,7 @@ space. On the other hand, it can be a bit confusing at first. <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> <a name="Section-3_002e2"></a> @@ -716,7 +715,7 @@ Up: <a rel="up" accesskey="u" href="#Installation">Installation</a> </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 ‘<samp><span class="samp">No such file or directory</span></samp>’ warnings when I compile?</h3> <p>Don't worry about them. The dependency files (which tell which files should be recompiled when certain files change) are created @@ -742,7 +741,7 @@ how you installed, they should be under either <samp><span class="file">/usr/loc <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 ‘<samp><span class="samp">No rule to make target xxxx needed by xxxx</span></samp>’ - how to fix?</h4> <ul> <li>See <a href="#Section-3_002e6">I get all kinds of weird compilation errors</a>, also try <samp><span class="command">make clean</span></samp> in <samp><span class="file">lm_sensors</span></samp>. @@ -853,7 +852,7 @@ old i2c stuff anymore anyway. Just don't use it with abandon. <li>Try (in the build directory of <samp><span class="file">lm_sensors)</span></samp> <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. More of a workaround than a real fix, but at least you can get it @@ -890,15 +889,15 @@ Up: <a rel="up" accesskey="u" href="#Top">Top</a> <li><a href="#Section-4_002e16">Section 4.16</a>: I ran sensors-detect, but now I get strange readings?! <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 ‘<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_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 ‘<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>’ <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 ‘<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>’ <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 <li><a href="#Section-4_002e30">Section 4.30</a>: Inserting modules slows down my board @@ -1446,7 +1445,7 @@ Up: <a rel="up" accesskey="u" href="#Problems">Problems</a> </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 ‘<samp><span class="samp">Upgrade BIOS</span></samp>’! 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 is complex. For the ALI M7101 device, there is a solution which uses the @@ -1454,21 +1453,21 @@ is complex. For the ALI M7101 device, there is a solution which uses the For other PCI devices, you can try to modify 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 ‘<samp><span class="samp">try force_addr</span></samp>’, 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 you can send us your request. <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 ‘<samp><span class="samp">use force_addr=0xaddr</span></samp>’! What address do I use?</h4> <p>If the problem is a PCI device whose base address is not set, you may be able to set the address with a force parameter. The via686a and sis5595 chip drivers, and some bus drivers, support the command line <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. <div class="node"> @@ -1481,7 +1480,7 @@ Up: <a rel="up" accesskey="u" href="#Problems">Problems</a> </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 ‘<samp><span class="samp">Can't access procfs/sysfs file</span></samp>’</h3> <ul> <li>Linux 2.6 @@ -1513,7 +1512,7 @@ Up: <a rel="up" accesskey="u" href="#Problems">Problems</a> </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 ‘<samp><span class="samp">No sensors found!</span></samp>’</h3> <ul> <li>Did <samp><span class="command">sensors-detect</span></samp> find sensors? (If not see <a href="#Sensors_002ddetect-doesnt-find-any-sensors">Sensors-detect doesnt find any sensors</a>) @@ -1660,7 +1659,7 @@ Up: <a rel="up" accesskey="u" href="#Problems">Problems</a> </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 ‘<samp><span class="samp">Error: Line xxx: zzzzzzz</span></samp>’</h3> <p>These are errors from the libsensors library in reading the <samp><span class="file">/etc/sensors.conf</span></samp> configuration file. Go to that line @@ -1701,7 +1700,7 @@ Up: <a rel="up" accesskey="u" href="#Problems">Problems</a> </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 ‘<samp><span class="samp">ERROR: Can't get xxxxx data!</span></samp>’</h3> <ul> <li>(Linux 2.6) Make sure you are using one of the @@ -1933,14 +1932,11 @@ emailed automatically when your question has been answered. <ul> <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 ‘<samp><span class="samp">XX</span></samp>’) </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 ‘<samp><span class="samp">XX</span></samp>’) </ul> <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard) <li>Motherboard type diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index 9cbff181..e74f2a00 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -1329,9 +1329,6 @@ Here's what you should send us: @item The output of (as root) @command{prog/detect/i2cdetect X} 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: @itemize |