public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>
Cc: Luca Tettamanti <kronos.it@gmail.com>
Subject: asus_atk0110 not working on Asus P7P55D PRO
Date: Wed, 16 Sep 2009 23:28:39 -0600	[thread overview]
Message-ID: <4AB1C907.1070503@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Just built a new system with an Asus P7P55D PRO motherboard. The ATK0110 
driver doesn't seem to be able to retrieve any hardware monitoring 
parameters successfully, sensors gives:

atk0110-acpi-0
Adapter: ACPI interface
ERROR: Can't get value of subfeature in0_input: I/O error
Vcore Voltage:      +0.00 V  (min =  +0.80 V, max =  +1.60 V)
ERROR: Can't get value of subfeature in1_input: I/O error
+3.3V Voltage:      +0.00 V  (min =  +2.97 V, max =  +3.63 V)
ERROR: Can't get value of subfeature in2_input: I/O error
+5V Voltage:        +0.00 V  (min =  +4.50 V, max =  +5.50 V)

etc. and dmesg spits out a bunch of these:

ATK0110 ATK0110:00: atk_read_value_new: ACPI exception: AE_BUFFER_OVERFLOW

I'm guessing this board uses a different format than what the driver is 
expecting. I'm attaching the gzipped decompiled DSDT from the board, 
hopefully it's useful to somebody..

[-- Attachment #2: p7p55dpro.asl.gz --]
[-- Type: application/x-gzip, Size: 41457 bytes --]

             reply	other threads:[~2009-09-17  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  5:28 Robert Hancock [this message]
2009-09-17  9:17 ` asus_atk0110 not working on Asus P7P55D PRO Luca Tettamanti
2009-09-20 16:23 ` Luca Tettamanti
2009-09-20 17:47   ` Robert Hancock
2009-09-20 18:58     ` Luca Tettamanti
2009-09-20 22:51       ` Robert Hancock
2009-09-21 19:04         ` Luca Tettamanti
2009-09-22  0:52           ` Robert Hancock

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=4AB1C907.1070503@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=kronos.it@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox