All of lore.kernel.org
 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 12:34:59 -0800	[thread overview]
Message-ID: <218bc0cd-3b42-55a8-9726-1baf2f0a2aee@gmail.com> (raw)
In-Reply-To: <5400ddb2-c70d-11b4-4414-158c7c40afa5@roeck-us.net>

On 12/24/19 11:57 AM, Guenter Roeck wrote:
> The BIOS does exactly what the board vendor wants it to do: Reject direct access
> to the Super-IO chip. The board vendor wants you to access the chip through ACPI,
> ie with asus_atk0110. Unfortunately, it looks like the board vendor also
> changed the ACPI data sufficiently enough to make that driver not work for
> your board (assuming you tried loading it without acpi_enforce_resources=lax).


WITH module

	lsmod | grep asus_atk
		asus_atk0110           24576  0

but WITHOUT cmd line

	... acpi_enforce_resources=lax ...


`sensors` returns ONLY the limited

	sensors
		k10temp-pci-00c3
		Adapter: PCI adapter
		Tdie:         +34.4°C  (high = +70.0°C)
		Tctl:         +34.4°C

OTOH, switching, WITHOUT module

	lsmod | grep asus_atk
		(empty)

and WITH cmd line

	... acpi_enforce_resources=lax ...


`sensors` returns the full(er) output, as posted.

note again, in this case, even ATTEMPTING to load asus_atk0110 FAILs due to the apparent conflict with the =lax spec'n.

> There is nothing we can do about that unless the board vendor provides the information
> necessary to interpret the DSDT, or someone spends the time to reverse engineer it.

got it.  i'll poke at ASUS support.

thx 4 the education re: this^^ !

      reply	other threads:[~2019-12-24 20:35 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
2019-12-24 19:57             ` Guenter Roeck
2019-12-24 20:34               ` PGNet Dev [this message]

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=218bc0cd-3b42-55a8-9726-1baf2f0a2aee@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.