Changeset 2129

Show
Ignore:
Timestamp:
12/02/03 04:16:57 (9 years ago)
Author:
mds
Message:

xeon doc update w/ help from P.P.

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

Legend:

Unmodified
Added
Removed
  • lm-sensors/trunk/doc/chips/adm1021

    r1870 r2129  
    1818    Datasheet: 
    1919  * Intel Xeon Processor 
    20     Prefix - any other - requires 'force_adm1021' parameter - see MODPARMS file 
     20    Prefix - any other - may require 'force_adm1021' parameter - 
     21    see MODPARMS and xeontemp files for more information 
    2122    Addresses scanned: none 
    2223    Datasheet: Publicly available at Intel website 
     
    133134Xeon support 
    134135------------ 
    135 The Xeon support is untested. 
    136 The Xeon has only one sensor where the other devices have two. 
    137 Use 'force_adm1021=BUS,ADDRESS' as a modprobe parameter. 
    138 ADDRESS can only be 0x18, 0x1a, 0x29, 0x2b, 0x4c, or 0x4e. 
    139 The driver will report two temperatures but one will be invalid. 
    140 It is not clear if all Xeon processors have this feature. 
    141 Please report results. 
     136Some Xeon processors have real max1617, adm1021, or compatible chips 
     137with in them, with two temperature sensors. 
     138 
     139Other Xeons have chips with only one sensor. 
     140 
     141If you have a Xeon, and the adm1021 module loads, and both 
     142temperatures appear valid, then things are good. 
     143 
     144If the adm1021 module doesn't load, you should try two things: 
     145        1) modprobe adm1021 force_adm1021=BUS,ADDRESS 
     146        ADDRESS can only be 0x18, 0x1a, 0x29, 0x2b, 0x4c, or 0x4e. 
     147        See if you have one or two valid temperatures 
     148 
     149        2) modprobe xeontemp 
     150        See if you have one valid temperature. 
     151 
     152Pick the best module for your processor based on the results. 
     153See the xeontemp documentation for further information. 
    142154 
    143155 
  • lm-sensors/trunk/doc/chips/xeontemp

    r1986 r2129  
    88    Prefix `xeontemp' 
    99    Addresses scanned: I2C 0x18, 0x1a, 0x29, 0x2b, 0x4c, 0x4e 
    10     Datasheet: Publicly available at the Intel website 
     10    Datasheets: Publicly available at the Intel website 
     11                See the adm1021 document for additional references 
    1112 
    1213Authors: Frodo Looijaard <frodol@dds.nl>,Philip Edelbrock 
     
    3940----------- 
    4041 
    41 Xeon and other Intel processors with an embedded i2c temperature 
    42 sensor look very similar to an adm1021. 
    43 The Xeon has only one sensor where the adm1021 has two. 
    44 Not all Xeon processors have this feature. 
    45 If you have an Intel processor, and sensors-detect recommended 
     42Many Xeons and other Intel processors have an embedded i2c temperature 
     43sensor that look very similar to an adm1021 or max1617. 
     44 
     45Some Xeons have honest to goodness, real live, actual MAX1617 chips on  
     46them.  Others Xeons made around the same time have other ADM1021  
     47compatible chips on them.  They are mounted on the CPU substrate along  
     48with the processor information EEPROM that is part of that generation of  
     49Xeon CPU's. 
     50 
     51So it's basically impossible to tell a Xeon TEMP sensor from a MAX1617  
     52since they are in fact the same chip.  The Xeon Temperature sensors spec  
     53is just a stripped down register spec for the ADM1021 that says the  
     54"on-board" or "built-in" sensor registers are "reserved".  That way  
     55Intel could substitute whatever ADM1021 compatible chip was cheapest at  
     56the time when they built the CPU's. 
     57 
     58One reason to use the xeontemp driver is if, when Intel built your  
     59particular Xeon's, they didn't use any of the ADM1021 compatible chips  
     60that the ADM1021 driver recognizes.  In that case, using the xeontemp  
     61driver will get you the temperatures you want without potentially  
     62messing up something in the sensor. 
     63 
     64Another reason is to avoid having 'sensors' report the second 
     65temperature. 
     66 
     67Unfortunately, the 533MHz FSB Xeon's, dropped the on-board sensor chip.  
     68So these new Xeons require a sensor on the motherboard to be connected  
     69to the thermal diode to read the temperature.  But these 533MHz capable  
     70motherboards can also accept 400MHz CPU's with the on-board sensor so it  
     71gets confusing in a hurry for motherboard vendors and users. 
     72 
     73If you have 400MHz FSB P4 Xeon CPU's, you should have an on-CPU ADM1021  
     74compatible sensor at 0x18 or 0x19.  In that case, use the ADM1021 driver  
     75if it detects a chip at that address.  The CPU DIE temperature (Tj) will  
     76be the "REMOTE" temperature from this sensor.  The "Board" or "built-in"  
     77temperature from the ADM1021 will be the temperature of the ADM1021  
     78compatible itself which is one of the chips you see on the side of the CPU. 
     79 
     80If you have sensors at 0x18 and 0x19 that are not detected by the  
     81ADM1021, and you have 400MHz Xeons, then you may want to try the  
     82xeontemp driver. 
     83 
     84If you have 533MHZ FSB Xeons, then you do *not* have an on-board thermal  
     85sensor and you should look for CPU temperatures from the other sensors  
     86on your motherboard. (Winbond chip for example). 
     87 
     88If you have an Intel Xeon processor, and sensors-detect recommended 
    4689the adm1021 driver, and the address is one of 
    47900x18, 0x1a, 0x29, 0x2b, 0x4c, or 0x4e, and when using the 
    4891adm1021 driver, temp1 is invalid but temp2 looks correct, then 
    49 it is likely you should use this driver instead. 
     92it is likely you should use the xeontemp driver instead. 
     93 
     94In summary, the xeontemp module supports one temperature and the  
     95adm1021 module supports two. Use the module that works best for you. 
    5096 
    5197See the adm1021 documentation for more information. 
     98 
    5299 
    53100Author/Maintainer 
     
    55102Mark D. Studebaker (mdsxyz123@yahoo.com). 
    56103Derived from the adm1021 driver. 
     104Thanks to Philip Pokorny for help with this document. 
    57105Send requests to the sensors@stimpy.netroedge.com mailing list.