From: Stefan Dietrich <roots@gmx.de>
To: linux-hwmon@vger.kernel.org
Subject: Re: hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D
Date: Sun, 05 Jul 2020 15:20:38 +0200 [thread overview]
Message-ID: <2a4aff669c44ff56532ac721d687e2b38466b7c7.camel@gmx.de> (raw)
In-Reply-To: <e4ad12d1-3dca-2ff5-a0a6-12dc6dc22c83@roeck-us.net>
On Fri, 2020-07-03 at 10:10 -0700, Guenter Roeck wrote:
> On 7/3/20 9:03 AM, Stefan Dietrich wrote:
> > Hi all,
> >
> > with my Asus Formula XII Z490 and 5.7.0-7.1-liquorix-amd64 I'm
> > getting
> > the following error messages during boot:
> >
> > nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
> > nct6775 nct6775.656: Invalid temperature source 28 at index 0,
> > source
> > register 0x100, temp register 0x73
> > nct6775 nct6775.656: Invalid temperature source 28 at index 1,
> > source
> > register 0x200, temp register 0x75
> > nct6775 nct6775.656: Invalid temperature source 28 at index 2,
> > source
> > register 0x300, temp register 0x77
> > nct6775 nct6775.656: Invalid temperature source 28 at index 3,
> > source
> > register 0x800, temp register 0x79
> > nct6775 nct6775.656: Invalid temperature source 28 at index 4,
> > source
> > register 0x900, temp register 0x7b
> > nct6775 nct6775.656: Invalid temperature source 28 at index 5,
> > source
> > register 0xa00, temp register 0x7d
> >
>
> There is nothing much if anything we can do about that. The NCT6798D
> datasheet reports temperature source 28 as reserved. You could ask
> Asus for support, but their usual response is that they don't support
> Linux.
Thanks for the quick reply. Would you briefly outline why this makes it
inaccessible for the NCT6776 driver? Is there a pool of registers that
I might probe for values that could be related to the desired
temperature values, even if they need to be scaled?
Thanks,
Stefan
> > During sensors-detect, most of the standard temperature, voltage
> > and
> > rpm sources are recognized, however, some of the values,
> > particularly
> > voltages, are off quite a bit. In addition, output of additional
>
> Voltages need to be scaled. Scaling factors are mainboard specific
> and
> would have to be determined by comparing BIOS reported voltages with
> raw voltages (board vendors usually don't provide the information).
> Scaling factors can then be entered into /etc/sensors3.conf.
>
> > temperature sensors (via headers on the mainboard) which are
> > reported
> > fine in BIOS, are missing.
> >
>
> Again, this is mainboard specific. We don't know how the hardware
> reports
> those values. Only ASUS could provide the necessary information.
> Unfortunately, as mentioned above, they are not exactly known to be
> Linux friendly.
>
> Guenter
>
> > Booting with acpi_enforce_resources=lax doesn't solve this issue.
> >
> > I'd be happy if anyone would be able to fix this issue or give any
> > pointers on how to do so. Unfortunately I only have very basic
> > coding
> > skills, but I'll be happy to assist in debugging.
> >
> >
> > Cheers,
> > Stefan
> >
next prev parent reply other threads:[~2020-07-05 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:03 hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D Stefan Dietrich
2020-07-03 17:10 ` Guenter Roeck
2020-07-05 13:20 ` Stefan Dietrich [this message]
[not found] ` <48f415c34f4ca3f5239650711daaf1e11342da8e.camel@gmx.de>
[not found] ` <d54732db-255c-54be-ab43-997369e0da87@roeck-us.net>
2020-07-05 15:47 ` Stefan Dietrich
[not found] ` <e02ef4f8633e035ecf6019abb72e3a22bfc29732.camel@gmx.de>
[not found] ` <20200712224620.GA19097@roeck-us.net>
2020-07-13 17:40 ` Stefan Dietrich
2020-07-14 5:18 ` Guenter Roeck
2020-07-14 17:19 ` Stefan Dietrich
2020-07-14 21:29 ` Guenter Roeck
2020-07-14 23:17 Alexey Galakhov
2020-07-14 23:58 ` Guenter Roeck
2020-07-15 0:19 ` Alexey Galakhov
2020-07-15 2:33 ` Guenter Roeck
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=2a4aff669c44ff56532ac721d687e2b38466b7c7.camel@gmx.de \
--to=roots@gmx.de \
--cc=linux-hwmon@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).