From: Stefan Dietrich <roots@gmx.de>
To: linux-hwmon@vger.kernel.org
Subject: hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D
Date: Fri, 03 Jul 2020 18:03:26 +0200 [thread overview]
Message-ID: <66053ce744dafbad6925df53b6ef2db1e2859740.camel@gmx.de> (raw)
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
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
temperature sensors (via headers on the mainboard) which are reported
fine in BIOS, are missing.
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 reply other threads:[~2020-07-03 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 16:03 Stefan Dietrich [this message]
2020-07-03 17:10 ` hwmon (nct6775): Please fix Invalid temperature source error for NCT6798D Guenter Roeck
2020-07-05 13:20 ` Stefan Dietrich
[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
-- strict thread matches above, loose matches on Subject: below --
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=66053ce744dafbad6925df53b6ef2db1e2859740.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