Dynamix - System Temp


Recommended Posts

On 8/16/2023 at 12:56 PM, PSYCHOPATHiO said:

@augot it was the corsair PSU plugin, once removed all back to normal. seems u have the same :)

Yep, but also the PSU itself - it was still happening even after I removed the plugin. Had to unplug the USB from the PSU so the sensors weren't picked up at all. Weird bug!

Edited by augot
Link to comment
2 hours ago, augot said:

Yep, but also the PSU itself - it was still happening even after I removed the plugin. Had to unplug the USB from the PSU so the sensors weren't picked up at all. Weird bug!

 Remove this line below from your config, or delete the config file completely and run sensors from the command line again. Hopefully this solves it.

 

Quote

chip "corsairpsu-hid-3-1"

ignore "fan1"

 

Link to comment
  • 3 weeks later...
On 8/20/2023 at 6:35 PM, PSYCHOPATHiO said:

 Remove this line below from your config, or delete the config file completely and run sensors from the command line again. Hopefully this solves it.

 

 

 

This is the weird thing - I found that unless I also unplugged the USB cable into my PSU, those lines kept getting re-added to the config file whenever I re-ran sensors (or changed things via the plugin GUI), even if I never selected them to be added. And that was even after removing the CorsairPSU plugin too. So weird!

Link to comment
2 hours ago, augot said:

 

This is the weird thing - I found that unless I also unplugged the USB cable into my PSU, those lines kept getting re-added to the config file whenever I re-ran sensors (or changed things via the plugin GUI), even if I never selected them to be added. And that was even after removing the CorsairPSU plugin too. So weird!

Well, I see you went through all the troubleshooting methods. Maybe unplug, remove plugin, delete the sensors config, reboot & test as a last resort.

Other than that, I got no clue. Maybe someone else has a similar issue with ha different solution.

Link to comment
  • 4 weeks later...

Hi, I have an HP Z840 workstation running unraid 6.12.4.   Using 2x E5-2680v4's (14c28t each).

Does the plugin support this platform?  Dashboard temps are blank and plugin settings don't show any sensors.  Detect shows coretemp as driver, but nothing under sensors.

I installed corefreq plugin and it shows the temps for all 56 cores

854078150_Screenshot2023-10-04222027.thumb.png.f52ee7897a6b751598507890ab0ca1c1.png

Edited by Cyklone
Link to comment
  • 4 weeks later...

Is there any way to add the drivers this plugin needs for your motherboard? It is something a lot of people like and really want to have working but of course, we know it cant support all motherboards. Is there no way to update it yourself to add your own drivers?

Edited by NotHere
Link to comment

 Hello Everybody, 

I´ve a little stuck with a B550 Taichi from Asrock. Maybe someone has already done it with this bord because I am stuck since i changed from a X470 to this bord. The Problem is that the Fans are not shown in the “System temp” Plugin and that is needed to add the fans to the fan control plugin. With the old bord it was working perfectly but sadly now I only can control the fans in BIOS.

 

