Version 6.12.13 2024-08-22

Had to swap some hardware recently. Went to a Gigabyte Z790 Aorus Elite AX - it was cheap and available next day when I needed it.
The 1 annoying thing about it is it doesn't seem to have a motherboard temperature sensor that the Dynamix temp plugin can read/report. I miss seeing the motherboard temp in the dashboard. Or at the very least if it's not available, I'd like to disable it for the motherboard rather than seeing "Temperature: --- °C" displayed. Is this a gigabyte thing? I can't imagine a modern mobo maker not including sensor information and/or making it available to 3rd party app writers for non-Windows OS users.

Edited November 21, 20241 yr by wildwolf

*Userscript plugin at first array start may be better for modprobe calls then go file to not brick at boot if problems...

BET - amd ryzne known issue its no cpu its tcdie / tckl for your cpu temp...

 

The issue of missing motherboard temperature readings or inaccurate temperature readings in Unraid with the Dynamix System Temperature plugin is fairly common, especially with newer motherboards like the Gigabyte Z790 Aorus Elite AX or AMD systems. Here's how to address it:

 

Why the Issue Occurs

Chipset Compatibility:

Newer motherboards may use monitoring chips (e.g., Nuvoton or ITE) that are not yet fully supported by the Linux kernel used by your Unraid version.

Driver/Module Limitations:

The Dynamix System Temperature plugin relies on Linux drivers (lm-sensors) to read sensor data. If the required kernel module for your motherboard’s sensor chip isn’t loaded or doesn’t exist, the plugin can’t fetch the temperature.

AMD Tctl/Tdie Temperature Issue:

On AMD systems, temperatures like "Tctl" and "Tdie" can sometimes be incorrectly reported or misinterpreted.

 

Steps to Fix or Mitigate...

 

Update to the Latest Unraid Version

Ensure you’re running the latest version of Unraid. Kernel updates in newer versions may include support for your motherboard's temperature sensors.

Check for plugin updates for Dynamix System Temperature.

 

Install Additional Kernel Modules

Sometimes the required modules for your sensors are not auto-loaded. Follow these steps:

Run sensors-detect to identify available sensors and recommend necessary modules.

Based on the output, manually load the suggested module(s), such as:

modprobe nct6775

Common modules include:

nct6775 for Nuvoton chips (used in many Gigabyte boards).

it87 for ITE chips.

Add the module to your go file to ensure it loads on boot

echo "modprobe nct6775" >> /boot/config/go

Check BIOS Settings

Some motherboards have sensor-related features in the BIOS that need to be enabled:

Ensure any "Hardware Monitoring" or "Smart Fan" features are enabled.

If you’re using fan control software, it may conflict with temperature monitoring; try disabling it temporarily.

 Customize the Dynamix Plugin

If the motherboard sensor isn’t available, you can hide the “--- °C” display by customizing the plugin:

Navigate to Settings > System Temperature in the Unraid web UI.

Under "Available Sensors," uncheck or deselect the motherboard sensor.

Save changes to avoid displaying non-existent temperature values.

 Alternative Sensor Readings

If the motherboard temperature sensor is unavailable, consider monitoring CPU package temperature (Tctl/Tdie) or other available sensors. These can give a general sense of system temperature.

 Update Sensor Drivers (Advanced)

If the required sensor driver is missing or outdated:

Search for an updated version of the nct6775 or it87 driver in the Unraid forums or GitHub.

If you find a patched driver, you can build it as a kernel module and load it. This requires a Linux environment with kernel headers matching your Unraid version.

 Use External Monitoring Solutions

If no sensor solution is available, consider using an external hardware monitor like a USB-connected sensor or IPMI (if your hardware supports it).

 

 

AMD-Specific Temperature Fixes

If you're on an AMD system and having Tctl/Tdie issues:

BIOS Updates:

Update the motherboard BIOS. Vendors often release updates to improve temperature reporting.

Correct Sensor Calibration:

Adjust the offset for Tctl (common on Ryzen CPUs):

