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 14:26:30 +0000 [thread overview]
Message-ID: <4EDCD1C6.40307@catcons.co.uk> (raw)
In-Reply-To: <4EDA27AA.7030203@catcons.co.uk>
On 05/12/11 18:33, Luca Tettamanti wrote:
> Hi,
>
[snip]
>
> It's not easy to do, proper detection would require the full ACPI
> stack in userspace.
>
[snip]
> You shouldn't need to load the driver manually; if it's not
> auto-loaded then your board is not recognized by the driver.
> ASUS has changed the ATK0110 interface from time to time, so hopefully
> a few tweaks is all that's needed.
> Please send me a copy of this file:
> /sys/firmware/acpi/tables/DSDT
>
> Luca
Thanks Luca :)
Slackware loads (auto-loads?) modules via the /etc/rc.d/modules symlink.
One problem may be that I am using a symlink target manually edited
from the 2.6.33.4 version instead of the 2.6.38.7 version.
ACPI modules in the original 2.6.33.4 version, commented out ready for
uncommenting by the sysadmin include (I have omitted "obviously"
irrelevant ones): button, fan, processor and thermal. I disabled
acpi-cpufreq in favour of cpufreq_ondemand. Would you like me to try
any changes?
I temporarily commented out w83627ehf and added asus_atk0110 then
removed kernel option acpi_enforce_resources=lax, rebooted and created a
file by catting /sys/firmware/acpi/tables/DSDT which I am sending you
off list.
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 14:26 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 [this message]
2011-12-05 14:43 ` Jean Delvare
2011-12-05 15:28 ` Luca Tettamanti
2011-12-05 15:52 ` Charles
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=4EDCD1C6.40307@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.