Changeset 2114

Show
Ignore:
Timestamp:
11/29/03 20:36:27 (11 years ago)
Author:
mds
Message:

add item on registering for announcements via freshmeat

Location:
lm-sensors/trunk/doc
Files:
3 modified

Legend:

Unmodified
Added
Removed
  • lm-sensors/trunk/doc/FAQ

    r1968 r2114  
     1START-INFO-DIR-ENTRY 
     2* lm_sensors-FAQ: (lm_sensors-FAQ)           The lm_sensors FAQ 
     3END-INFO-DIR-ENTRY 
     4 
     5Short Contents 
     6************** 
     7 
     8lm_sensors 
     91 PC and Sensor Overview 
     102 Sensor and Bus Basics 
     113 Installation and Management 
     124 Problems 
     135 How to Ask for Help 
     146 How to Contribute 
     157 Version 1 Specific Questions 
     16Appendix A Revision History of This Document 
     17 
     18 
    119Table of Contents 
    220***************** 
     
    117135  6.6 How to submit a patch 
    118136  6.7 How to REALLY help 
    119   6.8 How to block spam on the project mailing list 
     137  6.8 How to get release announcements 
     138  6.9 How to block spam on the project mailing list 
    120139 
    1211407 Version 1 Specific Questions 
     
    13651384experience necessary :) 
    13661385 
    1367 6.8 How to block spam on the project mailing list 
     13866.8 How to get release announcements 
     1387==================================== 
     1388 
     1389   We don't have a separate release announcement mailing list; however, 
     1390we put all our releases on freshmeat: `http://freshmeat.net' and you 
     1391can register on our freshmeat project page 
     1392`http://freshmeat.net/projects/lm_sensors' to 'subscribe to new 
     1393releases' and then freshmeat will email you announcement. 
     1394 
     13956.9 How to block spam on the project mailing list 
    13681396================================================= 
    13691397 
     
    14851513 
    14861514   * Rev 1.0 Written by Philip Edelbrock, 19980803 
    1487  
  • lm-sensors/trunk/doc/lm_sensors-FAQ.html

    r1968 r2114  
    1 <html lang="en"><head> 
     1<html lang="en"> 
     2<head> 
    23<title>Sensors FAQ for lm_sensors version 2.9</title> 
    34<meta http-equiv="Content-Type" content="text/html"> 
    45<meta name=description content="Sensors FAQ for lm_sensors version 2.9"> 
    5 <meta name=generator content="makeinfo 4.0"> 
    6 <link href="http://texinfo.org/" rel=generator-home> 
    7 </head><body> 
    8  
    9 <p>C<p>opyright (c) 1998 - 2002<br> 
     6<meta name=generator content="makeinfo 4.2"> 
     7<link href="http://www.gnu.org/software/texinfo/" rel=generator-home> 
     8</head> 
     9<body> 
     10<h1>Sensors FAQ for lm_sensors version 2.9</h1> 
     11Copyright (c) 1998 - 2002<br> 
    1012<a href="mailto:frodol@dds.nl">Frodo Looijaard</a>,<br> 
    1113<a href="mailto:phil@netroedge.com">Philip Edelbrock</a>,<br> 
     
    1416 
    1517 
    16 <h1>Table of Contents</h1> 
    17 <ul> 
    18 <li><a href="#Top">lm_sensors</a> 
    19 <li><a href="#Overview">1 PC and Sensor Overview</a> 
     18<h2>Short Contents</h2> 
     19<ul> 
     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 
     32<h2>Table of Contents</h2> 
     33<ul> 
     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> 
    2038<ul> 
    2139<li><a href="#Section%201.1">1.1 What sensors are available on my PC?</a> 
     
    2341<li><a href="#Section%201.3">1.3 Where do I find out more about any of these chips?</a> 
    2442</ul> 
    25 <li><a href="#Basics">2 Sensor and Bus Basics</a> 
     43<li><a name="toc_Basics"></a> 
     44    <a href="#Basics">2 Sensor and Bus Basics</a> 
    2645<ul> 
    2746<li><a href="#Section%202.1">2.1 How are these sensors read?</a> 
     
    3251<li><a href="#Section%202.6">2.6 How are alarms triggered?</a> 
    3352</ul> 
    34 <li><a href="#Installation">3 Installation and Management</a> 
     53<li><a name="toc_Installation"></a> 
     54    <a href="#Installation">3 Installation and Management</a> 
    3555<ul> 
    3656<li><a href="#Section%203.1">3.1 Why so many modules, and how do I cope with them?</a> 
     
    6282<li><a href="#Section%203.10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a> 
    6383</ul> 
    64 <li><a href="#Problems">4 Problems</a> 
     84<li><a name="toc_Problems"></a> 
     85    <a href="#Problems">4 Problems</a> 
    6586<ul> 
    6687<li><a href="#Section%204.1">4.1 My fans report exactly half/double their values compared to the BIOS?</a> 
     
    135156<li><a href="#Section%204.32">4.32 Problems on particular systems</a> 
    136157</ul> 
    137 <li><a href="#Help">5 How to Ask for Help</a> 
     158<li><a name="toc_Help"></a> 
     159    <a href="#Help">5 How to Ask for Help</a> 
    138160<ul> 
    139161<li><a href="#Section%205.1">5.1 What to send us when asking for help</a> 
     
    146168<li><a href="#Section%205.8">5.8 How do I follow up on a ticket?</a> 
    147169</ul> 
    148 <li><a href="#Contribute">6 How to Contribute</a> 
     170<li><a name="toc_Contribute"></a> 
     171    <a href="#Contribute">6 How to Contribute</a> 
    149172<ul> 
    150173<li><a href="#Section%206.1">6.1 How to write a driver</a> 
     
    155178<li><a href="#Section%206.6">6.6 How to submit a patch</a> 
    156179<li><a href="#Section%206.7">6.7 How to REALLY help</a> 
    157 <li><a href="#Section%206.8">6.8 How to block spam on the project mailing list</a> 
    158 </ul> 
    159 <li><a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
     180<li><a href="#Section%206.8">6.8 How to get release announcements</a> 
     181<li><a href="#Section%206.9">6.9 How to block spam on the project mailing list</a> 
     182</ul> 
     183<li><a name="toc_Version%201%20Specifics"></a> 
     184    <a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
    160185<ul> 
    161186<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> 
     
    164189<li><a href="#Section%207.4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a> 
    165190</ul> 
    166 <li><a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
     191<li><a name="toc_Document%20Revisions"></a> 
     192    <a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
    167193</ul> 
    168194 
    169195<p><hr> 
    170196Node:<a name="Top">Top</a>, 
    171 Next:<a rel=next href="#Overview">Overview</a>, 
    172 Up:<a rel=up href="#(dir)">(dir)</a> 
    173 <br> 
    174  
    175 <h1>lm_sensors</h1> 
     197Next:<a rel=next accesskey=n href="#Overview">Overview</a>, 
     198Up:<a rel=up accesskey=u href="#dir">(dir)</a> 
     199<br> 
     200 
     201<h2>lm_sensors</h2> 
    176202 
    177203<p>The lm_sensors package includes a collection of modules for general SMBus 
     
    180206 
    181207<ul> 
    182 <li><a href="#Overview">Overview</a>:                 PC and Sensor Overview 
    183 <li><a href="#Basics">Basics</a>:                   Sensor and Bus Basics 
    184 <li><a href="#Installation">Installation</a>:             Installation and Management 
    185 <li><a href="#Problems">Problems</a>:                 Problems 
    186 <li><a href="#Help">Help</a>:                     How to Ask for Help 
    187 <li><a href="#Contribute">Contribute</a>:               How to Contribute 
    188 <li><a href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
    189 <li><a href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
     208<li><a accesskey=1 href="#Overview">Overview</a>:                 PC and Sensor Overview 
     209<li><a accesskey=2 href="#Basics">Basics</a>:                   Sensor and Bus Basics 
     210<li><a accesskey=3 href="#Installation">Installation</a>:             Installation and Management 
     211<li><a accesskey=4 href="#Problems">Problems</a>:                 Problems 
     212<li><a accesskey=5 href="#Help">Help</a>:                     How to Ask for Help 
     213<li><a accesskey=6 href="#Contribute">Contribute</a>:               How to Contribute 
     214<li><a accesskey=7 href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
     215<li><a accesskey=8 href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
    190216</ul> 
    191217 
    192218<p><hr> 
    193219Node:<a name="Overview">Overview</a>, 
    194 Next:<a rel=next href="#Basics">Basics</a>, 
    195 Previous:<a rel=previous href="#Top">Top</a>, 
    196 Up:<a rel=up href="#Top">Top</a> 
    197 <br> 
    198  
    199 <h1>1 PC and Sensor Overview</h1> 
    200  
    201 <ul> 
    202 <li><a href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
    203 <li><a href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
    204 <li><a href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
     220Next:<a rel=next accesskey=n href="#Basics">Basics</a>, 
     221Previous:<a rel=previous accesskey=p href="#Top">Top</a>, 
     222Up:<a rel=up accesskey=u href="#Top">Top</a> 
     223<br> 
     224 
     225<h2>1 PC and Sensor Overview</h2> 
     226 
     227<ul> 
     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?  
    205231</ul> 
    206232 
    207233<p><hr> 
    208234Node:<a name="Section%201.1">Section 1.1</a>, 
    209 Next:<a rel=next href="#Section%201.2">Section 1.2</a>, 
    210 Up:<a rel=up href="#Overview">Overview</a> 
    211 <br> 
    212  
    213 <h2>1.1 What sensors are available on my PC?</h2> 
     235Next:<a rel=next accesskey=n href="#Section%201.2">Section 1.2</a>, 
     236Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
     237<br> 
     238 
     239<h3>1.1 What sensors are available on my PC?</h3> 
    214240 
    215241<p>Most PC's built since late 1997 now come with a 
     
    226252<p><hr> 
    227253Node:<a name="Section%201.2">Section 1.2</a>, 
    228 Next:<a rel=next href="#Section%201.3">Section 1.3</a>, 
    229 Previous:<a rel=previous href="#Section%201.1">Section 1.1</a>, 
    230 Up:<a rel=up href="#Overview">Overview</a> 
    231 <br> 
    232  
    233 <h2>1.2 What can a sensor chip like the "LM78" do?</h2> 
     254Next:<a rel=next accesskey=n href="#Section%201.3">Section 1.3</a>, 
     255Previous:<a rel=previous accesskey=p href="#Section%201.1">Section 1.1</a>, 
     256Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
     257<br> 
     258 
     259<h3>1.2 What can a sensor chip like the "LM78" do?</h3> 
    234260 
    235261<p>The LM78 is a chip made by National Semiconductor which can monitor 7 
     
    254280<p><hr> 
    255281Node:<a name="Section%201.3">Section 1.3</a>, 
    256 Previous:<a rel=previous href="#Section%201.2">Section 1.2</a>, 
    257 Up:<a rel=up href="#Overview">Overview</a> 
    258 <br> 
    259  
    260 <h2>1.3 Where do I find out more about any of these chips?</h2> 
     282Previous:<a rel=previous accesskey=p href="#Section%201.2">Section 1.2</a>, 
     283Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
     284<br> 
     285 
     286<h3>1.3 Where do I find out more about any of these chips?</h3> 
    261287 
    262288<p>Most semiconductor companies have comprehensive documentation, 
     
    277303<p><hr> 
    278304Node:<a name="Basics">Basics</a>, 
    279 Next:<a rel=next href="#Installation">Installation</a>, 
    280 Previous:<a rel=previous href="#Overview">Overview</a>, 
    281 Up:<a rel=up href="#Top">Top</a> 
    282 <br> 
    283  
    284 <h1>2 Sensor and Bus Basics</h1> 
    285  
    286 <ul> 
    287 <li><a href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
    288 <li><a href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
    289 <li><a href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
    290 <li><a href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
    291 <li><a href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
    292 <li><a href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
     305Next:<a rel=next accesskey=n href="#Installation">Installation</a>, 
     306Previous:<a rel=previous accesskey=p href="#Overview">Overview</a>, 
     307Up:<a rel=up accesskey=u href="#Top">Top</a> 
     308<br> 
     309 
     310<h2>2 Sensor and Bus Basics</h2> 
     311 
     312<ul> 
     313<li><a accesskey=1 href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
     314<li><a accesskey=2 href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
     315<li><a accesskey=3 href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
     316<li><a accesskey=4 href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
     317<li><a accesskey=5 href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
     318<li><a accesskey=6 href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
    293319</ul> 
    294320 
    295321<p><hr> 
    296322Node:<a name="Section%202.1">Section 2.1</a>, 
    297 Next:<a rel=next href="#Section%202.2">Section 2.2</a>, 
    298 Up:<a rel=up href="#Basics">Basics</a> 
    299 <br> 
    300  
    301 <h2>2.1 How are these sensors read?</h2> 
     323Next:<a rel=next accesskey=n href="#Section%202.2">Section 2.2</a>, 
     324Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     325<br> 
     326 
     327<h3>2.1 How are these sensors read?</h3> 
    302328 
    303329<p>Sensor chips reside on either the ISA bus, the SMBus, or both.  
     
    312338<p><hr> 
    313339Node:<a name="Section%202.2">Section 2.2</a>, 
    314 Next:<a rel=next href="#Section%202.3">Section 2.3</a>, 
    315 Previous:<a rel=previous href="#Section%202.1">Section 2.1</a>, 
    316 Up:<a rel=up href="#Basics">Basics</a> 
    317 <br> 
    318  
    319 <h2>2.2 What is the SMBus? And the I2C bus?</h2> 
     340Next:<a rel=next accesskey=n href="#Section%202.3">Section 2.3</a>, 
     341Previous:<a rel=previous accesskey=p href="#Section%202.1">Section 2.1</a>, 
     342Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     343<br> 
     344 
     345<h3>2.2 What is the SMBus? And the I2C bus?</h3> 
    320346 
    321347<p>The SMBus is the "System Management Bus".  More specifically, it is a 
     
    339365<p><hr> 
    340366Node:<a name="Section%202.3">Section 2.3</a>, 
    341 Next:<a rel=next href="#Section%202.4">Section 2.4</a>, 
    342 Previous:<a rel=previous href="#Section%202.2">Section 2.2</a>, 
    343 Up:<a rel=up href="#Basics">Basics</a> 
    344 <br> 
    345  
    346 <h2>2.3 I don't have an ISA bus!</h2> 
     367Next:<a rel=next accesskey=n href="#Section%202.4">Section 2.4</a>, 
     368Previous:<a rel=previous accesskey=p href="#Section%202.2">Section 2.2</a>, 
     369Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     370<br> 
     371 
     372<h3>2.3 I don't have an ISA bus!</h3> 
    347373 
    348374<p>We promise, you do, even if you don't have any old ISA slots.  
     
    357383<p><hr> 
    358384Node:<a name="Section%202.4">Section 2.4</a>, 
    359 Next:<a rel=next href="#Section%202.5">Section 2.5</a>, 
    360 Previous:<a rel=previous href="#Section%202.3">Section 2.3</a>, 
    361 Up:<a rel=up href="#Basics">Basics</a> 
    362 <br> 
    363  
    364 <h2>2.4 What sensors do processors have?</h2> 
     385Next:<a rel=next accesskey=n href="#Section%202.5">Section 2.5</a>, 
     386Previous:<a rel=previous accesskey=p href="#Section%202.3">Section 2.3</a>, 
     387Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     388<br> 
     389 
     390<h3>2.4 What sensors do processors have?</h3> 
    365391 
    366392<p>Most new processors contain a thermal diode on the die itself.  
     
    398424<p><hr> 
    399425Node:<a name="Section%202.5">Section 2.5</a>, 
    400 Next:<a rel=next href="#Section%202.6">Section 2.6</a>, 
    401 Previous:<a rel=previous href="#Section%202.4">Section 2.4</a>, 
    402 Up:<a rel=up href="#Basics">Basics</a> 
    403 <br> 
    404  
    405 <h2>2.5 How often are the sensor values updated?</h2> 
     426Next:<a rel=next accesskey=n href="#Section%202.6">Section 2.6</a>, 
     427Previous:<a rel=previous accesskey=p href="#Section%202.4">Section 2.4</a>, 
     428Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     429<br> 
     430 
     431<h3>2.5 How often are the sensor values updated?</h3> 
    406432 
    407433<p>The LM78, and most other sensor chips like it, reads its sensors one 
     
    415441<p><hr> 
    416442Node:<a name="Section%202.6">Section 2.6</a>, 
    417 Previous:<a rel=previous href="#Section%202.5">Section 2.5</a>, 
    418 Up:<a rel=up href="#Basics">Basics</a> 
    419 <br> 
    420  
    421 <h2>2.6 How are alarms triggered?</h2> 
     443Previous:<a rel=previous accesskey=p href="#Section%202.5">Section 2.5</a>, 
     444Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
     445<br> 
     446 
     447<h3>2.6 How are alarms triggered?</h3> 
    422448 
    423449<p>It is possible to monitor each sensor and have an alarm go off if 
     
    440466<p><hr> 
    441467Node:<a name="Installation">Installation</a>, 
    442 Next:<a rel=next href="#Problems">Problems</a>, 
    443 Previous:<a rel=previous href="#Basics">Basics</a>, 
    444 Up:<a rel=up href="#Top">Top</a> 
    445 <br> 
    446  
    447 <h1>3 Installation and Management</h1> 
    448  
    449 <ul> 
    450 <li><a href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
    451 <li><a href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
    452 <li><a href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
    453 <li><a href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
    454 <li><a href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
    455 <li><a href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
    456 <li><a href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
    457 <li><a href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
    458 <li><a href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
     468Next:<a rel=next accesskey=n href="#Problems">Problems</a>, 
     469Previous:<a rel=previous accesskey=p href="#Basics">Basics</a>, 
     470Up:<a rel=up accesskey=u href="#Top">Top</a> 
     471<br> 
     472 
     473<h2>3 Installation and Management</h2> 
     474 
     475<ul> 
     476<li><a accesskey=1 href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
     477<li><a accesskey=2 href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
     478<li><a accesskey=3 href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
     479<li><a accesskey=4 href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
     480<li><a accesskey=5 href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
     481<li><a accesskey=6 href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
     482<li><a accesskey=7 href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
     483<li><a accesskey=8 href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
     484<li><a accesskey=9 href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
    459485<li><a href="#Section%203.10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
    460486</ul> 
     
    462488<p><hr> 
    463489Node:<a name="Section%203.1">Section 3.1</a>, 
    464 Next:<a rel=next href="#Section%203.2">Section 3.2</a>, 
    465 Up:<a rel=up href="#Installation">Installation</a> 
    466 <br> 
    467  
    468 <h2>3.1 Why so many modules, and how do I cope with them?</h2> 
     490Next:<a rel=next accesskey=n href="#Section%203.2">Section 3.2</a>, 
     491Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     492<br> 
     493 
     494<h3>3.1 Why so many modules, and how do I cope with them?</h3> 
    469495 
    470496<p>We tried to make this package as modular as possible. This makes it 
     
    483509<p><hr> 
    484510Node:<a name="Section%203.2">Section 3.2</a>, 
    485 Next:<a rel=next href="#Section%203.3">Section 3.3</a>, 
    486 Previous:<a rel=previous href="#Section%203.1">Section 3.1</a>, 
    487 Up:<a rel=up href="#Installation">Installation</a> 
    488 <br> 
    489  
    490 <h2>3.2 How do I know which chips I own?</h2> 
     511Next:<a rel=next accesskey=n href="#Section%203.3">Section 3.3</a>, 
     512Previous:<a rel=previous accesskey=p href="#Section%203.1">Section 3.1</a>, 
     513Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     514<br> 
     515 
     516<h3>3.2 How do I know which chips I own?</h3> 
    491517 
    492518<p>We have an excellent program that scans all your hardware.  
     
    504530<p><a name="Section%203.2.1"></a> 
    505531 
    506 <h3>3.2.1 What chips are on motherboard XYZ?</h3> 
     532<h4>3.2.1 What chips are on motherboard XYZ?</h4> 
    507533 
    508534<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong> 
     
    524550<p><a name="Section%203.2.2"></a> 
    525551 
    526 <h3>3.2.2 Do you support motherboard XYZ?</h3> 
     552<h4>3.2.2 Do you support motherboard XYZ?</h4> 
    527553 
    528554<p>We don't support boards, we support chips. See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
     
    530556<p><a name="Section%203.2.3"></a> 
    531557 
    532 <h3>3.2.3 Do you support chip XYZ?</h3> 
     558<h4>3.2.3 Do you support chip XYZ?</h4> 
    533559 
    534560<p>This we have good answers for. 
     
    542568<p><a name="Section%203.2.4"></a> 
    543569 
    544 <h3>3.2.4 Anybody working on a driver for chip XYZ?</h3> 
     570<h4>3.2.4 Anybody working on a driver for chip XYZ?</h4> 
    545571 
    546572<p>Newest Driver Status: <a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html</a> 
     
    548574<p><hr> 
    549575Node:<a name="Section%203.3">Section 3.3</a>, 
    550 Next:<a rel=next href="#Section%203.4">Section 3.4</a>, 
    551 Previous:<a rel=previous href="#Section%203.2">Section 3.2</a>, 
    552 Up:<a rel=up href="#Installation">Installation</a> 
    553 <br> 
    554  
    555 <h2>3.3 Which modules should I insert?</h2> 
     576Next:<a rel=next accesskey=n href="#Section%203.4">Section 3.4</a>, 
     577Previous:<a rel=previous accesskey=p href="#Section%203.2">Section 3.2</a>, 
     578Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     579<br> 
     580 
     581<h3>3.3 Which modules should I insert?</h3> 
    556582 
    557583<p><code>sensors-detect</code> will tell you. Take the <code>modprobe</code> lines it 
     
    574600<p><hr> 
    575601Node:<a name="Section%203.4">Section 3.4</a>, 
    576 Next:<a rel=next href="#Section%203.5">Section 3.5</a>, 
    577 Previous:<a rel=previous href="#Section%203.3">Section 3.3</a>, 
    578 Up:<a rel=up href="#Installation">Installation</a> 
    579 <br> 
    580  
    581 <h2>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h2> 
     602Next:<a rel=next accesskey=n href="#Section%203.5">Section 3.5</a>, 
     603Previous:<a rel=previous accesskey=p href="#Section%203.3">Section 3.3</a>, 
     604Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     605<br> 
     606 
     607<h3>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h3> 
    582608 
    583609<p>Yes, for any applications that use <code>libsensors,</code> including the 
     
    591617<p><a name="Section%203.4.1"></a> 
    592618 
    593 <h3>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h3> 
     619<h4>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h4> 
    594620 
    595621<p>Every motherboard is different. You can customize the labels 
     
    600626<p><a name="Section%203.4.2"></a> 
    601627 
    602 <h3>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h3> 
     628<h4>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h4> 
    603629 
    604630<p>You can customize them in the file <code>/etc/sensors.conf</code>. See above. 
     
    606632<p><a name="Section%203.4.3"></a> 
    607633 
    608 <h3>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h3> 
     634<h4>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h4> 
    609635 
    610636<p>You forgot to run <code>sensors -s</code>. See above. 
     
    612638<p><a name="Section%203.4.4"></a> 
    613639 
    614 <h3>3.4.4 One sensor isn't hooked up on my board!</h3> 
     640<h4>3.4.4 One sensor isn't hooked up on my board!</h4> 
    615641 
    616642<p>Use an <code>ignore</code> line in <code>/etc/sensors.conf</code> so it isn't 
     
    619645<p><a name="Section%203.4.5"></a> 
    620646 
    621 <h3>3.4.5 I need help with <code>sensors.conf</code>!</h3> 
     647<h4>3.4.5 I need help with <code>sensors.conf</code>!</h4> 
    622648 
    623649<p>There is detailed help at the top of that file. 
     
    625651<p><a name="Section%203.4.6"></a> 
    626652 
    627 <h3>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h3> 
     653<h4>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h4> 
    628654 
    629655<p>No. Good idea though. If you would like to set one up on your website 
     
    632658<p><hr> 
    633659Node:<a name="Section%203.5">Section 3.5</a>, 
    634 Next:<a rel=next href="#Section%203.6">Section 3.6</a>, 
    635 Previous:<a rel=previous href="#Section%203.4">Section 3.4</a>, 
    636 Up:<a rel=up href="#Installation">Installation</a> 
    637 <br> 
    638  
    639 <h2>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h2> 
     660Next:<a rel=next accesskey=n href="#Section%203.6">Section 3.6</a>, 
     661Previous:<a rel=previous accesskey=p href="#Section%203.4">Section 3.4</a>, 
     662Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     663<br> 
     664 
     665<h3>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h3> 
    640666 
    641667<p>Don't worry about them. The dependency files (which tell which 
     
    647673<p><hr> 
    648674Node:<a name="Section%203.6">Section 3.6</a>, 
    649 Next:<a rel=next href="#Section%203.7">Section 3.7</a>, 
    650 Previous:<a rel=previous href="#Section%203.5">Section 3.5</a>, 
    651 Up:<a rel=up href="#Installation">Installation</a> 
    652 <br> 
    653  
    654 <h2>3.6 I get all kinds of weird compilation errors?</h2> 
     675Next:<a rel=next accesskey=n href="#Section%203.7">Section 3.7</a>, 
     676Previous:<a rel=previous accesskey=p href="#Section%203.5">Section 3.5</a>, 
     677Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     678<br> 
     679 
     680<h3>3.6 I get all kinds of weird compilation errors?</h3> 
    655681 
    656682<p>Check that the correct i2c header files are used. Depending on 
     
    660686<p><a name="Section%203.6.1"></a> 
    661687 
    662 <h3>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h3> 
     688<h4>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h4> 
    663689 
    664690<ul> 
     
    671697<p><hr> 
    672698Node:<a name="Section%203.7">Section 3.7</a>, 
    673 Next:<a rel=next href="#Section%203.8">Section 3.8</a>, 
    674 Previous:<a rel=previous href="#Section%203.6">Section 3.6</a>, 
    675 Up:<a rel=up href="#Installation">Installation</a> 
    676 <br> 
    677  
    678 <h2>3.7 It still does not compile or patch!</h2> 
     699Next:<a rel=next accesskey=n href="#Section%203.8">Section 3.8</a>, 
     700Previous:<a rel=previous accesskey=p href="#Section%203.6">Section 3.6</a>, 
     701Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     702<br> 
     703 
     704<h3>3.7 It still does not compile or patch!</h3> 
    679705 
    680706<p>Have you installed the matching version of the i2c package? Remember, 
     
    687713<p><hr> 
    688714Node:<a name="Section%203.8">Section 3.8</a>, 
    689 Next:<a rel=next href="#Section%203.9">Section 3.9</a>, 
    690 Previous:<a rel=previous href="#Section%203.7">Section 3.7</a>, 
    691 Up:<a rel=up href="#Installation">Installation</a> 
    692 <br> 
    693  
    694 <h2>3.8 <code>make install</code> fails on Mandrake kernels</h2> 
     715Next:<a rel=next accesskey=n href="#Section%203.9">Section 3.9</a>, 
     716Previous:<a rel=previous accesskey=p href="#Section%203.7">Section 3.7</a>, 
     717Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     718<br> 
     719 
     720<h3>3.8 <code>make install</code> fails on Mandrake kernels</h3> 
    695721 
    696722<p>Mandrake uses a non-standard <code>version.h</code> file which confuses our <code>Makefile</code>.  
     
    699725<p><hr> 
    700726Node:<a name="Section%203.9">Section 3.9</a>, 
    701 Next:<a rel=next href="#Section%203.10">Section 3.10</a>, 
    702 Previous:<a rel=previous href="#Section%203.8">Section 3.8</a>, 
    703 Up:<a rel=up href="#Installation">Installation</a> 
    704 <br> 
    705  
    706 <h2>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h2> 
     727Next:<a rel=next accesskey=n href="#Section%203.10">Section 3.10</a>, 
     728Previous:<a rel=previous accesskey=p href="#Section%203.8">Section 3.8</a>, 
     729Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     730<br> 
     731 
     732<h3>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h3> 
    707733 
    708734<p>Example: 
    709 <pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
     735<br><pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
    710736i2c_bit_add_bus_R8c3bc60e 
    711737i2c_bit_del_bus_R92b18f49 
     
    737763<p><hr> 
    738764Node:<a name="Section%203.10">Section 3.10</a>, 
    739 Previous:<a rel=previous href="#Section%203.9">Section 3.9</a>, 
    740 Up:<a rel=up href="#Installation">Installation</a> 
    741 <br> 
    742  
    743 <h2>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h2> 
     765Previous:<a rel=previous accesskey=p href="#Section%203.9">Section 3.9</a>, 
     766Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
     767<br> 
     768 
     769<h3>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3> 
    744770 
    745771<p>In some versions of Redhat, an RPM is included to provide i2c support.  
     
    758784old i2c stuff anymore anyway.  Just don't use it with abandon.  
    759785<li>Try (in the build directory of <code>lm_sensors)</code> 
    760 <pre><code>make clean</code> 
     786<br><pre><code>make clean</code> 
    761787<code>make</code> 
    762788</pre> 
     
    769795<p><hr> 
    770796Node:<a name="Problems">Problems</a>, 
    771 Next:<a rel=next href="#Help">Help</a>, 
    772 Previous:<a rel=previous href="#Installation">Installation</a>, 
    773 Up:<a rel=up href="#Top">Top</a> 
    774 <br> 
    775  
    776 <h1>4 Problems</h1> 
    777  
    778 <ul> 
    779 <li><a href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
    780 <li><a href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
    781 <li><a href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
    782 <li><a href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
    783 <li><a href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
    784 <li><a href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
    785 <li><a href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
    786 <li><a href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
    787 <li><a href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
     797Next:<a rel=next accesskey=n href="#Help">Help</a>, 
     798Previous:<a rel=previous accesskey=p href="#Installation">Installation</a>, 
     799Up:<a rel=up accesskey=u href="#Top">Top</a> 
     800<br> 
     801 
     802<h2>4 Problems</h2> 
     803 
     804<ul> 
     805<li><a accesskey=1 href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
     806<li><a accesskey=2 href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
     807<li><a accesskey=3 href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
     808<li><a accesskey=4 href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
     809<li><a accesskey=5 href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
     810<li><a accesskey=6 href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
     811<li><a accesskey=7 href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
     812<li><a accesskey=8 href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
     813<li><a accesskey=9 href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
    788814<li><a href="#Section%204.10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?  
    789815<li><a href="#Section%204.11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?  
     
    813839<p><hr> 
    814840Node:<a name="Section%204.1">Section 4.1</a>, 
    815 Next:<a rel=next href="#Section%204.2">Section 4.2</a>, 
    816 Up:<a rel=up href="#Problems">Problems</a> 
    817 <br> 
    818  
    819 <h2>4.1 My fans report exactly half/double their values compared to the BIOS?</h2> 
     841Next:<a rel=next accesskey=n href="#Section%204.2">Section 4.2</a>, 
     842Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     843<br> 
     844 
     845<h3>4.1 My fans report exactly half/double their values compared to the BIOS?</h3> 
    820846 
    821847<p>The problem with much of the sensor data is that it is impossible to 
     
    825851configuration file <code>/etc/sensors.conf</code>: 
    826852 
    827 <pre>chip lm78-*             # Or whatever chip this relates to 
     853<br><pre>chip lm78-*             # Or whatever chip this relates to 
    828854compute fan1 2*@,@/2    # This will double the fan1 reading 
    829855                        # -- or -- 
     
    835861<p><a name="Fans%20sometimes%2falways%20read%200!"></a> 
    836862 
    837 <h3>4.1.1 Fans sometimes/always read 0!!</h3> 
     863<h4>4.1.1 Fans sometimes/always read 0!!</h4> 
    838864 
    839865<p>You may not have a three-wire fan, which is required. 
     
    844870<p><a name="I%20doubled%20the%20fan%20divisor%20and%20the%20fan%20still%20reads%207000"></a> 
    845871 
    846 <h3>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h3> 
     872<h4>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4> 
    847873 
    848874<p>Believe it or not, doubling the 'fan divisor' will not halve 
     
    853879<p><hr> 
    854880Node:<a name="Section%204.2">Section 4.2</a>, 
    855 Next:<a rel=next href="#Section%204.3">Section 4.3</a>, 
    856 Previous:<a rel=previous href="#Section%204.1">Section 4.1</a>, 
    857 Up:<a rel=up href="#Problems">Problems</a> 
    858 <br> 
    859  
    860 <h2>4.2 Why do my two LM75's report "-48 degrees"?</h2> 
     881Next:<a rel=next accesskey=n href="#Section%204.3">Section 4.3</a>, 
     882Previous:<a rel=previous accesskey=p href="#Section%204.1">Section 4.1</a>, 
     883Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     884<br> 
     885 
     886<h3>4.2 Why do my two LM75's report "-48 degrees"?</h3> 
    861887 
    862888<p>For starters, those aren't LM75's.  Your mainboard actually has the 
     
    873899<p><hr> 
    874900Node:<a name="Section%204.3">Section 4.3</a>, 
    875 Next:<a rel=next href="#Section%204.4">Section 4.4</a>, 
    876 Previous:<a rel=previous href="#Section%204.2">Section 4.2</a>, 
    877 Up:<a rel=up href="#Problems">Problems</a> 
    878 <br> 
    879  
    880 <h2>4.3 Why do I have two Vcore readings, I have only one processor!</h2> 
     901Next:<a rel=next accesskey=n href="#Section%204.4">Section 4.4</a>, 
     902Previous:<a rel=previous accesskey=p href="#Section%204.2">Section 4.2</a>, 
     903Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     904<br> 
     905 
     906<h3>4.3 Why do I have two Vcore readings, I have only one processor!</h3> 
    881907 
    882908<p>The LM78 has seven voltage sensors. The default way of 
     
    895921<p><hr> 
    896922Node:<a name="Section%204.4">Section 4.4</a>, 
    897 Next:<a rel=next href="#Section%204.5">Section 4.5</a>, 
    898 Previous:<a rel=previous href="#Section%204.3">Section 4.3</a>, 
    899 Up:<a rel=up href="#Problems">Problems</a> 
    900 <br> 
    901  
    902 <h2>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h2> 
     923Next:<a rel=next accesskey=n href="#Section%204.5">Section 4.5</a>, 
     924Previous:<a rel=previous accesskey=p href="#Section%204.3">Section 4.3</a>, 
     925Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     926<br> 
     927 
     928<h3>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3> 
    903929 
    904930<p>The ALARM indications in <code>sensors</code> are those reported by the 
     
    924950<p><hr> 
    925951Node:<a name="Section%204.5">Section 4.5</a>, 
    926 Next:<a rel=next href="#Section%204.6">Section 4.6</a>, 
    927 Previous:<a rel=previous href="#Section%204.4">Section 4.4</a>, 
    928 Up:<a rel=up href="#Problems">Problems</a> 
    929 <br> 
    930  
    931 <h2>4.5 My voltage readings seem to drift a bit. Is something wrong?</h2> 
     952Next:<a rel=next accesskey=n href="#Section%204.6">Section 4.6</a>, 
     953Previous:<a rel=previous accesskey=p href="#Section%204.4">Section 4.4</a>, 
     954Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     955<br> 
     956 
     957<h3>4.5 My voltage readings seem to drift a bit. Is something wrong?</h3> 
    932958 
    933959<p>No, probably not. If your motherboard heats up a bit, the sensed 
     
    942968<p><hr> 
    943969Node:<a name="Section%204.6">Section 4.6</a>, 
    944 Next:<a rel=next href="#Section%204.7">Section 4.7</a>, 
    945 Previous:<a rel=previous href="#Section%204.5">Section 4.5</a>, 
    946 Up:<a rel=up href="#Problems">Problems</a> 
    947 <br> 
    948  
    949 <h2>4.6 Some measurements are way out of range. What happened?</h2> 
     970Next:<a rel=next accesskey=n href="#Section%204.7">Section 4.7</a>, 
     971Previous:<a rel=previous accesskey=p href="#Section%204.5">Section 4.5</a>, 
     972Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     973<br> 
     974 
     975<h3>4.6 Some measurements are way out of range. What happened?</h3> 
    950976 
    951977<p>Each module tries to set limits to sensible values on initialization, 
     
    963989<p><hr> 
    964990Node:<a name="Section%204.7">Section 4.7</a>, 
    965 Next:<a rel=next href="#Section%204.8">Section 4.8</a>, 
    966 Previous:<a rel=previous href="#Section%204.6">Section 4.6</a>, 
    967 Up:<a rel=up href="#Problems">Problems</a> 
    968 <br> 
    969  
    970 <h2>4.7 What are VID lines? Why is the VID reading wrong?</h2> 
     991Next:<a rel=next accesskey=n href="#Section%204.8">Section 4.8</a>, 
     992Previous:<a rel=previous accesskey=p href="#Section%204.6">Section 4.6</a>, 
     993Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     994<br> 
     995 
     996<h3>4.7 What are VID lines? Why is the VID reading wrong?</h3> 
    971997 
    972998<p>These describe the core voltage for your processor. They are 
     
    9801006<p><hr> 
    9811007Node:<a name="Section%204.8">Section 4.8</a>, 
    982 Next:<a rel=next href="#Section%204.9">Section 4.9</a>, 
    983 Previous:<a rel=previous href="#Section%204.7">Section 4.7</a>, 
    984 Up:<a rel=up href="#Problems">Problems</a> 
    985 <br> 
    986  
    987 <h2>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h2> 
     1008Next:<a rel=next accesskey=n href="#Section%204.9">Section 4.9</a>, 
     1009Previous:<a rel=previous accesskey=p href="#Section%204.7">Section 4.7</a>, 
     1010Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1011<br> 
     1012 
     1013<h3>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3> 
    9881014 
    9891015<p>If we would read the registers more often, it would not find the 
     
    9941020<p><hr> 
    9951021Node:<a name="Section%204.9">Section 4.9</a>, 
    996 Next:<a rel=next href="#Section%204.10">Section 4.10</a>, 
    997 Previous:<a rel=previous href="#Section%204.8">Section 4.8</a>, 
    998 Up:<a rel=up href="#Problems">Problems</a> 
    999 <br> 
    1000  
    1001 <h2>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h2> 
     1022Next:<a rel=next accesskey=n href="#Section%204.10">Section 4.10</a>, 
     1023Previous:<a rel=previous accesskey=p href="#Section%204.8">Section 4.8</a>, 
     1024Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1025<br> 
     1026 
     1027<h3>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3> 
    10021028 
    10031029<p>ISA bus access is fast, but SMBus access is really slow. If you have 
     
    10081034<p><hr> 
    10091035Node:<a name="Section%204.10">Section 4.10</a>, 
    1010 Next:<a rel=next href="#Section%204.11">Section 4.11</a>, 
    1011 Previous:<a rel=previous href="#Section%204.9">Section 4.9</a>, 
    1012 Up:<a rel=up href="#Problems">Problems</a> 
    1013 <br> 
    1014  
    1015 <h2>4.10 Can I be alerted when an ALARM occurs?</h2> 
     1036Next:<a rel=next accesskey=n href="#Section%204.11">Section 4.11</a>, 
     1037Previous:<a rel=previous accesskey=p href="#Section%204.9">Section 4.9</a>, 
     1038Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1039<br> 
     1040 
     1041<h3>4.10 Can I be alerted when an ALARM occurs?</h3> 
    10161042 
    10171043<p>No, you can't; and it may well be never supported. 
     
    10341060<p><hr> 
    10351061Node:<a name="Section%204.11">Section 4.11</a>, 
    1036 Next:<a rel=next href="#Section%204.12">Section 4.12</a>, 
    1037 Previous:<a rel=previous href="#Section%204.10">Section 4.10</a>, 
    1038 Up:<a rel=up href="#Problems">Problems</a> 
    1039 <br> 
    1040  
    1041 <h2>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h2> 
     1062Next:<a rel=next accesskey=n href="#Section%204.12">Section 4.12</a>, 
     1063Previous:<a rel=previous accesskey=p href="#Section%204.10">Section 4.10</a>, 
     1064Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1065<br> 
     1066 
     1067<h3>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3> 
    10421068 
    10431069<p>Some chips which mainboard makers connect to the SMBus are not SMBus 
     
    10531079<p><hr> 
    10541080Node:<a name="Section%204.12">Section 4.12</a>, 
    1055 Next:<a rel=next href="#Section%204.13">Section 4.13</a>, 
    1056 Previous:<a rel=previous href="#Section%204.11">Section 4.11</a>, 
    1057 Up:<a rel=up href="#Problems">Problems</a> 
    1058 <br> 
    1059  
    1060 <h2>4.12 My BIOS reports a much higher CPU temperature than your modules!</h2> 
     1081Next:<a rel=next accesskey=n href="#Section%204.13">Section 4.13</a>, 
     1082Previous:<a rel=previous accesskey=p href="#Section%204.11">Section 4.11</a>, 
     1083Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1084<br> 
     1085 
     1086<h3>4.12 My BIOS reports a much higher CPU temperature than your modules!</h3> 
    10611087 
    10621088<p>We display the actual temperature of the sensor. This may not be the 
     
    10681094in the module itself. You can do it through the configuration file, though: 
    10691095 
    1070 <pre>chip lm75-*-49                      # Or whatever chip this relates to 
     1096<br><pre>chip lm75-*-49                      # Or whatever chip this relates to 
    10711097label temp "Processor" 
    10721098compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula 
     
    10751101<p><hr> 
    10761102Node:<a name="Section%204.13">Section 4.13</a>, 
    1077 Next:<a rel=next href="#Section%204.14">Section 4.14</a>, 
    1078 Previous:<a rel=previous href="#Section%204.12">Section 4.12</a>, 
    1079 Up:<a rel=up href="#Problems">Problems</a> 
    1080 <br> 
    1081  
    1082 <h2>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h2> 
     1103Next:<a rel=next accesskey=n href="#Section%204.14">Section 4.14</a>, 
     1104Previous:<a rel=previous accesskey=p href="#Section%204.12">Section 4.12</a>, 
     1105Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1106<br> 
     1107 
     1108<h3>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h3> 
    10831109 
    10841110<p>Remember, these values do not take the configuration file 
     
    10891115<p><hr> 
    10901116Node:<a name="Section%204.14">Section 4.14</a>, 
    1091 Next:<a rel=next href="#Section%204.15">Section 4.15</a>, 
    1092 Previous:<a rel=previous href="#Section%204.13">Section 4.13</a>, 
    1093 Up:<a rel=up href="#Problems">Problems</a> 
    1094 <br> 
    1095  
    1096 <h2>4.14 How do I set new limits?</h2> 
     1117Next:<a rel=next accesskey=n href="#Section%204.15">Section 4.15</a>, 
     1118Previous:<a rel=previous accesskey=p href="#Section%204.13">Section 4.13</a>, 
     1119Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1120<br> 
     1121 
     1122<h3>4.14 How do I set new limits?</h3> 
    10971123 
    10981124<p>Change the limit values in <code>/etc/sensors.conf</code> and then run 
     
    11011127<p><a name="I%20set%20new%20limits%20and%20it%20didnt%20work"></a> 
    11021128 
    1103 <h3>4.14.1 I set new limits and it didn't work?</h3> 
     1129<h4>4.14.1 I set new limits and it didn't work?</h4> 
    11041130 
    11051131<p>You forgot to run <code>sensors -s</code>. Put it in a <code>/etc/rc.d/...</code> file 
     
    11081134<p><hr> 
    11091135Node:<a name="Section%204.15">Section 4.15</a>, 
    1110 Next:<a rel=next href="#Section%204.16">Section 4.16</a>, 
    1111 Previous:<a rel=previous href="#Section%204.14">Section 4.14</a>, 
    1112 Up:<a rel=up href="#Problems">Problems</a> 
    1113 <br> 
    1114  
    1115 <h2>4.15 Some sensors are doubly detected?</h2> 
     1136Next:<a rel=next accesskey=n href="#Section%204.16">Section 4.16</a>, 
     1137Previous:<a rel=previous accesskey=p href="#Section%204.14">Section 4.14</a>, 
     1138Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1139<br> 
     1140 
     1141<h3>4.15 Some sensors are doubly detected?</h3> 
    11161142 
    11171143<p>Yes, this is still a problem. It is partially solved by alias detection 
     
    11271153<p><hr> 
    11281154Node:<a name="Section%204.16">Section 4.16</a>, 
    1129 Next:<a rel=next href="#Section%204.17">Section 4.17</a>, 
    1130 Previous:<a rel=previous href="#Section%204.15">Section 4.15</a>, 
    1131 Up:<a rel=up href="#Problems">Problems</a> 
    1132 <br> 
    1133  
    1134 <h2>4.16 I ran sensors-detect, but now I get very strange readings?!?</h2> 
     1155Next:<a rel=next accesskey=n href="#Section%204.17">Section 4.17</a>, 
     1156Previous:<a rel=previous accesskey=p href="#Section%204.15">Section 4.15</a>, 
     1157Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1158<br> 
     1159 
     1160<h3>4.16 I ran sensors-detect, but now I get very strange readings?!?</h3> 
    11351161 
    11361162<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards 
     
    11441170<p><hr> 
    11451171Node:<a name="Section%204.17">Section 4.17</a>, 
    1146 Next:<a rel=next href="#Section%204.18">Section 4.18</a>, 
    1147 Previous:<a rel=previous href="#Section%204.16">Section 4.16</a>, 
    1148 Up:<a rel=up href="#Problems">Problems</a> 
    1149 <br> 
    1150  
    1151 <h2>4.17 Bad readings from particular chips</h2> 
     1172Next:<a rel=next accesskey=n href="#Section%204.18">Section 4.18</a>, 
     1173Previous:<a rel=previous accesskey=p href="#Section%204.16">Section 4.16</a>, 
     1174Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1175<br> 
     1176 
     1177<h3>4.17 Bad readings from particular chips</h3> 
    11521178 
    11531179<p>See below for some particularly troublesome chips.  
     
    11561182<p><a name="Bad%20readings%20from%20the%20AS99127F"></a> 
    11571183 
    1158 <h3>4.17.1 Bad readings from the AS99127F!</h3> 
     1184<h4>4.17.1 Bad readings from the AS99127F!</h4> 
    11591185 
    11601186<p>The Asus AS99127F is a modified version of the Winbond W83781D.  
     
    11661192<p><a name="Bad%20readings%20from%20the%20VIA%20686A"></a> 
    11671193 
    1168 <h3>4.17.2 Bad readings from the VIA 686A!</h3> 
     1194<h4>4.17.2 Bad readings from the VIA 686A!</h4> 
    11691195 
    11701196<p>The Via 686A datasheet is incomplete.  
     
    11771203<p><a name="Bad%20readings%20from%20the%20MTP008"></a> 
    11781204 
    1179 <h3>4.17.3 Bad readings from the MTP008!</h3> 
     1205<h4>4.17.3 Bad readings from the MTP008!</h4> 
    11801206 
    11811207<p>The MTP008 has programmable temperature sensor types.  
     
    11871213<p><a name="Bad%20temperature%20readings%20from%20the%20SIS5595"></a> 
    11881214 
    1189 <h3>4.17.4 Bad temperature readings from the SIS5595!</h3> 
     1215<h4>4.17.4 Bad temperature readings from the SIS5595!</h4> 
    11901216 
    11911217<p>This chip can use multiple thermistor types and there are also 
     
    11981224<p><a name="Bad%20readings%20from%20a%20w8378%5b12%5dd"></a> 
    11991225 
    1200 <h3>4.17.5 Bad readings from a w8378[12]d!</h3> 
     1226<h4>4.17.5 Bad readings from a w8378[12]d!</h4> 
    12011227 
    12021228<p>Do you own an ASUS motherboard?  Perhaps your chip is being 
     
    12121238<p><a name="Bus%20hangs%20on%20Ali%201543%20on%20Asus%20P5A%20boards"></a> 
    12131239 
    1214 <h3>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h3> 
     1240<h4>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4> 
    12151241 
    12161242<p>The SMBus tends to hang on this board and it seems to get worse 
     
    12211247<p><a name="Bad%20readings%20from%20LM75"></a> 
    12221248 
    1223 <h3>4.17.7 Bad readings from LM75!</h3> 
     1249<h4>4.17.7 Bad readings from LM75!</h4> 
    12241250 
    12251251<p>The LM75 detection is poor and other hardware is often misdetected 
     
    12281254<p><a name="Bad%20readings%20from%20LM78"></a> 
    12291255 
    1230 <h3>4.17.8 Bad readings from LM78!</h3> 
     1256<h4>4.17.8 Bad readings from LM78!</h4> 
    12311257 
    12321258<p>The LM78 is no longer manufactured by National Semiconductor.  
     
    12361262<p><a name="Bad%20readings%20from%20LM80"></a> 
    12371263 
    1238 <h3>4.17.9 Bad readings from LM80!</h3> 
     1264<h4>4.17.9 Bad readings from LM80!</h4> 
    12391265 
    12401266<p>The LM80 detection is poor and other hardware is often misdetected 
     
    12431269<p><a name="Bad%20readings%20from%20it87"></a> 
    12441270 
    1245 <h3>4.17.10 Bad readings from it87!</h3> 
     1271<h4>4.17.10 Bad readings from it87!</h4> 
    12461272 
    12471273<p>The it87 temperature sesnsors are configured, unfortunately, 
     
    12521278<p><hr> 
    12531279Node:<a name="Section%204.18">Section 4.18</a>, 
    1254 Next:<a rel=next href="#Section%204.19">Section 4.19</a>, 
    1255 Previous:<a rel=previous href="#Section%204.17">Section 4.17</a>, 
    1256 Up:<a rel=up href="#Problems">Problems</a> 
    1257 <br> 
    1258  
    1259 <h2>4.18 How do I configure two chips (LM87) differently?</h2> 
     1280Next:<a rel=next accesskey=n href="#Section%204.19">Section 4.19</a>, 
     1281Previous:<a rel=previous accesskey=p href="#Section%204.17">Section 4.17</a>, 
     1282Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1283<br> 
     1284 
     1285<h3>4.18 How do I configure two chips (LM87) differently?</h3> 
    12601286 
    12611287<p>There is a SuperMicro board with two LM87's on it that are 
     
    12641290 
    12651291<p>Make two different sections in <code>/etc/sensors.conf</code> as follows: 
    1266 <pre>chip "lm87-i2c-*-2c" 
     1292<br><pre>chip "lm87-i2c-*-2c" 
    12671293    put configuration for the chip at 0x2c here 
    12681294chip "lm87-i2c-*-2d" 
     
    12751301<p><hr> 
    12761302Node:<a name="Section%204.19">Section 4.19</a>, 
    1277 Next:<a rel=next href="#Section%204.20">Section 4.20</a>, 
    1278 Previous:<a rel=previous href="#Section%204.18">Section 4.18</a>, 
    1279 Up:<a rel=up href="#Problems">Problems</a> 
    1280 <br> 
    1281  
    1282 <h2>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h2> 
     1303Next:<a rel=next accesskey=n href="#Section%204.20">Section 4.20</a>, 
     1304Previous:<a rel=previous accesskey=p href="#Section%204.18">Section 4.18</a>, 
     1305Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1306<br> 
     1307 
     1308<h3>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h3> 
    12831309 
    12841310<p>If the problem is a PCI device is not present in <code>lspci</code>, the solution 
     
    12951321<p><a name="Dmesg%20says%20use%20force_addr%3d0xaddr!%20What%20address%20do%20I%20use"></a> 
    12961322 
    1297 <h3>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h3> 
     1323<h4>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h4> 
    12981324 
    12991325<p>If the problem is a PCI device whose base address is not set, 
     
    13071333<p><hr> 
    13081334Node:<a name="Section%204.20">Section 4.20</a>, 
    1309 Next:<a rel=next href="#Section%204.21">Section 4.21</a>, 
    1310 Previous:<a rel=previous href="#Section%204.19">Section 4.19</a>, 
    1311 Up:<a rel=up href="#Problems">Problems</a> 
    1312 <br> 
    1313  
    1314 <h2>4.20 Sensors says <code>Can't access <code>/proc</code> file</code></h2> 
     1335Next:<a rel=next accesskey=n href="#Section%204.21">Section 4.21</a>, 
     1336Previous:<a rel=previous accesskey=p href="#Section%204.19">Section 4.19</a>, 
     1337Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1338<br> 
     1339 
     1340<h3>4.20 Sensors says <code>Can't access <code>/proc</code> file</code></h3> 
    13151341 
    13161342<ul> 
     
    13231349<p><hr> 
    13241350Node:<a name="Section%204.21">Section 4.21</a>, 
    1325 Next:<a rel=next href="#Section%204.22">Section 4.22</a>, 
    1326 Previous:<a rel=previous href="#Section%204.20">Section 4.20</a>, 
    1327 Up:<a rel=up href="#Problems">Problems</a> 
    1328 <br> 
    1329  
    1330 <h2>4.21 Sensors says <code>No sensors found!</code></h2> 
     1351Next:<a rel=next accesskey=n href="#Section%204.22">Section 4.22</a>, 
     1352Previous:<a rel=previous accesskey=p href="#Section%204.20">Section 4.20</a>, 
     1353Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1354<br> 
     1355 
     1356<h3>4.21 Sensors says <code>No sensors found!</code></h3> 
    13311357 
    13321358<ul> 
     
    13411367<p><hr> 
    13421368Node:<a name="Section%204.22">Section 4.22</a>, 
    1343 Next:<a rel=next href="#Section%204.23">Section 4.23</a>, 
    1344 Previous:<a rel=previous href="#Section%204.21">Section 4.21</a>, 
    1345 Up:<a rel=up href="#Problems">Problems</a> 
    1346 <br> 
    1347  
    1348 <h2>4.22 Sensors output is not correct!</h2> 
     1369Next:<a rel=next accesskey=n href="#Section%204.23">Section 4.23</a>, 
     1370Previous:<a rel=previous accesskey=p href="#Section%204.21">Section 4.21</a>, 
     1371Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1372<br> 
     1373 
     1374<h3>4.22 Sensors output is not correct!</h3> 
    13491375 
    13501376<p>What specifically is the trouble? 
     
    13671393<p><hr> 
    13681394Node:<a name="Section%204.23">Section 4.23</a>, 
    1369 Next:<a rel=next href="#Section%204.24">Section 4.24</a>, 
    1370 Previous:<a rel=previous href="#Section%204.22">Section 4.22</a>, 
    1371 Up:<a rel=up href="#Problems">Problems</a> 
    1372 <br> 
    1373  
    1374 <h2>4.23 What is at I2C address XXX?</h2> 
     1395Next:<a rel=next accesskey=n href="#Section%204.24">Section 4.24</a>, 
     1396Previous:<a rel=previous accesskey=p href="#Section%204.22">Section 4.22</a>, 
     1397Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1398<br> 
     1399 
     1400<h3>4.23 What is at I2C address XXX?</h3> 
    13751401 
    13761402<p>In general, we don't know. Start by running <code>sensors-detect</code>.  
     
    13801406<p><a name="What%20is%20at%20I2C%20address%200x69"></a> 
    13811407 
    1382 <h3>4.23.1 What is at I2C address 0x69?</h3> 
     1408<h4>4.23.1 What is at I2C address 0x69?</h4> 
    13831409 
    13841410<p>A clock chip. Often, accessing these clock chips in the wrong 
     
    13901416<p><a name="What%20is%20at%20I2C%20addresses%200x50%20-%200x57"></a> 
    13911417 
    1392 <h3>4.23.2 What is at I2C addresses 0x50 - 0x57?</h3> 
     1418<h4>4.23.2 What is at I2C addresses 0x50 - 0x57?</h4> 
    13931419 
    13941420<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to 
     
    13981424<p><a name="What%20is%20at%20I2C%20addresses%200x30%20-%200x37"></a> 
    13991425 
    1400 <h3>4.23.3 What is at I2C addresses 0x30 - 0x37?</h3> 
     1426<h4>4.23.3 What is at I2C addresses 0x30 - 0x37?</h4> 
    14011427 
    14021428<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs 
     
    14081434<p><hr> 
    14091435Node:<a name="Section%204.24">Section 4.24</a>, 
    1410 Next:<a rel=next href="#Section%204.25">Section 4.25</a>, 
    1411 Previous:<a rel=previous href="#Section%204.23">Section 4.23</a>, 
    1412 Up:<a rel=up href="#Problems">Problems</a> 
    1413 <br> 
    1414  
    1415 <h2>4.24 Sensors-detect doesn't work at all</h2> 
     1436Next:<a rel=next accesskey=n href="#Section%204.25">Section 4.25</a>, 
     1437Previous:<a rel=previous accesskey=p href="#Section%204.23">Section 4.23</a>, 
     1438Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1439<br> 
     1440 
     1441<h3>4.24 Sensors-detect doesn't work at all</h3> 
    14161442 
    14171443<p>It could be many things. What was the problem? See <a href="#Section%204.31">Problems on particular motherboards</a>. 
     
    14191445<p><a name="Sensors-detect%20says%20%22Couldnt%20open%20%2fproc%2fbus%2fi2c%3f!%3f%22"></a> 
    14201446 
    1421 <h3>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h3> 
     1447<h4>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4> 
    14221448 
    14231449<p>You don't have i2c support in your kernel, or the i2c-core module 
     
    14261452<p><a name="Sensors-detect%20says%20%22Cant%20open%20%2fdev%2fi2c%5b-%2f%5d0%22"></a> 
    14271453 
    1428 <h3>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h3> 
     1454<h4>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4> 
    14291455 
    14301456<p>Your <code>/dev/i2c-0,</code> <code>/dev/i2c0</code>, or <code>/dev/i2c/0</code> files do not exist 
     
    14351461<p><a name="Sensors-detect%20doesnt%20find%20any%20sensors"></a> 
    14361462 
    1437 <h3>4.24.3 Sensors-detect doesn't find any sensors!</h3> 
     1463<h4>4.24.3 Sensors-detect doesn't find any sensors!</h4> 
    14381464 
    14391465<p>Either 
     
    14581484<p><hr> 
    14591485Node:<a name="Section%204.25">Section 4.25</a>, 
    1460 Next:<a rel=next href="#Section%204.26">Section 4.26</a>, 
    1461 Previous:<a rel=previous href="#Section%204.24">Section 4.24</a>, 
    1462 Up:<a rel=up href="#Problems">Problems</a> 
    1463 <br> 
    1464  
    1465 <h2>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h2> 
     1486Next:<a rel=next accesskey=n href="#Section%204.26">Section 4.26</a>, 
     1487Previous:<a rel=previous accesskey=p href="#Section%204.24">Section 4.24</a>, 
     1488Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1489<br> 
     1490 
     1491<h3>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h3> 
    14661492 
    14671493<p>These are errors from the libsensors library in 
     
    14721498<p><hr> 
    14731499Node:<a name="Section%204.26">Section 4.26</a>, 
    1474 Next:<a rel=next href="#Section%204.27">Section 4.27</a>, 
    1475 Previous:<a rel=previous href="#Section%204.25">Section 4.25</a>, 
    1476 Up:<a rel=up href="#Problems">Problems</a> 
    1477 <br> 
    1478  
    1479 <h2>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h2> 
     1500Next:<a rel=next accesskey=n href="#Section%204.27">Section 4.27</a>, 
     1501Previous:<a rel=previous accesskey=p href="#Section%204.25">Section 4.25</a>, 
     1502Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1503<br> 
     1504 
     1505<h3>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3> 
    14801506 
    14811507<p>If <code>sensors</code> only says this, for example, and doesn't 
    14821508provide any actual data at all: 
    14831509 
    1484 <pre>it87-isa-0290 
     1510<br><pre>it87-isa-0290 
    14851511Adapter: ISA adapter 
    14861512Algorithm: ISA algorithm 
     
    14941520<p><hr> 
    14951521Node:<a name="Section%204.27">Section 4.27</a>, 
    1496 Next:<a rel=next href="#Section%204.28">Section 4.28</a>, 
    1497 Previous:<a rel=previous href="#Section%204.26">Section 4.26</a>, 
    1498 Up:<a rel=up href="#Problems">Problems</a> 
    1499 <br> 
    1500  
    1501 <h2>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h2> 
     1522Next:<a rel=next accesskey=n href="#Section%204.28">Section 4.28</a>, 
     1523Previous:<a rel=previous accesskey=p href="#Section%204.26">Section 4.26</a>, 
     1524Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1525<br> 
     1526 
     1527<h3>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h3> 
    15021528 
    15031529<p>You have a <code>libsensors/sensors</code> mismatch. <code>sensors</code> is unable to 
     
    15111537<p><hr> 
    15121538Node:<a name="Section%204.28">Section 4.28</a>, 
    1513 Next:<a rel=next href="#Section%204.29">Section 4.29</a>, 
    1514 Previous:<a rel=previous href="#Section%204.27">Section 4.27</a>, 
    1515 Up:<a rel=up href="#Problems">Problems</a> 
    1516 <br> 
    1517  
    1518 <h2>4.28 Sensors doesn't find any sensors, just eeproms.</h2> 
     1539Next:<a rel=next accesskey=n href="#Section%204.29">Section 4.29</a>, 
     1540Previous:<a rel=previous accesskey=p href="#Section%204.27">Section 4.27</a>, 
     1541Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1542<br> 
     1543 
     1544<h3>4.28 Sensors doesn't find any sensors, just eeproms.</h3> 
    15191545 
    15201546<p>See <a href="#Section%204.24">Sensors-detect doesnt work at all</a>, if <code>sensors-detect</code> failed to find any sensors. 
     
    15281554<p><hr> 
    15291555Node:<a name="Section%204.29">Section 4.29</a>, 
    1530 Next:<a rel=next href="#Section%204.30">Section 4.30</a>, 
    1531 Previous:<a rel=previous href="#Section%204.28">Section 4.28</a>, 
    1532 Up:<a rel=up href="#Problems">Problems</a> 
    1533 <br> 
    1534  
    1535 <h2>4.29 Inserting modules hangs my board</h2> 
     1556Next:<a rel=next accesskey=n href="#Section%204.30">Section 4.30</a>, 
     1557Previous:<a rel=previous accesskey=p href="#Section%204.28">Section 4.28</a>, 
     1558Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1559<br> 
     1560 
     1561<h3>4.29 Inserting modules hangs my board</h3> 
    15361562 
    15371563<p>There are several possible causes: 
     
    15461572<p><hr> 
    15471573Node:<a name="Section%204.30">Section 4.30</a>, 
    1548 Next:<a rel=next href="#Section%204.31">Section 4.31</a>, 
    1549 Previous:<a rel=previous href="#Section%204.29">Section 4.29</a>, 
    1550 Up:<a rel=up href="#Problems">Problems</a> 
    1551 <br> 
    1552  
    1553 <h2>4.30 Inserting modules slows down my board</h2> 
     1574Next:<a rel=next accesskey=n href="#Section%204.31">Section 4.31</a>, 
     1575Previous:<a rel=previous accesskey=p href="#Section%204.29">Section 4.29</a>, 
     1576Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1577<br> 
     1578 
     1579<h3>4.30 Inserting modules slows down my board</h3> 
    15541580 
    15551581<p>Generally this is caused by an overtemperature alarm output from 
     
    15611587<p><hr> 
    15621588Node:<a name="Section%204.31">Section 4.31</a>, 
    1563 Next:<a rel=next href="#Section%204.32">Section 4.32</a>, 
    1564 Previous:<a rel=previous href="#Section%204.30">Section 4.30</a>, 
    1565 Up:<a rel=up href="#Problems">Problems</a> 
    1566 <br> 
    1567  
    1568 <h2>4.31 Problems on particular motherboards</h2> 
     1589Next:<a rel=next accesskey=n href="#Section%204.32">Section 4.32</a>, 
     1590Previous:<a rel=previous accesskey=p href="#Section%204.30">Section 4.30</a>, 
     1591Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1592<br> 
     1593 
     1594<h3>4.31 Problems on particular motherboards</h3> 
    15691595 
    15701596<p>The following boards have unique problems and solutions. 
     
    15721598<p><a name="Asus%20P4B"></a> 
    15731599 
    1574 <h3>4.31.1 Asus P4B</h3> 
     1600<h4>4.31.1 Asus P4B</h4> 
    15751601 
    15761602<p>See <code>prog/hotplug/README.p4b</code> if your SMBus master is not found. 
     
    15781604<p><a name="Tyan%202460%202462"></a> 
    15791605 
    1580 <h3>4.31.2 Tyan 2460, 2462</h3> 
     1606<h4>4.31.2 Tyan 2460, 2462</h4> 
    15811607 
    15821608<p>See support tickets 805, 765, 781, 812, 813, and 867 for information. 
     
    15841610<p><a name="Tyan%202466"></a> 
    15851611 
    1586 <h3>4.31.3 Tyan 2466</h3> 
     1612<h4>4.31.3 Tyan 2466</h4> 
    15871613 
    15881614<p>See support tickets 941, 840, and 841 for information. 
     
    15901616<p><a name="Tyan%202688"></a> 
    15911617 
    1592 <h3>4.31.4 Tyan 2688</h3> 
     1618<h4>4.31.4 Tyan 2688</h4> 
    15931619 
    15941620<p>For board hangs, see support ticket 721 for information.  
     
    15971623<p><hr> 
    15981624Node:<a name="Section%204.32">Section 4.32</a>, 
    1599 Previous:<a rel=previous href="#Section%204.31">Section 4.31</a>, 
    1600 Up:<a rel=up href="#Problems">Problems</a> 
    1601 <br> 
    1602  
    1603 <h2>4.32 Problems on particular systems</h2> 
     1625Previous:<a rel=previous accesskey=p href="#Section%204.31">Section 4.31</a>, 
     1626Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
     1627<br> 
     1628 
     1629<h3>4.32 Problems on particular systems</h3> 
    16041630 
    16051631<p>For IBM systems, see <code>README.thinkpad</code>. 
     
    16071633<p><hr> 
    16081634Node:<a name="Help">Help</a>, 
    1609 Next:<a rel=next href="#Contribute">Contribute</a>, 
    1610 Previous:<a rel=previous href="#Problems">Problems</a>, 
    1611 Up:<a rel=up href="#Top">Top</a> 
    1612 <br> 
    1613  
    1614 <h1>5 How to Ask for Help</h1> 
    1615  
    1616 <ul> 
    1617 <li><a href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
    1618 <li><a href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
    1619 <li><a href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
    1620 <li><a href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
    1621 <li><a href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
    1622 <li><a href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
    1623 <li><a href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
    1624 <li><a href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
     1635Next:<a rel=next accesskey=n href="#Contribute">Contribute</a>, 
     1636Previous:<a rel=previous accesskey=p href="#Problems">Problems</a>, 
     1637Up:<a rel=up accesskey=u href="#Top">Top</a> 
     1638<br> 
     1639 
     1640<h2>5 How to Ask for Help</h2> 
     1641 
     1642<ul> 
     1643<li><a accesskey=1 href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
     1644<li><a accesskey=2 href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
     1645<li><a accesskey=3 href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
     1646<li><a accesskey=4 href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
     1647<li><a accesskey=5 href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
     1648<li><a accesskey=6 href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
     1649<li><a accesskey=7 href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
     1650<li><a accesskey=8 href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
    16251651</ul> 
    16261652 
    16271653<p><hr> 
    16281654Node:<a name="Section%205.1">Section 5.1</a>, 
    1629 Next:<a rel=next href="#Section%205.2">Section 5.2</a>, 
    1630 Up:<a rel=up href="#Help">Help</a> 
    1631 <br> 
    1632  
    1633 <h2>5.1 What to send us when asking for help</h2> 
     1655Next:<a rel=next accesskey=n href="#Section%205.2">Section 5.2</a>, 
     1656Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1657<br> 
     1658 
     1659<h3>5.1 What to send us when asking for help</h3> 
    16341660 
    16351661<p>We are always willing to answer questions if things don't work out.  
     
    16731699<p><hr> 
    16741700Node:<a name="Section%205.2">Section 5.2</a>, 
    1675 Next:<a rel=next href="#Section%205.3">Section 5.3</a>, 
    1676 Previous:<a rel=previous href="#Section%205.1">Section 5.1</a>, 
    1677 Up:<a rel=up href="#Help">Help</a> 
    1678 <br> 
    1679  
    1680 <h2>5.2 What to do if a module won't insert?</h2> 
     1701Next:<a rel=next accesskey=n href="#Section%205.3">Section 5.3</a>, 
     1702Previous:<a rel=previous accesskey=p href="#Section%205.1">Section 5.1</a>, 
     1703Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1704<br> 
     1705 
     1706<h3>5.2 What to do if a module won't insert?</h3> 
    16811707 
    16821708<p>Did you use <code>modprobe</code> instead of <code>insmod</code>??? Don't use insmod. 
     
    16921718<p><hr> 
    16931719Node:<a name="Section%205.3">Section 5.3</a>, 
    1694 Next:<a rel=next href="#Section%205.4">Section 5.4</a>, 
    1695 Previous:<a rel=previous href="#Section%205.2">Section 5.2</a>, 
    1696 Up:<a rel=up href="#Help">Help</a> 
    1697 <br> 
    1698  
    1699 <h2>5.3 What to do if it inserts, but nothing happens?</h2> 
     1720Next:<a rel=next accesskey=n href="#Section%205.4">Section 5.4</a>, 
     1721Previous:<a rel=previous accesskey=p href="#Section%205.2">Section 5.2</a>, 
     1722Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1723<br> 
     1724 
     1725<h3>5.3 What to do if it inserts, but nothing happens?</h3> 
    17001726 
    17011727<p>For an ISA sensor chip, did you also <code>modprobe i2c-isa</code>? It must be inserted. 
     
    17101736<p><hr> 
    17111737Node:<a name="Section%205.4">Section 5.4</a>, 
    1712 Next:<a rel=next href="#Section%205.5">Section 5.5</a>, 
    1713 Previous:<a rel=previous href="#Section%205.3">Section 5.3</a>, 
    1714 Up:<a rel=up href="#Help">Help</a> 
    1715 <br> 
    1716  
    1717 <h2>5.4 What to do if I read only bogus information?</h2> 
     1738Next:<a rel=next accesskey=n href="#Section%205.5">Section 5.5</a>, 
     1739Previous:<a rel=previous accesskey=p href="#Section%205.3">Section 5.3</a>, 
     1740Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1741<br> 
     1742 
     1743<h3>5.4 What to do if I read only bogus information?</h3> 
    17181744 
    17191745<p>It may be that this was a mis-detection: the chip may not be 
     
    17251751<p><hr> 
    17261752Node:<a name="Section%205.5">Section 5.5</a>, 
    1727 Next:<a rel=next href="#Section%205.6">Section 5.6</a>, 
    1728 Previous:<a rel=previous href="#Section%205.4">Section 5.4</a>, 
    1729 Up:<a rel=up href="#Help">Help</a> 
    1730 <br> 
    1731  
    1732 <h2>5.5 What to do if you have other problems?</h2> 
     1753Next:<a rel=next accesskey=n href="#Section%205.6">Section 5.6</a>, 
     1754Previous:<a rel=previous accesskey=p href="#Section%205.4">Section 5.4</a>, 
     1755Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1756<br> 
     1757 
     1758<h3>5.5 What to do if you have other problems?</h3> 
    17331759 
    17341760<p>Again, send the output listed above. 
     
    17361762<p><hr> 
    17371763Node:<a name="Section%205.6">Section 5.6</a>, 
    1738 Next:<a rel=next href="#Section%205.7">Section 5.7</a>, 
    1739 Previous:<a rel=previous href="#Section%205.5">Section 5.5</a>, 
    1740 Up:<a rel=up href="#Help">Help</a> 
    1741 <br> 
    1742  
    1743 <h2>5.6 What if it just works like a charm?</h2> 
     1764Next:<a rel=next accesskey=n href="#Section%205.7">Section 5.7</a>, 
     1765Previous:<a rel=previous accesskey=p href="#Section%205.5">Section 5.5</a>, 
     1766Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1767<br> 
     1768 
     1769<h3>5.6 What if it just works like a charm?</h3> 
    17441770 
    17451771<p>Drop us a mail if you feel like it, mentioning the mainboard and 
     
    17481774<p><hr> 
    17491775Node:<a name="Section%205.7">Section 5.7</a>, 
    1750 Next:<a rel=next href="#Section%205.8">Section 5.8</a>, 
    1751 Previous:<a rel=previous href="#Section%205.6">Section 5.6</a>, 
    1752 Up:<a rel=up href="#Help">Help</a> 
    1753 <br> 
    1754  
    1755 <h2>5.7 How do I update a ticket?</h2> 
     1776Next:<a rel=next accesskey=n href="#Section%205.8">Section 5.8</a>, 
     1777Previous:<a rel=previous accesskey=p href="#Section%205.6">Section 5.6</a>, 
     1778Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1779<br> 
     1780 
     1781<h3>5.7 How do I update a ticket?</h3> 
    17561782 
    17571783<p>You can't. Only developers can. Follow up by emailing us 
     
    17621788<p><hr> 
    17631789Node:<a name="Section%205.8">Section 5.8</a>, 
    1764 Previous:<a rel=previous href="#Section%205.7">Section 5.7</a>, 
    1765 Up:<a rel=up href="#Help">Help</a> 
    1766 <br> 
    1767  
    1768 <h2>5.8 How do I follow up on a ticket?</h2> 
     1790Previous:<a rel=previous accesskey=p href="#Section%205.7">Section 5.7</a>, 
     1791Up:<a rel=up accesskey=u href="#Help">Help</a> 
     1792<br> 
     1793 
     1794<h3>5.8 How do I follow up on a ticket?</h3> 
    17691795 
    17701796<p>Follow up by emailing us at <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> 
     
    17731799<p><hr> 
    17741800Node:<a name="Contribute">Contribute</a>, 
    1775 Next:<a rel=next href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    1776 Previous:<a rel=previous href="#Help">Help</a>, 
    1777 Up:<a rel=up href="#Top">Top</a> 
    1778 <br> 
    1779  
    1780 <h1>6 How to Contribute</h1> 
    1781  
    1782 <ul> 
    1783 <li><a href="#Section%206.1">Section 6.1</a>:   How to write a driver 
    1784 <li><a href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
    1785 <li><a href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
    1786 <li><a href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
    1787 <li><a href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
    1788 <li><a href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
    1789 <li><a href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
    1790 <li><a href="#Section%206.8">Section 6.8</a>:   How to block spam on the project mailing list 
     1801Next:<a rel=next accesskey=n href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     1802Previous:<a rel=previous accesskey=p href="#Help">Help</a>, 
     1803Up:<a rel=up accesskey=u href="#Top">Top</a> 
     1804<br> 
     1805 
     1806<h2>6 How to Contribute</h2> 
     1807 
     1808<ul> 
     1809<li><a accesskey=1 href="#Section%206.1">Section 6.1</a>:   How to write a driver 
     1810<li><a accesskey=2 href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
     1811<li><a accesskey=3 href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
     1812<li><a accesskey=4 href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
     1813<li><a accesskey=5 href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
     1814<li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
     1815<li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
     1816<li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to get release announcements 
     1817<li><a accesskey=9 href="#Section%206.9">Section 6.9</a>:   How to block spam on the project mailing list 
    17911818</ul> 
    17921819 
    17931820<p><hr> 
    17941821Node:<a name="Section%206.1">Section 6.1</a>, 
    1795 Next:<a rel=next href="#Section%206.2">Section 6.2</a>, 
    1796 Up:<a rel=up href="#Contribute">Contribute</a> 
    1797 <br> 
    1798  
    1799 <h2>6.1 How to write a driver</h2> 
     1822Next:<a rel=next accesskey=n href="#Section%206.2">Section 6.2</a>, 
     1823Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1824<br> 
     1825 
     1826<h3>6.1 How to write a driver</h3> 
    18001827 
    18011828<p>See <code>doc/developers/new_drivers</code> in our package for instructions. 
     
    18031830<p><hr> 
    18041831Node:<a name="Section%206.2">Section 6.2</a>, 
    1805 Next:<a rel=next href="#Section%206.3">Section 6.3</a>, 
    1806 Previous:<a rel=previous href="#Section%206.1">Section 6.1</a>, 
    1807 Up:<a rel=up href="#Contribute">Contribute</a> 
    1808 <br> 
    1809  
    1810 <h2>6.2 How to get CVS access</h2> 
     1832Next:<a rel=next accesskey=n href="#Section%206.3">Section 6.3</a>, 
     1833Previous:<a rel=previous accesskey=p href="#Section%206.1">Section 6.1</a>, 
     1834Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1835<br> 
     1836 
     1837<h3>6.2 How to get CVS access</h3> 
    18111838 
    18121839<p>For anonymous CVS read access, see the instructions on our download page.  
     
    18191846<p><hr> 
    18201847Node:<a name="Section%206.3">Section 6.3</a>, 
    1821 Next:<a rel=next href="#Section%206.4">Section 6.4</a>, 
    1822 Previous:<a rel=previous href="#Section%206.2">Section 6.2</a>, 
    1823 Up:<a rel=up href="#Contribute">Contribute</a> 
    1824 <br> 
    1825  
    1826 <h2>6.3 How to donate hardware to the project</h2> 
     1848Next:<a rel=next accesskey=n href="#Section%206.4">Section 6.4</a>, 
     1849Previous:<a rel=previous accesskey=p href="#Section%206.2">Section 6.2</a>, 
     1850Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1851<br> 
     1852 
     1853<h3>6.3 How to donate hardware to the project</h3> 
    18271854 
    18281855<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. 
     
    18301857<p><hr> 
    18311858Node:<a name="Section%206.4">Section 6.4</a>, 
    1832 Next:<a rel=next href="#Section%206.5">Section 6.5</a>, 
    1833 Previous:<a rel=previous href="#Section%206.3">Section 6.3</a>, 
    1834 Up:<a rel=up href="#Contribute">Contribute</a> 
    1835 <br> 
    1836  
    1837 <h2>6.4 How to join the project mailing list</h2> 
     1859Next:<a rel=next accesskey=n href="#Section%206.5">Section 6.5</a>, 
     1860Previous:<a rel=previous accesskey=p href="#Section%206.3">Section 6.3</a>, 
     1861Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1862<br> 
     1863 
     1864<h3>6.4 How to join the project mailing list</h3> 
    18381865 
    18391866<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. Sorry, 
     
    18471874<p><hr> 
    18481875Node:<a name="Section%206.5">Section 6.5</a>, 
    1849 Next:<a rel=next href="#Section%206.6">Section 6.6</a>, 
    1850 Previous:<a rel=previous href="#Section%206.4">Section 6.4</a>, 
    1851 Up:<a rel=up href="#Contribute">Contribute</a> 
    1852 <br> 
    1853  
    1854 <h2>6.5 How to access mailing list archives</h2> 
     1876Next:<a rel=next accesskey=n href="#Section%206.6">Section 6.6</a>, 
     1877Previous:<a rel=previous accesskey=p href="#Section%206.4">Section 6.4</a>, 
     1878Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1879<br> 
     1880 
     1881<h3>6.5 How to access mailing list archives</h3> 
    18551882 
    18561883<p>The mailing list archive is at: <a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a> 
     
    18591886<p><hr> 
    18601887Node:<a name="Section%206.6">Section 6.6</a>, 
    1861 Next:<a rel=next href="#Section%206.7">Section 6.7</a>, 
    1862 Previous:<a rel=previous href="#Section%206.5">Section 6.5</a>, 
    1863 Up:<a rel=up href="#Contribute">Contribute</a> 
    1864 <br> 
    1865  
    1866 <h2>6.6 How to submit a patch</h2> 
     1888Next:<a rel=next accesskey=n href="#Section%206.7">Section 6.7</a>, 
     1889Previous:<a rel=previous accesskey=p href="#Section%206.5">Section 6.5</a>, 
     1890Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1891<br> 
     1892 
     1893<h3>6.6 How to submit a patch</h3> 
    18671894 
    18681895<p>Check out the latest from CVS, then copy the directory to another 
     
    18731900<p><hr> 
    18741901Node:<a name="Section%206.7">Section 6.7</a>, 
    1875 Next:<a rel=next href="#Section%206.8">Section 6.8</a>, 
    1876 Previous:<a rel=previous href="#Section%206.6">Section 6.6</a>, 
    1877 Up:<a rel=up href="#Contribute">Contribute</a> 
    1878 <br> 
    1879  
    1880 <h2>6.7 How to REALLY help</h2> 
     1902Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>, 
     1903Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>, 
     1904Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1905<br> 
     1906 
     1907<h3>6.7 How to REALLY help</h3> 
    18811908 
    18821909<p>Believe it or not, what we really need help with are: 
     
    18941921<p><hr> 
    18951922Node:<a name="Section%206.8">Section 6.8</a>, 
    1896 Previous:<a rel=previous href="#Section%206.7">Section 6.7</a>, 
    1897 Up:<a rel=up href="#Contribute">Contribute</a> 
    1898 <br> 
    1899  
    1900 <h2>6.8 How to block spam on the project mailing list</h2> 
     1923Next:<a rel=next accesskey=n href="#Section%206.9">Section 6.9</a>, 
     1924Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>, 
     1925Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1926<br> 
     1927 
     1928<h3>6.8 How to get release announcements</h3> 
     1929 
     1930<p>We don't have a separate release announcement mailing list; 
     1931however, we put all our releases on freshmeat: <a href="http://freshmeat.net">http://freshmeat.net</a> 
     1932and you can register on our freshmeat project page  <a href="http://freshmeat.net/projects/lm_sensors">http://freshmeat.net/projects/lm_sensors</a> 
     1933to 'subscribe to new releases' and then freshmeat 
     1934will email you announcement. 
     1935 
     1936<p><hr> 
     1937Node:<a name="Section%206.9">Section 6.9</a>, 
     1938Previous:<a rel=previous accesskey=p href="#Section%206.8">Section 6.8</a>, 
     1939Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
     1940<br> 
     1941 
     1942<h3>6.9 How to block spam on the project mailing list</h3> 
    19011943 
    19021944<p>Sorry, we know the spam is a hassle.  It would be nice to have a 
     
    19121954<p><hr> 
    19131955Node:<a name="Version%201%20Specifics">Version 1 Specifics</a>, 
    1914 Next:<a rel=next href="#Document%20Revisions">Document Revisions</a>, 
    1915 Previous:<a rel=previous href="#Contribute">Contribute</a>, 
    1916 Up:<a rel=up href="#Top">Top</a> 
    1917 <br> 
    1918  
    1919 <h1>7 Version 1 Specific Questions</h1> 
    1920  
    1921 <ul> 
    1922 <li><a href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
    1923 <li><a href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
    1924 <li><a href="#Section%207.3">Section 7.3</a>:   I get a "No sensor data yet (try again in a few moments)" msg.  
    1925 <li><a href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
     1956Next:<a rel=next accesskey=n href="#Document%20Revisions">Document Revisions</a>, 
     1957Previous:<a rel=previous accesskey=p href="#Contribute">Contribute</a>, 
     1958Up:<a rel=up accesskey=u href="#Top">Top</a> 
     1959<br> 
     1960 
     1961<h2>7 Version 1 Specific Questions</h2> 
     1962 
     1963<ul> 
     1964<li><a accesskey=1 href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
     1965<li><a accesskey=2 href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
     1966<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.  
     1967<li><a accesskey=4 href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
    19261968</ul> 
    19271969 
     
    19301972<p><hr> 
    19311973Node:<a name="Section%207.1">Section 7.1</a>, 
    1932 Next:<a rel=next href="#Section%207.2">Section 7.2</a>, 
    1933 Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1934 <br> 
    1935  
    1936 <h2>7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it.  What's wrong?</h2> 
     1974Next:<a rel=next accesskey=n href="#Section%207.2">Section 7.2</a>, 
     1975Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1976<br> 
     1977 
     1978<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> 
    19371979 
    19381980<p>Currently, our code only assumes that an SMBus exists if it originates 
     
    19571999<p><hr> 
    19582000Node:<a name="Section%207.2">Section 7.2</a>, 
    1959 Next:<a rel=next href="#Section%207.3">Section 7.3</a>, 
    1960 Previous:<a rel=previous href="#Section%207.1">Section 7.1</a>, 
    1961 Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1962 <br> 
    1963  
    1964 <h2>7.2 The modules won't load, saying 'SMBus not detected'.</h2> 
     2001Next:<a rel=next accesskey=n href="#Section%207.3">Section 7.3</a>, 
     2002Previous:<a rel=previous accesskey=p href="#Section%207.1">Section 7.1</a>, 
     2003Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
     2004<br> 
     2005 
     2006<h3>7.2 The modules won't load, saying 'SMBus not detected'.</h3> 
    19652007 
    19662008<p>This should no longer be an issue in 1.4.10 and later; it will 
     
    19692011<p><hr> 
    19702012Node:<a name="Section%207.3">Section 7.3</a>, 
    1971 Next:<a rel=next href="#Section%207.4">Section 7.4</a>, 
    1972 Previous:<a rel=previous href="#Section%207.2">Section 7.2</a>, 
    1973 Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1974 <br> 
    1975  
    1976 <h2>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?</h2> 
     2013Next:<a rel=next accesskey=n href="#Section%207.4">Section 7.4</a>, 
     2014Previous:<a rel=previous accesskey=p href="#Section%207.2">Section 7.2</a>, 
     2015Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
     2016<br> 
     2017 
     2018<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> 
    19772019 
    19782020<p>It takes about 1.5 seconds for the LM78 to update all its sensor 
     
    19872029<p><hr> 
    19882030Node:<a name="Section%207.4">Section 7.4</a>, 
    1989 Previous:<a rel=previous href="#Section%207.3">Section 7.3</a>, 
    1990 Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1991 <br> 
    1992  
    1993 <h2>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h2> 
     2031Previous:<a rel=previous accesskey=p href="#Section%207.3">Section 7.3</a>, 
     2032Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
     2033<br> 
     2034 
     2035<h3>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3> 
    19942036 
    19952037<p>This is a bug we have only observed on Dell computers. There is 
     
    20032045<p><hr> 
    20042046Node:<a name="Document%20Revisions">Document Revisions</a>, 
    2005 Previous:<a rel=previous href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    2006 Up:<a rel=up href="#Top">Top</a> 
    2007 <br> 
    2008  
    2009 <h1>Appendix A Revision History of This Document</h1> 
     2047Previous:<a rel=previous accesskey=p href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     2048Up:<a rel=up accesskey=u href="#Top">Top</a> 
     2049<br> 
     2050 
     2051<h2>Appendix A Revision History of This Document</h2> 
    20102052 
    20112053<ul> 
     
    20342076 
    20352077</body></html> 
    2036  
  • lm-sensors/trunk/doc/lm_sensors-FAQ.texi

    r1968 r2114  
    13461346* Section 6.6::  How to submit a patch 
    13471347* Section 6.7::  How to REALLY help 
    1348 * Section 6.8::  How to block spam on the project mailing list 
     1348* Section 6.8::  How to get release announcements 
     1349* Section 6.9::  How to block spam on the project mailing list 
    13491350@end menu 
    13501351 
     
    14151416 
    14161417 
    1417 @node Section 6.8, , Section 6.7, Contribute 
     1418@node Section 6.8, Section 6.9, Section 6.7, Contribute 
     1419@section How to get release announcements 
     1420 
     1421We don't have a separate release announcement mailing list; 
     1422however, we put all our releases on freshmeat: @uref{http://freshmeat.net} 
     1423and you can register on our freshmeat project page  @uref{http://freshmeat.net/projects/lm_sensors} 
     1424to 'subscribe to new releases' and then freshmeat 
     1425will email you announcement. 
     1426 
     1427@node Section 6.9, , Section 6.8, Contribute 
    14181428@section How to block spam on the project mailing list 
    14191429