All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, Ahmad Khalifa <ahmad@khalifa.ws>,
	Sebastian Arnhold <sebastian.arnhold@posteo.de>
Subject: Re: [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D
Date: Fri, 30 Dec 2022 21:34:23 +0100	[thread overview]
Message-ID: <c8d68feb-d44f-02c6-0a08-d199cef00b46@gmail.com> (raw)
In-Reply-To: <20221230175021.GA1136102@roeck-us.net>

Hi Guenter,

On 12/30/22 18:50, Guenter Roeck wrote:
 > On Fri, Dec 30, 2022 at 06:32:23PM +0100, Christian Lamparter wrote:
 >> On 12/28/22 14:57, Guenter Roeck wrote:
 >>> NCT6799D is mostly compatible to NCT6798D, with minor variations.
 >>>
 >>> Note that NCT6798D and NCT6799D have a new means to select temperature
 >>> sources, and to report temperatures from those sources. This is not
 >>> currently implemented, meaning that most likely not all temperatures
 >>> are reported.
 >>>
 >>> Initial support. Compile tested only.
 >>
 >> FYI: This ID is compatible with the NCT6796D-S on the ASRock X670E PG Lighting Mainboard.
 >> (Previous discussion: "[PATCH v1] hwmon: (nct6775) Add chip ID for NCT6796D-S"
 >> <https://www.spinics.net/lists/linux-hwmon/msg17785.html>)
 >>
 >> With this patch applied, the nct6775 module loads and produces the following output when loaded.
 >>
 >> | [28152.009197] nct6775: Found NCT6799D or compatible chip at 0x2e:0x290
 >>
 >> and lm-sensors also enumerates the sensors and finally all six fans.
 >> So this is definitively an improvement over my patch.
 >>
 >
 > Thanks a lot for testing. I'd suspect that NCT6796D-S was mislabeled
 > in the user manual. That would not be the first time.
The chips sits behind the GPU now. But I made a blurry photo before
I added the GPU though :-). The IC's label shows "Nuvoton NCT6796D-S"
<https://gist.github.com/chunkeey/89aeb85d6f71e7a2da9344615303c203>
(the chip is soldered at an 45° angle, hence I rotated the picture)

I got that MB because of the phoronix review:
<https://www.phoronix.com/review/asrock-x670e-pg>
(NB: The review also noted the missing sensor support...
But not for much longer ;-) )

Michael Larabel also made (better) pictures:
<https://www.phoronix.com/image-viewer.php?id=asrock-x670e-pg&image=asrock_x670pglightning_3_lrg>

(While not the same motherboard, this Japanese review site has a
really sharp picture from the ASRock X670E Taichi NCT6796D-S SuperIO
<https://www.gdm.or.jp/x670etaichi_57_1024x768>)

That all being said: Other users in the github thread for the
lm-sensors project:
<https://github.com/lm-sensors/lm-sensors/issues/416#issuecomment-1276620580>
clearly stated that their ASUS X670E TUF came with a "NCT6799D-R".

Obviously, I'm totally fine with what the module calls it:
"NCT6799D or compatible".

 >> |# sensors
 >> |
 >> |nct6799-isa-0290
 >> |Adapter: ISA adapter
 >> |in0:                   720.00 mV (min =  +0.00 V, max =  +1.74 V)
 >> |in1:                     1.82 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in2:                     3.39 V  (min =  +2.98 V, max =  +3.63 V)
 >> |in3:                     3.28 V  (min =  +2.98 V, max =  +3.63 V)
 >> |in4:                     1.65 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in5:                     1.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in6:                     1.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in7:                     3.39 V  (min =  +2.98 V, max =  +3.63 V)
 >> |in8:                     3.23 V  (min =  +2.70 V, max =  +3.63 V)
 >> |in9:                   904.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in10:                  600.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in11:                  608.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in12:                    1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in13:                  896.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |in14:                    1.26 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
 >> |fan1:                   891 RPM  (min =    0 RPM)
 >> |fan2:                     0 RPM  (min =    0 RPM)
 >> |fan3:                  1345 RPM  (min =    0 RPM)
 >> |fan4:                   774 RPM  (min =    0 RPM)
 >> |fan5:                     0 RPM  (min =    0 RPM)
 >> |fan7:                     0 RPM  (min =    0 RPM)
 >
 > Interesting. Do you have three fans connected, and the motherboard has
 > seven fans ?

There are six 4-pin fan ports on the motherboard (the list above has fan7
but not fan6. So there are still in total: six fans).

Three fans (well - one AIO with a pump and two extra fans) are permanently installed
into the case. But I have connected an old, external CPU-Fan just to check the function
of fan2,fan5 and fan7 tachometers. So this worked :).

 >
 >> |SYSTIN:                 +29.5°C    sensor = thermistor
 >> |CPUTIN:                 +29.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
 >> |AUXTIN0:                 +4.0°C  (high = +67.0°C, hyst = +110.0°C)  sensor = thermistor
 >
 > Hmm, that hysteresis value seems wrong. I'll need to check if the
 > register addresses are correct.
Do you have the datasheet? I'm looking for it (I've also asked Nuvoton).
But so far no response. If you need a register range dump,
please let me know.

(AFAIK, all AMD5 X670E broads have dual chipset "chips". I think CPUTIN is
one of the two "PROM21" chips. Don't know what AUXTIN0 is...)
 >> |AUXTIN1:                +15.0°C    sensor = thermistor
 >> |AUXTIN2:                +15.0°C    sensor = thermistor
 >> |AUXTIN3:                +13.0°C    sensor = thermistor
 >
 > Looks like either those are not connected, or there is a temperature
 > offset which is not applied, or it is set to wrong values (the chip
 > does support temperature offset registers).
yes, I too think these are not connected. The values don't move, even after
a prolonged stresstest. Furthermore, neither the UEFI BIOS nor the Windows
utility has additional temperature gauges.

Regards,
Christian

  reply	other threads:[~2022-12-30 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221228135744.281752-1-linux () roeck-us ! net>
2022-12-30 17:32 ` [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D Christian Lamparter
2022-12-30 17:50   ` Guenter Roeck
2022-12-30 20:34     ` Christian Lamparter [this message]
2022-12-30 21:48       ` Guenter Roeck
2022-12-30 22:13         ` Sebastian Arnhold
2022-12-30 22:46           ` Guenter Roeck
2022-12-30 22:58           ` Christian Lamparter
2022-12-31 23:42             ` Sebastian Arnhold
2023-01-04  3:41               ` Guenter Roeck
2023-01-05 12:46                 ` Sebastian Arnhold
2023-01-07 18:37                   ` Denis Pauk
2023-01-07 18:50                     ` Denis Pauk
2022-12-28 13:57 Guenter Roeck
2023-05-11 21:02 ` Denis Pauk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c8d68feb-d44f-02c6-0a08-d199cef00b46@gmail.com \
    --to=chunkeey@gmail.com \
    --cc=ahmad@khalifa.ws \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sebastian.arnhold@posteo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.