Hardware temperatures help explain throttling, loud fans, and unexpected shutdowns. In Linux, sensors displays temperatures exposed by hardware-monitoring drivers; labels and limits depend on the device.

Example output:

The sensors command comes from lm-sensors and can report processor and board temperatures alongside fan speeds and voltages. Linux also exposes firmware- or driver-reported thermal zones, which may cover a processor package or another region of the system rather than an individual core.

Sensor coverage depends on the machine, firmware, kernel driver, and runtime environment. Containers and many virtual machines often report no sensors because host hardware is not exposed, while disk temperature normally comes from drive S.M.A.R.T. data rather than lm-sensors.

Step-by-step video guide:

Steps to check hardware temperatures in Linux:

  1. Install lm-sensors on Debian or Ubuntu if sensors is missing.
    $ sudo apt install lm-sensors

    On Fedora, the package is named lm_sensors.

  2. Display the current sensor report. Example output:
    $ sensors
    coretemp-isa-0000
    Adapter: ISA adapter
    Package id 0:  +48.0°C  (high = +100.0°C, crit = +100.0°C)
    Core 0:        +45.0°C  (high = +100.0°C, crit = +100.0°C)
    Core 1:        +46.0°C  (high = +100.0°C, crit = +100.0°C)
    
    acpitz-acpi-0
    Adapter: ACPI interface
    temp1:        +42.0°C  (crit = +105.0°C)

    For Intel's coretemp driver, Package id 0 is the temperature of processor package 0, not a count of cores, and Core 0 and Core 1 are individual cores within that package. acpitz identifies an ACPI thermal zone, and a generic label such as temp1 does not by itself identify a CPU sensor. Other drivers and boards use different labels.

    No sensors found! means the hardware is not exposed to sensors, not that temperatures are safe. It is common in containers and many virtual machines, and driver support may also be missing on physical hardware. The sensors-detect utility that the message suggests probes hardware buses and can hang some machines, so save your work before running it.

  3. Compare each temperature with the limits reported on the same line.

    high is the reported upper temperature limit, and crit is the critical upper limit. A reading above high deserves attention even while it remains below crit, and a reading at or near crit leaves little thermal margin. Limits may be absent or equal, and their meaning depends on the driver and hardware.

  4. Watch the report refresh while the system is busy to see how far the temperatures climb under load.
    $ watch sensors

    This step is optional. watch reruns sensors every two seconds until Ctrl+C stops it.

  5. Read the name of each kernel thermal zone. Example output:
    $ cat /sys/class/thermal/thermal_zone*/type
    x86_pkg_temp
    acpitz

    Names such as x86_pkg_temp, acpitz, or vendor-specific labels identify the driver-reported zone. A No such file or directory error means this system exposes no thermal zones.

  6. Read the temperature of each thermal zone. Example output:
    $ cat /sys/class/thermal/thermal_zone*/temp
    48000
    42000

    Temperatures print in the same order as the names and are in millidegrees Celsius, so 48000 represents 48°C.

Share this guide