From: Charles <c@catcons.co.uk>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Kernel module asus_atk0110
Date: Mon, 05 Dec 2011 15:52:30 +0000 [thread overview]
Message-ID: <4EDCE5EE.4040509@catcons.co.uk> (raw)
In-Reply-To: <4EDA27AA.7030203@catcons.co.uk>
On 05/12/11 20:58, Luca Tettamanti wrote:
> On Mon, Dec 5, 2011 at 3:43 PM, Jean Delvare <khali@linux-fr.org> wrote:
>>
>> The question is, does "sensors" output anything with only the
>> asus_atk0110 driver loaded? If not, hopefully Luca will be able to
>> figure out why from the DSDT.
>
> ATK0110 is not present in the DSDT. The IO range is reserved and used
> to check a single temperature against high and hysteresis thresholds
> (see method _L16) and notify WMI (yeah...). The method also reads a
> bit at 0x41 (AUIS) which is not used in the linux driver; the value is
> discarded, it might be a read-to-clear alarm bit; Jean do you know
> what that might be?
> Anyway, the board does not expose a monitoring framework :-(
>
> Luca
> [1] The disassembled DSDT: http://pastebin.com/YZX2uY3a
Thanks Luca :)
That sounds pretty final for using asus_atk0110 on the ASUS P8H67-V :(
Not surprisingly, then, sensors only finds coretemps when asus_atk0110
is modprobed.
It's great that an ordinary and naive user can get this level of suport
from real experts and so quickly. Many thanks to Jean, Guenter and Luca :)
Best
Charles
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-12-05 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 13:56 [lm-sensors] Kernel module asus_atk0110 Charles
2011-12-04 7:15 ` Charles
2011-12-05 13:03 ` Luca Tettamanti
2011-12-05 14:26 ` Charles
2011-12-05 14:43 ` Jean Delvare
2011-12-05 15:28 ` Luca Tettamanti
2011-12-05 15:52 ` Charles [this message]
2011-12-05 16:04 ` Jean Delvare
2011-12-06 15:21 ` Luca Tettamanti
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=4EDCE5EE.4040509@catcons.co.uk \
--to=c@catcons.co.uk \
--cc=lm-sensors@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 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.