wt/lm-sensors
1
0 Fork 0
mirror of https://github.com/lm-sensors/lm-sensors.git synced 2026-10-30 13:00:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove the version 1 specifics part. It's very old and I'd hope

Browse Source 
nobody uses this anymore. At any rate, there's little point in including
version 1 information in the version 2 FAQ. Set FAQ version to 2.18.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@3216 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Jean Delvare committed 2005-12-17 11:25:33 +00:00
1 parent e843854352
commit 4d5a7df886
4 files changed
+14 -248
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

doc/FAQ
+2 -63
View File
@@ -8,7 +8,6 @@ lm_sensors
4 Problems
5 How to Ask for Help
6 How to Contribute
7 Version 1 Specific Questions
Appendix A Revision History of This Document
@@ -128,11 +127,6 @@ lm_sensors
6.6 How to submit a patch
6.7 How to REALLY help
6.8 How to get release announcements
7 Version 1 Specific Questions
7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?
7.2 The modules won't load, saying 'SMBus not detected'.
7.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why?
7.4 On my Dell, a LM80 is detected, but all readings are 0!
Appendix A Revision History of This Document
@@ -1539,66 +1533,11 @@ register on our freshmeat project page
`http://freshmeat.net/projects/lm_sensors' to 'subscribe to new
releases' and then freshmeat will email you announcement.
7 Version 1 Specific Questions
******************************
Note: Version 1 is very very old and is not recommended.
7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?
======================================================================================================================
Currently, our code only assumes that an SMBus exists if it originates
from the Intel PIIX4 (82371AB). If your computer doesn't have one, or
if your SMBus originates from a different SMBus 'host', then you are
out of luck. :'( Our experience is, though, that most machines have a
PIIX4, and that it is where the SMBus is hosted.
Regarding the VIA chip set(s):
Right now, the SMBus code depends on the Intel PIIX4 chip to handle
SMBus transactions. The VIA chip set is NOT supported at this time
because it forces much of the SMBus protocol to be implemented by
software.
To implement the SMBus correctly with the VIA chip, it needs to be
written at a low level to be quick. A more attractive alternative is to
use the Bios SMBus interface (not always available nor standard).
Version 2 supports the VIA chipset, and will support other chipsets.
Version 1 never will.
7.2 The modules won't load, saying 'SMBus not detected'.
========================================================
This should no longer be an issue in 1.4.10 and later; it will continue
loading, but it won't support SMBus-connected devices, of course.
7.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why?
==============================================================================================================
It takes about 1.5 seconds for the LM78 to update all its sensor
values. If we would try to read it before it finished that, you would
get old garbage instead. So you have to wait 1.5 seconds after the
module is inserted before you can access `/proc/sensors'.
Module versions 1.3.7 and later let the process sleep if it tries to
access sensor data right after insertion time, and do not display this
message anymore.
7.4 On my Dell, a LM80 is detected, but all readings are 0!
===========================================================
This is a bug we have only observed on Dell computers. There is
probably a problem with the way the SMBus is accessed; but it is not yet
clear whether the problem is in our code or with the Dells.
There are very probably no sensor chips at all on your computer; but
until somebody contacts Dell about this and tells us the results, we
can not be sure.
Appendix A Revision History of This Document
********************************************
* Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
* Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips),
removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
doc/lm_sensors-FAQ.html
+7 -111
View File
@@ -1,8 +1,8 @@
<html lang="en">
<head>
<title>Sensors FAQ for lm_sensors version 2.17</title>
<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.17">
<meta name="description" content="Sensors FAQ for lm_sensors version 2.18">
<meta name="generator" content="makeinfo 4.7">
<link title="Top" rel="top" href="#Top">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
@@ -19,7 +19,7 @@
--></style>
</head>
<body>
<h1 class="settitle">Sensors FAQ for lm_sensors version 2.17</h1>
<h1 class="settitle">Sensors FAQ for lm_sensors version 2.18</h1>
Copyright (C) 1998 - 2005<br>
Frodo Looijaard,<br>
Philip Edelbrock,<br>
@@ -37,7 +37,6 @@ Jean Delvare<br>
<li><a href="#toc_Problems">4 Problems</a></li>
<li><a href="#toc_Help">5 How to Ask for Help</a></li>
<li><a href="#toc_Contribute">6 How to Contribute</a></li>
<li><a href="#toc_Version-1-Specifics">7 Version 1 Specific Questions</a></li>
<li><a href="#toc_Document-Revisions">Appendix A Revision History of This Document</a></li>
</ul>
</div>
@@ -194,13 +193,6 @@ Jean Delvare<br>
<li><a href="#Section-6_002e7">6.7 How to REALLY help</a>
<li><a href="#Section-6_002e8">6.8 How to get release announcements</a>
</li></ul>
<li><a name="toc_Version-1-Specifics" href="#Version-1-Specifics">7 Version 1 Specific Questions</a>
<ul>
<li><a href="#Section-7_002e1">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>
<li><a href="#Section-7_002e2">7.2 The modules won't load, saying 'SMBus not detected'.</a>
<li><a href="#Section-7_002e3">7.3 I try to read <span class="file">/proc/sensors</span>, and I get a "No sensor data yet (try again in a few moments)" message. Why?</a>
<li><a href="#Section-7_002e4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a>
</li></ul>
<li><a name="toc_Document-Revisions" href="#Document-Revisions">Appendix A Revision History of This Document</a>
</li></ul>
</div>
@@ -225,8 +217,7 @@ is not in standard 2.2-vintage kernels.
<li><a accesskey="4" href="#Problems">Problems</a>: Problems
<li><a accesskey="5" href="#Help">Help</a>: How to Ask for Help
<li><a accesskey="6" href="#Contribute">Contribute</a>: How to Contribute
<li><a accesskey="7" href="#Version-1-Specifics">Version 1 Specifics</a>: Version 1 Specific Questions
<li><a accesskey="8" href="#Document-Revisions">Document Revisions</a>: Revision History of This Document
<li><a accesskey="7" href="#Document-Revisions">Document Revisions</a>: Revision History of This Document
</ul>
<div class="node">
@@ -2034,7 +2025,7 @@ driver, we will apply it. This generic code is unlikely to cause trouble.
<div class="node">
<p><hr>
<a name="Contribute"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Version-1-Specifics">Version 1 Specifics</a>,
<a name="Contribute"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Document-Revisions">Document Revisions</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Help">Help</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br>
@@ -2195,103 +2186,7 @@ will email you announcement.
<div class="node">
<p><hr>
<a name="Version-1-Specifics"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Document-Revisions">Document Revisions</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Contribute">Contribute</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br>
</div>
<h2 class="chapter">7 Version 1 Specific Questions</h2>
<ul class="menu">
<li><a accesskey="1" href="#Section-7_002e1">Section 7.1</a>: My mainboard has an SMBus, your code can't find it. Why?
<li><a accesskey="2" href="#Section-7_002e2">Section 7.2</a>: The modules won't load, saying 'SMBus not detected'.
<li><a accesskey="3" href="#Section-7_002e3">Section 7.3</a>: I get a "No sensor data yet (try again in a few moments)" msg.
<li><a accesskey="4" href="#Section-7_002e4">Section 7.4</a>: On my Dell, a LM80 is detected, but all readings are 0!
</ul>
<p>Note: Version 1 is very very old and is not recommended.
<div class="node">
<p><hr>
<a name="Section-7_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e2">Section 7.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a>
<br>
</div>
<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>
<p>Currently, our code only assumes that an SMBus exists if it originates
from the Intel PIIX4 (82371AB). If your computer doesn't have one, or if your
SMBus originates from a different SMBus 'host', then you are out of luck. :'(
Our experience is, though, that most machines have a PIIX4, and that it is
where the SMBus is hosted.
<p>Regarding the VIA chip set(s):
<p>Right now, the SMBus code depends on the Intel PIIX4 chip to handle
SMBus transactions. The VIA chip set is NOT supported at this time because
it forces much of the SMBus protocol to be implemented by software.
<p>To implement the SMBus correctly with the VIA chip, it needs to be
written at a low level to be quick. A more attractive alternative is to
use the Bios SMBus interface (not always available nor standard).
<p>Version 2 supports the VIA chipset, and will support other chipsets.
Version 1 never will.
<div class="node">
<p><hr>
<a name="Section-7_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e3">Section 7.3</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e1">Section 7.1</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a>
<br>
</div>
<h3 class="section">7.2 The modules won't load, saying 'SMBus not detected'.</h3>
<p>This should no longer be an issue in 1.4.10 and later; it will
continue loading, but it won't support SMBus-connected devices, of course.
<div class="node">
<p><hr>
<a name="Section-7_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e4">Section 7.4</a>,
Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e2">Section 7.2</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a>
<br>
</div>
<h3 class="section">7.3 I try to read <span class="file">/proc/sensors</span>, and I get a "No sensor data yet (try again in a few moments)" message. Why?</h3>
<p>It takes about 1.5 seconds for the LM78 to update all its sensor
values. If we would try to read it before it finished that, you would get
old garbage instead. So you have to wait 1.5 seconds after the module is
inserted before you can access <span class="file">/proc/sensors</span>.
<p>Module versions 1.3.7 and later let the process sleep if it tries
to access sensor data right after insertion time, and do not display this
message anymore.
<div class="node">
<p><hr>
<a name="Section-7_002e4"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e3">Section 7.3</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a>
<br>
</div>
<h3 class="section">7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3>
<p>This is a bug we have only observed on Dell computers. There is
probably a problem with the way the SMBus is accessed; but it is not yet
clear whether the problem is in our code or with the Dells.
<p>There are very probably no sensor chips at all on your computer;
but until somebody contacts Dell about this and tells us the results, we
can not be sure.
<div class="node">
<p><hr>
<a name="Document-Revisions"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Version-1-Specifics">Version 1 Specifics</a>,
<a name="Document-Revisions"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Contribute">Contribute</a>,
Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br>
</div>
@@ -2299,6 +2194,7 @@ Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<h2 class="appendix">Appendix A Revision History of This Document</h2>
<ul>
<li>Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
<li>Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips),
removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
<li>Rev 2.16 (JD) Added 4.33.2, 2005-09-06
doc/lm_sensors-FAQ.texi
+3 -72
View File
@@ -52,7 +52,6 @@ is not in standard 2.2-vintage kernels.
* Problems:: Problems
* Help:: How to Ask for Help
* Contribute:: How to Contribute
* Version 1 Specifics:: Version 1 Specific Questions
* Document Revisions:: Revision History of This Document
@end menu
@@ -1486,7 +1485,7 @@ provides a patch to libsensors and/or sensors to add support for this
driver, we will apply it. This generic code is unlikely to cause trouble.
@node Contribute, Version 1 Specifics, Help, Top
@node Contribute, Document Revisions, Help, Top
@chapter How to Contribute
@menu
@@ -1594,79 +1593,11 @@ to 'subscribe to new releases' and then freshmeat
will email you announcement.
@node Version 1 Specifics, Document Revisions, Contribute, Top
@chapter Version 1 Specific Questions
@menu
* Section 7.1:: My mainboard has an SMBus, your code can't find it. Why?
* Section 7.2:: The modules won't load, saying 'SMBus not detected'.
* Section 7.3:: I get a "No sensor data yet (try again in a few moments)" msg.
* Section 7.4:: On my Dell, a LM80 is detected, but all readings are 0!
@end menu
Note: Version 1 is very very old and is not recommended.
@node Section 7.1, Section 7.2, , Version 1 Specifics
@section My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?
Currently, our code only assumes that an SMBus exists if it originates
from the Intel PIIX4 (82371AB). If your computer doesn't have one, or if your
SMBus originates from a different SMBus 'host', then you are out of luck. :'(
Our experience is, though, that most machines have a PIIX4, and that it is
where the SMBus is hosted.
Regarding the VIA chip set(s):
Right now, the SMBus code depends on the Intel PIIX4 chip to handle
SMBus transactions. The VIA chip set is NOT supported at this time because
it forces much of the SMBus protocol to be implemented by software.
To implement the SMBus correctly with the VIA chip, it needs to be
written at a low level to be quick. A more attractive alternative is to
use the Bios SMBus interface (not always available nor standard).
Version 2 supports the VIA chipset, and will support other chipsets.
Version 1 never will.
@node Section 7.2, Section 7.3, Section 7.1, Version 1 Specifics
@section The modules won't load, saying 'SMBus not detected'.
This should no longer be an issue in 1.4.10 and later; it will
continue loading, but it won't support SMBus-connected devices, of course.
@node Section 7.3, Section 7.4, Section 7.2, Version 1 Specifics
@section I try to read @file{/proc/sensors}, and I get a "No sensor data yet (try again in a few moments)" message. Why?
It takes about 1.5 seconds for the LM78 to update all its sensor
values. If we would try to read it before it finished that, you would get
old garbage instead. So you have to wait 1.5 seconds after the module is
inserted before you can access @file{/proc/sensors}.
Module versions 1.3.7 and later let the process sleep if it tries
to access sensor data right after insertion time, and do not display this
message anymore.
@node Section 7.4, , Section 7.3, Version 1 Specifics
@section On my Dell, a LM80 is detected, but all readings are 0!
This is a bug we have only observed on Dell computers. There is
probably a problem with the way the SMBus is accessed; but it is not yet
clear whether the problem is in our code or with the Dells.
There are very probably no sensor chips at all on your computer;
but until somebody contacts Dell about this and tells us the results, we
can not be sure.
@node Document Revisions, , Version 1 Specifics, Top
@node Document Revisions, , Contribute, Top
@appendix Revision History of This Document
@itemize
@item Rev 2.18 (JD) Removed version 1 specifics part, 2005-12-17
@item Rev 2.17 (JD) Added 5.9 (why we don't support undocumented chips),
removed 6.9 (doesn't apply to the new mailing list), 2005-10-05
@item Rev 2.16 (JD) Added 4.33.2, 2005-09-06
doc/version.texi
+2 -2
View File
@@ -1,2 +1,2 @@
@set UPDATED 5 October 2005
@set VERSION 2.17
@set UPDATED 17 December 2005
@set VERSION 2.18