Use sensors to identify the sensor reporting the incorrect temperature.

Modify the calibration in the Dynamix plugin or directly in the configuration file for lm-sensors.

Kernel Modules for AMD CPUs:

Ensure the k10temp module is loaded for AMD CPU temperature monitoring

modprobe k10temp

Add to the go file if needed:

echo "modprobe k10temp" >> /boot/config/go

Future Recommendations

Motherboard Selection: Some motherboard manufacturers (e.g., ASUS) tend to provide better Linux support for sensors compared to Gigabyte.

Forum Support: Check the Unraid forums for users with the same motherboard. They may have posted specific fixes or kernel patches.

 

amd ryzen chaged the cpu core temp in loger stuff the :

k10temp-pci-00c3 Adapter: PCI adapter Tctl: +56.4°C

is you cpu temp.

https://www.hwinfo.com/forum/threads/cpu-temp-sensors-explanation.5597/
-CPU (onboard sensor): This is either a temperature measured by a dedicated sensor on mainboard located inside the CPU socket (the external CPU temperature) or temperature obtained from internal CPU thermal sensor (i.e. DTS = Digital Thermal Sensor).

-Core Max: The maximum temperature among all cores in the CPU.

-CPU (Tctl): This is the T_control temperature available on AMD CPUs only. On several generations before Zen (Ryzen), this is not a reliable representation of the temperature. On AMD Zen series this is the temperature used to control cooling and is a fixed offset from the real CPU temperature. Offset is used mostly on X-series and some Threadripper CPUs; in such case two values are shown: Tctl and Tdie. If no offset is used, then only a single value is shown as Tctl/Tdie, which equals the real temperature.

-CPU (Tdie): This value is shown in case the CPU uses an offset from Tctl and represents the real temperature (Tdie = Tctl - Tctl_offset).

-CPU Package: Shown on Intel CPUs represents a 256-millisecond average value (calculated by CPU) of the hottest temperature sensor within the CPU package.

-CPU Package (TSI): Available on pre-Zen AMD CPUs is the CPU temperature obtained via TSI interface.

-Core #n (n=any number): Actual temperature of a particular CPU core.

-CPU IA Cores: Maximum temperature among all computing (x86) cores in CPU (so part of CPU except Uncore and Graphics logic).

-CPU GT Cores: Temperature of the integrated graphics part of CPU (if present).

There a whole thing due to how amd chagned ryzen temp sensors...

Thanks all, latest/greatest release, BIOS updated to latest. It's an i5-12600K CPU on an Intel z790 chipset motherboard.
sensor-detect only shows modprobe coretemp

Guess I'll just need to be patient. Have checked BIOS a couple times for any enable/disable, will check again at next reboot.

 

 

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

 

# sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +27.8°C  (crit = +105.0°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +34.9°C  (low  = -273.1°C, high = +84.8°C)
                       (crit = +84.8°C)
Sensor 1:     +34.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +37.9°C  (low  = -273.1°C, high = +65261.8°C)

coretemp-isa-0000
Adapter: ISA adapter
CPU Temp:     +36.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:       +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 4:       +35.0°C  (high = +80.0°C, crit = +100.0°C)
Core 8:       +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 12:      +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 16:      +35.0°C  (high = +80.0°C, crit = +100.0°C)
Core 20:      +30.0°C  (high = +80.0°C, crit = +100.0°C)
Core 28:      +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 29:      +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 30:      +34.0°C  (high = +80.0°C, crit = +100.0°C)
Core 31:      +33.0°C  (high = +80.0°C, crit = +100.0°C)

i don't remember which one for Intel 90% of temp i see and come across are amd and its ryzen confusion....

i vague remember an old thread with a similar issue where an extra package was need ?lm_sensor i think...

https://docs.unraid.net/legacy/FAQ/setting-up-cpu-and-board-temperature-sensing/

you may need to 3rd party install the Slackware package to use it in unraid.

revieing the processor and chipset across other site will get back to you if i find something.

