From: PGNet Dev <pgnet.dev@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>, linux-hwmon@vger.kernel.org
Cc: marcel.p.bocu@gmail.com
Subject: Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"
Date: Mon, 23 Dec 2019 21:50:05 -0800 [thread overview]
Message-ID: <2c858787-1e5e-77e4-30ef-f17036b205c2@gmail.com> (raw)
In-Reply-To: <b2f72e65-4a80-0aaf-ce7e-0880fdcf60c7@roeck-us.net>
hi,
On 12/23/19 9:28 PM, Guenter Roeck wrote:
> In the specific issue referenced above, it appears that a Nuvoton NCT6796D
> was detected but not instantiated. Most likely the problem is that the IO address
> range necessary to access the chip is reserved by the BIOS. Looking into the
> kernel log would reveal that information. Again, that has nothing to do with
> support for the CPU installed on the board, but with the board vendor and,
> to a substantial degree, the lack of support for Linux by that board vendor.
not sure if this is of note,
superiotool --dump
superiotool r
No Super I/O found
I've contacted Asus tech re: BIOS 'gotchas' that might be interfering; I'll pass on your comments. So far, on other issues, they've been very cooperative/helpful; we'll see how this goes.
As for the kernel log, anything specific to look for, share here? Or just grab & post the whole thing somewhere?
> If you think something is missing that should be displayed by k10temp,
> if you have documentation from AMD describing the necessary registers to
> obtain this information, and if you have permission from AMD to publish
> it, please feel free to submit a patch adding it to the k10temp driver.
> Please make sure that the additional information follows the hardware
> monitoring ABI (specifically, CPU frequencies are not part of that ABI).
Not entirely sure on the 'should' of it ... yet.
I _can_ say that, currently, for the 'new' setup, the limited info with 'k10temp' is
(1) ASUSTeK PRIME X570-PRO mobo + Ryzen7 3700X
sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +59.9°C (high = +70.0°C)
Tctl: +59.9°C
and for an older board/cpu, also with 'k10temp', it's
(2) Asus M3A78-CM with a non-Ryzen, AMD Phenom II
sensors
k10temp-pci-00c3
Adapter: PCI adapter
temp1: +42.9°C (high = +70.0°C)
(crit = +99.5°C, hyst = +97.5°C)
atk0110-acpi-0
Adapter: ACPI interface
Vcore Voltage: 1.02 V (min = +0.85 V, max = +1.60 V)
+3.3 Voltage: 3.23 V (min = +2.97 V, max = +3.63 V)
+5 Voltage: 4.86 V (min = +4.50 V, max = +5.50 V)
+12 Voltage: 12.04 V (min = +10.20 V, max = +13.80 V)
CPU FAN Speed: 2789 RPM (min = 600 RPM, max = 7200 RPM)
CHASSIS FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
POWER FAN Speed: 0 RPM (min = 600 RPM, max = 7200 RPM)
CPU Temperature: +44.0°C (high = +60.0°C, crit = +95.0°C)
MB Temperature: +34.0°C (high = +45.0°C, crit = +95.0°C)
next prev parent reply other threads:[~2019-12-24 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 2:46 kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X" PGNet Dev
2019-12-24 5:28 ` Guenter Roeck
2019-12-24 5:50 ` PGNet Dev [this message]
2019-12-24 14:25 ` Guenter Roeck
2019-12-24 15:59 ` PGNet Dev
2019-12-24 16:29 ` Guenter Roeck
2019-12-24 17:14 ` PGNet Dev
2019-12-24 17:38 ` PGNet Dev
2019-12-24 19:57 ` Guenter Roeck
2019-12-24 20:34 ` PGNet Dev
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=2c858787-1e5e-77e4-30ef-f17036b205c2@gmail.com \
--to=pgnet.dev@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marcel.p.bocu@gmail.com \
/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