From: Charles <c@catcons.co.uk>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Kernel module asus_atk0110
Date: Sat, 03 Dec 2011 13:56:10 +0000 [thread overview]
Message-ID: <4EDA27AA.7030203@catcons.co.uk> (raw)
Hello :-)
According to http://hansdegoede.livejournal.com/7932.html and
http://pavelshub.com/blog/2010/12/fatal-error-inserting-w83627ehf/, the
proper module to use on ASUS motherboards equipped with the Nuvoton
NCT6776F is asus_atk0110, not w83627ehf, but there is an open lm_sensors
ticket (http://www.lm-sensors.org/ticket/2374) about sensors-detect not
supporting is asus_atk0110.
Running Slackware64 13.1 with a 2.6.38.7 kernel on an ASUS P8H67-V
motherboard with an NCT6776F and asus_atk0110 modeprobed, sensors-detect
3.3.1 was not successful. Digging deeper, looking for directories under
/sys/bus/acpi/drivers/ATK0110 found nothing:
root@CW8:~# ls -l /sys/bus/acpi/drivers/ATK0110
total 0
--w------- 1 root root 4.0K 2011-12-02 18:49 bind
--w------- 1 root root 4.0K 2011-12-02 18:49 uevent
--w------- 1 root root 4.0K 2011-12-02 18:49 unbind
Others have been able to use asus_atk0110 with lm_sensors (examples:
http://pastebin.com/8gREkwXZ,
http://comments.gmane.org/gmane.comp.gnome.apps.gkrellm/1556,
http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/423075-does-your-pwmconfig-find-modules-run.html;
there are many more).
The issue was worked around by using kernel option
acpi_enforce_resources=lax but I understand this will not work with
later kernels.
What to do for best?
Best
Charles
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2011-12-03 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 13:56 Charles [this message]
2011-12-04 7:15 ` [lm-sensors] Kernel module asus_atk0110 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
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=4EDA27AA.7030203@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.