What I’ve done until now.

  • reinstalled the System Temp Plugin
  • reinstall Nerd Pack 
  • tipped Sensor Detect in the console and added the sensors with Mudprobe in the go file
  • changed Bios fan settings to every possible setting
  • Installed the Nuvoton NCT 6687 Driver pack
  • Added "append initrd=/bzroot acpi_enforce_resources=lax" in the start sequenz of the flash drive
  • Ask in the German forum (
  • Googled a lot.
  • now asking in the system tempo forum

 

Would be nice if someone has some advice.

 

 

 

hanasselnas-diagnostics-20231102-1500.zip sensors detect.txt

Screenshot 2023-10-29 173048.png

Screenshot 2023-11-02 150658.png

Edited by Tidus1307
Link to comment
  • 1 month later...

hi, starting from today i have a problem. Untill yesterday i can see mobo and cpu temp and can pwm my fan

This morning nothing is working, or better, i can see coretemp CPU TEMP, but no pwm control and mobo temp

 

Untill yesterday my sensor was NCT6775 today it recognize it as lm75....

(here my log  of july

Jul 29 16:23:04 LordbyeNas autofan: autofan process ID 15733 started, To terminate it, type: autofan -q -c /sys/devices/platform/nct6775.2592/hwmon/hwmon1/pwm3 -f -q)

how can i try to solve? or where can i find any error?

thanks

 

sensors-detect version 3.6.0
# System:  JINGSHA AD12-B
# Kernel: 6.1.64-Unraid x86_64
# Processor: Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz (6/63/2)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0xfdfd
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0xfdfd

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      Success!
    (confidence 4, driver `to-be-written')
Probing for `IPMI BMC SMIC' at 0xca8...                     Success!
    (confidence 4, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-i801' for device 0000:00:1f.3: Wellsburg (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 0580 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x4f
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  Success!
    (confidence 3, driver `lm75')
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP422'...                   No
Probing for `Texas Instruments TMP435'...                   No
Probing for `Texas Instruments TMP441'...                   No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No

Next adapter: NVIDIA i2c adapter 3 at 3:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 4 at 3:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 6 at 3:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 


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)

Driver `to-be-written':
  * ISA bus, address 0xca0
    Chip `IPMI BMC KCS' (confidence: 4)
  * ISA bus, address 0xca8
    Chip `IPMI BMC SMIC' (confidence: 4)

Driver `lm75':
  * Bus `SMBus I801 adapter at 0580'
    Busdriver `i2c_i801', I2C address 0x4f
    Chip `Dallas Semiconductor DS75' (confidence: 3)

Note: there is no driver for IPMI BMC KCS yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): n
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
modprobe lm75
/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

 

 

image.png.9ea4ae4a1469bdeb1a0e946e929ebc39.png

 

image.png.7c36cc43aeb4f31d2ebfa413c824b1b5.png

 

 

image.png.98854269951389ed690ab0581b9b647e.png
 

Edited by Lordbye
Link to comment
On 12/14/2023 at 11:42 AM, Lordbye said:

hi, starting from today i have a problem. Untill yesterday i can see mobo and cpu temp and can pwm my fan

This morning nothing is working, or better, i can see coretemp CPU TEMP, but no pwm control and mobo temp

 

Untill yesterday my sensor was NCT6775 today it recognize it as lm75....

(here my log  of july

Jul 29 16:23:04 LordbyeNas autofan: autofan process ID 15733 started, To terminate it, type: autofan -q -c /sys/devices/platform/nct6775.2592/hwmon/hwmon1/pwm3 -f -q)

how can i try to solve? or where can i find any error?

thanks

 

sensors-detect version 3.6.0
# System:  JINGSHA AD12-B
# Kernel: 6.1.64-Unraid x86_64
# Processor: Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz (6/63/2)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): 
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): 
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0xfdfd
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0xfdfd

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): 
Probing for `IPMI BMC KCS' at 0xca0...                      Success!
    (confidence 4, driver `to-be-written')
Probing for `IPMI BMC SMIC' at 0xca8...                     Success!
    (confidence 4, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): 
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-i801' for device 0000:00:1f.3: Wellsburg (PCH)
Module i2c-dev loaded successfully.

Next adapter: SMBus I801 adapter at 0580 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x4f
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  Success!
    (confidence 3, driver `lm75')
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP422'...                   No
Probing for `Texas Instruments TMP435'...                   No
Probing for `Texas Instruments TMP441'...                   No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No

Next adapter: NVIDIA i2c adapter 3 at 3:00.0 (i2c-1)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 4 at 3:00.0 (i2c-2)
Do you want to scan it? (yes/NO/selectively): 

Next adapter: NVIDIA i2c adapter 6 at 3:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): 


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)

Driver `to-be-written':
  * ISA bus, address 0xca0
    Chip `IPMI BMC KCS' (confidence: 4)
  * ISA bus, address 0xca8
    Chip `IPMI BMC SMIC' (confidence: 4)

Driver `lm75':
  * Bus `SMBus I801 adapter at 0580'
    Busdriver `i2c_i801', I2C address 0x4f
    Chip `Dallas Semiconductor DS75' (confidence: 3)

Note: there is no driver for IPMI BMC KCS yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): n
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
modprobe lm75
/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

 

 

image.png.9ea4ae4a1469bdeb1a0e946e929ebc39.png

 

image.png.7c36cc43aeb4f31d2ebfa413c824b1b5.png

 

 

image.png.98854269951389ed690ab0581b9b647e.png
 

i have solved with a downgrade to 6.12.5 and new update to 6.12.6

now 

image.thumb.png.f0b57a43e4593d0e8e0e5d89f4016130.png

 

Link to comment
  • 3 weeks later...

Anyone here have an Asrock Z690 series motherboard, and the sensors show a very high Systin temp?

Here's my truncated list of sensors (took out coretemp and nvme sensors).

Where it says MB Temp, that's my "SYSTIN" sensor. From what I've been able to Google, SYSTIN is probably the mb temp, but its reading so high. That just seems unusual to me.
 

nct6798-isa-02a0
Adapter: ISA adapter
in0:          784.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:            1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:            3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:            3.36 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:            1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:          128.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:          120.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:            3.44 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:            3.18 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:          528.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:          72.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:          56.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:           1.14 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:         144.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:           1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
Array Fan:     776 RPM  (min =    0 RPM)
Array Fan:    1146 RPM  (min =    0 RPM)
Array Fan:    1002 RPM  (min =    0 RPM)
MB Temp:      +122.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
CPUTIN:        +37.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:      +112.0°C    sensor = thermistor
AUXTIN1:      +117.0°C    sensor = thermistor
AUXTIN2:      +117.0°C    sensor = thermistor
AUXTIN3:        -2.0°C    sensor = thermistor
PECI Agent 0:  +25.5°C  (high = +80.0°C, hyst = +75.0°C)

 

Link to comment
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.