Yeah, lm_sensor:
https://slackware.pkgs.org/15.0/slackware-x86_64/lm_sensors-3.6.0-x86_64-3.txz.html

 

cd /boot/extra
wget https://slackware.uk/slackware/slackware64-15.0/slackware64/ap/lm_sensors-3.6.0-x86_64-3.txz

reboot to install 3rd party package

docks run/make sensor probe conf:

modprobe lm_sensor

*Not sure is peral install is needed anymore...
Review doc: https://docs.unraid.net/legacy/FAQ/setting-up-cpu-and-board-temperature-sensing/
 

To enable CPU and motherboard temperature monitoring on your Unraid system, follow these steps:

 

Install the lm_sensors Package:

Unraid doesn't include lm_sensors by default. You'll need to install it manually. Download the appropriate Slackware package for lm_sensors and place it in the /boot/extra directory on your Unraid USB flash drive. On the next system boot, Unraid will automatically install packages from this directory.

 

Install Perl:

The sensors-detect script, which identifies available sensors, requires Perl. You can install Perl using the NerdPack plugin:

Install the NerdPack plugin from the Unraid Community Applications.

Within NerdPack, enable and install Perl.

 

Detect Available Sensors:

After installing lm_sensors and Perl, run the detection script:

Open a terminal session on your Unraid server.

Execute sensors-detect and follow the prompts to identify available sensors.

The script will suggest kernel modules to load for your hardware.

 

Load the Suggested Modules:

Based on the output from sensors-detect, load the necessary modules:

Use the modprobe command to load each module.

To ensure these modules load on every boot, add them to the /boot/config/go script.

 

Install the Dynamix System Temperature Plugin:

This plugin provides a user-friendly interface for monitoring temperatures:

Install it via the Unraid Community Applications.

After installation, navigate to the plugin's settings page.

Click the "Detect" button to automatically find available sensors.

Assign the appropriate sensors for CPU and motherboard readings.

 

Verify Sensor Readings:

After configuration, verify that temperature readings appear correctly on your Unraid dashboard.

For detailed instructions and additional information, refer to the Unraid documentation on setting up CPU and board temper

By following these steps, you should be able to monitor your system's temperatures effectively.

Edited November 23, 20241 yr by bmartino1
typo / extra data

Perl/nerd pack already installed. Followed command presented to download lm_sensors, /boot/extra didn't exist. Created it, placed file from wget command there. Ran sensors-detect, no change on output.

 

Saw I could potentially try: installpkg/boot/packages/lm_sensors-3.6_0_x86_64_3.txz after placing into /boot/packages directory. Tried that, ran sensors-detect again. Output still the same.

 

Tried to modprobe the lm_sensor or lm_sensors

 

modprobe lm_sensor
modprobe: FATAL: Module lm_sensor not found in directory /lib/modules/6.1.106-Unraid

modprobe lm_sensors
modprobe: FATAL: Module lm_sensors not found in directory /lib/modules/6.1.106-Unraid

 

 

lm_sensor is missing a lib file to run on latter unraid you may need another 3rd pary app installed.

 

it doesn't look like the lm_sensor package is gettign installed.

 

wget https://slackware.uk/slackware/slackware64-current/slackware64/l/lm_sensors-3.6.0-x86_64-3.txz

mkdir -p /boot/extra
mv lm_sensors-3.6.0-x86_64-3.txz /boot/extra/

 

Install manually slackware package manger may or may not be installed:

installpkg /boot/extra/lm_sensors-3.6.0-x86_64-3.txz
 

lm_sensors depends on kernel modules for sensor detection. If modprobe fails, it typically means:

The necessary modules aren't part of your Unraid kernel.

You need to explicitly load them after installing lm_sensors.

Run sensors-detect:

This command scans your system for compatible sensors and suggests which modules to load.

 

run sensors-detect first

 

Baased on sensor detect:

 

modprobe coretemp  # For Intel CPUs
modprobe k10temp   # For AMD CPUs
 

Verify Sensor Detection

Run sensors:

 

Persist Module Loading:

Add the modules to your go file for persistence across reboots:

