C
opyright (c) 1998 - 2002
+
+
+
+
+
/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 /proc file
+Can't access /proc file
No sensors found!
Error: Line xxx: zzzzzzz
ERROR: Can't get xxxxx data!
@@ -131,10 +150,10 @@ and/proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?
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. -
Most PC's built since late 1997 now come with a +
Most PC's built since late 1997 now come with a hardware health monitoring chip. This chip may be accessed via the ISA bus or the SMBus, depending on the motherboard. -
Some motherboard chipsets, notably the Via 686 and the SiS 5595, +
Some motherboard chipsets, notably the Via 686 and the SiS 5595, contain hardware monitor functions. -
This FAQ frequently refers to the "LM78". This chip has been +
This FAQ frequently refers to the "LM78". This chip has been obsoleted by National Semiconductor. Most motherboards today contain a chip with similar functions. +
The LM78 is a chip made by National Semiconductor which can monitor 7 +
The LM78 is a chip made by National Semiconductor which can monitor 7 voltages (5 positive, 2 negative) from 0 to 4.08V. The inputs are usually in series with voltage dividers which lower the +/- 12V and +/- 5V supplies to measurable range. Therefore, the readings for such inputs need to be re-scaled appropriately by software. -
The LM78 also has 3 fan speed monitoring inputs, an internal +
The LM78 also has 3 fan speed monitoring inputs, an internal temperature sensor, a chassis intrusion sensor, and a couple maskable interrupt inputs. The LM78 can also relay the processor's (P6 or Pent II) VID lines which are hardwired and used to indicate to the power regulator (usually on the mainboard close to the processor socket/slot) what voltage to supply to the processor. -
The LM78 can be interfaced to a system via the ISA bus and/or the +
The LM78 can be interfaced to a system via the ISA bus and/or the SMBus. -
Most other sensor chips have comparable functionality. Each supported +
Most other sensor chips have comparable functionality. Each supported
chip is documented in the doc/chips directory.
+
Most semiconductor companies have comprehensive documentation, +
Most semiconductor companies have comprehensive documentation, including complete datasheets, on their websites. Analog Devices, Dallas Semiconductor, Maxim, and National Semiconductor have the widest selection of sensor chips. Their websites are: -
Please see the file http://www2.lm-sensors.nu/~lm78/useful_addresses.html +
Please see the file http://www2.lm-sensors.nu/~lm78/useful_addresses.html for links to other companies' websites. +
Sensor chips reside on either the ISA bus, the SMBus, or both. +
Sensor chips reside on either the ISA bus, the SMBus, or both.
See the file doc/chips/SUMMARY in our package for a list.
-
To communicate with chips on the ISA bus, the software uses +
To communicate with chips on the ISA bus, the software uses simple I/O reads and writes. -
To communicate with chips on the SMBus, the software must +
To communicate with chips on the SMBus, the software must use an SMBus interface device, explained below. +
The SMBus is the "System Management Bus". More specifically, it is a +
The SMBus is the "System Management Bus". More specifically, it is a 2-wire, low-speed serial communication bus used for basic health monitoring and hardware management. It is a specific implementation of the more general I2C (pronunciation: I-squared-C) bus. In fact, both I2C devices and SMBus devices may be connected to the same (I2C) bus. -
The SMBus (or I2C bus) starts at the host controller, used for +
The SMBus (or I2C bus) starts at the host controller, used for starting transactions on the SMBus. From the host interface, the devices communicated with are the slave devices. Each slave device has a unique 7-bit address which the host uses to refer to that device. -
For each supported SMBus host, there is a separate kernel module +
For each supported SMBus host, there is a separate kernel module which implements the communication protocol with the host. Some SMBus hosts really operate on the SMBus level; these hosts can not cope with pure I2C devices. Other hosts are in fact I2C hosts: in this case, we implement the SMBus protocol in terms of I2C operations. But these hosts can also talk to pure I2C devices. +
We promise, you do, even if you don't have any old ISA slots. +
We promise, you do, even if you don't have any old ISA slots.
The "ISA Bus" exists in your computer even if you don't have ISA slots;
it is simply a memory-mapped area, 64KB in size (0x0000 - 0xFFFF)
where many "legacy" functions, such as keyboard and interrupt controllers,
@@ -354,16 +392,18 @@ See the file /proc/ioports for a list of devices living on
the "ISA Bus" in your system. If you don't like the term "ISA Bus"
think "I/O Space".
+
Most new processors contain a thermal diode on the die itself. +
Most new processors contain a thermal diode on the die itself.
The electical properties of all diodes and transistors vary
slightly with temperature. The thermal diode is exceptionally accurate
because it is directly on the die. Newer temperature sensor chips,
@@ -373,10 +413,10 @@ an external diode and converting this data to a temperature.
Any sensor chip listed in doc/chips/SUMMARY in our package which
has support for more than one temperature supports external temperature sensing.
-
Older motherboards and processors without this feature generally use +
Older motherboards and processors without this feature generally use an LM75 placed close to the processor. This is much less accurate. -
The Pentium 2 'boxed' processor usually has an LM75 very close to the +
The Pentium 2 'boxed' processor usually has an LM75 very close to the base of the box. It can be read through the SMBus to report the approximate temperature of the processor. The processor also contains an internal temperature sensor (of low accuracy) used as a fail-safe to disable the @@ -385,26 +425,28 @@ the Pentium 2 also has a hard-wired signal (VID lines) on it's SEC (single edge connector) which indicates what power supply is required to operate the processor. -
The P6 (Pentium-Pro) may have an LM75 in or just under the socket. +
The P6 (Pentium-Pro) may have an LM75 in or just under the socket. P6's also have VID lines. -
Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have +
Pentiums and Pentium w/ MMX do not have VID lines, and sometimes have LM75's under the sockets (depends on the mainboard, and how 'modern' the mainboard is). -
The P2 Xeon was the first Intel processor to include the SMBus +
The P2 Xeon was the first Intel processor to include the SMBus interface on the P2 Xeon SEC. +
The LM78, and most other sensor chips like it, reads its sensors one +
The LM78, and most other sensor chips like it, reads its sensors one by one. A complete scanning sweep will take about 1.5 seconds. The LM78 stops readings sensors if you try to access it, so if you access it very often (by reading sensor values; writing new limits is safe) it will not find the @@ -412,15 +454,17 @@ time to update its sensor values at all! Fortunately, the kernel module takes care not to do this, and only reads new values each 1.5 seconds. If you read the values again, you will get the 'old' values again. +
-It is possible to monitor each sensor and have an alarm go off if +
It is possible to monitor each sensor and have an alarm go off if it crosses some pre-determined limits. There are two sorts of interrupts which can be generated by sensor chips if this happens (it depends a bit on the actual chip if both are supported; the LM80, for example, has only @@ -431,138 +475,146 @@ puts the processor in a secure environment independent of any other things running. SMI is currently not supported by the Linux kernel. IRQs are supported, of course. -
Even if no interrupt is generated, some bits in a status register +
Even if no interrupt is generated, some bits in a status register will be set until the register is read the next time. If the alarm condition persists after that, the bits will be set on the next scanning sweep, etc. -
Most drivers in our package do not support interrupts at this time. +
Most drivers in our package do not support interrupts at this time. +
/etc/sensors.conf?
-No such file or directory warnings
-make install fails on Mandrake kernels
-modprobe modules
+
+
-We tried to make this package as modular as possible. This makes it +
We tried to make this package as modular as possible. This makes it easy to add new drivers, and unused drivers will take no precious kernel space. On the other hand, it can be a bit confusing at first. -
Here are two simple guidelines: -
Here are two simple guidelines: +
sensors-detect and do what it tells you.
modprobe, not insmod.
Further information is in doc/modules.
+
Further information is in doc/modules.
-
We have an excellent program that scans all your hardware. +
We have an excellent program that scans all your hardware.
It is called sensors-detect and is installed in /usr/local/sbin
by make install. Just execute this script, and it will tell you.
-
Chip detection in the drivers is fairly good. That means that it is +
Chip detection in the drivers is fairly good. That means that it is usually harmless to insert more chip drivers than you need. However, this can still lead to problems, so we do not recommend it. -
If sensors-detect didn't find any sensors, either you don't have +
If sensors-detect didn't find any sensors, either you don't have any, or the ones you have, we don't support. (Look at your motherboard for candidates, then see Help) -
!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!! +
!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!! -
We have no idea. Here is what you should do: -
We have no idea. Here is what you should do: +
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
@@ -571,16 +623,18 @@ 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
@@ -588,140 +642,150 @@ 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
@@ -734,21 +798,23 @@ 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)
@@ -757,34 +823,36 @@ 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.
-The problem with much of the sensor data is that it is impossible to +
The problem with much of the sensor data is that it is impossible to
properly interpret some of the readings without knowing what the hardware
configuration is. Some fans report one 'tick' each rotation, some report
two 'ticks' each rotation. It is easy to resolve this through the
configuration file /etc/sensors.conf:
-
chip lm78-* # Or whatever chip this relates to -compute fan1 2*@,@/2 # This will double the fan1 reading - # -- or -- -compute fan1 @/2,2*@ # This will halve the fan1 reading -+
chip lm78-* # Or whatever chip this relates to + compute fan1 2*@,@/2 # This will double the fan1 reading + # -- or -- + compute fan1 @/2,2*@ # This will halve the fan1 reading +-
See doc/fan-divisors in our package for further information.
+
See doc/fan-divisors in our package for further information.
-
You may not have a three-wire fan, which is required. +
You may not have a three-wire fan, which is required. -
You may need to increase the 'fan divisor'. See doc/fan-divisors
+
You may need to increase the 'fan divisor'. See doc/fan-divisors
in our package for further information.
-
Believe it or not, doubling the 'fan divisor' will not halve +
Believe it or not, doubling the 'fan divisor' will not halve
the fan reading. You have to add a compute line in /etc/sensors.conf.
See My fans report exactly half/double their values compared to the BIOS,
and see doc/fan-divisors in our package for further information.
+
For starters, those aren't LM75's. Your mainboard actually has the +
For starters, those aren't LM75's. Your mainboard actually has the Winbond W83781D which emulates two LM75's, but many systems which use the Winbond chip (such as the Asus P2B) don't have the thermo-resisters connected to the chip resulting in these strange -48 degree readings. -
If you have an Asus P2B and want more information on adding thermal sensing capability, check out: +
If you have an Asus P2B and want more information on adding thermal sensing capability, check out: http://ultimatepc.fsn.net/techinfo/p2bthermistor/p2bthermistor.htm -
In upcoming versions, you will be able to disable non-interesting +
In upcoming versions, you will be able to disable non-interesting readings. +
The LM78 has seven voltage sensors. The default way of +
The LM78 has seven voltage sensors. The default way of
connecting them is used in the configuration file. This includes a VCore2,
even if you do not have one. You can easily edit the configuration file
to give it another name, or make this reading disappear using
an ignore line.
-
Note that Vcore2 is often the same as Vcore on motherboards which +
Note that Vcore2 is often the same as Vcore on motherboards which only support one processor. Another possibility is that Vcore2 is not connected at all and will not have a valid reading at all. A third possibility, is that Vcore2 monitors something else, so you should not be too surprised if the values are completely different. +
The ALARM indications in sensors are those reported by the
+
The ALARM indications in sensors are those reported by the
sensor chip itself. They are NOT calculated by sensors. sensors
simply reads the ALARM bits and reports them.
-
An ALARM will go off when a minimum or maximum limit is crossed. +
An ALARM will go off when a minimum or maximum limit is crossed. The ALARM is then latched - that is, it will stay there until the chip's registers are next accessed - which will be the next time you read these values, but not within (usually) 1.5 seconds since the last update. -
Reading the registers clears the ALARMS, unless the current +
Reading the registers clears the ALARMS, unless the current value is still out of range. -
The purpose of this scheme is to tell you if there has been +
The purpose of this scheme is to tell you if there has been
a problem and report it to the user. Voltage or temperature spikes
get detected without having to read the sensor chip hundreds of times
a second. The implemetation details depend a bit on the kind of chip.
See the specific chip documentation in doc/chips and the
chip datasheet for more information.
+
No, probably not. If your motherboard heats up a bit, the sensed +
No, probably not. If your motherboard heats up a bit, the sensed voltages will drift a bit. If your power supply is loaded (because a disk gets going, for example), the voltages may get a bit lower. Heavy processor activity, in particular, dramatically increases core voltage @@ -939,37 +1017,41 @@ As long as they stay within a sensible range (say 5% of the nominal value for CPU core voltages, and 10% for other voltages), there is no reason to worry. +
Each module tries to set limits to sensible values on initialization, +
Each module tries to set limits to sensible values on initialization, but a module does not know how a chip is actually connected. This is described in the configuration file, which is not read by kernel modules. So limits can be strange, if the chip is connected in a non-standard way. -
Readings can also be strange; there are several reasons for this. +
Readings can also be strange; there are several reasons for this. Temperature sensors, for example, can simply not be present, even though the chip supports them. Also, it can be that the input is used in a non-standard way. You can use the configuration file to describe how this measurement should be interpreted; see the comments the example file for more information. +
These describe the core voltage for your processor. They are +
These describe the core voltage for your processor. They are
supported for most processors, however they are not always
correctly connected to the sensor chip, so the readings may be invalid.
A reading of 0V, +3.5V or +2.05V is especially suspect.
@@ -977,89 +1059,99 @@ If this is the case, add a line If we would read the registers more often, it would not find the
+ If we would read the registers more often, it would not find the
time to update them. So we only update our readings once each 1.5 seconds
(the actual delay is chip-specific; for some chips, it may not be needed
at all).
+ ISA bus access is fast, but SMBus access is really slow. If you have
+ ISA bus access is fast, but SMBus access is really slow. If you have
a lot of sensors, it just takes a lot of time to access them. Fortunately,
this has almost no impact on the system as a whole, as another job can run
while we are waiting for the transaction to finish.
+ No, you can't; and it may well be never supported.
+ No, you can't; and it may well be never supported.
- Almost no mainboard we have encountered have actually connected the
+ Almost no mainboard we have encountered have actually connected the
IRQ-out pin of sensor chips. That means that we could enable IRQ reporting, but
nothing would happen. Also, even if a motherboard has it connected, it is
unclear what interrupt number would be triggered. And IRQ lines are a scarce
facility, which means that almost nobody would be able to use it anyway.
- The SMI interrupt is only available on a few types of chips. It is
+ The SMI interrupt is only available on a few types of chips. It is
really a very obscure way to handle interrupts, and supporting it under Linux
might be quite hard to do.
- Your best bet would be to poll the alarm file with a user-land daemon
+ Your best bet would be to poll the alarm file with a user-land daemon
which alerts you if an alarm is raised. I am not aware of any program which
does the job, though you might want to examine one of the graphical monitor
programs under X, see http://www2.lm-sensors.nu/~lm78/useful_addresses.html for addresses.
+ Some chips which mainboard makers connect to the SMBus are not SMBus
+ Some chips which mainboard makers connect to the SMBus are not SMBus
devices. An example is the 91xx clock generator chips. When read, these
devices can lock up the SMBus until the next hard reboot. This is because
they have a similar serial interface (like the I2C), but don't conform to
Intel's SMBus standard.
- Why did they connect these devices to the SMBus if they aren't
+ Why did they connect these devices to the SMBus if they aren't
compatible? Good question! :') Actually, these devices may support being
written to, but lock things up when they are read.
+ We display the actual temperature of the sensor. This may not be the
+ We display the actual temperature of the sensor. This may not be the
temperature you are interested in, though. If a sensor should measure
the CPU temperature, it must be in thermal contact with it. In practice,
it is just somewhere near it. Your BIOS may correct for this (by adding,
@@ -1067,73 +1159,81 @@ for example, thirty degrees to the measured temperature). The correction
factor is regrettably different for each mainboard, so we can not do this
in the module itself. You can do it through the configuration file, though:
- Remember, these values do not take the configuration file
+ Remember, these values do not take the configuration file
Change the limit values in Change the limit values in You forgot to run You forgot to run Yes, this is still a problem. It is partially solved by alias detection
+ Yes, this is still a problem. It is partially solved by alias detection
and confidence values in sensors-detect, but it is really tough.
- Double detections can be caused by two things:
+ Double detections can be caused by two things:
sensors can be detected to both the ISA and the SMBus (and if you have
loaded the approprate adapter drivers, it will be detected on both), and
some chips simulate other chips (the Winbond W83781D simulates LM75 chips
on the SMBus, for example). Remove the offending adapter or chip driver, or
run sensors-detect and add the Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards
+ Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards
which connect a clock chip to the SMBus. Unfortunately, this clock chip
hangs the PIIX4 if it is read (it is an I2C device, but not SMBus compatible).
We have found no way of solving this, except for rebooting your computer.
@@ -1141,65 +1241,67 @@ Next time when you run sensors-detect, you may want to exclude addresses
0x69 and/or 0x6a, by entering s when you are asked whether you want to
scan the PIIX4.
+ See below for some particularly troublesome chips.
+ See below for some particularly troublesome chips.
Also be sure and check The Asus AS99127F is a modified version of the Winbond W83781D.
+ The Asus AS99127F is a modified version of the Winbond W83781D.
Asus will not release a datasheet. The driver was developed by tedious
experimentation. We've done the best we can. If you want to make adjustments
to the readings please edit The Via 686A datasheet is incomplete.
+ The Via 686A datasheet is incomplete.
Via will not release details. The driver was developed by tedious
experimentation. We've done the best we can. If you want to make adjustments
to the readings please edit The MTP008 has programmable temperature sensor types.
+ The MTP008 has programmable temperature sensor types.
If your sensor type does not match the default, you will have to change it.
See This chip can use multiple thermistor types and there are also
+ This chip can use multiple thermistor types and there are also
two different versions of the chip. We are trying to get the driver
working better and develop formulas for different thermistors
but we aren't there yet. Sorry.
Also, many times the chip isn't really a sis5595 but it was
misidentified. We are working on improving that too.
- Do you own an ASUS motherboard? Perhaps your chip is being
+ Do you own an ASUS motherboard? Perhaps your chip is being
misidentified. Look on the motherboard (or at
http://mbm.livewiredev.com) for a 'Winbond' or Asus chip.
Often the real device is an Asus as99127f. If so, the driver can be
@@ -1209,127 +1311,135 @@ Cat /proc/bus/i2c to see a list of bus numbers.
Read the w83781d module documentation ( The SMBus tends to hang on this board and it seems to get worse
+ The SMBus tends to hang on this board and it seems to get worse
at higher temperatures. Use ISA accesses to reliably use the w83781d
monitor chip on this board and use the The LM75 detection is poor and other hardware is often misdetected
+ The LM75 detection is poor and other hardware is often misdetected
as an LM75. Figure out what you really have See What chips are on motherboard XYZ.
- The LM78 is no longer manufactured by National Semiconductor.
+ The LM78 is no longer manufactured by National Semiconductor.
You probably don't have a real LM78 but something similar that we
do not recogize or support. Figure out what you really have See What chips are on motherboard XYZ.
- The LM80 detection is poor and other hardware is often misdetected
+ The LM80 detection is poor and other hardware is often misdetected
as an LM80. Figure out what you really have See What chips are on motherboard XYZ.
- The it87 temperature sesnsors are configured, unfortunately,
+ The it87 temperature sesnsors are configured, unfortunately,
in a way different from w83781d. They cannot be configured from
There is a SuperMicro board with two LM87's on it that are
+ There is a SuperMicro board with two LM87's on it that are
not hooked up in the same way, so they need different defaults.
For example, both CPU temperatures go to one LM87.
- Make two different sections in Make two different sections in There is a commented example in There is a commented example in If the problem is a PCI device is not present in If the problem is a PCI device is not present in If dmesg says If dmesg says If the problem is a PCI device whose base address is not set,
+ If the problem is a PCI device whose base address is not set,
you may be able to set the address with a force parameter. The via686a
and sis5595 chip drivers, and some bus drivers, support the command line
What specifically is the trouble?
- What specifically is the trouble?
+ In general, we don't know. Start by running In general, we don't know. Start by running A clock chip. Often, accessing these clock chips in the wrong
+ A clock chip. Often, accessing these clock chips in the wrong
way will instantly crash your computer. Sensors-detect carefully
avoids these chips. If you really really want to play with your clock
chip you can look at EEPROMs on your SDRAM DIMMs. Load the eeprom module to
+ EEPROMs on your SDRAM DIMMs. Load the eeprom module to
look at some basic data in These are often 'shadows' of your EEPROMs on your SDRAM DIMMs
+ These are often 'shadows' of your EEPROMs on your SDRAM DIMMs
at addresses 0x50 - 0x57. They aren't really there. If you try and
do a It could be many things. What was the problem? See Problems on particular motherboards.
+ It could be many things. What was the problem? See Problems on particular motherboards.
- You don't have i2c support in your kernel, or the i2c-core module
+ You don't have i2c support in your kernel, or the i2c-core module
was not loaded and you did not run sensors-detect as root.
- Your Your Either
-ignore vid to /etc/sensors.co
and change the min and max settings for the Processor Core voltage
(often in0_min and in0_max) in that file so that they don't depend on vid.
+
Node:Section 4.8,
-Next:Section 4.9,
-Previous:Section 4.7,
-Up:Problems
+Next:Section 4.9,
+Previous:Section 4.7,
+Up:Problems
+4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?
+4.8 I read sensor values several times a second, but they are only updated only each second or so. Why?
-
Node:Section 4.9,
-Next:Section 4.10,
-Previous:Section 4.8,
-Up:Problems
+Next:Section 4.10,
+Previous:Section 4.8,
+Up:Problems
+4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?
+4.9 It sometimes seems to take almost a second before I see the sensor reading results. Why?
-
Node:Section 4.10,
-Next:Section 4.11,
-Previous:Section 4.9,
-Up:Problems
+Next:Section 4.11,
+Previous:Section 4.9,
+Up:Problems
+4.10 Can I be alerted when an ALARM occurs?
+4.10 Can I be alerted when an ALARM occurs?
-
Node:Section 4.11,
-Next:Section 4.12,
-Previous:Section 4.10,
-Up:Problems
+Next:Section 4.12,
+Previous:Section 4.10,
+Up:Problems
+4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen). Why?
+4.11 SMBus transactions on my PIIX4 simply don't work (timeouts happen). Why?
-
Node:Section 4.12,
-Next:Section 4.13,
-Previous:Section 4.11,
-Up:Problems
+Next:Section 4.13,
+Previous:Section 4.11,
+Up:Problems
+4.12 My BIOS reports a much higher CPU temperature than your modules!
+4.12 My BIOS reports a much higher CPU temperature than your modules!
-chip lm75-*-49 # Or whatever chip this relates to
-label temp "Processor"
-compute temp @*1.2+13,(@-13)/1.2 # Or whatever formula
-
+ chip lm75-*-49 # Or whatever chip this relates to
+ label temp "Processor"
+ compute temp @*1.2+13,(@-13)/1.2 # Or whatever formula
+
+
Node:Section 4.13,
-Next:Section 4.14,
-Previous:Section 4.12,
-Up:Problems
+Next:Section 4.14,
+Previous:Section 4.12,
+Up:Problems
+4.13 I try to read the raw
+/proc files, but the values are strange?!?4.13 I try to read the raw
-/proc files, but the values are strange?!?compute lines in account. This is especially obvious for voltage readings
(usually called in? or vin?). Use a program linked to libsensors (like
the provided sensors program) instead.
+
Node:Section 4.14,
-Next:Section 4.15,
-Previous:Section 4.13,
-Up:Problems
+Next:Section 4.15,
+Previous:Section 4.13,
+Up:Problems
+4.14 How do I set new limits?
+4.14 How do I set new limits?
-/etc/sensors.conf and then run
+ /etc/sensors.conf and then run
sensors -s.
-4.14.1 I set new limits and it didn't work?
+4.14.1 I set new limits and it didn't work?
-sensors -s. Put it in a /etc/rc.d/... file
+ sensors -s. Put it in a /etc/rc.d/... file
after the modprobe lines to run at startup.
+
Node:Section 4.15,
-Next:Section 4.16,
-Previous:Section 4.14,
-Up:Problems
+Next:Section 4.16,
+Previous:Section 4.14,
+Up:Problems
+4.15 Some sensors are doubly detected?
+4.15 Some sensors are doubly detected?
-ignore= modprobe parameters it suggests.
+
Node:Section 4.16,
-Next:Section 4.17,
-Previous:Section 4.15,
-Up:Problems
+Next:Section 4.17,
+Previous:Section 4.15,
+Up:Problems
+4.16 I ran sensors-detect, but now I get very strange readings?!?
+4.16 I ran sensors-detect, but now I get very strange readings?!?
-
Node:Section 4.17,
-Next:Section 4.18,
-Previous:Section 4.16,
-Up:Problems
+Next:Section 4.18,
+Previous:Section 4.16,
+Up:Problems
+4.17 Bad readings from particular chips
+4.17 Bad readings from particular chips
-doc/chips/xxxxx for the particular driver.
-4.17.1 Bad readings from the AS99127F!
+4.17.1 Bad readings from the AS99127F!
-/etc/sensors.conf. Please don't ask us to
fix the driver. Ask Asus to release a datasheet.
-4.17.2 Bad readings from the VIA 686A!
+4.17.2 Bad readings from the VIA 686A!
-/etc/sensors.conf. Please don't ask us to
fix the driver. Ask Via to release a better datasheet.
Also, don't forget to modprobe i2c-isa.
-4.17.3 Bad readings from the MTP008!
+4.17.3 Bad readings from the MTP008!
-doc/chips/mtp008 for details.
Also, MTP008 chips seem to randomly refuse to respond, for
unknown reasons. You can see this as 'XX' entries in i2cdump.
-4.17.4 Bad temperature readings from the SIS5595!
+4.17.4 Bad temperature readings from the SIS5595!
-4.17.5 Bad readings from a w8378[12]d!
+4.17.5 Bad readings from a w8378[12]d!
-doc/chips/w83781d)
for more details.
-4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!
+4.17.6 Bus hangs on Ali 1543 on Asus P5A boards!
-ignore=1,0x2d or similar option
to the w83781d module to prevent i2c accesses.
-4.17.7 Bad readings from LM75!
+4.17.7 Bad readings from LM75!
-4.17.8 Bad readings from LM78!
+4.17.8 Bad readings from LM78!
-4.17.9 Bad readings from LM80!
+4.17.9 Bad readings from LM80!
-4.17.10 Bad readings from it87!
+4.17.10 Bad readings from it87!
-/etc/sensors.conf; they must be set at modprobe insertion with
modprobe it87 temp_type=0xXX. See doc/chips/it87 for details.
+
Node:Section 4.18,
-Next:Section 4.19,
-Previous:Section 4.17,
-Up:Problems
+Next:Section 4.19,
+Previous:Section 4.17,
+Up:Problems
+4.18 How do I configure two chips (LM87) differently?
+4.18 How do I configure two chips (LM87) differently?
-/etc/sensors.conf as follows:
-chip "lm87-i2c-*-2c"
- put configuration for the chip at 0x2c here
-chip "lm87-i2c-*-2d"
- put configuration for the chip at 0x2d here
-
+ /etc/sensors.conf as follows:
+ chip "lm87-i2c-*-2c"
+ put configuration for the chip at 0x2c here
+ chip "lm87-i2c-*-2d"
+ put configuration for the chip at 0x2d here
+
-sensors.conf.eg which should
+ sensors.conf.eg which should
be helpful.
+
Node:Section 4.19,
-Next:Section 4.20,
-Previous:Section 4.18,
-Up:Problems
+Next:Section 4.20,
+Previous:Section 4.18,
+Up:Problems
+4.19 Dmesg says
+Upgrade BIOS! I don't want to!4.19 Dmesg says
-Upgrade BIOS! I don't want to!lspci, the solution
+ lspci, the solution
is complex. For the ALI M7101 device, there is a solution which uses the
2.4 kernel's hotplug facility. See prog/hotplug in our package.
For other PCI devices, you can try to modify
the m7101 solution in prog/hotplug.
-try force_addr, see below. Other drivers generally do not
+ try force_addr, see below. Other drivers generally do not
support the force_addr parameter. Sorry. Check the documentation
for your driver in doc/[chips,busses] and if we don't support it
you can send us your request.
-4.19.1 Dmesg says
+use force_addr=0xaddr! What address do I use?4.19.1 Dmesg says
-use force_addr=0xaddr! What address do I use?modprobe via686a force_addr=0xADDRESS where ADDRESS
is the I/O address. You must select an address that is not in use.
-cat to check (carefully) for conflicts. A high number like
+/proc/ioportscat /proc/ioports to check (carefully) for conflicts. A high number like
0xf000 is generally safe.
+
Node:Section 4.20,
-Next:Section 4.21,
-Previous:Section 4.19,
-Up:Problems
+Next:Section 4.21,
+Previous:Section 4.19,
+Up:Problems
+4.20 Sensors says
+Can't access /proc file4.20 Sensors says
-Can't access /proc file
+
+modprobe i2c-proc? Check lsmod.
sensors -s, did you run it as root?
/proc support in your kernel (is /proc there?)
Node:Section 4.21,
-Next:Section 4.22,
-Previous:Section 4.20,
-Up:Problems
+Next:Section 4.22,
+Previous:Section 4.20,
+Up:Problems
+4.21 Sensors says
+No sensors found!4.21 Sensors says
-No sensors found!
+
+sensors-detect find sensors? (If not see Sensors-detect doesnt find any sensors)
sensors-detect said?
modprobe your sensor modules?
@@ -1338,17 +1448,19 @@ Up:Problems
lsmod.
Node:Section 4.22,
-Next:Section 4.23,
-Previous:Section 4.21,
-Up:Problems
+Next:Section 4.23,
+Previous:Section 4.21,
+Up:Problems
+4.22 Sensors output is not correct!
+4.22 Sensors output is not correct!
-
+
+
+
+
-sensors.conf calculation.
Node:Section 4.23,
-Next:Section 4.24,
-Previous:Section 4.22,
-Up:Problems
+Next:Section 4.24,
+Previous:Section 4.22,
+Up:Problems
+4.23 What is at I2C address XXX?
+4.23 What is at I2C address XXX?
-sensors-detect.
+ sensors-detect.
If it doesn't recognize it, try running i2cdump. A partial list
of manufacturers' IDs are at the bottom of doc/chips/SUMMARY.
-4.23.1 What is at I2C address 0x69?
+4.23.1 What is at I2C address 0x69?
-kernel/chips/icspll.c in our package. But we
do not recommend it. You have been warned.
-4.23.2 What is at I2C addresses 0x50 - 0x57?
+4.23.2 What is at I2C addresses 0x50 - 0x57?
-sensors or use the program
prog/eeprom/decode-dimms.pl to get more information than you ever wanted.
-4.23.3 What is at I2C addresses 0x30 - 0x37?
+4.23.3 What is at I2C addresses 0x30 - 0x37?
-i2cdump on them you won't get anything. This is probably
caused by some timing problem on your motherboard or on the DIMMs.
We don't know the exact cause.
+
Node:Section 4.24,
-Next:Section 4.25,
-Previous:Section 4.23,
-Up:Problems
+Next:Section 4.25,
+Previous:Section 4.23,
+Up:Problems
+4.24 Sensors-detect doesn't work at all
+4.24 Sensors-detect doesn't work at all
-4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"
+4.24.1 Sensors-detect says "Couldn't open /proc/bus/i2c?!?"
-4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"
+4.24.2 Sensors-detect says "Can't open /dev/i2c[-/]0"
-/dev/i2c-0, /dev/i2c0, or /dev/i2c/0 files do not exist
+ /dev/i2c-0, /dev/i2c0, or /dev/i2c/0 files do not exist
or you did not run sensors-detect as root.
Run the script prog/mkdev/mkdev.sh to create the /dev/i2c-x files.
Run devfs in the kernel to get the /dev/i2c/x files.
-4.24.3 Sensors-detect doesn't find any sensors!
+4.24.3 Sensors-detect doesn't find any sensors!
-
-
Either +
But in any case you should figure out what is on the board: -
But in any case you should figure out what is on the board: +
When you know what chips you have, check the +
When you know what chips you have, check the Newest Driver Status web page to see if support has been added for your chip in a later release or in CVS. +
Error: Line xxx: zzzzzzzError: Line xxx: zzzzzzzThese are errors from the libsensors library in +
These are errors from the libsensors library in
reading the /etc/sensors.conf configuration file. Go to that line
number and fix it. If you have a parse error, perhaps you have
to put the feature name in double quotes.
+
If sensors only says this, for example, and doesn't
+
If sensors only says this, for example, and doesn't
provide any actual data at all:
-
it87-isa-0290 -Adapter: ISA adapter -Algorithm: ISA algorithm -+
it87-isa-0290 + Adapter: ISA adapter + Algorithm: ISA algorithm +-
Your chip is not currently supported by sensors and so all it
+
Your chip is not currently supported by sensors and so all it
does is print out that information. Get the latest release
and be sure you are running the sensors program it installed
and not some older sensors.
+
ERROR: Can't get xxxxx data!ERROR: Can't get xxxxx data!You have a libsensors/sensors mismatch. sensors is unable to
+
You have a libsensors/sensors mismatch. sensors is unable to
get a data entry from libsensors. You probably have an
old libsensors in your /etc/ld.so.conf path.
Make sure you did (as root) a make install followed by a ldconfig.
@@ -1508,151 +1630,165 @@ Then check the output of ldconfig -v | grep libsensors to
verify that there is only ONE libsensors entry and that it matches
the libsensors that was built in the lib/ directory in lm_sensors2.
+
See Sensors-detect doesnt work at all, if sensors-detect failed to find any sensors.
+
See Sensors-detect doesnt work at all, if sensors-detect failed to find any sensors.
-
If sensors-detect did find sensors, did you insert your modules? For chips on the ISA
+
If sensors-detect did find sensors, did you insert your modules? For chips on the ISA
bus, did you insert i2c-isa?
-
See What to do if a module wont insert, if the modules didn't insert, +
See What to do if a module wont insert, if the modules didn't insert, also Sensors says No sensors found. +
There are several possible causes: -
There are several possible causes: +
init=0 for the w83781d driver; this is the only driver supporting this parameter.
i2cdetect on the bus, then i2cdump on each address responding to i2cdetect. This may find the culprit. Do not i2cdump address 0x69, the clock chip.
modprobe ignore_range=0,0x00,0x28,0,0x2a,0x7f to prevent access to other addresses. (init=0 also req'd for the Tyan 2688).
-Generally this is caused by an overtemperature alarm output from +
Generally this is caused by an overtemperature alarm output from
the sensor chip. This triggers hardware on the board which
automatically slows down the CPU clock. Be sure that your
temperature limits are above the temperature reading. Put
the new limits in /etc/sensors.conf and run sensors -s.
+
The following boards have unique problems and solutions. +
The following boards have unique problems and solutions. -
See prog/hotplug/README.p4b if your SMBus master is not found.
+
See prog/hotplug/README.p4b if your SMBus master is not found.
-
See support tickets 805, 765, 781, 812, 813, and 867 for information. +
See support tickets 805, 765, 781, 812, 813, and 867 for information. -
See support tickets 941, 840, and 841 for information. +
See support tickets 941, 840, and 841 for information. -
For board hangs, see support ticket 721 for information. +
For board hangs, see support ticket 721 for information. Also Inserting modules hangs my board. +
-For IBM systems, see README.thinkpad.
+
For IBM systems, see README.thinkpad.
+
We are always willing to answer questions if things don't work out. +
We are always willing to answer questions if things don't work out. Please email sensors@stimpy.netroedge.com, and not the individual authors, unless you have something private to say. -
Instead of using email, you can also use the web-based support +
Instead of using email, you can also use the web-based support area, at http://secure.netroedge.com/~lm78/support.html. You will be helped just as fast, and others may profit from the answer too. You will be emailed automatically when your question has been answered. -
Here's what you should send us: +
Here's what you should send us: -
prog/detect/sensors-detect
lsmod
lspci -n
prog/detect/i2cdetect X
where X = the bus number (run i2cdetect with no arguments to list the busses)
(please send this only if it's not all XX)
@@ -1660,222 +1796,252 @@ where X = the bus number (run i2cdetect with no arguments to list t
where XX = the address of each chip you see in the output of i2cdetect. (run once for each chip)
(please send this only if it's not all ff)
prog/dump/isadump 0x295 0x296 (only if it's not all XX)
Did you use modprobe instead of insmod??? Don't use insmod.
+
Did you use modprobe instead of insmod??? Don't use insmod.
-
Were there unresolved symbols? Did you run depmod -a? Run
+
Were there unresolved symbols? Did you run depmod -a? Run
depmod -a -e to see where the symbol problem is.
-
ALWAYS inspect the output of dmesg. That's where the error
+
ALWAYS inspect the output of dmesg. That's where the error
messages come out!!! Don't rely on the generic message from modprobe.
If you still can't figure it out, send us the information
listed above.
+
For an ISA sensor chip, did you also modprobe i2c-isa? It must be inserted.
+
For an ISA sensor chip, did you also modprobe i2c-isa? It must be inserted.
-
For an I2C sensor chip, did you also modprobe i2c-xxx where xxx is your
+
For an I2C sensor chip, did you also modprobe i2c-xxx where xxx is your
I2C bus adapter? It must be inserted.
-
Always inspect the output of dmesg. That's where the error
+
Always inspect the output of dmesg. That's where the error
messages come out. If you still can't figure it out, send us the information
listed above.
+
It may be that this was a mis-detection: the chip may not be +
It may be that this was a mis-detection: the chip may not be present. If you are convinced there is something wrong, verify that you indeed have the devices on your motherboard that you think you do. Look at the motherboard and make sure. If you are still stuck, please send us the usual information (see Help) +
Again, send the output listed above. +
Again, send the output listed above. +
Drop us a mail if you feel like it, mentioning the mainboard and +
Drop us a mail if you feel like it, mentioning the mainboard and detected chip type. That way, we have some positive feedback, too! +
You can't. Only developers can. Follow up by emailing us +
You can't. Only developers can. Follow up by emailing us at sensors@stimpy.netroedge.com and reference your ticket number in the subject. Please don't enter a new ticket with follow-up information, email us instead. Thanks. +
-Follow up by emailing us at sensors@stimpy.netroedge.com +
Follow up by emailing us at sensors@stimpy.netroedge.com and reference your ticket number in the subject. +
See doc/developers/new_drivers in our package for instructions.
+
See doc/developers/new_drivers in our package for instructions.
+
For anonymous CVS read access, see the instructions on our download page. +
For anonymous CVS read access, see the instructions on our download page. Sorry, we don't have automatically generated CVS tarballs. -
For write access, run the script doc/developers/genpasswd.pl in
+
For write access, run the script doc/developers/genpasswd.pl in
our package and follow the instructions. Let us know what part
of the package you would like to work on.
+
Send us email sensors@stimpy.netroedge.com. +
Send us email sensors@stimpy.netroedge.com. +
Send us email sensors@stimpy.netroedge.com. Sorry, +
Send us email sensors@stimpy.netroedge.com. Sorry, there is no automated subscribe/unsubscribe service. +
The mailing list archive is at: http://archives.andrew.net.au/lm-sensors +
The mailing list archive is at: http://archives.andrew.net.au/lm-sensors Sorry, it only contains messages since October 28, 2001. +
Check out the latest from CVS, then copy the directory to another +
Check out the latest from CVS, then copy the directory to another
directory, and make your changes. Generate the diff with
diff -u2 -r DIR1 DIR2. Or you can generate the diff in CVS with
cvs diff -u2. Send us the patch in an email and tell us what it does.
+
Believe it or not, what we really need help with are: -
Believe it or not, what we really need help with are: +
Send us email sensors@stimpy.netroedge.com if you can help. +
Send us email sensors@stimpy.netroedge.com if you can help. No experience necessary :) +
-Sorry, we know the spam is a hassle. It would be nice to have a +
Sorry, we know the spam is a hassle. It would be nice to have a moderator who can screen everything, but that takes too much time and delays emails. Right now there is a procmail script which tags likely spam and puts in a X-SBClass: header. If it is followed by 'Spam', then @@ -1904,107 +2072,119 @@ rules in your mail client to throw those emails into a seperate folder. It's not bullet proof (some legit mails get tagged wrong, and vice versa), but it seems to be about 95% accurate in our experience. +
Note: Version 1 is very very old and is not recommended. +
Note: Version 1 is very very old and is not recommended. +
Currently, our code only assumes that an SMBus exists if it originates +
Currently, our code only assumes that an SMBus exists if it originates from the Intel PIIX4 (82371AB). If your computer doesn't have one, or if your SMBus originates from a different SMBus 'host', then you are out of luck. :'( Our experience is, though, that most machines have a PIIX4, and that it is where the SMBus is hosted. -
Regarding the VIA chip set(s): +
Regarding the VIA chip set(s): -
Right now, the SMBus code depends on the Intel PIIX4 chip to handle +
Right now, the SMBus code depends on the Intel PIIX4 chip to handle SMBus transactions. The VIA chip set is NOT supported at this time because it forces much of the SMBus protocol to be implemented by software. -
To implement the SMBus correctly with the VIA chip, it needs to be +
To implement the SMBus correctly with the VIA chip, it needs to be written at a low level to be quick. A more attractive alternative is to use the Bios SMBus interface (not always available nor standard). -
Version 2 supports the VIA chipset, and will support other chipsets. +
Version 2 supports the VIA chipset, and will support other chipsets. Version 1 never will. +
This should no longer be an issue in 1.4.10 and later; it will +
This should no longer be an issue in 1.4.10 and later; it will continue loading, but it won't support SMBus-connected devices, of course. +
/proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?/proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?It takes about 1.5 seconds for the LM78 to update all its sensor +
It takes about 1.5 seconds for the LM78 to update all its sensor
values. If we would try to read it before it finished that, you would get
old garbage instead. So you have to wait 1.5 seconds after the module is
inserted before you can access /proc/sensors.
-
Module versions 1.3.7 and later let the process sleep if it tries +
Module versions 1.3.7 and later let the process sleep if it tries to access sensor data right after insertion time, and do not display this message anymore. +
This is a bug we have only observed on Dell computers. There is +
This is a bug we have only observed on Dell computers. There is probably a problem with the way the SMBus is accessed; but it is not yet clear whether the problem is in our code or with the Dells. -
There are very probably no sensor chips at all on your computer; +
There are very probably no sensor chips at all on your computer; but until somebody contacts Dell about this and tells us the results, we can not be sure. +