linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 24 Dec 2019 09:38:24 -0800	[thread overview]
Message-ID: <77116fda-e9f2-ce0b-3add-3c4a4880d4b8@gmail.com> (raw)
In-Reply-To: <bf771959-f19b-1abb-7d94-bb5f65c68952@gmail.com>

On 12/24/19 9:14 AM, PGNet Dev wrote:
> , with ALL of those now available to desktop utils such as KDE's (slightly broken) ThermalMonitor plasma widget ... (need to figure out which of those are the CPU, vs Mobo, fan/temp sensors)
> 
> I don't know what, if any, issues are introducted by the use of `acpi_enforce_resources=lax` ...
> This _is_ just a workaround, yes?  I.e., BIOS still should have a fix?

and, fwiw, `pwmconfig` now executes correctly, generating /etc/fancontrol data/config.

given BIOS's foibles, is it generally recommended to USE thermal/fan control via `fancontrol` on linux/OS?  or leave it to BIOS?

  reply	other threads:[~2019-12-24 17:38 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
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 [this message]
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=77116fda-e9f2-ce0b-3add-3c4a4880d4b8@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;
as well as URLs for NNTP newsgroup(s).