echo "modprobe coretemp" >> /boot/config/go
echo "modprobe k10temp" >> /boot/config/go

*May be better as a uiser script first array start...

whats the outpuit of:

ls /lib/modules/$(uname -r)/kernel/drivers/hwmon/
 

Edited November 23, 20241 yr by bmartino1

# ls /lib/modules/$(uname -r)/kernel/drivers/hwmon
abituguru.ko.xz            corsair-psu.ko.xz     lineage-pem.ko.xz   max31790.ko.xz         smsc47b397.ko.xz
abituguru3.ko.xz           dell-smm-hwmon.ko.xz  lm63.ko.xz          max6620.ko.xz          smsc47m1.ko.xz
acpi_power_meter.ko.xz     dme1737.ko.xz         lm73.ko.xz          max6621.ko.xz          smsc47m192.ko.xz
ad7414.ko.xz               drivetemp.ko.xz       lm75.ko.xz          max6639.ko.xz          stts751.ko.xz
ad7418.ko.xz               ds1621.ko.xz          lm77.ko.xz          max6650.ko.xz          tc654.ko.xz
adc128d818.ko.xz           ds620.ko.xz           lm78.ko.xz          max6697.ko.xz          tc74.ko.xz
adm1025.ko.xz              emc1403.ko.xz         lm80.ko.xz          mcp3021.ko.xz          thmc50.ko.xz
adm1026.ko.xz              emc2103.ko.xz         lm83.ko.xz          mr75203.ko.xz          tmp102.ko.xz
adm1029.ko.xz              emc6w201.ko.xz        lm85.ko.xz          nct6683.ko.xz          tmp103.ko.xz
adm1031.ko.xz              f71805f.ko.xz         lm87.ko.xz          nct6775-core.ko.xz     tmp108.ko.xz
adm1177.ko.xz              f71882fg.ko.xz        lm90.ko.xz          nct6775.ko.xz          tmp401.ko.xz
adm9240.ko.xz              f75375s.ko.xz         lm92.ko.xz          nct7802.ko.xz          tmp421.ko.xz
ads7828.ko.xz              fam15h_power.ko.xz    lm93.ko.xz          nct7904.ko.xz          tmp464.ko.xz
adt7410.ko.xz              fschmd.ko.xz          lm95234.ko.xz       npcm750-pwm-fan.ko.xz  tmp513.ko.xz
adt7411.ko.xz              ftsteutates.ko.xz     lm95241.ko.xz       nzxt-kraken2.ko.xz     tps23861.ko.xz
adt7462.ko.xz              g760a.ko.xz           lm95245.ko.xz       nzxt-smart2.ko.xz      via-cputemp.ko.xz
adt7470.ko.xz              g762.ko.xz            ltc2945.ko.xz       pc87360.ko.xz          via686a.ko.xz
adt7475.ko.xz              gl518sm.ko.xz         ltc2947-core.ko.xz  pc87427.ko.xz          vt1211.ko.xz
adt7x10.ko.xz              gl520sm.ko.xz         ltc2947-i2c.ko.xz   pcf8591.ko.xz          vt8231.ko.xz
aht10.ko.xz                hih6130.ko.xz         ltc2990.ko.xz       pmbus/                 w83627ehf.ko.xz
amc6821.ko.xz              hwmon-vid.ko.xz       ltc2992.ko.xz       powr1220.ko.xz         w83627hf.ko.xz
applesmc.ko.xz             i5500_temp.ko.xz      ltc4151.ko.xz       sbrmi.ko.xz            w83773g.ko.xz
aquacomputer_d5next.ko.xz  i5k_amb.ko.xz         ltc4215.ko.xz       sbtsi_temp.ko.xz       w83781d.ko.xz
as370-hwmon.ko.xz          ibmaem.ko.xz          ltc4222.ko.xz       sch5627.ko.xz          w83791d.ko.xz
asb100.ko.xz               ibmpex.ko.xz          ltc4245.ko.xz       sch5636.ko.xz          w83792d.ko.xz
asc7621.ko.xz              ina209.ko.xz          ltc4260.ko.xz       sch56xx-common.ko.xz   w83793.ko.xz
asus-ec-sensors.ko.xz      ina238.ko.xz          ltc4261.ko.xz       sht15.ko.xz            w83795.ko.xz
asus_atk0110.ko.xz         ina2xx.ko.xz          max127.ko.xz        sht21.ko.xz            w83l785ts.ko.xz
asus_wmi_sensors.ko.xz     ina3221.ko.xz         max16065.ko.xz      sht3x.ko.xz            w83l786ng.ko.xz
atxp1.ko.xz                it87.ko.xz            max1619.ko.xz       sht4x.ko.xz            xgene-hwmon.ko.xz
axi-fan-control.ko.xz      jc42.ko.xz            max1668.ko.xz       shtc1.ko.xz
coretemp.ko.xz             k10temp.ko.xz         max197.ko.xz        sis5595.ko.xz
corsair-cpro.ko.xz         k8temp.ko.xz          max31730.ko.xz      smm665.ko.xz

