mirror of
https://github.com/lm-sensors/lm-sensors
synced 2025-09-01 23:05:25 +00:00
Fold BACKGROUND into README.
git-svn-id: http://lm-sensors.org/svn/lm-sensors/branches/lm-sensors-3.0.0@4874 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
30
BACKGROUND
30
BACKGROUND
@@ -1,30 +0,0 @@
|
|||||||
When you want to communicate with a piece of hardware, you need a kernel
|
|
||||||
driver (well, that is not quite true, but it is in most cases the only
|
|
||||||
way to do it safely).
|
|
||||||
|
|
||||||
The kernel modules communicate their information through the /sys inter-
|
|
||||||
face. Because every motherboard is different, the sensor chips always
|
|
||||||
advert the measurements at their pins. This means that the values they
|
|
||||||
report are not always immediately relevant to you. They have to be
|
|
||||||
labelled properly, and sometimes they must be scaled to correspond to
|
|
||||||
the real world.
|
|
||||||
|
|
||||||
libsensors is a (shared or static) library of access functions. It
|
|
||||||
offers a simple-to-use interface for applications to access the sensor
|
|
||||||
chip readings, to set new limits, and all other commonly needed things.
|
|
||||||
It has a configuration file where you can put all the
|
|
||||||
motherboard-specific labels and conversion rules. That way, all
|
|
||||||
applications do not need to duplicate the effort and can simply link
|
|
||||||
with libsensors and work out of the box.
|
|
||||||
|
|
||||||
This package does not contain a nice graphical monitor. Look at the file
|
|
||||||
doc/useful_addresses.html for pointers to such programs. It does contain
|
|
||||||
an example console program that reports all current sensors values. This
|
|
||||||
program is called 'sensors'. You can use it as a reference implementation
|
|
||||||
for more intricate programs.
|
|
||||||
|
|
||||||
The Linux 2.6 kernel has many, many sensor drivers, and there are lots
|
|
||||||
of different sensor chips supported. Sometimes, it can be hard to
|
|
||||||
determine what chips and adapters you have, and which modules correspond
|
|
||||||
to them. Fortunately, there is a user-space application 'sensors-detect'
|
|
||||||
that should tell you exactly what is available, and what you need to do.
|
|
32
README
32
README
@@ -33,6 +33,8 @@ See the INSTALL file.
|
|||||||
HARDWARE SUPPORT
|
HARDWARE SUPPORT
|
||||||
----------------
|
----------------
|
||||||
|
|
||||||
|
To find out what hardware you have, just run 'sensors-detect' as root.
|
||||||
|
|
||||||
Most modern mainboards incorporate some form of hardware monitoring chips.
|
Most modern mainboards incorporate some form of hardware monitoring chips.
|
||||||
These chips read things like chip temperatures, fan rotation speeds and
|
These chips read things like chip temperatures, fan rotation speeds and
|
||||||
voltage levels. There are quite a few different chips which can be used by
|
voltage levels. There are quite a few different chips which can be used by
|
||||||
@@ -52,6 +54,36 @@ even need to wait for a new kernel driver to be written. Updating the
|
|||||||
lm-sensors package itself will not help.
|
lm-sensors package itself will not help.
|
||||||
|
|
||||||
|
|
||||||
|
LIBSENSORS
|
||||||
|
----------
|
||||||
|
|
||||||
|
The kernel drivers communicate their information through the /sys
|
||||||
|
interface. Because every motherboard is different, the drivers always
|
||||||
|
advert the measurements at their pins. This means that the values they
|
||||||
|
report are not always immediately relevant to you. They have to be
|
||||||
|
labelled properly, and sometimes they must be scaled to correspond to
|
||||||
|
real-world values.
|
||||||
|
|
||||||
|
libsensors is a (shared or static) library of access functions. It
|
||||||
|
offers a simple-to-use interface for applications to access the sensor
|
||||||
|
chip readings and configure them as you like. It has a configuration
|
||||||
|
file where you can put all the motherboard-specific labels and
|
||||||
|
conversion rules. That way, all applications do not need to duplicate
|
||||||
|
the effort and can simply link with libsensors and work out of the box.
|
||||||
|
|
||||||
|
|
||||||
|
APPLICATIONS
|
||||||
|
------------
|
||||||
|
|
||||||
|
This package does not contain a nice graphical monitor. Look at the file
|
||||||
|
doc/useful_addresses.html for pointers to such programs. It does contain
|
||||||
|
an example console program that reports all current sensors values. This
|
||||||
|
program is called 'sensors'. You can use it as a reference implementation
|
||||||
|
for more intricate programs. It also contains a daemon watching for
|
||||||
|
sensor values, logging alarms and feeding an RRD database with the sensor
|
||||||
|
measurements.
|
||||||
|
|
||||||
|
|
||||||
OTHER INFORMATION
|
OTHER INFORMATION
|
||||||
-----------------
|
-----------------
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user