Changeset 1733

Show
Ignore:
Timestamp:
04/15/03 16:47:32 (10 years ago)
Author:
khali
Message:

Added reference to README.thinkpad, as suggested by Moritz

Moeller-Herrmann.

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

Legend:

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

    r1713 r1733  
    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***************** 
     
    11597    4.31.3 Tyan 2466 
    11698    4.31.4 Tyan 2688 
     99  4.32 Problems on particular systems 
    117100 
    1181015 How to Ask for Help 
     
    12041187Inserting modules hangs my board: Section 4.29. 
    12051188 
     11894.32 Problems on particular systems 
     1190=================================== 
     1191 
     1192   For IBM systems, see `README.thinkpad'. 
     1193 
    120611945 How to Ask for Help 
    12071195********************* 
     
    14931481 
    14941482   * Rev 1.0 Written by Philip Edelbrock, 19980803 
     1483 
  • lm-sensors/trunk/doc/lm_sensors-FAQ.html

    r1713 r1733  
    1 <html lang="en"> 
    2 <head> 
     1<html lang="en"><head> 
    32<title>Sensors FAQ for lm_sensors version 2.0</title> 
    43<meta http-equiv="Content-Type" content="text/html"> 
    54<meta name=description content="Sensors FAQ for lm_sensors version 2.0"> 
    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.0</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> 
     
    154133<li><a href="#Section%204.31">4.31.4 Tyan 2688</a> 
    155134</ul> 
    156 </ul> 
    157 <li><a name="toc_Help"></a> 
    158     <a href="#Help">5 How to Ask for Help</a> 
     135<li><a href="#Section%204.32">4.32 Problems on particular systems</a> 
     136</ul> 
     137<li><a href="#Help">5 How to Ask for Help</a> 
    159138<ul> 
    160139<li><a href="#Section%205.1">5.1 What to send us when asking for help</a> 
     
    167146<li><a href="#Section%205.8">5.8 How do I follow up on a ticket?</a> 
    168147</ul> 
    169 <li><a name="toc_Contribute"></a> 
    170     <a href="#Contribute">6 How to Contribute</a> 
     148<li><a href="#Contribute">6 How to Contribute</a> 
    171149<ul> 
    172150<li><a href="#Section%206.1">6.1 How to write a driver</a> 
     
    179157<li><a href="#Section%206.8">6.8 How to block spam on the project mailing list</a> 
    180158</ul> 
    181 <li><a name="toc_Version%201%20Specifics"></a> 
    182     <a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
     159<li><a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
    183160<ul> 
    184161<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> 
     
    187164<li><a href="#Section%207.4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a> 
    188165</ul> 
    189 <li><a name="toc_Document%20Revisions"></a> 
    190     <a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
     166<li><a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
    191167</ul> 
    192168 
    193169<p><hr> 
    194170Node:<a name="Top">Top</a>, 
    195 Next:<a rel=next accesskey=n href="#Overview">Overview</a>, 
    196 Up:<a rel=up accesskey=u href="#dir">(dir)</a> 
    197 <br> 
    198  
    199 <h2>lm_sensors</h2> 
     171Next:<a rel=next href="#Overview">Overview</a>, 
     172Up:<a rel=up href="#(dir)">(dir)</a> 
     173<br> 
     174 
     175<h1>lm_sensors</h1> 
    200176 
    201177<p>The lm_sensors package includes a collection of modules for general SMBus 
     
    204180 
    205181<ul> 
    206 <li><a accesskey=1 href="#Overview">Overview</a>:                 PC and Sensor Overview 
    207 <li><a accesskey=2 href="#Basics">Basics</a>:                   Sensor and Bus Basics 
    208 <li><a accesskey=3 href="#Installation">Installation</a>:             Installation and Management 
    209 <li><a accesskey=4 href="#Problems">Problems</a>:                 Problems 
    210 <li><a accesskey=5 href="#Help">Help</a>:                     How to Ask for Help 
    211 <li><a accesskey=6 href="#Contribute">Contribute</a>:               How to Contribute 
    212 <li><a accesskey=7 href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
    213 <li><a accesskey=8 href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
     182<li><a href="#Overview">Overview</a>:                 PC and Sensor Overview 
     183<li><a href="#Basics">Basics</a>:                   Sensor and Bus Basics 
     184<li><a href="#Installation">Installation</a>:             Installation and Management 
     185<li><a href="#Problems">Problems</a>:                 Problems 
     186<li><a href="#Help">Help</a>:                     How to Ask for Help 
     187<li><a href="#Contribute">Contribute</a>:               How to Contribute 
     188<li><a href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
     189<li><a href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
    214190</ul> 
    215191 
    216192<p><hr> 
    217193Node:<a name="Overview">Overview</a>, 
    218 Next:<a rel=next accesskey=n href="#Basics">Basics</a>, 
    219 Previous:<a rel=previous accesskey=p href="#Top">Top</a>, 
    220 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    221 <br> 
    222  
    223 <h2>1 PC and Sensor Overview</h2> 
    224  
    225 <ul> 
    226 <li><a accesskey=1 href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
    227 <li><a accesskey=2 href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
    228 <li><a accesskey=3 href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
     194Next:<a rel=next href="#Basics">Basics</a>, 
     195Previous:<a rel=previous href="#Top">Top</a>, 
     196Up:<a rel=up href="#Top">Top</a> 
     197<br> 
     198 
     199<h1>1 PC and Sensor Overview</h1> 
     200 
     201<ul> 
     202<li><a href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
     203<li><a href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
     204<li><a href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
    229205</ul> 
    230206 
    231207<p><hr> 
    232208Node:<a name="Section%201.1">Section 1.1</a>, 
    233 Next:<a rel=next accesskey=n href="#Section%201.2">Section 1.2</a>, 
    234 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    235 <br> 
    236  
    237 <h3>1.1 What sensors are available on my PC?</h3> 
     209Next:<a rel=next href="#Section%201.2">Section 1.2</a>, 
     210Up:<a rel=up href="#Overview">Overview</a> 
     211<br> 
     212 
     213<h2>1.1 What sensors are available on my PC?</h2> 
    238214 
    239215<p>Most PC's built since late 1997 now come with a 
     
    250226<p><hr> 
    251227Node:<a name="Section%201.2">Section 1.2</a>, 
    252 Next:<a rel=next accesskey=n href="#Section%201.3">Section 1.3</a>, 
    253 Previous:<a rel=previous accesskey=p href="#Section%201.1">Section 1.1</a>, 
    254 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    255 <br> 
    256  
    257 <h3>1.2 What can a sensor chip like the "LM78" do?</h3> 
     228Next:<a rel=next href="#Section%201.3">Section 1.3</a>, 
     229Previous:<a rel=previous href="#Section%201.1">Section 1.1</a>, 
     230Up:<a rel=up href="#Overview">Overview</a> 
     231<br> 
     232 
     233<h2>1.2 What can a sensor chip like the "LM78" do?</h2> 
    258234 
    259235<p>The LM78 is a chip made by National Semiconductor which can monitor 7 
     
    278254<p><hr> 
    279255Node:<a name="Section%201.3">Section 1.3</a>, 
    280 Previous:<a rel=previous accesskey=p href="#Section%201.2">Section 1.2</a>, 
    281 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    282 <br> 
    283  
    284 <h3>1.3 Where do I find out more about any of these chips?</h3> 
     256Previous:<a rel=previous href="#Section%201.2">Section 1.2</a>, 
     257Up:<a rel=up href="#Overview">Overview</a> 
     258<br> 
     259 
     260<h2>1.3 Where do I find out more about any of these chips?</h2> 
    285261 
    286262<p>Most semiconductor companies have comprehensive documentation, 
     
    301277<p><hr> 
    302278Node:<a name="Basics">Basics</a>, 
    303 Next:<a rel=next accesskey=n href="#Installation">Installation</a>, 
    304 Previous:<a rel=previous accesskey=p href="#Overview">Overview</a>, 
    305 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    306 <br> 
    307  
    308 <h2>2 Sensor and Bus Basics</h2> 
    309  
    310 <ul> 
    311 <li><a accesskey=1 href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
    312 <li><a accesskey=2 href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
    313 <li><a accesskey=3 href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
    314 <li><a accesskey=4 href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
    315 <li><a accesskey=5 href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
    316 <li><a accesskey=6 href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
     279Next:<a rel=next href="#Installation">Installation</a>, 
     280Previous:<a rel=previous href="#Overview">Overview</a>, 
     281Up:<a rel=up href="#Top">Top</a> 
     282<br> 
     283 
     284<h1>2 Sensor and Bus Basics</h1> 
     285 
     286<ul> 
     287<li><a href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
     288<li><a href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
     289<li><a href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
     290<li><a href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
     291<li><a href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
     292<li><a href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
    317293</ul> 
    318294 
    319295<p><hr> 
    320296Node:<a name="Section%202.1">Section 2.1</a>, 
    321 Next:<a rel=next accesskey=n href="#Section%202.2">Section 2.2</a>, 
    322 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    323 <br> 
    324  
    325 <h3>2.1 How are these sensors read?</h3> 
     297Next:<a rel=next href="#Section%202.2">Section 2.2</a>, 
     298Up:<a rel=up href="#Basics">Basics</a> 
     299<br> 
     300 
     301<h2>2.1 How are these sensors read?</h2> 
    326302 
    327303<p>Sensor chips reside on either the ISA bus, the SMBus, or both.  
     
    336312<p><hr> 
    337313Node:<a name="Section%202.2">Section 2.2</a>, 
    338 Next:<a rel=next accesskey=n href="#Section%202.3">Section 2.3</a>, 
    339 Previous:<a rel=previous accesskey=p href="#Section%202.1">Section 2.1</a>, 
    340 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    341 <br> 
    342  
    343 <h3>2.2 What is the SMBus? And the I2C bus?</h3> 
     314Next:<a rel=next href="#Section%202.3">Section 2.3</a>, 
     315Previous:<a rel=previous href="#Section%202.1">Section 2.1</a>, 
     316Up:<a rel=up href="#Basics">Basics</a> 
     317<br> 
     318 
     319<h2>2.2 What is the SMBus? And the I2C bus?</h2> 
    344320 
    345321<p>The SMBus is the "System Management Bus".  More specifically, it is a 
     
    363339<p><hr> 
    364340Node:<a name="Section%202.3">Section 2.3</a>, 
    365 Next:<a rel=next accesskey=n href="#Section%202.4">Section 2.4</a>, 
    366 Previous:<a rel=previous accesskey=p href="#Section%202.2">Section 2.2</a>, 
    367 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    368 <br> 
    369  
    370 <h3>2.3 I don't have an ISA bus!</h3> 
     341Next:<a rel=next href="#Section%202.4">Section 2.4</a>, 
     342Previous:<a rel=previous href="#Section%202.2">Section 2.2</a>, 
     343Up:<a rel=up href="#Basics">Basics</a> 
     344<br> 
     345 
     346<h2>2.3 I don't have an ISA bus!</h2> 
    371347 
    372348<p>We promise, you do, even if you don't have any old ISA slots.  
     
    381357<p><hr> 
    382358Node:<a name="Section%202.4">Section 2.4</a>, 
    383 Next:<a rel=next accesskey=n href="#Section%202.5">Section 2.5</a>, 
    384 Previous:<a rel=previous accesskey=p href="#Section%202.3">Section 2.3</a>, 
    385 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    386 <br> 
    387  
    388 <h3>2.4 What sensors do processors have?</h3> 
     359Next:<a rel=next href="#Section%202.5">Section 2.5</a>, 
     360Previous:<a rel=previous href="#Section%202.3">Section 2.3</a>, 
     361Up:<a rel=up href="#Basics">Basics</a> 
     362<br> 
     363 
     364<h2>2.4 What sensors do processors have?</h2> 
    389365 
    390366<p>Most new processors contain a thermal diode on the die itself.  
     
    422398<p><hr> 
    423399Node:<a name="Section%202.5">Section 2.5</a>, 
    424 Next:<a rel=next accesskey=n href="#Section%202.6">Section 2.6</a>, 
    425 Previous:<a rel=previous accesskey=p href="#Section%202.4">Section 2.4</a>, 
    426 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    427 <br> 
    428  
    429 <h3>2.5 How often are the sensor values updated?</h3> 
     400Next:<a rel=next href="#Section%202.6">Section 2.6</a>, 
     401Previous:<a rel=previous href="#Section%202.4">Section 2.4</a>, 
     402Up:<a rel=up href="#Basics">Basics</a> 
     403<br> 
     404 
     405<h2>2.5 How often are the sensor values updated?</h2> 
    430406 
    431407<p>The LM78, and most other sensor chips like it, reads its sensors one 
     
    439415<p><hr> 
    440416Node:<a name="Section%202.6">Section 2.6</a>, 
    441 Previous:<a rel=previous accesskey=p href="#Section%202.5">Section 2.5</a>, 
    442 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    443 <br> 
    444  
    445 <h3>2.6 How are alarms triggered?</h3> 
     417Previous:<a rel=previous href="#Section%202.5">Section 2.5</a>, 
     418Up:<a rel=up href="#Basics">Basics</a> 
     419<br> 
     420 
     421<h2>2.6 How are alarms triggered?</h2> 
    446422 
    447423<p>It is possible to monitor each sensor and have an alarm go off if 
     
    464440<p><hr> 
    465441Node:<a name="Installation">Installation</a>, 
    466 Next:<a rel=next accesskey=n href="#Problems">Problems</a>, 
    467 Previous:<a rel=previous accesskey=p href="#Basics">Basics</a>, 
    468 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    469 <br> 
    470  
    471 <h2>3 Installation and Management</h2> 
    472  
    473 <ul> 
    474 <li><a accesskey=1 href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
    475 <li><a accesskey=2 href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
    476 <li><a accesskey=3 href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
    477 <li><a accesskey=4 href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
    478 <li><a accesskey=5 href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
    479 <li><a accesskey=6 href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
    480 <li><a accesskey=7 href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
    481 <li><a accesskey=8 href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
    482 <li><a accesskey=9 href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
     442Next:<a rel=next href="#Problems">Problems</a>, 
     443Previous:<a rel=previous href="#Basics">Basics</a>, 
     444Up:<a rel=up href="#Top">Top</a> 
     445<br> 
     446 
     447<h1>3 Installation and Management</h1> 
     448 
     449<ul> 
     450<li><a href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
     451<li><a href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
     452<li><a href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
     453<li><a href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
     454<li><a href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
     455<li><a href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
     456<li><a href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
     457<li><a href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
     458<li><a href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
    483459<li><a href="#Section%203.10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
    484460</ul> 
     
    486462<p><hr> 
    487463Node:<a name="Section%203.1">Section 3.1</a>, 
    488 Next:<a rel=next accesskey=n href="#Section%203.2">Section 3.2</a>, 
    489 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    490 <br> 
    491  
    492 <h3>3.1 Why so many modules, and how do I cope with them?</h3> 
     464Next:<a rel=next href="#Section%203.2">Section 3.2</a>, 
     465Up:<a rel=up href="#Installation">Installation</a> 
     466<br> 
     467 
     468<h2>3.1 Why so many modules, and how do I cope with them?</h2> 
    493469 
    494470<p>We tried to make this package as modular as possible. This makes it 
     
    507483<p><hr> 
    508484Node:<a name="Section%203.2">Section 3.2</a>, 
    509 Next:<a rel=next accesskey=n href="#Section%203.3">Section 3.3</a>, 
    510 Previous:<a rel=previous accesskey=p href="#Section%203.1">Section 3.1</a>, 
    511 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    512 <br> 
    513  
    514 <h3>3.2 How do I know which chips I own?</h3> 
     485Next:<a rel=next href="#Section%203.3">Section 3.3</a>, 
     486Previous:<a rel=previous href="#Section%203.1">Section 3.1</a>, 
     487Up:<a rel=up href="#Installation">Installation</a> 
     488<br> 
     489 
     490<h2>3.2 How do I know which chips I own?</h2> 
    515491 
    516492<p>We have an excellent program that scans all your hardware.  
     
    528504<p><a name="Section%203.2.1"></a> 
    529505 
    530 <h4>3.2.1 What chips are on motherboard XYZ?</h4> 
     506<h3>3.2.1 What chips are on motherboard XYZ?</h3> 
    531507 
    532508<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong> 
     
    548524<p><a name="Section%203.2.2"></a> 
    549525 
    550 <h4>3.2.2 Do you support motherboard XYZ?</h4> 
     526<h3>3.2.2 Do you support motherboard XYZ?</h3> 
    551527 
    552528<p>We don't support boards, we support chips. See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
     
    554530<p><a name="Section%203.2.3"></a> 
    555531 
    556 <h4>3.2.3 Do you support chip XYZ?</h4> 
     532<h3>3.2.3 Do you support chip XYZ?</h3> 
    557533 
    558534<p>This we have good answers for. 
     
    566542<p><a name="Section%203.2.4"></a> 
    567543 
    568 <h4>3.2.4 Anybody working on a driver for chip XYZ?</h4> 
     544<h3>3.2.4 Anybody working on a driver for chip XYZ?</h3> 
    569545 
    570546<p>Newest Driver Status: <a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html</a> 
     
    572548<p><hr> 
    573549Node:<a name="Section%203.3">Section 3.3</a>, 
    574 Next:<a rel=next accesskey=n href="#Section%203.4">Section 3.4</a>, 
    575 Previous:<a rel=previous accesskey=p href="#Section%203.2">Section 3.2</a>, 
    576 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    577 <br> 
    578  
    579 <h3>3.3 Which modules should I insert?</h3> 
     550Next:<a rel=next href="#Section%203.4">Section 3.4</a>, 
     551Previous:<a rel=previous href="#Section%203.2">Section 3.2</a>, 
     552Up:<a rel=up href="#Installation">Installation</a> 
     553<br> 
     554 
     555<h2>3.3 Which modules should I insert?</h2> 
    580556 
    581557<p><code>sensors-detect</code> will tell you. Take the <code>modprobe</code> lines it 
     
    598574<p><hr> 
    599575Node:<a name="Section%203.4">Section 3.4</a>, 
    600 Next:<a rel=next accesskey=n href="#Section%203.5">Section 3.5</a>, 
    601 Previous:<a rel=previous accesskey=p href="#Section%203.3">Section 3.3</a>, 
    602 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    603 <br> 
    604  
    605 <h3>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h3> 
     576Next:<a rel=next href="#Section%203.5">Section 3.5</a>, 
     577Previous:<a rel=previous href="#Section%203.3">Section 3.3</a>, 
     578Up:<a rel=up href="#Installation">Installation</a> 
     579<br> 
     580 
     581<h2>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h2> 
    606582 
    607583<p>Yes, for any applications that use <code>libsensors,</code> including the 
     
    615591<p><a name="Section%203.4.1"></a> 
    616592 
    617 <h4>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h4> 
     593<h3>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h3> 
    618594 
    619595<p>Every motherboard is different. You can customize the labels 
     
    624600<p><a name="Section%203.4.2"></a> 
    625601 
    626 <h4>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h4> 
     602<h3>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h3> 
    627603 
    628604<p>You can customize them in the file <code>/etc/sensors.conf</code>. See above. 
     
    630606<p><a name="Section%203.4.3"></a> 
    631607 
    632 <h4>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h4> 
     608<h3>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h3> 
    633609 
    634610<p>You forgot to run <code>sensors -s</code>. See above. 
     
    636612<p><a name="Section%203.4.4"></a> 
    637613 
    638 <h4>3.4.4 One sensor isn't hooked up on my board!</h4> 
     614<h3>3.4.4 One sensor isn't hooked up on my board!</h3> 
    639615 
    640616<p>Use an <code>ignore</code> line in <code>/etc/sensors.conf</code> so it isn't 
     
    643619<p><a name="Section%203.4.5"></a> 
    644620 
    645 <h4>3.4.5 I need help with <code>sensors.conf</code>!</h4> 
     621<h3>3.4.5 I need help with <code>sensors.conf</code>!</h3> 
    646622 
    647623<p>There is detailed help at the top of that file. 
     
    649625<p><a name="Section%203.4.6"></a> 
    650626 
    651 <h4>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h4> 
     627<h3>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h3> 
    652628 
    653629<p>No. Good idea though. If you would like to set one up on your website 
     
    656632<p><hr> 
    657633Node:<a name="Section%203.5">Section 3.5</a>, 
    658 Next:<a rel=next accesskey=n href="#Section%203.6">Section 3.6</a>, 
    659 Previous:<a rel=previous accesskey=p href="#Section%203.4">Section 3.4</a>, 
    660 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    661 <br> 
    662  
    663 <h3>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h3> 
     634Next:<a rel=next href="#Section%203.6">Section 3.6</a>, 
     635Previous:<a rel=previous href="#Section%203.4">Section 3.4</a>, 
     636Up:<a rel=up href="#Installation">Installation</a> 
     637<br> 
     638 
     639<h2>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h2> 
    664640 
    665641<p>Don't worry about them. The dependency files (which tell which 
     
    671647<p><hr> 
    672648Node:<a name="Section%203.6">Section 3.6</a>, 
    673 Next:<a rel=next accesskey=n href="#Section%203.7">Section 3.7</a>, 
    674 Previous:<a rel=previous accesskey=p href="#Section%203.5">Section 3.5</a>, 
    675 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    676 <br> 
    677  
    678 <h3>3.6 I get all kinds of weird compilation errors?</h3> 
     649Next:<a rel=next href="#Section%203.7">Section 3.7</a>, 
     650Previous:<a rel=previous href="#Section%203.5">Section 3.5</a>, 
     651Up:<a rel=up href="#Installation">Installation</a> 
     652<br> 
     653 
     654<h2>3.6 I get all kinds of weird compilation errors?</h2> 
    679655 
    680656<p>Check that the correct i2c header files are used. Depending on 
     
    684660<p><a name="Section%203.6.1"></a> 
    685661 
    686 <h4>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h4> 
     662<h3>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h3> 
    687663 
    688664<ul> 
     
    695671<p><hr> 
    696672Node:<a name="Section%203.7">Section 3.7</a>, 
    697 Next:<a rel=next accesskey=n href="#Section%203.8">Section 3.8</a>, 
    698 Previous:<a rel=previous accesskey=p href="#Section%203.6">Section 3.6</a>, 
    699 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    700 <br> 
    701  
    702 <h3>3.7 It still does not compile or patch!</h3> 
     673Next:<a rel=next href="#Section%203.8">Section 3.8</a>, 
     674Previous:<a rel=previous href="#Section%203.6">Section 3.6</a>, 
     675Up:<a rel=up href="#Installation">Installation</a> 
     676<br> 
     677 
     678<h2>3.7 It still does not compile or patch!</h2> 
    703679 
    704680<p>Have you installed the matching version of the i2c package? Remember, 
     
    711687<p><hr> 
    712688Node:<a name="Section%203.8">Section 3.8</a>, 
    713 Next:<a rel=next accesskey=n href="#Section%203.9">Section 3.9</a>, 
    714 Previous:<a rel=previous accesskey=p href="#Section%203.7">Section 3.7</a>, 
    715 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    716 <br> 
    717  
    718 <h3>3.8 <code>make install</code> fails on Mandrake kernels</h3> 
     689Next:<a rel=next href="#Section%203.9">Section 3.9</a>, 
     690Previous:<a rel=previous href="#Section%203.7">Section 3.7</a>, 
     691Up:<a rel=up href="#Installation">Installation</a> 
     692<br> 
     693 
     694<h2>3.8 <code>make install</code> fails on Mandrake kernels</h2> 
    719695 
    720696<p>Mandrake uses a non-standard <code>version.h</code> file which confuses our <code>Makefile</code>.  
     
    723699<p><hr> 
    724700Node:<a name="Section%203.9">Section 3.9</a>, 
    725 Next:<a rel=next accesskey=n href="#Section%203.10">Section 3.10</a>, 
    726 Previous:<a rel=previous accesskey=p href="#Section%203.8">Section 3.8</a>, 
    727 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    728 <br> 
    729  
    730 <h3>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h3> 
     701Next:<a rel=next href="#Section%203.10">Section 3.10</a>, 
     702Previous:<a rel=previous href="#Section%203.8">Section 3.8</a>, 
     703Up:<a rel=up href="#Installation">Installation</a> 
     704<br> 
     705 
     706<h2>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h2> 
    731707 
    732708<p>Example: 
    733 <br><pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
     709<pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
    734710i2c_bit_add_bus_R8c3bc60e 
    735711i2c_bit_del_bus_R92b18f49 
     
    761737<p><hr> 
    762738Node:<a name="Section%203.10">Section 3.10</a>, 
    763 Previous:<a rel=previous accesskey=p href="#Section%203.9">Section 3.9</a>, 
    764 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    765 <br> 
    766  
    767 <h3>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3> 
     739Previous:<a rel=previous href="#Section%203.9">Section 3.9</a>, 
     740Up:<a rel=up href="#Installation">Installation</a> 
     741<br> 
     742 
     743<h2>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h2> 
    768744 
    769745<p>In some versions of Redhat, an RPM is included to provide i2c support.  
     
    782758old i2c stuff anymore anyway.  Just don't use it with abandon.  
    783759<li>Try (in the build directory of <code>lm_sensors)</code> 
    784 <br><pre><code>make clean</code> 
     760<pre><code>make clean</code> 
    785761<code>make</code> 
    786762</pre> 
     
    793769<p><hr> 
    794770Node:<a name="Problems">Problems</a>, 
    795 Next:<a rel=next accesskey=n href="#Help">Help</a>, 
    796 Previous:<a rel=previous accesskey=p href="#Installation">Installation</a>, 
    797 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    798 <br> 
    799  
    800 <h2>4 Problems</h2> 
    801  
    802 <ul> 
    803 <li><a accesskey=1 href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
    804 <li><a accesskey=2 href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
    805 <li><a accesskey=3 href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
    806 <li><a accesskey=4 href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
    807 <li><a accesskey=5 href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
    808 <li><a accesskey=6 href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
    809 <li><a accesskey=7 href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
    810 <li><a accesskey=8 href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
    811 <li><a accesskey=9 href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
     771Next:<a rel=next href="#Help">Help</a>, 
     772Previous:<a rel=previous href="#Installation">Installation</a>, 
     773Up:<a rel=up href="#Top">Top</a> 
     774<br> 
     775 
     776<h1>4 Problems</h1> 
     777 
     778<ul> 
     779<li><a href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
     780<li><a href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
     781<li><a href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
     782<li><a href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
     783<li><a href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
     784<li><a href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
     785<li><a href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
     786<li><a href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
     787<li><a href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
    812788<li><a href="#Section%204.10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?  
    813789<li><a href="#Section%204.11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?  
     
    832808<li><a href="#Section%204.30">Section 4.30</a>:         Inserting modules slows down my board 
    833809<li><a href="#Section%204.31">Section 4.31</a>:         Problems on particular motherboards 
     810<li><a href="#Section%204.32">Section 4.32</a>:         Problems on particular systems 
    834811</ul> 
    835812 
    836813<p><hr> 
    837814Node:<a name="Section%204.1">Section 4.1</a>, 
    838 Next:<a rel=next accesskey=n href="#Section%204.2">Section 4.2</a>, 
    839 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    840 <br> 
    841  
    842 <h3>4.1 My fans report exactly half/double their values compared to the BIOS?</h3> 
     815Next:<a rel=next href="#Section%204.2">Section 4.2</a>, 
     816Up:<a rel=up href="#Problems">Problems</a> 
     817<br> 
     818 
     819<h2>4.1 My fans report exactly half/double their values compared to the BIOS?</h2> 
    843820 
    844821<p>The problem with much of the sensor data is that it is impossible to 
     
    848825configuration file <code>/etc/sensors.conf</code>: 
    849826 
    850 <br><pre>chip lm78-*             # Or whatever chip this relates to 
     827<pre>chip lm78-*             # Or whatever chip this relates to 
    851828compute fan1 2*@,@/2    # This will double the fan1 reading 
    852829                        # -- or -- 
     
    858835<p><a name="Fans%20sometimes%2falways%20read%200!"></a> 
    859836 
    860 <h4>4.1.1 Fans sometimes/always read 0!!</h4> 
     837<h3>4.1.1 Fans sometimes/always read 0!!</h3> 
    861838 
    862839<p>You may not have a three-wire fan, which is required. 
     
    867844<p><a name="I%20doubled%20the%20fan%20divisor%20and%20the%20fan%20still%20reads%207000"></a> 
    868845 
    869 <h4>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4> 
     846<h3>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h3> 
    870847 
    871848<p>Believe it or not, doubling the 'fan divisor' will not halve 
     
    876853<p><hr> 
    877854Node:<a name="Section%204.2">Section 4.2</a>, 
    878 Next:<a rel=next accesskey=n href="#Section%204.3">Section 4.3</a>, 
    879 Previous:<a rel=previous accesskey=p href="#Section%204.1">Section 4.1</a>, 
    880 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    881 <br> 
    882  
    883 <h3>4.2 Why do my two LM75's report "-48 degrees"?</h3> 
     855Next:<a rel=next href="#Section%204.3">Section 4.3</a>, 
     856Previous:<a rel=previous href="#Section%204.1">Section 4.1</a>, 
     857Up:<a rel=up href="#Problems">Problems</a> 
     858<br> 
     859 
     860<h2>4.2 Why do my two LM75's report "-48 degrees"?</h2> 
    884861 
    885862<p>For starters, those aren't LM75's.  Your mainboard actually has the 
     
    896873<p><hr> 
    897874Node:<a name="Section%204.3">Section 4.3</a>, 
    898 Next:<a rel=next accesskey=n href="#Section%204.4">Section 4.4</a>, 
    899 Previous:<a rel=previous accesskey=p href="#Section%204.2">Section 4.2</a>, 
    900 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    901 <br> 
    902  
    903 <h3>4.3 Why do I have two Vcore readings, I have only one processor!</h3> 
     875Next:<a rel=next href="#Section%204.4">Section 4.4</a>, 
     876Previous:<a rel=previous href="#Section%204.2">Section 4.2</a>, 
     877Up:<a rel=up href="#Problems">Problems</a> 
     878<br> 
     879 
     880<h2>4.3 Why do I have two Vcore readings, I have only one processor!</h2> 
    904881 
    905882<p>The LM78 has seven voltage sensors. The default way of 
     
    918895<p><hr> 
    919896Node:<a name="Section%204.4">Section 4.4</a>, 
    920 Next:<a rel=next accesskey=n href="#Section%204.5">Section 4.5</a>, 
    921 Previous:<a rel=previous accesskey=p href="#Section%204.3">Section 4.3</a>, 
    922 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    923 <br> 
    924  
    925 <h3>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3> 
     897Next:<a rel=next href="#Section%204.5">Section 4.5</a>, 
     898Previous:<a rel=previous href="#Section%204.3">Section 4.3</a>, 
     899Up:<a rel=up href="#Problems">Problems</a> 
     900<br> 
     901 
     902<h2>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h2> 
    926903 
    927904<p>The ALARM indications in <code>sensors</code> are those reported by the 
     
    947924<p><hr> 
    948925Node:<a name="Section%204.5">Section 4.5</a>, 
    949 Next:<a rel=next accesskey=n href="#Section%204.6">Section 4.6</a>, 
    950 Previous:<a rel=previous accesskey=p href="#Section%204.4">Section 4.4</a>, 
    951 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    952 <br> 
    953  
    954 <h3>4.5 My voltage readings seem to drift a bit. Is something wrong?</h3> 
     926Next:<a rel=next href="#Section%204.6">Section 4.6</a>, 
     927Previous:<a rel=previous href="#Section%204.4">Section 4.4</a>, 
     928Up:<a rel=up href="#Problems">Problems</a> 
     929<br> 
     930 
     931<h2>4.5 My voltage readings seem to drift a bit. Is something wrong?</h2> 
    955932 
    956933<p>No, probably not. If your motherboard heats up a bit, the sensed 
     
    965942<p><hr> 
    966943Node:<a name="Section%204.6">Section 4.6</a>, 
    967 Next:<a rel=next accesskey=n href="#Section%204.7">Section 4.7</a>, 
    968 Previous:<a rel=previous accesskey=p href="#Section%204.5">Section 4.5</a>, 
    969 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    970 <br> 
    971  
    972 <h3>4.6 Some measurements are way out of range. What happened?</h3> 
     944Next:<a rel=next href="#Section%204.7">Section 4.7</a>, 
     945Previous:<a rel=previous href="#Section%204.5">Section 4.5</a>, 
     946Up:<a rel=up href="#Problems">Problems</a> 
     947<br> 
     948 
     949<h2>4.6 Some measurements are way out of range. What happened?</h2> 
    973950 
    974951<p>Each module tries to set limits to sensible values on initialization, 
     
    986963<p><hr> 
    987964Node:<a name="Section%204.7">Section 4.7</a>, 
    988 Next:<a rel=next accesskey=n href="#Section%204.8">Section 4.8</a>, 
    989 Previous:<a rel=previous accesskey=p href="#Section%204.6">Section 4.6</a>, 
    990 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    991 <br> 
    992  
    993 <h3>4.7 What are VID lines? Why is the VID reading wrong?</h3> 
     965Next:<a rel=next href="#Section%204.8">Section 4.8</a>, 
     966Previous:<a rel=previous href="#Section%204.6">Section 4.6</a>, 
     967Up:<a rel=up href="#Problems">Problems</a> 
     968<br> 
     969 
     970<h2>4.7 What are VID lines? Why is the VID reading wrong?</h2> 
    994971 
    995972<p>These describe the core voltage for your processor. They are 
     
    1003980<p><hr> 
    1004981Node:<a name="Section%204.8">Section 4.8</a>, 
    1005 Next:<a rel=next accesskey=n href="#Section%204.9">Section 4.9</a>, 
    1006 Previous:<a rel=previous accesskey=p href="#Section%204.7">Section 4.7</a>, 
    1007 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1008 <br> 
    1009  
    1010 <h3>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3> 
     982Next:<a rel=next href="#Section%204.9">Section 4.9</a>, 
     983Previous:<a rel=previous href="#Section%204.7">Section 4.7</a>, 
     984Up:<a rel=up href="#Problems">Problems</a> 
     985<br> 
     986 
     987<h2>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h2> 
    1011988 
    1012989<p>If we would read the registers more often, it would not find the 
     
    1017994<p><hr> 
    1018995Node:<a name="Section%204.9">Section 4.9</a>, 
    1019 Next:<a rel=next accesskey=n href="#Section%204.10">Section 4.10</a>, 
    1020 Previous:<a rel=previous accesskey=p href="#Section%204.8">Section 4.8</a>, 
    1021 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1022 <br> 
    1023  
    1024 <h3>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3> 
     996Next:<a rel=next href="#Section%204.10">Section 4.10</a>, 
     997Previous:<a rel=previous href="#Section%204.8">Section 4.8</a>, 
     998Up:<a rel=up href="#Problems">Problems</a> 
     999<br> 
     1000 
     1001<h2>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h2> 
    10251002 
    10261003<p>ISA bus access is fast, but SMBus access is really slow. If you have 
     
    10311008<p><hr> 
    10321009Node:<a name="Section%204.10">Section 4.10</a>, 
    1033 Next:<a rel=next accesskey=n href="#Section%204.11">Section 4.11</a>, 
    1034 Previous:<a rel=previous accesskey=p href="#Section%204.9">Section 4.9</a>, 
    1035 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1036 <br> 
    1037  
    1038 <h3>4.10 Can I be alerted when an ALARM occurs?</h3> 
     1010Next:<a rel=next href="#Section%204.11">Section 4.11</a>, 
     1011Previous:<a rel=previous href="#Section%204.9">Section 4.9</a>, 
     1012Up:<a rel=up href="#Problems">Problems</a> 
     1013<br> 
     1014 
     1015<h2>4.10 Can I be alerted when an ALARM occurs?</h2> 
    10391016 
    10401017<p>No, you can't; and it may well be never supported. 
     
    10571034<p><hr> 
    10581035Node:<a name="Section%204.11">Section 4.11</a>, 
    1059 Next:<a rel=next accesskey=n href="#Section%204.12">Section 4.12</a>, 
    1060 Previous:<a rel=previous accesskey=p href="#Section%204.10">Section 4.10</a>, 
    1061 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1062 <br> 
    1063  
    1064 <h3>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3> 
     1036Next:<a rel=next href="#Section%204.12">Section 4.12</a>, 
     1037Previous:<a rel=previous href="#Section%204.10">Section 4.10</a>, 
     1038Up:<a rel=up href="#Problems">Problems</a> 
     1039<br> 
     1040 
     1041<h2>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h2> 
    10651042 
    10661043<p>Some chips which mainboard makers connect to the SMBus are not SMBus 
     
    10761053<p><hr> 
    10771054Node:<a name="Section%204.12">Section 4.12</a>, 
    1078 Next:<a rel=next accesskey=n href="#Section%204.13">Section 4.13</a>, 
    1079 Previous:<a rel=previous accesskey=p href="#Section%204.11">Section 4.11</a>, 
    1080 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1081 <br> 
    1082  
    1083 <h3>4.12 My BIOS reports a much higher CPU temperature than your modules!</h3> 
     1055Next:<a rel=next href="#Section%204.13">Section 4.13</a>, 
     1056Previous:<a rel=previous href="#Section%204.11">Section 4.11</a>, 
     1057Up:<a rel=up href="#Problems">Problems</a> 
     1058<br> 
     1059 
     1060<h2>4.12 My BIOS reports a much higher CPU temperature than your modules!</h2> 
    10841061 
    10851062<p>We display the actual temperature of the sensor. This may not be the 
     
    10911068in the module itself. You can do it through the configuration file, though: 
    10921069 
    1093 <br><pre>chip lm75-*-49                      # Or whatever chip this relates to 
     1070<pre>chip lm75-*-49                      # Or whatever chip this relates to 
    10941071label temp "Processor" 
    10951072compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula 
     
    10981075<p><hr> 
    10991076Node:<a name="Section%204.13">Section 4.13</a>, 
    1100 Next:<a rel=next accesskey=n href="#Section%204.14">Section 4.14</a>, 
    1101 Previous:<a rel=previous accesskey=p href="#Section%204.12">Section 4.12</a>, 
    1102 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1103 <br> 
    1104  
    1105 <h3>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h3> 
     1077Next:<a rel=next href="#Section%204.14">Section 4.14</a>, 
     1078Previous:<a rel=previous href="#Section%204.12">Section 4.12</a>, 
     1079Up:<a rel=up href="#Problems">Problems</a> 
     1080<br> 
     1081 
     1082<h2>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h2> 
    11061083 
    11071084<p>Remember, these values do not take the configuration file 
     
    11121089<p><hr> 
    11131090Node:<a name="Section%204.14">Section 4.14</a>, 
    1114 Next:<a rel=next accesskey=n href="#Section%204.15">Section 4.15</a>, 
    1115 Previous:<a rel=previous accesskey=p href="#Section%204.13">Section 4.13</a>, 
    1116 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1117 <br> 
    1118  
    1119 <h3>4.14 How do I set new limits?</h3> 
     1091Next:<a rel=next href="#Section%204.15">Section 4.15</a>, 
     1092Previous:<a rel=previous href="#Section%204.13">Section 4.13</a>, 
     1093Up:<a rel=up href="#Problems">Problems</a> 
     1094<br> 
     1095 
     1096<h2>4.14 How do I set new limits?</h2> 
    11201097 
    11211098<p>Change the limit values in <code>/etc/sensors.conf</code> and then run 
     
    11241101<p><a name="I%20set%20new%20limits%20and%20it%20didnt%20work"></a> 
    11251102 
    1126 <h4>4.14.1 I set new limits and it didn't work?</h4> 
     1103<h3>4.14.1 I set new limits and it didn't work?</h3> 
    11271104 
    11281105<p>You forgot to run <code>sensors -s</code>. Put it in a <code>/etc/rc.d/...</code> file 
     
    11311108<p><hr> 
    11321109Node:<a name="Section%204.15">Section 4.15</a>, 
    1133 Next:<a rel=next accesskey=n href="#Section%204.16">Section 4.16</a>, 
    1134 Previous:<a rel=previous accesskey=p href="#Section%204.14">Section 4.14</a>, 
    1135 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1136 <br> 
    1137  
    1138 <h3>4.15 Some sensors are doubly detected?</h3> 
     1110Next:<a rel=next href="#Section%204.16">Section 4.16</a>, 
     1111Previous:<a rel=previous href="#Section%204.14">Section 4.14</a>, 
     1112Up:<a rel=up href="#Problems">Problems</a> 
     1113<br> 
     1114 
     1115<h2>4.15 Some sensors are doubly detected?</h2> 
    11391116 
    11401117<p>Yes, this is still a problem. It is partially solved by alias detection 
     
    11501127<p><hr> 
    11511128Node:<a name="Section%204.16">Section 4.16</a>, 
    1152 Next:<a rel=next accesskey=n href="#Section%204.17">Section 4.17</a>, 
    1153 Previous:<a rel=previous accesskey=p href="#Section%204.15">Section 4.15</a>, 
    1154 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1155 <br> 
    1156  
    1157 <h3>4.16 I ran sensors-detect, but now I get very strange readings?!?</h3> 
     1129Next:<a rel=next href="#Section%204.17">Section 4.17</a>, 
     1130Previous:<a rel=previous href="#Section%204.15">Section 4.15</a>, 
     1131Up:<a rel=up href="#Problems">Problems</a> 
     1132<br> 
     1133 
     1134<h2>4.16 I ran sensors-detect, but now I get very strange readings?!?</h2> 
    11581135 
    11591136<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards 
     
    11671144<p><hr> 
    11681145Node:<a name="Section%204.17">Section 4.17</a>, 
    1169 Next:<a rel=next accesskey=n href="#Section%204.18">Section 4.18</a>, 
    1170 Previous:<a rel=previous accesskey=p href="#Section%204.16">Section 4.16</a>, 
    1171 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1172 <br> 
    1173  
    1174 <h3>4.17 Bad readings from particular chips</h3> 
     1146Next:<a rel=next href="#Section%204.18">Section 4.18</a>, 
     1147Previous:<a rel=previous href="#Section%204.16">Section 4.16</a>, 
     1148Up:<a rel=up href="#Problems">Problems</a> 
     1149<br> 
     1150 
     1151<h2>4.17 Bad readings from particular chips</h2> 
    11751152 
    11761153<p>See below for some particularly troublesome chips.  
     
    11791156<p><a name="Bad%20readings%20from%20the%20AS99127F"></a> 
    11801157 
    1181 <h4>4.17.1 Bad readings from the AS99127F!</h4> 
     1158<h3>4.17.1 Bad readings from the AS99127F!</h3> 
    11821159 
    11831160<p>The Asus AS99127F is a modified version of the Winbond W83781D.  
     
    11891166<p><a name="Bad%20readings%20from%20the%20VIA%20686A"></a> 
    11901167 
    1191 <h4>4.17.2 Bad readings from the VIA 686A!</h4> 
     1168<h3>4.17.2 Bad readings from the VIA 686A!</h3> 
    11921169 
    11931170<p>The Via 686A datasheet is incomplete.  
     
    12001177<p><a name="Bad%20readings%20from%20the%20MTP008"></a> 
    12011178 
    1202 <h4>4.17.3 Bad readings from the MTP008!</h4> 
     1179<h3>4.17.3 Bad readings from the MTP008!</h3> 
    12031180 
    12041181<p>The MTP008 has programmable temperature sensor types.  
     
    12101187<p><a name="Bad%20temperature%20readings%20from%20the%20SIS5595"></a> 
    12111188 
    1212 <h4>4.17.4 Bad temperature readings from the SIS5595!</h4> 
     1189<h3>4.17.4 Bad temperature readings from the SIS5595!</h3> 
    12131190 
    12141191<p>This chip can use multiple thermistor types and there are also 
     
    12211198<p><a name="Bad%20readings%20from%20a%20w8378%5b12%5dd"></a> 
    12221199 
    1223 <h4>4.17.5 Bad readings from a w8378[12]d!</h4> 
     1200<h3>4.17.5 Bad readings from a w8378[12]d!</h3> 
    12241201 
    12251202<p>Do you own an ASUS motherboard?  Perhaps your chip is being 
     
    12351212<p><a name="Bus%20hangs%20on%20Ali%201543%20on%20Asus%20P5A%20boards"></a> 
    12361213 
    1237 <h4>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4> 
     1214<h3>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h3> 
    12381215 
    12391216<p>The SMBus tends to hang on this board and it seems to get worse 
     
    12441221<p><a name="Bad%20readings%20from%20LM75"></a> 
    12451222 
    1246 <h4>4.17.7 Bad readings from LM75!</h4> 
     1223<h3>4.17.7 Bad readings from LM75!</h3> 
    12471224 
    12481225<p>The LM75 detection is poor and other hardware is often misdetected 
     
    12511228<p><a name="Bad%20readings%20from%20LM78"></a> 
    12521229 
    1253 <h4>4.17.8 Bad readings from LM78!</h4> 
     1230<h3>4.17.8 Bad readings from LM78!</h3> 
    12541231 
    12551232<p>The LM78 is no longer manufactured by National Semiconductor.  
     
    12591236<p><a name="Bad%20readings%20from%20LM80"></a> 
    12601237 
    1261 <h4>4.17.9 Bad readings from LM80!</h4> 
     1238<h3>4.17.9 Bad readings from LM80!</h3> 
    12621239 
    12631240<p>The LM80 detection is poor and other hardware is often misdetected 
     
    12661243<p><a name="Bad%20readings%20from%20it87"></a> 
    12671244 
    1268 <h4>4.17.10 Bad readings from it87!</h4> 
     1245<h3>4.17.10 Bad readings from it87!</h3> 
    12691246 
    12701247<p>The it87 temperature sesnsors are configured, unfortunately, 
     
    12751252<p><hr> 
    12761253Node:<a name="Section%204.18">Section 4.18</a>, 
    1277 Next:<a rel=next accesskey=n href="#Section%204.19">Section 4.19</a>, 
    1278 Previous:<a rel=previous accesskey=p href="#Section%204.17">Section 4.17</a>, 
    1279 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1280 <br> 
    1281  
    1282 <h3>4.18 How do I configure two chips (LM87) differently?</h3> 
     1254Next:<a rel=next href="#Section%204.19">Section 4.19</a>, 
     1255Previous:<a rel=previous href="#Section%204.17">Section 4.17</a>, 
     1256Up:<a rel=up href="#Problems">Problems</a> 
     1257<br> 
     1258 
     1259<h2>4.18 How do I configure two chips (LM87) differently?</h2> 
    12831260 
    12841261<p>There is a SuperMicro board with two LM87's on it that are 
     
    12871264 
    12881265<p>Make two different sections in <code>/etc/sensors.conf</code> as follows: 
    1289 <br><pre>chip "lm87-i2c-*-2c" 
     1266<pre>chip "lm87-i2c-*-2c" 
    12901267    put configuration for the chip at 0x2c here 
    12911268chip "lm87-i2c-*-2d" 
     
    12981275<p><hr> 
    12991276Node:<a name="Section%204.19">Section 4.19</a>, 
    1300 Next:<a rel=next accesskey=n href="#Section%204.20">Section 4.20</a>, 
    1301 Previous:<a rel=previous accesskey=p href="#Section%204.18">Section 4.18</a>, 
    1302 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1303 <br> 
    1304  
    1305 <h3>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h3> 
     1277Next:<a rel=next href="#Section%204.20">Section 4.20</a>, 
     1278Previous:<a rel=previous href="#Section%204.18">Section 4.18</a>, 
     1279Up:<a rel=up href="#Problems">Problems</a> 
     1280<br> 
     1281 
     1282<h2>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h2> 
    13061283 
    13071284<p>If the problem is a PCI device is not present in <code>lspci</code>, the solution 
     
    13181295<p><a name="Dmesg%20says%20use%20force_addr%3d0xaddr!%20What%20address%20do%20I%20use"></a> 
    13191296 
    1320 <h4>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h4> 
     1297<h3>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h3> 
    13211298 
    13221299<p>If the problem is a PCI device whose base address is not set, 
     
    13301307<p><hr> 
    13311308Node:<a name="Section%204.20">Section 4.20</a>, 
    1332 Next:<a rel=next accesskey=n href="#Section%204.21">Section 4.21</a>, 
    1333 Previous:<a rel=previous accesskey=p href="#Section%204.19">Section 4.19</a>, 
    1334 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1335 <br> 
    1336  
    1337 <h3>4.20 Sensors says <code>Can't access <code>/proc</code> file</code></h3> 
     1309Next:<a rel=next href="#Section%204.21">Section 4.21</a>, 
     1310Previous:<a rel=previous href="#Section%204.19">Section 4.19</a>, 
     1311Up:<a rel=up href="#Problems">Problems</a> 
     1312<br> 
     1313 
     1314<h2>4.20 Sensors says <code>Can't access <code>/proc</code> file</code></h2> 
    13381315 
    13391316<ul> 
     
    13461323<p><hr> 
    13471324Node:<a name="Section%204.21">Section 4.21</a>, 
    1348 Next:<a rel=next accesskey=n href="#Section%204.22">Section 4.22</a>, 
    1349 Previous:<a rel=previous accesskey=p href="#Section%204.20">Section 4.20</a>, 
    1350 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1351 <br> 
    1352  
    1353 <h3>4.21 Sensors says <code>No sensors found!</code></h3> 
     1325Next:<a rel=next href="#Section%204.22">Section 4.22</a>, 
     1326Previous:<a rel=previous href="#Section%204.20">Section 4.20</a>, 
     1327Up:<a rel=up href="#Problems">Problems</a> 
     1328<br> 
     1329 
     1330<h2>4.21 Sensors says <code>No sensors found!</code></h2> 
    13541331 
    13551332<ul> 
     
    13641341<p><hr> 
    13651342Node:<a name="Section%204.22">Section 4.22</a>, 
    1366 Next:<a rel=next accesskey=n href="#Section%204.23">Section 4.23</a>, 
    1367 Previous:<a rel=previous accesskey=p href="#Section%204.21">Section 4.21</a>, 
    1368 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1369 <br> 
    1370  
    1371 <h3>4.22 Sensors output is not correct!</h3> 
     1343Next:<a rel=next href="#Section%204.23">Section 4.23</a>, 
     1344Previous:<a rel=previous href="#Section%204.21">Section 4.21</a>, 
     1345Up:<a rel=up href="#Problems">Problems</a> 
     1346<br> 
     1347 
     1348<h2>4.22 Sensors output is not correct!</h2> 
    13721349 
    13731350<p>What specifically is the trouble? 
     
    13901367<p><hr> 
    13911368Node:<a name="Section%204.23">Section 4.23</a>, 
    1392 Next:<a rel=next accesskey=n href="#Section%204.24">Section 4.24</a>, 
    1393 Previous:<a rel=previous accesskey=p href="#Section%204.22">Section 4.22</a>, 
    1394 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1395 <br> 
    1396  
    1397 <h3>4.23 What is at I2C address XXX?</h3> 
     1369Next:<a rel=next href="#Section%204.24">Section 4.24</a>, 
     1370Previous:<a rel=previous href="#Section%204.22">Section 4.22</a>, 
     1371Up:<a rel=up href="#Problems">Problems</a> 
     1372<br> 
     1373 
     1374<h2>4.23 What is at I2C address XXX?</h2> 
    13981375 
    13991376<p>In general, we don't know. Start by running <code>sensors-detect</code>.  
     
    14031380<p><a name="What%20is%20at%20I2C%20address%200x69"></a> 
    14041381 
    1405 <h4>4.23.1 What is at I2C address 0x69?</h4> 
     1382<h3>4.23.1 What is at I2C address 0x69?</h3> 
    14061383 
    14071384<p>A clock chip. Often, accessing these clock chips in the wrong 
     
    14131390<p><a name="What%20is%20at%20I2C%20addresses%200x50%20-%200x57"></a> 
    14141391 
    1415 <h4>4.23.2 What is at I2C addresses 0x50 - 0x57?</h4> 
     1392<h3>4.23.2 What is at I2C addresses 0x50 - 0x57?</h3> 
    14161393 
    14171394<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to 
     
    14211398<p><a name="What%20is%20at%20I2C%20addresses%200x30%20-%200x37"></a> 
    14221399 
    1423 <h4>4.23.3 What is at I2C addresses 0x30 - 0x37?</h4> 
     1400<h3>4.23.3 What is at I2C addresses 0x30 - 0x37?</h3> 
    14241401 
    14251402<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs 
     
    14311408<p><hr> 
    14321409Node:<a name="Section%204.24">Section 4.24</a>, 
    1433 Next:<a rel=next accesskey=n href="#Section%204.25">Section 4.25</a>, 
    1434 Previous:<a rel=previous accesskey=p href="#Section%204.23">Section 4.23</a>, 
    1435 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1436 <br> 
    1437  
    1438 <h3>4.24 Sensors-detect doesn't work at all</h3> 
     1410Next:<a rel=next href="#Section%204.25">Section 4.25</a>, 
     1411Previous:<a rel=previous href="#Section%204.23">Section 4.23</a>, 
     1412Up:<a rel=up href="#Problems">Problems</a> 
     1413<br> 
     1414 
     1415<h2>4.24 Sensors-detect doesn't work at all</h2> 
    14391416 
    14401417<p>It could be many things. What was the problem? See <a href="#Section%204.31">Problems on particular motherboards</a>. 
     
    14421419<p><a name="Sensors-detect%20says%20%22Couldnt%20open%20%2fproc%2fbus%2fi2c%3f!%3f%22"></a> 
    14431420 
    1444 <h4>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4> 
     1421<h3>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h3> 
    14451422 
    14461423<p>You don't have i2c support in your kernel, or the i2c-core module 
     
    14491426<p><a name="Sensors-detect%20says%20%22Cant%20open%20%2fdev%2fi2c%5b-%2f%5d0%22"></a> 
    14501427 
    1451 <h4>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4> 
     1428<h3>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h3> 
    14521429 
    14531430<p>Your <code>/dev/i2c-0,</code> <code>/dev/i2c0</code>, or <code>/dev/i2c/0</code> files do not exist 
     
    14581435<p><a name="Sensors-detect%20doesnt%20find%20any%20sensors"></a> 
    14591436 
    1460 <h4>4.24.3 Sensors-detect doesn't find any sensors!</h4> 
     1437<h3>4.24.3 Sensors-detect doesn't find any sensors!</h3> 
    14611438 
    14621439<p>Either 
     
    14811458<p><hr> 
    14821459Node:<a name="Section%204.25">Section 4.25</a>, 
    1483 Next:<a rel=next accesskey=n href="#Section%204.26">Section 4.26</a>, 
    1484 Previous:<a rel=previous accesskey=p href="#Section%204.24">Section 4.24</a>, 
    1485 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1486 <br> 
    1487  
    1488 <h3>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h3> 
     1460Next:<a rel=next href="#Section%204.26">Section 4.26</a>, 
     1461Previous:<a rel=previous href="#Section%204.24">Section 4.24</a>, 
     1462Up:<a rel=up href="#Problems">Problems</a> 
     1463<br> 
     1464 
     1465<h2>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h2> 
    14891466 
    14901467<p>These are errors from the libsensors library in 
     
    14951472<p><hr> 
    14961473Node:<a name="Section%204.26">Section 4.26</a>, 
    1497 Next:<a rel=next accesskey=n href="#Section%204.27">Section 4.27</a>, 
    1498 Previous:<a rel=previous accesskey=p href="#Section%204.25">Section 4.25</a>, 
    1499 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1500 <br> 
    1501  
    1502 <h3>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3> 
     1474Next:<a rel=next href="#Section%204.27">Section 4.27</a>, 
     1475Previous:<a rel=previous href="#Section%204.25">Section 4.25</a>, 
     1476Up:<a rel=up href="#Problems">Problems</a> 
     1477<br> 
     1478 
     1479<h2>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h2> 
    15031480 
    15041481<p>If <code>sensors</code> only says this, for example, and doesn't 
    15051482provide any actual data at all: 
    15061483 
    1507 <br><pre>it87-isa-0290 
     1484<pre>it87-isa-0290 
    15081485Adapter: ISA adapter 
    15091486Algorithm: ISA algorithm 
     
    15171494<p><hr> 
    15181495Node:<a name="Section%204.27">Section 4.27</a>, 
    1519 Next:<a rel=next accesskey=n href="#Section%204.28">Section 4.28</a>, 
    1520 Previous:<a rel=previous accesskey=p href="#Section%204.26">Section 4.26</a>, 
    1521 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1522 <br> 
    1523  
    1524 <h3>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h3> 
     1496Next:<a rel=next href="#Section%204.28">Section 4.28</a>, 
     1497Previous:<a rel=previous href="#Section%204.26">Section 4.26</a>, 
     1498Up:<a rel=up href="#Problems">Problems</a> 
     1499<br> 
     1500 
     1501<h2>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h2> 
    15251502 
    15261503<p>You have a <code>libsensors/sensors</code> mismatch. <code>sensors</code> is unable to 
     
    15341511<p><hr> 
    15351512Node:<a name="Section%204.28">Section 4.28</a>, 
    1536 Next:<a rel=next accesskey=n href="#Section%204.29">Section 4.29</a>, 
    1537 Previous:<a rel=previous accesskey=p href="#Section%204.27">Section 4.27</a>, 
    1538 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1539 <br> 
    1540  
    1541 <h3>4.28 Sensors doesn't find any sensors, just eeproms.</h3> 
     1513Next:<a rel=next href="#Section%204.29">Section 4.29</a>, 
     1514Previous:<a rel=previous href="#Section%204.27">Section 4.27</a>, 
     1515Up:<a rel=up href="#Problems">Problems</a> 
     1516<br> 
     1517 
     1518<h2>4.28 Sensors doesn't find any sensors, just eeproms.</h2> 
    15421519 
    15431520<p>See <a href="#Section%204.24">Sensors-detect doesnt work at all</a>, if <code>sensors-detect</code> failed to find any sensors. 
     
    15511528<p><hr> 
    15521529Node:<a name="Section%204.29">Section 4.29</a>, 
    1553 Next:<a rel=next accesskey=n href="#Section%204.30">Section 4.30</a>, 
    1554 Previous:<a rel=previous accesskey=p href="#Section%204.28">Section 4.28</a>, 
    1555 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1556 <br> 
    1557  
    1558 <h3>4.29 Inserting modules hangs my board</h3> 
     1530Next:<a rel=next href="#Section%204.30">Section 4.30</a>, 
     1531Previous:<a rel=previous href="#Section%204.28">Section 4.28</a>, 
     1532Up:<a rel=up href="#Problems">Problems</a> 
     1533<br> 
     1534 
     1535<h2>4.29 Inserting modules hangs my board</h2> 
    15591536 
    15601537<p>There are several possible causes: 
     
    15691546<p><hr> 
    15701547Node:<a name="Section%204.30">Section 4.30</a>, 
    1571 Next:<a rel=next accesskey=n href="#Section%204.31">Section 4.31</a>, 
    1572 Previous:<a rel=previous accesskey=p href="#Section%204.29">Section 4.29</a>, 
    1573 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1574 <br> 
    1575  
    1576 <h3>4.30 Inserting modules slows down my board</h3> 
     1548Next:<a rel=next href="#Section%204.31">Section 4.31</a>, 
     1549Previous:<a rel=previous href="#Section%204.29">Section 4.29</a>, 
     1550Up:<a rel=up href="#Problems">Problems</a> 
     1551<br> 
     1552 
     1553<h2>4.30 Inserting modules slows down my board</h2> 
    15771554 
    15781555<p>Generally this is caused by an overtemperature alarm output from 
     
    15841561<p><hr> 
    15851562Node:<a name="Section%204.31">Section 4.31</a>, 
    1586 Previous:<a rel=previous accesskey=p href="#Section%204.30">Section 4.30</a>, 
    1587 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1588 <br> 
    1589  
    1590 <h3>4.31 Problems on particular motherboards</h3> 
     1563Next:<a rel=next href="#Section%204.32">Section 4.32</a>, 
     1564Previous:<a rel=previous href="#Section%204.30">Section 4.30</a>, 
     1565Up:<a rel=up href="#Problems">Problems</a> 
     1566<br> 
     1567 
     1568<h2>4.31 Problems on particular motherboards</h2> 
    15911569 
    15921570<p>The following boards have unique problems and solutions. 
     
    15941572<p><a name="Asus%20P4B"></a> 
    15951573 
    1596 <h4>4.31.1 Asus P4B</h4> 
     1574<h3>4.31.1 Asus P4B</h3> 
    15971575 
    15981576<p>See <code>prog/hotplug/README.p4b</code> if your SMBus master is not found. 
     
    16001578<p><a name="Tyan%202460%202462"></a> 
    16011579 
    1602 <h4>4.31.2 Tyan 2460, 2462</h4> 
     1580<h3>4.31.2 Tyan 2460, 2462</h3> 
    16031581 
    16041582<p>See support tickets 805, 765, 781, 812, 813, and 867 for information. 
     
    16061584<p><a name="Tyan%202466"></a> 
    16071585 
    1608 <h4>4.31.3 Tyan 2466</h4> 
     1586<h3>4.31.3 Tyan 2466</h3> 
    16091587 
    16101588<p>See support tickets 941, 840, and 841 for information. 
     
    16121590<p><a name="Tyan%202688"></a> 
    16131591 
    1614 <h4>4.31.4 Tyan 2688</h4> 
     1592<h3>4.31.4 Tyan 2688</h3> 
    16151593 
    16161594<p>For board hangs, see support ticket 721 for information.  
     
    16181596 
    16191597<p><hr> 
     1598Node:<a name="Section%204.32">Section 4.32</a>, 
     1599Previous:<a rel=previous href="#Section%204.31">Section 4.31</a>, 
     1600Up:<a rel=up href="#Problems">Problems</a> 
     1601<br> 
     1602 
     1603<h2>4.32 Problems on particular systems</h2> 
     1604 
     1605<p>For IBM systems, see <code>README.thinkpad</code>. 
     1606 
     1607<p><hr> 
    16201608Node:<a name="Help">Help</a>, 
    1621 Next:<a rel=next accesskey=n href="#Contribute">Contribute</a>, 
    1622 Previous:<a rel=previous accesskey=p href="#Problems">Problems</a>, 
    1623 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1624 <br> 
    1625  
    1626 <h2>5 How to Ask for Help</h2> 
    1627  
    1628 <ul> 
    1629 <li><a accesskey=1 href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
    1630 <li><a accesskey=2 href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
    1631 <li><a accesskey=3 href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
    1632 <li><a accesskey=4 href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
    1633 <li><a accesskey=5 href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
    1634 <li><a accesskey=6 href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
    1635 <li><a accesskey=7 href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
    1636 <li><a accesskey=8 href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
     1609Next:<a rel=next href="#Contribute">Contribute</a>, 
     1610Previous:<a rel=previous href="#Problems">Problems</a>, 
     1611Up:<a rel=up href="#Top">Top</a> 
     1612<br> 
     1613 
     1614<h1>5 How to Ask for Help</h1> 
     1615 
     1616<ul> 
     1617<li><a href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
     1618<li><a href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
     1619<li><a href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
     1620<li><a href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
     1621<li><a href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
     1622<li><a href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
     1623<li><a href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
     1624<li><a href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
    16371625</ul> 
    16381626 
    16391627<p><hr> 
    16401628Node:<a name="Section%205.1">Section 5.1</a>, 
    1641 Next:<a rel=next accesskey=n href="#Section%205.2">Section 5.2</a>, 
    1642 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1643 <br> 
    1644  
    1645 <h3>5.1 What to send us when asking for help</h3> 
     1629Next:<a rel=next href="#Section%205.2">Section 5.2</a>, 
     1630Up:<a rel=up href="#Help">Help</a> 
     1631<br> 
     1632 
     1633<h2>5.1 What to send us when asking for help</h2> 
    16461634 
    16471635<p>We are always willing to answer questions if things don't work out.  
     
    16851673<p><hr> 
    16861674Node:<a name="Section%205.2">Section 5.2</a>, 
    1687 Next:<a rel=next accesskey=n href="#Section%205.3">Section 5.3</a>, 
    1688 Previous:<a rel=previous accesskey=p href="#Section%205.1">Section 5.1</a>, 
    1689 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1690 <br> 
    1691  
    1692 <h3>5.2 What to do if a module won't insert?</h3> 
     1675Next:<a rel=next href="#Section%205.3">Section 5.3</a>, 
     1676Previous:<a rel=previous href="#Section%205.1">Section 5.1</a>, 
     1677Up:<a rel=up href="#Help">Help</a> 
     1678<br> 
     1679 
     1680<h2>5.2 What to do if a module won't insert?</h2> 
    16931681 
    16941682<p>Did you use <code>modprobe</code> instead of <code>insmod</code>??? Don't use insmod. 
     
    17041692<p><hr> 
    17051693Node:<a name="Section%205.3">Section 5.3</a>, 
    1706 Next:<a rel=next accesskey=n href="#Section%205.4">Section 5.4</a>, 
    1707 Previous:<a rel=previous accesskey=p href="#Section%205.2">Section 5.2</a>, 
    1708 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1709 <br> 
    1710  
    1711 <h3>5.3 What to do if it inserts, but nothing happens?</h3> 
     1694Next:<a rel=next href="#Section%205.4">Section 5.4</a>, 
     1695Previous:<a rel=previous href="#Section%205.2">Section 5.2</a>, 
     1696Up:<a rel=up href="#Help">Help</a> 
     1697<br> 
     1698 
     1699<h2>5.3 What to do if it inserts, but nothing happens?</h2> 
    17121700 
    17131701<p>For an ISA sensor chip, did you also <code>modprobe i2c-isa</code>? It must be inserted. 
     
    17221710<p><hr> 
    17231711Node:<a name="Section%205.4">Section 5.4</a>, 
    1724 Next:<a rel=next accesskey=n href="#Section%205.5">Section 5.5</a>, 
    1725 Previous:<a rel=previous accesskey=p href="#Section%205.3">Section 5.3</a>, 
    1726 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1727 <br> 
    1728  
    1729 <h3>5.4 What to do if I read only bogus information?</h3> 
     1712Next:<a rel=next href="#Section%205.5">Section 5.5</a>, 
     1713Previous:<a rel=previous href="#Section%205.3">Section 5.3</a>, 
     1714Up:<a rel=up href="#Help">Help</a> 
     1715<br> 
     1716 
     1717<h2>5.4 What to do if I read only bogus information?</h2> 
    17301718 
    17311719<p>It may be that this was a mis-detection: the chip may not be 
     
    17371725<p><hr> 
    17381726Node:<a name="Section%205.5">Section 5.5</a>, 
    1739 Next:<a rel=next accesskey=n href="#Section%205.6">Section 5.6</a>, 
    1740 Previous:<a rel=previous accesskey=p href="#Section%205.4">Section 5.4</a>, 
    1741 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1742 <br> 
    1743  
    1744 <h3>5.5 What to do if you have other problems?</h3> 
     1727Next:<a rel=next href="#Section%205.6">Section 5.6</a>, 
     1728Previous:<a rel=previous href="#Section%205.4">Section 5.4</a>, 
     1729Up:<a rel=up href="#Help">Help</a> 
     1730<br> 
     1731 
     1732<h2>5.5 What to do if you have other problems?</h2> 
    17451733 
    17461734<p>Again, send the output listed above. 
     
    17481736<p><hr> 
    17491737Node:<a name="Section%205.6">Section 5.6</a>, 
    1750 Next:<a rel=next accesskey=n href="#Section%205.7">Section 5.7</a>, 
    1751 Previous:<a rel=previous accesskey=p href="#Section%205.5">Section 5.5</a>, 
    1752 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1753 <br> 
    1754  
    1755 <h3>5.6 What if it just works like a charm?</h3> 
     1738Next:<a rel=next href="#Section%205.7">Section 5.7</a>, 
     1739Previous:<a rel=previous href="#Section%205.5">Section 5.5</a>, 
     1740Up:<a rel=up href="#Help">Help</a> 
     1741<br> 
     1742 
     1743<h2>5.6 What if it just works like a charm?</h2> 
    17561744 
    17571745<p>Drop us a mail if you feel like it, mentioning the mainboard and 
     
    17601748<p><hr> 
    17611749Node:<a name="Section%205.7">Section 5.7</a>, 
    1762 Next:<a rel=next accesskey=n href="#Section%205.8">Section 5.8</a>, 
    1763 Previous:<a rel=previous accesskey=p href="#Section%205.6">Section 5.6</a>, 
    1764 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1765 <br> 
    1766  
    1767 <h3>5.7 How do I update a ticket?</h3> 
     1750Next:<a rel=next href="#Section%205.8">Section 5.8</a>, 
     1751Previous:<a rel=previous href="#Section%205.6">Section 5.6</a>, 
     1752Up:<a rel=up href="#Help">Help</a> 
     1753<br> 
     1754 
     1755<h2>5.7 How do I update a ticket?</h2> 
    17681756 
    17691757<p>You can't. Only developers can. Follow up by emailing us 
     
    17741762<p><hr> 
    17751763Node:<a name="Section%205.8">Section 5.8</a>, 
    1776 Previous:<a rel=previous accesskey=p href="#Section%205.7">Section 5.7</a>, 
    1777 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1778 <br> 
    1779  
    1780 <h3>5.8 How do I follow up on a ticket?</h3> 
     1764Previous:<a rel=previous href="#Section%205.7">Section 5.7</a>, 
     1765Up:<a rel=up href="#Help">Help</a> 
     1766<br> 
     1767 
     1768<h2>5.8 How do I follow up on a ticket?</h2> 
    17811769 
    17821770<p>Follow up by emailing us at <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> 
     
    17851773<p><hr> 
    17861774Node:<a name="Contribute">Contribute</a>, 
    1787 Next:<a rel=next accesskey=n href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    1788 Previous:<a rel=previous accesskey=p href="#Help">Help</a>, 
    1789 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1790 <br> 
    1791  
    1792 <h2>6 How to Contribute</h2> 
    1793  
    1794 <ul> 
    1795 <li><a accesskey=1 href="#Section%206.1">Section 6.1</a>:   How to write a driver 
    1796 <li><a accesskey=2 href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
    1797 <li><a accesskey=3 href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
    1798 <li><a accesskey=4 href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
    1799 <li><a accesskey=5 href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
    1800 <li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
    1801 <li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
    1802 <li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to block spam on the project mailing list 
     1775Next:<a rel=next href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     1776Previous:<a rel=previous href="#Help">Help</a>, 
     1777Up:<a rel=up href="#Top">Top</a> 
     1778<br> 
     1779 
     1780<h1>6 How to Contribute</h1> 
     1781 
     1782<ul> 
     1783<li><a href="#Section%206.1">Section 6.1</a>:   How to write a driver 
     1784<li><a href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
     1785<li><a href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
     1786<li><a href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
     1787<li><a href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
     1788<li><a href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
     1789<li><a href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
     1790<li><a href="#Section%206.8">Section 6.8</a>:   How to block spam on the project mailing list 
    18031791</ul> 
    18041792 
    18051793<p><hr> 
    18061794Node:<a name="Section%206.1">Section 6.1</a>, 
    1807 Next:<a rel=next accesskey=n href="#Section%206.2">Section 6.2</a>, 
    1808 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1809 <br> 
    1810  
    1811 <h3>6.1 How to write a driver</h3> 
     1795Next:<a rel=next href="#Section%206.2">Section 6.2</a>, 
     1796Up:<a rel=up href="#Contribute">Contribute</a> 
     1797<br> 
     1798 
     1799<h2>6.1 How to write a driver</h2> 
    18121800 
    18131801<p>See <code>doc/developers/new_drivers</code> in our package for instructions. 
     
    18151803<p><hr> 
    18161804Node:<a name="Section%206.2">Section 6.2</a>, 
    1817 Next:<a rel=next accesskey=n href="#Section%206.3">Section 6.3</a>, 
    1818 Previous:<a rel=previous accesskey=p href="#Section%206.1">Section 6.1</a>, 
    1819 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1820 <br> 
    1821  
    1822 <h3>6.2 How to get CVS access</h3> 
     1805Next:<a rel=next href="#Section%206.3">Section 6.3</a>, 
     1806Previous:<a rel=previous href="#Section%206.1">Section 6.1</a>, 
     1807Up:<a rel=up href="#Contribute">Contribute</a> 
     1808<br> 
     1809 
     1810<h2>6.2 How to get CVS access</h2> 
    18231811 
    18241812<p>For anonymous CVS read access, see the instructions on our download page.  
     
    18311819<p><hr> 
    18321820Node:<a name="Section%206.3">Section 6.3</a>, 
    1833 Next:<a rel=next accesskey=n href="#Section%206.4">Section 6.4</a>, 
    1834 Previous:<a rel=previous accesskey=p href="#Section%206.2">Section 6.2</a>, 
    1835 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1836 <br> 
    1837  
    1838 <h3>6.3 How to donate hardware to the project</h3> 
     1821Next:<a rel=next href="#Section%206.4">Section 6.4</a>, 
     1822Previous:<a rel=previous href="#Section%206.2">Section 6.2</a>, 
     1823Up:<a rel=up href="#Contribute">Contribute</a> 
     1824<br> 
     1825 
     1826<h2>6.3 How to donate hardware to the project</h2> 
    18391827 
    18401828<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. 
     
    18421830<p><hr> 
    18431831Node:<a name="Section%206.4">Section 6.4</a>, 
    1844 Next:<a rel=next accesskey=n href="#Section%206.5">Section 6.5</a>, 
    1845 Previous:<a rel=previous accesskey=p href="#Section%206.3">Section 6.3</a>, 
    1846 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1847 <br> 
    1848  
    1849 <h3>6.4 How to join the project mailing list</h3> 
     1832Next:<a rel=next href="#Section%206.5">Section 6.5</a>, 
     1833Previous:<a rel=previous href="#Section%206.3">Section 6.3</a>, 
     1834Up:<a rel=up href="#Contribute">Contribute</a> 
     1835<br> 
     1836 
     1837<h2>6.4 How to join the project mailing list</h2> 
    18501838 
    18511839<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. Sorry, 
     
    18541842<p><hr> 
    18551843Node:<a name="Section%206.5">Section 6.5</a>, 
    1856 Next:<a rel=next accesskey=n href="#Section%206.6">Section 6.6</a>, 
    1857 Previous:<a rel=previous accesskey=p href="#Section%206.4">Section 6.4</a>, 
    1858 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1859 <br> 
    1860  
    1861 <h3>6.5 How to access mailing list archives</h3> 
     1844Next:<a rel=next href="#Section%206.6">Section 6.6</a>, 
     1845Previous:<a rel=previous href="#Section%206.4">Section 6.4</a>, 
     1846Up:<a rel=up href="#Contribute">Contribute</a> 
     1847<br> 
     1848 
     1849<h2>6.5 How to access mailing list archives</h2> 
    18621850 
    18631851<p>The mailing list archive is at: <a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a> 
     
    18661854<p><hr> 
    18671855Node:<a name="Section%206.6">Section 6.6</a>, 
    1868 Next:<a rel=next accesskey=n href="#Section%206.7">Section 6.7</a>, 
    1869 Previous:<a rel=previous accesskey=p href="#Section%206.5">Section 6.5</a>, 
    1870 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1871 <br> 
    1872  
    1873 <h3>6.6 How to submit a patch</h3> 
     1856Next:<a rel=next href="#Section%206.7">Section 6.7</a>, 
     1857Previous:<a rel=previous href="#Section%206.5">Section 6.5</a>, 
     1858Up:<a rel=up href="#Contribute">Contribute</a> 
     1859<br> 
     1860 
     1861<h2>6.6 How to submit a patch</h2> 
    18741862 
    18751863<p>Check out the latest from CVS, then copy the directory to another 
     
    18801868<p><hr> 
    18811869Node:<a name="Section%206.7">Section 6.7</a>, 
    1882 Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>, 
    1883 Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>, 
    1884 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1885 <br> 
    1886  
    1887 <h3>6.7 How to REALLY help</h3> 
     1870Next:<a rel=next href="#Section%206.8">Section 6.8</a>, 
     1871Previous:<a rel=previous href="#Section%206.6">Section 6.6</a>, 
     1872Up:<a rel=up href="#Contribute">Contribute</a> 
     1873<br> 
     1874 
     1875<h2>6.7 How to REALLY help</h2> 
    18881876 
    18891877<p>Believe it or not, what we really need help with are: 
     
    19011889<p><hr> 
    19021890Node:<a name="Section%206.8">Section 6.8</a>, 
    1903 Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>, 
    1904 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1905 <br> 
    1906  
    1907 <h3>6.8 How to block spam on the project mailing list</h3> 
     1891Previous:<a rel=previous href="#Section%206.7">Section 6.7</a>, 
     1892Up:<a rel=up href="#Contribute">Contribute</a> 
     1893<br> 
     1894 
     1895<h2>6.8 How to block spam on the project mailing list</h2> 
    19081896 
    19091897<p>Sorry, we know the spam is a hassle.  It would be nice to have a 
     
    19191907<p><hr> 
    19201908Node:<a name="Version%201%20Specifics">Version 1 Specifics</a>, 
    1921 Next:<a rel=next accesskey=n href="#Document%20Revisions">Document Revisions</a>, 
    1922 Previous:<a rel=previous accesskey=p href="#Contribute">Contribute</a>, 
    1923 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1924 <br> 
    1925  
    1926 <h2>7 Version 1 Specific Questions</h2> 
    1927  
    1928 <ul> 
    1929 <li><a accesskey=1 href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
    1930 <li><a accesskey=2 href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
    1931 <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.  
    1932 <li><a accesskey=4 href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
     1909Next:<a rel=next href="#Document%20Revisions">Document Revisions</a>, 
     1910Previous:<a rel=previous href="#Contribute">Contribute</a>, 
     1911Up:<a rel=up href="#Top">Top</a> 
     1912<br> 
     1913 
     1914<h1>7 Version 1 Specific Questions</h1> 
     1915 
     1916<ul> 
     1917<li><a href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
     1918<li><a href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
     1919<li><a href="#Section%207.3">Section 7.3</a>:   I get a "No sensor data yet (try again in a few moments)" msg.  
     1920<li><a href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
    19331921</ul> 
    19341922 
     
    19371925<p><hr> 
    19381926Node:<a name="Section%207.1">Section 7.1</a>, 
    1939 Next:<a rel=next accesskey=n href="#Section%207.2">Section 7.2</a>, 
    1940 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1941 <br> 
    1942  
    1943 <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> 
     1927Next:<a rel=next href="#Section%207.2">Section 7.2</a>, 
     1928Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1929<br> 
     1930 
     1931<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> 
    19441932 
    19451933<p>Currently, our code only assumes that an SMBus exists if it originates 
     
    19641952<p><hr> 
    19651953Node:<a name="Section%207.2">Section 7.2</a>, 
    1966 Next:<a rel=next accesskey=n href="#Section%207.3">Section 7.3</a>, 
    1967 Previous:<a rel=previous accesskey=p href="#Section%207.1">Section 7.1</a>, 
    1968 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1969 <br> 
    1970  
    1971 <h3>7.2 The modules won't load, saying 'SMBus not detected'.</h3> 
     1954Next:<a rel=next href="#Section%207.3">Section 7.3</a>, 
     1955Previous:<a rel=previous href="#Section%207.1">Section 7.1</a>, 
     1956Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1957<br> 
     1958 
     1959<h2>7.2 The modules won't load, saying 'SMBus not detected'.</h2> 
    19721960 
    19731961<p>This should no longer be an issue in 1.4.10 and later; it will 
     
    19761964<p><hr> 
    19771965Node:<a name="Section%207.3">Section 7.3</a>, 
    1978 Next:<a rel=next accesskey=n href="#Section%207.4">Section 7.4</a>, 
    1979 Previous:<a rel=previous accesskey=p href="#Section%207.2">Section 7.2</a>, 
    1980 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1981 <br> 
    1982  
    1983 <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> 
     1966Next:<a rel=next href="#Section%207.4">Section 7.4</a>, 
     1967Previous:<a rel=previous 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.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> 
    19841972 
    19851973<p>It takes about 1.5 seconds for the LM78 to update all its sensor 
     
    19941982<p><hr> 
    19951983Node:<a name="Section%207.4">Section 7.4</a>, 
    1996 Previous:<a rel=previous accesskey=p href="#Section%207.3">Section 7.3</a>, 
    1997 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    1998 <br> 
    1999  
    2000 <h3>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3> 
     1984Previous:<a rel=previous href="#Section%207.3">Section 7.3</a>, 
     1985Up:<a rel=up href="#Version%201%20Specifics">Version 1 Specifics</a> 
     1986<br> 
     1987 
     1988<h2>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h2> 
    20011989 
    20021990<p>This is a bug we have only observed on Dell computers. There is 
     
    20101998<p><hr> 
    20111999Node:<a name="Document%20Revisions">Document Revisions</a>, 
    2012 Previous:<a rel=previous accesskey=p href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    2013 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    2014 <br> 
    2015  
    2016 <h2>Appendix A Revision History of This Document</h2> 
     2000Previous:<a rel=previous href="#Version%201%20Specifics">Version 1 Specifics</a>, 
     2001Up:<a rel=up href="#Top">Top</a> 
     2002<br> 
     2003 
     2004<h1>Appendix A Revision History of This Document</h1> 
    20172005 
    20182006<ul> 
     
    20412029 
    20422030</body></html> 
     2031 
  • lm-sensors/trunk/doc/lm_sensors-FAQ.texi

    r1713 r1733  
    568568* Section 4.30::        Inserting modules slows down my board 
    569569* Section 4.31::        Problems on particular motherboards 
     570* Section 4.32::        Problems on particular systems 
    570571@end menu 
    571572 
     
    11741175 
    11751176 
    1176 @node Section 4.31, , Section 4.30, Problems 
     1177@node Section 4.31, Section 4.32, Section 4.30, Problems 
    11771178@section Problems on particular motherboards 
    11781179 
     
    12031204For board hangs, see support ticket 721 for information. 
    12041205Also @ref{Section 4.29, Inserting modules hangs my board}. 
     1206 
     1207 
     1208@node Section 4.32, , Section 4.31, Problems 
     1209@section Problems on particular systems 
     1210 
     1211For IBM systems, see @file{README.thinkpad}. 
    12051212 
    12061213