sensors-detect runs. It only suggests the modprobe coretemp. 

 

Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): NO
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# Chip drivers
modprobe coretemp
/usr/bin/sensors -s
#----cut here----

You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.

Unloading i2c-dev... OK

I've already put that in /boot/config/go:

# cat /boot/config/go 
#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
modprobe coretemp

 

A couple days ago, I placed it in /boot/packages, and tried:
installpkg /boot/packages/lm_sensors-3.6.0-x86_64-3.txz

 

 

 

Proper unraid application in binary format as Slackware .txz file located in /boot/extra are installed at unraid first boot.

did you reboot the machine after placing the file in the extra folder?

looks like lm sensor / coretemp is there running sensor should show you coretemp.

you may need to run modprobe coretemp as a user script at first array start and not int eh go file i dot' like to mess with the go file and found something's don't work nor run due to missing thing when ran due to how early it is in the boot process.

 

so let overview and confrim and double check:

It seems like you've made considerable progress in setting up temperature monitoring for your Gigabyte Z790 Aorus Elite AX motherboard on Unraid. However, the issue of not seeing the expected temperature readings may stem from a combination of configuration mismatches, hardware support limitations, or driver/module loading issues. Here's a step-by-step troubleshooting approach

 

Confirm the coretemp module is correctly loaded:

lsmod | grep coretemp

If it's not listed, try:

modprobe coretemp

 

Double check syslog... check dmesg for any errors related to the coretemp module

dmesg | grep coretemp

?any errors?

 

Double-Check Sensors Configuration

run again... sensors-detect

follow or give its output...
We want to:

Ensure it suggests coretemp and load it manually for testing.

You can also confirm by generating the /etc/sysconfig/lm_sensors file.

Test lm_sensors Setup

After ensuring the coretemp module is loaded, test the output of

sensors
do you see coretemp?

journalctl -xe | grep sensors

otherwise, please post diag file.

Again, coretemp is working/has always worked, as I'm assuming that's what shows me the CPU temp. What I don't get from it is a motherboard reading. 

 

# lsmod | grep coretemp
coretemp               16384  0
# dmesg | grep coretemp

 

# journalctl -xe | grep sensors
bash: journalctl: command not found

 

Motherboard is a Gigabyte Z790 AORUS ELITE AX. Manual shows temperature sensors near CPU, z790 chipset, by the battery, F_AUDIO connection, and under the PCIEX16 slot. My assumption is that coretemp doesn't have access/ability to read those 5 sensors, and it's annoying. 

 

 

 

the motheboard may have a acpi or bios section for it but no probe or silicone lottery the probe was dead at post.

that something you would need to ask gigabyte support on for what linux mod or what probes exist on board.

Happy to report that after I upgraded to unRAID 7 on 2 servers with a Gigabyte motherboard, I can now choose one of several temperature sensors on the motherboard and now have it showing on the dashboard. 

/me doing happy dance.

Edited January 12, 20251 yr by wildwolf