From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensors in kernel 2.6.31
Date: Sat, 20 Feb 2010 17:55:10 +0000 [thread overview]
Message-ID: <20100220185510.5da9ae84@hyperion.delvare> (raw)
In-Reply-To: <4B643CC1.2000003@redhat.com>
On Sat, 20 Feb 2010 17:45:19 +0100 (CET), Otto wrote:
> Hi,
>
> At the moment my Linux server is running kernel 2.6.31-19 and using the
> asus_atk0110 kernel module. As I discussed with Hans de Goede in Dutch
> below, unfortunately the command `sensors` is only functioning on my
> system when using the 'acpi_enforce_resources=lax' kernel option. Hans
> advised me to send this email, because I have an Asus motherboard and it's
> a bad idea to use both the acp_enforce_resources option and the
> asus_atk0110 driver.
It's not that it's a bad idea... it is simply never needed. You need
the acpi_enforce_resource parameter only if you want to use a native
hwmon driver (e.g. it87 or w83627ehf) instead of asus_atk0110. If you
use the asus_atk0110 driver, you don't need it, by definition: it is an
ACPI driver.
> Ps. More info on my system is attached in the file sysinfo.txt.
> root@tommie:~# strings /dev/mem |grep P5
> P5K-V
> P5K-V
> P5K
>
> root@tommie:~# strings /dev/mem |grep ASUS
> ASUSTeK Computer INC.
> ASUSTeK Pegasus
These are stupid and potentially dangerous commands. Use dmidecode or
any equivalent command instead.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-02-20 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 14:05 [lm-sensors] sensors in kernel 2.6.31 Hans de Goede
2010-02-20 16:45 ` Otto
2010-02-20 17:55 ` Jean Delvare [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=20100220185510.5da9ae84@hyperion.delvare \
--to=khali@linux-fr.org \
--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.