Hardware Temperature Monitor

admin
  • The definition of the S 2-RM is independent of vendor software and hardware systems. Both allow the monitoring of physical or environmental conditions, such as temperature, sound, vibration.
  • The free Open Hardware Monitor software runs on Microsoft Windows with the.NET Framework version 4.5 and above. On Linux systems the Open Hardware Monitor requires Mono with WinForms.

CPU Temp, Fan Speeds, Mainboard Voltages, GPU Sensors and Hard Disk Temperatures of a PC The Open Hardware Monitor is a free open source software that monitors temperature sensors.

HWMonitor is a small and free system monitoring application which can keep tabs on different components and sensors on a Windows PC.

The application is small and fast. HWMonitor requires little in terms of configuration and immediately starts monitoring your system when you run the program.

The information that HWMonitor provides can be useful and includes details about the system CPU, hard drive and graphics adapter. It displays details about voltage, speed, temperature and more.

The system information that HWMonitor collects can be exported as a text document for future reference.

Overall, HWMonitor is a useful tool to find out details about installed components on a Windows PC.

HWMonitor 1.44.0 on 32-bit and 64-bit PCs

This download is licensed as freeware for the Windows (32-bit and 64-bit) operating system on a laptop or desktop PC from hardware diagnostic software without restrictions. HWMonitor 1.44.0 is available to all software users as a free download for Windows.

Filed under:
  1. HWMonitor Download
  2. Freeware Hardware Diagnostic Software
  3. Major release: HWMonitor 1.44
  4. Hardware Monitoring Software

lm_sensors (Linux monitoring sensors) is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors.

Installation

Install the lm_sensors package.

Note: More documentation is at the GitHub repository. In the future these may be installed, see FS#48354.

Setup

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

Warning: Do not use anything other than the default options (by just hitting Enter), unless you know exactly what you are doing. See #Laptop screen issues after running sensors-detect.

It will ask 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. This will create the /etc/conf.d/lm_sensors configuration file which is used by lm_sensors.service to automatically load kernel modules on boot.

When the detection is finished, a summary of the probes is presented.

Example:

Note: A systemd service is automatically enabled if users answer YES when asked about generating /etc/conf.d/lm_sensors. Answering YES also automatically starts the service.

Running sensors

Example running sensors:

Reading SPD values from memory modules (optional)

To read the SPD timing values from memory modules, install the i2c-tools package. Once installed, load the eepromkernel module.

Finally, view memory information with decode-dimms.

Here is partial output from one machine:

Using sensor data

Graphical front-ends

There are a variety of front-ends for sensors data.

  • psensor — GTK application for monitoring hardware sensors, including temperatures and fan speeds. Monitors motherboard and CPU (using lm-sensors), Nvidia GPUs (using XNVCtrl), and harddisks (using hddtemp or libatasmart).
https://wpitchoune.net/psensor/ psensor
  • xsensors — X11 interface to lm_sensors.
Computer
https://linuxhardware.org/xsensors/ xsensors

For specific Desktop environments:

  • Freon (GNOME Shell extension) — Extension for displaying CPU temperature, disk temperature, video card temperature , voltage and fan RPM in GNOME Shell.
https://github.com/UshakovVasilii/gnome-shell-extension-freon gnome-shell-extension-freonAUR
  • GNOME Sensors Applet — Applet for the GNOME Panel to display readings from hardware sensors, including CPU temperature, fan speeds and voltage readings.
http://sensors-applet.sourceforge.net/ sensors-applet

Hardware Temperature Monitor Windows

  • lm-sensors (LXPanel plugin) — Monitor temperature/voltages/fan speeds in LXDE through lm-sensors.
https://danamlund.dk/sensors_lxpanel_plugin/ sensors-lxpanel-pluginAUR
  • MATE Sensors Applet — Display readings from hardware sensors in your MATE panel.
https://github.com/mate-desktop/mate-sensors-applet mate-sensors-applet
  • Sensors (Xfce4 panel plugin) — Hardware sensors plugin for the Xfce panel.
https://goodies.xfce.org/projects/panel-plugins/xfce4-sensors-plugin xfce4-sensors-plugin
Hardware Temperature Monitor
  • Thermal Monitor (Plasma 5 applet) — KDE Plasma applet for monitoring CPU, GPU and other available temperature sensors.
https://gitlab.com/agurenko/plasma-applet-thermal-monitor plasma5-applets-thermal-monitor-gitAUR

sensord

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

Tips and tricks

Adjusting values

In some cases, the data displayed might be incorrect or users may wish to rename the output. Use cases include:

  • Incorrect temperature values due to a wrong offset (i.e. temps are reported 20 °C higher than actual).
  • Users wish to rename the output of some sensors.
  • The cores might be displayed in an incorrect order.

All of the above (and more) can be adjusted by overriding the package provides settings in /etc/sensors3.conf by creating /etc/sensors.d/foo wherein any number of tweaks will override the default values. It is recommended to rename 'foo' to the motherboard brand and model but this naming nomenclature is optional.

Open hardware monitor incorrect cpu core
Note: Do not edit /etc/sensors3.conf directly since package updates will overwrite any changes thus losing them.

