You are not logged in.

#1 2024-02-03 08:06:58

folkdanskung
Member
Registered: 2015-07-16
Posts: 13

[SOLVED] Fan control issues coretemp/NCT6793D

Good day, I've been scouring the net to solve this but to no avail. I have a ASUS PRIME Z370-P motherboard with a Nuvoton chipset which supports pwm. Can control fans just fine in Windows with Speedfan. BIOS also has a fan control application (which is lousy and barely works).

In Arch however I cannot get this to work. I've run sensors-detect successfully, saved lm_sensors config and upon booting correct modules are loaded. See output below.

Output of sensors-detect

# sensors-detect version 3.6.0+git
# Board: ASUSTeK COMPUTER INC. PRIME Z370-P
# Kernel: 6.7.2-arch1-1 x86_64
# Processor: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (6/158/10)

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): y
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
AMD Family 19h 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6793D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

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): y
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

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): y
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): y
Using driver `i2c-i801' for device 0000:00:1f.4: Kaby Lake (PCH)

Next adapter: SMBus I801 adapter at f000 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Handled by driver `ee1004' (already loaded), chip type `ee1004'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x51
Handled by driver `ee1004' (already loaded), chip type `ee1004'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `ee1004' (already loaded), chip type `ee1004'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x53
Handled by driver `ee1004' (already loaded), chip type `ee1004'
    (note: this is probably NOT a sensor chip!)

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

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

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

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

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


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 `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6793D Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): y

Output of lsmod | grep nct

nct6775                40960  0
nct6775_core           81920  1 nct6775
hwmon_vid              12288  1 nct6775

Output of lsmod | grep coretemp

coretemp               16384  0

Output of sensors

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  
temp2:        +29.8°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +32.0°C  (high = +82.0°C, crit = +100.0°C)
Core 0:        +27.0°C  (high = +82.0°C, crit = +100.0°C)
Core 1:        +29.0°C  (high = +82.0°C, crit = +100.0°C)
Core 2:        +28.0°C  (high = +82.0°C, crit = +100.0°C)
Core 3:        +27.0°C  (high = +82.0°C, crit = +100.0°C)
Core 4:        +32.0°C  (high = +82.0°C, crit = +100.0°C)
Core 5:        +28.0°C  (high = +82.0°C, crit = +100.0°C)

nvme-pci-0500
Adapter: PCI adapter
Composite:    +29.9°C  (low  = -20.1°C, high = +74.8°C)
                       (crit = +79.8°C)

Upon performing pwmconfig I run into the classic error (cropped message)

/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed

From here I haven't progressed. Searched the net and found lots of people having the same error but no solution, same when searching this forum specifically.

So, I tried other paths. Found coolercontrol in AUR which seems like a good alternative. Successfully installed, enabled and started daemon, application starts but shows only a dark blue screen. Right-clicking allows the window to be refreshed, which it does, and continues to show a dark blue screen. But this is another story/post.

Do anyone have any clue on how to proceed with fancontrol here? Thanks in advance.

Best regards
Marc

Last edited by folkdanskung (2024-02-06 18:49:00)

Offline

#2 2024-02-03 15:56:20

merlock
Member
Registered: 2018-10-30
Posts: 236

Re: [SOLVED] Fan control issues coretemp/NCT6793D

I have a Z370-A. I had to add

acpi_enforce_resources=lax

to the kernel command-line to enable the 6793D. Then run

sudo sensors-detect

again.

You should get an output similar to this (without a configuration in /etc/sensors.d):

6793D output

folkdanskung wrote:

BIOS also has a fan control application (which is lousy and barely works).

Why do you say that?  I have my fans set thru BIOS...spin-up/spin-down on demand, without having to mess with the various fan-speed apps (which may or may not work).

Last edited by merlock (2024-02-07 02:25:15)


Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '

Offline

#3 2024-02-06 18:47:41

folkdanskung
Member
Registered: 2015-07-16
Posts: 13

Re: [SOLVED] Fan control issues coretemp/NCT6793D

merlock wrote:

I have a Z370-A. I had to add

acpi_enforce_resources=lax

to the kernel command-line to enable the 6793D. Then run

sudo sensors-detect

again.

You should get an output similar to this (without a configuration in /etc/sensors.d):

6973D output

It did indeed work, thank you!

merlock wrote:
folkdanskung wrote:

BIOS also has a fan control application (which is lousy and barely works).

Why do you say that?  I have my fans set thru BIOS...spin-up/spin-down on demand, without having to mess with the various fan-speed apps (which may or may not work).

I may have exaggerated slightly. It is however when compared to Speedfan in my opinion, not good. Only allows three set points per fan for speed curve and minimum threshold is quite high, so I can't get my pc as quiet as with Speedfan. Maybe your version works better. Though I have been using it in lack of anything else. Looking forward to set fancontrol up properly now.

Again, thank you!

Best regards
Marc

Offline

#4 2024-02-07 02:33:45

merlock
Member
Registered: 2018-10-30
Posts: 236

Re: [SOLVED] Fan control issues coretemp/NCT6793D

One thing to keep in mind...if you're going to use the chip to set curves up for each fan, you'll need to verify what each header on your board equates to what output of the chip (as an example, fan5 on my output is the AIO header on the mobo).


Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '

Offline

Board footer

Powered by FluxBB