X370 Taichi fan UEFI management
Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=6266
Printed Date: 27 Dec 2024 at 4:11pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: X370 Taichi fan UEFI management
Posted By: Nocturnal
Subject: X370 Taichi fan UEFI management
Date Posted: 06 Oct 2017 at 4:26am
|
" rel="nofollow - I still can not fully understand which sensor the fan speed is adjusted to. I have a bios version 3.00. I have heard that now the temperature is taken from the Tctl/Tdie sensor. Is this really so? Or
is the temperature taken from the sensor indicated in Hwinfo64 as
NUVOTON 6779d (and this number is always much lower than the temperature of
the Tctl/Tdie)? I need an exact answer in order to correctly configure the case fans using BIOS UEFI settings. |
Replies:
Posted By: nangu
Date Posted: 06 Oct 2017 at 11:29am
|
UEFI version 3.0 is CPU Tctl (AMD Ryzen on HWinfo64) The latest version, I think it's the 3.10 for the Taichi, added the posibility to select either Tctl or CPU socket temp to manage fans, which is the Nuvoton CPU reading. On Ryzen "X" CPUs, Tctl = Tdie + 20°. If you have a non "X" CPU, Tctl = Tdie. The "real" CPU temperature is Tdie. ------------- R7 1700 @3.90 1.25v - GSkill TridentZ 3200c16 Hynix MFR @2933 14-16-16-32 - Fatal1ty Gaming X370 K4 - Gigabyte GTX 1070 G1 - WD 256 Black M2 Nvme as Windows 10 boot drive - EVGA Gold 650W |
Posted By: Nocturnal
Date Posted: 13 Oct 2017 at 2:42am
|
Thank you for your answer |
Posted By: parsec
Date Posted: 13 Oct 2017 at 5:56am
" rel="nofollow -
The Nuvoton 6779D chip is the main temperature, voltage, power, etc monitoring chip your board. Any and all temperature readings are read by and made available to programs with this chip. For your X370 Taichi, with UEFI version 3.00, you cannot select which CPU temperature reading of the two you mentioned in the UEFI/BIOS. That feature was added in version 3.10. As I recall, your board's UEFI 3.00 changed to monitoring Tctl, where previously it was using the other CPU temperature that does not change much at all. That temperature seems to be similar to the old AMD socket temperature. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Nocturnal wrote:Posted By: Nocturnal
Date Posted: 13 Oct 2017 at 2:49pm
|
After installing version 3.10, I noticed that the fan speed began to change very quickly after the start and end of the load. It is very convenient that now the real temperature is being monitored (i choose Tctl sensor). |
Posted By: VUMeter
Date Posted: 30 Oct 2017 at 3:01am
|
The real annoyance is that there is no hysteresis option on the fan control. I guess it's not a big issue if you have a CPU fan that doesn't really make much noise and you don't hear it ramping up/down. Unfortunately, all fan speed controlling software cannot measure the Tdie or Tctrl temperature. That's not to say those sensors cannot be read by software (HWinfo can), it's just that the ones that allow fan control such as SpeedFan only monitor temps from the motherboard Nuvoton chip. This leads me to the conclusion that it is entirely possible to build a software fan controller that will respond to different sensors, it's just that it has not been done yet, at least not for this model. UEFI/BIOS v3.00 does use Tctrl (Tdie+20) as it's report for CPU temp in it's H/W info page. It also uses this sensor to control CPU fan speed (should you have the function enabled), and thus will make the fans spin up/down quite often, and with tiny load changes. It's arguably safer than using T-socket as a temp source, as there is some lag in getting that temp up, whilst the Tdie is rather toasty at a point earlier. However, it is quite nice that T-scoket takes a while longer to cool down, so the fan stays faster for longer, cooling more than just the CPU. ------------- X370 TaiChi | 1700X P3.10 stock clocks | (2x 16GB) 32GB FlareX 2400MHz. https://valid.x86.fr/ikadaa" rel="nofollow"> 
|