Changeset 5515 for lm-sensors/branches

Show
Ignore:
Timestamp:
12/03/08 16:15:39 (3 years ago)
Author:
khali
Message:

Document the new detection order and rules.
Drop the reference to i2cdetect, as it has moved to a separate package.
Update the date and authors section.

Location:
lm-sensors/branches/lm-sensors-3.0.0
Files:
2 modified

Legend:

Unmodified
Added
Removed
  • lm-sensors/branches/lm-sensors-3.0.0/CHANGES

    r5513 r5515  
    4040                  Skip SMBus probing by default if a Super I/O was found (#2322) 
    4141                  Display I2C address statictics with --stat 
     42                  Document the new detection order and rules 
    4243  sensors-detect-stat.pl: Delete (functionality merged into sensors-detect) 
    4344 
  • lm-sensors/branches/lm-sensors-3.0.0/prog/detect/sensors-detect.8

    r4699 r5515  
    1 .TH SENSORS-DETECT 8 "March 2004" "lm-sensors 3" 
     1.TH SENSORS-DETECT 8 "December 2008" "lm-sensors 3" 
    22.SH NAME 
    33sensors-detect \- detect hardware monitoring chips 
     
    1212tool suite. 
    1313 
     14sensors-detect will look for the following devices, in order: 
     15.IP \(bu 
     16Sensors embedded in CPUs, south bridges and memory controllers. 
     17.IP \(bu 
     18Sensors embedded in Super I/O chips. 
     19.IP \(bu 
     20Hardware monitoring chips accessed through ISA I/O ports. 
     21.IP \(bu 
     22Hardware monitoring chips reachable over the SMBus or more generally 
     23any I2C bus on your system. 
     24.PP 
     25As the last two detection steps can cause trouble on some systems, they 
     26are normally not attempted if the second detection step led to the 
     27discovery of a Super I/O chip with complete hardware monitoring features. 
     28However, the user is always free to ask for all detection steps if so is 
     29his/her wish. This can be useful if a given system has more than one 
     30hardware monitoring chip. Some vendors are known to do this, most notably 
     31Asus and Tyan. 
     32 
     33.SH WARNING 
     34sensors-detect needs to access the hardware for most of the chip detections. 
     35By definition, it doesn't know which chips are there before it manages to 
     36identify them. This means that it can access chips in a way these chips do 
     37not like, causing problems ranging from SMBus lockup to permanent hardware 
     38damage (a rare case, thankfully.) 
     39 
     40The authors made their best to make the detection as safe as possible, and 
     41it turns out to work just fine in most cases, however it is impossible to 
     42guarantee that sensors-detect will not lock or kill a specific system. So, 
     43as a rule of thumb, you should not run sensors-detect on production servers, 
     44and you should not run sensors-detect if can't afford replacing a random 
     45part of your system. Also, it is recommended to not force a detection step 
     46which would have been skipped by default, unless you know what you are doing. 
     47 
    1448.SH SEE ALSO 
    15 sensors(1), libsensors(3), i2cdetect(8) 
     49sensors(1), libsensors(3) 
    1650 
    1751.SH AUTHOR 
    18 Frodo Looijaard and the lm_sensors group 
    19 http://www.lm-sensors.org/ 
    20 This manual page was written by Joey Hess <joey@debian.org>, for 
    21 the Debian GNU/Linux system. It was then reviewed by the lm_sensors team and 
    22 is now part of the lm_sensors source distribution. 
     52Frodo Looijaard and Jean Delvare