C
opyright (c) 1998 - 2002
Frodo Looijaard,
Philip Edelbrock,
and
Mark Studebaker
-
/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 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 hardware health monitoring chip. This chip may be accessed via the @@ -249,12 +225,12 @@ a chip with similar functions.
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
@@ -277,11 +253,11 @@ chip is documented in the doc/chips directory.
Most semiconductor companies have comprehensive documentation, including complete datasheets, on their websites. Analog Devices, @@ -300,29 +276,29 @@ for links to other companies' websites.
Sensor chips reside on either the ISA bus, the SMBus, or both.
See the file doc/chips/SUMMARY in our package for a list.
@@ -335,12 +311,12 @@ use an SMBus interface device, explained below.
The SMBus is the "System Management Bus". More specifically, it is a 2-wire, low-speed serial communication bus used for basic health monitoring @@ -362,12 +338,12 @@ talk to pure I2C devices.
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; @@ -380,12 +356,12 @@ think "I/O Space".
Most new processors contain a thermal diode on the die itself. The electical properties of all diodes and transistors vary @@ -421,12 +397,12 @@ interface on the P2 Xeon SEC.
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 @@ -438,11 +414,11 @@ 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 crosses some pre-determined limits. There are two sorts of interrupts @@ -463,33 +439,33 @@ persists after that, the bits will be set on the next scanning sweep, etc.
/etc/sensors.conf?
-No such file or directory warnings
-make install fails on Mandrake kernels
-modprobe modules
+/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 easy to add new drivers, and unused drivers will take no precious kernel @@ -506,12 +482,12 @@ space. On the other hand, it can be a bit confusing at first.
We have an excellent program that scans all your hardware.
It is called sensors-detect and is installed in /usr/local/sbin
@@ -527,7 +503,7 @@ for candidates, then see Help)
!!!!!!!!! YES THIS IS THE MOST FREQUENT QUESTION WE GET !!!!!!!!! @@ -547,13 +523,13 @@ page on our website some good cro
We don't support boards, we support chips. See What chips are on motherboard XYZ.
This we have good answers for.
Newest Driver Status: http://www2.lm-sensors.nu/~lm78/newdrivers.html
sensors-detect will tell you. Take the modprobe lines it
recommends and paste them into the appropriate /etc/rc.d/xxxx file
@@ -597,12 +573,12 @@ following lines:
/etc/sensors.conf?/etc/sensors.conf?Yes, for any applications that use libsensors, including the
sensors application included in our package.
@@ -614,7 +590,7 @@ overwrite any existing file with that name.
sensors are incorrect!sensors are incorrect!Every motherboard is different. You can customize the labels
in the file /etc/sensors.conf. That's why it exists!
@@ -623,44 +599,44 @@ a template.
sensors are incorrect!sensors are incorrect!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.
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.
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 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 files should be recompiled when certain files change) are created @@ -670,12 +646,12 @@ it will do is generate them. So all is well.
Check that the correct i2c header files are used. Depending on
how you installed, they should be under either /usr/local/include or
@@ -683,7 +659,7 @@ how you installed, they should be under either /usr/local/include o
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.
@@ -694,12 +670,12 @@ how you installed, they should be under either /usr/local/include o
Have you installed the matching version of the i2c package? Remember, compilation is not enough, you also need to install it for the header @@ -710,27 +686,27 @@ patches first!
make install fails on Mandrake kernelsmake install fails on Mandrake kernelsMandrake 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 +*** Unresolved symbols in /lib/modules/2.4.5/kernel/drivers/i2c/i2c-i810.o i2c_bit_add_bus_R8c3bc60e i2c_bit_del_bus_R92b18f49@@ -760,11 +736,11 @@ versioning problem.
Node:Section 3.10, -Previous:Section 3.9, -Up:Installation +Previous:Section 3.9, +Up:Installation
-3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
+3.10 I2C_DRIVERID_ADM1024 undefined (Red Hat especially)
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 @@ -781,7 +757,7 @@ 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 cleanmake
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
@@ -847,7 +824,7 @@ 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
+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
@@ -857,7 +834,7 @@ compute fan1 @/2,2*@ # This will halve the fan1 reading
4.1.1 Fans sometimes/always read 0!!
+4.1.1 Fans sometimes/always read 0!!
You may not have a three-wire fan, which is required.
@@ -866,7 +843,7 @@ in our package for further information.
4.1.2 I doubled the fan divisor and the fan still reads 7000!
+4.1.2 I doubled the fan divisor and the fan still reads 7000!
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.
@@ -875,12 +852,12 @@ and see doc/fan-divisors in our package for further information.
Node:Section 4.2,
-Next:Section 4.3,
-Previous:Section 4.1,
-Up:Problems
+Next:Section 4.3,
+Previous:Section 4.1,
+Up:Problems
-4.2 Why do my two LM75's report "-48 degrees"?
+4.2 Why do my two LM75's report "-48 degrees"?
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
@@ -895,12 +872,12 @@ readings.
Node:Section 4.3,
-Next:Section 4.4,
-Previous:Section 4.2,
-Up:Problems
+Next:Section 4.4,
+Previous:Section 4.2,
+Up:Problems
-4.3 Why do I have two Vcore readings, I have only one processor!
+4.3 Why do I have two Vcore readings, I have only one processor!
The LM78 has seven voltage sensors. The default way of
connecting them is used in the configuration file. This includes a VCore2,
@@ -917,12 +894,12 @@ different.
Node:Section 4.4,
-Next:Section 4.5,
-Previous:Section 4.3,
-Up:Problems
+Next:Section 4.5,
+Previous:Section 4.3,
+Up:Problems
-4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!
+4.4 How do those ALARMS work? The current value is within range but there is still an ALARM warning!
The ALARM indications in sensors are those reported by the
sensor chip itself. They are NOT calculated by sensors. sensors
@@ -946,12 +923,12 @@ chip datasheet for more information.
Node:Section 4.5,
-Next:Section 4.6,
-Previous:Section 4.4,
-Up:Problems
+Next:Section 4.6,
+Previous:Section 4.4,
+Up:Problems
-4.5 My voltage readings seem to drift a bit. Is something wrong?
+4.5 My voltage readings seem to drift a bit. Is something wrong?
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
@@ -964,12 +941,12 @@ reason to worry.
Node:Section 4.6,
-Next:Section 4.7,
-Previous:Section 4.5,
-Up:Problems
+Next:Section 4.7,
+Previous:Section 4.5,
+Up:Problems
-4.6 Some measurements are way out of range. What happened?
+4.6 Some measurements are way out of range. What happened?
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
@@ -985,12 +962,12 @@ more information.
Node:Section 4.7,
-Next:Section 4.8,
-Previous:Section 4.6,
-Up:Problems
+Next:Section 4.8,
+Previous:Section 4.6,
+Up:Problems
-4.7 What are VID lines? Why is the VID reading wrong?
+4.7 What are VID lines? Why is the VID reading wrong?
These describe the core voltage for your processor. They are
supported for most processors, however they are not always
@@ -1002,12 +979,12 @@ and change the min and max settings for the Processor Core voltage
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?
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
@@ -1016,12 +993,12 @@ at all).
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?
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,
@@ -1030,12 +1007,12 @@ while we are waiting for the transaction to finish.
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?
No, you can't; and it may well be never supported.
@@ -1056,12 +1033,12 @@ programs under X, see 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?
Some chips which mainboard makers connect to the SMBus are not SMBus
devices. An example is the 91xx clock generator chips. When read, these
@@ -1075,12 +1052,12 @@ written to, but lock things up when they are read.
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!
We display the actual temperature of the sensor. This may not be the
temperature you are interested in, though. If a sensor should measure
@@ -1090,19 +1067,19 @@ 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:
-
chip lm75-*-49 # Or whatever chip this relates to
+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?!?
Remember, these values do not take the configuration file
compute lines in account. This is especially obvious for voltage readings
@@ -1111,31 +1088,31 @@ 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?
Change the limit values in /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?
You forgot to run 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?
Yes, this is still a problem. It is partially solved by alias detection
and confidence values in sensors-detect, but it is really tough.
@@ -1149,12 +1126,12 @@ run sensors-detect and add the ignore= modprobe parameters it sugge
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?!?
Your SMBus (PIIX4?) is probably crashed or hung. There are some mainboards
which connect a clock chip to the SMBus. Unfortunately, this clock chip
@@ -1166,19 +1143,19 @@ scan the PIIX4.
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
See below for some particularly troublesome chips.
Also be sure and check doc/chips/xxxxx for the particular driver.
4.17.1 Bad readings from the AS99127F!
+4.17.1 Bad readings from the AS99127F!
The Asus AS99127F is a modified version of the Winbond W83781D.
Asus will not release a datasheet. The driver was developed by tedious
@@ -1188,7 +1165,7 @@ 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!
The Via 686A datasheet is incomplete.
Via will not release details. The driver was developed by tedious
@@ -1199,7 +1176,7 @@ Also, don't forget to modprobe i2c-isa.
4.17.3 Bad readings from the MTP008!
+4.17.3 Bad readings from the MTP008!
The MTP008 has programmable temperature sensor types.
If your sensor type does not match the default, you will have to change it.
@@ -1209,7 +1186,7 @@ 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!
This chip can use multiple thermistor types and there are also
two different versions of the chip. We are trying to get the driver
@@ -1220,7 +1197,7 @@ misidentified. We are working on improving that too.
4.17.5 Bad readings from a w8378[12]d!
+4.17.5 Bad readings from a w8378[12]d!
Do you own an ASUS motherboard? Perhaps your chip is being
misidentified. Look on the motherboard (or at
@@ -1234,7 +1211,7 @@ 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!
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
@@ -1243,14 +1220,14 @@ to the w83781d module to prevent i2c accesses.
4.17.7 Bad readings from LM75!
+4.17.7 Bad readings from LM75!
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.
4.17.8 Bad readings from LM78!
+4.17.8 Bad readings from LM78!
The LM78 is no longer manufactured by National Semiconductor.
You probably don't have a real LM78 but something similar that we
@@ -1258,14 +1235,14 @@ do not recogize or support. Figure out what you really have See
-
4.17.9 Bad readings from LM80!
+4.17.9 Bad readings from LM80!
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.
4.17.10 Bad readings from it87!
+4.17.10 Bad readings from it87!
The it87 temperature sesnsors are configured, unfortunately,
in a way different from w83781d. They cannot be configured from
@@ -1274,19 +1251,19 @@ in a way different from w83781d. They cannot be configured from
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?
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 /etc/sensors.conf as follows:
-
chip "lm87-i2c-*-2c"
+chip "lm87-i2c-*-2c"
put configuration for the chip at 0x2c here
chip "lm87-i2c-*-2d"
put configuration for the chip at 0x2d here
@@ -1297,12 +1274,12 @@ 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!
If the problem is a PCI device is not present in lspci, the solution
is complex. For the ALI M7101 device, there is a solution which uses the
@@ -1317,7 +1294,7 @@ 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?
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
@@ -1329,12 +1306,12 @@ is the I/O address. You must select an address that is not in use.
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 file
+4.20 Sensors says Can't access /proc file
modprobe i2c-proc? Check lsmod.
@@ -1345,12 +1322,12 @@ Up:Problems
No sensors found!No sensors found!sensors-detect find sensors? (If not see Sensors-detect doesnt find any sensors)
@@ -1363,12 +1340,12 @@ Up:Problems
What specifically is the trouble?
In general, we don't know. Start by running sensors-detect.
If it doesn't recognize it, try running i2cdump. A partial list
@@ -1402,7 +1379,7 @@ of manufacturers' IDs are at the bottom of doc/chips/SUMMARY.
A clock chip. Often, accessing these clock chips in the wrong way will instantly crash your computer. Sensors-detect carefully @@ -1412,7 +1389,7 @@ do not recommend it. You have been warned.
EEPROMs on your SDRAM DIMMs. Load the eeprom module to
look at some basic data in sensors or use the program
@@ -1420,7 +1397,7 @@ look at some basic data in sensors or use the program
These are often 'shadows' of your EEPROMs on your SDRAM DIMMs at addresses 0x50 - 0x57. They aren't really there. If you try and @@ -1430,25 +1407,25 @@ We don't know the exact cause.
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 was not loaded and you did not run sensors-detect as root.
Your /dev/i2c-0, /dev/i2c0, or /dev/i2c/0 files do not exist
or you did not run sensors-detect as root.
@@ -1457,7 +1434,7 @@ Run devfs in the kernel to get the /dev/i2c/x files.
Either
Error: Line xxx: zzzzzzzError: Line xxx: zzzzzzzThese are errors from the libsensors library in
reading the /etc/sensors.conf configuration file. Go to that line
@@ -1494,17 +1471,17 @@ to put the feature name in double quotes.
If sensors only says this, for example, and doesn't
provide any actual data at all:
-
it87-isa-0290 +it87-isa-0290 Adapter: ISA adapter Algorithm: ISA algorithm@@ -1516,12 +1493,12 @@ and not some oldersensors.
Node:Section 4.27, -Next:Section 4.28, -Previous:Section 4.26, -Up:Problems +Next:Section 4.28, +Previous:Section 4.26, +Up:Problems
-4.27 Sensors says
+ERROR: Can't get xxxxx data!4.27 Sensors says
ERROR: Can't get xxxxx data!You have a
libsensors/sensorsmismatch.sensorsis unable to get a data entry fromlibsensors. You probably have an @@ -1533,12 +1510,12 @@ thelibsensorsthat was built in thelib/directory in
Node:Section 4.28, -Next:Section 4.29, -Previous:Section 4.27, -Up:Problems +Next:Section 4.29, +Previous:Section 4.27, +Up:Problems
-4.28 Sensors doesn't find any sensors, just eeproms.
+4.28 Sensors doesn't find any sensors, just eeproms.
See Sensors-detect doesnt work at all, if
sensors-detectfailed to find any sensors. @@ -1550,12 +1527,12 @@ also Sensors says No sensors found.
Node:Section 4.29, -Next:Section 4.30, -Previous:Section 4.28, -Up:Problems +Next:Section 4.30, +Previous:Section 4.28, +Up:Problems
-4.29 Inserting modules hangs my board
+4.29 Inserting modules hangs my board
There are several possible causes:
@@ -1568,12 +1545,12 @@ Up:Problems
Node:Section 4.30, -Next:Section 4.31, -Previous:Section 4.29, -Up:Problems +Next:Section 4.31, +Previous:Section 4.29, +Up:Problems
-4.30 Inserting modules slows down my board
+4.30 Inserting modules slows down my board
Generally this is caused by an overtemperature alarm output from the sensor chip. This triggers hardware on the board which @@ -1583,66 +1560,77 @@ the new limits in
/etc/sensors.confand runsensors -s
Node:Section 4.31, -Previous:Section 4.30, -Up:Problems +Next:Section 4.32, +Previous:Section 4.30, +Up:Problems
-4.31 Problems on particular motherboards
+4.31 Problems on particular motherboards
The following boards have unique problems and solutions.
4.31.1 Asus P4B
+4.31.1 Asus P4B
See
prog/hotplug/README.p4bif your SMBus master is not found.4.31.2 Tyan 2460, 2462
+4.31.2 Tyan 2460, 2462
See support tickets 805, 765, 781, 812, 813, and 867 for information.
4.31.3 Tyan 2466
+4.31.3 Tyan 2466
See support tickets 941, 840, and 841 for information.
4.31.4 Tyan 2688
+4.31.4 Tyan 2688
For board hangs, see support ticket 721 for information. Also Inserting modules hangs my board.
-Node:Help, -Next:Contribute, -Previous:Problems, -Up:Top +Node:Section 4.32, +Previous:Section 4.31, +Up:Problems
-5 How to Ask for Help
+4.32 Problems on particular systems
+ +For IBM systems, see
README.thinkpad. + +
+Node:Help, +Next:Contribute, +Previous:Problems, +Up:Top +
+ +5 How to Ask for Help
-
- Section 5.1: What to send us when asking for help -
- Section 5.2: What to do if a module won't insert? -
- Section 5.3: What to do if it inserts, but nothing happens? -
- Section 5.4: What to do if I read only bogus information? -
- Section 5.5: What to do if you have other problems? -
- Section 5.6: What if it just works like a charm? -
- Section 5.7: How do I update a ticket? -
- Section 5.8: How do I follow up on a ticket? +
- Section 5.1: What to send us when asking for help +
- Section 5.2: What to do if a module won't insert? +
- Section 5.3: What to do if it inserts, but nothing happens? +
- Section 5.4: What to do if I read only bogus information? +
- Section 5.5: What to do if you have other problems? +
- Section 5.6: What if it just works like a charm? +
- Section 5.7: How do I update a ticket? +
- Section 5.8: How do I follow up on a ticket?
Node:Section 5.1, -Next:Section 5.2, -Up:Help +Next:Section 5.2, +Up:Help
-5.1 What to send us when asking for help
+5.1 What to send us when asking for help
We are always willing to answer questions if things don't work out. Please email sensors@stimpy.netroedge.com, and not the individual authors, @@ -1684,12 +1672,12 @@ where XX = the address of each chip you see in the output of
i2cdetect
Node:Section 5.2, -Next:Section 5.3, -Previous:Section 5.1, -Up:Help +Next:Section 5.3, +Previous:Section 5.1, +Up:Help
-5.2 What to do if a module won't insert?
+5.2 What to do if a module won't insert?
Did you use
modprobeinstead ofinsmod??? Don't use insmod. @@ -1703,12 +1691,12 @@ listed above.
Node:Section 5.3, -Next:Section 5.4, -Previous:Section 5.2, -Up:Help +Next:Section 5.4, +Previous:Section 5.2, +Up:Help
-5.3 What to do if it inserts, but nothing happens?
+5.3 What to do if it inserts, but nothing happens?
For an ISA sensor chip, did you also
modprobe i2c-isa? It must be inserted. @@ -1721,12 +1709,12 @@ listed above.
Node:Section 5.4, -Next:Section 5.5, -Previous:Section 5.3, -Up:Help +Next:Section 5.5, +Previous:Section 5.3, +Up:Help
-5.4 What to do if I read only bogus information?
+5.4 What to do if I read only bogus information?
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 @@ -1736,35 +1724,35 @@ please send us the usual information (see Help)
Node:Section 5.5, -Next:Section 5.6, -Previous:Section 5.4, -Up:Help +Next:Section 5.6, +Previous:Section 5.4, +Up:Help
-5.5 What to do if you have other problems?
+5.5 What to do if you have other problems?
Again, send the output listed above.
Node:Section 5.6, -Next:Section 5.7, -Previous:Section 5.5, -Up:Help +Next:Section 5.7, +Previous:Section 5.5, +Up:Help
-5.6 What if it just works like a charm?
+5.6 What if it just works like a charm?
Drop us a mail if you feel like it, mentioning the mainboard and detected chip type. That way, we have some positive feedback, too!
Node:Section 5.7, -Next:Section 5.8, -Previous:Section 5.6, -Up:Help +Next:Section 5.8, +Previous:Section 5.6, +Up:Help
-5.7 How do I update a ticket?
+5.7 How do I update a ticket?
You can't. Only developers can. Follow up by emailing us at sensors@stimpy.netroedge.com and reference your ticket number @@ -1773,53 +1761,53 @@ follow-up information, email us instead. Thanks.
Node:Section 5.8, -Previous:Section 5.7, -Up:Help +Previous:Section 5.7, +Up:Help
-5.8 How do I follow up on a ticket?
+5.8 How do I follow up on a ticket?
Follow up by emailing us at sensors@stimpy.netroedge.com and reference your ticket number in the subject.
Node:Contribute, -Next:Version 1 Specifics, -Previous:Help, -Up:Top +Next:Version 1 Specifics, +Previous:Help, +Up:Top
-6 How to Contribute
+6 How to Contribute
-
- Section 6.1: How to write a driver -
- Section 6.2: How to get CVS access -
- Section 6.3: How to donate hardware to the project -
- Section 6.4: How to join the project mailing list -
- Section 6.5: How to access mailing list archives -
- Section 6.6: How to submit a patch -
- Section 6.7: How to REALLY help -
- Section 6.8: How to block spam on the project mailing list +
- Section 6.1: How to write a driver +
- Section 6.2: How to get CVS access +
- Section 6.3: How to donate hardware to the project +
- Section 6.4: How to join the project mailing list +
- Section 6.5: How to access mailing list archives +
- Section 6.6: How to submit a patch +
- Section 6.7: How to REALLY help +
- Section 6.8: How to block spam on the project mailing list
Node:Section 6.1, -Next:Section 6.2, -Up:Contribute +Next:Section 6.2, +Up:Contribute
-6.1 How to write a driver
+6.1 How to write a driver
See
doc/developers/new_driversin our package for instructions.
Node:Section 6.2, -Next:Section 6.3, -Previous:Section 6.1, -Up:Contribute +Next:Section 6.3, +Previous:Section 6.1, +Up:Contribute
-6.2 How to get CVS access
+6.2 How to get CVS access
For anonymous CVS read access, see the instructions on our download page. Sorry, we don't have automatically generated CVS tarballs. @@ -1830,47 +1818,47 @@ of the package you would like to work on.
Node:Section 6.3, -Next:Section 6.4, -Previous:Section 6.2, -Up:Contribute +Next:Section 6.4, +Previous:Section 6.2, +Up:Contribute
-6.3 How to donate hardware to the project
+6.3 How to donate hardware to the project
Send us email sensors@stimpy.netroedge.com.
Node:Section 6.4, -Next:Section 6.5, -Previous:Section 6.3, -Up:Contribute +Next:Section 6.5, +Previous:Section 6.3, +Up:Contribute
-6.4 How to join the project mailing list
+6.4 How to join the project mailing list
Send us email sensors@stimpy.netroedge.com. Sorry, there is no automated subscribe/unsubscribe service.
Node:Section 6.5, -Next:Section 6.6, -Previous:Section 6.4, -Up:Contribute +Next:Section 6.6, +Previous:Section 6.4, +Up:Contribute
-6.5 How to access mailing list archives
+6.5 How to access mailing list archives
The mailing list archive is at: http://archives.andrew.net.au/lm-sensors Sorry, it only contains messages since October 28, 2001.
Node:Section 6.6, -Next:Section 6.7, -Previous:Section 6.5, -Up:Contribute +Next:Section 6.7, +Previous:Section 6.5, +Up:Contribute
-6.6 How to submit a patch
+6.6 How to submit a patch
Check out the latest from CVS, then copy the directory to another directory, and make your changes. Generate the diff with @@ -1879,12 +1867,12 @@ directory, and make your changes. Generate the diff with
Node:Section 6.7, -Next:Section 6.8, -Previous:Section 6.6, -Up:Contribute +Next:Section 6.8, +Previous:Section 6.6, +Up:Contribute
-6.7 How to REALLY help
+6.7 How to REALLY help
Believe it or not, what we really need help with are:
@@ -1900,11 +1888,11 @@ No experience necessary :)
Node:Section 6.8, -Previous:Section 6.7, -Up:Contribute +Previous:Section 6.7, +Up:Contribute
-6.8 How to block spam on the project mailing list
+6.8 How to block spam on the project mailing list
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 @@ -1918,29 +1906,29 @@ versa), but it seems to be about 95% accurate in our experience.
Node:Version 1 Specifics, -Next:Document Revisions, -Previous:Contribute, -Up:Top +Next:Document Revisions, +Previous:Contribute, +Up:Top
-7 Version 1 Specific Questions
+7 Version 1 Specific Questions
-
- Section 7.1: My mainboard has an SMBus, your code can't find it. Why? -
- Section 7.2: The modules won't load, saying 'SMBus not detected'. -
- Section 7.3: I get a "No sensor data yet (try again in a few moments)" msg. -
- Section 7.4: On my Dell, a LM80 is detected, but all readings are 0! +
- Section 7.1: My mainboard has an SMBus, your code can't find it. Why? +
- Section 7.2: The modules won't load, saying 'SMBus not detected'. +
- Section 7.3: I get a "No sensor data yet (try again in a few moments)" msg. +
- Section 7.4: On my Dell, a LM80 is detected, but all readings are 0!
Note: Version 1 is very very old and is not recommended.
Node:Section 7.1, -Next:Section 7.2, -Up:Version 1 Specifics +Next:Section 7.2, +Up:Version 1 Specifics
-7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?
+7.1 My manufacturer swears that my mainboard has an SMBus, but your code reports that it can't find it. What's wrong?
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 @@ -1963,24 +1951,24 @@ Version 1 never will.
Node:Section 7.2, -Next:Section 7.3, -Previous:Section 7.1, -Up:Version 1 Specifics +Next:Section 7.3, +Previous:Section 7.1, +Up:Version 1 Specifics
-7.2 The modules won't load, saying 'SMBus not detected'.
+7.2 The modules won't load, saying 'SMBus not detected'.
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.
Node:Section 7.3, -Next:Section 7.4, -Previous:Section 7.2, -Up:Version 1 Specifics +Next:Section 7.4, +Previous:Section 7.2, +Up:Version 1 Specifics
-7.3 I try to read
+/proc/sensors, and I get a "No sensor data yet (try again in a few moments)" message. Why?7.3 I try to read
/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 values. If we would try to read it before it finished that, you would get @@ -1993,11 +1981,11 @@ message anymore.
Node:Section 7.4, -Previous:Section 7.3, -Up:Version 1 Specifics +Previous:Section 7.3, +Up:Version 1 Specifics
-7.4 On my Dell, a LM80 is detected, but all readings are 0!
+7.4 On my Dell, a LM80 is detected, but all readings are 0!
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 @@ -2009,11 +1997,11 @@ can not be sure.
Node:Document Revisions, -Previous:Version 1 Specifics, -Up:Top +Previous:Version 1 Specifics, +Up:Top
-Appendix A Revision History of This Document
+Appendix A Revision History of This Document
+ diff --git a/doc/lm_sensors-FAQ.texi b/doc/lm_sensors-FAQ.texi index 2b82b93f..4bf05b1e 100644 --- a/doc/lm_sensors-FAQ.texi +++ b/doc/lm_sensors-FAQ.texi @@ -567,6 +567,7 @@ to work. * Section 4.29:: Inserting modules hangs my board * Section 4.30:: Inserting modules slows down my board * Section 4.31:: Problems on particular motherboards +* Section 4.32:: Problems on particular systems @end menu @@ -1173,7 +1174,7 @@ temperature limits are above the temperature reading. Put the new limits in @file{/etc/sensors.conf} and run @command{sensors -s}. -@node Section 4.31, , Section 4.30, Problems +@node Section 4.31, Section 4.32, Section 4.30, Problems @section Problems on particular motherboards The following boards have unique problems and solutions. @@ -1204,6 +1205,12 @@ For board hangs, see support ticket 721 for information. Also @ref{Section 4.29, Inserting modules hangs my board}. +@node Section 4.32, , Section 4.31, Problems +@section Problems on particular systems + +For IBM systems, see @file{README.thinkpad}. + + @node Help, Contribute, Problems, Top @chapter How to Ask for Help
- Rev 2.9 (CP) Converted to Gnu texinfo format, 20020910 @@ -2040,3 +2028,4 @@ Up:Top