Changeset 2450

Show
Ignore:
Timestamp:
04/18/04 15:46:16 (9 years ago)
Author:
mds
Message:

regenerated with makeinfo 4.7

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

Legend:

Unmodified
Added
Removed

  • lm-sensors/trunk/doc/FAQ

    r2447 r2450  
    1 START-INFO-DIR-ENTRY 
    2 * lm_sensors-FAQ: (lm_sensors-FAQ)           The lm_sensors FAQ 
    3 END-INFO-DIR-ENTRY 
    4  
    51Short Contents 
    62************** 
    … …  
    2016***************** 
    2117 
    22  
    2318lm_sensors 
    24  
    25191 PC and Sensor Overview 
    2620  1.1 What sensors are available on my PC? 
    2721  1.2 What can a sensor chip like the "LM78" do? 
    2822  1.3 Where do I find out more about any of these chips? 
    29  
    30232 Sensor and Bus Basics 
    3124  2.1 How are these sensors read? 
    … …  
    3528  2.5 How often are the sensor values updated? 
    3629  2.6 How are alarms triggered? 
    37  
    38303 Installation and Management 
    3931  3.1 Why so many modules, and how do I cope with them? 
    … …  
    5850  3.9 I get unresolved symbols when I `modprobe' modules (Red Hat especially) 
    5951  3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
    60  
    61524 Problems 
    6253  4.1 My fans report exactly half/double their values compared to the BIOS? 
    … …  
    117108  4.32 Problems on particular systems 
    118109  4.33 Problems on 2.6 kernels 
    119  
    1201105 How to Ask for Help 
    121111  5.1 What to send us when asking for help 
    … …  
    127117  5.7 How do I update a ticket? 
    128118  5.8 How do I follow up on a ticket? 
    129  
    1301196 How to Contribute 
    131120  6.1 How to write a driver 
    … …  
    138127  6.8 How to get release announcements 
    139128  6.9 How to block spam on the project mailing list 
    140  
    1411297 Version 1 Specific Questions 
    142130  7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it.  What's wrong? 
    … …  
    144132  7.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why? 
    145133  7.4 On my Dell, a LM80 is detected, but all readings are 0! 
    146  
    147134Appendix A Revision History of This Document 
    148135 
    … …  
    151138********** 
    152139 
    153    The lm_sensors package includes a collection of modules for general 
     140The lm_sensors package includes a collection of modules for general 
    154141SMBus access and hardware monitoring.  NOTE: this requires special 
    155142support which is not in standard 2.2-vintage kernels. 
    … …  
    161148======================================== 
    162149 
    163    Most PC's built since late 1997 now come with a hardware health 
     150Most PC's built since late 1997 now come with a hardware health 
    164151monitoring chip. This chip may be accessed via the ISA bus or the 
    165152SMBus, depending on the motherboard. 
    … …  
    175162============================================== 
    176163 
    177    The LM78 is a chip made by National Semiconductor which can monitor 7 
     164The LM78 is a chip made by National Semiconductor which can monitor 7 
    178165voltages (5 positive, 2 negative) from 0 to 4.08V.  The inputs are 
    179166usually in series with voltage dividers which lower the +/- 12V and +/- 
    … …  
    197184====================================================== 
    198185 
    199    Most semiconductor companies have comprehensive documentation, 
     186Most semiconductor companies have comprehensive documentation, 
    200187including complete datasheets, on their websites. Analog Devices, 
    201188Dallas Semiconductor, Maxim, and National Semiconductor have the widest 
    … …  
    220207=============================== 
    221208 
    222    Sensor chips reside on either the ISA bus, the SMBus, or both.  See 
    223 the file `doc/chips/SUMMARY' in our package for a list. 
     209Sensor chips reside on either the ISA bus, the SMBus, or both.  See the 
     210file `doc/chips/SUMMARY' in our package for a list. 
    224211 
    225212   To communicate with chips on the ISA bus, the software uses simple 
    … …  
    232219======================================= 
    233220 
    234    The SMBus is the "System Management Bus".  More specifically, it is a 
     221The SMBus is the "System Management Bus".  More specifically, it is a 
    2352222-wire, low-speed serial communication bus used for basic health 
    236223monitoring and hardware management. It is a specific implementation of 
    … …  
    253240============================ 
    254241 
    255    We promise, you do, even if you don't have any old ISA slots.  The 
    256 "ISA Bus" exists in your computer even if you don't have ISA slots; it 
    257 is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF) where 
    258 many "legacy" functions, such as keyboard and interrupt controllers, 
    259 are found. It isn't necessarily a separate physical bus.  See the file 
     242We promise, you do, even if you don't have any old ISA slots.  The "ISA 
     243Bus" exists in your computer even if you don't have ISA slots; it is 
     244simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF) where many 
     245"legacy" functions, such as keyboard and interrupt controllers, are 
     246found. It isn't necessarily a separate physical bus.  See the file 
    260247`/proc/ioports' for a list of devices living on the "ISA Bus" in your 
    261248system. If you don't like the term "ISA Bus" think "I/O Space". 
    … …  
    264251==================================== 
    265252 
    266    Most new processors contain a thermal diode on the die itself.  The 
     253Most new processors contain a thermal diode on the die itself.  The 
    267254electical properties of all diodes and transistors vary slightly with 
    268255temperature. The thermal diode is exceptionally accurate because it is 
    … …  
    299286============================================ 
    300287 
    301    The LM78, and most other sensor chips like it, reads its sensors one 
    302 by one. A complete scanning sweep will take about 1.5 seconds. The LM78 
     288The LM78, and most other sensor chips like it, reads its sensors one by 
     289one. A complete scanning sweep will take about 1.5 seconds. The LM78 
    303290stops readings sensors if you try to access it, so if you access it 
    304291very often (by reading sensor values; writing new limits is safe) it 
    … …  
    311298============================= 
    312299 
    313    It is possible to monitor each sensor and have an alarm go off if it 
     300It is possible to monitor each sensor and have an alarm go off if it 
    314301crosses some pre-determined limits.  There are two sorts of interrupts 
    315302which can be generated by sensor chips if this happens (it depends a 
    … …  
    335322===================================================== 
    336323 
    337    We tried to make this package as modular as possible. This makes it 
     324We tried to make this package as modular as possible. This makes it 
    338325easy to add new drivers, and unused drivers will take no precious kernel 
    339326space. On the other hand, it can be a bit confusing at first. 
    … …  
    349336==================================== 
    350337 
    351    We have an excellent program that scans all your hardware.  It is 
     338We have an excellent program that scans all your hardware.  It is 
    352339called `sensors-detect' and is installed in `/usr/local/sbin' by `make 
    353340install'. Just execute this script, and it will tell you. 
    … …  
    364351---------------------------------------- 
    365352 
    366    *!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!* 
     353*!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!* 
    367354 
    368355   We have no idea. Here is what you should do: 
    … …  
    383370------------------------------------- 
    384371 
    385    We don't support boards, we support chips. *Note What chips are on 
     372We don't support boards, we support chips. *Note What chips are on 
    386373motherboard XYZ: Section 3.2.1. 
    387374 
    … …  
    389376------------------------------ 
    390377 
    391    This we have good answers for. 
     378This we have good answers for. 
    392379   * Sorted by Manufacturer:   `README' 
    393380 
    … …  
    403390----------------------------------------------- 
    404391 
    405    Newest Driver Status: 
    406 `http://www2.lm-sensors.nu/~lm78/newdrivers.html' 
     392Newest Driver Status: `http://www2.lm-sensors.nu/~lm78/newdrivers.html' 
    407393 
    4083943.3 Which modules should I insert? 
    409395================================== 
    410396 
    411    `sensors-detect' will tell you. Take the `modprobe' lines it 
    412 recommends and paste them into the appropriate `/etc/rc.d/xxxx' file to 
    413 be executed at startup. 
     397`sensors-detect' will tell you. Take the `modprobe' lines it recommends 
     398and paste them into the appropriate `/etc/rc.d/xxxx' file to be 
     399executed at startup. 
    414400 
    415401   You need one module for each sensor chip and bus adapter you own; if 
    … …  
    432418========================================================= 
    433419 
    434    Yes, for any applications that use `libsensors,' including the 
     420Yes, for any applications that use `libsensors,' including the 
    435421`sensors' application included in our package.  It tells libsensors how 
    436422to translate the values the chip measures to real-world values. This is 
    … …  
    443429------------------------------------------------------------------------------------- 
    444430 
    445    Every motherboard is different. You can customize the labels in the 
     431Every motherboard is different. You can customize the labels in the 
    446432file `/etc/sensors.conf'. That's why it exists!  The default labelling 
    447433(in `lib/chips.c' and `/etc/sensors.conf') is just a template. 
    … …  
    450436------------------------------------------------------------------ 
    451437 
    452    You can customize them in the file `/etc/sensors.conf'. See above. 
     438You can customize them in the file `/etc/sensors.conf'. See above. 
    453439 
    4544403.4.3 The min and max settings in `/etc/sensors.conf' didn't take effect! 
    455441------------------------------------------------------------------------- 
    456442 
    457    You forgot to run `sensors -s'. See above. 
     443You forgot to run `sensors -s'. See above. 
    458444 
    4594453.4.4 One sensor isn't hooked up on my board! 
    460446--------------------------------------------- 
    461447 
    462    Use an `ignore' line in `/etc/sensors.conf' so it isn't displayed in 
     448Use an `ignore' line in `/etc/sensors.conf' so it isn't displayed in 
    463449`sensors'. 
    464450 
    … …  
    466452-------------------------------------- 
    467453 
    468    There is detailed help at the top of that file. 
     454There is detailed help at the top of that file. 
    469455 
    4704563.4.6 Do you have a database of `sensors.conf' entries for specific boards? 
    471457--------------------------------------------------------------------------- 
    472458 
    473    No. Good idea though. If you would like to set one up on your website 
     459No. Good idea though. If you would like to set one up on your website 
    474460send us mail and we will set up a link to it. 
    475461 
    … …  
    477463======================================================================= 
    478464 
    479    Don't worry about them. The dependency files (which tell which files 
     465Don't worry about them. The dependency files (which tell which files 
    480466should be recompiled when certain files change) are created 
    481467dynamically. They are not distributed with the package. The `make' 
    … …  
    486472================================================ 
    487473 
    488    Check that the correct i2c header files are used. Depending on how 
    489 you installed, they should be under either `/usr/local/include' or 
     474Check that the correct i2c header files are used. Depending on how you 
     475installed, they should be under either `/usr/local/include' or 
    490476`/usr/src/linux*/include'. Try to edit the `Makefile' for the other 
    491477setting. 
    … …  
    507493======================================= 
    508494 
    509    Have you installed the matching version of the i2c package? Remember, 
     495Have you installed the matching version of the i2c package? Remember, 
    510496compilation is not enough, you also need to install it for the header 
    511497files to be found! 
    … …  
    517503============================================ 
    518504 
    519    Mandrake uses a non-standard `version.h' file which confuses our 
     505Mandrake uses a non-standard `version.h' file which confuses our 
    520506`Makefile'.  Edit our `Makefile' on the `MODDIR :=' line to hard-code 
    521507the module directory. 
    … …  
    524510=========================================================================== 
    525511 
    526    Example: 
     512Example: 
    527513     *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
    528514     i2c_bit_add_bus_R8c3bc60e 
    … …  
    555541======================================================== 
    556542 
    557    In some versions of Redhat, an RPM is included to provide i2c 
    558 support.  However, this RPM does not place the header files in the 
    559 kernel directory structure.  When you update kernels, they may persist. 
    560 To get rid of these obsolete header files, at a command prompt: 
     543In some versions of Redhat, an RPM is included to provide i2c support. 
     544However, this RPM does not place the header files in the kernel 
     545directory structure.  When you update kernels, they may persist.  To 
     546get rid of these obsolete header files, at a command prompt: 
    561547 
    562548  1. `rpm -qa | grep i2c' 
    … …  
    585571========================================================================= 
    586572 
    587    The problem with much of the sensor data is that it is impossible to 
     573The problem with much of the sensor data is that it is impossible to 
    588574properly interpret some of the readings without knowing what the 
    589575hardware configuration is.  Some fans report one 'tick' each rotation, 
    … …  
    601587------------------------------------ 
    602588 
    603    You may not have a three-wire fan, which is required. 
     589You may not have a three-wire fan, which is required. 
    604590 
    605591   You may need to increase the 'fan divisor'. See `doc/fan-divisors' 
    … …  
    609595------------------------------------------------------------- 
    610596 
    611    Believe it or not, doubling the 'fan divisor' will not halve the fan 
     597Believe it or not, doubling the 'fan divisor' will not halve the fan 
    612598reading. You have to add a compute line in `/etc/sensors.conf'.  *Note 
    613599My fans report exactly half/double their values compared to the BIOS: 
    … …  
    618604============================================== 
    619605 
    620    For starters, those aren't LM75's.  Your mainboard actually has the 
     606For starters, those aren't LM75's.  Your mainboard actually has the 
    621607Winbond W83781D which emulates two LM75's, but many systems which use 
    622608the Winbond chip (such as the Asus P2B) don't have the thermo-resisters 
    … …  
    629615================================================================ 
    630616 
    631    The LM78 has seven voltage sensors. The default way of connecting 
    632 them is used in the configuration file. This includes a VCore2, even if 
    633 you do not have one. You can easily edit the configuration file to give 
    634 it another name, or make this reading disappear using an `ignore' line. 
     617The LM78 has seven voltage sensors. The default way of connecting them 
     618is used in the configuration file. This includes a VCore2, even if you 
     619do not have one. You can easily edit the configuration file to give it 
     620another name, or make this reading disappear using an `ignore' line. 
    635621 
    636622   Note that Vcore2 is often the same as Vcore on motherboards which 
    … …  
    643629==================================================================================================== 
    644630 
    645    The ALARM indications in `sensors' are those reported by the sensor 
     631The ALARM indications in `sensors' are those reported by the sensor 
    646632chip itself. They are NOT calculated by `sensors'. `sensors' simply 
    647633reads the ALARM bits and reports them. 
    … …  
    666652================================================================ 
    667653 
    668    No, probably not. If your motherboard heats up a bit, the sensed 
     654No, probably not. If your motherboard heats up a bit, the sensed 
    669655voltages will drift a bit. If your power supply is loaded (because a 
    670656disk gets going, for example), the voltages may get a bit lower. Heavy 
    … …  
    678664========================================================== 
    679665 
    680    Each module tries to set limits to sensible values on initialization, 
     666Each module tries to set limits to sensible values on initialization, 
    681667but a module does not know how a chip is actually connected. This is 
    682668described in the configuration file, which is not read by kernel 
    … …  
    694680===================================================== 
    695681 
    696    These describe the core voltage for your processor. They are 
    697 supported for most processors, however they are not always correctly 
    698 connected to the sensor chip, so the readings may be invalid.  A 
    699 reading of 0V, +3.5V or +2.05V is especially suspect.  If this is the 
    700 case, add a line `ignore vid' to `/etc/sensors.conf', and change the 
    701 min and max settings for the Processor Core voltage (often in0_min and 
    702 in0_max) in that file so that they don't depend on vid. 
     682These describe the core voltage for your processor. They are supported 
     683for most processors, however they are not always correctly connected to 
     684the sensor chip, so the readings may be invalid.  A reading of 0V, 
     685+3.5V or +2.05V is especially suspect.  If this is the case, add a line 
     686`ignore vid' to `/etc/sensors.conf', and change the min and max 
     687settings for the Processor Core voltage (often in0_min and in0_max) in 
     688that file so that they don't depend on vid. 
    703689 
    7046904.8 I read sensor values several times a second, but they are only updated only each second or so. Why? 
    705691======================================================================================================= 
    706692 
    707    If we would read the registers more often, it would not find the 
    708 time to update them. So we only update our readings once each 1.5 
    709 seconds (the actual delay is chip-specific; for some chips, it may not 
    710 be needed at all). 
     693If we would read the registers more often, it would not find the time 
     694to update them. So we only update our readings once each 1.5 seconds 
     695(the actual delay is chip-specific; for some chips, it may not be needed 
     696at all). 
    711697 
    7126984.9 It sometimes seems to take almost a second before I see the sensor reading results. Why? 
    713699============================================================================================ 
    714700 
    715    ISA bus access is fast, but SMBus access is really slow. If you have 
    716 a lot of sensors, it just takes a lot of time to access them. 
    717 Fortunately, this has almost no impact on the system as a whole, as 
    718 another job can run while we are waiting for the transaction to finish. 
     701ISA bus access is fast, but SMBus access is really slow. If you have a 
     702lot of sensors, it just takes a lot of time to access them. Fortunately, 
     703this has almost no impact on the system as a whole, as another job can 
     704run while we are waiting for the transaction to finish. 
    719705 
    7207064.10 Can I be alerted when an ALARM occurs? 
    721707=========================================== 
    722708 
    723    No, you can't; and it may well be never supported. 
     709No, you can't; and it may well be never supported. 
    724710 
    725711   Almost no mainboard we have encountered have actually connected the 
    … …  
    743729============================================================================== 
    744730 
    745    Some chips which mainboard makers connect to the SMBus are not SMBus 
     731Some chips which mainboard makers connect to the SMBus are not SMBus 
    746732devices.  An example is the 91xx clock generator chips.  When read, 
    747733these devices can lock up the SMBus until the next hard reboot.  This 
    … …  
    756742===================================================================== 
    757743 
    758    We display the actual temperature of the sensor. This may not be the 
     744We display the actual temperature of the sensor. This may not be the 
    759745temperature you are interested in, though.  If a sensor should measure 
    760746the CPU temperature, it must be in thermal contact with it.  In 
    … …  
    772758======================================================================= 
    773759 
    774    Remember, these values do not take the configuration file `compute' 
     760Remember, these values do not take the configuration file `compute' 
    775761lines in account. This is especially obvious for voltage readings 
    776762(usually called in? or vin?). Use a program linked to libsensors (like 
    … …  
    780766============================= 
    781767 
    782    Change the limit values in `/etc/sensors.conf' and then run `sensors 
     768Change the limit values in `/etc/sensors.conf' and then run `sensors 
    783769-s'. 
    784770 
    … …  
    786772------------------------------------------- 
    787773 
    788    You forgot to run `sensors -s'. Put it in a `/etc/rc.d/...' file 
    789 after the modprobe lines to run at startup. 
     774You forgot to run `sensors -s'. Put it in a `/etc/rc.d/...' file after 
     775the modprobe lines to run at startup. 
    790776 
    7917774.15 Some sensors are doubly detected? 
    792778====================================== 
    793779 
    794    Yes, this is still a problem. It is partially solved by alias 
    795 detection and confidence values in sensors-detect, but it is really 
    796 tough. 
     780Yes, this is still a problem. It is partially solved by alias detection 
     781and confidence values in sensors-detect, but it is really tough. 
    797782 
    798783   Double detections can be caused by two things: sensors can be 
    … …  
    807792================================================================= 
    808793 
    809    Your SMBus (PIIX4?) is probably crashed or hung. There are some 
     794Your SMBus (PIIX4?) is probably crashed or hung. There are some 
    810795mainboards which connect a clock chip to the SMBus. Unfortunately, this 
    811796clock chip hangs the PIIX4 if it is read (it is an I2C device, but not 
    … …  
    818803======================================= 
    819804 
    820    See below for some particularly troublesome chips.  Also be sure and 
     805See below for some particularly troublesome chips.  Also be sure and 
    821806check `doc/chips/xxxxx' for the particular driver. 
    822807 
    … …  
    824809-------------------------------------- 
    825810 
    826    The Asus AS99127F is a modified version of the Winbond W83781D. 
    827 Asus will not release a datasheet. The driver was developed by tedious 
     811The Asus AS99127F is a modified version of the Winbond W83781D.  Asus 
     812will not release a datasheet. The driver was developed by tedious 
    828813experimentation. We've done the best we can. If you want to make 
    829814adjustments to the readings please edit `/etc/sensors.conf.' Please 
    … …  
    833818-------------------------------------- 
    834819 
    835    The Via 686A datasheet is incomplete.  Via will not release details. 
     820The Via 686A datasheet is incomplete.  Via will not release details. 
    836821The driver was developed by tedious experimentation. We've done the 
    837822best we can. If you want to make adjustments to the readings please 
    … …  
    843828------------------------------------ 
    844829 
    845    The MTP008 has programmable temperature sensor types.  If your 
    846 sensor type does not match the default, you will have to change it. 
    847 See `doc/chips/mtp008' for details.  Also, MTP008 chips seem to 
    848 randomly refuse to respond, for unknown reasons. You can see this as 
    849 'XX' entries in i2cdump. 
     830The MTP008 has programmable temperature sensor types.  If your sensor 
     831type does not match the default, you will have to change it.  See 
     832`doc/chips/mtp008' for details.  Also, MTP008 chips seem to randomly 
     833refuse to respond, for unknown reasons. You can see this as 'XX' 
     834entries in i2cdump. 
    850835 
    8518364.17.4 Bad temperature readings from the SIS5595! 
    852837------------------------------------------------- 
    853838 
    854    This chip can use multiple thermistor types and there are also two 
     839This chip can use multiple thermistor types and there are also two 
    855840different versions of the chip. We are trying to get the driver working 
    856841better and develop formulas for different thermistors but we aren't 
    … …  
    861846-------------------------------------- 
    862847 
    863    Do you own an ASUS motherboard?  Perhaps your chip is being 
     848Do you own an ASUS motherboard?  Perhaps your chip is being 
    864849misidentified.  Look on the motherboard (or at 
    865850`http://mbm.livewiredev.com') for a 'Winbond' or Asus chip.  Often the 
    … …  
    873858------------------------------------------------ 
    874859 
    875    The SMBus tends to hang on this board and it seems to get worse at 
     860The SMBus tends to hang on this board and it seems to get worse at 
    876861higher temperatures. Use ISA accesses to reliably use the w83781d 
    877862monitor chip on this board and use the `ignore=1,0x2d' or similar option 
    … …  
    881866------------------------------ 
    882867 
    883    The LM75 detection is poor and other hardware is often misdetected 
    884 as an LM75. Figure out what you really have *Note What chips are on 
     868The LM75 detection is poor and other hardware is often misdetected as 
     869an LM75. Figure out what you really have *Note What chips are on 
    885870motherboard XYZ: Section 3.2.1. 
    886871 
    … …  
    888873------------------------------ 
    889874 
    890    The LM78 is no longer manufactured by National Semiconductor.  You 
     875The LM78 is no longer manufactured by National Semiconductor.  You 
    891876probably don't have a real LM78 but something similar that we do not 
    892877recogize or support. Figure out what you really have *Note What chips 
    … …  
    896881------------------------------ 
    897882 
    898    The LM80 detection is poor and other hardware is often misdetected 
    899 as an LM80. Figure out what you really have *Note What chips are on 
     883The LM80 detection is poor and other hardware is often misdetected as 
     884an LM80. Figure out what you really have *Note What chips are on 
    900885motherboard XYZ: Section 3.2.1. 
    901886 
    … …  
    903888------------------------------- 
    904889 
    905    The it87 temperature sesnsors are configured, unfortunately, in a 
    906 way different from w83781d. They cannot be configured from 
     890The it87 temperature sesnsors are configured, unfortunately, in a way 
     891different from w83781d. They cannot be configured from 
    907892`/etc/sensors.conf'; they must be set at modprobe insertion with 
    908893`modprobe it87 temp_type=0xXX'. See `doc/chips/it87' for details. 
    … …  
    911896===================================================== 
    912897 
    913    There is a SuperMicro board with two LM87's on it that are not 
    914 hooked up in the same way, so they need different defaults.  For 
    915 example, both CPU temperatures go to one LM87. 
     898There is a SuperMicro board with two LM87's on it that are not hooked 
     899up in the same way, so they need different defaults.  For example, both 
     900CPU temperatures go to one LM87. 
    916901 
    917902   Make two different sections in `/etc/sensors.conf' as follows: 
    … …  
    927912================================================ 
    928913 
    929    If the problem is a PCI device is not present in `lspci', the 
    930 solution is complex. For the ALI M7101 device, there is a solution 
    931 which uses the 2.4 kernel's `hotplug' facility. See `prog/hotplug' in 
    932 our package.  For other PCI devices, you can try to modify the m7101 
    933 solution in `prog/hotplug'. 
     914If the problem is a PCI device is not present in `lspci', the solution 
     915is complex. For the ALI M7101 device, there is a solution which uses the 
     9162.4 kernel's `hotplug' facility. See `prog/hotplug' in our package. 
     917For other PCI devices, you can try to modify the m7101 solution in 
     918`prog/hotplug'. 
    934919 
    935920   If dmesg says `try force_addr', see below. Other drivers generally 
    … …  
    941926----------------------------------------------------------------- 
    942927 
    943    If the problem is a PCI device whose base address is not set, you 
    944 may be able to set the address with a force parameter. The via686a and 
     928If the problem is a PCI device whose base address is not set, you may 
     929be able to set the address with a force parameter. The via686a and 
    945930sis5595 chip drivers, and some bus drivers, support the command line 
    946931`modprobe via686a force_addr=0xADDRESS' where ADDRESS is the I/O 
    … …  
    983968=================================== 
    984969 
    985    What specifically is the trouble? 
     970What specifically is the trouble? 
    986971   * Labels: *Note The labels for the voltage and temperature readings 
    987972     in sensors are incorrect: Section 3.4.1. 
    … …  
    10201005================================ 
    10211006 
    1022    In general, we don't know. Start by running `sensors-detect'.  If it 
     1007In general, we don't know. Start by running `sensors-detect'.  If it 
    10231008doesn't recognize it, try running `i2cdump'. A partial list of 
    10241009manufacturers' IDs are at the bottom of `doc/chips/SUMMARY'. 
    … …  
    10271012----------------------------------- 
    10281013 
    1029    A clock chip. Often, accessing these clock chips in the wrong way 
    1030 will instantly crash your computer. Sensors-detect carefully avoids 
    1031 these chips. If you really really want to play with your clock chip you 
    1032 can look at `kernel/chips/icspll.c' in our package. But we do not 
    1033 recommend it. You have been warned. 
     1014A clock chip. Often, accessing these clock chips in the wrong way will 
     1015instantly crash your computer. Sensors-detect carefully avoids these 
     1016chips. If you really really want to play with your clock chip you can 
     1017look at `kernel/chips/icspll.c' in our package. But we do not recommend 
     1018it. You have been warned. 
    10341019 
    103510204.23.2 What is at I2C addresses 0x50 - 0x57? 
    10361021-------------------------------------------- 
    10371022 
    1038    EEPROMs on your SDRAM DIMMs. Load the eeprom module to look at some 
     1023EEPROMs on your SDRAM DIMMs. Load the eeprom module to look at some 
    10391024basic data in `sensors' or use the program 
    10401025`prog/eeprom/decode-dimms.pl' to get more information than you ever 
    … …  
    10441029-------------------------------------------- 
    10451030 
    1046    These are often 'shadows' of your EEPROMs on your SDRAM DIMMs at 
     1031These are often 'shadows' of your EEPROMs on your SDRAM DIMMs at 
    10471032addresses 0x50 - 0x57. They are the 'software write-protect' registers 
    10481033of the SDRAM Serial Presence Detect EEPROMs.  If you try and do a 
    … …  
    10541039======================================= 
    10551040 
    1056    It could be many things. What was the problem? *Note Problems on 
     1041It could be many things. What was the problem? *Note Problems on 
    10571042particular motherboards: Section 4.31. 
    10581043 
    … …  
    10601045----------------------------------------------------------- 
    10611046 
    1062    You don't have i2c support in your kernel, or the i2c-core module 
    1063 was not loaded and you did not run sensors-detect as root. 
     1047You don't have i2c support in your kernel, or the i2c-core module was 
     1048not loaded and you did not run sensors-detect as root. 
    10641049 
    106510504.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0" 
    10661051----------------------------------------------------- 
    10671052 
    1068    Your `/dev/i2c-0,' `/dev/i2c0', or `/dev/i2c/0' files do not exist 
    1069 or you did not run `sensors-detect' as root.  Run the script 
     1053Your `/dev/i2c-0,' `/dev/i2c0', or `/dev/i2c/0' files do not exist or 
     1054you did not run `sensors-detect' as root.  Run the script 
    10701055`prog/mkdev/mkdev.sh' to create the `/dev/i2c-x' files.  Run `devfs' in 
    10711056the kernel to get the `/dev/i2c/x' files. 
    … …  
    10741059----------------------------------------------- 
    10751060 
    1076    Either 
     1061Either 
    10771062  1. The board doesn't have any sensors. 
    10781063 
    … …  
    10991084============================================ 
    11001085 
    1101    These are errors from the libsensors library in reading the 
     1086These are errors from the libsensors library in reading the 
    11021087`/etc/sensors.conf' configuration file. Go to that line number and fix 
    11031088it. If you have a parse error, perhaps you have to put the feature name 
    … …  
    11071092==================================================================== 
    11081093 
    1109    If `sensors' only says this, for example, and doesn't provide any 
     1094If `sensors' only says this, for example, and doesn't provide any 
    11101095actual data at all: 
    11111096 
    … …  
    11381123==================================================== 
    11391124 
    1140    *Note Sensors-detect doesnt work at all: Section 4.24, if 
     1125*Note Sensors-detect doesnt work at all: Section 4.24, if 
    11411126`sensors-detect' failed to find any sensors. 
    11421127 
    … …  
    11511136===================================== 
    11521137 
    1153    There are several possible causes: 
     1138There are several possible causes: 
    11541139  1. Bus driver problems. Insert the bus driver first, before you have 
    11551140     inserted any chip drivers, to verify. 
    … …  
    11791164========================================== 
    11801165 
    1181    Generally this is caused by an overtemperature alarm output from the 
     1166Generally this is caused by an overtemperature alarm output from the 
    11821167sensor chip. This triggers hardware on the board which automatically 
    11831168slows down the CPU clock. Be sure that your temperature limits are 
    … …  
    11881173======================================== 
    11891174 
    1190    The following boards have unique problems and solutions. 
     1175The following boards have unique problems and solutions. 
    11911176 
    119211774.31.1 Asus P4B 
    11931178--------------- 
    11941179 
    1195    See `prog/hotplug/README.p4b' if your SMBus master is not found. 
     1180See `prog/hotplug/README.p4b' if your SMBus master is not found. 
    11961181 
    119711824.31.2 Tyan 2460, 2462 
    11981183---------------------- 
    11991184 
    1200    See support tickets 805, 765, 781, 812, 813, and 867 for information. 
     1185See support tickets 805, 765, 781, 812, 813, and 867 for information. 
    12011186 
    120211874.31.3 Tyan 2466 
    12031188---------------- 
    12041189 
    1205    See support tickets 941, 840, and 841 for information. 
     1190See support tickets 941, 840, and 841 for information. 
    12061191 
    120711924.31.4 Tyan 2688 
    12081193---------------- 
    12091194 
    1210    For board hangs, see support ticket 721 for information.  Also *Note 
     1195For board hangs, see support ticket 721 for information.  Also *Note 
    12111196Inserting modules hangs my board: Section 4.29. 
    12121197 
    … …  
    12141199=================================== 
    12151200 
    1216    For IBM systems, see `README.thinkpad'. 
     1201For IBM systems, see `README.thinkpad'. 
    12171202 
    121812034.33 Problems on 2.6 kernels 
    12191204============================ 
    12201205 
    1221    Not all drivers have been ported to 2.6. If your favorite driver is 
    1222 not in 2.6, the reason is that nobody has ported it.  Please don't 
    1223 bother asking us why it is not in 2.6.  If you would like to port the 
    1224 driver, see the file Documentation/i2c/porting-clients in the 2.6 
    1225 kernel tree for help, then send us the ported driver when you are done. 
     1206Not all drivers have been ported to 2.6. If your favorite driver is not 
     1207in 2.6, the reason is that nobody has ported it.  Please don't bother 
     1208asking us why it is not in 2.6.  If you would like to port the driver, 
     1209see the file Documentation/i2c/porting-clients in the 2.6 kernel tree 
     1210for help, then send us the ported driver when you are done. 
    12261211 
    122712125 How to Ask for Help 
    … …  
    12311216======================================== 
    12321217 
    1233    We are always willing to answer questions if things don't work out. 
     1218We are always willing to answer questions if things don't work out. 
    12341219Please email <sensors@stimpy.netroedge.com>, and not the individual 
    12351220authors, unless you have something private to say. 
    … …  
    12771262======================================== 
    12781263 
    1279    Did you use `modprobe' instead of `insmod'??? Don't use insmod. 
     1264Did you use `modprobe' instead of `insmod'??? Don't use insmod. 
    12801265 
    12811266   Were there unresolved symbols? Did you run `depmod -a'? Run `depmod 
    … …  
    12891274================================================== 
    12901275 
    1291    For an ISA sensor chip, did you also `modprobe i2c-isa'? It must be 
     1276For an ISA sensor chip, did you also `modprobe i2c-isa'? It must be 
    12921277inserted. 
    12931278 
    … …  
    13021287================================================ 
    13031288 
    1304    It may be that this was a mis-detection: the chip may not be 
    1305 present. If you are convinced there is something wrong, verify that you 
    1306 indeed have the devices on your motherboard that you think you do. 
    1307 Look at the motherboard and make sure. If you are still stuck, please 
    1308 send us the usual information (*note Help::) 
     1289It may be that this was a mis-detection: the chip may not be present. 
     1290If you are convinced there is something wrong, verify that you indeed 
     1291have the devices on your motherboard that you think you do.  Look at 
     1292the motherboard and make sure. If you are still stuck, please send us 
     1293the usual information (*note Help::) 
    13091294 
    131012955.5 What to do if you have other problems? 
    13111296========================================== 
    13121297 
    1313    Again, send the output listed above. 
     1298Again, send the output listed above. 
    13141299 
    131513005.6 What if it just works like a charm? 
    13161301======================================= 
    13171302 
    1318    Drop us a mail if you feel like it, mentioning the mainboard and 
     1303Drop us a mail if you feel like it, mentioning the mainboard and 
    13191304detected chip type. That way, we have some positive feedback, too! 
    13201305 
    … …  
    13221307============================= 
    13231308 
    1324    You can't. Only developers can. Follow up by emailing us at 
     1309You can't. Only developers can. Follow up by emailing us at 
    13251310<sensors@stimpy.netroedge.com> and reference your ticket number in the 
    13261311subject. Please don't enter a new ticket with follow-up information, 
    … …  
    13301315=================================== 
    13311316 
    1332    Follow up by emailing us at <sensors@stimpy.netroedge.com> and 
     1317Follow up by emailing us at <sensors@stimpy.netroedge.com> and 
    13331318reference your ticket number in the subject. 
    13341319 
    … …  
    13391324========================= 
    13401325 
    1341    See `doc/developers/new_drivers' in our package for instructions. 
     1326See `doc/developers/new_drivers' in our package for instructions. 
    13421327 
    134313286.2 How to get CVS access 
    13441329========================= 
    13451330 
    1346    For anonymous CVS read access, see the instructions on our download 
     1331For anonymous CVS read access, see the instructions on our download 
    13471332page.  Sorry, we don't have automatically generated CVS tarballs. 
    13481333 
    … …  
    13541339========================================= 
    13551340 
    1356    Send us email <sensors@stimpy.netroedge.com>. 
     1341Send us email <sensors@stimpy.netroedge.com>. 
    13571342 
    135813436.4 How to join the project mailing list 
    13591344======================================== 
    13601345 
    1361    Send us email <sensors@stimpy.netroedge.com>. Sorry, there is no 
     1346Send us email <sensors@stimpy.netroedge.com>. Sorry, there is no 
    13621347automated subscribe/unsubscribe service yet (but we're seriously 
    13631348thinking of switching to majordomo).  Please note that you do NOT need 
    … …  
    13691354======================================= 
    13701355 
    1371    The mailing list archive is at: 
     1356The mailing list archive is at: 
    13721357`http://archives.andrew.net.au/lm-sensors' Sorry, it only contains 
    13731358messages since October 28, 2001. 
    … …  
    13761361========================= 
    13771362 
    1378    Check out the latest from CVS, then copy the directory to another 
     1363Check out the latest from CVS, then copy the directory to another 
    13791364directory, and make your changes. Generate the diff with `diff -u2 -r 
    13801365DIR1 DIR2'. Or you can generate the diff in CVS with `cvs diff -u2'. 
    … …  
    13841369====================== 
    13851370 
    1386    Believe it or not, what we really need help with are: 
     1371Believe it or not, what we really need help with are: 
    13871372   * Answering email 
    13881373 
    … …  
    14011386==================================== 
    14021387 
    1403    We don't have a separate release announcement mailing list; however, 
    1404 we put all our releases on freshmeat: `http://freshmeat.net' and you 
    1405 can register on our freshmeat project page 
     1388We don't have a separate release announcement mailing list; however, we 
     1389put all our releases on freshmeat: `http://freshmeat.net' and you can 
     1390register on our freshmeat project page 
    14061391`http://freshmeat.net/projects/lm_sensors' to 'subscribe to new 
    14071392releases' and then freshmeat will email you announcement. 
    … …  
    14101395================================================= 
    14111396 
    1412    Sorry, we know the spam is a hassle.  It would be nice to have a 
     1397Sorry, we know the spam is a hassle.  It would be nice to have a 
    14131398moderator who can screen everything, but that takes too much time and 
    14141399delays emails.  Right now there is a procmail script which tags likely 
    … …  
    14231408****************************** 
    14241409 
    1425    Note: Version 1 is very very old and is not recommended. 
     1410Note: Version 1 is very very old and is not recommended. 
    14261411 
    142714127.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it.  What's wrong? 
    14281413====================================================================================================================== 
    14291414 
    1430    Currently, our code only assumes that an SMBus exists if it 
    1431 originates from the Intel PIIX4 (82371AB).  If your computer doesn't 
    1432 have one, or if your SMBus originates from a different SMBus 'host', 
    1433 then you are out of luck. :'( Our experience is, though, that most 
    1434 machines have a PIIX4, and that it is where the SMBus is hosted. 
     1415Currently, our code only assumes that an SMBus exists if it originates 
     1416from the Intel PIIX4 (82371AB).  If your computer doesn't have one, or 
     1417if your SMBus originates from a different SMBus 'host', then you are 
     1418out of luck. :'( Our experience is, though, that most machines have a 
     1419PIIX4, and that it is where the SMBus is hosted. 
    14351420 
    14361421   Regarding the VIA chip set(s): 
    … …  
    14511436======================================================== 
    14521437 
    1453    This should no longer be an issue in 1.4.10 and later; it will 
    1454 continue loading, but it won't support SMBus-connected devices, of 
    1455 course. 
     1438This should no longer be an issue in 1.4.10 and later; it will continue 
     1439loading, but it won't support SMBus-connected devices, of course. 
    14561440 
    145714417.3 I try to read `/proc/sensors', and I get a "No sensor data yet (try again in a few moments)" message. Why? 
    14581442============================================================================================================== 
    14591443 
    1460    It takes about 1.5 seconds for the LM78 to update all its sensor 
     1444It takes about 1.5 seconds for the LM78 to update all its sensor 
    14611445values.  If we would try to read it before it finished that, you would 
    14621446get old garbage instead. So you have to wait 1.5 seconds after the 
    … …  
    14701454=========================================================== 
    14711455 
    1472    This is a bug we have only observed on Dell computers. There is 
     1456This is a bug we have only observed on Dell computers. There is 
    14731457probably a problem with the way the SMBus is accessed; but it is not yet 
    14741458clear whether the problem is in our code or with the Dells. 
    … …  
    15291513 
    15301514   * Rev 1.0 Written by Philip Edelbrock, 19980803 
     1515 

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

    r2447 r2450  
    33<title>Sensors FAQ for lm_sensors version 2.12</title> 
    44<meta http-equiv="Content-Type" content="text/html"> 
    5 <meta name=description content="Sensors FAQ for lm_sensors version 2.12"> 
    6 <meta name=generator content="makeinfo 4.2"> 
    7 <link href="http://www.gnu.org/software/texinfo/" rel=generator-home> 
     5<meta name="description" content="Sensors FAQ for lm_sensors version 2.12"> 
     6<meta name="generator" content="makeinfo 4.7"> 
     7<link title="Top" rel="top" href="#Top"> 
     8<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> 
     9<meta http-equiv="Content-Style-Type" content="text/css"> 
     10<style type="text/css"><!-- 
     11  pre.display { font-family:inherit } 
     12  pre.format  { font-family:inherit } 
     13  pre.smalldisplay { font-family:inherit; font-size:smaller } 
     14  pre.smallformat  { font-family:inherit; font-size:smaller } 
     15  pre.smallexample { font-size:smaller } 
     16  pre.smalllisp    { font-size:smaller } 
     17  span.sc { font-variant:small-caps } 
     18  span.roman { font-family: serif; font-weight: normal; }  
     19--></style> 
    820</head> 
    921<body> 
    10 <h1>Sensors FAQ for lm_sensors version 2.12</h1> 
     22<h1 class="settitle">Sensors FAQ for lm_sensors version 2.12</h1> 
    1123Copyright (C) 1998 - 2004<br> 
    1224Frodo Looijaard,<br> 
    … …  
    1527<a href="mailto:mdsxyz123@yahoo.com">Mark Studebaker</a><br> 
    1628 
    17  
     29   <div class="shortcontents"> 
    1830<h2>Short Contents</h2> 
    1931<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<li><a href="#toc_Top">lm_sensors</a></li> 
     33<li><a href="#toc_Overview">1 PC and Sensor Overview</a></li> 
     34<li><a href="#toc_Basics">2 Sensor and Bus Basics</a></li> 
     35<li><a href="#toc_Installation">3 Installation and Management</a></li> 
     36<li><a href="#toc_Problems">4 Problems</a></li> 
     37<li><a href="#toc_Help">5 How to Ask for Help</a></li> 
     38<li><a href="#toc_Contribute">6 How to Contribute</a></li> 
     39<li><a href="#toc_Version-1-Specifics">7 Version 1 Specific Questions</a></li> 
     40<li><a href="#toc_Document-Revisions">Appendix A Revision History of This Document</a></li> 
     41</ul> 
     42</div> 
     43 
     44   <div class="contents"> 
    3245<h2>Table of Contents</h2> 
    3346<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> 
     47<li><a name="toc_Top" href="#Top">lm_sensors</a> 
     48<li><a name="toc_Overview" href="#Overview">1 PC and Sensor Overview</a> 
    3849<ul> 
    39 <li><a href="#Section%201.1">1.1 What sensors are available on my PC?</a> 
    40 <li><a href="#Section%201.2">1.2 What can a sensor chip like the "LM78" do?</a> 
    41 <li><a href="#Section%201.3">1.3 Where do I find out more about any of these chips?</a> 
    42 </ul> 
    43 <li><a name="toc_Basics"></a> 
    44     <a href="#Basics">2 Sensor and Bus Basics</a> 
     50<li><a href="#Section-1_002e1">1.1 What sensors are available on my PC?</a> 
     51<li><a href="#Section-1_002e2">1.2 What can a sensor chip like the "LM78" do?</a> 
     52<li><a href="#Section-1_002e3">1.3 Where do I find out more about any of these chips?</a> 
     53</li></ul> 
     54<li><a name="toc_Basics" href="#Basics">2 Sensor and Bus Basics</a> 
    4555<ul> 
    46 <li><a href="#Section%202.1">2.1 How are these sensors read?</a> 
    47 <li><a href="#Section%202.2">2.2 What is the SMBus? And the I2C bus?</a> 
    48 <li><a href="#Section%202.3">2.3 I don't have an ISA bus!</a> 
    49 <li><a href="#Section%202.4">2.4 What sensors do processors have?</a> 
    50 <li><a href="#Section%202.5">2.5 How often are the sensor values updated?</a> 
    51 <li><a href="#Section%202.6">2.6 How are alarms triggered?</a> 
    52 </ul> 
    53 <li><a name="toc_Installation"></a> 
    54     <a href="#Installation">3 Installation and Management</a> 
     56<li><a href="#Section-2_002e1">2.1 How are these sensors read?</a> 
     57<li><a href="#Section-2_002e2">2.2 What is the SMBus? And the I2C bus?</a> 
     58<li><a href="#Section-2_002e3">2.3 I don't have an ISA bus!</a> 
     59<li><a href="#Section-2_002e4">2.4 What sensors do processors have?</a> 
     60<li><a href="#Section-2_002e5">2.5 How often are the sensor values updated?</a> 
     61<li><a href="#Section-2_002e6">2.6 How are alarms triggered?</a> 
     62</li></ul> 
     63<li><a name="toc_Installation" href="#Installation">3 Installation and Management</a> 
    5564<ul> 
    56 <li><a href="#Section%203.1">3.1 Why so many modules, and how do I cope with them?</a> 
    57 <li><a href="#Section%203.2">3.2 How do I know which chips I own?</a> 
     65<li><a href="#Section-3_002e1">3.1 Why so many modules, and how do I cope with them?</a> 
     66<li><a href="#Section-3_002e2">3.2 How do I know which chips I own?</a> 
    5867<ul> 
    59 <li><a href="#Section%203.2">3.2.1 What chips are on motherboard XYZ?</a> 
    60 <li><a href="#Section%203.2">3.2.2 Do you support motherboard XYZ?</a> 
    61 <li><a href="#Section%203.2">3.2.3 Do you support chip XYZ?</a> 
    62 <li><a href="#Section%203.2">3.2.4 Anybody working on a driver for chip XYZ?</a> 
    63 </ul> 
    64 <li><a href="#Section%203.3">3.3 Which modules should I insert?</a> 
    65 <li><a href="#Section%203.4">3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</a> 
     68<li><a href="#Section-3_002e2">3.2.1 What chips are on motherboard XYZ?</a> 
     69<li><a href="#Section-3_002e2">3.2.2 Do you support motherboard XYZ?</a> 
     70<li><a href="#Section-3_002e2">3.2.3 Do you support chip XYZ?</a> 
     71<li><a href="#Section-3_002e2">3.2.4 Anybody working on a driver for chip XYZ?</a> 
     72</li></ul> 
     73<li><a href="#Section-3_002e3">3.3 Which modules should I insert?</a> 
     74<li><a href="#Section-3_002e4">3.4 Do I need the configuration file <span class="file">/etc/sensors.conf</span>?</a> 
    6675<ul> 
    67 <li><a href="#Section%203.4">3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</a> 
    68 <li><a href="#Section%203.4">3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</a> 
    69 <li><a href="#Section%203.4">3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</a> 
    70 <li><a href="#Section%203.4">3.4.4 One sensor isn't hooked up on my board!</a> 
    71 <li><a href="#Section%203.4">3.4.5 I need help with <code>sensors.conf</code>!</a> 
    72 <li><a href="#Section%203.4">3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</a> 
    73 </ul> 
    74 <li><a href="#Section%203.5">3.5 What about the <code>No such file or directory</code> warnings when I compile?</a> 
    75 <li><a href="#Section%203.6">3.6 I get all kinds of weird compilation errors?</a> 
     76<li><a href="#Section-3_002e4">3.4.1 The labels for the voltage and temperature readings in <span class="command">sensors</span> are incorrect!</a> 
     77<li><a href="#Section-3_002e4">3.4.2 The min and max for the readings in <span class="command">sensors</span> are incorrect!</a> 
     78<li><a href="#Section-3_002e4">3.4.3 The min and max settings in <span class="file">/etc/sensors.conf</span> didn't take effect!</a> 
     79<li><a href="#Section-3_002e4">3.4.4 One sensor isn't hooked up on my board!</a> 
     80<li><a href="#Section-3_002e4">3.4.5 I need help with <span class="file">sensors.conf</span>!</a> 
     81<li><a href="#Section-3_002e4">3.4.6 Do you have a database of <span class="file">sensors.conf</span> entries for specific boards?</a> 
     82</li></ul> 
     83<li><a href="#Section-3_002e5">3.5 What about the <span class="samp">No such file or directory</span> warnings when I compile?</a> 
     84<li><a href="#Section-3_002e6">3.6 I get all kinds of weird compilation errors?</a> 
    7685<ul> 
    77 <li><a href="#Section%203.6">3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</a> 
    78 </ul> 
    79 <li><a href="#Section%203.7">3.7 It still does not compile or patch!</a> 
    80 <li><a href="#Section%203.8">3.8 <code>make install</code> fails on Mandrake kernels</a> 
    81 <li><a href="#Section%203.9">3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</a> 
    82 <li><a href="#Section%203.10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a> 
    83 </ul> 
    84 <li><a name="toc_Problems"></a> 
    85     <a href="#Problems">4 Problems</a> 
     86<li><a href="#Section-3_002e6">3.6.1 <span class="samp">No rule to make target xxxx needed by xxxx</span> - how to fix?</a> 
     87</li></ul> 
     88<li><a href="#Section-3_002e7">3.7 It still does not compile or patch!</a> 
     89<li><a href="#Section-3_002e8">3.8 <span class="command">make install</span> fails on Mandrake kernels</a> 
     90<li><a href="#Section-3_002e9">3.9 I get unresolved symbols when I <span class="command">modprobe</span> modules (Red Hat especially)</a> 
     91<li><a href="#Section-3_002e10">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</a> 
     92</li></ul> 
     93<li><a name="toc_Problems" href="#Problems">4 Problems</a> 
    8694<ul> 
    87 <li><a href="#Section%204.1">4.1 My fans report exactly half/double their values compared to the BIOS?</a> 
     95<li><a href="#Section-4_002e1">4.1 My fans report exactly half/double their values compared to the BIOS?</a> 
    8896<ul> 
    89 <li><a href="#Section%204.1">4.1.1 Fans sometimes/always read 0!!</a> 
    90 <li><a href="#Section%204.1">4.1.2 I doubled the fan divisor and the fan still reads 7000!</a> 
    91 </ul> 
    92 <li><a href="#Section%204.2">4.2 Why do my two LM75's report "-48 degrees"?</a> 
    93 <li><a href="#Section%204.3">4.3 Why do I have two Vcore readings, I have only one processor!</a> 
    94 <li><a href="#Section%204.4">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</a> 
    95 <li><a href="#Section%204.5">4.5 My voltage readings seem to drift a bit. Is something wrong?</a> 
    96 <li><a href="#Section%204.6">4.6 Some measurements are way out of range. What happened?</a> 
    97 <li><a href="#Section%204.7">4.7 What are VID lines? Why is the VID reading wrong?</a> 
    98 <li><a href="#Section%204.8">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</a> 
    99 <li><a href="#Section%204.9">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</a> 
    100 <li><a href="#Section%204.10">4.10 Can I be alerted when an ALARM occurs?</a> 
    101 <li><a href="#Section%204.11">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</a> 
    102 <li><a href="#Section%204.12">4.12 My BIOS reports a much higher CPU temperature than your modules!</a> 
    103 <li><a href="#Section%204.13">4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</a> 
    104 <li><a href="#Section%204.14">4.14 How do I set new limits?</a> 
     97<li><a href="#Section-4_002e1">4.1.1 Fans sometimes/always read 0!!</a> 
     98<li><a href="#Section-4_002e1">4.1.2 I doubled the fan divisor and the fan still reads 7000!</a> 
     99</li></ul> 
     100<li><a href="#Section-4_002e2">4.2 Why do my two LM75's report "-48 degrees"?</a> 
     101<li><a href="#Section-4_002e3">4.3 Why do I have two Vcore readings, I have only one processor!</a> 
     102<li><a href="#Section-4_002e4">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</a> 
     103<li><a href="#Section-4_002e5">4.5 My voltage readings seem to drift a bit. Is something wrong?</a> 
     104<li><a href="#Section-4_002e6">4.6 Some measurements are way out of range. What happened?</a> 
     105<li><a href="#Section-4_002e7">4.7 What are VID lines? Why is the VID reading wrong?</a> 
     106<li><a href="#Section-4_002e8">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</a> 
     107<li><a href="#Section-4_002e9">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</a> 
     108<li><a href="#Section-4_002e10">4.10 Can I be alerted when an ALARM occurs?</a> 
     109<li><a href="#Section-4_002e11">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</a> 
     110<li><a href="#Section-4_002e12">4.12 My BIOS reports a much higher CPU temperature than your modules!</a> 
     111<li><a href="#Section-4_002e13">4.13 I try to read the raw <span class="file">/proc</span> files, but the values are strange?!?</a> 
     112<li><a href="#Section-4_002e14">4.14 How do I set new limits?</a> 
    105113<ul> 
    106 <li><a href="#Section%204.14">4.14.1 I set new limits and it didn't work?</a> 
    107 </ul> 
    108 <li><a href="#Section%204.15">4.15 Some sensors are doubly detected?</a> 
    109 <li><a href="#Section%204.16">4.16 I ran sensors-detect, but now I get very strange readings?!?</a> 
    110 <li><a href="#Section%204.17">4.17 Bad readings from particular chips</a> 
     114<li><a href="#Section-4_002e14">4.14.1 I set new limits and it didn't work?</a> 
     115</li></ul> 
     116<li><a href="#Section-4_002e15">4.15 Some sensors are doubly detected?</a> 
     117<li><a href="#Section-4_002e16">4.16 I ran sensors-detect, but now I get very strange readings?!?</a> 
     118<li><a href="#Section-4_002e17">4.17 Bad readings from particular chips</a> 
    111119<ul> 
    112 <li><a href="#Section%204.17">4.17.1 Bad readings from the AS99127F!</a> 
    113 <li><a href="#Section%204.17">4.17.2 Bad readings from the VIA 686A!</a> 
    114 <li><a href="#Section%204.17">4.17.3 Bad readings from the MTP008!</a> 
    115 <li><a href="#Section%204.17">4.17.4 Bad temperature readings from the SIS5595!</a> 
    116 <li><a href="#Section%204.17">4.17.5 Bad readings from a w8378[12]d!</a> 
    117 <li><a href="#Section%204.17">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</a> 
    118 <li><a href="#Section%204.17">4.17.7 Bad readings from LM75!</a> 
    119 <li><a href="#Section%204.17">4.17.8 Bad readings from LM78!</a> 
    120 <li><a href="#Section%204.17">4.17.9 Bad readings from LM80!</a> 
    121 <li><a href="#Section%204.17">4.17.10 Bad readings from it87!</a> 
    122 </ul> 
    123 <li><a href="#Section%204.18">4.18 How do I configure two chips (LM87) differently?</a> 
    124 <li><a href="#Section%204.19">4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</a> 
     120<li><a href="#Section-4_002e17">4.17.1 Bad readings from the AS99127F!</a> 
     121<li><a href="#Section-4_002e17">4.17.2 Bad readings from the VIA 686A!</a> 
     122<li><a href="#Section-4_002e17">4.17.3 Bad readings from the MTP008!</a> 
     123<li><a href="#Section-4_002e17">4.17.4 Bad temperature readings from the SIS5595!</a> 
     124<li><a href="#Section-4_002e17">4.17.5 Bad readings from a w8378[12]d!</a> 
     125<li><a href="#Section-4_002e17">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</a> 
     126<li><a href="#Section-4_002e17">4.17.7 Bad readings from LM75!</a> 
     127<li><a href="#Section-4_002e17">4.17.8 Bad readings from LM78!</a> 
     128<li><a href="#Section-4_002e17">4.17.9 Bad readings from LM80!</a> 
     129<li><a href="#Section-4_002e17">4.17.10 Bad readings from it87!</a> 
     130</li></ul> 
     131<li><a href="#Section-4_002e18">4.18 How do I configure two chips (LM87) differently?</a> 
     132<li><a href="#Section-4_002e19">4.19 Dmesg says <span class="samp">Upgrade BIOS</span>! I don't want to!</a> 
    125133<ul> 
    126 <li><a href="#Section%204.19">4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</a> 
    127 </ul> 
    128 <li><a href="#Section%204.20">4.20 Sensors says <code>Can't access procfs/sysfs file</code></a> 
    129 <li><a href="#Section%204.21">4.21 Sensors says <code>No sensors found!</code></a> 
    130 <li><a href="#Section%204.22">4.22 Sensors output is not correct!</a> 
    131 <li><a href="#Section%204.23">4.23 What is at I2C address XXX?</a> 
     134<li><a href="#Section-4_002e19">4.19.1 Dmesg says <span class="samp">use force_addr=0xaddr</span>! What address do I use?</a> 
     135</li></ul> 
     136<li><a href="#Section-4_002e20">4.20 Sensors says <span class="samp">Can't access procfs/sysfs file</span></a> 
     137<li><a href="#Section-4_002e21">4.21 Sensors says <span class="samp">No sensors found!</span></a> 
     138<li><a href="#Section-4_002e22">4.22 Sensors output is not correct!</a> 
     139<li><a href="#Section-4_002e23">4.23 What is at I2C address XXX?</a> 
    132140<ul> 
    133 <li><a href="#Section%204.23">4.23.1 What is at I2C address 0x69?</a> 
    134 <li><a href="#Section%204.23">4.23.2 What is at I2C addresses 0x50 - 0x57?</a> 
    135 <li><a href="#Section%204.23">4.23.3 What is at I2C addresses 0x30 - 0x37?</a> 
    136 </ul> 
    137 <li><a href="#Section%204.24">4.24 Sensors-detect doesn't work at all</a> 
     141<li><a href="#Section-4_002e23">4.23.1 What is at I2C address 0x69?</a> 
     142<li><a href="#Section-4_002e23">4.23.2 What is at I2C addresses 0x50 - 0x57?</a> 
     143<li><a href="#Section-4_002e23">4.23.3 What is at I2C addresses 0x30 - 0x37?</a> 
     144</li></ul> 
     145<li><a href="#Section-4_002e24">4.24 Sensors-detect doesn't work at all</a> 
    138146<ul> 
    139 <li><a href="#Section%204.24">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</a> 
    140 <li><a href="#Section%204.24">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</a> 
    141 <li><a href="#Section%204.24">4.24.3 Sensors-detect doesn't find any sensors!</a> 
    142 </ul> 
    143 <li><a href="#Section%204.25">4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></a> 
    144 <li><a href="#Section%204.26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a> 
    145 <li><a href="#Section%204.27">4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></a> 
    146 <li><a href="#Section%204.28">4.28 Sensors doesn't find any sensors, just eeproms.</a> 
    147 <li><a href="#Section%204.29">4.29 Inserting modules hangs my board</a> 
    148 <li><a href="#Section%204.30">4.30 Inserting modules slows down my board</a> 
    149 <li><a href="#Section%204.31">4.31 Problems on particular motherboards</a> 
     147<li><a href="#Section-4_002e24">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</a> 
     148<li><a href="#Section-4_002e24">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</a> 
     149<li><a href="#Section-4_002e24">4.24.3 Sensors-detect doesn't find any sensors!</a> 
     150</li></ul> 
     151<li><a href="#Section-4_002e25">4.25 Sensors says <span class="samp">Error: Line xxx: zzzzzzz</span></a> 
     152<li><a href="#Section-4_002e26">4.26 Sensors only gives the name, adapter, and algorithm for my chip</a> 
     153<li><a href="#Section-4_002e27">4.27 Sensors says <span class="samp">ERROR: Can't get xxxxx data!</span></a> 
     154<li><a href="#Section-4_002e28">4.28 Sensors doesn't find any sensors, just eeproms.</a> 
     155<li><a href="#Section-4_002e29">4.29 Inserting modules hangs my board</a> 
     156<li><a href="#Section-4_002e30">4.30 Inserting modules slows down my board</a> 
     157<li><a href="#Section-4_002e31">4.31 Problems on particular motherboards</a> 
    150158<ul> 
    151 <li><a href="#Section%204.31">4.31.1 Asus P4B</a> 
    152 <li><a href="#Section%204.31">4.31.2 Tyan 2460, 2462</a> 
    153 <li><a href="#Section%204.31">4.31.3 Tyan 2466</a> 
    154 <li><a href="#Section%204.31">4.31.4 Tyan 2688</a> 
    155 </ul> 
    156 <li><a href="#Section%204.32">4.32 Problems on particular systems</a> 
    157 <li><a href="#Section%204.33">4.33 Problems on 2.6 kernels</a> 
    158 </ul> 
    159 <li><a name="toc_Help"></a> 
    160     <a href="#Help">5 How to Ask for Help</a> 
     159<li><a href="#Section-4_002e31">4.31.1 Asus P4B</a> 
     160<li><a href="#Section-4_002e31">4.31.2 Tyan 2460, 2462</a> 
     161<li><a href="#Section-4_002e31">4.31.3 Tyan 2466</a> 
     162<li><a href="#Section-4_002e31">4.31.4 Tyan 2688</a> 
     163</li></ul> 
     164<li><a href="#Section-4_002e32">4.32 Problems on particular systems</a> 
     165<li><a href="#Section-4_002e33">4.33 Problems on 2.6 kernels</a> 
     166</li></ul> 
     167<li><a name="toc_Help" href="#Help">5 How to Ask for Help</a> 
    161168<ul> 
    162 <li><a href="#Section%205.1">5.1 What to send us when asking for help</a> 
    163 <li><a href="#Section%205.2">5.2 What to do if a module won't insert?</a> 
    164 <li><a href="#Section%205.3">5.3 What to do if it inserts, but nothing happens?</a> 
    165 <li><a href="#Section%205.4">5.4 What to do if I read only bogus information?</a> 
    166 <li><a href="#Section%205.5">5.5 What to do if you have other problems?</a> 
    167 <li><a href="#Section%205.6">5.6 What if it just works like a charm?</a> 
    168 <li><a href="#Section%205.7">5.7 How do I update a ticket?</a> 
    169 <li><a href="#Section%205.8">5.8 How do I follow up on a ticket?</a> 
    170 </ul> 
    171 <li><a name="toc_Contribute"></a> 
    172     <a href="#Contribute">6 How to Contribute</a> 
     169<li><a href="#Section-5_002e1">5.1 What to send us when asking for help</a> 
     170<li><a href="#Section-5_002e2">5.2 What to do if a module won't insert?</a> 
     171<li><a href="#Section-5_002e3">5.3 What to do if it inserts, but nothing happens?</a> 
     172<li><a href="#Section-5_002e4">5.4 What to do if I read only bogus information?</a> 
     173<li><a href="#Section-5_002e5">5.5 What to do if you have other problems?</a> 
     174<li><a href="#Section-5_002e6">5.6 What if it just works like a charm?</a> 
     175<li><a href="#Section-5_002e7">5.7 How do I update a ticket?</a> 
     176<li><a href="#Section-5_002e8">5.8 How do I follow up on a ticket?</a> 
     177</li></ul> 
     178<li><a name="toc_Contribute" href="#Contribute">6 How to Contribute</a> 
    173179<ul> 
    174 <li><a href="#Section%206.1">6.1 How to write a driver</a> 
    175 <li><a href="#Section%206.2">6.2 How to get CVS access</a> 
    176 <li><a href="#Section%206.3">6.3 How to donate hardware to the project</a> 
    177 <li><a href="#Section%206.4">6.4 How to join the project mailing list</a> 
    178 <li><a href="#Section%206.5">6.5 How to access mailing list archives</a> 
    179 <li><a href="#Section%206.6">6.6 How to submit a patch</a> 
    180 <li><a href="#Section%206.7">6.7 How to REALLY help</a> 
    181 <li><a href="#Section%206.8">6.8 How to get release announcements</a> 
    182 <li><a href="#Section%206.9">6.9 How to block spam on the project mailing list</a> 
    183 </ul> 
    184 <li><a name="toc_Version%201%20Specifics"></a> 
    185     <a href="#Version%201%20Specifics">7 Version 1 Specific Questions</a> 
     180<li><a href="#Section-6_002e1">6.1 How to write a driver</a> 
     181<li><a href="#Section-6_002e2">6.2 How to get CVS access</a> 
     182<li><a href="#Section-6_002e3">6.3 How to donate hardware to the project</a> 
     183<li><a href="#Section-6_002e4">6.4 How to join the project mailing list</a> 
     184<li><a href="#Section-6_002e5">6.5 How to access mailing list archives</a> 
     185<li><a href="#Section-6_002e6">6.6 How to submit a patch</a> 
     186<li><a href="#Section-6_002e7">6.7 How to REALLY help</a> 
     187<li><a href="#Section-6_002e8">6.8 How to get release announcements</a> 
     188<li><a href="#Section-6_002e9">6.9 How to block spam on the project mailing list</a> 
     189</li></ul> 
     190<li><a name="toc_Version-1-Specifics" href="#Version-1-Specifics">7 Version 1 Specific Questions</a> 
    186191<ul> 
    187 <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> 
    188 <li><a href="#Section%207.2">7.2 The modules won't load, saying 'SMBus not detected'.</a> 
    189 <li><a href="#Section%207.3">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?</a> 
    190 <li><a href="#Section%207.4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a> 
    191 </ul> 
    192 <li><a name="toc_Document%20Revisions"></a> 
    193     <a href="#Document%20Revisions">Appendix A Revision History of This Document</a> 
    194 </ul> 
    195  
    196 <p><hr> 
    197 Node:<a name="Top">Top</a>, 
    198 Next:<a rel=next accesskey=n href="#Overview">Overview</a>, 
    199 Up:<a rel=up accesskey=u href="#dir">(dir)</a> 
    200 <br> 
    201  
    202 <h2>lm_sensors</h2> 
     192<li><a href="#Section-7_002e1">7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it.  What's wrong?</a> 
     193<li><a href="#Section-7_002e2">7.2 The modules won't load, saying 'SMBus not detected'.</a> 
     194<li><a href="#Section-7_002e3">7.3 I try to read <span class="file">/proc/sensors</span>, and I get a "No sensor data yet (try again in a few moments)" message. Why?</a> 
     195<li><a href="#Section-7_002e4">7.4 On my Dell, a LM80 is detected, but all readings are 0!</a> 
     196</li></ul> 
     197<li><a name="toc_Document-Revisions" href="#Document-Revisions">Appendix A Revision History of This Document</a> 
     198</li></ul> 
     199</div> 
     200 
     201<div class="node"> 
     202<p><hr> 
     203<a name="Top"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Overview">Overview</a>, 
     204Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a> 
     205<br> 
     206</div> 
     207 
     208<h2 class="unnumbered">lm_sensors</h2> 
    203209 
    204210<p>The lm_sensors package includes a collection of modules for general SMBus 
    … …  
    206212is not in standard 2.2-vintage kernels. 
    207213 
    208 <ul> 
    209 <li><a accesskey=1 href="#Overview">Overview</a>:                 PC and Sensor Overview 
    210 <li><a accesskey=2 href="#Basics">Basics</a>:                   Sensor and Bus Basics 
    211 <li><a accesskey=3 href="#Installation">Installation</a>:             Installation and Management 
    212 <li><a accesskey=4 href="#Problems">Problems</a>:                 Problems 
    213 <li><a accesskey=5 href="#Help">Help</a>:                     How to Ask for Help 
    214 <li><a accesskey=6 href="#Contribute">Contribute</a>:               How to Contribute 
    215 <li><a accesskey=7 href="#Version%201%20Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
    216 <li><a accesskey=8 href="#Document%20Revisions">Document Revisions</a>:       Revision History of This Document 
    217 </ul> 
    218  
    219 <p><hr> 
    220 Node:<a name="Overview">Overview</a>, 
    221 Next:<a rel=next accesskey=n href="#Basics">Basics</a>, 
    222 Previous:<a rel=previous accesskey=p href="#Top">Top</a>, 
    223 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    224 <br> 
    225  
    226 <h2>1 PC and Sensor Overview</h2> 
    227  
    228 <ul> 
    229 <li><a accesskey=1 href="#Section%201.1">Section 1.1</a>:              What sensors are available on my PC?  
    230 <li><a accesskey=2 href="#Section%201.2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
    231 <li><a accesskey=3 href="#Section%201.3">Section 1.3</a>:              Where do I find out more about any of these chips?  
    232 </ul> 
    233  
    234 <p><hr> 
    235 Node:<a name="Section%201.1">Section 1.1</a>, 
    236 Next:<a rel=next accesskey=n href="#Section%201.2">Section 1.2</a>, 
    237 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    238 <br> 
    239  
    240 <h3>1.1 What sensors are available on my PC?</h3> 
     214<ul class="menu"> 
     215<li><a accesskey="1" href="#Overview">Overview</a>:                 PC and Sensor Overview 
     216<li><a accesskey="2" href="#Basics">Basics</a>:                   Sensor and Bus Basics 
     217<li><a accesskey="3" href="#Installation">Installation</a>:             Installation and Management 
     218<li><a accesskey="4" href="#Problems">Problems</a>:                 Problems 
     219<li><a accesskey="5" href="#Help">Help</a>:                     How to Ask for Help 
     220<li><a accesskey="6" href="#Contribute">Contribute</a>:               How to Contribute 
     221<li><a accesskey="7" href="#Version-1-Specifics">Version 1 Specifics</a>:      Version 1 Specific Questions 
     222<li><a accesskey="8" href="#Document-Revisions">Document Revisions</a>:       Revision History of This Document 
     223</ul> 
     224 
     225<div class="node"> 
     226<p><hr> 
     227<a name="Overview"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Basics">Basics</a>, 
     228Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>, 
     229Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     230<br> 
     231</div> 
     232 
     233<h2 class="chapter">1 PC and Sensor Overview</h2> 
     234 
     235<ul class="menu"> 
     236<li><a accesskey="1" href="#Section-1_002e1">Section 1.1</a>:              What sensors are available on my PC?  
     237<li><a accesskey="2" href="#Section-1_002e2">Section 1.2</a>:              What can a sensor chip like the "LM78" do?  
     238<li><a accesskey="3" href="#Section-1_002e3">Section 1.3</a>:              Where do I find out more about any of these chips?  
     239</ul> 
     240 
     241<div class="node"> 
     242<p><hr> 
     243<a name="Section-1_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e2">Section 1.2</a>, 
     244Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a> 
     245<br> 
     246</div> 
     247 
     248<h3 class="section">1.1 What sensors are available on my PC?</h3> 
    241249 
    242250<p>Most PC's built since late 1997 now come with a 
    … …  
    244252ISA bus or the SMBus, depending on the motherboard. 
    245253 
    246 <p>Some motherboard chipsets, notably the Via 686 and the SiS 5595, 
     254   <p>Some motherboard chipsets, notably the Via 686 and the SiS 5595, 
    247255contain hardware monitor functions. 
    248256 
    249 <p>This FAQ frequently refers to the "LM78". This chip has been 
     257   <p>This FAQ frequently refers to the "LM78". This chip has been 
    250258obsoleted by National Semiconductor. Most motherboards today contain 
    251259a chip with similar functions. 
    252260 
    253 <p><hr> 
    254 Node:<a name="Section%201.2">Section 1.2</a>, 
    255 Next:<a rel=next accesskey=n href="#Section%201.3">Section 1.3</a>, 
    256 Previous:<a rel=previous accesskey=p href="#Section%201.1">Section 1.1</a>, 
    257 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    258 <br> 
    259  
    260 <h3>1.2 What can a sensor chip like the "LM78" do?</h3> 
     261<div class="node"> 
     262<p><hr> 
     263<a name="Section-1_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-1_002e3">Section 1.3</a>, 
     264Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e1">Section 1.1</a>, 
     265Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a> 
     266<br> 
     267</div> 
     268 
     269<h3 class="section">1.2 What can a sensor chip like the "LM78" do?</h3> 
    261270 
    262271<p>The LM78 is a chip made by National Semiconductor which can monitor 7 
    … …  
    266275re-scaled appropriately by software. 
    267276 
    268 <p>The LM78 also has 3 fan speed monitoring inputs, an internal 
     277   <p>The LM78 also has 3 fan speed monitoring inputs, an internal 
    269278temperature sensor, a chassis intrusion sensor, and a couple maskable interrupt 
    270279inputs.  The LM78 can also relay the processor's (P6 or Pent II) VID lines 
    … …  
    273282the processor. 
    274283 
    275 <p>The LM78 can be interfaced to a system via the ISA bus and/or the 
     284   <p>The LM78 can be interfaced to a system via the ISA bus and/or the 
    276285SMBus. 
    277286 
    278 <p>Most other sensor chips have comparable functionality. Each supported 
    279 chip is documented in the <code>doc/chips</code> directory. 
    280  
    281 <p><hr> 
    282 Node:<a name="Section%201.3">Section 1.3</a>, 
    283 Previous:<a rel=previous accesskey=p href="#Section%201.2">Section 1.2</a>, 
    284 Up:<a rel=up accesskey=u href="#Overview">Overview</a> 
    285 <br> 
    286  
    287 <h3>1.3 Where do I find out more about any of these chips?</h3> 
     287   <p>Most other sensor chips have comparable functionality. Each supported 
     288chip is documented in the <span class="file">doc/chips</span> directory. 
     289 
     290<div class="node"> 
     291<p><hr> 
     292<a name="Section-1_002e3"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-1_002e2">Section 1.2</a>, 
     293Up:&nbsp;<a rel="up" accesskey="u" href="#Overview">Overview</a> 
     294<br> 
     295</div> 
     296 
     297<h3 class="section">1.3 Where do I find out more about any of these chips?</h3> 
    288298 
    289299<p>Most semiconductor companies have comprehensive documentation, 
    … …  
    292302of sensor chips. Their websites are: 
    293303 
    294 <ul> 
     304     <ul> 
    295305  <li><a href="http://www.analog.com">http://www.analog.com</a> 
    296306  <li><a href="http://www.dalsemi.com">http://www.dalsemi.com</a> 
    … …  
    299309</ul> 
    300310 
    301 <p>Please see the file <a href="http://www2.lm-sensors.nu/~lm78/useful_addresses.html">http://www2.lm-sensors.nu/~lm78/useful_addresses.html</a> 
     311   <p>Please see the file <a href="http://www2.lm-sensors.nu/~lm78/useful_addresses.html">http://www2.lm-sensors.nu/~lm78/useful_addresses.html</a> 
    302312for links to other companies' websites. 
    303313 
    304 <p><hr> 
    305 Node:<a name="Basics">Basics</a>, 
    306 Next:<a rel=next accesskey=n href="#Installation">Installation</a>, 
    307 Previous:<a rel=previous accesskey=p href="#Overview">Overview</a>, 
    308 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    309 <br> 
    310  
    311 <h2>2 Sensor and Bus Basics</h2> 
    312  
    313 <ul> 
    314 <li><a accesskey=1 href="#Section%202.1">Section 2.1</a>:              What sensors are available on my PC?  
    315 <li><a accesskey=2 href="#Section%202.2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
    316 <li><a accesskey=3 href="#Section%202.3">Section 2.3</a>:              Where do I find out more about any of these chips?  
    317 <li><a accesskey=4 href="#Section%202.4">Section 2.4</a>:              What sensors are available on my PC?  
    318 <li><a accesskey=5 href="#Section%202.5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
    319 <li><a accesskey=6 href="#Section%202.6">Section 2.6</a>:              Where do I find out more about any of these chips?  
    320 </ul> 
    321  
    322 <p><hr> 
    323 Node:<a name="Section%202.1">Section 2.1</a>, 
    324 Next:<a rel=next accesskey=n href="#Section%202.2">Section 2.2</a>, 
    325 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    326 <br> 
    327  
    328 <h3>2.1 How are these sensors read?</h3> 
     314<div class="node"> 
     315<p><hr> 
     316<a name="Basics"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Installation">Installation</a>, 
     317Previous:&nbsp;<a rel="previous" accesskey="p" href="#Overview">Overview</a>, 
     318Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     319<br> 
     320</div> 
     321 
     322<h2 class="chapter">2 Sensor and Bus Basics</h2> 
     323 
     324<ul class="menu"> 
     325<li><a accesskey="1" href="#Section-2_002e1">Section 2.1</a>:              What sensors are available on my PC?  
     326<li><a accesskey="2" href="#Section-2_002e2">Section 2.2</a>:              What can a sensor chip like the "LM78" do?  
     327<li><a accesskey="3" href="#Section-2_002e3">Section 2.3</a>:              Where do I find out more about any of these chips?  
     328<li><a accesskey="4" href="#Section-2_002e4">Section 2.4</a>:              What sensors are available on my PC?  
     329<li><a accesskey="5" href="#Section-2_002e5">Section 2.5</a>:              What can a sensor chip like the "LM78" do?  
     330<li><a accesskey="6" href="#Section-2_002e6">Section 2.6</a>:              Where do I find out more about any of these chips?  
     331</ul> 
     332 
     333<div class="node"> 
     334<p><hr> 
     335<a name="Section-2_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e2">Section 2.2</a>, 
     336Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     337<br> 
     338</div> 
     339 
     340<h3 class="section">2.1 How are these sensors read?</h3> 
    329341 
    330342<p>Sensor chips reside on either the ISA bus, the SMBus, or both.  
    331 See the file <code>doc/chips/SUMMARY</code> in our package for a list. 
    332  
    333 <p>To communicate with chips on the ISA bus, the software uses 
     343See the file <span class="file">doc/chips/SUMMARY</span> in our package for a list. 
     344 
     345   <p>To communicate with chips on the ISA bus, the software uses 
    334346simple I/O reads and writes. 
    335347 
    336 <p>To communicate with chips on the SMBus, the software must 
     348   <p>To communicate with chips on the SMBus, the software must 
    337349use an SMBus interface device, explained below. 
    338350 
    339 <p><hr> 
    340 Node:<a name="Section%202.2">Section 2.2</a>, 
    341 Next:<a rel=next accesskey=n href="#Section%202.3">Section 2.3</a>, 
    342 Previous:<a rel=previous accesskey=p href="#Section%202.1">Section 2.1</a>, 
    343 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    344 <br> 
    345  
    346 <h3>2.2 What is the SMBus? And the I2C bus?</h3> 
     351<div class="node"> 
     352<p><hr> 
     353<a name="Section-2_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e3">Section 2.3</a>, 
     354Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e1">Section 2.1</a>, 
     355Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     356<br> 
     357</div> 
     358 
     359<h3 class="section">2.2 What is the SMBus? And the I2C bus?</h3> 
    347360 
    348361<p>The SMBus is the "System Management Bus".  More specifically, it is a 
    … …  
    352365and SMBus devices may be connected to the same (I2C) bus. 
    353366 
    354 <p>The SMBus (or I2C bus) starts at the host controller, used for 
     367   <p>The SMBus (or I2C bus) starts at the host controller, used for 
    355368starting transactions on the SMBus.  From the host interface, the 
    356369devices communicated with are the <dfn>slave</dfn> devices.  Each slave device has a 
    357370unique 7-bit address which the host uses to refer to that device. 
    358371 
    359 <p>For each supported SMBus host, there is a separate kernel module 
     372   <p>For each supported SMBus host, there is a separate kernel module 
    360373which implements the communication protocol with the host. Some SMBus hosts 
    361374really operate on the SMBus level; these hosts can not cope with pure I2C 
    … …  
    364377talk to pure I2C devices. 
    365378 
    366 <p><hr> 
    367 Node:<a name="Section%202.3">Section 2.3</a>, 
    368 Next:<a rel=next accesskey=n href="#Section%202.4">Section 2.4</a>, 
    369 Previous:<a rel=previous accesskey=p href="#Section%202.2">Section 2.2</a>, 
    370 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    371 <br> 
    372  
    373 <h3>2.3 I don't have an ISA bus!</h3> 
     379<div class="node"> 
     380<p><hr> 
     381<a name="Section-2_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e4">Section 2.4</a>, 
     382Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e2">Section 2.2</a>, 
     383Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     384<br> 
     385</div> 
     386 
     387<h3 class="section">2.3 I don't have an ISA bus!</h3> 
    374388 
    375389<p>We promise, you do, even if you don't have any old ISA slots.  
    … …  
    378392where many "legacy" functions, such as keyboard and interrupt controllers, 
    379393are found. It isn't necessarily a separate physical bus.  
    380 See the file <code>/proc/ioports</code> for a list of devices living on 
     394See the file <span class="file">/proc/ioports</span> for a list of devices living on 
    381395the "ISA Bus" in your system. If you don't like the term "ISA Bus" 
    382396think "I/O Space". 
    383397 
    384 <p><hr> 
    385 Node:<a name="Section%202.4">Section 2.4</a>, 
    386 Next:<a rel=next accesskey=n href="#Section%202.5">Section 2.5</a>, 
    387 Previous:<a rel=previous accesskey=p href="#Section%202.3">Section 2.3</a>, 
    388 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    389 <br> 
    390  
    391 <h3>2.4 What sensors do processors have?</h3> 
     398<div class="node"> 
     399<p><hr> 
     400<a name="Section-2_002e4"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e5">Section 2.5</a>, 
     401Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e3">Section 2.3</a>, 
     402Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     403<br> 
     404</div> 
     405 
     406<h3 class="section">2.4 What sensors do processors have?</h3> 
    392407 
    393408<p>Most new processors contain a thermal diode on the die itself.  
    … …  
    398413have circuitry for measuring the the electrical properties of 
    399414an external diode and converting this data to a temperature.  
    400 Any sensor chip listed in <code>doc/chips/SUMMARY</code> in our package which 
     415Any sensor chip listed in <span class="file">doc/chips/SUMMARY</span> in our package which 
    401416has support for more than one temperature supports external temperature sensing. 
    402417 
    403 <p>Older motherboards and processors without this feature generally use 
     418   <p>Older motherboards and processors without this feature generally use 
    404419an LM75 placed close to the processor. This is much less accurate. 
    405420 
    406 <p>The Pentium 2 'boxed' processor usually has an LM75 very close to the 
     421   <p>The Pentium 2 'boxed' processor usually has an LM75 very close to the 
    407422base of the box. It can be read through the SMBus to report the approximate 
    408423temperature of the processor.  The processor also contains an internal 
    … …  
    413428processor. 
    414429 
    415 <p>The P6 (Pentium-Pro) may have an LM75 in or just under the socket.  
     430   <p>The P6 (Pentium-Pro) may have an LM75 in or just under the socket.  
    416431P6's also have VID lines. 
    417432 
    418 <p>Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have 
     433   <p>Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have 
    419434LM75's under the sockets (depends on the mainboard, and how 'modern' the 
    420435mainboard is). 
    421436 
    422 <p>The P2 Xeon was the first Intel processor to include the SMBus 
     437   <p>The P2 Xeon was the first Intel processor to include the SMBus 
    423438interface on the P2 Xeon SEC. 
    424439 
    425 <p><hr> 
    426 Node:<a name="Section%202.5">Section 2.5</a>, 
    427 Next:<a rel=next accesskey=n href="#Section%202.6">Section 2.6</a>, 
    428 Previous:<a rel=previous accesskey=p href="#Section%202.4">Section 2.4</a>, 
    429 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    430 <br> 
    431  
    432 <h3>2.5 How often are the sensor values updated?</h3> 
     440<div class="node"> 
     441<p><hr> 
     442<a name="Section-2_002e5"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-2_002e6">Section 2.6</a>, 
     443Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e4">Section 2.4</a>, 
     444Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     445<br> 
     446</div> 
     447 
     448<h3 class="section">2.5 How often are the sensor values updated?</h3> 
    433449 
    434450<p>The LM78, and most other sensor chips like it, reads its sensors one 
    … …  
    440456read the values again, you will get the 'old' values again. 
    441457 
    442 <p><hr> 
    443 Node:<a name="Section%202.6">Section 2.6</a>, 
    444 Previous:<a rel=previous accesskey=p href="#Section%202.5">Section 2.5</a>, 
    445 Up:<a rel=up accesskey=u href="#Basics">Basics</a> 
    446 <br> 
    447  
    448 <h3>2.6 How are alarms triggered?</h3> 
     458<div class="node"> 
     459<p><hr> 
     460<a name="Section-2_002e6"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-2_002e5">Section 2.5</a>, 
     461Up:&nbsp;<a rel="up" accesskey="u" href="#Basics">Basics</a> 
     462<br> 
     463</div> 
     464 
     465<h3 class="section">2.6 How are alarms triggered?</h3> 
    449466 
    450467<p>It is possible to monitor each sensor and have an alarm go off if 
    … …  
    453470the actual chip if both are supported; the LM80, for example, has only 
    454471IRQ interrupts): IRQ interrupts and SMI interrupts.  IRQ stands for 
    455 Interrupt Request and are the interrupt lines you can find in <code>/proc/interrupts</code>.  
     472Interrupt Request and are the interrupt lines you can find in <span class="file">/proc/interrupts</span>.  
    456473SMI stands for System Management Interrupt, and is a special interrupt which 
    457474puts the processor in a secure environment independent of any other things 
    … …  
    459476supported, of course. 
    460477 
    461 <p>Even if no interrupt is generated, some bits in a status register 
     478   <p>Even if no interrupt is generated, some bits in a status register 
    462479will be set until the register is read the next time. If the alarm condition 
    463480persists after that, the bits will be set on the next scanning sweep, etc. 
    464481 
    465 <p>Most drivers in our package do not support interrupts at this time. 
    466  
    467 <p><hr> 
    468 Node:<a name="Installation">Installation</a>, 
    469 Next:<a rel=next accesskey=n href="#Problems">Problems</a>, 
    470 Previous:<a rel=previous accesskey=p href="#Basics">Basics</a>, 
    471 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    472 <br> 
    473  
    474 <h2>3 Installation and Management</h2> 
    475  
    476 <ul> 
    477 <li><a accesskey=1 href="#Section%203.1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
    478 <li><a accesskey=2 href="#Section%203.2">Section 3.2</a>:      How do I know which chips I own?  
    479 <li><a accesskey=3 href="#Section%203.3">Section 3.3</a>:      Which modules should I insert?  
    480 <li><a accesskey=4 href="#Section%203.4">Section 3.4</a>:      Do I need the configuration file <code>/etc/sensors.conf</code>?  
    481 <li><a accesskey=5 href="#Section%203.5">Section 3.5</a>:      What about the <code>No such file or directory</code> warnings 
    482 <li><a accesskey=6 href="#Section%203.6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
    483 <li><a accesskey=7 href="#Section%203.7">Section 3.7</a>:      It still does not compile or patch!  
    484 <li><a accesskey=8 href="#Section%203.8">Section 3.8</a>:      <code>make install</code> fails on Mandrake kernels 
    485 <li><a accesskey=9 href="#Section%203.9">Section 3.9</a>:      I get unresolved symbols when I <code>modprobe</code> modules 
    486 <li><a href="#Section%203.10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
    487 </ul> 
    488  
    489 <p><hr> 
    490 Node:<a name="Section%203.1">Section 3.1</a>, 
    491 Next:<a rel=next accesskey=n href="#Section%203.2">Section 3.2</a>, 
    492 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    493 <br> 
    494  
    495 <h3>3.1 Why so many modules, and how do I cope with them?</h3> 
     482   <p>Most drivers in our package do not support interrupts at this time. 
     483 
     484<div class="node"> 
     485<p><hr> 
     486<a name="Installation"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Problems">Problems</a>, 
     487Previous:&nbsp;<a rel="previous" accesskey="p" href="#Basics">Basics</a>, 
     488Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     489<br> 
     490</div> 
     491 
     492<h2 class="chapter">3 Installation and Management</h2> 
     493 
     494<ul class="menu"> 
     495<li><a accesskey="1" href="#Section-3_002e1">Section 3.1</a>:      Why so many modules, and how do I cope with them?  
     496<li><a accesskey="2" href="#Section-3_002e2">Section 3.2</a>:      How do I know which chips I own?  
     497<li><a accesskey="3" href="#Section-3_002e3">Section 3.3</a>:      Which modules should I insert?  
     498<li><a accesskey="4" href="#Section-3_002e4">Section 3.4</a>:      Do I need the configuration file <span class="file">/etc/sensors.conf</span>?  
     499<li><a accesskey="5" href="#Section-3_002e5">Section 3.5</a>:      What about the <span class="samp">No such file or directory</span> warnings 
     500<li><a accesskey="6" href="#Section-3_002e6">Section 3.6</a>:      I get all kinds of weird compilation errors?  
     501<li><a accesskey="7" href="#Section-3_002e7">Section 3.7</a>:      It still does not compile or patch!  
     502<li><a accesskey="8" href="#Section-3_002e8">Section 3.8</a>:      <span class="command">make install</span> fails on Mandrake kernels 
     503<li><a accesskey="9" href="#Section-3_002e9">Section 3.9</a>:      I get unresolved symbols when I <span class="command">modprobe</span> modules 
     504<li><a href="#Section-3_002e10">Section 3.10</a>:     I2C_DRIVERID_ADM1024 undefined (Red Hat especially) 
     505</ul> 
     506 
     507<div class="node"> 
     508<p><hr> 
     509<a name="Section-3_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e2">Section 3.2</a>, 
     510Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     511<br> 
     512</div> 
     513 
     514<h3 class="section">3.1 Why so many modules, and how do I cope with them?</h3> 
    496515 
    497516<p>We tried to make this package as modular as possible. This makes it 
    … …  
    499518space. On the other hand, it can be a bit confusing at first. 
    500519 
    501 <p>Here are two simple guidelines: 
    502 <ul> 
    503   <li>Run <code>sensors-detect</code> and do what it tells you.  
    504   <li>Always use <code>modprobe</code>, not <code>insmod</code>.  
    505 </ul> 
    506  
    507 <p>Further information is in <code>doc/modules</code>. 
    508  
    509 <p><a name="How%20do%20I%20know%20which%20chips%20I%20own"></a> 
    510 <p><hr> 
    511 Node:<a name="Section%203.2">Section 3.2</a>, 
    512 Next:<a rel=next accesskey=n href="#Section%203.3">Section 3.3</a>, 
    513 Previous:<a rel=previous accesskey=p href="#Section%203.1">Section 3.1</a>, 
    514 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    515 <br> 
    516  
    517 <h3>3.2 How do I know which chips I own?</h3> 
     520   <p>Here are two simple guidelines: 
     521     <ul> 
     522  <li>Run <span class="command">sensors-detect</span> and do what it tells you.  
     523  <li>Always use <span class="command">modprobe</span>, not <span class="command">insmod</span>.  
     524</ul> 
     525 
     526   <p>Further information is in <span class="file">doc/modules</span>. 
     527 
     528   <p><a name="How-do-I-know-which-chips-I-own"></a> 
     529<div class="node"> 
     530<p><hr> 
     531<a name="Section-3_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e3">Section 3.3</a>, 
     532Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e1">Section 3.1</a>, 
     533Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     534<br> 
     535</div> 
     536 
     537<h3 class="section">3.2 How do I know which chips I own?</h3> 
    518538 
    519539<p>We have an excellent program that scans all your hardware.  
    520 It is called <code>sensors-detect</code> and is installed in <code>/usr/local/sbin</code> 
    521 by <code>make install</code>. Just execute this script, and it will tell you. 
    522  
    523 <p>Chip detection in the drivers is fairly good. That means that it is 
     540It is called <span class="file">sensors-detect</span> and is installed in <span class="file">/usr/local/sbin</span> 
     541by <span class="command">make install</span>. Just execute this script, and it will tell you. 
     542 
     543   <p>Chip detection in the drivers is fairly good. That means that it is 
    524544usually harmless to insert more chip drivers than you need. However, this 
    525545can still lead to problems, so we do not recommend it. 
    526546 
    527 <p>If sensors-detect didn't find any sensors, either you don't have 
     547   <p>If sensors-detect didn't find any sensors, either you don't have 
    528548any, or the ones you have, we don't support. (Look at your motherboard 
    529549for candidates, then see <a href="#Help">Help</a>) 
    530550 
    531 <p><a name="Section%203.2.1"></a> 
    532  
    533 <h4>3.2.1 What chips are on motherboard XYZ?</h4> 
     551   <p><a name="Section-3_002e2_002e1"></a> 
     552 
     553<h4 class="subsection">3.2.1 What chips are on motherboard XYZ?</h4> 
    534554 
    535555<p><strong>!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!!</strong> 
    536556 
    537 <p>We have no idea. Here is what you should do: 
    538 <ol type=1 start=1> 
    539   </p><li>Run sensors-detect. 
    540 </ol> 
    541  
    542 <p>If that doesn't work: 
    543 <ol type=1 start=2> 
    544 </p><li>Look at your motherboard.  
     557   <p>We have no idea. Here is what you should do: 
     558     <ol type=1 start=1> 
     559  <li>Run sensors-detect. 
     560        </ol> 
     561 
     562   <p>If that doesn't work: 
     563     <ol type=1 start=2> 
     564<li>Look at your motherboard.  
    545565<li>Check the manufacturer's website or ask their support 
    546566<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website and the 
    547567<a href="http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/doc/useful_addresses.html">"links"</a> 
    548568page on <a href="http://www2.lm-sensors.nu/~lm78/">our website</a> some good cross-references. 
    549 </ol> 
    550  
    551 <p><a name="Section%203.2.2"></a> 
    552  
    553 <h4>3.2.2 Do you support motherboard XYZ?</h4> 
    554  
    555 <p>We don't support boards, we support chips. See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
    556  
    557 <p><a name="Section%203.2.3"></a> 
    558  
    559 <h4>3.2.3 Do you support chip XYZ?</h4> 
     569        </ol> 
     570 
     571   <p><a name="Section-3_002e2_002e2"></a> 
     572 
     573<h4 class="subsection">3.2.2 Do you support motherboard XYZ?</h4> 
     574 
     575<p>We don't support boards, we support chips. See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>. 
     576 
     577   <p><a name="Section-3_002e2_002e3"></a> 
     578 
     579<h4 class="subsection">3.2.3 Do you support chip XYZ?</h4> 
    560580 
    561581<p>This we have good answers for. 
    562 <ul> 
    563 <li>Sorted by Manufacturer:   <code>README</code> 
     582     <ul> 
     583<li>Sorted by Manufacturer:   <span class="file">README</span> 
    564584<li>Sorted by Manufacturer:   <a href="http://www2.lm-sensors.nu/~lm78/supported.html">http://www2.lm-sensors.nu/~lm78/supported.html</a> 
    565 <li>Sorted by Sensor Driver:  <code>doc/chips/SUMMARY</code> 
     585<li>Sorted by Sensor Driver:  <span class="file">doc/chips/SUMMARY</span> 
    566586<li>Newest Driver Status:     <a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html</a> 
    567587</ul> 
    568588 
    569 <p><a name="Section%203.2.4"></a> 
    570  
    571 <h4>3.2.4 Anybody working on a driver for chip XYZ?</h4> 
     589   <p><a name="Section-3_002e2_002e4"></a> 
     590 
     591<h4 class="subsection">3.2.4 Anybody working on a driver for chip XYZ?</h4> 
    572592 
    573593<p>Newest Driver Status: <a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">http://www2.lm-sensors.nu/~lm78/newdrivers.html</a> 
    574594 
    575 <p><hr> 
    576 Node:<a name="Section%203.3">Section 3.3</a>, 
    577 Next:<a rel=next accesskey=n href="#Section%203.4">Section 3.4</a>, 
    578 Previous:<a rel=previous accesskey=p href="#Section%203.2">Section 3.2</a>, 
    579 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    580 <br> 
    581  
    582 <h3>3.3 Which modules should I insert?</h3> 
    583  
    584 <p><code>sensors-detect</code> will tell you. Take the <code>modprobe</code> lines it 
    585 recommends and paste them into the appropriate <code>/etc/rc.d/xxxx</code> file 
     595<div class="node"> 
     596<p><hr> 
     597<a name="Section-3_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e4">Section 3.4</a>, 
     598Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e2">Section 3.2</a>, 
     599Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     600<br> 
     601</div> 
     602 
     603<h3 class="section">3.3 Which modules should I insert?</h3> 
     604 
     605<p><span class="command">sensors-detect</span> will tell you. Take the <span class="command">modprobe</span> lines it 
     606recommends and paste them into the appropriate <span class="file">/etc/rc.d/xxxx</span> file 
    586607to be executed at startup. 
    587608 
    588 <p>You need one module for each sensor chip and bus adapter you own; 
    589 if there are sensor chips on the ISA bus, you also need <code>i2c-isa.o</code>.  
     609   <p>You need one module for each sensor chip and bus adapter you own; 
     610if there are sensor chips on the ISA bus, you also need <span class="file">i2c-isa.o</span>.  
    590611for each type of chip you own. That's all. On my computer, I could use the 
    591612following lines: 
    592 <ul> 
    593 <li><code>modprobe i2c-isa</code> 
    594 <li><code>modprobe i2c-piix4</code> 
    595 <li><code>modprobe lm78</code> 
    596 <li><code>modprobe lm75</code> 
    597 <li><code>modprobe i2c-dev</code> 
    598 <li><code>sensors -s</code> 
    599 </ul> 
    600  
    601 <p><hr> 
    602 Node:<a name="Section%203.4">Section 3.4</a>, 
    603 Next:<a rel=next accesskey=n href="#Section%203.5">Section 3.5</a>, 
    604 Previous:<a rel=previous accesskey=p href="#Section%203.3">Section 3.3</a>, 
    605 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    606 <br> 
    607  
    608 <h3>3.4 Do I need the configuration file <code>/etc/sensors.conf</code>?</h3> 
    609  
    610 <p>Yes, for any applications that use <code>libsensors,</code> including the 
    611 <code>sensors</code> application included in our package.  
     613     <ul> 
     614<li><span class="command">modprobe i2c-isa</span> 
     615<li><span class="command">modprobe i2c-piix4</span> 
     616<li><span class="command">modprobe lm78</span> 
     617<li><span class="command">modprobe lm75</span> 
     618<li><span class="command">modprobe i2c-dev</span> 
     619<li><span class="command">sensors -s</span> 
     620</ul> 
     621 
     622<div class="node"> 
     623<p><hr> 
     624<a name="Section-3_002e4"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e5">Section 3.5</a>, 
     625Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e3">Section 3.3</a>, 
     626Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     627<br> 
     628</div> 
     629 
     630<h3 class="section">3.4 Do I need the configuration file <span class="file">/etc/sensors.conf</span>?</h3> 
     631 
     632<p>Yes, for any applications that use <span class="file">libsensors,</span> including the 
     633<span class="command">sensors</span> application included in our package.  
    612634It tells libsensors how to translate the values the chip 
    613635measures to real-world values. This is especially important for voltage 
    614636inputs. The default configuration file should usually do the trick.  
    615 It is automatically installed as <code>/etc/sensors.conf</code>, but it will not 
     637It is automatically installed as <span class="file">/etc/sensors.conf</span>, but it will not 
    616638overwrite any existing file with that name. 
    617639 
    618 <p><a name="Section%203.4.1"></a> 
    619  
    620 <h4>3.4.1 The labels for the voltage and temperature readings in <code>sensors</code> are incorrect!</h4> 
     640   <p><a name="Section-3_002e4_002e1"></a> 
     641 
     642<h4 class="subsection">3.4.1 The labels for the voltage and temperature readings in <span class="command">sensors</span> are incorrect!</h4> 
    621643 
    622644<p>Every motherboard is different. You can customize the labels 
    623 in the file <code>/etc/sensors.conf</code>. That's why it exists!  
    624 The default labelling (in <code>lib/chips.c</code> and <code>/etc/sensors.conf</code>) is just 
     645in the file <span class="file">/etc/sensors.conf</span>. That's why it exists!  
     646The default labelling (in <span class="file">lib/chips.c</span> and <span class="file">/etc/sensors.conf</span>) is just 
    625647a template. 
    626648 
    627 <p><a name="Section%203.4.2"></a> 
    628  
    629 <h4>3.4.2 The min and max for the readings in <code>sensors</code> are incorrect!</h4> 
    630  
    631 <p>You can customize them in the file <code>/etc/sensors.conf</code>. See above. 
    632  
    633 <p><a name="Section%203.4.3"></a> 
    634  
    635 <h4>3.4.3 The min and max settings in <code>/etc/sensors.conf</code> didn't take effect!</h4> 
    636  
    637 <p>You forgot to run <code>sensors -s</code>. See above. 
    638  
    639 <p><a name="Section%203.4.4"></a> 
    640  
    641 <h4>3.4.4 One sensor isn't hooked up on my board!</h4> 
    642  
    643 <p>Use an <code>ignore</code> line in <code>/etc/sensors.conf</code> so it isn't 
    644 displayed in <code>sensors</code>. 
    645  
    646 <p><a name="Section%203.4.5"></a> 
    647  
    648 <h4>3.4.5 I need help with <code>sensors.conf</code>!</h4> 
     649   <p><a name="Section-3_002e4_002e2"></a> 
     650 
     651<h4 class="subsection">3.4.2 The min and max for the readings in <span class="command">sensors</span> are incorrect!</h4> 
     652 
     653<p>You can customize them in the file <span class="file">/etc/sensors.conf</span>. See above. 
     654 
     655   <p><a name="Section-3_002e4_002e3"></a> 
     656 
     657<h4 class="subsection">3.4.3 The min and max settings in <span class="file">/etc/sensors.conf</span> didn't take effect!</h4> 
     658 
     659<p>You forgot to run <span class="command">sensors -s</span>. See above. 
     660 
     661   <p><a name="Section-3_002e4_002e4"></a> 
     662 
     663<h4 class="subsection">3.4.4 One sensor isn't hooked up on my board!</h4> 
     664 
     665<p>Use an <span class="command">ignore</span> line in <span class="file">/etc/sensors.conf</span> so it isn't 
     666displayed in <span class="command">sensors</span>. 
     667 
     668   <p><a name="Section-3_002e4_002e5"></a> 
     669 
     670<h4 class="subsection">3.4.5 I need help with <span class="file">sensors.conf</span>!</h4> 
    649671 
    650672<p>There is detailed help at the top of that file. 
    651673 
    652 <p><a name="Section%203.4.6"></a> 
    653  
    654 <h4>3.4.6 Do you have a database of <code>sensors.conf</code> entries for specific boards?</h4> 
     674   <p><a name="Section-3_002e4_002e6"></a> 
     675 
     676<h4 class="subsection">3.4.6 Do you have a database of <span class="file">sensors.conf</span> entries for specific boards?</h4> 
    655677 
    656678<p>No. Good idea though. If you would like to set one up on your website 
    657679send us mail and we will set up a link to it. 
    658680 
    659 <p><hr> 
    660 Node:<a name="Section%203.5">Section 3.5</a>, 
    661 Next:<a rel=next accesskey=n href="#Section%203.6">Section 3.6</a>, 
    662 Previous:<a rel=previous accesskey=p href="#Section%203.4">Section 3.4</a>, 
    663 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    664 <br> 
    665  
    666 <h3>3.5 What about the <code>No such file or directory</code> warnings when I compile?</h3> 
     681<div class="node"> 
     682<p><hr> 
     683<a name="Section-3_002e5"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e6">Section 3.6</a>, 
     684Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e4">Section 3.4</a>, 
     685Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     686<br> 
     687</div> 
     688 
     689<h3 class="section">3.5 What about the <span class="samp">No such file or directory</span> warnings when I compile?</h3> 
    667690 
    668691<p>Don't worry about them. The dependency files (which tell which 
    669692files should be recompiled when certain files change) are created 
    670 dynamically. They are not distributed with the package. The <code>make</code> program 
     693dynamically. They are not distributed with the package. The <span class="command">make</span> program 
    671694notices they are not there, and warns about that - and the first thing 
    672695it will do is generate them. So all is well. 
    673696 
    674 <p><hr> 
    675 Node:<a name="Section%203.6">Section 3.6</a>, 
    676 Next:<a rel=next accesskey=n href="#Section%203.7">Section 3.7</a>, 
    677 Previous:<a rel=previous accesskey=p href="#Section%203.5">Section 3.5</a>, 
    678 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    679 <br> 
    680  
    681 <h3>3.6 I get all kinds of weird compilation errors?</h3> 
     697<div class="node"> 
     698<p><hr> 
     699<a name="Section-3_002e6"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e7">Section 3.7</a>, 
     700Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e5">Section 3.5</a>, 
     701Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     702<br> 
     703</div> 
     704 
     705<h3 class="section">3.6 I get all kinds of weird compilation errors?</h3> 
    682706 
    683707<p>Check that the correct i2c header files are used. Depending on 
    684 how you installed, they should be under either <code>/usr/local/include</code> or 
    685 <code>/usr/src/linux*/include</code>. Try to edit the <code>Makefile</code> for the other setting. 
    686  
    687 <p><a name="Section%203.6.1"></a> 
    688  
    689 <h4>3.6.1 <code>No rule to make target xxxx needed by xxxx</code> - how to fix?</h4> 
    690  
    691 <ul> 
    692 <li>See <a href="#Section%203.6">I get all kinds of weird compilation errors</a>, also try <code>make clean</code> in <code>lm_sensors</code>.  
    693 <li>If that doesn't work, try <code>make clean</code> in <code>i2c</code>.  
    694 <li>If that doesn't work, try <code>make clean</code> in the kernel.  
    695 <li>Also make sure <code>/usr/include/linux</code> points to <code>/usr/src/linux/include/linux</code>.  
    696 </ul> 
    697  
    698 <p><hr> 
    699 Node:<a name="Section%203.7">Section 3.7</a>, 
    700 Next:<a rel=next accesskey=n href="#Section%203.8">Section 3.8</a>, 
    701 Previous:<a rel=previous accesskey=p href="#Section%203.6">Section 3.6</a>, 
    702 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    703 <br> 
    704  
    705 <h3>3.7 It still does not compile or patch!</h3> 
     708how you installed, they should be under either <span class="file">/usr/local/include</span> or 
     709<span class="file">/usr/src/linux*/include</span>. Try to edit the <span class="file">Makefile</span> for the other setting. 
     710 
     711   <p><a name="Section-3_002e6_002e1"></a> 
     712 
     713<h4 class="subsection">3.6.1 <span class="samp">No rule to make target xxxx needed by xxxx</span> - how to fix?</h4> 
     714 
     715     <ul> 
     716<li>See <a href="#Section-3_002e6">I get all kinds of weird compilation errors</a>, also try <span class="command">make clean</span> in <span class="file">lm_sensors</span>.  
     717<li>If that doesn't work, try <span class="command">make clean</span> in <span class="file">i2c</span>.  
     718<li>If that doesn't work, try <span class="command">make clean</span> in the kernel.  
     719<li>Also make sure <span class="file">/usr/include/linux</span> points to <span class="file">/usr/src/linux/include/linux</span>.  
     720</ul> 
     721 
     722<div class="node"> 
     723<p><hr> 
     724<a name="Section-3_002e7"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e8">Section 3.8</a>, 
     725Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e6">Section 3.6</a>, 
     726Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     727<br> 
     728</div> 
     729 
     730<h3 class="section">3.7 It still does not compile or patch!</h3> 
    706731 
    707732<p>Have you installed the matching version of the i2c package? Remember, 
    … …  
    709734files to be found! 
    710735 
    711 <p>If you want to patch the kernel, you will have to apply the i2c 
     736   <p>If you want to patch the kernel, you will have to apply the i2c 
    712737patches first! 
    713738 
    714 <p><hr> 
    715 Node:<a name="Section%203.8">Section 3.8</a>, 
    716 Next:<a rel=next accesskey=n href="#Section%203.9">Section 3.9</a>, 
    717 Previous:<a rel=previous accesskey=p href="#Section%203.7">Section 3.7</a>, 
    718 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    719 <br> 
    720  
    721 <h3>3.8 <code>make install</code> fails on Mandrake kernels</h3> 
    722  
    723 <p>Mandrake uses a non-standard <code>version.h</code> file which confuses our <code>Makefile</code>.  
    724 Edit our <code>Makefile</code> on the <code>MODDIR :=</code> line to hard-code the module directory. 
    725  
    726 <p><hr> 
    727 Node:<a name="Section%203.9">Section 3.9</a>, 
    728 Next:<a rel=next accesskey=n href="#Section%203.10">Section 3.10</a>, 
    729 Previous:<a rel=previous accesskey=p href="#Section%203.8">Section 3.8</a>, 
    730 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    731 <br> 
    732  
    733 <h3>3.9 I get unresolved symbols when I <code>modprobe</code> modules (Red Hat especially)</h3> 
     739<div class="node"> 
     740<p><hr> 
     741<a name="Section-3_002e8"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e9">Section 3.9</a>, 
     742Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e7">Section 3.7</a>, 
     743Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     744<br> 
     745</div> 
     746 
     747<h3 class="section">3.8 <span class="command">make install</span> fails on Mandrake kernels</h3> 
     748 
     749<p>Mandrake uses a non-standard <span class="file">version.h</span> file which confuses our <span class="file">Makefile</span>.  
     750Edit our <span class="file">Makefile</span> on the <code>MODDIR :=</code> line to hard-code the module directory. 
     751 
     752<div class="node"> 
     753<p><hr> 
     754<a name="Section-3_002e9"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-3_002e10">Section 3.10</a>, 
     755Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e8">Section 3.8</a>, 
     756Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     757<br> 
     758</div> 
     759 
     760<h3 class="section">3.9 I get unresolved symbols when I <span class="command">modprobe</span> modules (Red Hat especially)</h3> 
    734761 
    735762<p>Example: 
    736 <br><pre>*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
    737 i2c_bit_add_bus_R8c3bc60e 
    738 i2c_bit_del_bus_R92b18f49 
     763<pre class="example">     *** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o 
     764     i2c_bit_add_bus_R8c3bc60e 
     765     i2c_bit_del_bus_R92b18f49 
    739766</pre> 
    740  
    741 <p>You can also run <code>depmod -a -e</code> to see all unresolved symbols. 
    742  
    743 <p>These are module versioning problems. Generally you did not compile 
     767   <p>You can also run <span class="command">depmod -a -e</span> to see all unresolved symbols. 
     768 
     769   <p>These are module versioning problems. Generally you did not compile 
    744770against the kernel you are running. Sometimes the Red Hat source you 
    745771have is not for the kernel you are running.  
    746772You must compile our package against the source for the kernel you 
    747 are running with something like <code>make LINUX=/usr/src/linux-2.4.14</code>. 
    748  
    749 <p>Try the following to be sure: 
    750  
    751 <ul> 
    752 <li><code>nm --extern MODULE.o</code> 
     773are running with something like <span class="command">make LINUX=/usr/src/linux-2.4.14</span>. 
     774 
     775   <p>Try the following to be sure: 
     776 
     777     <ul> 
     778<li><span class="command">nm --extern MODULE.o</span> 
    753779Filter out the kernel symbols, like <code>kmalloc</code>, <code>printk</code> etc. and note the 
    754780number code behind them, like <code>printk_R1b7d4074</code>. If there is no numeric 
    755781code after them, note this too.  
    756 <li><code>grep SYMBOL /proc/ksyms</code> 
     782<li><span class="command">grep SYMBOL /proc/ksyms</span> 
    757783Substitute SYMBOL by the basename of the symbols above, like <code>kmalloc</code>, 
    758784<code>printk</code> etc. Note the number code behind them, or the lack thereof.  
    … …  
    762788</ul> 
    763789 
    764 <p><hr> 
    765 Node:<a name="Section%203.10">Section 3.10</a>, 
    766 Previous:<a rel=previous accesskey=p href="#Section%203.9">Section 3.9</a>, 
    767 Up:<a rel=up accesskey=u href="#Installation">Installation</a> 
    768 <br> 
    769  
    770 <h3>3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3> 
     790<div class="node"> 
     791<p><hr> 
     792<a name="Section-3_002e10"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-3_002e9">Section 3.9</a>, 
     793Up:&nbsp;<a rel="up" accesskey="u" href="#Installation">Installation</a> 
     794<br> 
     795</div> 
     796 
     797<h3 class="section">3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)</h3> 
    771798 
    772799<p>In some versions of Redhat, an RPM is included to provide i2c support.  
    … …  
    775802these obsolete header files, at a command prompt: 
    776803 
    777 <ol type=1 start=1> 
    778 </p><li><code>rpm -qa | grep i2c</code> 
    779 <li>Look for <code>kernel-i2c,</code> or a similar rpm in the output 
     804     <ol type=1 start=1> 
     805<li><span class="command">rpm -qa | grep i2c</span> 
     806<li>Look for <span class="file">kernel-i2c,</span> or a similar rpm in the output 
    780807<li>&lt;as root&gt; 
    781 <code>rpm -ev kernel-i2c</code> (or the name of the similar package) 
     808<span class="command">rpm -ev kernel-i2c</span> (or the name of the similar package) 
    782809If this complains about dependencies, you can try adding 
    783 <code>--nodeps</code>, but this *MAY* break something else.  Not likely, 
     810<span class="command">--nodeps</span>, but this *MAY* break something else.  Not likely, 
    784811as you have upgraded kernels, and nothing should be using the 
    785812old i2c stuff anymore anyway.  Just don't use it with abandon.  
    786 <li>Try (in the build directory of <code>lm_sensors)</code> 
    787 <br><pre><code>make clean</code> 
    788 <code>make</code> 
    789 </pre> 
    790 <li><em>If</em> you still have problems, you may have to replace the include 
    791 paths in the <code>.c/.h</code> files with absolute paths to the header files.  
     813<li>Try (in the build directory of <span class="file">lm_sensors)</span> 
     814     <pre class="example">          <span class="command">make clean</span> 
     815          <span class="command">make</span> 
     816     </pre> 
     817     <li><em>If</em> you still have problems, you may have to replace the include 
     818paths in the <span class="file">.c/.h</span> files with absolute paths to the header files.  
    792819More of a workaround than a real fix, but at least you can get it 
    793820to work. 
    794 </ol> 
    795  
    796 <p><hr> 
    797 Node:<a name="Problems">Problems</a>, 
    798 Next:<a rel=next accesskey=n href="#Help">Help</a>, 
    799 Previous:<a rel=previous accesskey=p href="#Installation">Installation</a>, 
    800 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    801 <br> 
    802  
    803 <h2>4 Problems</h2> 
    804  
    805 <ul> 
    806 <li><a accesskey=1 href="#Section%204.1">Section 4.1</a>:          My fans report exactly half/double their values?  
    807 <li><a accesskey=2 href="#Section%204.2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
    808 <li><a accesskey=3 href="#Section%204.3">Section 4.3</a>:          Why do I have two Vcore readings?  
    809 <li><a accesskey=4 href="#Section%204.4">Section 4.4</a>:          How do those ALARMS work?  
    810 <li><a accesskey=5 href="#Section%204.5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
    811 <li><a accesskey=6 href="#Section%204.6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
    812 <li><a accesskey=7 href="#Section%204.7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
    813 <li><a accesskey=8 href="#Section%204.8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
    814 <li><a accesskey=9 href="#Section%204.9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
    815 <li><a href="#Section%204.10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?  
    816 <li><a href="#Section%204.11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?  
    817 <li><a href="#Section%204.12">Section 4.12</a>:         My BIOS reports a higher CPU temperature than you!  
    818 <li><a href="#Section%204.13">Section 4.13</a>:         I read strange values from the raw <code>/proc</code> files!  
    819 <li><a href="#Section%204.14">Section 4.14</a>:         How do I set new limits?  
    820 <li><a href="#Section%204.15">Section 4.15</a>:         Some sensors are doubly detected?  
    821 <li><a href="#Section%204.16">Section 4.16</a>:         I ran sensors-detect, but now I get strange readings?!  
    822 <li><a href="#Section%204.17">Section 4.17</a>:         Bad readings from particular chips 
    823 <li><a href="#Section%204.18">Section 4.18</a>:         How do I configure two chips (LM87) differently?  
    824 <li><a href="#Section%204.19">Section 4.19</a>:         Dmesg says <code>Upgrade BIOS</code>! I don't want to!  
    825 <li><a href="#Section%204.20">Section 4.20</a>:         Sensors says <code>Can't access procfs/sysfs file</code> 
    826 <li><a href="#Section%204.21">Section 4.21</a>:         Sensors says <code>No sensors found!</code> 
    827 <li><a href="#Section%204.22">Section 4.22</a>:         Sensors output is not correct!  
    828 <li><a href="#Section%204.23">Section 4.23</a>:         What is at I2C address XXX?  
    829 <li><a href="#Section%204.24">Section 4.24</a>:         Sensors-detect doesn't work at all 
    830 <li><a href="#Section%204.25">Section 4.25</a>:         Sensors says <code>Error: Line xxx: zzzzzzz</code> 
    831 <li><a href="#Section%204.26">Section 4.26</a>:         Sensors only gives the name, adapter, and algorithm!  
    832 <li><a href="#Section%204.27">Section 4.27</a>:         Sensors says <code>ERROR: Can't get xxxxx data!</code> 
    833 <li><a href="#Section%204.28">Section 4.28</a>:         Sensors doesn't find any sensors, just eeproms.  
    834 <li><a href="#Section%204.29">Section 4.29</a>:         Inserting modules hangs my board 
    835 <li><a href="#Section%204.30">Section 4.30</a>:         Inserting modules slows down my board 
    836 <li><a href="#Section%204.31">Section 4.31</a>:         Problems on particular motherboards 
    837 <li><a href="#Section%204.32">Section 4.32</a>:         Problems on particular systems 
    838 <li><a href="#Section%204.33">Section 4.33</a>:         Problems on 2.6 kernels 
    839 </ul> 
    840  
    841 <p><hr> 
    842 Node:<a name="Section%204.1">Section 4.1</a>, 
    843 Next:<a rel=next accesskey=n href="#Section%204.2">Section 4.2</a>, 
    844 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    845 <br> 
    846  
    847 <h3>4.1 My fans report exactly half/double their values compared to the BIOS?</h3> 
     821        </ol> 
     822 
     823<div class="node"> 
     824<p><hr> 
     825<a name="Problems"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Help">Help</a>, 
     826Previous:&nbsp;<a rel="previous" accesskey="p" href="#Installation">Installation</a>, 
     827Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     828<br> 
     829</div> 
     830 
     831<h2 class="chapter">4 Problems</h2> 
     832 
     833<ul class="menu"> 
     834<li><a accesskey="1" href="#Section-4_002e1">Section 4.1</a>:          My fans report exactly half/double their values?  
     835<li><a accesskey="2" href="#Section-4_002e2">Section 4.2</a>:          Why do my two LM75's report "-48 degrees"?  
     836<li><a accesskey="3" href="#Section-4_002e3">Section 4.3</a>:          Why do I have two Vcore readings?  
     837<li><a accesskey="4" href="#Section-4_002e4">Section 4.4</a>:          How do those ALARMS work?  
     838<li><a accesskey="5" href="#Section-4_002e5">Section 4.5</a>:          My voltage readings seem to drift a bit. What's wrong?  
     839<li><a accesskey="6" href="#Section-4_002e6">Section 4.6</a>:          Some measurements are way out of range. What happened?  
     840<li><a accesskey="7" href="#Section-4_002e7">Section 4.7</a>:          What are VID lines? Why is the VID reading wrong?  
     841<li><a accesskey="8" href="#Section-4_002e8">Section 4.8</a>:          Sensor are only updated each second or so. Why?  
     842<li><a accesskey="9" href="#Section-4_002e9">Section 4.9</a>:          It takes a second before reading sensor results. Why?  
     843<li><a href="#Section-4_002e10">Section 4.10</a>:         Can I be alerted when an ALARM occurs?  
     844<li><a href="#Section-4_002e11">Section 4.11</a>:         SMBus transactions on my PIIX4 simply don't work. Why?  
     845<li><a href="#Section-4_002e12">Section 4.12</a>:         My BIOS reports a higher CPU temperature than you!  
     846<li><a href="#Section-4_002e13">Section 4.13</a>:         I read strange values from the raw <span class="file">/proc</span> files!  
     847<li><a href="#Section-4_002e14">Section 4.14</a>:         How do I set new limits?  
     848<li><a href="#Section-4_002e15">Section 4.15</a>:         Some sensors are doubly detected?  
     849<li><a href="#Section-4_002e16">Section 4.16</a>:         I ran sensors-detect, but now I get strange readings?!  
     850<li><a href="#Section-4_002e17">Section 4.17</a>:         Bad readings from particular chips 
     851<li><a href="#Section-4_002e18">Section 4.18</a>:         How do I configure two chips (LM87) differently?  
     852<li><a href="#Section-4_002e19">Section 4.19</a>:         Dmesg says <span class="samp">Upgrade BIOS</span>! I don't want to!  
     853<li><a href="#Section-4_002e20">Section 4.20</a>:         Sensors says <span class="samp">Can't access procfs/sysfs file</span> 
     854<li><a href="#Section-4_002e21">Section 4.21</a>:         Sensors says <span class="samp">No sensors found!</span> 
     855<li><a href="#Section-4_002e22">Section 4.22</a>:         Sensors output is not correct!  
     856<li><a href="#Section-4_002e23">Section 4.23</a>:         What is at I2C address XXX?  
     857<li><a href="#Section-4_002e24">Section 4.24</a>:         Sensors-detect doesn't work at all 
     858<li><a href="#Section-4_002e25">Section 4.25</a>:         Sensors says <span class="samp">Error: Line xxx: zzzzzzz</span> 
     859<li><a href="#Section-4_002e26">Section 4.26</a>:         Sensors only gives the name, adapter, and algorithm!  
     860<li><a href="#Section-4_002e27">Section 4.27</a>:         Sensors says <span class="samp">ERROR: Can't get xxxxx data!</span> 
     861<li><a href="#Section-4_002e28">Section 4.28</a>:         Sensors doesn't find any sensors, just eeproms.  
     862<li><a href="#Section-4_002e29">Section 4.29</a>:         Inserting modules hangs my board 
     863<li><a href="#Section-4_002e30">Section 4.30</a>:         Inserting modules slows down my board 
     864<li><a href="#Section-4_002e31">Section 4.31</a>:         Problems on particular motherboards 
     865<li><a href="#Section-4_002e32">Section 4.32</a>:         Problems on particular systems 
     866<li><a href="#Section-4_002e33">Section 4.33</a>:         Problems on 2.6 kernels 
     867</ul> 
     868 
     869<div class="node"> 
     870<p><hr> 
     871<a name="Section-4_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e2">Section 4.2</a>, 
     872Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     873<br> 
     874</div> 
     875 
     876<h3 class="section">4.1 My fans report exactly half/double their values compared to the BIOS?</h3> 
    848877 
    849878<p>The problem with much of the sensor data is that it is impossible to 
    … …  
    851880configuration is.  Some fans report one 'tick' each rotation, some report 
    852881two 'ticks' each rotation. It is easy to resolve this through the 
    853 configuration file <code>/etc/sensors.conf</code>: 
    854  
    855 <br><pre>chip lm78-*             # Or whatever chip this relates to 
    856 compute fan1 2*@,@/2    # This will double the fan1 reading 
    857                         # -- or -- 
    858 compute fan1 @/2,2*@    # This will halve the fan1 reading 
     882configuration file <span class="file">/etc/sensors.conf</span>: 
     883 
     884<pre class="example">     chip lm78-*             # Or whatever chip this relates to 
     885     compute fan1 2*@,@/2    # This will double the fan1 reading 
     886                             # -- or -- 
     887     compute fan1 @/2,2*@    # This will halve the fan1 reading 
    859888</pre> 
    860  
    861 <p>See <code>doc/fan-divisors</code> in our package for further information. 
    862  
    863 <p><a name="Fans%20sometimes%2falways%20read%200!"></a> 
    864  
    865 <h4>4.1.1 Fans sometimes/always read 0!!</h4> 
     889   <p>See <span class="file">doc/fan-divisors</span> in our package for further information. 
     890 
     891   <p><a name="Fans-sometimes_002falways-read-0_0021"></a> 
     892 
     893<h4 class="subsection">4.1.1 Fans sometimes/always read 0!!</h4> 
    866894 
    867895<p>You may not have a three-wire fan, which is required. 
    868896 
    869 <p>You may need to increase the 'fan divisor'. See <code>doc/fan-divisors</code> 
     897   <p>You may need to increase the 'fan divisor'. See <span class="file">doc/fan-divisors</span> 
    870898in our package for further information. 
    871899 
    872 <p><a name="I%20doubled%20the%20fan%20divisor%20and%20the%20fan%20still%20reads%207000"></a> 
    873  
    874 <h4>4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4> 
     900   <p><a name="I-doubled-the-fan-divisor-and-the-fan-still-reads-7000"></a> 
     901 
     902<h4 class="subsection">4.1.2 I doubled the fan divisor and the fan still reads 7000!</h4> 
    875903 
    876904<p>Believe it or not, doubling the 'fan divisor' will not halve 
    877 the fan reading. You have to add a compute line in <code>/etc/sensors.conf</code>.  
    878 See <a href="#Section%204.1">My fans report exactly half/double their values compared to the BIOS</a>, 
    879 and see <code>doc/fan-divisors</code> in our package for further information. 
    880  
    881 <p><hr> 
    882 Node:<a name="Section%204.2">Section 4.2</a>, 
    883 Next:<a rel=next accesskey=n href="#Section%204.3">Section 4.3</a>, 
    884 Previous:<a rel=previous accesskey=p href="#Section%204.1">Section 4.1</a>, 
    885 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    886 <br> 
    887  
    888 <h3>4.2 Why do my two LM75's report "-48 degrees"?</h3> 
     905the fan reading. You have to add a compute line in <span class="file">/etc/sensors.conf</span>.  
     906See <a href="#Section-4_002e1">My fans report exactly half/double their values compared to the BIOS</a>, 
     907and see <span class="file">doc/fan-divisors</span> in our package for further information. 
     908 
     909<div class="node"> 
     910<p><hr> 
     911<a name="Section-4_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e3">Section 4.3</a>, 
     912Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e1">Section 4.1</a>, 
     913Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     914<br> 
     915</div> 
     916 
     917<h3 class="section">4.2 Why do my two LM75's report "-48 degrees"?</h3> 
    889918 
    890919<p>For starters, those aren't LM75's.  Your mainboard actually has the 
    … …  
    893922to the chip resulting in these strange -48 degree readings. 
    894923 
    895 <p>In upcoming versions, you will be able to disable non-interesting 
     924   <p>In upcoming versions, you will be able to disable non-interesting 
    896925readings. 
    897926 
    898 <p><hr> 
    899 Node:<a name="Section%204.3">Section 4.3</a>, 
    900 Next:<a rel=next accesskey=n href="#Section%204.4">Section 4.4</a>, 
    901 Previous:<a rel=previous accesskey=p href="#Section%204.2">Section 4.2</a>, 
    902 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    903 <br> 
    904  
    905 <h3>4.3 Why do I have two Vcore readings, I have only one processor!</h3> 
     927<div class="node"> 
     928<p><hr> 
     929<a name="Section-4_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e4">Section 4.4</a>, 
     930Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e2">Section 4.2</a>, 
     931Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     932<br> 
     933</div> 
     934 
     935<h3 class="section">4.3 Why do I have two Vcore readings, I have only one processor!</h3> 
    906936 
    907937<p>The LM78 has seven voltage sensors. The default way of 
    … …  
    909939even if you do not have one. You can easily edit the configuration file 
    910940to give it another name, or make this reading disappear using 
    911 an <code>ignore</code> line. 
    912  
    913 <p>Note that Vcore2 is often the same as Vcore on motherboards which 
     941an <span class="command">ignore</span> line. 
     942 
     943   <p>Note that Vcore2 is often the same as Vcore on motherboards which 
    914944only support one processor. Another possibility is that Vcore2 is not 
    915945connected at all and will not have a valid reading at all.  
    … …  
    918948different. 
    919949 
    920 <p><hr> 
    921 Node:<a name="Section%204.4">Section 4.4</a>, 
    922 Next:<a rel=next accesskey=n href="#Section%204.5">Section 4.5</a>, 
    923 Previous:<a rel=previous accesskey=p href="#Section%204.3">Section 4.3</a>, 
    924 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    925 <br> 
    926  
    927 <h3>4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3> 
    928  
    929 <p>The ALARM indications in <code>sensors</code> are those reported by the 
    930 sensor chip itself. They are NOT calculated by <code>sensors</code>. <code>sensors</code> 
     950<div class="node"> 
     951<p><hr> 
     952<a name="Section-4_002e4"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e5">Section 4.5</a>, 
     953Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e3">Section 4.3</a>, 
     954Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     955<br> 
     956</div> 
     957 
     958<h3 class="section">4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!</h3> 
     959 
     960<p>The ALARM indications in <span class="command">sensors</span> are those reported by the 
     961sensor chip itself. They are NOT calculated by <span class="command">sensors</span>. <span class="command">sensors</span> 
    931962simply reads the ALARM bits and reports them. 
    932963 
    933 <p>An ALARM will go off when a minimum or maximum limit is crossed.  
     964   <p>An ALARM will go off when a minimum or maximum limit is crossed.  
    934965The ALARM is then latched - that is, it will stay there until the 
    935966chip's registers are next accessed - which will be the next time 
    … …  
    937968update. 
    938969 
    939 <p>Reading the registers clears the ALARMS, unless the current 
     970   <p>Reading the registers clears the ALARMS, unless the current 
    940971value is still out of range. 
    941972 
    942 <p>The purpose of this scheme is to tell you if there has been 
     973   <p>The purpose of this scheme is to tell you if there has been 
    943974a problem and report it to the user. Voltage or temperature spikes 
    944975get detected without having to read the sensor chip hundreds of times 
    945976a second. The implemetation details depend a bit on the kind of chip.  
    946 See the specific chip documentation in <code>doc/chips</code> and the 
     977See the specific chip documentation in <span class="file">doc/chips</span> and the 
    947978chip datasheet for more information. 
    948979 
    949 <p><hr> 
    950 Node:<a name="Section%204.5">Section 4.5</a>, 
    951 Next:<a rel=next accesskey=n href="#Section%204.6">Section 4.6</a>, 
    952 Previous:<a rel=previous accesskey=p href="#Section%204.4">Section 4.4</a>, 
    953 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    954 <br> 
    955  
    956 <h3>4.5 My voltage readings seem to drift a bit. Is something wrong?</h3> 
     980<div class="node"> 
     981<p><hr> 
     982<a name="Section-4_002e5"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e6">Section 4.6</a>, 
     983Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e4">Section 4.4</a>, 
     984Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     985<br> 
     986</div> 
     987 
     988<h3 class="section">4.5 My voltage readings seem to drift a bit. Is something wrong?</h3> 
    957989 
    958990<p>No, probably not. If your motherboard heats up a bit, the sensed 
    … …  
    965997reason to worry. 
    966998 
    967 <p><hr> 
    968 Node:<a name="Section%204.6">Section 4.6</a>, 
    969 Next:<a rel=next accesskey=n href="#Section%204.7">Section 4.7</a>, 
    970 Previous:<a rel=previous accesskey=p href="#Section%204.5">Section 4.5</a>, 
    971 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    972 <br> 
    973  
    974 <h3>4.6 Some measurements are way out of range. What happened?</h3> 
     999<div class="node"> 
     1000<p><hr> 
     1001<a name="Section-4_002e6"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e7">Section 4.7</a>, 
     1002Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e5">Section 4.5</a>, 
     1003Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1004<br> 
     1005</div> 
     1006 
     1007<h3 class="section">4.6 Some measurements are way out of range. What happened?</h3> 
    9751008 
    9761009<p>Each module tries to set limits to sensible values on initialization, 
    … …  
    9791012So limits can be strange, if the chip is connected in a non-standard way. 
    9801013 
    981 <p>Readings can also be strange; there are several reasons for this.  
     1014   <p>Readings can also be strange; there are several reasons for this.  
    9821015Temperature sensors, for example, can simply not be present, even though 
    9831016the chip supports them. Also, it can be that the input is used in a 
    … …  
    9861019more information. 
    9871020 
    988 <p><hr> 
    989 Node:<a name="Section%204.7">Section 4.7</a>, 
    990 Next:<a rel=next accesskey=n href="#Section%204.8">Section 4.8</a>, 
    991 Previous:<a rel=previous accesskey=p href="#Section%204.6">Section 4.6</a>, 
    992 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    993 <br> 
    994  
    995 <h3>4.7 What are VID lines? Why is the VID reading wrong?</h3> 
     1021<div class="node"> 
     1022<p><hr> 
     1023<a name="Section-4_002e7"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e8">Section 4.8</a>, 
     1024Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e6">Section 4.6</a>, 
     1025Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1026<br> 
     1027</div> 
     1028 
     1029<h3 class="section">4.7 What are VID lines? Why is the VID reading wrong?</h3> 
    9961030 
    9971031<p>These describe the core voltage for your processor. They are 
    … …  
    9991033correctly connected to the sensor chip, so the readings may be invalid.  
    10001034A reading of 0V, +3.5V or +2.05V is especially suspect.  
    1001 If this is the case, add a line <code>ignore vid</code> to <code>/etc/sensors.conf</code>, 
     1035If this is the case, add a line <span class="command">ignore vid</span> to <span class="file">/etc/sensors.conf</span>, 
    10021036and change the min and max settings for the Processor Core voltage 
    10031037(often in0_min and in0_max) in that file so that they don't depend on vid. 
    10041038 
    1005 <p><hr> 
    1006 Node:<a name="Section%204.8">Section 4.8</a>, 
    1007 Next:<a rel=next accesskey=n href="#Section%204.9">Section 4.9</a>, 
    1008 Previous:<a rel=previous accesskey=p href="#Section%204.7">Section 4.7</a>, 
    1009 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1010 <br> 
    1011  
    1012 <h3>4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3> 
     1039<div class="node"> 
     1040<p><hr> 
     1041<a name="Section-4_002e8"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e9">Section 4.9</a>, 
     1042Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e7">Section 4.7</a>, 
     1043Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1044<br> 
     1045</div> 
     1046 
     1047<h3 class="section">4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?</h3> 
    10131048 
    10141049<p>If we would read the registers more often, it would not find the 
    … …  
    10171052at all). 
    10181053 
    1019 <p><hr> 
    1020 Node:<a name="Section%204.9">Section 4.9</a>, 
    1021 Next:<a rel=next accesskey=n href="#Section%204.10">Section 4.10</a>, 
    1022 Previous:<a rel=previous accesskey=p href="#Section%204.8">Section 4.8</a>, 
    1023 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1024 <br> 
    1025  
    1026 <h3>4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3> 
     1054<div class="node"> 
     1055<p><hr> 
     1056<a name="Section-4_002e9"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e10">Section 4.10</a>, 
     1057Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e8">Section 4.8</a>, 
     1058Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1059<br> 
     1060</div> 
     1061 
     1062<h3 class="section">4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?</h3> 
    10271063 
    10281064<p>ISA bus access is fast, but SMBus access is really slow. If you have 
    … …  
    10311067while we are waiting for the transaction to finish. 
    10321068 
    1033 <p><hr> 
    1034 Node:<a name="Section%204.10">Section 4.10</a>, 
    1035 Next:<a rel=next accesskey=n href="#Section%204.11">Section 4.11</a>, 
    1036 Previous:<a rel=previous accesskey=p href="#Section%204.9">Section 4.9</a>, 
    1037 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1038 <br> 
    1039  
    1040 <h3>4.10 Can I be alerted when an ALARM occurs?</h3> 
     1069<div class="node"> 
     1070<p><hr> 
     1071<a name="Section-4_002e10"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e11">Section 4.11</a>, 
     1072Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e9">Section 4.9</a>, 
     1073Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1074<br> 
     1075</div> 
     1076 
     1077<h3 class="section">4.10 Can I be alerted when an ALARM occurs?</h3> 
    10411078 
    10421079<p>No, you can't; and it may well be never supported. 
    10431080 
    1044 <p>Almost no mainboard we have encountered have actually connected the 
     1081   <p>Almost no mainboard we have encountered have actually connected the 
    10451082IRQ-out pin of sensor chips. That means that we could enable IRQ reporting, but 
    10461083nothing would happen. Also, even if a motherboard has it connected, it is 
    … …  
    10481085facility, which means that almost nobody would be able to use it anyway. 
    10491086 
    1050 <p>The SMI interrupt is only available on a few types of chips. It is 
     1087   <p>The SMI interrupt is only available on a few types of chips. It is 
    10511088really a very obscure way to handle interrupts, and supporting it under Linux 
    10521089might be quite hard to do. 
    10531090 
    1054 <p>Your best bet would be to poll the alarm file with a user-land daemon 
     1091   <p>Your best bet would be to poll the alarm file with a user-land daemon 
    10551092which alerts you if an alarm is raised. I am not aware of any program which 
    10561093does the job, though you might want to examine one of the graphical monitor 
    10571094programs under X, see <a href="http://www2.lm-sensors.nu/~lm78/useful_addresses.html">http://www2.lm-sensors.nu/~lm78/useful_addresses.html</a> for addresses. 
    10581095 
    1059 <p><hr> 
    1060 Node:<a name="Section%204.11">Section 4.11</a>, 
    1061 Next:<a rel=next accesskey=n href="#Section%204.12">Section 4.12</a>, 
    1062 Previous:<a rel=previous accesskey=p href="#Section%204.10">Section 4.10</a>, 
    1063 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1064 <br> 
    1065  
    1066 <h3>4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3> 
     1096<div class="node"> 
     1097<p><hr> 
     1098<a name="Section-4_002e11"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e12">Section 4.12</a>, 
     1099Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e10">Section 4.10</a>, 
     1100Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1101<br> 
     1102</div> 
     1103 
     1104<h3 class="section">4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen).  Why?</h3> 
    10671105 
    10681106<p>Some chips which mainboard makers connect to the SMBus are not SMBus 
    … …  
    10721110Intel's SMBus standard. 
    10731111 
    1074 <p>Why did they connect these devices to the SMBus if they aren't 
     1112   <p>Why did they connect these devices to the SMBus if they aren't 
    10751113compatible?  Good question! :')  Actually, these devices may support being 
    10761114written to, but lock things up when they are read. 
    10771115 
    1078 <p><hr> 
    1079 Node:<a name="Section%204.12">Section 4.12</a>, 
    1080 Next:<a rel=next accesskey=n href="#Section%204.13">Section 4.13</a>, 
    1081 Previous:<a rel=previous accesskey=p href="#Section%204.11">Section 4.11</a>, 
    1082 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1083 <br> 
    1084  
    1085 <h3>4.12 My BIOS reports a much higher CPU temperature than your modules!</h3> 
     1116<div class="node"> 
     1117<p><hr> 
     1118<a name="Section-4_002e12"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e13">Section 4.13</a>, 
     1119Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e11">Section 4.11</a>, 
     1120Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1121<br> 
     1122</div> 
     1123 
     1124<h3 class="section">4.12 My BIOS reports a much higher CPU temperature than your modules!</h3> 
    10861125 
    10871126<p>We display the actual temperature of the sensor. This may not be the 
    … …  
    10931132in the module itself. You can do it through the configuration file, though: 
    10941133 
    1095 <br><pre>chip lm75-*-49                      # Or whatever chip this relates to 
    1096 label temp "Processor" 
    1097 compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula 
     1134<pre class="example">     chip lm75-*-49                      # Or whatever chip this relates to 
     1135     label temp "Processor" 
     1136     compute temp @*1.2+13,(@-13)/1.2    # Or whatever formula 
    10981137</pre> 
    1099  
    1100 <p><hr> 
    1101 Node:<a name="Section%204.13">Section 4.13</a>, 
    1102 Next:<a rel=next accesskey=n href="#Section%204.14">Section 4.14</a>, 
    1103 Previous:<a rel=previous accesskey=p href="#Section%204.12">Section 4.12</a>, 
    1104 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1105 <br> 
    1106  
    1107 <h3>4.13 I try to read the raw <code>/proc</code> files, but the values are strange?!?</h3> 
     1138   <div class="node"> 
     1139<p><hr> 
     1140<a name="Section-4_002e13"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e14">Section 4.14</a>, 
     1141Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e12">Section 4.12</a>, 
     1142Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1143<br> 
     1144</div> 
     1145 
     1146<h3 class="section">4.13 I try to read the raw <span class="file">/proc</span> files, but the values are strange?!?</h3> 
    11081147 
    11091148<p>Remember, these values do not take the configuration file 
    1110 <code>compute</code> lines in account. This is especially obvious for voltage readings 
     1149<span class="file">compute</span> lines in account. This is especially obvious for voltage readings 
    11111150(usually called in? or vin?). Use a program linked to libsensors (like 
    1112 the provided <code>sensors</code> program) instead. 
    1113  
    1114 <p><hr> 
    1115 Node:<a name="Section%204.14">Section 4.14</a>, 
    1116 Next:<a rel=next accesskey=n href="#Section%204.15">Section 4.15</a>, 
    1117 Previous:<a rel=previous accesskey=p href="#Section%204.13">Section 4.13</a>, 
    1118 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1119 <br> 
    1120  
    1121 <h3>4.14 How do I set new limits?</h3> 
    1122  
    1123 <p>Change the limit values in <code>/etc/sensors.conf</code> and then run 
    1124 <code>sensors -s</code>. 
    1125  
    1126 <p><a name="I%20set%20new%20limits%20and%20it%20didnt%20work"></a> 
    1127  
    1128 <h4>4.14.1 I set new limits and it didn't work?</h4> 
    1129  
    1130 <p>You forgot to run <code>sensors -s</code>. Put it in a <code>/etc/rc.d/...</code> file 
     1151the provided <span class="command">sensors</span> program) instead. 
     1152 
     1153<div class="node"> 
     1154<p><hr> 
     1155<a name="Section-4_002e14"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e15">Section 4.15</a>, 
     1156Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e13">Section 4.13</a>, 
     1157Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1158<br> 
     1159</div> 
     1160 
     1161<h3 class="section">4.14 How do I set new limits?</h3> 
     1162 
     1163<p>Change the limit values in <span class="file">/etc/sensors.conf</span> and then run 
     1164<span class="command">sensors -s</span>. 
     1165 
     1166   <p><a name="I-set-new-limits-and-it-didnt-work"></a> 
     1167 
     1168<h4 class="subsection">4.14.1 I set new limits and it didn't work?</h4> 
     1169 
     1170<p>You forgot to run <span class="command">sensors -s</span>. Put it in a <span class="file">/etc/rc.d/...</span> file 
    11311171after the modprobe lines to run at startup. 
    11321172 
    1133 <p><hr> 
    1134 Node:<a name="Section%204.15">Section 4.15</a>, 
    1135 Next:<a rel=next accesskey=n href="#Section%204.16">Section 4.16</a>, 
    1136 Previous:<a rel=previous accesskey=p href="#Section%204.14">Section 4.14</a>, 
    1137 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1138 <br> 
    1139  
    1140 <h3>4.15 Some sensors are doubly detected?</h3> 
     1173<div class="node"> 
     1174<p><hr> 
     1175<a name="Section-4_002e15"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e16">Section 4.16</a>, 
     1176Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e14">Section 4.14</a>, 
     1177Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1178<br> 
     1179</div> 
     1180 
     1181<h3 class="section">4.15 Some sensors are doubly detected?</h3> 
    11411182 
    11421183<p>Yes, this is still a problem. It is partially solved by alias detection 
    11431184and confidence values in sensors-detect, but it is really tough. 
    11441185 
    1145 <p>Double detections can be caused by two things: 
     1186   <p>Double detections can be caused by two things: 
    11461187sensors can be detected to both the ISA and the SMBus (and if you have 
    11471188loaded the approprate adapter drivers, it will be detected on both), and 
    11481189some chips simulate other chips (the Winbond W83781D simulates LM75 chips 
    11491190on the SMBus, for example). Remove the offending adapter or chip driver, or 
    1150 run sensors-detect and add the <code>ignore=</code> modprobe parameters it suggests. 
    1151  
    1152 <p><hr> 
    1153 Node:<a name="Section%204.16">Section 4.16</a>, 
    1154 Next:<a rel=next accesskey=n href="#Section%204.17">Section 4.17</a>, 
    1155 Previous:<a rel=previous accesskey=p href="#Section%204.15">Section 4.15</a>, 
    1156 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1157 <br> 
    1158  
    1159 <h3>4.16 I ran sensors-detect, but now I get very strange readings?!?</h3> 
     1191run sensors-detect and add the <span class="command">ignore=</span> modprobe parameters it suggests. 
     1192 
     1193<div class="node"> 
     1194<p><hr> 
     1195<a name="Section-4_002e16"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e17">Section 4.17</a>, 
     1196Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e15">Section 4.15</a>, 
     1197Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1198<br> 
     1199</div> 
     1200 
     1201<h3 class="section">4.16 I ran sensors-detect, but now I get very strange readings?!?</h3> 
    11601202 
    11611203<p>Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards 
    … …  
    11671209scan the PIIX4. 
    11681210 
    1169 <p><hr> 
    1170 Node:<a name="Section%204.17">Section 4.17</a>, 
    1171 Next:<a rel=next accesskey=n href="#Section%204.18">Section 4.18</a>, 
    1172 Previous:<a rel=previous accesskey=p href="#Section%204.16">Section 4.16</a>, 
    1173 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1174 <br> 
    1175  
    1176 <h3>4.17 Bad readings from particular chips</h3> 
     1211<div class="node"> 
     1212<p><hr> 
     1213<a name="Section-4_002e17"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e18">Section 4.18</a>, 
     1214Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e16">Section 4.16</a>, 
     1215Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1216<br> 
     1217</div> 
     1218 
     1219<h3 class="section">4.17 Bad readings from particular chips</h3> 
    11771220 
    11781221<p>See below for some particularly troublesome chips.  
    1179 Also be sure and check <code>doc/chips/xxxxx</code> for the particular driver. 
    1180  
    1181 <p><a name="Bad%20readings%20from%20the%20AS99127F"></a> 
    1182  
    1183 <h4>4.17.1 Bad readings from the AS99127F!</h4> 
     1222Also be sure and check <span class="file">doc/chips/xxxxx</span> for the particular driver. 
     1223 
     1224   <p><a name="Bad-readings-from-the-AS99127F"></a> 
     1225 
     1226<h4 class="subsection">4.17.1 Bad readings from the AS99127F!</h4> 
    11841227 
    11851228<p>The Asus AS99127F is a modified version of the Winbond W83781D.  
    11861229Asus will not release a datasheet. The driver was developed by tedious 
    11871230experimentation. We've done the best we can. If you want to make adjustments 
    1188 to the readings please edit <code>/etc/sensors.conf.</code> Please don't ask us to 
     1231to the readings please edit <span class="file">/etc/sensors.conf.</span> Please don't ask us to 
    11891232fix the driver. Ask Asus to release a datasheet. 
    11901233 
    1191 <p><a name="Bad%20readings%20from%20the%20VIA%20686A"></a> 
    1192  
    1193 <h4>4.17.2 Bad readings from the VIA 686A!</h4> 
     1234   <p><a name="Bad-readings-from-the-VIA-686A"></a> 
     1235 
     1236<h4 class="subsection">4.17.2 Bad readings from the VIA 686A!</h4> 
    11941237 
    11951238<p>The Via 686A datasheet is incomplete.  
    11961239Via will not release details. The driver was developed by tedious 
    11971240experimentation. We've done the best we can. If you want to make adjustments 
    1198 to the readings please edit <code>/etc/sensors.conf.</code> Please don't ask us to 
     1241to the readings please edit <span class="file">/etc/sensors.conf.</span> Please don't ask us to 
    11991242fix the driver. Ask Via to release a better datasheet.  
    1200 Also, don't forget to <code>modprobe i2c-isa</code>. 
    1201  
    1202 <p><a name="Bad%20readings%20from%20the%20MTP008"></a> 
    1203  
    1204 <h4>4.17.3 Bad readings from the MTP008!</h4> 
     1243Also, don't forget to <span class="command">modprobe i2c-isa</span>. 
     1244 
     1245   <p><a name="Bad-readings-from-the-MTP008"></a> 
     1246 
     1247<h4 class="subsection">4.17.3 Bad readings from the MTP008!</h4> 
    12051248 
    12061249<p>The MTP008 has programmable temperature sensor types.  
    12071250If your sensor type does not match the default, you will have to change it.  
    1208 See <code>doc/chips/mtp008</code> for details.  
     1251See <span class="file">doc/chips/mtp008</span> for details.  
    12091252Also, MTP008 chips seem to randomly refuse to respond, for 
    12101253unknown reasons. You can see this as 'XX' entries in i2cdump. 
    12111254 
    1212 <p><a name="Bad%20temperature%20readings%20from%20the%20SIS5595"></a> 
    1213  
    1214 <h4>4.17.4 Bad temperature readings from the SIS5595!</h4> 
     1255   <p><a name="Bad-temperature-readings-from-the-SIS5595"></a> 
     1256 
     1257<h4 class="subsection">4.17.4 Bad temperature readings from the SIS5595!</h4> 
    12151258 
    12161259<p>This chip can use multiple thermistor types and there are also 
    … …  
    12211264misidentified. We are working on improving that too. 
    12221265 
    1223 <p><a name="Bad%20readings%20from%20a%20w8378%5b12%5dd"></a> 
    1224  
    1225 <h4>4.17.5 Bad readings from a w8378[12]d!</h4> 
     1266   <p><a name="Bad-readings-from-a-w8378_005b12_005dd"></a> 
     1267 
     1268<h4 class="subsection">4.17.5 Bad readings from a w8378[12]d!</h4> 
    12261269 
    12271270<p>Do you own an ASUS motherboard?  Perhaps your chip is being 
    … …  
    12301273Often the real device is an Asus as99127f. If so, the driver can be 
    12311274forced to recognize the as99127f with 
    1232 <code>force_as99127f=BUS,0x2d</code> where <code>BUS</code> is your i2c bus number.  
     1275<span class="command">force_as99127f=BUS,0x2d</span> where <code>BUS</code> is your i2c bus number.  
    12331276Cat /proc/bus/i2c to see a list of bus numbers.  
    1234 Read the w83781d module documentation (<code>doc/chips/w83781d</code>) 
     1277Read the w83781d module documentation (<span class="file">doc/chips/w83781d</span>) 
    12351278for more details. 
    12361279 
    1237 <p><a name="Bus%20hangs%20on%20Ali%201543%20on%20Asus%20P5A%20boards"></a> 
    1238  
    1239 <h4>4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4> 
     1280   <p><a name="Bus-hangs-on-Ali-1543-on-Asus-P5A-boards"></a> 
     1281 
     1282<h4 class="subsection">4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!</h4> 
    12401283 
    12411284<p>The SMBus tends to hang on this board and it seems to get worse 
    12421285at higher temperatures. Use ISA accesses to reliably use the w83781d 
    1243 monitor chip on this board and use the <code>ignore=1,0x2d</code> or similar option 
     1286monitor chip on this board and use the <span class="command">ignore=1,0x2d</span> or similar option 
    12441287to the w83781d module to prevent i2c accesses. 
    12451288 
    1246 <p><a name="Bad%20readings%20from%20LM75"></a> 
    1247  
    1248 <h4>4.17.7 Bad readings from LM75!</h4> 
     1289   <p><a name="Bad-readings-from-LM75"></a> 
     1290 
     1291<h4 class="subsection">4.17.7 Bad readings from LM75!</h4> 
    12491292 
    12501293<p>The LM75 detection is poor and other hardware is often misdetected 
    1251 as an LM75. Figure out what you really have See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
    1252  
    1253 <p><a name="Bad%20readings%20from%20LM78"></a> 
    1254  
    1255 <h4>4.17.8 Bad readings from LM78!</h4> 
     1294as an LM75. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>. 
     1295 
     1296   <p><a name="Bad-readings-from-LM78"></a> 
     1297 
     1298<h4 class="subsection">4.17.8 Bad readings from LM78!</h4> 
    12561299 
    12571300<p>The LM78 is no longer manufactured by National Semiconductor.  
    12581301You probably don't have a real LM78 but something similar that we 
    1259 do not recogize or support. Figure out what you really have See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
    1260  
    1261 <p><a name="Bad%20readings%20from%20LM80"></a> 
    1262  
    1263 <h4>4.17.9 Bad readings from LM80!</h4> 
     1302do not recogize or support. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>. 
     1303 
     1304   <p><a name="Bad-readings-from-LM80"></a> 
     1305 
     1306<h4 class="subsection">4.17.9 Bad readings from LM80!</h4> 
    12641307 
    12651308<p>The LM80 detection is poor and other hardware is often misdetected 
    1266 as an LM80. Figure out what you really have See <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>. 
    1267  
    1268 <p><a name="Bad%20readings%20from%20it87"></a> 
    1269  
    1270 <h4>4.17.10 Bad readings from it87!</h4> 
     1309as an LM80. Figure out what you really have See <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>. 
     1310 
     1311   <p><a name="Bad-readings-from-it87"></a> 
     1312 
     1313<h4 class="subsection">4.17.10 Bad readings from it87!</h4> 
    12711314 
    12721315<p>The it87 temperature sesnsors are configured, unfortunately, 
    12731316in a way different from w83781d. They cannot be configured from 
    1274 <code>/etc/sensors.conf</code>; they must be set at modprobe insertion with 
    1275 <code>modprobe it87 temp_type=0xXX</code>. See <code>doc/chips/it87</code> for details. 
    1276  
    1277 <p><hr> 
    1278 Node:<a name="Section%204.18">Section 4.18</a>, 
    1279 Next:<a rel=next accesskey=n href="#Section%204.19">Section 4.19</a>, 
    1280 Previous:<a rel=previous accesskey=p href="#Section%204.17">Section 4.17</a>, 
    1281 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1282 <br> 
    1283  
    1284 <h3>4.18 How do I configure two chips (LM87) differently?</h3> 
     1317<span class="file">/etc/sensors.conf</span>; they must be set at modprobe insertion with 
     1318<span class="command">modprobe it87 temp_type=0xXX</span>. See <span class="file">doc/chips/it87</span> for details. 
     1319 
     1320<div class="node"> 
     1321<p><hr> 
     1322<a name="Section-4_002e18"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e19">Section 4.19</a>, 
     1323Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e17">Section 4.17</a>, 
     1324Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1325<br> 
     1326</div> 
     1327 
     1328<h3 class="section">4.18 How do I configure two chips (LM87) differently?</h3> 
    12851329 
    12861330<p>There is a SuperMicro board with two LM87's on it that are 
    … …  
    12881332For example, both CPU temperatures go to one LM87. 
    12891333 
    1290 <p>Make two different sections in <code>/etc/sensors.conf</code> as follows: 
    1291 <br><pre>chip "lm87-i2c-*-2c" 
    1292     put configuration for the chip at 0x2c here 
    1293 chip "lm87-i2c-*-2d" 
    1294     put configuration for the chip at 0x2d here 
     1334   <p>Make two different sections in <span class="file">/etc/sensors.conf</span> as follows: 
     1335<pre class="example">     chip "lm87-i2c-*-2c" 
     1336         put configuration for the chip at 0x2c here 
     1337     chip "lm87-i2c-*-2d" 
     1338         put configuration for the chip at 0x2d here 
    12951339</pre> 
    1296  
    1297 <p>There is a commented example in <code>sensors.conf.eg</code> which should 
     1340   <p>There is a commented example in <span class="file">sensors.conf.eg</span> which should 
    12981341be helpful. 
    12991342 
    1300 <p><hr> 
    1301 Node:<a name="Section%204.19">Section 4.19</a>, 
    1302 Next:<a rel=next accesskey=n href="#Section%204.20">Section 4.20</a>, 
    1303 Previous:<a rel=previous accesskey=p href="#Section%204.18">Section 4.18</a>, 
    1304 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1305 <br> 
    1306  
    1307 <h3>4.19 Dmesg says <code>Upgrade BIOS</code>! I don't want to!</h3> 
    1308  
    1309 <p>If the problem is a PCI device is not present in <code>lspci</code>, the solution 
     1343<div class="node"> 
     1344<p><hr> 
     1345<a name="Section-4_002e19"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e20">Section 4.20</a>, 
     1346Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e18">Section 4.18</a>, 
     1347Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1348<br> 
     1349</div> 
     1350 
     1351<h3 class="section">4.19 Dmesg says <span class="samp">Upgrade BIOS</span>! I don't want to!</h3> 
     1352 
     1353<p>If the problem is a PCI device is not present in <span class="command">lspci</span>, the solution 
    13101354is complex. For the ALI M7101 device, there is a solution which uses the 
    1311 2.4 kernel's <code>hotplug</code> facility. See <code>prog/hotplug</code> in our package.  
     13552.4 kernel's <span class="command">hotplug</span> facility. See <span class="file">prog/hotplug</span> in our package.  
    13121356For other PCI devices, you can try to modify 
    1313 the m7101 solution in <code>prog/hotplug</code>. 
    1314  
    1315 <p>If dmesg says <code>try force_addr</code>, see below. Other drivers generally do not 
     1357the m7101 solution in <span class="file">prog/hotplug</span>. 
     1358 
     1359   <p>If dmesg says <span class="samp">try force_addr</span>, see below. Other drivers generally do not 
    13161360support the force_addr parameter. Sorry. Check the documentation 
    1317 for your driver in <code>doc/[chips,busses]</code> and if we don't support it 
     1361for your driver in <span class="file">doc/[chips,busses]</span> and if we don't support it 
    13181362you can send us your request. 
    13191363 
    1320 <p><a name="Dmesg%20says%20use%20force_addr%3d0xaddr!%20What%20address%20do%20I%20use"></a> 
    1321  
    1322 <h4>4.19.1 Dmesg says <code>use force_addr=0xaddr</code>! What address do I use?</h4> 
     1364   <p><a name="Dmesg-says-use-force_005faddr_003d0xaddr_0021-What-address-do-I-use"></a> 
     1365 
     1366<h4 class="subsection">4.19.1 Dmesg says <span class="samp">use force_addr=0xaddr</span>! What address do I use?</h4> 
    13231367 
    13241368<p>If the problem is a PCI device whose base address is not set, 
    13251369you may be able to set the address with a force parameter. The via686a 
    13261370and sis5595 chip drivers, and some bus drivers, support the command line 
    1327 <code>modprobe via686a force_addr=0xADDRESS</code> where ADDRESS 
     1371<span class="command">modprobe via686a force_addr=0xADDRESS</span> where ADDRESS 
    13281372is the I/O address. You must select an address that is not in use.  
    1329 <code>cat <code>/proc/ioports</code></code> to check (carefully) for conflicts. A high number like 
     1373<span class="command">cat /proc/ioports</span> to check (carefully) for conflicts. A high number like 
    133013740xf000 is generally safe. 
    13311375 
    1332 <p><hr> 
    1333 Node:<a name="Section%204.20">Section 4.20</a>, 
    1334 Next:<a rel=next accesskey=n href="#Section%204.21">Section 4.21</a>, 
    1335 Previous:<a rel=previous accesskey=p href="#Section%204.19">Section 4.19</a>, 
    1336 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1337 <br> 
    1338  
    1339 <h3>4.20 Sensors says <code>Can't access procfs/sysfs file</code></h3> 
    1340  
    1341 <ul> 
    1342 <li>(Linux 2.6) Did you <code>modprobe i2c_sensor</code>? Check <code>lsmod</code>.  
    1343 <li>(Linux 2.4) Did you <code>modprobe i2c-proc</code>? Check <code>lsmod</code>.  
    1344 <li>If you did <code>sensors -s</code>, did you run it as root?  
    1345 <li>(Linux 2.6) Do you have sysfs support in your kernel (is <code>/sys</code> there and populated)?  
    1346 <li>(Linux 2.4) Do you have procfs support in your kernel (is <code>/proc</code> there and populated)?  
    1347 </ul> 
    1348  
    1349 <p><hr> 
    1350 Node:<a name="Section%204.21">Section 4.21</a>, 
    1351 Next:<a rel=next accesskey=n href="#Section%204.22">Section 4.22</a>, 
    1352 Previous:<a rel=previous accesskey=p href="#Section%204.20">Section 4.20</a>, 
    1353 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1354 <br> 
    1355  
    1356 <h3>4.21 Sensors says <code>No sensors found!</code></h3> 
    1357  
    1358 <ul> 
    1359 <li>Did <code>sensors-detect</code> find sensors? (If not see <a href="#Sensors-detect%20doesnt%20find%20any%20sensors">Sensors-detect doesnt find any sensors</a>) 
    1360 <li>Did you do what <code>sensors-detect</code> said?  
    1361 <li>Did you <code>modprobe</code> your sensor modules?  
    1362 <li>Did you <code>modprobe</code> your I2C adapter modules?  
    1363 <li>Did you <code>modprobe i2c-isa</code> if you have ISA sensor chips?  
    1364 <li>Check <code>lsmod</code>.  
    1365 </ul> 
    1366  
    1367 <p><hr> 
    1368 Node:<a name="Section%204.22">Section 4.22</a>, 
    1369 Next:<a rel=next accesskey=n href="#Section%204.23">Section 4.23</a>, 
    1370 Previous:<a rel=previous accesskey=p href="#Section%204.21">Section 4.21</a>, 
    1371 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1372 <br> 
    1373  
    1374 <h3>4.22 Sensors output is not correct!</h3> 
     1376<div class="node"> 
     1377<p><hr> 
     1378<a name="Section-4_002e20"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e21">Section 4.21</a>, 
     1379Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e19">Section 4.19</a>, 
     1380Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1381<br> 
     1382</div> 
     1383 
     1384<h3 class="section">4.20 Sensors says <span class="samp">Can't access procfs/sysfs file</span></h3> 
     1385 
     1386     <ul> 
     1387<li>(Linux 2.6) Did you <span class="command">modprobe i2c_sensor</span>? Check <span class="command">lsmod</span>.  
     1388<li>(Linux 2.4) Did you <span class="command">modprobe i2c-proc</span>? Check <span class="command">lsmod</span>.  
     1389<li>If you did <span class="command">sensors -s</span>, did you run it as root?  
     1390<li>(Linux 2.6) Do you have sysfs support in your kernel (is <span class="file">/sys</span> there and populated)?  
     1391<li>(Linux 2.4) Do you have procfs support in your kernel (is <span class="file">/proc</span> there and populated)?  
     1392</ul> 
     1393 
     1394<div class="node"> 
     1395<p><hr> 
     1396<a name="Section-4_002e21"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e22">Section 4.22</a>, 
     1397Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e20">Section 4.20</a>, 
     1398Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1399<br> 
     1400</div> 
     1401 
     1402<h3 class="section">4.21 Sensors says <span class="samp">No sensors found!</span></h3> 
     1403 
     1404     <ul> 
     1405<li>Did <span class="command">sensors-detect</span> find sensors? (If not see <a href="#Sensors_002ddetect-doesnt-find-any-sensors">Sensors-detect doesnt find any sensors</a>) 
     1406<li>Did you do what <span class="command">sensors-detect</span> said?  
     1407<li>Did you <span class="command">modprobe</span> your sensor modules?  
     1408<li>Did you <span class="command">modprobe</span> your I2C adapter modules?  
     1409<li>Did you <span class="command">modprobe i2c-isa</span> if you have ISA sensor chips?  
     1410<li>Check <span class="command">lsmod</span>.  
     1411</ul> 
     1412 
     1413<div class="node"> 
     1414<p><hr> 
     1415<a name="Section-4_002e22"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e23">Section 4.23</a>, 
     1416Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e21">Section 4.21</a>, 
     1417Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1418<br> 
     1419</div> 
     1420 
     1421<h3 class="section">4.22 Sensors output is not correct!</h3> 
    13751422 
    13761423<p>What specifically is the trouble? 
    1377 <ul> 
    1378 <li>Labels: See <a href="#Section%203.4.1">The labels for the voltage and temperature readings in sensors are incorrect</a>.  
    1379 <li>Min/max readings: See <a href="#Section%203.4.2">The min and max for the readings in sensors are incorrect</a>, and See <a href="#Section%203.4.3">The min and max settings didnt take effect</a>.  
    1380 <li>AS99127F: See <a href="#Section%204.16">I ran sensors-detect but now I get very strange readings?</a>.  
    1381 <li>Via 686A: See <a href="#Section%204.16">I ran sensors-detect but now I get very strange readings?</a>.  
    1382 <li>Other specific chips: See <a href="#Section%204.16">I ran sensors-detect but now I get very strange readings?</a>.  
    1383 <li>No output for a particular sensors chip: See <a href="#Section%205.3">What to do if it inserts but nothing happens</a>.  
    1384 <li>No output at all: See <a href="#Section%204.21">Sensors says No sensors found</a>, See <a href="#Section%205.3">What to do if it inserts but nothing happens</a>.  
    1385 <li>Completely bad output for a particular sensor chip: See <a href="#Section%205.4">What to do if I read only bogus information</a>.  
     1424     <ul> 
     1425<li>Labels: See <a href="#Section-3_002e4_002e1">The labels for the voltage and temperature readings in sensors are incorrect</a>.  
     1426<li>Min/max readings: See <a href="#Section-3_002e4_002e2">The min and max for the readings in sensors are incorrect</a>, and See <a href="#Section-3_002e4_002e3">The min and max settings didnt take effect</a>.  
     1427<li>AS99127F: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.  
     1428<li>Via 686A: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.  
     1429<li>Other specific chips: See <a href="#Section-4_002e16">I ran sensors-detect but now I get very strange readings?</a>.  
     1430<li>No output for a particular sensors chip: See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>.  
     1431<li>No output at all: See <a href="#Section-4_002e21">Sensors says No sensors found</a>, See <a href="#Section-5_002e3">What to do if it inserts but nothing happens</a>.  
     1432<li>Completely bad output for a particular sensor chip: See <a href="#Section-5_002e4">What to do if I read only bogus information</a>.  
    13861433<li>One particular sensor readings: 
    1387 <ul> 
    1388 <li>Maybe it isn't hooked up? - tell 'sensors' to ignore it. See <a href="#Section%203.4.4">One sensor isnt hooked up on my board</a>.  
    1389 <li>Maybe it is hooked up differently on your motherboard? - adjust <code>sensors.conf</code> calculation.  
    1390 </ul> 
    1391 </ul> 
    1392  
    1393 <p><hr> 
    1394 Node:<a name="Section%204.23">Section 4.23</a>, 
    1395 Next:<a rel=next accesskey=n href="#Section%204.24">Section 4.24</a>, 
    1396 Previous:<a rel=previous accesskey=p href="#Section%204.22">Section 4.22</a>, 
    1397 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1398 <br> 
    1399  
    1400 <h3>4.23 What is at I2C address XXX?</h3> 
    1401  
    1402 <p>In general, we don't know. Start by running <code>sensors-detect</code>.  
    1403 If it doesn't recognize it, try running <code>i2cdump</code>. A partial list 
    1404 of manufacturers' IDs are at the bottom of <code>doc/chips/SUMMARY</code>. 
    1405  
    1406 <p><a name="What%20is%20at%20I2C%20address%200x69"></a> 
    1407  
    1408 <h4>4.23.1 What is at I2C address 0x69?</h4> 
     1434          <ul> 
     1435<li>Maybe it isn't hooked up? - tell 'sensors' to ignore it. See <a href="#Section-3_002e4_002e4">One sensor isnt hooked up on my board</a>.  
     1436<li>Maybe it is hooked up differently on your motherboard? - adjust <span class="file">sensors.conf</span> calculation.  
     1437</ul> 
     1438     </ul> 
     1439 
     1440<div class="node"> 
     1441<p><hr> 
     1442<a name="Section-4_002e23"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e24">Section 4.24</a>, 
     1443Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e22">Section 4.22</a>, 
     1444Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1445<br> 
     1446</div> 
     1447 
     1448<h3 class="section">4.23 What is at I2C address XXX?</h3> 
     1449 
     1450<p>In general, we don't know. Start by running <span class="command">sensors-detect</span>.  
     1451If it doesn't recognize it, try running <span class="command">i2cdump</span>. A partial list 
     1452of manufacturers' IDs are at the bottom of <span class="file">doc/chips/SUMMARY</span>. 
     1453 
     1454   <p><a name="What-is-at-I2C-address-0x69"></a> 
     1455 
     1456<h4 class="subsection">4.23.1 What is at I2C address 0x69?</h4> 
    14091457 
    14101458<p>A clock chip. Often, accessing these clock chips in the wrong 
    14111459way will instantly crash your computer. Sensors-detect carefully 
    14121460avoids these chips. If you really really want to play with your clock 
    1413 chip you can look at <code>kernel/chips/icspll.c</code> in our package. But we 
     1461chip you can look at <span class="file">kernel/chips/icspll.c</span> in our package. But we 
    14141462do not recommend it. You have been warned. 
    14151463 
    1416 <p><a name="What%20is%20at%20I2C%20addresses%200x50%20-%200x57"></a> 
    1417  
    1418 <h4>4.23.2 What is at I2C addresses 0x50 - 0x57?</h4> 
     1464   <p><a name="What-is-at-I2C-addresses-0x50-_002d-0x57"></a> 
     1465 
     1466<h4 class="subsection">4.23.2 What is at I2C addresses 0x50 - 0x57?</h4> 
    14191467 
    14201468<p>EEPROMs on your SDRAM DIMMs. Load the eeprom module to 
    1421 look at some basic data in <code>sensors</code> or use the program 
    1422 <code>prog/eeprom/decode-dimms.pl</code> to get more information than you ever wanted. 
    1423  
    1424 <p><a name="What%20is%20at%20I2C%20addresses%200x30%20-%200x37"></a> 
    1425  
    1426 <h4>4.23.3 What is at I2C addresses 0x30 - 0x37?</h4> 
     1469look at some basic data in <span class="command">sensors</span> or use the program 
     1470<span class="command">prog/eeprom/decode-dimms.pl</span> to get more information than you ever wanted. 
     1471 
     1472   <p><a name="What-is-at-I2C-addresses-0x30-_002d-0x37"></a> 
     1473 
     1474<h4 class="subsection">4.23.3 What is at I2C addresses 0x30 - 0x37?</h4> 
    14271475 
    14281476<p>These are often 'shadows' of your EEPROMs on your SDRAM DIMMs 
    … …  
    14301478registers of the SDRAM Serial Presence Detect EEPROMs.  
    14311479If you try and 
    1432 do a <code>i2cdump</code> on them to read the location, you won't get anything, 
     1480do a <span class="command">i2cdump</span> on them to read the location, you won't get anything, 
    14331481because they contain a single write-only register.  
    14341482This register can be used to permanently 
    14351483write-protect the contents of the eeprom. 
    14361484 
    1437 <p><hr> 
    1438 Node:<a name="Section%204.24">Section 4.24</a>, 
    1439 Next:<a rel=next accesskey=n href="#Section%204.25">Section 4.25</a>, 
    1440 Previous:<a rel=previous accesskey=p href="#Section%204.23">Section 4.23</a>, 
    1441 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1442 <br> 
    1443  
    1444 <h3>4.24 Sensors-detect doesn't work at all</h3> 
    1445  
    1446 <p>It could be many things. What was the problem? See <a href="#Section%204.31">Problems on particular motherboards</a>. 
    1447  
    1448 <p><a name="Sensors-detect%20says%20%22Couldnt%20open%20%2fproc%2fbus%2fi2c%3f!%3f%22"></a> 
    1449  
    1450 <h4>4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4> 
     1485<div class="node"> 
     1486<p><hr> 
     1487<a name="Section-4_002e24"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e25">Section 4.25</a>, 
     1488Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e23">Section 4.23</a>, 
     1489Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1490<br> 
     1491</div> 
     1492 
     1493<h3 class="section">4.24 Sensors-detect doesn't work at all</h3> 
     1494 
     1495<p>It could be many things. What was the problem? See <a href="#Section-4_002e31">Problems on particular motherboards</a>. 
     1496 
     1497   <p><a name="Sensors_002ddetect-says-_0022Couldnt-open-_002fproc_002fbus_002fi2c_003f_0021_003f_0022"></a> 
     1498 
     1499<h4 class="subsection">4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"</h4> 
    14511500 
    14521501<p>You don't have i2c support in your kernel, or the i2c-core module 
    14531502was not loaded and you did not run sensors-detect as root. 
    14541503 
    1455 <p><a name="Sensors-detect%20says%20%22Cant%20open%20%2fdev%2fi2c%5b-%2f%5d0%22"></a> 
    1456  
    1457 <h4>4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4> 
    1458  
    1459 <p>Your <code>/dev/i2c-0,</code> <code>/dev/i2c0</code>, or <code>/dev/i2c/0</code> files do not exist 
    1460 or you did not run <code>sensors-detect</code> as root.  
    1461 Run the script <code>prog/mkdev/mkdev.sh</code> to create the <code>/dev/i2c-x</code> files.  
    1462 Run <code>devfs</code> in the kernel to get the <code>/dev/i2c/x</code> files. 
    1463  
    1464 <p><a name="Sensors-detect%20doesnt%20find%20any%20sensors"></a> 
    1465  
    1466 <h4>4.24.3 Sensors-detect doesn't find any sensors!</h4> 
     1504   <p><a name="Sensors_002ddetect-says-_0022Cant-open-_002fdev_002fi2c_005b_002d_002f_005d0_0022"></a> 
     1505 
     1506<h4 class="subsection">4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"</h4> 
     1507 
     1508<p>Your <span class="file">/dev/i2c-0,</span> <span class="file">/dev/i2c0</span>, or <span class="file">/dev/i2c/0</span> files do not exist 
     1509or you did not run <span class="command">sensors-detect</span> as root.  
     1510Run the script <span class="command">prog/mkdev/mkdev.sh</span> to create the <span class="file">/dev/i2c-x</span> files.  
     1511Run <span class="command">devfs</span> in the kernel to get the <span class="file">/dev/i2c/x</span> files. 
     1512 
     1513   <p><a name="Sensors_002ddetect-doesnt-find-any-sensors"></a> 
     1514 
     1515<h4 class="subsection">4.24.3 Sensors-detect doesn't find any sensors!</h4> 
    14671516 
    14681517<p>Either 
    1469 <ol type=1 start=1> 
    1470 </p><li>The board doesn't have any sensors.  
     1518     <ol type=1 start=1> 
     1519<li>The board doesn't have any sensors.  
    14711520<li>We don't support the sensors on the board.  
    14721521<li>The sensors it has are on an I2C bus connected to an I2C bus adapter that we don't support.  
    14731522<li>You don't have the latest version of lm_sensors. 
    1474 </ol> 
    1475  
    1476 <p>But in any case you should figure out what is on the board: 
    1477 <ol type=1 start=1> 
    1478 </p><li>Look at your motherboard.  
     1523        </ol> 
     1524 
     1525   <p>But in any case you should figure out what is on the board: 
     1526     <ol type=1 start=1> 
     1527<li>Look at your motherboard.  
    14791528<li>Check the manufacturer's website.  
    14801529<li>Check the <a href="http://mbm.livewiredev.com/">Motherboard Monitor</a> website. 
    1481 </ol> 
    1482  
    1483 <p>When you know what chips you have, check the 
     1530        </ol> 
     1531 
     1532   <p>When you know what chips you have, check the 
    14841533<a href="http://www2.lm-sensors.nu/~lm78/newdrivers.html">Newest Driver Status</a> web page to 
    14851534see if support has been added for your chip in a later release or in CVS. 
    14861535 
    1487 <p><hr> 
    1488 Node:<a name="Section%204.25">Section 4.25</a>, 
    1489 Next:<a rel=next accesskey=n href="#Section%204.26">Section 4.26</a>, 
    1490 Previous:<a rel=previous accesskey=p href="#Section%204.24">Section 4.24</a>, 
    1491 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1492 <br> 
    1493  
    1494 <h3>4.25 Sensors says <code>Error: Line xxx: zzzzzzz</code></h3> 
     1536<div class="node"> 
     1537<p><hr> 
     1538<a name="Section-4_002e25"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e26">Section 4.26</a>, 
     1539Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e24">Section 4.24</a>, 
     1540Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1541<br> 
     1542</div> 
     1543 
     1544<h3 class="section">4.25 Sensors says <span class="samp">Error: Line xxx: zzzzzzz</span></h3> 
    14951545 
    14961546<p>These are errors from the libsensors library in 
    1497 reading the <code>/etc/sensors.conf</code> configuration file. Go to that line 
     1547reading the <span class="file">/etc/sensors.conf</span> configuration file. Go to that line 
    14981548number and fix it. If you have a parse error, perhaps you have 
    14991549to put the feature name in double quotes. 
    15001550 
    1501 <p><hr> 
    1502 Node:<a name="Section%204.26">Section 4.26</a>, 
    1503 Next:<a rel=next accesskey=n href="#Section%204.27">Section 4.27</a>, 
    1504 Previous:<a rel=previous accesskey=p href="#Section%204.25">Section 4.25</a>, 
    1505 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1506 <br> 
    1507  
    1508 <h3>4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3> 
    1509  
    1510 <p>If <code>sensors</code> only says this, for example, and doesn't 
     1551<div class="node"> 
     1552<p><hr> 
     1553<a name="Section-4_002e26"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e27">Section 4.27</a>, 
     1554Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e25">Section 4.25</a>, 
     1555Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1556<br> 
     1557</div> 
     1558 
     1559<h3 class="section">4.26 Sensors only gives the name, adapter, and algorithm for my chip</h3> 
     1560 
     1561<p>If <span class="command">sensors</span> only says this, for example, and doesn't 
    15111562provide any actual data at all: 
    15121563 
    1513 <br><pre>it87-isa-0290 
    1514 Adapter: ISA adapter 
    1515 Algorithm: ISA algorithm 
     1564<pre class="example">     it87-isa-0290 
     1565     Adapter: ISA adapter 
     1566     Algorithm: ISA algorithm 
    15161567</pre> 
    1517  
    1518 <p>Your chip is not currently supported by <code>sensors</code> and so all it 
     1568   <p>Your chip is not currently supported by <span class="command">sensors</span> and so all it 
    15191569does is print out that information. Get the latest release 
    1520 and be sure you are running the <code>sensors</code> program it installed 
    1521 and not some older <code>sensors</code>. 
    1522  
    1523 <p><hr> 
    1524 Node:<a name="Section%204.27">Section 4.27</a>, 
    1525 Next:<a rel=next accesskey=n href="#Section%204.28">Section 4.28</a>, 
    1526 Previous:<a rel=previous accesskey=p href="#Section%204.26">Section 4.26</a>, 
    1527 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1528 <br> 
    1529  
    1530 <h3>4.27 Sensors says <code>ERROR: Can't get xxxxx data!</code></h3> 
    1531  
    1532 <ul> 
     1570and be sure you are running the <span class="command">sensors</span> program it installed 
     1571and not some older <span class="command">sensors</span>. 
     1572 
     1573<div class="node"> 
     1574<p><hr> 
     1575<a name="Section-4_002e27"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e28">Section 4.28</a>, 
     1576Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e26">Section 4.26</a>, 
     1577Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1578<br> 
     1579</div> 
     1580 
     1581<h3 class="section">4.27 Sensors says <span class="samp">ERROR: Can't get xxxxx data!</span></h3> 
     1582 
     1583     <ul> 
    15331584<li>(Linux 2.6) Make sure you are using one of the 
    15341585<a href="http://secure.netroedge.com/~lm78/kernel26.html">recommended kernel/lm_sensors combination</a>.  
    1535 <li>You have a <code>libsensors</code>/<code>sensors</code> mismatch.  
    1536 <code>sensors</code> is unable to 
    1537 get a data entry from <code>libsensors</code>. You probably have an 
    1538 old <code>libsensors</code> in your <code>/etc/ld.so.conf</code> path.  
    1539 Make sure you did (as root) a <code>make install</code> (Linux 2.4) or 
    1540 <code>make user_install</code> (Linux 2.6) followed by a <code>ldconfig</code>.  
    1541 Then check the output of <code>ldconfig -v | grep libsensors</code> to 
    1542 verify that there is only ONE <code>libsensors</code> entry and that it matches 
    1543 the <code>libsensors</code> that was built in the <code>lib/</code> directory in <code>lm_sensors2</code>.  
    1544 </ul> 
    1545  
    1546 <p><hr> 
    1547 Node:<a name="Section%204.28">Section 4.28</a>, 
    1548 Next:<a rel=next accesskey=n href="#Section%204.29">Section 4.29</a>, 
    1549 Previous:<a rel=previous accesskey=p href="#Section%204.27">Section 4.27</a>, 
    1550 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1551 <br> 
    1552  
    1553 <h3>4.28 Sensors doesn't find any sensors, just eeproms.</h3> 
    1554  
    1555 <p>See <a href="#Section%204.24">Sensors-detect doesnt work at all</a>, if <code>sensors-detect</code> failed to find any sensors. 
    1556  
    1557 <p>If <code>sensors-detect</code> did find sensors, did you insert your modules? For chips on the ISA 
     1586<li>You have a <span class="file">libsensors</span>/<span class="command">sensors</span> mismatch.  
     1587<span class="command">sensors</span> is unable to 
     1588get a data entry from <span class="file">libsensors</span>. You probably have an 
     1589old <span class="file">libsensors</span> in your <span class="file">/etc/ld.so.conf</span> path.  
     1590Make sure you did (as root) a <span class="command">make install</span> (Linux 2.4) or 
     1591<span class="command">make user_install</span> (Linux 2.6) followed by a <span class="command">ldconfig</span>.  
     1592Then check the output of <span class="command">ldconfig -v | grep libsensors</span> to 
     1593verify that there is only ONE <span class="file">libsensors</span> entry and that it matches 
     1594the <span class="file">libsensors</span> that was built in the <span class="file">lib/</span> directory in <span class="file">lm_sensors2</span>.  
     1595</ul> 
     1596 
     1597<div class="node"> 
     1598<p><hr> 
     1599<a name="Section-4_002e28"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e29">Section 4.29</a>, 
     1600Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e27">Section 4.27</a>, 
     1601Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1602<br> 
     1603</div> 
     1604 
     1605<h3 class="section">4.28 Sensors doesn't find any sensors, just eeproms.</h3> 
     1606 
     1607<p>See <a href="#Section-4_002e24">Sensors-detect doesnt work at all</a>, if <span class="command">sensors-detect</span> failed to find any sensors. 
     1608 
     1609   <p>If <span class="command">sensors-detect</span> did find sensors, did you insert your modules? For chips on the ISA 
    15581610bus, did you insert i2c-isa? 
    15591611 
    1560 <p>See <a href="#Section%205.2">What to do if a module wont insert</a>, if the modules didn't insert, 
    1561 also <a href="#Section%204.21">Sensors says No sensors found</a>. 
    1562  
    1563 <p><hr> 
    1564 Node:<a name="Section%204.29">Section 4.29</a>, 
    1565 Next:<a rel=next accesskey=n href="#Section%204.30">Section 4.30</a>, 
    1566 Previous:<a rel=previous accesskey=p href="#Section%204.28">Section 4.28</a>, 
    1567 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1568 <br> 
    1569  
    1570 <h3>4.29 Inserting modules hangs my board</h3> 
     1612   <p>See <a href="#Section-5_002e2">What to do if a module wont insert</a>, if the modules didn't insert, 
     1613also <a href="#Section-4_002e21">Sensors says No sensors found</a>. 
     1614 
     1615<div class="node"> 
     1616<p><hr> 
     1617<a name="Section-4_002e29"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e30">Section 4.30</a>, 
     1618Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e28">Section 4.28</a>, 
     1619Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1620<br> 
     1621</div> 
     1622 
     1623<h3 class="section">4.29 Inserting modules hangs my board</h3> 
    15711624 
    15721625<p>There are several possible causes: 
    1573 <ol type=1 start=1> 
    1574 </p><li>Bus driver problems. Insert the bus driver first, before you have inserted any chip drivers, to verify.  
    1575 <li>Wrong chip driver. Verify that you have a chip supported by the chip driver, see <a href="#Section%203.2.1">What chips are on motherboard XYZ</a>.  
    1576 <li>The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS.  Try the parameter <code>init=0</code> for the w83781d driver; this is the only driver supporting this parameter.  
    1577 <li>Some chips on the bus don't like to be probed at all.  After inserting the bus driver (but not the chip drivers), run <code>i2cdetect</code> on the bus, then <code>i2cdump</code> on each address responding to <code>i2cdetect</code>. This may find the culprit.  Do not <code>i2cdump address 0x69</code>, the clock chip.  
    1578 <li>The chip driver is incorrectly finding a second chip on the bus and is accessing it. For example, with the Tyan 2688 with a w83781d at 0x29, use <code>modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f</code> to prevent access to other addresses. (<code>init=0</code> also req'd for the Tyan 2688). 
    1579 </ol> 
    1580  
    1581 <p><hr> 
    1582 Node:<a name="Section%204.30">Section 4.30</a>, 
    1583 Next:<a rel=next accesskey=n href="#Section%204.31">Section 4.31</a>, 
    1584 Previous:<a rel=previous accesskey=p href="#Section%204.29">Section 4.29</a>, 
    1585 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1586 <br> 
    1587  
    1588 <h3>4.30 Inserting modules slows down my board</h3> 
     1626     <ol type=1 start=1> 
     1627<li>Bus driver problems. Insert the bus driver first, before you have inserted any chip drivers, to verify.  
     1628<li>Wrong chip driver. Verify that you have a chip supported by the chip driver, see <a href="#Section-3_002e2_002e1">What chips are on motherboard XYZ</a>.  
     1629<li>The chip driver is reinitializing the chip, which undoes critical initialization done by the BIOS.  Try the parameter <span class="command">init=0</span> for the w83781d driver; this is the only driver supporting this parameter.  
     1630<li>Some chips on the bus don't like to be probed at all.  After inserting the bus driver (but not the chip drivers), run <span class="command">i2cdetect</span> on the bus, then <span class="command">i2cdump</span> on each address responding to <span class="command">i2cdetect</span>. This may find the culprit.  Do not <span class="command">i2cdump address 0x69</span>, the clock chip.  
     1631<li>The chip driver is incorrectly finding a second chip on the bus and is accessing it. For example, with the Tyan 2688 with a w83781d at 0x29, use <span class="command">modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f</span> to prevent access to other addresses. (<span class="command">init=0</span> also req'd for the Tyan 2688). 
     1632        </ol> 
     1633 
     1634<div class="node"> 
     1635<p><hr> 
     1636<a name="Section-4_002e30"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e31">Section 4.31</a>, 
     1637Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e29">Section 4.29</a>, 
     1638Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1639<br> 
     1640</div> 
     1641 
     1642<h3 class="section">4.30 Inserting modules slows down my board</h3> 
    15891643 
    15901644<p>Generally this is caused by an overtemperature alarm output from 
    … …  
    15921646automatically slows down the CPU clock. Be sure that your 
    15931647temperature limits are above the temperature reading. Put 
    1594 the new limits in <code>/etc/sensors.conf</code> and run <code>sensors -s</code>. 
    1595  
    1596 <p><hr> 
    1597 Node:<a name="Section%204.31">Section 4.31</a>, 
    1598 Next:<a rel=next accesskey=n href="#Section%204.32">Section 4.32</a>, 
    1599 Previous:<a rel=previous accesskey=p href="#Section%204.30">Section 4.30</a>, 
    1600 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1601 <br> 
    1602  
    1603 <h3>4.31 Problems on particular motherboards</h3> 
     1648the new limits in <span class="file">/etc/sensors.conf</span> and run <span class="command">sensors -s</span>. 
     1649 
     1650<div class="node"> 
     1651<p><hr> 
     1652<a name="Section-4_002e31"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e32">Section 4.32</a>, 
     1653Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e30">Section 4.30</a>, 
     1654Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1655<br> 
     1656</div> 
     1657 
     1658<h3 class="section">4.31 Problems on particular motherboards</h3> 
    16041659 
    16051660<p>The following boards have unique problems and solutions. 
    16061661 
    1607 <p><a name="Asus%20P4B"></a> 
    1608  
    1609 <h4>4.31.1 Asus P4B</h4> 
    1610  
    1611 <p>See <code>prog/hotplug/README.p4b</code> if your SMBus master is not found. 
    1612  
    1613 <p><a name="Tyan%202460%202462"></a> 
    1614  
    1615 <h4>4.31.2 Tyan 2460, 2462</h4> 
     1662   <p><a name="Asus-P4B"></a> 
     1663 
     1664<h4 class="subsection">4.31.1 Asus P4B</h4> 
     1665 
     1666<p>See <span class="file">prog/hotplug/README.p4b</span> if your SMBus master is not found. 
     1667 
     1668   <p><a name="Tyan-2460-2462"></a> 
     1669 
     1670<h4 class="subsection">4.31.2 Tyan 2460, 2462</h4> 
    16161671 
    16171672<p>See support tickets 805, 765, 781, 812, 813, and 867 for information. 
    16181673 
    1619 <p><a name="Tyan%202466"></a> 
    1620  
    1621 <h4>4.31.3 Tyan 2466</h4> 
     1674   <p><a name="Tyan-2466"></a> 
     1675 
     1676<h4 class="subsection">4.31.3 Tyan 2466</h4> 
    16221677 
    16231678<p>See support tickets 941, 840, and 841 for information. 
    16241679 
    1625 <p><a name="Tyan%202688"></a> 
    1626  
    1627 <h4>4.31.4 Tyan 2688</h4> 
     1680   <p><a name="Tyan-2688"></a> 
     1681 
     1682<h4 class="subsection">4.31.4 Tyan 2688</h4> 
    16281683 
    16291684<p>For board hangs, see support ticket 721 for information.  
    1630 Also <a href="#Section%204.29">Inserting modules hangs my board</a>. 
    1631  
    1632 <p><hr> 
    1633 Node:<a name="Section%204.32">Section 4.32</a>, 
    1634 Next:<a rel=next accesskey=n href="#Section%204.33">Section 4.33</a>, 
    1635 Previous:<a rel=previous accesskey=p href="#Section%204.31">Section 4.31</a>, 
    1636 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1637 <br> 
    1638  
    1639 <h3>4.32 Problems on particular systems</h3> 
    1640  
    1641 <p>For IBM systems, see <code>README.thinkpad</code>. 
    1642  
    1643 <p><hr> 
    1644 Node:<a name="Section%204.33">Section 4.33</a>, 
    1645 Previous:<a rel=previous accesskey=p href="#Section%204.32">Section 4.32</a>, 
    1646 Up:<a rel=up accesskey=u href="#Problems">Problems</a> 
    1647 <br> 
    1648  
    1649 <h3>4.33 Problems on 2.6 kernels</h3> 
     1685Also <a href="#Section-4_002e29">Inserting modules hangs my board</a>. 
     1686 
     1687<div class="node"> 
     1688<p><hr> 
     1689<a name="Section-4_002e32"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-4_002e33">Section 4.33</a>, 
     1690Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e31">Section 4.31</a>, 
     1691Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1692<br> 
     1693</div> 
     1694 
     1695<h3 class="section">4.32 Problems on particular systems</h3> 
     1696 
     1697<p>For IBM systems, see <span class="file">README.thinkpad</span>. 
     1698 
     1699<div class="node"> 
     1700<p><hr> 
     1701<a name="Section-4_002e33"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-4_002e32">Section 4.32</a>, 
     1702Up:&nbsp;<a rel="up" accesskey="u" href="#Problems">Problems</a> 
     1703<br> 
     1704</div> 
     1705 
     1706<h3 class="section">4.33 Problems on 2.6 kernels</h3> 
    16501707 
    16511708<p>Not all drivers have been ported to 2.6. If your favorite driver is not 
    … …  
    16561713then send us the ported driver when you are done. 
    16571714 
    1658 <p><hr> 
    1659 Node:<a name="Help">Help</a>, 
    1660 Next:<a rel=next accesskey=n href="#Contribute">Contribute</a>, 
    1661 Previous:<a rel=previous accesskey=p href="#Problems">Problems</a>, 
    1662 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1663 <br> 
    1664  
    1665 <h2>5 How to Ask for Help</h2> 
    1666  
    1667 <ul> 
    1668 <li><a accesskey=1 href="#Section%205.1">Section 5.1</a>:   What to send us when asking for help 
    1669 <li><a accesskey=2 href="#Section%205.2">Section 5.2</a>:   What to do if a module won't insert?  
    1670 <li><a accesskey=3 href="#Section%205.3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
    1671 <li><a accesskey=4 href="#Section%205.4">Section 5.4</a>:   What to do if I read only bogus information?  
    1672 <li><a accesskey=5 href="#Section%205.5">Section 5.5</a>:   What to do if you have other problems?  
    1673 <li><a accesskey=6 href="#Section%205.6">Section 5.6</a>:   What if it just works like a charm?  
    1674 <li><a accesskey=7 href="#Section%205.7">Section 5.7</a>:   How do I update a ticket?  
    1675 <li><a accesskey=8 href="#Section%205.8">Section 5.8</a>:   How do I follow up on a ticket?  
    1676 </ul> 
    1677  
    1678 <p><hr> 
    1679 Node:<a name="Section%205.1">Section 5.1</a>, 
    1680 Next:<a rel=next accesskey=n href="#Section%205.2">Section 5.2</a>, 
    1681 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1682 <br> 
    1683  
    1684 <h3>5.1 What to send us when asking for help</h3> 
     1715<div class="node"> 
     1716<p><hr> 
     1717<a name="Help"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Contribute">Contribute</a>, 
     1718Previous:&nbsp;<a rel="previous" accesskey="p" href="#Problems">Problems</a>, 
     1719Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     1720<br> 
     1721</div> 
     1722 
     1723<h2 class="chapter">5 How to Ask for Help</h2> 
     1724 
     1725<ul class="menu"> 
     1726<li><a accesskey="1" href="#Section-5_002e1">Section 5.1</a>:   What to send us when asking for help 
     1727<li><a accesskey="2" href="#Section-5_002e2">Section 5.2</a>:   What to do if a module won't insert?  
     1728<li><a accesskey="3" href="#Section-5_002e3">Section 5.3</a>:   What to do if it inserts, but nothing happens?  
     1729<li><a accesskey="4" href="#Section-5_002e4">Section 5.4</a>:   What to do if I read only bogus information?  
     1730<li><a accesskey="5" href="#Section-5_002e5">Section 5.5</a>:   What to do if you have other problems?  
     1731<li><a accesskey="6" href="#Section-5_002e6">Section 5.6</a>:   What if it just works like a charm?  
     1732<li><a accesskey="7" href="#Section-5_002e7">Section 5.7</a>:   How do I update a ticket?  
     1733<li><a accesskey="8" href="#Section-5_002e8">Section 5.8</a>:   How do I follow up on a ticket?  
     1734</ul> 
     1735 
     1736<div class="node"> 
     1737<p><hr> 
     1738<a name="Section-5_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e2">Section 5.2</a>, 
     1739Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1740<br> 
     1741</div> 
     1742 
     1743<h3 class="section">5.1 What to send us when asking for help</h3> 
    16851744 
    16861745<p>We are always willing to answer questions if things don't work out.  
    … …  
    16881747unless you have something private to say. 
    16891748 
    1690 <p>Instead of using email, you can also use the web-based support 
     1749   <p>Instead of using email, you can also use the web-based support 
    16911750area, at <a href="http://secure.netroedge.com/~lm78/support.html">http://secure.netroedge.com/~lm78/support.html</a>. You will be helped 
    16921751just as fast, and others may profit from the answer too. You will be 
    16931752emailed automatically when your question has been answered. 
    16941753 
    1695 <p>Here's what you should send us: 
    1696  
    1697 <ul> 
     1754   <p>Here's what you should send us: 
     1755 
     1756     <ul> 
    16981757<li>The dmesg or syslog output if applicable 
    1699 <li>The output of (as root) <code>prog/detect/sensors-detect</code> 
    1700 <li>The output of <code>lsmod</code> 
     1758<li>The output of (as root) <span class="command">prog/detect/sensors-detect</span> 
     1759<li>The output of <span class="command">lsmod</span> 
    17011760<li>If a PCI chip problem: 
    1702 <ul> 
    1703 <li>The output of <code>lspci -n</code> 
    1704 </ul> 
    1705 <li>If an I2C sensor chip problem: 
    1706 <ul> 
    1707 <li>The output of (as root) <code>prog/detect/i2cdetect X</code> 
    1708 where X = the bus number (run <code>i2cdetect</code> with no arguments to list the busses) 
    1709 (please send this only if it's not all <code>XX</code>) 
    1710 <li>The output of (as root) <code>prog/dump/i2cdump X 0xXX</code> 
    1711 where XX = the address of each chip you see in the output of <code>i2cdetect</code>. (run once for each chip) 
    1712 (please send this only if it's not all <code>ff</code>) 
    1713 </ul> 
    1714 <li>If an ISA sensor chip problem: 
    1715 <ul> 
    1716 <li>The output of (as root) <code>prog/dump/isadump 0x295 0x296</code> (only if it's not all <code>XX</code>) 
    1717 </ul> 
    1718 <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard) 
     1761          <ul> 
     1762<li>The output of <span class="command">lspci -n</span> 
     1763</ul> 
     1764     <li>If an I2C sensor chip problem: 
     1765          <ul> 
     1766<li>The output of (as root) <span class="command">prog/detect/i2cdetect X</span> 
     1767where X = the bus number (run <span class="command">i2cdetect</span> with no arguments to list the busses) 
     1768(please send this only if it's not all <span class="samp">XX</span>) 
     1769<li>The output of (as root) <span class="command">prog/dump/i2cdump X 0xXX</span> 
     1770where XX = the address of each chip you see in the output of <span class="command">i2cdetect</span>. (run once for each chip) 
     1771(please send this only if it's not all <span class="samp">ff</span>) 
     1772</ul> 
     1773     <li>If an ISA sensor chip problem: 
     1774          <ul> 
     1775<li>The output of (as root) <span class="command">prog/dump/isadump 0x295 0x296</span> (only if it's not all <span class="samp">XX</span>) 
     1776</ul> 
     1777     <li>Part numbers of chips on your motherboard you think are the sensor chips (look at your motherboard) 
    17191778<li>Motherboard type 
    17201779<li>Sensors version 
    … …  
    17221781</ul> 
    17231782 
    1724 <p><hr> 
    1725 Node:<a name="Section%205.2">Section 5.2</a>, 
    1726 Next:<a rel=next accesskey=n href="#Section%205.3">Section 5.3</a>, 
    1727 Previous:<a rel=previous accesskey=p href="#Section%205.1">Section 5.1</a>, 
    1728 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1729 <br> 
    1730  
    1731 <h3>5.2 What to do if a module won't insert?</h3> 
    1732  
    1733 <p>Did you use <code>modprobe</code> instead of <code>insmod</code>??? Don't use insmod. 
    1734  
    1735 <p>Were there unresolved symbols? Did you run <code>depmod -a</code>? Run 
    1736 <code>depmod -a -e</code> to see where the symbol problem is. 
    1737  
    1738 <p>ALWAYS inspect the output of <code>dmesg</code>. That's where the error 
    1739 messages come out!!! Don't rely on the generic message from <code>modprobe</code>.  
     1783<div class="node"> 
     1784<p><hr> 
     1785<a name="Section-5_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e3">Section 5.3</a>, 
     1786Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e1">Section 5.1</a>, 
     1787Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1788<br> 
     1789</div> 
     1790 
     1791<h3 class="section">5.2 What to do if a module won't insert?</h3> 
     1792 
     1793<p>Did you use <span class="command">modprobe</span> instead of <span class="command">insmod</span>??? Don't use insmod. 
     1794 
     1795   <p>Were there unresolved symbols? Did you run <span class="command">depmod -a</span>? Run 
     1796<span class="command">depmod -a -e</span> to see where the symbol problem is. 
     1797 
     1798   <p>ALWAYS inspect the output of <span class="command">dmesg</span>. That's where the error 
     1799messages come out!!! Don't rely on the generic message from <span class="command">modprobe</span>.  
    17401800If you still can't figure it out, send us the information 
    17411801listed above. 
    17421802 
    1743 <p><hr> 
    1744 Node:<a name="Section%205.3">Section 5.3</a>, 
    1745 Next:<a rel=next accesskey=n href="#Section%205.4">Section 5.4</a>, 
    1746 Previous:<a rel=previous accesskey=p href="#Section%205.2">Section 5.2</a>, 
    1747 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1748 <br> 
    1749  
    1750 <h3>5.3 What to do if it inserts, but nothing happens?</h3> 
    1751  
    1752 <p>For an ISA sensor chip, did you also <code>modprobe i2c-isa</code>? It must be inserted. 
    1753  
    1754 <p>For an I2C sensor chip, did you also <code>modprobe i2c-xxx</code> where xxx is your 
     1803<div class="node"> 
     1804<p><hr> 
     1805<a name="Section-5_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e4">Section 5.4</a>, 
     1806Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e2">Section 5.2</a>, 
     1807Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1808<br> 
     1809</div> 
     1810 
     1811<h3 class="section">5.3 What to do if it inserts, but nothing happens?</h3> 
     1812 
     1813<p>For an ISA sensor chip, did you also <span class="command">modprobe i2c-isa</span>? It must be inserted. 
     1814 
     1815   <p>For an I2C sensor chip, did you also <span class="command">modprobe i2c-xxx</span> where xxx is your 
    17551816I2C bus adapter? It must be inserted. 
    17561817 
    1757 <p>Always inspect the output of <code>dmesg</code>. That's where the error 
     1818   <p>Always inspect the output of <span class="command">dmesg</span>. That's where the error 
    17581819messages come out. If you still can't figure it out, send us the information 
    17591820listed above. 
    17601821 
    1761 <p><hr> 
    1762 Node:<a name="Section%205.4">Section 5.4</a>, 
    1763 Next:<a rel=next accesskey=n href="#Section%205.5">Section 5.5</a>, 
    1764 Previous:<a rel=previous accesskey=p href="#Section%205.3">Section 5.3</a>, 
    1765 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1766 <br> 
    1767  
    1768 <h3>5.4 What to do if I read only bogus information?</h3> 
     1822<div class="node"> 
     1823<p><hr> 
     1824<a name="Section-5_002e4"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e5">Section 5.5</a>, 
     1825Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e3">Section 5.3</a>, 
     1826Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1827<br> 
     1828</div> 
     1829 
     1830<h3 class="section">5.4 What to do if I read only bogus information?</h3> 
    17691831 
    17701832<p>It may be that this was a mis-detection: the chip may not be 
    … …  
    17741836please send us the usual information (see <a href="#Help">Help</a>) 
    17751837 
    1776 <p><hr> 
    1777 Node:<a name="Section%205.5">Section 5.5</a>, 
    1778 Next:<a rel=next accesskey=n href="#Section%205.6">Section 5.6</a>, 
    1779 Previous:<a rel=previous accesskey=p href="#Section%205.4">Section 5.4</a>, 
    1780 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1781 <br> 
    1782  
    1783 <h3>5.5 What to do if you have other problems?</h3> 
     1838<div class="node"> 
     1839<p><hr> 
     1840<a name="Section-5_002e5"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e6">Section 5.6</a>, 
     1841Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e4">Section 5.4</a>, 
     1842Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1843<br> 
     1844</div> 
     1845 
     1846<h3 class="section">5.5 What to do if you have other problems?</h3> 
    17841847 
    17851848<p>Again, send the output listed above. 
    17861849 
    1787 <p><hr> 
    1788 Node:<a name="Section%205.6">Section 5.6</a>, 
    1789 Next:<a rel=next accesskey=n href="#Section%205.7">Section 5.7</a>, 
    1790 Previous:<a rel=previous accesskey=p href="#Section%205.5">Section 5.5</a>, 
    1791 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1792 <br> 
    1793  
    1794 <h3>5.6 What if it just works like a charm?</h3> 
     1850<div class="node"> 
     1851<p><hr> 
     1852<a name="Section-5_002e6"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e7">Section 5.7</a>, 
     1853Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e5">Section 5.5</a>, 
     1854Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1855<br> 
     1856</div> 
     1857 
     1858<h3 class="section">5.6 What if it just works like a charm?</h3> 
    17951859 
    17961860<p>Drop us a mail if you feel like it, mentioning the mainboard and 
    17971861detected chip type. That way, we have some positive feedback, too! 
    17981862 
    1799 <p><hr> 
    1800 Node:<a name="Section%205.7">Section 5.7</a>, 
    1801 Next:<a rel=next accesskey=n href="#Section%205.8">Section 5.8</a>, 
    1802 Previous:<a rel=previous accesskey=p href="#Section%205.6">Section 5.6</a>, 
    1803 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1804 <br> 
    1805  
    1806 <h3>5.7 How do I update a ticket?</h3> 
     1863<div class="node"> 
     1864<p><hr> 
     1865<a name="Section-5_002e7"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-5_002e8">Section 5.8</a>, 
     1866Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e6">Section 5.6</a>, 
     1867Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1868<br> 
     1869</div> 
     1870 
     1871<h3 class="section">5.7 How do I update a ticket?</h3> 
    18071872 
    18081873<p>You can't. Only developers can. Follow up by emailing us 
    … …  
    18111876follow-up information, email us instead. Thanks. 
    18121877 
    1813 <p><hr> 
    1814 Node:<a name="Section%205.8">Section 5.8</a>, 
    1815 Previous:<a rel=previous accesskey=p href="#Section%205.7">Section 5.7</a>, 
    1816 Up:<a rel=up accesskey=u href="#Help">Help</a> 
    1817 <br> 
    1818  
    1819 <h3>5.8 How do I follow up on a ticket?</h3> 
     1878<div class="node"> 
     1879<p><hr> 
     1880<a name="Section-5_002e8"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-5_002e7">Section 5.7</a>, 
     1881Up:&nbsp;<a rel="up" accesskey="u" href="#Help">Help</a> 
     1882<br> 
     1883</div> 
     1884 
     1885<h3 class="section">5.8 How do I follow up on a ticket?</h3> 
    18201886 
    18211887<p>Follow up by emailing us at <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> 
    18221888and reference your ticket number in the subject. 
    18231889 
    1824 <p><hr> 
    1825 Node:<a name="Contribute">Contribute</a>, 
    1826 Next:<a rel=next accesskey=n href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    1827 Previous:<a rel=previous accesskey=p href="#Help">Help</a>, 
    1828 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1829 <br> 
    1830  
    1831 <h2>6 How to Contribute</h2> 
    1832  
    1833 <ul> 
    1834 <li><a accesskey=1 href="#Section%206.1">Section 6.1</a>:   How to write a driver 
    1835 <li><a accesskey=2 href="#Section%206.2">Section 6.2</a>:   How to get CVS access 
    1836 <li><a accesskey=3 href="#Section%206.3">Section 6.3</a>:   How to donate hardware to the project 
    1837 <li><a accesskey=4 href="#Section%206.4">Section 6.4</a>:   How to join the project mailing list 
    1838 <li><a accesskey=5 href="#Section%206.5">Section 6.5</a>:   How to access mailing list archives 
    1839 <li><a accesskey=6 href="#Section%206.6">Section 6.6</a>:   How to submit a patch 
    1840 <li><a accesskey=7 href="#Section%206.7">Section 6.7</a>:   How to REALLY help 
    1841 <li><a accesskey=8 href="#Section%206.8">Section 6.8</a>:   How to get release announcements 
    1842 <li><a accesskey=9 href="#Section%206.9">Section 6.9</a>:   How to block spam on the project mailing list 
    1843 </ul> 
    1844  
    1845 <p><hr> 
    1846 Node:<a name="Section%206.1">Section 6.1</a>, 
    1847 Next:<a rel=next accesskey=n href="#Section%206.2">Section 6.2</a>, 
    1848 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1849 <br> 
    1850  
    1851 <h3>6.1 How to write a driver</h3> 
    1852  
    1853 <p>See <code>doc/developers/new_drivers</code> in our package for instructions. 
    1854  
    1855 <p><hr> 
    1856 Node:<a name="Section%206.2">Section 6.2</a>, 
    1857 Next:<a rel=next accesskey=n href="#Section%206.3">Section 6.3</a>, 
    1858 Previous:<a rel=previous accesskey=p href="#Section%206.1">Section 6.1</a>, 
    1859 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1860 <br> 
    1861  
    1862 <h3>6.2 How to get CVS access</h3> 
     1890<div class="node"> 
     1891<p><hr> 
     1892<a name="Contribute"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Version-1-Specifics">Version 1 Specifics</a>, 
     1893Previous:&nbsp;<a rel="previous" accesskey="p" href="#Help">Help</a>, 
     1894Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     1895<br> 
     1896</div> 
     1897 
     1898<h2 class="chapter">6 How to Contribute</h2> 
     1899 
     1900<ul class="menu"> 
     1901<li><a accesskey="1" href="#Section-6_002e1">Section 6.1</a>:   How to write a driver 
     1902<li><a accesskey="2" href="#Section-6_002e2">Section 6.2</a>:   How to get CVS access 
     1903<li><a accesskey="3" href="#Section-6_002e3">Section 6.3</a>:   How to donate hardware to the project 
     1904<li><a accesskey="4" href="#Section-6_002e4">Section 6.4</a>:   How to join the project mailing list 
     1905<li><a accesskey="5" href="#Section-6_002e5">Section 6.5</a>:   How to access mailing list archives 
     1906<li><a accesskey="6" href="#Section-6_002e6">Section 6.6</a>:   How to submit a patch 
     1907<li><a accesskey="7" href="#Section-6_002e7">Section 6.7</a>:   How to REALLY help 
     1908<li><a accesskey="8" href="#Section-6_002e8">Section 6.8</a>:   How to get release announcements 
     1909<li><a accesskey="9" href="#Section-6_002e9">Section 6.9</a>:   How to block spam on the project mailing list 
     1910</ul> 
     1911 
     1912<div class="node"> 
     1913<p><hr> 
     1914<a name="Section-6_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e2">Section 6.2</a>, 
     1915Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1916<br> 
     1917</div> 
     1918 
     1919<h3 class="section">6.1 How to write a driver</h3> 
     1920 
     1921<p>See <span class="file">doc/developers/new_drivers</span> in our package for instructions. 
     1922 
     1923<div class="node"> 
     1924<p><hr> 
     1925<a name="Section-6_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e3">Section 6.3</a>, 
     1926Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e1">Section 6.1</a>, 
     1927Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1928<br> 
     1929</div> 
     1930 
     1931<h3 class="section">6.2 How to get CVS access</h3> 
    18631932 
    18641933<p>For anonymous CVS read access, see the instructions on our download page.  
    18651934Sorry, we don't have automatically generated CVS tarballs. 
    18661935 
    1867 <p>For write access, run the script <code>doc/developers/genpasswd.pl</code> in 
     1936   <p>For write access, run the script <span class="command">doc/developers/genpasswd.pl</span> in 
    18681937our package and follow the instructions. Let us know what part 
    18691938of the package you would like to work on. 
    18701939 
    1871 <p><hr> 
    1872 Node:<a name="Section%206.3">Section 6.3</a>, 
    1873 Next:<a rel=next accesskey=n href="#Section%206.4">Section 6.4</a>, 
    1874 Previous:<a rel=previous accesskey=p href="#Section%206.2">Section 6.2</a>, 
    1875 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1876 <br> 
    1877  
    1878 <h3>6.3 How to donate hardware to the project</h3> 
     1940<div class="node"> 
     1941<p><hr> 
     1942<a name="Section-6_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e4">Section 6.4</a>, 
     1943Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e2">Section 6.2</a>, 
     1944Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1945<br> 
     1946</div> 
     1947 
     1948<h3 class="section">6.3 How to donate hardware to the project</h3> 
    18791949 
    18801950<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. 
    18811951 
    1882 <p><hr> 
    1883 Node:<a name="Section%206.4">Section 6.4</a>, 
    1884 Next:<a rel=next accesskey=n href="#Section%206.5">Section 6.5</a>, 
    1885 Previous:<a rel=previous accesskey=p href="#Section%206.3">Section 6.3</a>, 
    1886 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1887 <br> 
    1888  
    1889 <h3>6.4 How to join the project mailing list</h3> 
     1952<div class="node"> 
     1953<p><hr> 
     1954<a name="Section-6_002e4"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e5">Section 6.5</a>, 
     1955Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e3">Section 6.3</a>, 
     1956Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1957<br> 
     1958</div> 
     1959 
     1960<h3 class="section">6.4 How to join the project mailing list</h3> 
    18901961 
    18911962<p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a>. Sorry, 
    … …  
    18971968CC'd on all replies. 
    18981969 
    1899 <p><hr> 
    1900 Node:<a name="Section%206.5">Section 6.5</a>, 
    1901 Next:<a rel=next accesskey=n href="#Section%206.6">Section 6.6</a>, 
    1902 Previous:<a rel=previous accesskey=p href="#Section%206.4">Section 6.4</a>, 
    1903 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1904 <br> 
    1905  
    1906 <h3>6.5 How to access mailing list archives</h3> 
     1970<div class="node"> 
     1971<p><hr> 
     1972<a name="Section-6_002e5"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e6">Section 6.6</a>, 
     1973Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e4">Section 6.4</a>, 
     1974Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1975<br> 
     1976</div> 
     1977 
     1978<h3 class="section">6.5 How to access mailing list archives</h3> 
    19071979 
    19081980<p>The mailing list archive is at: <a href="http://archives.andrew.net.au/lm-sensors">http://archives.andrew.net.au/lm-sensors</a> 
    19091981Sorry, it only contains messages since October 28, 2001. 
    19101982 
    1911 <p><hr> 
    1912 Node:<a name="Section%206.6">Section 6.6</a>, 
    1913 Next:<a rel=next accesskey=n href="#Section%206.7">Section 6.7</a>, 
    1914 Previous:<a rel=previous accesskey=p href="#Section%206.5">Section 6.5</a>, 
    1915 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1916 <br> 
    1917  
    1918 <h3>6.6 How to submit a patch</h3> 
     1983<div class="node"> 
     1984<p><hr> 
     1985<a name="Section-6_002e6"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e7">Section 6.7</a>, 
     1986Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e5">Section 6.5</a>, 
     1987Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     1988<br> 
     1989</div> 
     1990 
     1991<h3 class="section">6.6 How to submit a patch</h3> 
    19191992 
    19201993<p>Check out the latest from CVS, then copy the directory to another 
    19211994directory, and make your changes. Generate the diff with 
    1922 <code>diff -u2 -r DIR1 DIR2</code>. Or you can generate the diff in CVS with 
    1923 <code>cvs diff -u2</code>. Send us the patch in an email and tell us what it does. 
    1924  
    1925 <p><hr> 
    1926 Node:<a name="Section%206.7">Section 6.7</a>, 
    1927 Next:<a rel=next accesskey=n href="#Section%206.8">Section 6.8</a>, 
    1928 Previous:<a rel=previous accesskey=p href="#Section%206.6">Section 6.6</a>, 
    1929 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1930 <br> 
    1931  
    1932 <h3>6.7 How to REALLY help</h3> 
     1995<span class="command">diff -u2 -r DIR1 DIR2</span>. Or you can generate the diff in CVS with 
     1996<span class="command">cvs diff -u2</span>. Send us the patch in an email and tell us what it does. 
     1997 
     1998<div class="node"> 
     1999<p><hr> 
     2000<a name="Section-6_002e7"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e8">Section 6.8</a>, 
     2001Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e6">Section 6.6</a>, 
     2002Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     2003<br> 
     2004</div> 
     2005 
     2006<h3 class="section">6.7 How to REALLY help</h3> 
    19332007 
    19342008<p>Believe it or not, what we really need help with are: 
    1935 <ul> 
     2009     <ul> 
    19362010<li>Answering email 
    19372011<li>Answering support tickets 
    … …  
    19412015</ul> 
    19422016 
    1943 <p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> if you can help.  
     2017   <p>Send us email <a href="mailto:sensors@stimpy.netroedge.com">sensors@stimpy.netroedge.com</a> if you can help.  
    19442018No experience necessary :) 
    19452019 
    1946 <p><hr> 
    1947 Node:<a name="Section%206.8">Section 6.8</a>, 
    1948 Next:<a rel=next accesskey=n href="#Section%206.9">Section 6.9</a>, 
    1949 Previous:<a rel=previous accesskey=p href="#Section%206.7">Section 6.7</a>, 
    1950 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1951 <br> 
    1952  
    1953 <h3>6.8 How to get release announcements</h3> 
     2020<div class="node"> 
     2021<p><hr> 
     2022<a name="Section-6_002e8"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-6_002e9">Section 6.9</a>, 
     2023Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e7">Section 6.7</a>, 
     2024Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     2025<br> 
     2026</div> 
     2027 
     2028<h3 class="section">6.8 How to get release announcements</h3> 
    19542029 
    19552030<p>We don't have a separate release announcement mailing list; 
    … …  
    19592034will email you announcement. 
    19602035 
    1961 <p><hr> 
    1962 Node:<a name="Section%206.9">Section 6.9</a>, 
    1963 Previous:<a rel=previous accesskey=p href="#Section%206.8">Section 6.8</a>, 
    1964 Up:<a rel=up accesskey=u href="#Contribute">Contribute</a> 
    1965 <br> 
    1966  
    1967 <h3>6.9 How to block spam on the project mailing list</h3> 
     2036<div class="node"> 
     2037<p><hr> 
     2038<a name="Section-6_002e9"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-6_002e8">Section 6.8</a>, 
     2039Up:&nbsp;<a rel="up" accesskey="u" href="#Contribute">Contribute</a> 
     2040<br> 
     2041</div> 
     2042 
     2043<h3 class="section">6.9 How to block spam on the project mailing list</h3> 
    19682044 
    19692045<p>Sorry, we know the spam is a hassle.  It would be nice to have a 
    … …  
    19772053versa), but it seems to be about 95% accurate in our experience. 
    19782054 
    1979 <p><hr> 
    1980 Node:<a name="Version%201%20Specifics">Version 1 Specifics</a>, 
    1981 Next:<a rel=next accesskey=n href="#Document%20Revisions">Document Revisions</a>, 
    1982 Previous:<a rel=previous accesskey=p href="#Contribute">Contribute</a>, 
    1983 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    1984 <br> 
    1985  
    1986 <h2>7 Version 1 Specific Questions</h2> 
    1987  
    1988 <ul> 
    1989 <li><a accesskey=1 href="#Section%207.1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
    1990 <li><a accesskey=2 href="#Section%207.2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
    1991 <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.  
    1992 <li><a accesskey=4 href="#Section%207.4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
     2055<div class="node"> 
     2056<p><hr> 
     2057<a name="Version-1-Specifics"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Document-Revisions">Document Revisions</a>, 
     2058Previous:&nbsp;<a rel="previous" accesskey="p" href="#Contribute">Contribute</a>, 
     2059Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     2060<br> 
     2061</div> 
     2062 
     2063<h2 class="chapter">7 Version 1 Specific Questions</h2> 
     2064 
     2065<ul class="menu"> 
     2066<li><a accesskey="1" href="#Section-7_002e1">Section 7.1</a>:   My mainboard has an SMBus, your code can't find it.  Why?  
     2067<li><a accesskey="2" href="#Section-7_002e2">Section 7.2</a>:   The modules won't load, saying 'SMBus not detected'.  
     2068<li><a accesskey="3" href="#Section-7_002e3">Section 7.3</a>:   I get a "No sensor data yet (try again in a few moments)" msg.  
     2069<li><a accesskey="4" href="#Section-7_002e4">Section 7.4</a>:   On my Dell, a LM80 is detected, but all readings are 0!  
    19932070</ul> 
    19942071 
    19952072<p>Note: Version 1 is very very old and is not recommended. 
    19962073 
    1997 <p><hr> 
    1998 Node:<a name="Section%207.1">Section 7.1</a>, 
    1999 Next:<a rel=next accesskey=n href="#Section%207.2">Section 7.2</a>, 
    2000 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2001 <br> 
    2002  
    2003 <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> 
     2074<div class="node"> 
     2075<p><hr> 
     2076<a name="Section-7_002e1"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e2">Section 7.2</a>, 
     2077Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a> 
     2078<br> 
     2079</div> 
     2080 
     2081<h3 class="section">7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it.  What's wrong?</h3> 
    20042082 
    20052083<p>Currently, our code only assumes that an SMBus exists if it originates 
    … …  
    20092087where the SMBus is hosted. 
    20102088 
    2011 <p>Regarding the VIA chip set(s): 
    2012  
    2013 <p>Right now, the SMBus code depends on the Intel PIIX4 chip to handle 
     2089   <p>Regarding the VIA chip set(s): 
     2090 
     2091   <p>Right now, the SMBus code depends on the Intel PIIX4 chip to handle 
    20142092SMBus transactions.  The VIA chip set is NOT supported at this time because 
    20152093it forces much of the SMBus protocol to be implemented by software. 
    20162094 
    2017 <p>To implement the SMBus correctly with the VIA chip, it needs to be 
     2095   <p>To implement the SMBus correctly with the VIA chip, it needs to be 
    20182096written at a low level to be quick.  A more attractive alternative is to 
    20192097use the Bios SMBus interface (not always available nor standard). 
    20202098 
    2021 <p>Version 2 supports the VIA chipset, and will support other chipsets.  
     2099   <p>Version 2 supports the VIA chipset, and will support other chipsets.  
    20222100Version 1 never will. 
    20232101 
    2024 <p><hr> 
    2025 Node:<a name="Section%207.2">Section 7.2</a>, 
    2026 Next:<a rel=next accesskey=n href="#Section%207.3">Section 7.3</a>, 
    2027 Previous:<a rel=previous accesskey=p href="#Section%207.1">Section 7.1</a>, 
    2028 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2029 <br> 
    2030  
    2031 <h3>7.2 The modules won't load, saying 'SMBus not detected'.</h3> 
     2102<div class="node"> 
     2103<p><hr> 
     2104<a name="Section-7_002e2"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e3">Section 7.3</a>, 
     2105Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e1">Section 7.1</a>, 
     2106Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a> 
     2107<br> 
     2108</div> 
     2109 
     2110<h3 class="section">7.2 The modules won't load, saying 'SMBus not detected'.</h3> 
    20322111 
    20332112<p>This should no longer be an issue in 1.4.10 and later; it will 
    20342113continue loading, but it won't support SMBus-connected devices, of course. 
    20352114 
    2036 <p><hr> 
    2037 Node:<a name="Section%207.3">Section 7.3</a>, 
    2038 Next:<a rel=next accesskey=n href="#Section%207.4">Section 7.4</a>, 
    2039 Previous:<a rel=previous accesskey=p href="#Section%207.2">Section 7.2</a>, 
    2040 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2041 <br> 
    2042  
    2043 <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> 
     2115<div class="node"> 
     2116<p><hr> 
     2117<a name="Section-7_002e3"></a>Next:&nbsp;<a rel="next" accesskey="n" href="#Section-7_002e4">Section 7.4</a>, 
     2118Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e2">Section 7.2</a>, 
     2119Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a> 
     2120<br> 
     2121</div> 
     2122 
     2123<h3 class="section">7.3 I try to read <span class="file">/proc/sensors</span>, and I get a "No sensor data yet (try again in a few moments)" message. Why?</h3> 
    20442124 
    20452125<p>It takes about 1.5 seconds for the LM78 to update all its sensor 
    20462126values.  If we would try to read it before it finished that, you would get 
    20472127old garbage instead. So you have to wait 1.5 seconds after the module is 
    2048 inserted before you can access <code>/proc/sensors</code>. 
    2049  
    2050 <p>Module versions 1.3.7 and later let the process sleep if it tries 
     2128inserted before you can access <span class="file">/proc/sensors</span>. 
     2129 
     2130   <p>Module versions 1.3.7 and later let the process sleep if it tries 
    20512131to access sensor data right after insertion time, and do not display this 
    20522132message anymore. 
    20532133 
    2054 <p><hr> 
    2055 Node:<a name="Section%207.4">Section 7.4</a>, 
    2056 Previous:<a rel=previous accesskey=p href="#Section%207.3">Section 7.3</a>, 
    2057 Up:<a rel=up accesskey=u href="#Version%201%20Specifics">Version 1 Specifics</a> 
    2058 <br> 
    2059  
    2060 <h3>7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3> 
     2134<div class="node"> 
     2135<p><hr> 
     2136<a name="Section-7_002e4"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Section-7_002e3">Section 7.3</a>, 
     2137Up:&nbsp;<a rel="up" accesskey="u" href="#Version-1-Specifics">Version 1 Specifics</a> 
     2138<br> 
     2139</div> 
     2140 
     2141<h3 class="section">7.4 On my Dell, a LM80 is detected, but all readings are 0!</h3> 
    20612142 
    20622143<p>This is a bug we have only observed on Dell computers. There is 
    … …  
    20642145clear whether the problem is in our code or with the Dells. 
    20652146 
    2066 <p>There are very probably no sensor chips at all on your computer; 
     2147   <p>There are very probably no sensor chips at all on your computer; 
    20672148but until somebody contacts Dell about this and tells us the results, we 
    20682149can not be sure. 
    20692150 
    2070 <p><hr> 
    2071 Node:<a name="Document%20Revisions">Document Revisions</a>, 
    2072 Previous:<a rel=previous accesskey=p href="#Version%201%20Specifics">Version 1 Specifics</a>, 
    2073 Up:<a rel=up accesskey=u href="#Top">Top</a> 
    2074 <br> 
    2075  
    2076 <h2>Appendix A Revision History of This Document</h2> 
    2077  
    2078 <ul> 
     2151<div class="node"> 
     2152<p><hr> 
     2153<a name="Document-Revisions"></a>Previous:&nbsp;<a rel="previous" accesskey="p" href="#Version-1-Specifics">Version 1 Specifics</a>, 
     2154Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a> 
     2155<br> 
     2156</div> 
     2157 
     2158<h2 class="appendix">Appendix A Revision History of This Document</h2> 
     2159 
     2160     <ul> 
    20792161<li>Rev 2.10 (MDS) Various updates, 20040103 
    20802162<li>Rev 2.9 (CP) Converted to Gnu texinfo format, 20020910 
    … …  
    21022184 
    21032185</body></html> 
     2186