public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: linux-hwmon@vger.kernel.org
Cc: marcel.p.bocu@gmail.com
Subject: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"
Date: Mon, 23 Dec 2019 18:46:28 -0800	[thread overview]
Message-ID: <bb629ef6-a669-8849-17f4-481c8c9f9347@gmail.com> (raw)

I'm running linux kernel 5.4.6-24.ge5f8301-default on an AMD Ryzen 3700X cpu.

I'm seeing very limited lm_sensors output.

I've posted my recent detail to an existing, but closed (?), lm_sensors issue,

	Can't display frequency and others of Ryzen7 3700X. #187
	https://github.com/lm-sensors/lm-sensors/issues/187#issuecomment-568630737

I note some recent work in kernel logs,

	https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4

particularly by Marcel Bocu.

b4 (re)opening any new tickets, etc, checking-in here first.

*IS* the kernel support for Zen2 Ryzen 3700X incomplete, as yet?

And, *should* sensors output for Zen arch be full/complete?

Or is there something lm_sensors-specific going on here, preventing the sensors output?

Thanks for any comments/hints!


             reply	other threads:[~2019-12-24  2:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  2:46 PGNet Dev [this message]
2019-12-24  5:28 ` kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X" Guenter Roeck
2019-12-24  5:50   ` PGNet Dev
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=bb629ef6-a669-8849-17f4-481c8c9f9347@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --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