From ef2e3e0b1d4648953d668ab0d8f38c238b14d2d0 Mon Sep 17 00:00:00 2001
From: "Mark D. Studebaker" The lm_sensors package includes a collection of modules for general SMBus
+ The lm_sensors package includes a collection of modules for general SMBus
access and hardware monitoring. NOTE: this requires special support which
is not in standard 2.2-vintage kernels.
-Sensors FAQ for lm_sensors version 2.12
+Sensors FAQ for lm_sensors version 2.12
Copyright (C) 1998 - 2004
Frodo Looijaard,
Philip Edelbrock,
@@ -15,33 +15,33 @@ and
Mark Studebaker
-Short Contents
-
-Table of Contents
-
+/etc/sensors.conf?
+
No such file or directory warnings when I compile?
make install fails on Mandrake kernels
modprobe modules (Red Hat especially)
Upgrade BIOS! I don't want to!
+
Can't access procfs/sysfs file
No sensors found!
Error: Line xxx: zzzzzzz
ERROR: Can't get xxxxx data!
@@ -150,11 +152,12 @@ and
-/proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?
lm_sensors
+lm_sensors
-
If that doesn't work: -
If that doesn't work: +
We don't support boards, we support chips. See What chips are on motherboard XYZ. +
We don't support boards, we support chips. See What chips are on motherboard XYZ. -
This we have good answers for. -
This we have good answers for. +
README
doc/chips/SUMMARY
Newest Driver Status: http://www2.lm-sensors.nu/~lm78/newdrivers.html +
Newest Driver Status: http://www2.lm-sensors.nu/~lm78/newdrivers.html -
sensors-detect will tell you. Take the modprobe lines it
+
sensors-detect will tell you. Take the modprobe lines it
recommends and paste them into the appropriate /etc/rc.d/xxxx file
to be executed at startup.
-
You need one module for each sensor chip and bus adapter you own; +
You need one module for each sensor chip and bus adapter you own;
if there are sensor chips on the ISA bus, you also need i2c-isa.o.
for each type of chip you own. That's all. On my computer, I could use the
following lines:
-
modprobe i2c-isa
modprobe i2c-piix4
modprobe lm78
@@ -625,18 +598,16 @@ following lines:
sensors -s
/etc/sensors.conf?/etc/sensors.conf?Yes, for any applications that use libsensors, including the
+
Yes, for any applications that use libsensors, including the
sensors application included in our package.
It tells libsensors how to translate the values the chip
measures to real-world values. This is especially important for voltage
@@ -644,150 +615,140 @@ inputs. The default configuration file should usually do the trick.
It is automatically installed as /etc/sensors.conf, but it will not
overwrite any existing file with that name.
-
sensors are incorrect!sensors are incorrect!Every motherboard is different. You can customize the labels +
Every motherboard is different. You can customize the labels
in the file /etc/sensors.conf. That's why it exists!
The default labelling (in lib/chips.c and /etc/sensors.conf) is just
a template.
-
sensors are incorrect!sensors are incorrect!You can customize them in the file /etc/sensors.conf. See above.
+
You can customize them in the file /etc/sensors.conf. See above.
-
/etc/sensors.conf didn't take effect!/etc/sensors.conf didn't take effect!You forgot to run sensors -s. See above.
+
You forgot to run sensors -s. See above.
-
Use an ignore line in /etc/sensors.conf so it isn't
+
Use an ignore line in /etc/sensors.conf so it isn't
displayed in sensors.
-
sensors.conf!sensors.conf!There is detailed help at the top of that file. +
There is detailed help at the top of that file. -
sensors.conf entries for specific boards?sensors.conf entries for specific boards?No. Good idea though. If you would like to set one up on your website +
No. Good idea though. If you would like to set one up on your website send us mail and we will set up a link to it. -
No such file or directory warnings when I compile?No such file or directory warnings when I compile?Don't worry about them. The dependency files (which tell which +
Don't worry about them. The dependency files (which tell which
files should be recompiled when certain files change) are created
dynamically. They are not distributed with the package. The make program
notices they are not there, and warns about that - and the first thing
it will do is generate them. So all is well.
-
Check that the correct i2c header files are used. Depending on +
Check that the correct i2c header files are used. Depending on
how you installed, they should be under either /usr/local/include or
/usr/src/linux*/include. Try to edit the Makefile for the other setting.
-
No rule to make target xxxx needed by xxxx - how to fix?No rule to make target xxxx needed by xxxx - how to fix?make clean in lm_sensors.
make clean in i2c.
make clean in the kernel.
/usr/include/linux points to /usr/src/linux/include/linux.
Have you installed the matching version of the i2c package? Remember, +
Have you installed the matching version of the i2c package? Remember, compilation is not enough, you also need to install it for the header files to be found! -
If you want to patch the kernel, you will have to apply the i2c +
If you want to patch the kernel, you will have to apply the i2c patches first! -
make install fails on Mandrake kernelsmake install fails on Mandrake kernelsMandrake uses a non-standard version.h file which confuses our Makefile.
+
Mandrake uses a non-standard version.h file which confuses our Makefile.
Edit our Makefile on the MODDIR := line to hard-code the module directory.
-
modprobe modules (Red Hat especially)modprobe modules (Red Hat especially)Example: -
*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o - i2c_bit_add_bus_R8c3bc60e - i2c_bit_del_bus_R92b18f49 -+
Example:
+
*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o +i2c_bit_add_bus_R8c3bc60e +i2c_bit_del_bus_R92b18f49 +-
You can also run depmod -a -e to see all unresolved symbols.
+
You can also run depmod -a -e to see all unresolved symbols.
-
These are module versioning problems. Generally you did not compile +
These are module versioning problems. Generally you did not compile
against the kernel you are running. Sometimes the Red Hat source you
have is not for the kernel you are running.
You must compile our package against the source for the kernel you
are running with something like make LINUX=/usr/src/linux-2.4.14.
-
Try the following to be sure: +
Try the following to be sure: -
nm --extern MODULE.o
Filter out the kernel symbols, like kmalloc, printk etc. and note the
number code behind them, like printk_R1b7d4074. If there is no numeric
@@ -800,23 +761,21 @@ lies somewhere else. Are they different? If so, you have a module
versioning problem.
In some versions of Redhat, an RPM is included to provide i2c support. +
In some versions of Redhat, an RPM is included to provide i2c support. However, this RPM does not place the header files in the kernel directory structure. When you update kernels, they may persist. To get rid of these obsolete header files, at a command prompt: -
rpm -qa | grep i2c
+rpm -qa | grep i2c
kernel-i2c, or a similar rpm in the output
rpm -ev kernel-i2c (or the name of the similar package)
@@ -825,36 +784,34 @@ If this complains about dependencies, you can try adding
as you have upgraded kernels, and nothing should be using the
old i2c stuff anymore anyway. Just don't use it with abandon.
lm_sensors)
- -make clean-make-
+make clean+make+
.c/.h files with absolute paths to the header files.
More of a workaround than a real fix, but at least you can get it
to work.
-