Changeset 2209

Show
Ignore:
Timestamp:
01/09/04 22:11:11 (9 years ago)
Author:
khali
Message:

Regenerate from the latest texi source.

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

Legend:

Unmodified
Added
Removed

  • lm-sensors/trunk/doc/FAQ

    r2198 r2209  
    1 START-INFO-DIR-ENTRY 
    2 * lm_sensors-FAQ: (lm_sensors-FAQ)           The lm_sensors FAQ 
    3 END-INFO-DIR-ENTRY 
    4  
    5 Short Contents 
    6 ************** 
    7  
    8 lm_sensors 
    9 1 PC and Sensor Overview 
    10 2 Sensor and Bus Basics 
    11 3 Installation and Management 
    12 4 Problems 
    13 5 How to Ask for Help 
    14 6 How to Contribute 
    15 7 Version 1 Specific Questions 
    16 Appendix A Revision History of This Document 
    17  
    18  
    191Table of Contents 
    202***************** 
    … …  
    9375  4.19 Dmesg says `Upgrade BIOS'! I don't want to! 
    9476    4.19.1 Dmesg says `use force_addr=0xaddr'! What address do I use? 
    95   4.20 Sensors says `Can't access `/proc' file' 
     77  4.20 Sensors says `Can't access procfs/sysfs file' 
    9678  4.21 Sensors says `No sensors found!' 
    9779  4.22 Sensors output is not correct! 
    … …  
    9539350xf000 is generally safe. 
    954936 
    955 4.20 Sensors says `Can't access `/proc' file' 
    956 ============================================= 
     9374.20 Sensors says `Can't access procfs/sysfs file' 
     938================================================== 
    957939 
    958940   * (release 2.6.0 and later) Did you `modprobe i2c-proc'? Check 
    … …  
    15251507 
    15261508   * Rev 1.0 Written by Philip Edelbrock, 19980803 
     1509 

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

    r2198 r2209  
    1 <html lang="en"> 
    2 <head> 
     1<html lang="en"><head> 
    32<title>Sensors FAQ for lm_sensors version 2.10</title> 
    43<meta http-equiv="Content-Type" content="text/html"> 
    54<meta name=description content="Sensors FAQ for lm_sensors version 2.10"> 
    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.10</h1> 
    11 Copyright (c) 1998 - 2002<br> 
     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> 
    1210<a href="mailto:frodol@dds.nl">Frodo Looijaard</a>,<br> 
    1311<a href="mailto:phil@netroedge.com">Philip Edelbrock</a>,<br> 
    … …  
    1614 
    1715 
    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> 
     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> 
    3820<ul> 
    3921<li><a href="#Section%201.1">1.1 What sensors are available on my PC?</a> 
    … …  
    4123<li><a href="#Section%201.3">1.3 Where do I find out more about any of these chips?</a> 
    4224</ul> 
    43 <li><a name="toc_Basics"></a> 
    44     <a href="#Basics">2 Sensor and Bus Basics</a> 
     25<li><a href="#Basics">2 Sensor and Bus Basics</a> 
    4526<ul> 
    4627<li><a href="#Section%202.1">2.1 How are these sensors read?</a> 
    … …  
    5132<li><a href="#Section%202.6">2.6 How are alarms triggered?</a> 
    5233</ul> 
    53 <li><a name="toc_Installation"></a> 
    54     <a href="#Installation">3 Installation and Management</a> 
     34<li><a href="#Installation">3 Installation and Management</a> 
    5535<ul> 
    5636<li><a href="#Section%203.1">3.1 Why so many modules, and how do I cope with them?</a> 
    … …  
    8262<li><a href="#Section%203.10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a> 
    8363</ul> 
    84 <li><a name="toc_Problems"></a> 
    85     <a href="#Problems">4 Problems</a> 
     64<li><a href="#Problems">4 Problems</a> 
    8665<ul> 
    8766<li><a href="#Section%204.1">4.1 My fans report exactly half/double their values compared to the BIOS?</a> 
    … …  
    126105<li><a href="#Section%204.19">4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</a> 
    127106</ul> 
    128 <li><a href="#Section%204.20">4.20 Sensors says <code>Can't access <code>/proc</code> file</code></a> 
     107<li><a href="#Section%204.20">4.20 Sensors says <code>Can't access procfs/sysfs file</code></a> 
    129108<li><a href="#Section%204.21">4.21 Sensors says <code>No sensors found!</code></a> 
    130109<li><a href="#Section%204.22">4.22 Sensors output is not correct!</a> 
    … …  
    157136<li><a href="#Section%204.33">4.33 Problems on 2.6 kernels</a> 
    158137</ul> 
    159 <li><a name="toc_Help"></a> 
    160     <a href="#Help">5 How to Ask for Help</a> 
     138<li><a href="#Help">5 How to Ask for Help</a> 
    161139<ul> 
    162140<li><a href="#Section%205.1">5.1 What to send us when asking for help</a> 
    … …  
    169147<li><a href="#Section%205.8">5.8 How do I follow up on a ticket?</a> 
    170148</ul> 
    171 <li><a name="toc_Contribute"></a> 
    172     <a href="#Contribute">6 How to Contribute</a> 
     149<li><a href="#Contribute">6 How to Contribute</a> 
    173150<ul> 
    174151<li><a href="#Section%206.1">6.1 How to write a driver</a> 
    … …  
    182159<li><a href="#Section%206.9">6.9 How to block spam on the project mailing list</a> 
    183160</ul> 
    184 <li><a name="toc_Version%201%20Specifics"></a> 
    185     <a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
     161<li><a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
    186162<ul> 
    187163<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> 
    … …  
    190166<li><a href="#Section%207.4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a> 
    191167</ul> 
    192 <li><a name="toc_Document%20Revisions"></a> 
    193     <a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
     168<li><a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
    194169</ul> 
    195170 
    196171<p><hr> 
    197172Node:<a name="Top">Top</a>, 
    198 Next:<a rel=next accesskey=n href="#Overview">Overview</a>, 
    199 Up:<a rel=up accesskey=u href="#dir">(dir)</a> 
    200 <br> 
    201  
    202 <h2>lm_sensors</h2> 
     173Next:<a rel=next href="#Overview">Overview</a>, 
     174Up:<a rel=up href="#(dir)">(dir)</a> 
     175<br> 
     176 
     177<h1>lm_sensors</h1> 
    203178 
    204179<p>The lm_sensors package includes a collection of modules for general SMBus 
    … …  
    207182 
    208183<ul> 
    209 <li><a accesskey=1 href="#Overview">Overview</a>:                 PC and Sensor Overview 
    210 <li><a accesskey=2 href="#Basics">Basics</a>:                   Sensor and Bus Basics 
    211 <li><a accesskey=3 href="#Installation">Installation</a>:             Installation and Management 
    212 <li><a accesskey=4 href="#Problems">Problems</a>:                 Problems 
    213 <li><a accesskey=5 href="#Help">Help</a>:                     How to Ask for Help 
    214 <li><a accesskey=6 href="#Contribute">Contribute</a>:               How to Contribute 
    215 <li><a accesskey=7 href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
    216 <li><a accesskey=8 href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
     184<li><a href="#Overview">Overview</a>:                 PC and Sensor Overview 
     185<li><a href="#Basics">Basics</a>:                   Sensor and Bus Basics 
     186<li><a href="#Installation">Installation</a>:             Installation and Management 
     187<li><a href="#Problems">Problems</a>:                 Problems 
     188<li><a href="#Help">Help</a>:                     How to Ask for Help 
     189<li><a href="#Contribute">Contribute</a>:               How to Contribute 
     190<li><a href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
     191<li><a href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
    217192</ul> 
    218193 
    219194<p><hr> 
    220195Node:<a name="Overview">Overview</a>, 
    221 Next:<a rel=next accesskey=n href="#Basics">Basics</a>, 
    222 Previous:<a rel=previous accesskey=p href="#Top">Top</a>, 
    223 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    224 <br> 
    225  
    226 <h2>1 PC and Sensor Overview</h2> 
    227  
    228 <ul> 
    229 <li><a accesskey=1 href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
    230 <li><a accesskey=2 href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
    231 <li><a accesskey=3 href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
     196Next:<a rel=next href="#Basics">Basics</a>, 
     197Previous:<a rel=previous href="#Top">Top</a>, 
     198Up:<a rel=up href="#Top">Top</a> 
     199<br> 
     200 
     201<h1>1 PC and Sensor Overview</h1> 
     202 
     203<ul> 
     204<li><a href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
     205<li><a href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
     206<li><a href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
    232207</ul> 
    233208 
    234209<p><hr> 
    235210Node:<a name="Section%201.1">Section 1.1</a>, 
    236 Next:<a rel=next accesskey=n href="#Section%201.2">Section 1.2</a>, 
    237 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    238 <br> 
    239  
    240 <h3>1.1 What sensors are available on my PC?</h3> 
     211Next:<a rel=next href="#Section%201.2">Section 1.2</a>, 
     212Up:<a rel=up href="#Overview">Overview</a> 
     213<br> 
     214 
     215<h2>1.1 What sensors are available on my PC?</h2> 
    241216 
    242217<p>Most PC's built since late 1997 now come with a 
    … …  
    253228<p><hr> 
    254229Node:<a name="Section%201.2">Section 1.2</a>, 
    255 Next:<a rel=next accesskey=n href="#Section%201.3">Section 1.3</a>, 
    256 Previous:<a rel=previous accesskey=p href="#Section%201.1">Section 1.1</a>, 
    257 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    258 <br> 
    259  
    260 <h3>1.2 What can a sensor chip like the "LM78" do?</h3> 
     230Next:<a rel=next href="#Section%201.3">Section 1.3</a>, 
     231Previous:<a rel=previous href="#Section%201.1">Section 1.1</a>, 
     232Up:<a rel=up href="#Overview">Overview</a> 
     233<br> 
     234 
     235<h2>1.2 What can a sensor chip like the "LM78" do?</h2> 
    261236 
    262237<p>The LM78 is a chip made by National Semiconductor which can monitor 7 
    … …  
    281256<p><hr> 
    282257Node:<a name="Section%201.3">Section 1.3</a>, 
    283 Previous:<a rel=previous accesskey=p href="#Section%201.2">Section 1.2</a>, 
    284 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    285 <br> 
    286  
    287 <h3>1.3 Where do I find out more about any of these chips?</h3> 
     258Previous:<a rel=previous href="#Section%201.2">Section 1.2</a>, 
     259Up:<a rel=up href="#Overview">Overview</a> 
     260<br> 
     261 
     262<h2>1.3 Where do I find out more about any of these chips?</h2> 
    288263 
    289264<p>Most semiconductor companies have comprehensive documentation, 
    … …  
    304279<p><hr> 
    305280Node:<a name="Basics">Basics</a>, 
    306 Next:<a rel=next accesskey=n href="#Installation">Installation</a>, 
    307 Previous:<a rel=previous accesskey=p href="#Overview">Overview</a>, 
    308 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    309 <br> 
    310  
    311 <h2>2 Sensor and Bus Basics</h2> 
    312  
    313 <ul> 
    314 <li><a accesskey=1 href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
    315 <li><a accesskey=2 href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
    316 <li><a accesskey=3 href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
    317 <li><a accesskey=4 href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
    318 <li><a accesskey=5 href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
    319 <li><a accesskey=6 href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
     281Next:<a rel=next href="#Installation">Installation</a>, 
     282Previous:<a rel=previous href="#Overview">Overview</a>, 
     283Up:<a rel=up href="#Top">Top</a> 
     284<br> 
     285 
     286<h1>2 Sensor and Bus Basics</h1> 
     287 
     288<ul> 
     289<li><a href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
     290<li><a href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
     291<li><a href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
     292<li><a href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
     293<li><a href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
     294<li><a href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
    320295</ul> 
    321296 
    322297<p><hr> 
    323298Node:<a name="Section%202.1">Section 2.1</a>, 
    324 Next:<a rel=next accesskey=n href="#Section%202.2">Section 2.2</a>, 
    325 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    326 <br> 
    327  
    328 <h3>2.1 How are these sensors read?</h3> 
     299Next:<a rel=next href="#Section%202.2">Section 2.2</a>, 
     300Up:<a rel=up href="#Basics">Basics</a> 
     301<br> 
     302 
     303<h2>2.1 How are these sensors read?</h2> 
    329304 
    330305<p>Sensor chips reside on either the ISA bus, the SMBus, or both.  
    … …  
    339314<p><hr> 
    340315Node:<a name="Section%202.2">Section 2.2</a>, 
    341 Next:<a rel=next accesskey=n href="#Section%202.3">Section 2.3</a>, 
    342 Previous:<a rel=previous accesskey=p href="#Section%202.1">Section 2.1</a>, 
    343 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    344 <br> 
    345  
    346 <h3>2.2 What is the SMBus? And the I2C bus?</h3> 
     316Next:<a rel=next href="#Section%202.3">Section 2.3</a>, 
     317Previous:<a rel=previous href="#Section%202.1">Section 2.1</a>, 
     318Up:<a rel=up href="#Basics">Basics</a> 
     319<br> 
     320 
     321<h2>2.2 What is the SMBus? And the I2C bus?</h2> 
    347322 
    348323<p>The SMBus is the "System Management Bus".  More specifically, it is a 
    … …  
    366341<p><hr> 
    367342Node:<a name="Section%202.3">Section 2.3</a>, 
    368 Next:<a rel=next accesskey=n href="#Section%202.4">Section 2.4</a>, 
    369 Previous:<a rel=previous accesskey=p href="#Section%202.2">Section 2.2</a>, 
    370 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    371 <br> 
    372  
    373 <h3>2.3 I don't have an ISA bus!</h3> 
     343Next:<a rel=next href="#Section%202.4">Section 2.4</a>, 
     344Previous:<a rel=previous href="#Section%202.2">Section 2.2</a>, 
     345Up:<a rel=up href="#Basics">Basics</a> 
     346<br> 
     347 
     348<h2>2.3 I don't have an ISA bus!</h2> 
    374349 
    375350<p>We promise, you do, even if you don't have any old ISA slots.  
    … …  
    384359<p><hr> 
    385360Node:<a name="Section%202.4">Section 2.4</a>, 
    386 Next:<a rel=next accesskey=n href="#Section%202.5">Section 2.5</a>, 
    387 Previous:<a rel=previous accesskey=p href="#Section%202.3">Section 2.3</a>, 
    388 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    389 <br> 
    390  
    391 <h3>2.4 What sensors do processors have?</h3> 
     361Next:<a rel=next href="#Section%202.5">Section 2.5</a>, 
     362Previous:<a rel=previous href="#Section%202.3">Section 2.3</a>, 
     363Up:<a rel=up href="#Basics">Basics</a> 
     364<br> 
     365 
     366<h2>2.4 What sensors do processors have?</h2> 
    392367 
    393368<p>Most new processors contain a thermal diode on the die itself.  
    … …  
    425400<p><hr> 
    426401Node:<a name="Section%202.5">Section 2.5</a>, 
    427 Next:<a rel=next accesskey=n href="#Section%202.6">Section 2.6</a>, 
    428 Previous:<a rel=previous accesskey=p href="#Section%202.4">Section 2.4</a>, 
    429 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    430 <br> 
    431  
    432 <h3>2.5 How often are the sensor values updated?</h3> 
     402Next:<a rel=next href="#Section%202.6">Section 2.6</a>, 
     403Previous:<a rel=previous href="#Section%202.4">Section 2.4</a>, 
     404Up:<a rel=up href="#Basics">Basics</a> 
     405<br> 
     406 
     407<h2>2.5 How often are the sensor values updated?</h2> 
    433408 
    434409<p>The LM78, and most other sensor chips like it, reads its sensors one 
    … …  
    442417<p><hr> 
    443418Node:<a name="Section%202.6">Section 2.6</a>, 
    444 Previous:<a rel=previous accesskey=p href="#Section%202.5">Section 2.5</a>, 
    445 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    446 <br> 
    447  
    448 <h3>2.6 How are alarms triggered?</h3> 
     419Previous:<a rel=previous href="#Section%202.5">Section 2.5</a>, 
     420Up:<a rel=up href="#Basics">Basics</a> 
     421<br> 
     422 
     423<h2>2.6 How are alarms triggered?</h2> 
    449424 
    450425<p>It is possible to monitor each sensor and have an alarm go off if 
    … …  
    467442<p><hr> 
    468443Node:<a name="Installation">Installation</a>, 
    469 Next:<a rel=next accesskey=n href="#Problems">Problems</a>, 
    470 Previous:<a rel=previous accesskey=p href="#Basics">Basics</a>, 
    471 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    472 <br> 
    473  
    474 <h2>3 Installation and Management</h2> 
    475  
    476 <ul> 
    477 <li><a accesskey=1 href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
    478 <li><a accesskey=2 href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
    479 <li><a accesskey=3 href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
    480 <li><a accesskey=4 href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
    481 <li><a accesskey=5 href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
    482 <li><a accesskey=6 href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
    483 <li><a accesskey=7 href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
    484 <li><a accesskey=8 href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
    485 <li><a accesskey=9 href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
     444Next:<a rel=next href="#Problems">Problems</a>, 
     445Previous:<a rel=previous href="#Basics">Basics</a>, 
     446Up:<a rel=up href="#Top">Top</a> 
     447<br> 
     448 
     449<h1>3 Installation and Management</h1> 
     450 
     451<ul> 
     452<li><a href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
     453<li><a href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
     454<li><a href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
     455<li><a href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
     456<li><a href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
     457<li><a href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
     458<li><a href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
     459<li><a href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
     460<li><a href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
    486461<li><a href="#Section%203.10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
    487462</ul> 
    … …  
    489464<p><hr> 
    490465Node:<a name="Section%203.1">Section 3.1</a>, 
    491 Next:<a rel=next accesskey=n href="#Section%203.2">Section 3.2</a>, 
    492 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    493 <br> 
    494  
    495 <h3>3.1 Why so many modules, and how do I cope with them?</h3> 
     466Next:<a rel=next href="#Section%203.2">Section 3.2</a>, 
     467Up:<a rel=up href="#Installation">Installation</a> 
     468<br> 
     469 
     470<h2>3.1 Why so many modules, and how do I cope with them?</h2> 
    496471 
    497472<p>We tried to make this package as modular as possible. This makes it 
    … …  
    510485<p><hr> 
    511486Node:<a name="Section%203.2">Section 3.2</a>, 
    512 Next:<a rel=next accesskey=n href="#Section%203.3">Section 3.3</a>, 
    513 Previous:<a rel=previous accesskey=p href="#Section%203.1">Section 3.1</a>, 
    514 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    515 <br> 
    516  
    517 <h3>3.2 How do I know which chips I own?</h3> 
     487Next:<a rel=next href="#Section%203.3">Section 3.3</a>, 
     488Previous:<a rel=previous href="#Section%203.1">Section 3.1</a>, 
     489Up:<a rel=up href="#Installation">Installation</a> 
     490<br> 
     491 
     492<h2>3.2 How do I know which chips I own?</h2> 
    518493 
    519494<p>We have an excellent program that scans all your hardware.  
    … …  
    531506<p><a name="Section%203.2.1"></a> 
    532507 
    533 <h4>3.2.1 What chips are on motherboard XYZ?</h4> 
     508<h3>3.2.1 What chips are on motherboard XYZ?</h3> 
    534509 
    535510<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong> 
    … …  
    551526<p><a name="Section%203.2.2"></a> 
    552527 
    553 <h4>3.2.2 Do you support motherboard XYZ?</h4> 
     528<h3>3.2.2 Do you support motherboard XYZ?</h3> 
    554529 
    555530<p>We don't support boards, we support chips. See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
    … …  
    557532<p><a name="Section%203.2.3"></a> 
    558533 
    559 <h4>3.2.3 Do you support chip XYZ?</h4> 
     534<h3>3.2.3 Do you support chip XYZ?</h3> 
    560535 
    561536<p>This we have good answers for. 
    … …  
    569544<p><a name="Section%203.2.4"></a> 
    570545 
    571 <h4>3.2.4 Anybody working on a driver for chip XYZ?</h4> 
     546<h3>3.2.4 Anybody working on a driver for chip XYZ?</h3> 
    572547 
    573548<p>Newest Driver Status: <a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html</a> 
    … …  
    575550<p><hr> 
    576551Node:<a name="Section%203.3">Section 3.3</a>, 
    577 Next:<a rel=next accesskey=n href="#Section%203.4">Section 3.4</a>, 
    578 Previous:<a rel=previous accesskey=p href="#Section%203.2">Section 3.2</a>, 
    579 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    580 <br> 
    581  
    582 <h3>3.3 Which modules should I insert?</h3> 
     552Next:<a rel=next href="#Section%203.4">Section 3.4</a>, 
     553Previous:<a rel=previous href="#Section%203.2">Section 3.2</a>, 
     554Up:<a rel=up href="#Installation">Installation</a> 
     555<br> 
     556 
     557<h2>3.3 Which modules should I insert?</h2> 
    583558 
    584559<p><code>sensors-detect</code> will tell you. Take the <code>modprobe</code> lines it 
    … …  
    601576<p><hr> 
    602577Node:<a name="Section%203.4">Section 3.4</a>, 
    603 Next:<a rel=next accesskey=n href="#Section%203.5">Section 3.5</a>, 
    604 Previous:<a rel=previous accesskey=p href="#Section%203.3">Section 3.3</a>, 
    605 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    606 <br> 
    607  
    608 <h3>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h3> 
     578Next:<a rel=next href="#Section%203.5">Section 3.5</a>, 
     579Previous:<a rel=previous href="#Section%203.3">Section 3.3</a>, 
     580Up:<a rel=up href="#Installation">Installation</a> 
     581<br> 
     582 
     583<h2>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h2> 
    609584 
    610585<p>Yes, for any applications that use <code>libsensors,</code> including the 
    … …  
    618593<p><a name="Section%203.4.1"></a> 
    619594 
    620 <h4>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h4> 
     595<h3>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h3> 
    621596 
    622597<p>Every motherboard is different. You can customize the labels 
    … …  
    627602<p><a name="Section%203.4.2"></a> 
    628603 
    629 <h4>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h4> 
     604<h3>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h3> 
    630605 
    631606<p>You can customize them in the file <code>/etc/sensors.conf</code>. See above. 
    … …  
    633608<p><a name="Section%203.4.3"></a> 
    634609 
    635 <h4>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h4> 
     610<h3>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h3> 
    636611 
    637612<p>You forgot to run <code>sensors -s</code>. See above. 
    … …  
    639614<p><a name="Section%203.4.4"></a> 
    640615 
    641 <h4>3.4.4 One sensor isn't hooked up on my board!</h4> 
     616<h3>3.4.4 One sensor isn't hooked up on my board!</h3> 
    642617 
    643618<p>Use an <code>ignore</code> line in <code>/etc/sensors.conf</code> so it isn't 
    … …  
    646621<p><a name="Section%203.4.5"></a> 
    647622 
    648 <h4>3.4.5 I need help with <code>sensors.conf</code>!</h4> 
     623<h3>3.4.5 I need help with <code>sensors.conf</code>!</h3> 
    649624 
    650625<p>There is detailed help at the top of that file. 
    … …  
    652627<p><a name="Section%203.4.6"></a> 
    653628 
    654 <h4>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h4> 
     629<h3>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h3> 
    655630 
    656631<p>No. Good idea though. If you would like to set one up on your website 
    … …  
    659634<p><hr> 
    660635Node:<a name="Section%203.5">Section 3.5</a>, 
    661 Next:<a rel=next accesskey=n href="#Section%203.6">Section 3.6</a>, 
    662 Previous:<a rel=previous accesskey=p href="#Section%203.4">Section 3.4</a>, 
    663 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    664 <br> 
    665  
    666 <h3>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h3> 
     636Next:<a rel=next href="#Section%203.6">Section 3.6</a>, 
     637Previous:<a rel=previous href="#Section%203.4">Section 3.4</a>, 
     638Up:<a rel=up href="#Installation">Installation</a> 
     639<br> 
     640 
     641<h2>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h2> 
    667642 
    668643<p>Don't worry about them. The dependency files (which tell which 
    … …  
    674649<p><hr> 
    675650Node:<a name="Section%203.6">Section 3.6</a>, 
    676 Next:<a rel=next accesskey=n href="#Section%203.7">Section 3.7</a>, 
    677 Previous:<a rel=previous accesskey=p href="#Section%203.5">Section 3.5</a>, 
    678 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    679 <br> 
    680  
    681 <h3>3.6 I get all kinds of weird compilation errors?</h3> 
     651Next:<a rel=next href="#Section%203.7">Section 3.7</a>, 
     652Previous:<a rel=previous href="#Section%203.5">Section 3.5</a>, 
     653Up:<a rel=up href="#Installation">Installation</a> 
     654<br> 
     655 
     656<h2>3.6 I get all kinds of weird compilation errors?</h2> 
    682657 
    683658<p>Check that the correct i2c header files are used. Depending on 
    … …  
    687662<p><a name="Section%203.6.1"></a> 
    688663 
    689 <h4>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h4> 
     664<h3>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h3> 
    690665 
    691666<ul> 
    … …  
    698673<p><hr> 
    699674Node:<a name="Section%203.7">Section 3.7</a>, 
    700 Next:<a rel=next accesskey=n href="#Section%203.8">Section 3.8</a>, 
    701 Previous:<a rel=previous accesskey=p href="#Section%203.6">Section 3.6</a>, 
    702 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    703 <br> 
    704  
    705 <h3>3.7 It still does not compile or patch!</h3> 
     675Next:<a rel=next href="#Section%203.8">Section 3.8</a>, 
     676Previous:<a rel=previous href="#Section%203.6">Section 3.6</a>, 
     677Up:<a rel=up href="#Installation">Installation</a> 
     678<br> 
     679 
     680<h2>3.7 It still does not compile or patch!</h2> 
    706681 
    707682<p>Have you installed the matching version of the i2c package? Remember, 
    … …  
    714689<p><hr> 
    715690Node:<a name="Section%203.8">Section 3.8</a>, 
    716 Next:<a rel=next accesskey=n href="#Section%203.9">Section 3.9</a>, 
    717 Previous:<a rel=previous accesskey=p href="#Section%203.7">Section 3.7</a>, 
    718 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    719 <br> 
    720  
    721 <h3>3.8 <code>make install</code> fails on Mandrake kernels</h3> 
     691Next:<a rel=next href="#Section%203.9">Section 3.9</a>, 
     692Previous:<a rel=previous href="#Section%203.7">Section 3.7</a>, 
     693Up:<a rel=up href="#Installation">Installation</a> 
     694<br> 
     695 
     696<h2>3.8 <code>make install</code> fails on Mandrake kernels</h2> 
    722697 
    723698<p>Mandrake uses a non-standard <code>version.h</code> file which confuses our <code>Makefile</code>.  
    … …  
    726701<p><hr> 
    727702Node:<a name="Section%203.9">Section 3.9</a>, 
    728 Next:<a rel=next accesskey=n href="#Section%203.10">Section 3.10</a>, 
    729 Previous:<a rel=previous accesskey=p href="#Section%203.8">Section 3.8</a>, 
    730 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    731 <br> 
    732  
    733 <h3>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h3> 
     703Next:<a rel=next href="#Section%203.10">Section 3.10</a>, 
     704Previous:<a rel=previous href="#Section%203.8">Section 3.8</a>, 
     705Up:<a rel=up href="#Installation">Installation</a> 
     706<br> 
     707 
     708<h2>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h2> 
    734709 
    735710<p>Example: 
    736 <br><pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
     711<pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
    737712i2c_bit_add_bus_R8c3bc60e 
    738713i2c_bit_del_bus_R92b18f49 
    … …  
    764739<p><hr> 
    765740Node:<a name="Section%203.10">Section 3.10</a>, 
    766 Previous:<a rel=previous accesskey=p href="#Section%203.9">Section 3.9</a>, 
    767 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    768 <br> 
    769  
    770 <h3>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3> 
     741Previous:<a rel=previous href="#Section%203.9">Section 3.9</a>, 
     742Up:<a rel=up href="#Installation">Installation</a> 
     743<br> 
     744 
     745<h2>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h2> 
    771746 
    772747<p>In some versions of Redhat, an RPM is included to provide i2c support.  
    … …  
    785760old i2c stuff anymore anyway.  Just don't use it with abandon.  
    786761<li>Try (in the build directory of <code>lm_sensors)</code> 
    787 <br><pre><code>make clean</code> 
     762<pre><code>make clean</code> 
    788763<code>make</code> 
    789764</pre> 
    … …  
    796771<p><hr> 
    797772Node:<a name="Problems">Problems</a>, 
    798 Next:<a rel=next accesskey=n href="#Help">Help</a>, 
    799 Previous:<a rel=previous accesskey=p href="#Installation">Installation</a>, 
    800 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    801 <br> 
    802  
    803 <h2>4 Problems</h2> 
    804  
    805 <ul> 
    806 <li><a accesskey=1 href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
    807 <li><a accesskey=2 href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
    808 <li><a accesskey=3 href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
    809 <li><a accesskey=4 href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
    810 <li><a accesskey=5 href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
    811 <li><a accesskey=6 href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
    812 <li><a accesskey=7 href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
    813 <li><a accesskey=8 href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
    814 <li><a accesskey=9 href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
     773Next:<a rel=next href="#Help">Help</a>, 
     774Previous:<a rel=previous href="#Installation">Installation</a>, 
     775Up:<a rel=up href="#Top">Top</a> 
     776<br> 
     777 
     778<h1>4 Problems</h1> 
     779 
     780<ul> 
     781<li><a href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
     782<li><a href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
     783<li><a href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
     784<li><a href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
     785<li><a href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
     786<li><a href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
     787<li><a href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
     788<li><a href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
     789<li><a href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
    815790<li><a href="#Section%204.10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?  
    816791<li><a href="#Section%204.11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?  
    … …  
    823798<li><a href="#Section%204.18">Section 4.18</a>:         How do I configure two chips (LM87) differently?  
    824799<li><a href="#Section%204.19">Section 4.19</a>:         Dmesg says <code>Upgrade BIOS</code>! I don't want to!  
    825 <li><a href="#Section%204.20">Section 4.20</a>:         Sensors says <code>Can't access <code>/proc</code> file</code> 
     800<li><a href="#Section%204.20">Section 4.20</a>:         Sensors says <code>Can't access procfs/sysfs file</code> 
    826801<li><a href="#Section%204.21">Section 4.21</a>:         Sensors says <code>No sensors found!</code> 
    827802<li><a href="#Section%204.22">Section 4.22</a>:         Sensors output is not correct!  
    … …  
    841816<p><hr> 
    842817Node:<a name="Section%204.1">Section 4.1</a>, 
    843 Next:<a rel=next accesskey=n href="#Section%204.2">Section 4.2</a>, 
    844 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    845 <br> 
    846  
    847 <h3>4.1 My fans report exactly half/double their values compared to the BIOS?</h3> 
     818Next:<a rel=next href="#Section%204.2">Section 4.2</a>, 
     819Up:<a rel=up href="#Problems">Problems</a> 
     820<br> 
     821 
     822<h2>4.1 My fans report exactly half/double their values compared to the BIOS?</h2> 
    848823 
    849824<p>The problem with much of the sensor data is that it is impossible to 
    … …  
    853828configuration file <code>/etc/sensors.conf</code>: 
    854829 
    855 <br><pre>chip lm78-*             # Or whatever chip this relates to 
     830<pre>chip lm78-*             # Or whatever chip this relates to 
    856831compute fan1 2*@,@/2    # This will double the fan1 reading 
    857832                        # -- or -- 
    … …  
    863838<p><a name="Fans%20sometimes%2falways%20read%200!"></a> 
    864839 
    865 <h4>4.1.1 Fans sometimes/always read 0!!</h4> 
     840<h3>4.1.1 Fans sometimes/always read 0!!</h3> 
    866841 
    867842<p>You may not have a three-wire fan, which is required. 
    … …  
    872847<p><a name="I%20doubled%20the%20fan%20divisor%20and%20the%20fan%20still%20reads%207000"></a> 
    873848 
    874 <h4>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4> 
     849<h3>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h3> 
    875850 
    876851<p>Believe it or not, doubling the 'fan divisor' will not halve 
    … …  
    881856<p><hr> 
    882857Node:<a name="Section%204.2">Section 4.2</a>, 
    883 Next:<a rel=next accesskey=n href="#Section%204.3">Section 4.3</a>, 
    884 Previous:<a rel=previous accesskey=p href="#Section%204.1">Section 4.1</a>, 
    885 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    886 <br> 
    887  
    888 <h3>4.2 Why do my two LM75's report "-48 degrees"?</h3> 
     858Next:<a rel=next href="#Section%204.3">Section 4.3</a>, 
     859Previous:<a rel=previous href="#Section%204.1">Section 4.1</a>, 
     860Up:<a rel=up href="#Problems">Problems</a> 
     861<br> 
     862 
     863<h2>4.2 Why do my two LM75's report "-48 degrees"?</h2> 
    889864 
    890865<p>For starters, those aren't LM75's.  Your mainboard actually has the 
    … …  
    901876<p><hr> 
    902877Node:<a name="Section%204.3">Section 4.3</a>, 
    903 Next:<a rel=next accesskey=n href="#Section%204.4">Section 4.4</a>, 
    904 Previous:<a rel=previous accesskey=p href="#Section%204.2">Section 4.2</a>, 
    905 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    906 <br> 
    907  
    908 <h3>4.3 Why do I have two Vcore readings, I have only one processor!</h3> 
     878Next:<a rel=next href="#Section%204.4">Section 4.4</a>, 
     879Previous:<a rel=previous href="#Section%204.2">Section 4.2</a>, 
     880Up:<a rel=up href="#Problems">Problems</a> 
     881<br> 
     882 
     883<h2>4.3 Why do I have two Vcore readings, I have only one processor!</h2> 
    909884 
    910885<p>The LM78 has seven voltage sensors. The default way of 
    … …  
    923898<p><hr> 
    924899Node:<a name="Section%204.4">Section 4.4</a>, 
    925 Next:<a rel=next accesskey=n href="#Section%204.5">Section 4.5</a>, 
    926 Previous:<a rel=previous accesskey=p href="#Section%204.3">Section 4.3</a>, 
    927 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    928 <br> 
    929  
    930 <h3>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3> 
     900Next:<a rel=next href="#Section%204.5">Section 4.5</a>, 
     901Previous:<a rel=previous href="#Section%204.3">Section 4.3</a>, 
     902Up:<a rel=up href="#Problems">Problems</a> 
     903<br> 
     904 
     905<h2>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h2> 
    931906 
    932907<p>The ALARM indications in <code>sensors</code> are those reported by the 
    … …  
    952927<p><hr> 
    953928Node:<a name="Section%204.5">Section 4.5</a>, 
    954 Next:<a rel=next accesskey=n href="#Section%204.6">Section 4.6</a>, 
    955 Previous:<a rel=previous accesskey=p href="#Section%204.4">Section 4.4</a>, 
    956 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    957 <br> 
    958  
    959 <h3>4.5 My voltage readings seem to drift a bit. Is something wrong?</h3> 
     929Next:<a rel=next href="#Section%204.6">Section 4.6</a>, 
     930Previous:<a rel=previous href="#Section%204.4">Section 4.4</a>, 
     931Up:<a rel=up href="#Problems">Problems</a> 
     932<br> 
     933 
     934<h2>4.5 My voltage readings seem to drift a bit. Is something wrong?</h2> 
    960935 
    961936<p>No, probably not. If your motherboard heats up a bit, the sensed 
    … …  
    970945<p><hr> 
    971946Node:<a name="Section%204.6">Section 4.6</a>, 
    972 Next:<a rel=next accesskey=n href="#Section%204.7">Section 4.7</a>, 
    973 Previous:<a rel=previous accesskey=p href="#Section%204.5">Section 4.5</a>, 
    974 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    975 <br> 
    976  
    977 <h3>4.6 Some measurements are way out of range. What happened?</h3> 
     947Next:<a rel=next href="#Section%204.7">Section 4.7</a>, 
     948Previous:<a rel=previous href="#Section%204.5">Section 4.5</a>, 
     949Up:<a rel=up href="#Problems">Problems</a> 
     950<br> 
     951 
     952<h2>4.6 Some measurements are way out of range. What happened?</h2> 
    978953 
    979954<p>Each module tries to set limits to sensible values on initialization, 
    … …  
    991966<p><hr> 
    992967Node:<a name="Section%204.7">Section 4.7</a>, 
    993 Next:<a rel=next accesskey=n href="#Section%204.8">Section 4.8</a>, 
    994 Previous:<a rel=previous accesskey=p href="#Section%204.6">Section 4.6</a>, 
    995 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    996 <br> 
    997  
    998 <h3>4.7 What are VID lines? Why is the VID reading wrong?</h3> 
     968Next:<a rel=next href="#Section%204.8">Section 4.8</a>, 
     969Previous:<a rel=previous href="#Section%204.6">Section 4.6</a>, 
     970Up:<a rel=up href="#Problems">Problems</a> 
     971<br> 
     972 
     973<h2>4.7 What are VID lines? Why is the VID reading wrong?</h2> 
    999974 
    1000975<p>These describe the core voltage for your processor. They are 
    … …  
    1008983<p><hr> 
    1009984Node:<a name="Section%204.8">Section 4.8</a>, 
    1010 Next:<a rel=next accesskey=n href="#Section%204.9">Section 4.9</a>, 
    1011 Previous:<a rel=previous accesskey=p href="#Section%204.7">Section 4.7</a>, 
    1012 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1013 <br> 
    1014  
    1015 <h3>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3> 
     985Next:<a rel=next href="#Section%204.9">Section 4.9</a>, 
     986Previous:<a rel=previous href="#Section%204.7">Section 4.7</a>, 
     987Up:<a rel=up href="#Problems">Problems</a> 
     988<br> 
     989 
     990<h2>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h2> 
    1016991 
    1017992<p>If we would read the registers more often, it would not find the 
    … …  
    1022997<p><hr> 
    1023998Node:<a name="Section%204.9">Section 4.9</a>, 
    1024 Next:<a rel=next accesskey=n href="#Section%204.10">Section 4.10</a>, 
    1025 Previous:<a rel=previous accesskey=p href="#Section%204.8">Section 4.8</a>, 
    1026 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1027 <br> 
    1028  
    1029 <h3>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3> 
     999Next:<a rel=next href="#Section%204.10">Section 4.10</a>, 
     1000Previous:<a rel=previous href="#Section%204.8">Section 4.8</a>, 
     1001Up:<a rel=up href="#Problems">Problems</a> 
     1002<br> 
     1003 
     1004<h2>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h2> 
    10301005 
    10311006<p>ISA bus access is fast, but SMBus access is really slow. If you have 
    … …  
    10361011<p><hr> 
    10371012Node:<a name="Section%204.10">Section 4.10</a>, 
    1038 Next:<a rel=next accesskey=n href="#Section%204.11">Section 4.11</a>, 
    1039 Previous:<a rel=previous accesskey=p href="#Section%204.9">Section 4.9</a>, 
    1040 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1041 <br> 
    1042  
    1043 <h3>4.10 Can I be alerted when an ALARM occurs?</h3> 
     1013Next:<a rel=next href="#Section%204.11">Section 4.11</a>, 
     1014Previous:<a rel=previous href="#Section%204.9">Section 4.9</a>, 
     1015Up:<a rel=up href="#Problems">Problems</a> 
     1016<br> 
     1017 
     1018<h2>4.10 Can I be alerted when an ALARM occurs?</h2> 
    10441019 
    10451020<p>No, you can't; and it may well be never supported. 
    … …  
    10621037<p><hr> 
    10631038Node:<a name="Section%204.11">Section 4.11</a>, 
    1064 Next:<a rel=next accesskey=n href="#Section%204.12">Section 4.12</a>, 
    1065 Previous:<a rel=previous accesskey=p href="#Section%204.10">Section 4.10</a>, 
    1066 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1067 <br> 
    1068  
    1069 <h3>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3> 
     1039Next:<a rel=next href="#Section%204.12">Section 4.12</a>, 
     1040Previous:<a rel=previous href="#Section%204.10">Section 4.10</a>, 
     1041Up:<a rel=up href="#Problems">Problems</a> 
     1042<br> 
     1043 
     1044<h2>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h2> 
    10701045 
    10711046<p>Some chips which mainboard makers connect to the SMBus are not SMBus 
    … …  
    10811056<p><hr> 
    10821057Node:<a name="Section%204.12">Section 4.12</a>, 
    1083 Next:<a rel=next accesskey=n href="#Section%204.13">Section 4.13</a>, 
    1084 Previous:<a rel=previous accesskey=p href="#Section%204.11">Section 4.11</a>, 
    1085 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1086 <br> 
    1087  
    1088 <h3>4.12 My BIOS reports a much higher CPU temperature than your modules!</h3> 
     1058Next:<a rel=next href="#Section%204.13">Section 4.13</a>, 
     1059Previous:<a rel=previous href="#Section%204.11">Section 4.11</a>, 
     1060Up:<a rel=up href="#Problems">Problems</a> 
     1061<br> 
     1062 
     1063<h2>4.12 My BIOS reports a much higher CPU temperature than your modules!</h2> 
    10891064 
    10901065<p>We display the actual temperature of the sensor. This may not be the 
    … …  
    10961071in the module itself. You can do it through the configuration file, though: 
    10971072 
    1098 <br><pre>chip lm75-*-49                      # Or whatever chip this relates to 
     1073<pre>chip lm75-*-49                      # Or whatever chip this relates to 
    10991074label temp "Processor" 
    11001075compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula 
    … …  
    11031078<p><hr> 
    11041079Node:<a name="Section%204.13">Section 4.13</a>, 
    1105 Next:<a rel=next accesskey=n href="#Section%204.14">Section 4.14</a>, 
    1106 Previous:<a rel=previous accesskey=p href="#Section%204.12">Section 4.12</a>, 
    1107 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1108 <br> 
    1109  
    1110 <h3>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h3> 
     1080Next:<a rel=next href="#Section%204.14">Section 4.14</a>, 
     1081Previous:<a rel=previous href="#Section%204.12">Section 4.12</a>, 
     1082Up:<a rel=up href="#Problems">Problems</a> 
     1083<br> 
     1084 
     1085<h2>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h2> 
    11111086 
    11121087<p>Remember, these values do not take the configuration file 
    … …  
    11171092<p><hr> 
    11181093Node:<a name="Section%204.14">Section 4.14</a>, 
    1119 Next:<a rel=next accesskey=n href="#Section%204.15">Section 4.15</a>, 
    1120 Previous:<a rel=previous accesskey=p href="#Section%204.13">Section 4.13</a>, 
    1121 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1122 <br> 
    1123  
    1124 <h3>4.14 How do I set new limits?</h3> 
     1094Next:<a rel=next href="#Section%204.15">Section 4.15</a>, 
     1095Previous:<a rel=previous href="#Section%204.13">Section 4.13</a>, 
     1096Up:<a rel=up href="#Problems">Problems</a> 
     1097<br> 
     1098 
     1099<h2>4.14 How do I set new limits?</h2> 
    11251100 
    11261101<p>Change the limit values in <code>/etc/sensors.conf</code> and then run 
    … …  
    11291104<p><a name="I%20set%20new%20limits%20and%20it%20didnt%20work"></a> 
    11301105 
    1131 <h4>4.14.1 I set new limits and it didn't work?</h4> 
     1106<h3>4.14.1 I set new limits and it didn't work?</h3> 
    11321107 
    11331108<p>You forgot to run <code>sensors -s</code>. Put it in a <code>/etc/rc.d/...</code> file 
    … …  
    11361111<p><hr> 
    11371112Node:<a name="Section%204.15">Section 4.15</a>, 
    1138 Next:<a rel=next accesskey=n href="#Section%204.16">Section 4.16</a>, 
    1139 Previous:<a rel=previous accesskey=p href="#Section%204.14">Section 4.14</a>, 
    1140 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1141 <br> 
    1142  
    1143 <h3>4.15 Some sensors are doubly detected?</h3> 
     1113Next:<a rel=next href="#Section%204.16">Section 4.16</a>, 
     1114Previous:<a rel=previous href="#Section%204.14">Section 4.14</a>, 
     1115Up:<a rel=up href="#Problems">Problems</a> 
     1116<br> 
     1117 
     1118<h2>4.15 Some sensors are doubly detected?</h2> 
    11441119 
    11451120<p>Yes, this is still a problem. It is partially solved by alias detection 
    … …  
    11551130<p><hr> 
    11561131Node:<a name="Section%204.16">Section 4.16</a>, 
    1157 Next:<a rel=next accesskey=n href="#Section%204.17">Section 4.17</a>, 
    1158 Previous:<a rel=previous accesskey=p href="#Section%204.15">Section 4.15</a>, 
    1159 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1160 <br> 
    1161  
    1162 <h3>4.16 I ran sensors-detect, but now I get very strange readings?!?</h3> 
     1132Next:<a rel=next href="#Section%204.17">Section 4.17</a>, 
     1133Previous:<a rel=previous href="#Section%204.15">Section 4.15</a>, 
     1134Up:<a rel=up href="#Problems">Problems</a> 
     1135<br> 
     1136 
     1137<h2>4.16 I ran sensors-detect, but now I get very strange readings?!?</h2> 
    11631138 
    11641139<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards 
    … …  
    11721147<p><hr> 
    11731148Node:<a name="Section%204.17">Section 4.17</a>, 
    1174 Next:<a rel=next accesskey=n href="#Section%204.18">Section 4.18</a>, 
    1175 Previous:<a rel=previous accesskey=p href="#Section%204.16">Section 4.16</a>, 
    1176 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1177 <br> 
    1178  
    1179 <h3>4.17 Bad readings from particular chips</h3> 
     1149Next:<a rel=next href="#Section%204.18">Section 4.18</a>, 
     1150Previous:<a rel=previous href="#Section%204.16">Section 4.16</a>, 
     1151Up:<a rel=up href="#Problems">Problems</a> 
     1152<br> 
     1153 
     1154<h2>4.17 Bad readings from particular chips</h2> 
    11801155 
    11811156<p>See below for some particularly troublesome chips.  
    … …  
    11841159<p><a name="Bad%20readings%20from%20the%20AS99127F"></a> 
    11851160 
    1186 <h4>4.17.1 Bad readings from the AS99127F!</h4> 
     1161<h3>4.17.1 Bad readings from the AS99127F!</h3> 
    11871162 
    11881163<p>The Asus AS99127F is a modified version of the Winbond W83781D.  
    … …  
    11941169<p><a name="Bad%20readings%20from%20the%20VIA%20686A"></a> 
    11951170 
    1196 <h4>4.17.2 Bad readings from the VIA 686A!</h4> 
     1171<h3>4.17.2 Bad readings from the VIA 686A!</h3> 
    11971172 
    11981173<p>The Via 686A datasheet is incomplete.  
    … …  
    12051180<p><a name="Bad%20readings%20from%20the%20MTP008"></a> 
    12061181 
    1207 <h4>4.17.3 Bad readings from the MTP008!</h4> 
     1182<h3>4.17.3 Bad readings from the MTP008!</h3> 
    12081183 
    12091184<p>The MTP008 has programmable temperature sensor types.  
    … …  
    12151190<p><a name="Bad%20temperature%20readings%20from%20the%20SIS5595"></a> 
    12161191 
    1217 <h4>4.17.4 Bad temperature readings from the SIS5595!</h4> 
     1192<h3>4.17.4 Bad temperature readings from the SIS5595!</h3> 
    12181193 
    12191194<p>This chip can use multiple thermistor types and there are also 
    … …  
    12261201<p><a name="Bad%20readings%20from%20a%20w8378%5b12%5dd"></a> 
    12271202 
    1228 <h4>4.17.5 Bad readings from a w8378[12]d!</h4> 
     1203<h3>4.17.5 Bad readings from a w8378[12]d!</h3> 
    12291204 
    12301205<p>Do you own an ASUS motherboard?  Perhaps your chip is being 
    … …  
    12401215<p><a name="Bus%20hangs%20on%20Ali%201543%20on%20Asus%20P5A%20boards"></a> 
    12411216 
    1242 <h4>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4> 
     1217<h3>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h3> 
    12431218 
    12441219<p>The SMBus tends to hang on this board and it seems to get worse 
    … …  
    12491224<p><a name="Bad%20readings%20from%20LM75"></a> 
    12501225 
    1251 <h4>4.17.7 Bad readings from LM75!</h4> 
     1226<h3>4.17.7 Bad readings from LM75!</h3> 
    12521227 
    12531228<p>The LM75 detection is poor and other hardware is often misdetected 
    … …  
    12561231<p><a name="Bad%20readings%20from%20LM78"></a> 
    12571232 
    1258 <h4>4.17.8 Bad readings from LM78!</h4> 
     1233<h3>4.17.8 Bad readings from LM78!</h3> 
    12591234 
    12601235<p>The LM78 is no longer manufactured by National Semiconductor.  
    … …  
    12641239<p><a name="Bad%20readings%20from%20LM80"></a> 
    12651240 
    1266 <h4>4.17.9 Bad readings from LM80!</h4> 
     1241<h3>4.17.9 Bad readings from LM80!</h3> 
    12671242 
    12681243<p>The LM80 detection is poor and other hardware is often misdetected 
    … …  
    12711246<p><a name="Bad%20readings%20from%20it87"></a> 
    12721247 
    1273 <h4>4.17.10 Bad readings from it87!</h4> 
     1248<h3>4.17.10 Bad readings from it87!</h3> 
    12741249 
    12751250<p>The it87 temperature sesnsors are configured, unfortunately, 
    … …  
    12801255<p><hr> 
    12811256Node:<a name="Section%204.18">Section 4.18</a>, 
    1282 Next:<a rel=next accesskey=n href="#Section%204.19">Section 4.19</a>, 
    1283 Previous:<a rel=previous accesskey=p href="#Section%204.17">Section 4.17</a>, 
    1284 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1285 <br> 
    1286  
    1287 <h3>4.18 How do I configure two chips (LM87) differently?</h3> 
     1257Next:<a rel=next href="#Section%204.19">Section 4.19</a>, 
     1258Previous:<a rel=previous href="#Section%204.17">Section 4.17</a>, 
     1259Up:<a rel=up href="#Problems">Problems</a> 
     1260<br> 
     1261 
     1262<h2>4.18 How do I configure two chips (LM87) differently?</h2> 
    12881263 
    12891264<p>There is a SuperMicro board with two LM87's on it that are 
    … …  
    12921267 
    12931268<p>Make two different sections in <code>/etc/sensors.conf</code> as follows: 
    1294 <br><pre>chip "lm87-i2c-*-2c" 
     1269<pre>chip "lm87-i2c-*-2c" 
    12951270    put configuration for the chip at 0x2c here 
    12961271chip "lm87-i2c-*-2d" 
    … …  
    13031278<p><hr> 
    13041279Node:<a name="Section%204.19">Section 4.19</a>, 
    1305 Next:<a rel=next accesskey=n href="#Section%204.20">Section 4.20</a>, 
    1306 Previous:<a rel=previous accesskey=p href="#Section%204.18">Section 4.18</a>, 
    1307 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1308 <br> 
    1309  
    1310 <h3>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h3> 
     1280Next:<a rel=next href="#Section%204.20">Section 4.20</a>, 
     1281Previous:<a rel=previous href="#Section%204.18">Section 4.18</a>, 
     1282Up:<a rel=up href="#Problems">Problems</a> 
     1283<br> 
     1284 
     1285<h2>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h2> 
    13111286 
    13121287<p>If the problem is a PCI device is not present in <code>lspci</code>, the solution 
    … …  
    13231298<p><a name="Dmesg%20says%20use%20force_addr%3d0xaddr!%20What%20address%20do%20I%20use"></a> 
    13241299 
    1325 <h4>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h4> 
     1300<h3>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h3> 
    13261301 
    13271302<p>If the problem is a PCI device whose base address is not set, 
    … …  
    13351310<p><hr> 
    13361311Node:<a name="Section%204.20">Section 4.20</a>, 
    1337 Next:<a rel=next accesskey=n href="#Section%204.21">Section 4.21</a>, 
    1338 Previous:<a rel=previous accesskey=p href="#Section%204.19">Section 4.19</a>, 
    1339 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1340 <br> 
    1341  
    1342 <h3>4.20 Sensors says <code>Can't access <code>/proc</code> file</code></h3> 
     1312Next:<a rel=next href="#Section%204.21">Section 4.21</a>, 
     1313Previous:<a rel=previous href="#Section%204.19">Section 4.19</a>, 
     1314Up:<a rel=up href="#Problems">Problems</a> 
     1315<br> 
     1316 
     1317<h2>4.20 Sensors says <code>Can't access procfs/sysfs file</code></h2> 
    13431318 
    13441319<ul> 
    … …  
    13511326<p><hr> 
    13521327Node:<a name="Section%204.21">Section 4.21</a>, 
    1353 Next:<a rel=next accesskey=n href="#Section%204.22">Section 4.22</a>, 
    1354 Previous:<a rel=previous accesskey=p href="#Section%204.20">Section 4.20</a>, 
    1355 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1356 <br> 
    1357  
    1358 <h3>4.21 Sensors says <code>No sensors found!</code></h3> 
     1328Next:<a rel=next href="#Section%204.22">Section 4.22</a>, 
     1329Previous:<a rel=previous href="#Section%204.20">Section 4.20</a>, 
     1330Up:<a rel=up href="#Problems">Problems</a> 
     1331<br> 
     1332 
     1333<h2>4.21 Sensors says <code>No sensors found!</code></h2> 
    13591334 
    13601335<ul> 
    … …  
    13691344<p><hr> 
    13701345Node:<a name="Section%204.22">Section 4.22</a>, 
    1371 Next:<a rel=next accesskey=n href="#Section%204.23">Section 4.23</a>, 
    1372 Previous:<a rel=previous accesskey=p href="#Section%204.21">Section 4.21</a>, 
    1373 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1374 <br> 
    1375  
    1376 <h3>4.22 Sensors output is not correct!</h3> 
     1346Next:<a rel=next href="#Section%204.23">Section 4.23</a>, 
     1347Previous:<a rel=previous href="#Section%204.21">Section 4.21</a>, 
     1348Up:<a rel=up href="#Problems">Problems</a> 
     1349<br> 
     1350 
     1351<h2>4.22 Sensors output is not correct!</h2> 
    13771352 
    13781353<p>What specifically is the trouble? 
    … …  
    13951370<p><hr> 
    13961371Node:<a name="Section%204.23">Section 4.23</a>, 
    1397 Next:<a rel=next accesskey=n href="#Section%204.24">Section 4.24</a>, 
    1398 Previous:<a rel=previous accesskey=p href="#Section%204.22">Section 4.22</a>, 
    1399 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1400 <br> 
    1401  
    1402 <h3>4.23 What is at I2C address XXX?</h3> 
     1372Next:<a rel=next href="#Section%204.24">Section 4.24</a>, 
     1373Previous:<a rel=previous href="#Section%204.22">Section 4.22</a>, 
     1374Up:<a rel=up href="#Problems">Problems</a> 
     1375<br> 
     1376 
     1377<h2>4.23 What is at I2C address XXX?</h2> 
    14031378 
    14041379<p>In general, we don't know. Start by running <code>sensors-detect</code>.  
    … …  
    14081383<p><a name="What%20is%20at%20I2C%20address%200x69"></a> 
    14091384 
    1410 <h4>4.23.1 What is at I2C address 0x69?</h4> 
     1385<h3>4.23.1 What is at I2C address 0x69?</h3> 
    14111386 
    14121387<p>A clock chip. Often, accessing these clock chips in the wrong 
    … …  
    14181393<p><a name="What%20is%20at%20I2C%20addresses%200x50%20-%200x57"></a> 
    14191394 
    1420 <h4>4.23.2 What is at I2C addresses 0x50 - 0x57?</h4> 
     1395<h3>4.23.2 What is at I2C addresses 0x50 - 0x57?</h3> 
    14211396 
    14221397<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to 
    … …  
    14261401<p><a name="What%20is%20at%20I2C%20addresses%200x30%20-%200x37"></a> 
    14271402 
    1428 <h4>4.23.3 What is at I2C addresses 0x30 - 0x37?</h4> 
     1403<h3>4.23.3 What is at I2C addresses 0x30 - 0x37?</h3> 
    14291404 
    14301405<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs 
    … …  
    14361411<p><hr> 
    14371412Node:<a name="Section%204.24">Section 4.24</a>, 
    1438 Next:<a rel=next accesskey=n href="#Section%204.25">Section 4.25</a>, 
    1439 Previous:<a rel=previous accesskey=p href="#Section%204.23">Section 4.23</a>, 
    1440 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1441 <br> 
    1442  
    1443 <h3>4.24 Sensors-detect doesn't work at all</h3> 
     1413Next:<a rel=next href="#Section%204.25">Section 4.25</a>, 
     1414Previous:<a rel=previous href="#Section%204.23">Section 4.23</a>, 
     1415Up:<a rel=up href="#Problems">Problems</a> 
     1416<br> 
     1417 
     1418<h2>4.24 Sensors-detect doesn't work at all</h2> 
    14441419 
    14451420<p>It could be many things. What was the problem? See <a href="#Section%204.31">Problems on particular motherboards</a>. 
    … …  
    14471422<p><a name="Sensors-detect%20says%20%22Couldnt%20open%20%2fproc%2fbus%2fi2c%3f!%3f%22"></a> 
    14481423 
    1449 <h4>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4> 
     1424<h3>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h3> 
    14501425 
    14511426<p>You don't have i2c support in your kernel, or the i2c-core module 
    … …  
    14541429<p><a name="Sensors-detect%20says%20%22Cant%20open%20%2fdev%2fi2c%5b-%2f%5d0%22"></a> 
    14551430 
    1456 <h4>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4> 
     1431<h3>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h3> 
    14571432 
    14581433<p>Your <code>/dev/i2c-0,</code> <code>/dev/i2c0</code>, or <code>/dev/i2c/0</code> files do not exist 
    … …  
    14631438<p><a name="Sensors-detect%20doesnt%20find%20any%20sensors"></a> 
    14641439 
    1465 <h4>4.24.3 Sensors-detect doesn't find any sensors!</h4> 
     1440<h3>4.24.3 Sensors-detect doesn't find any sensors!</h3> 
    14661441 
    14671442<p>Either 
    … …  
    14861461<p><hr> 
    14871462Node:<a name="Section%204.25">Section 4.25</a>, 
    1488 Next:<a rel=next accesskey=n href="#Section%204.26">Section 4.26</a>, 
    1489 Previous:<a rel=previous accesskey=p href="#Section%204.24">Section 4.24</a>, 
    1490 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1491 <br> 
    1492  
    1493 <h3>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h3> 
     1463Next:<a rel=next href="#Section%204.26">Section 4.26</a>, 
     1464Previous:<a rel=previous href="#Section%204.24">Section 4.24</a>, 
     1465Up:<a rel=up href="#Problems">Problems</a> 
     1466<br> 
     1467 
     1468<h2>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h2> 
    14941469 
    14951470<p>These are errors from the libsensors library in 
    … …  
    15001475<p><hr> 
    15011476Node:<a name="Section%204.26">Section 4.26</a>, 
    1502 Next:<a rel=next accesskey=n href="#Section%204.27">Section 4.27</a>, 
    1503 Previous:<a rel=previous accesskey=p href="#Section%204.25">Section 4.25</a>, 
    1504 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1505 <br> 
    1506  
    1507 <h3>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3> 
     1477Next:<a rel=next href="#Section%204.27">Section 4.27</a>, 
     1478Previous:<a rel=previous href="#Section%204.25">Section 4.25</a>, 
     1479Up:<a rel=up href="#Problems">Problems</a> 
     1480<br> 
     1481 
     1482<h2>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h2> 
    15081483 
    15091484<p>If <code>sensors</code> only says this, for example, and doesn't 
    15101485provide any actual data at all: 
    15111486 
    1512 <br><pre>it87-isa-0290 
     1487<pre>it87-isa-0290 
    15131488Adapter: ISA adapter 
    15141489Algorithm: ISA algorithm 
    … …  
    15221497<p><hr> 
    15231498Node:<a name="Section%204.27">Section 4.27</a>, 
    1524 Next:<a rel=next accesskey=n href="#Section%204.28">Section 4.28</a>, 
    1525 Previous:<a rel=previous accesskey=p href="#Section%204.26">Section 4.26</a>, 
    1526 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1527 <br> 
    1528  
    1529 <h3>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h3> 
     1499Next:<a rel=next href="#Section%204.28">Section 4.28</a>, 
     1500Previous:<a rel=previous href="#Section%204.26">Section 4.26</a>, 
     1501Up:<a rel=up href="#Problems">Problems</a> 
     1502<br> 
     1503 
     1504<h2>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h2> 
    15301505 
    15311506<p>You have a <code>libsensors/sensors</code> mismatch. <code>sensors</code> is unable to 
    … …  
    15391514<p><hr> 
    15401515Node:<a name="Section%204.28">Section 4.28</a>, 
    1541 Next:<a rel=next accesskey=n href="#Section%204.29">Section 4.29</a>, 
    1542 Previous:<a rel=previous accesskey=p href="#Section%204.27">Section 4.27</a>, 
    1543 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1544 <br> 
    1545  
    1546 <h3>4.28 Sensors doesn't find any sensors, just eeproms.</h3> 
     1516Next:<a rel=next href="#Section%204.29">Section 4.29</a>, 
     1517Previous:<a rel=previous href="#Section%204.27">Section 4.27</a>, 
     1518Up:<a rel=up href="#Problems">Problems</a> 
     1519<br> 
     1520 
     1521<h2>4.28 Sensors doesn't find any sensors, just eeproms.</h2> 
    15471522 
    15481523<p>See <a href="#Section%204.24">Sensors-detect doesnt work at all</a>, if <code>sensors-detect</code> failed to find any sensors. 
    … …  
    15561531<p><hr> 
    15571532Node:<a name="Section%204.29">Section 4.29</a>, 
    1558 Next:<a rel=next accesskey=n href="#Section%204.30">Section 4.30</a>, 
    1559 Previous:<a rel=previous accesskey=p href="#Section%204.28">Section 4.28</a>, 
    1560 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1561 <br> 
    1562  
    1563 <h3>4.29 Inserting modules hangs my board</h3> 
     1533Next:<a rel=next href="#Section%204.30">Section 4.30</a>, 
     1534Previous:<a rel=previous href="#Section%204.28">Section 4.28</a>, 
     1535Up:<a rel=up href="#Problems">Problems</a> 
     1536<br> 
     1537 
     1538<h2>4.29 Inserting modules hangs my board</h2> 
    15641539 
    15651540<p>There are several possible causes: 
    … …  
    15741549<p><hr> 
    15751550Node:<a name="Section%204.30">Section 4.30</a>, 
    1576 Next:<a rel=next accesskey=n href="#Section%204.31">Section 4.31</a>, 
    1577 Previous:<a rel=previous accesskey=p href="#Section%204.29">Section 4.29</a>, 
    1578 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1579 <br> 
    1580  
    1581 <h3>4.30 Inserting modules slows down my board</h3> 
     1551Next:<a rel=next href="#Section%204.31">Section 4.31</a>, 
     1552Previous:<a rel=previous href="#Section%204.29">Section 4.29</a>, 
     1553Up:<a rel=up href="#Problems">Problems</a> 
     1554<br> 
     1555 
     1556<h2>4.30 Inserting modules slows down my board</h2> 
    15821557 
    15831558<p>Generally this is caused by an overtemperature alarm output from 
    … …  
    15891564<p><hr> 
    15901565Node:<a name="Section%204.31">Section 4.31</a>, 
    1591 Next:<a rel=next accesskey=n href="#Section%204.32">Section 4.32</a>, 
    1592 Previous:<a rel=previous accesskey=p href="#Section%204.30">Section 4.30</a>, 
    1593 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1594 <br> 
    1595  
    1596 <h3>4.31 Problems on particular motherboards</h3> 
     1566Next:<a rel=next href="#Section%204.32">Section 4.32</a>, 
     1567Previous:<a rel=previous href="#Section%204.30">Section 4.30</a>, 
     1568Up:<a rel=up href="#Problems">Problems</a> 
     1569<br> 
     1570 
     1571<h2>4.31 Problems on particular motherboards</h2> 
    15971572 
    15981573<p>The following boards have unique problems and solutions. 
    … …  
    16001575<p><a name="Asus%20P4B"></a> 
    16011576 
    1602 <h4>4.31.1 Asus P4B</h4> 
     1577<h3>4.31.1 Asus P4B</h3> 
    16031578 
    16041579<p>See <code>prog/hotplug/README.p4b</code> if your SMBus master is not found. 
    … …  
    16061581<p><a name="Tyan%202460%202462"></a> 
    16071582 
    1608 <h4>4.31.2 Tyan 2460, 2462</h4> 
     1583<h3>4.31.2 Tyan 2460, 2462</h3> 
    16091584 
    16101585<p>See support tickets 805, 765, 781, 812, 813, and 867 for information. 
    … …  
    16121587<p><a name="Tyan%202466"></a> 
    16131588 
    1614 <h4>4.31.3 Tyan 2466</h4> 
     1589<h3>4.31.3 Tyan 2466</h3> 
    16151590 
    16161591<p>See support tickets 941, 840, and 841 for information. 
    … …  
    16181593<p><a name="Tyan%202688"></a> 
    16191594 
    1620 <h4>4.31.4 Tyan 2688</h4> 
     1595<h3>4.31.4 Tyan 2688</h3> 
    16211596 
    16221597<p>For board hangs, see support ticket 721 for information.  
    … …  
    16251600<p><hr> 
    16261601Node:<a name="Section%204.32">Section 4.32</a>, 
    1627 Next:<a rel=next accesskey=n href="#Section%204.33">Section 4.33</a>, 
    1628 Previous:<a rel=previous accesskey=p href="#Section%204.31">Section 4.31</a>, 
    1629 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1630 <br> 
    1631  
    1632 <h3>4.32 Problems on particular systems</h3> 
     1602Next:<a rel=next href="#Section%204.33">Section 4.33</a>, 
     1603Previous:<a rel=previous href="#Section%204.31">Section 4.31</a>, 
     1604Up:<a rel=up href="#Problems">Problems</a> 
     1605<br> 
     1606 
     1607<h2>4.32 Problems on particular systems</h2> 
    16331608 
    16341609<p>For IBM systems, see <code>README.thinkpad</code>. 
    … …  
    16361611<p><hr> 
    16371612Node:<a name="Section%204.33">Section 4.33</a>, 
    1638 Previous:<a rel=previous accesskey=p href="#Section%204.32">Section 4.32</a>, 
    1639 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1640 <br> 
    1641  
    1642 <h3>4.33 Problems on 2.6 kernels</h3> 
     1613Previous:<a rel=previous href="#Section%204.32">Section 4.32</a>, 
     1614Up:<a rel=up href="#Problems">Problems</a> 
     1615<br> 
     1616 
     1617<h2>4.33 Problems on 2.6 kernels</h2> 
    16431618 
    16441619<p>Not all drivers have been ported to 2.6. If your favorite driver is not 
    … …  
    16511626<p><hr> 
    16521627Node:<a name="Help">Help</a>, 
    1653 Next:<a rel=next accesskey=n href="#Contribute">Contribute</a>, 
    1654 Previous:<a rel=previous accesskey=p href="#Problems">Problems</a>, 
    1655 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1656 <br> 
    1657  
    1658 <h2>5 How to Ask for Help</h2> 
    1659  
    1660 <ul> 
    1661 <li><a accesskey=1 href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
    1662 <li><a accesskey=2 href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
    1663 <li><a accesskey=3 href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
    1664 <li><a accesskey=4 href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
    1665 <li><a accesskey=5 href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
    1666 <li><a accesskey=6 href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
    1667 <li><a accesskey=7 href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
    1668 <li><a accesskey=8 href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
     1628Next:<a rel=next href="#Contribute">Contribute</a>, 
     1629Previous:<a rel=previous href="#Problems">Problems</a>, 
     1630Up:<a rel=up href="#Top">Top</a> 
     1631<br> 
     1632 
     1633<h1>5 How to Ask for Help</h1> 
     1634 
     1635<ul> 
     1636<li><a href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
     1637<li><a href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
     1638<li><a href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
     1639<li><a href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
     1640<li><a href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
     1641<li><a href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
     1642<li><a href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
     1643<li><a href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
    16691644</ul> 
    16701645 
    16711646<p><hr> 
    16721647Node:<a name="Section%205.1">Section 5.1</a>, 
    1673 Next:<a rel=next accesskey=n href="#Section%205.2">Section 5.2</a>, 
    1674 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1675 <br> 
    1676  
    1677 <h3>5.1 What to send us when asking for help</h3> 
     1648Next:<a rel=next href="#Section%205.2">Section 5.2</a>, 
     1649Up:<a rel=up href="#Help">Help</a> 
     1650<br> 
     1651 
     1652<h2>5.1 What to send us when asking for help</h2> 
    16781653 
    16791654<p>We are always willing to answer questions if things don't work out.  
    … …  
    17171692<p><hr> 
    17181693Node:<a name="Section%205.2">Section 5.2</a>, 
    1719 Next:<a rel=next accesskey=n href="#Section%205.3">Section 5.3</a>, 
    1720 Previous:<a rel=previous accesskey=p href="#Section%205.1">Section 5.1</a>, 
    1721 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1722 <br> 
    1723  
    1724 <h3>5.2 What to do if a module won't insert?</h3> 
     1694Next:<a rel=next href="#Section%205.3">Section 5.3</a>, 
     1695Previous:<a rel=previous href="#Section%205.1">Section 5.1</a>, 
     1696Up:<a rel=up href="#Help">Help</a> 
     1697<br> 
     1698 
     1699<h2>5.2 What to do if a module won't insert?</h2> 
    17251700 
    17261701<p>Did you use <code>modprobe</code> instead of <code>insmod</code>??? Don't use insmod. 
    … …  
    17361711<p><hr> 
    17371712Node:<a name="Section%205.3">Section 5.3</a>, 
    1738 Next:<a rel=next accesskey=n href="#Section%205.4">Section 5.4</a>, 
    1739 Previous:<a rel=previous accesskey=p href="#Section%205.2">Section 5.2</a>, 
    1740 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1741 <br> 
    1742  
    1743 <h3>5.3 What to do if it inserts, but nothing happens?</h3> 
     1713Next:<a rel=next href="#Section%205.4">Section 5.4</a>, 
     1714Previous:<a rel=previous href="#Section%205.2">Section 5.2</a>, 
     1715Up:<a rel=up href="#Help">Help</a> 
     1716<br> 
     1717 
     1718<h2>5.3 What to do if it inserts, but nothing happens?</h2> 
    17441719 
    17451720<p>For an ISA sensor chip, did you also <code>modprobe i2c-isa</code>? It must be inserted. 
    … …  
    17541729<p><hr> 
    17551730Node:<a name="Section%205.4">Section 5.4</a>, 
    1756 Next:<a rel=next accesskey=n href="#Section%205.5">Section 5.5</a>, 
    1757 Previous:<a rel=previous accesskey=p href="#Section%205.3">Section 5.3</a>, 
    1758 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1759 <br> 
    1760  
    1761 <h3>5.4 What to do if I read only bogus information?</h3> 
     1731Next:<a rel=next href="#Section%205.5">Section 5.5</a>, 
     1732Previous:<a rel=previous href="#Section%205.3">Section 5.3</a>, 
     1733Up:<a rel=up href="#Help">Help</a> 
     1734<br> 
     1735 
     1736<h2>5.4 What to do if I read only bogus information?</h2> 
    17621737 
    17631738<p>It may be that this was a mis-detection: the chip may not be 
    … …  
    17691744<p><hr> 
    17701745Node:<a name="Section%205.5">Section 5.5</a>, 
    1771 Next:<a rel=next accesskey=n href="#Section%205.6">Section 5.6</a>, 
    1772 Previous:<a rel=previous accesskey=p href="#Section%205.4">Section 5.4</a>, 
    1773 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1774 <br> 
    1775  
    1776 <h3>5.5 What to do if you have other problems?</h3> 
     1746Next:<a rel=next href="#Section%205.6">Section 5.6</a>, 
     1747Previous:<a rel=previous href="#Section%205.4">Section 5.4</a>, 
     1748Up:<a rel=up href="#Help">Help</a> 
     1749<br> 
     1750 
     1751<h2>5.5 What to do if you have other problems?</h2> 
    17771752 
    17781753<p>Again, send the output listed above. 
    … …  
    17801755<p><hr> 
    17811756Node:<a name="Section%205.6">Section 5.6</a>, 
    1782 Next:<a rel=next accesskey=n href="#Section%205.7">Section 5.7</a>, 
    1783 Previous:<a rel=previous accesskey=p href="#Section%205.5">Section 5.5</a>, 
    1784 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1785 <br> 
    1786  
    1787 <h3>5.6 What if it just works like a charm?</h3> 
     1757Next:<a rel=next href="#Section%205.7">Section 5.7</a>, 
     1758Previous:<a rel=previous href="#Section%205.5">Section 5.5</a>, 
     1759Up:<a rel=up href="#Help">Help</a> 
     1760<br> 
     1761 
     1762<h2>5.6 What if it just works like a charm?</h2> 
    17881763 
    17891764<p>Drop us a mail if you feel like it, mentioning the mainboard and 
    … …  
    17921767<p><hr> 
    17931768Node:<a name="Section%205.7">Section 5.7</a>, 
    1794 Next:<a rel=next accesskey=n href="#Section%205.8">Section 5.8</a>, 
    1795 Previous:<a rel=previous accesskey=p href="#Section%205.6">Section 5.6</a>, 
    1796 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1797 <br> 
    1798  
    1799 <h3>5.7 How do I update a ticket?</h3> 
     1769Next:<a rel=next href="#Section%205.8">Section 5.8</a>, 
     1770Previous:<a rel=previous href="#Section%205.6">Section 5.6</a>, 
     1771Up:<a rel=up href="#Help">Help</a> 
     1772<br> 
     1773 
     1774<h2>5.7 How do I update a ticket?</h2> 
    18001775 
    18011776<p>You can't. Only developers can. Follow up by emailing us 
    … …  
    18061781<p><hr> 
    18071782Node:<a name="Section%205.8">Section 5.8</a>, 
    1808 Previous:<a rel=previous accesskey=p href="#Section%205.7">Section 5.7</a>, 
    1809 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1810 <br> 
    1811  
    1812 <h3>5.8 How do I follow up on a ticket?</h3> 
     1783Previous:<a rel=previous href="#Section%205.7">Section 5.7</a>, 
     1784Up:<a rel=up href="#Help">Help</a> 
     1785<br> 
     1786 
     1787<h2>5.8 How do I follow up on a ticket?</h2> 
    18131788 
    18141789<p>Follow up by emailing us at <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> 
    … …  
    18171792<p><hr> 
    18181793Node:<a name="Contribute">Contribute</a>, 
    1819 Next:<a rel=next accesskey=n href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    1820 Previous:<a rel=previous accesskey=p href="#Help">Help</a>, 
    1821 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1822 <br> 
    1823  
    1824 <h2>6 How to Contribute</h2> 
    1825  
    1826 <ul> 
    1827 <li><a accesskey=1 href="#Section%206.1">Section 6.1</a>:   How to write a driver 
    1828 <li><a accesskey=2 href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
    1829 <li><a accesskey=3 href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
    1830 <li><a accesskey=4 href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
    1831 <li><a accesskey=5 href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
    1832 <li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
    1833 <li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
    1834 <li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to get release announcements 
    1835 <li><a accesskey=9 href="#Section%206.9">Section 6.9</a>:   How to block spam on the project mailing list 
     1794Next:<a rel=next href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     1795Previous:<a rel=previous href="#Help">Help</a>, 
     1796Up:<a rel=up href="#Top">Top</a> 
     1797<br> 
     1798 
     1799<h1>6 How to Contribute</h1> 
     1800 
     1801<ul> 
     1802<li><a href="#Section%206.1">Section 6.1</a>:   How to write a driver 
     1803<li><a href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
     1804<li><a href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
     1805<li><a href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
     1806<li><a href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
     1807<li><a href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
     1808<li><a href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
     1809<li><a href="#Section%206.8">Section 6.8</a>:   How to get release announcements 
     1810<li><a href="#Section%206.9">Section 6.9</a>:   How to block spam on the project mailing list 
    18361811</ul> 
    18371812 
    18381813<p><hr> 
    18391814Node:<a name="Section%206.1">Section 6.1</a>, 
    1840 Next:<a rel=next accesskey=n href="#Section%206.2">Section 6.2</a>, 
    1841 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1842 <br> 
    1843  
    1844 <h3>6.1 How to write a driver</h3> 
     1815Next:<a rel=next href="#Section%206.2">Section 6.2</a>, 
     1816Up:<a rel=up href="#Contribute">Contribute</a> 
     1817<br> 
     1818 
     1819<h2>6.1 How to write a driver</h2> 
    18451820 
    18461821<p>See <code>doc/developers/new_drivers</code> in our package for instructions. 
    … …  
    18481823<p><hr> 
    18491824Node:<a name="Section%206.2">Section 6.2</a>, 
    1850 Next:<a rel=next accesskey=n href="#Section%206.3">Section 6.3</a>, 
    1851 Previous:<a rel=previous accesskey=p href="#Section%206.1">Section 6.1</a>, 
    1852 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1853 <br> 
    1854  
    1855 <h3>6.2 How to get CVS access</h3> 
     1825Next:<a rel=next href="#Section%206.3">Section 6.3</a>, 
     1826Previous:<a rel=previous href="#Section%206.1">Section 6.1</a>, 
     1827Up:<a rel=up href="#Contribute">Contribute</a> 
     1828<br> 
     1829 
     1830<h2>6.2 How to get CVS access</h2> 
    18561831 
    18571832<p>For anonymous CVS read access, see the instructions on our download page.  
    … …  
    18641839<p><hr> 
    18651840Node:<a name="Section%206.3">Section 6.3</a>, 
    1866 Next:<a rel=next accesskey=n href="#Section%206.4">Section 6.4</a>, 
    1867 Previous:<a rel=previous accesskey=p href="#Section%206.2">Section 6.2</a>, 
    1868 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1869 <br> 
    1870  
    1871 <h3>6.3 How to donate hardware to the project</h3> 
     1841Next:<a rel=next href="#Section%206.4">Section 6.4</a>, 
     1842Previous:<a rel=previous href="#Section%206.2">Section 6.2</a>, 
     1843Up:<a rel=up href="#Contribute">Contribute</a> 
     1844<br> 
     1845 
     1846<h2>6.3 How to donate hardware to the project</h2> 
    18721847 
    18731848<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. 
    … …  
    18751850<p><hr> 
    18761851Node:<a name="Section%206.4">Section 6.4</a>, 
    1877 Next:<a rel=next accesskey=n href="#Section%206.5">Section 6.5</a>, 
    1878 Previous:<a rel=previous accesskey=p href="#Section%206.3">Section 6.3</a>, 
    1879 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1880 <br> 
    1881  
    1882 <h3>6.4 How to join the project mailing list</h3> 
     1852Next:<a rel=next href="#Section%206.5">Section 6.5</a>, 
     1853Previous:<a rel=previous href="#Section%206.3">Section 6.3</a>, 
     1854Up:<a rel=up href="#Contribute">Contribute</a> 
     1855<br> 
     1856 
     1857<h2>6.4 How to join the project mailing list</h2> 
    18831858 
    18841859<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. Sorry, 
    … …  
    18921867<p><hr> 
    18931868Node:<a name="Section%206.5">Section 6.5</a>, 
    1894 Next:<a rel=next accesskey=n href="#Section%206.6">Section 6.6</a>, 
    1895 Previous:<a rel=previous accesskey=p href="#Section%206.4">Section 6.4</a>, 
    1896 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1897 <br> 
    1898  
    1899 <h3>6.5 How to access mailing list archives</h3> 
     1869Next:<a rel=next href="#Section%206.6">Section 6.6</a>, 
     1870Previous:<a rel=previous href="#Section%206.4">Section 6.4</a>, 
     1871Up:<a rel=up href="#Contribute">Contribute</a> 
     1872<br> 
     1873 
     1874<h2>6.5 How to access mailing list archives</h2> 
    19001875 
    19011876<p>The mailing list archive is at: <a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a> 
    … …  
    19041879<p><hr> 
    19051880Node:<a name="Section%206.6">Section 6.6</a>, 
    1906 Next:<a rel=next accesskey=n href="#Section%206.7">Section 6.7</a>, 
    1907 Previous:<a rel=previous accesskey=p href="#Section%206.5">Section 6.5</a>, 
    1908 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1909 <br> 
    1910  
    1911 <h3>6.6 How to submit a patch</h3> 
     1881Next:<a rel=next href="#Section%206.7">Section 6.7</a>, 
     1882Previous:<a rel=previous href="#Section%206.5">Section 6.5</a>, 
     1883Up:<a rel=up href="#Contribute">Contribute</a> 
     1884<br> 
     1885 
     1886<h2>6.6 How to submit a patch</h2> 
    19121887 
    19131888<p>Check out the latest from CVS, then copy the directory to another 
    … …  
    19181893<p><hr> 
    19191894Node:<a name="Section%206.7">Section 6.7</a>, 
    1920 Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>, 
    1921 Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>, 
    1922 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1923 <br> 
    1924  
    1925 <h3>6.7 How to REALLY help</h3> 
     1895Next:<a rel=next href="#Section%206.8">Section 6.8</a>, 
     1896Previous:<a rel=previous href="#Section%206.6">Section 6.6</a>, 
     1897Up:<a rel=up href="#Contribute">Contribute</a> 
     1898<br> 
     1899 
     1900<h2>6.7 How to REALLY help</h2> 
    19261901 
    19271902<p>Believe it or not, what we really need help with are: 
    … …  
    19391914<p><hr> 
    19401915Node:<a name="Section%206.8">Section 6.8</a>, 
    1941 Next:<a rel=next accesskey=n href="#Section%206.9">Section 6.9</a>, 
    1942 Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>, 
    1943 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1944 <br> 
    1945  
    1946 <h3>6.8 How to get release announcements</h3> 
     1916Next:<a rel=next href="#Section%206.9">Section 6.9</a>, 
     1917Previous:<a rel=previous href="#Section%206.7">Section 6.7</a>, 
     1918Up:<a rel=up href="#Contribute">Contribute</a> 
     1919<br> 
     1920 
     1921<h2>6.8 How to get release announcements</h2> 
    19471922 
    19481923<p>We don't have a separate release announcement mailing list; 
    … …  
    19541929<p><hr> 
    19551930Node:<a name="Section%206.9">Section 6.9</a>, 
    1956 Previous:<a rel=previous accesskey=p href="#Section%206.8">Section 6.8</a>, 
    1957 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1958 <br> 
    1959  
    1960 <h3>6.9 How to block spam on the project mailing list</h3> 
     1931Previous:<a rel=previous href="#Section%206.8">Section 6.8</a>, 
     1932Up:<a rel=up href="#Contribute">Contribute</a> 
     1933<br> 
     1934 
     1935<h2>6.9 How to block spam on the project mailing list</h2> 
    19611936 
    19621937<p>Sorry, we know the spam is a hassle.  It would be nice to have a 
    … …  
    19721947<p><hr> 
    19731948Node:<a name="Version%201%20Specifics">Version 1 Specifics</a>, 
    1974 Next:<a rel=next accesskey=n href="#Document%20Revisions">Document Revisions</a>, 
    1975 Previous:<a rel=previous accesskey=p href="#Contribute">Contribute</a>, 
    1976 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1977 <br> 
    1978  
    1979 <h2>7 Version 1 Specific Questions</h2> 
    1980  
    1981 <ul> 
    1982 <li><a accesskey=1 href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
    1983 <li><a accesskey=2 href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
    1984 <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.  
    1985 <li><a accesskey=4 href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
     1949Next:<a rel=next href="#Document%20Revisions">Document Revisions</a>, 
     1950Previous:<a rel=previous href="#Contribute">Contribute</a>, 
     1951Up:<a rel=up href="#Top">Top</a> 
     1952<br> 
     1953 
     1954<h1>7 Version 1 Specific Questions</h1> 
     1955 
     1956<ul> 
     1957<li><a href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
     1958<li><a href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
     1959<li><a href="#Section%207.3">Section 7.3</a>:   I get a "No sensor data yet (try again in a few moments)" msg.  
     1960<li><a href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
    19861961</ul> 
    19871962 
    … …  
    19901965<p><hr> 
    19911966Node:<a name="Section%207.1">Section 7.1</a>, 
    1992 Next:<a rel=next accesskey=n href="#Section%207.2">Section 7.2</a>, 
    1993 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1994 <br> 
    1995  
    1996 <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> 
     1967Next:<a rel=next href="#Section%207.2">Section 7.2</a>, 
     1968Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1969<br> 
     1970 
     1971<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> 
    19971972 
    19981973<p>Currently, our code only assumes that an SMBus exists if it originates 
    … …  
    20171992<p><hr> 
    20181993Node:<a name="Section%207.2">Section 7.2</a>, 
    2019 Next:<a rel=next accesskey=n href="#Section%207.3">Section 7.3</a>, 
    2020 Previous:<a rel=previous accesskey=p href="#Section%207.1">Section 7.1</a>, 
    2021 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2022 <br> 
    2023  
    2024 <h3>7.2 The modules won't load, saying 'SMBus not detected'.</h3> 
     1994Next:<a rel=next href="#Section%207.3">Section 7.3</a>, 
     1995Previous:<a rel=previous href="#Section%207.1">Section 7.1</a>, 
     1996Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1997<br> 
     1998 
     1999<h2>7.2 The modules won't load, saying 'SMBus not detected'.</h2> 
    20252000 
    20262001<p>This should no longer be an issue in 1.4.10 and later; it will 
    … …  
    20292004<p><hr> 
    20302005Node:<a name="Section%207.3">Section 7.3</a>, 
    2031 Next:<a rel=next accesskey=n href="#Section%207.4">Section 7.4</a>, 
    2032 Previous:<a rel=previous accesskey=p href="#Section%207.2">Section 7.2</a>, 
    2033 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2034 <br> 
    2035  
    2036 <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> 
     2006Next:<a rel=next href="#Section%207.4">Section 7.4</a>, 
     2007Previous:<a rel=previous href="#Section%207.2">Section 7.2</a>, 
     2008Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     2009<br> 
     2010 
     2011<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> 
    20372012 
    20382013<p>It takes about 1.5 seconds for the LM78 to update all its sensor 
    … …  
    20472022<p><hr> 
    20482023Node:<a name="Section%207.4">Section 7.4</a>, 
    2049 Previous:<a rel=previous accesskey=p href="#Section%207.3">Section 7.3</a>, 
    2050 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2051 <br> 
    2052  
    2053 <h3>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3> 
     2024Previous:<a rel=previous href="#Section%207.3">Section 7.3</a>, 
     2025Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     2026<br> 
     2027 
     2028<h2>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h2> 
    20542029 
    20552030<p>This is a bug we have only observed on Dell computers. There is 
    … …  
    20632038<p><hr> 
    20642039Node:<a name="Document%20Revisions">Document Revisions</a>, 
    2065 Previous:<a rel=previous accesskey=p href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    2066 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    2067 <br> 
    2068  
    2069 <h2>Appendix A Revision History of This Document</h2> 
     2040Previous:<a rel=previous href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     2041Up:<a rel=up href="#Top">Top</a> 
     2042<br> 
     2043 
     2044<h1>Appendix A Revision History of This Document</h1> 
    20702045 
    20712046<ul> 
    … …  
    20952070 
    20962071</body></html> 
     2072