Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASRock X470 taichi ultimate - temperatures #3

Open
mavelli opened this issue Aug 18, 2018 · 7 comments
Open

ASRock X470 taichi ultimate - temperatures #3

mavelli opened this issue Aug 18, 2018 · 7 comments

Comments

@mavelli
Copy link

mavelli commented Aug 18, 2018

Temperatures
   label temp1 "Motherboard"
   label temp2 "CPU MB"
   label temp3 "Auxillary"
   label temp4 "VRM"
   label temp5 "AUXTIN2"
   label temp6 "CPU (PECI)" #Almsot always at -25. Not certain what to do about this.
   label temp7 "CPU tCTL (offset included)" #A Thermal BIAS value generated by CPU, includes variation based on expected CPU load & Temperature (Not a true temperature)

i have also the x470 taichi ultimate (BIOS 1.50) running with a ryzen 2700x on my semi-open workstation and without a custom config file (on archlinux, linux 4.18.1.arch1 and lm_sensors 3.4.0) i get:

SYSTIN:                 +37.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = thermistor
CPUTIN:                 -62.5°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                 +5.0°C    sensor = thermistor
AUXTIN1:                +36.0°C    sensor = thermistor
AUXTIN2:                +22.0°C    sensor = thermistor
AUXTIN3:                -27.0°C    sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  

for the temp1 till temp10 values and as reference temps from k10temp this

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +31.8°C  (high = +70.0°C)
Tctl:         +41.8°C  

when idle and after 10 min under 90 % of time under load (16 threads of PrimeGrid) i see the following numbers plateau-ing:

SYSTIN:                 +38.0°C  (high =  +0.0°C, hyst =  +0.0°C)  sensor = thermistor
CPUTIN:                 -16.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
AUXTIN0:                 +5.0°C    sensor = thermistor
AUXTIN1:                +54.0°C    sensor = thermistor
AUXTIN2:                +21.0°C    sensor = thermistor
AUXTIN3:                -27.0°C    sensor = thermistor
PCH_CHIP_CPU_MAX_TEMP:   +0.0°C  
PCH_CHIP_TEMP:           +0.0°C  
PCH_CPU_TEMP:            +0.0°C  
PCH_MCH_TEMP:            +0.0°C  

and

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +79.2°C  (high = +70.0°C)
Tctl:         +89.2°C  

also noteworthy:

  • in the BIOS, the CPU temperature i see always around 55-60 °C which is strange on an idle system (my guess is that ASRock is not calculating it right in BIOS, since the air comming from the CPU fan is cold)
  • for me, the BIOS/MB is not regulating the fans at all... i run 1 CPU fan and two case-fans (detectable under fan2 and fan4 and fan5) which stay constant (lowest configurable in BIOS) speed despite temperatures and curves set in BIOS

since the k10temp values reflect more what i measure on the heatsink on the heatpipes at the bottom (also shifted around 10 °C but linear following), i trust these.

my "issue" with your config file (sorry for the long text):

  • temp2: you calculated a correction factor? the value changes depending on load, lags behind the Tdie and makes sense to be CPU MB temp
  • temp3: you get also such a low value?
  • temp5: not sure what this is, as ambient temp is higher than 21 for us in summer now - maybe ambient temp -5 °C?
  • temp6: i dont know it either - but seems i get -27 vs your -25
  • temp7: is constantly 0 for me - maybe my CPU fails to calculate the right value?
@rigred
Copy link
Owner

rigred commented Aug 18, 2018

I previously did include a correction value for the temp2 (CPU temp as reported by BIOS)

  • temp2 - this may be connected differently on your board, usually temp7 is CPU package temperature + offset. on X370, temp2 is a thermistor near the CPU on the mainboard.
  • temp3 is a low value, I'm still not sure what it's supposed to be and it almost never changes, it may just be an input on the SIO chip that's pulled low and used for something else.
  • temp5 is similarly an odd temperature, I haven't got documentation for what it's supposed to be and it rarely changes. HWInfo on windows reports the same value. I think it's just a sensor input line that's floating at the equivalent 8bit value of 21C.
  • temp7 is only reported if in the bios you have selected to drive fans based on tCtrl temperature.
    Temp7 is offset depending on the CPU model, some use 20C or 10C while the Threadripper CPU's use 27C. I prefer not to do any Temperature offset calculation via the config file as that would require me to read out the CPU model string, something that must be done in the lm_sensors code and cannot be done in the sensor config code.

For comparison these are values reported by my system with 1700X on kernel 4.17.14

image

@rigred
Copy link
Owner

rigred commented Aug 18, 2018

Please give me a dump of sensors -u for your mainboard plus if possible bios screenshots of all sensor values.

If you have windows you can also post a log file of HWInfo64 data.
The sensor config for the ASRock X470 I have put together with help of a friend as I don't have the X470 Ultimate Taichi myself. It may not be perfect yet.

@mavelli
Copy link
Author

mavelli commented Aug 18, 2018

sensors_u_asrock_x470_ultimate_2700x.txt

i have no native MS Windows, just in VM

@mavelli
Copy link
Author

mavelli commented Aug 18, 2018

Bios HW Monitor screenshot
one row didnt fit: 3.30 V at +3.344 V

@rigred
Copy link
Owner

rigred commented Aug 18, 2018

Thanks,
I'll see what I can do.

Also note that your UEFI is only reporting 3 temperatures.
lm_sensors is able to find even more than that, but in a lot of case many vendors don't use all of the I/O capability of the SIO chip.

@jds11111
Copy link

I get similar results, including temps below freezing, so I guess that this was never fixed.

@dv1
Copy link

dv1 commented Oct 12, 2022

Same here. Can values that aren't implemented by the mainboard manufacturer be turned off to avoid confusion?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants