From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to
Date: Mon, 08 Mar 2010 21:17:43 +0000 [thread overview]
Message-ID: <20100308221743.10ff1de6@hyperion.delvare> (raw)
In-Reply-To: <20100305222015.GR11436@alpha.zimage.com>
On Mon, 8 Mar 2010 21:57:25 +0100, Luca Tettamanti wrote:
> On Sat, Mar 6, 2010 at 1:02 AM, Luca Tettamanti <kronos.it@gmail.com> wrote:
> > On Fri, Mar 5, 2010 at 11:20 PM, Phillip Pi <ant@zimage.com> wrote:
> >> This morning, I rebooted my old Debian box to start using its new Kernel
> >> 2.6.32 from 2.6.30, but I noticed my lm_sensors didn't show everything
> >> (voltages, fan RPMs, etc.) anymore compared to 2.6.30 and earlier. I am
> >> using a MSI K8N NEO4-F (MS-7125) motherboard.
> > [...]
> >> I looked at the FAQ and saw
> >> http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31
> >> which look like my issue and matches dmesg: http://pastie.org/856424 ...
> >>
> >> I am scared to use the lax method since it is not recommended. Is there
> >> another way to show the datas safely? Or do I have to use this trick or
> >> live without them?
> >
> > Asus provides an ACPI interface for accessing the sensors in a safe
> > way; I don't know what it's used on MSI boards, but I can take a look:
> > please send me a dump of the DSDT table
>
> Nothing interesting in the DSDT; the hwmon chip is used only for
> reading a temperature (TZ).
> I think you can use "acpi_enforce_resources=lax", there not other ways
> to access the sensor data.
If you do, please make sure to blacklist the ACPI "thermal" driver.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-03-08 21:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 22:20 [lm-sensors] Upgraded my old Debian box's Kernel from 2.6.30 to Phillip Pi
2010-03-06 0:02 ` Luca Tettamanti
2010-03-08 20:57 ` Luca Tettamanti
2010-03-08 21:10 ` Phillip Pi
2010-03-08 21:17 ` Jean Delvare [this message]
2010-03-08 21:28 ` Luca Tettamanti
2010-03-08 21:28 ` Phillip Pi
2010-03-08 21:31 ` Phillip Pi
2010-03-08 21:34 ` Luca Tettamanti
2010-03-08 21:38 ` Jean Delvare
2010-03-08 21:39 ` Phillip Pi
2010-03-08 21:43 ` Phillip Pi
2010-03-08 21:44 ` Luca Tettamanti
2010-03-09 8:40 ` Jean Delvare
2010-03-09 8:45 ` Jean Delvare
2010-03-09 8:48 ` Jean Delvare
2010-03-09 9:05 ` Phillip Pi
2010-03-09 9:30 ` Jean Delvare
2010-03-09 14:20 ` Phillip Pi
2010-03-09 16:35 ` Jean Delvare
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=20100308221743.10ff1de6@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.