Issue: There is a bug in k10temp with >=2.6.39 kernels that when loading the k10temp module an error is thrown: "k10temp unreliable CPU thermal sensor; monitoring disabled".

+

Some K10 processors have issues with their temperature sensor. From the kernel documentation ({{Filename|linux-&lt;version&gt;/Documentation/hwmon/k10temp}}):

+

:''All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless you specify the "force=1" module parameter.''

−

Solution:

+

:''Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, if you are using an AM3 processor on an AM2+ mainboard, you can safely use the "force=1" parameter.''

−

* Load module with force=1

+

+

On affected machines the module will report "unreliable CPU thermal sensor; monitoring disabled". If you still want to use the module you can:

# rmmod k10temp

# rmmod k10temp

# modprobe k10temp force=1

# modprobe k10temp force=1

−

Confirm with [[Lm_sensors#Testing your lm_sensors]] that the sensor is in fact valid and reliable, if it is you can then make it apply at boot:

+

Confirm with [[Lm_sensors#Testing your lm_sensors]] that the sensor is in fact valid and reliable. If it is, you can edit {{Filename|/etc/modprobe.d/k10temp.conf}} and add:

−

Edit "/etc/modprobe.d/k10temp.conf" and add:

options k10temp force=1

options k10temp force=1

+

This will allow the module to load at boot.

==See also==

==See also==

*[[hddtemp]] - Software to read temps of HDDs.

*[[hddtemp]] - Software to read temps of HDDs.

*[[monitorix]] - Monitorix is a free, open source, lightweight system monitoring tool designed to monitor as many services and system resources as possible.

*[[monitorix]] - Monitorix is a free, open source, lightweight system monitoring tool designed to monitor as many services and system resources as possible.

Revision as of 03:26, 7 September 2011

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Usage

Installation

Setting up lm_sensors

Use sensors-detect to detect and generate a list of kernel modules:

# sensors-detect

This will create the Template:Filename configuration file which is used by the Template:Codeline daemon to automatically load kernel modules on boot. You will be asked if you want to probe for various hardware. The "safe" answers are the defaults so just hitting enter to all the questions will generally not cause any problems.

When the detection is finished, you will be presented with a summary of the probes. Here is an example summary from my system:

Template:Package AUR - an applet for the GNOME Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings.

Template:Package AUR - a GNOME Panel applet that displays some sensors readings as well as other hardware monitoring.

sensord

There is an optional daemon called sensord (included with the lm_sensors package) which can log your data to a round robin database (rrd) and later visualize graphically. See the sensord man page for details.

Troubleshooting

Sensors not working since Linux 2.6.31

A change in version 2.6.31 has made some sensors stop working. See this FAQ entry for a detailed explanation and for some example errors. To fix sensors, add the following to your kernel boot line (e.g. in your GRUB/GRUB2 configuration file) and reboot your machine:

acpi_enforce_resources=lax

Warning: In some situations, this may be dangerous. Consult the FAQ for details.

Note that in most cases the information is still accessible via other modules (e.g. via ACPI modules) for the hardware in question. Many utilities and monitors (e.g. /usr/bin/sensors) can gather information from either source. Where possible, this is the preferred solution.

Asus P8P67, Intel dh67cf motherboard

This article or section is out of date.

Reason:please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Lm sensors#)

K10Temp Module

Some K10 processors have issues with their temperature sensor. From the kernel documentation (Template:Filename):

All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless you specify the "force=1" module parameter.

Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, if you are using an AM3 processor on an AM2+ mainboard, you can safely use the "force=1" parameter.

On affected machines the module will report "unreliable CPU thermal sensor; monitoring disabled". If you still want to use the module you can: