monitoring carte mere

Having a proper kernel tree (compilation option 1)
==================================================

Usually, if you compile a user-space application, you can get away with
having a different version of the kernel running than the version of the
kernel header files against which you compiled it. But a perfect match
is needed for the first two compilation options above.

Let's say you want to use the lm_sensors modules with the kernel 2.1.12 you
are running now. What you need, is the original tree in which you
compiled that 2.1.12 kernel. A freshly unpacked 2.1.12 kernel will not
cut it, because `make *config dep' creates some files that are needed.
And even then, you will run into trouble, because you may not have
selected the exact same configuration variables. Plain advise: if you
do not have your original kernel tree anymore, recompile your kernel
first.

Note that there is no need for a perfect match at compilation time, just
at run-time. This means you can cross-compile against a different kernel
version, and the Makefile does not check for this.

Usually problems if the match is imperfect, is that either this package
won't compile at all (because it was a freshly unpacked tree without
some files generated by `make *config dep'), or that you can't insert
modules because of either a `kernel-module version mismatch' or because
of `unresolved kernel symbols'. If you get either of these messages,
check your kernel tree!

Note that some distributions are notably bad at this. To offset this
somewhat, not the files in /usr/include/{linux,asm} are used, but instead
those in /usr/src/linux/include/{linux,asm}. It is also possible to
tell the Makefile the kernel is somewhere else than at /usr/src/linux.

To keep problems to a minimum, please use a 'vanilla' kernel tree,
as distributed on ftp://ftp.kernel/org/pub/linux/kernel, and not one
patched by your distribution.


Separate from kernel compilation (compilation option 1)
=======================================================

This will compile and install the complete lm_sensors package. Though
nothing is written to your kernel tree, a proper tree is still needed
for this. See earlier for what a proper kernel tree is.

At the top of the Makefile are a couple of configuration variables that
you may want to change. As far as possible, the Makefile tries to figure
out by itself their settings, but it is possible to overrule them. A list
is found below. Most important are the variables that determine where
your kernel is located (LINUX=/lib/modules/KERNELVERSION/build, usually
links to /usr/src/linux or something similar), where the i2c header files
are (I2C_HEADERS=/usr/local/include) and where you want to install
your modules (MODDIR=/lib/modules/KERNELVERSION) and header files
(LINUX_INCLUDE_DIR=/usr/local/include/linux). You can see that the
installation locations are choosen in such a way that they are separate
from the true kernel.

Compilation is done by `make all'; `make install' installs the package.
You will get a lot of warnings about files which are not found, all
ending on `.*d'. You can safely ignore this; they contain dependency
information, which is regenerated on the spot.

Please continue reading this file before you start compiling.


Makefile configuration variables (compilation option 1)
==============================================================

SHELL (default: /bin/sh)
You may have to specify the full path to Bash here, if /bin/sh is some
other shell. There have been conflicting reports on whether this is
needed.
KERNELVERSION
The version of the currently running kernel.
LINUX (default: /lib/modules/$(KERNELVERSION)/build)
The location of your kernel tree.
COMPILE_KERNEL
Determine whether you want to consider the kernel modules for compilation
at all. By default, compilation option 1 will only compile and install
those modules which are not built into the kernel.
If some modules are built into your kernel, and this package is much
newer, you may find you can not insert the newly compiled modules.
Sorry.
You may want to set this to 0 if you have just patched and compiled
your kernel using the same version of this package, and just want to
compile the user-space tools.
I2C_HEADERS (default: /usr/local/include)
This lists where the i2c headers are found. If you used compilation
option 1 for the i2c package, the default will be right. If you used
compilation options 2 or 3, it will not, and may actually cause
problems if you have the left-overs of a previous installation.
If you have weird compilation problems, try to change this to
$(LINUX_HEADERS).
SMP
This must be set to 1 for a SMP kernel. The magic invocation should
determine this automatically, so you should not have to bother with
this.
MODVER
This must be set to 1 if CONFIG_MODVERSIONS is defined. The magic
invocation should determine this automatically, so you should not
have to bother with this.
WARN (default: 0)
Generate additional compilation warnings; mainly interesting for
developers.
DEBUG (default: 0)
Some drivers will issue more debug information if you set this to
1. Don't do it, unless you are a developer or are instructed to do
so by the lm_sensors team.
PREFIX (default: /usr/local)
Prefix for almost all installation directories.
MODPREF (default: /lib/modules/$(KERNELVERSION))
The location where the kernel modules will be installed.
ETCDIR (default: /etc)
Installation location of the sensors.conf configuration file.
LIBDIR (default: $(PREFIX)/lib)
Installation location of all static and shared libraries.
BINDIR (default: $(PREFIX)/bin)
Installation directory of programs useful for users.
SBINDIR (default: $(PREFIX)/sbin)
Installation directory of system administrator-only programs.
INCLUDEDIR (default: $(PREFIX)/include)
Base installation directory for include files (see next two vars).
SYSINCLUDEDIR (default: $(INCLUDEDIR)/linux)
Installation directory for system include files.
LIBINCLUDEDIR (default: $(INCLUDEDIR)/sensors)
Installation directory for libsensors include files.
MANDIR (default: $(PREFIX)/man)
Base installation directory for manual pages.
MANOWN (default: root)
Owner of manual pages.
MANGRP (default: root)
Group of manual pages.



Handling the modules (compilation option 1)
===========================================

Run the command `depmod -a' to have the new modules recognised. Most
distributions run this command when you boot, so if you were cross-
compiling, you can skip this step.

See doc/modules for a more detailed treatment.