Example 1. Adjusting temperature offsets

This is a real example on a Zotac ION-ITX-A-U motherboard. The coretemp values are off by 20 °C (too high) and are adjusted down to Intel specs.

Run sensors with the -u switch to see what options are available for each physical chip (raw mode):

Temperature

Create the following file overriding the default values:

Now invoking sensors shows the adjust values:

Example 2. Renaming labels

This is a real example on an Asus A7M266. The user wishes more verbose names for the temperature labels temp1 and temp2:

Create the following file to override the default values:

Now invoking sensors shows the adjust values:

Example 3. Renumbering cores for multi-CPU systems

This is a real example on an HP Z600 workstation with dual Xeons. The actual numbering of physical cores is incorrect: numbered 0, 1, 9, 10 which is repeated into the second CPU. Most users expect the core temperatures to report out in sequential order, i.e. 0,1,2,3,4,5,6,7.

Again, run sensors with the -u switch to see what options are available for each physical chip:

Create the following file overriding the default values:

Now invoking sensors shows the adjust values:

Automatic lm_sensors deployment

Users wishing to deploy lm_sensors on multiple machines can use the following to accept the defaults to all questions:

Troubleshooting

K10Temp module

Some K10 processors have issues with their temperature sensor. From the kernel documentation (linux-<version>/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 users 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, users of an AM3 processor on an AM2+ mainboard, can safely use the force=1 parameter.

On affected machines the module will report 'unreliable CPU thermal sensor; monitoring disabled'. To force monitoring anyway, you can run the following:

Confirm that the sensor is in fact valid and reliable. If it is, can edit /etc/modprobe.d/k10temp.conf and add:

This will allow the module to load at boot.

Asus B450M-A/A320M-K/A320M-K-BR motherboards

These motherboards use a IT8655E chip, which is not supported by the it87 kernel driver, as of Nov 2020 [1]. However, it is supported by the upstream version of the kernel driver [2]. The DKMS variant is contained in it87-dkms-gitAUR.

Asus B450/X399/X470 motherboards with AM4 Socket

Some recent Asus motherboards use a ITE IT8665E chip, accessing the temperature, fan and voltage sensors may require the asus-wmi-sensors module. Installasus-wmi-sensors-dkms-gitAUR and load the asus-wmi-sensorskernel module, the module uses the UEFI interface and may require a BIOS update on some boards [3].

Monitor

Alternatively, the it87 module reads the values from the chip directly, install it87-dkms-gitAUR and load the it87kernel module.

Asus H97/Z97/Z170/X570 motherboards

With some recent Asus motherboards, fan and voltage sensor access may require the nct6775kernel module to be loaded.

Additionally, add to the kernel boot parameters:

Cpu Gpu Temperature Monitor

Gigabyte B250/Z370/B450M motherboards

Some Gigabyte motherboards use the ITE IT8686E chip, which is not supported by the it87 kernel driver, as of May 2019 [4]. However, it is supported by the upstream version of the kernel driver [5]. The DKMS variant is contained in it87-dkms-gitAUR. As with #Asus H97/Z97/Z170/X570 motherboards, a kernel parameter is required before attempting to install the module:

Furthermore, supply the id of the chip when loading the module as follows:

Hardware Monitor Temperature Readings

Or you can load the module during boot process by creating the following two files:

Once the module is loaded you can use the sensors tool to probe the chip.Now you can also use fancontrol to control the speed step of your case fan.

Optionally installation of zenpower-dkmsAUR may allow greater fine tuning of the motherboard's cooling system. However, it does disable the default k10temp module.

Gigabyte GA-J1900N-D3V

This motherboard uses the ITE IT8620E chip (useful also to read voltages, mainboard temp, fan speed). As of October 2014, lm_sensors has no driver support for chip ITE IT8620E [6][7]. lm_sensors developers had a report that the chip is somewhat compatible with the IT8728F for the hardware monitoring part. However, as of August 2016, [8] lists the IT8620E as supported.

You can load the module at runtime with modprobe:

Or you can load the modules during boot process by creating the following two files:

Once the module is loaded you can use the sensors tool to probe the chip.

Now you can also use fancontrol to control the speedsteps of your case fan.

Laptop screen issues after running sensors-detect

This is caused by lm-sensors messing with the Vcom values of the screen while probing for sensors. It has been discussed and solved at the forums already: https://bbs.archlinux.org/viewtopic.php?id=193048. However, make sure to read through the thread carefully before running any of the suggested commands.

i2c bus errors on AMD Navi 2 GPUs

There is currently a bug in the way the kernel handles reading the i2c bus on AMD Navi 2 GPUs. The bus currently can only be used with EEPROMs and trying to use it with other devices will cause it to fail. This can cause crashes, black screens, and even cause the card to behave oddly like unable to switch power states. Its currently advised not to scan the i2c bus if you have a Navi 2 based card. You can read more here: https://gitlab.freedesktop.org/drm/amd/-/issues/1470

Retrieved from 'https://wiki.archlinux.org/index.php?title=Lm_sensors&oldid=669047'