public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Prendel <andre.prendel@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Udo van den Heuvel <udovdh@xs4all.nl>,
	linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 2.6.33 on jetway nc81-lf board
Date: Thu, 4 Mar 2010 10:17:41 +0100	[thread overview]
Message-ID: <20100304091741.GA1995@andre-laptop> (raw)
In-Reply-To: <20100302213709.951ee97b.akpm@linux-foundation.org>

On Tue, Mar 02, 2010 at 09:37:09PM -0800, Andrew Morton wrote:
> (cc lm-sensors)
> 
> On Mon, 01 Mar 2010 19:21:12 +0100 Udo van den Heuvel <udovdh@xs4all.nl> wrote:
> 
> > Hello,

Hi,

> > 
> > I just compiled 2.6.33 on a Jetway NC81-LF board with AMD 235E CPU.
> > While trying to get lm_sensors to work I get in dmesg stuff like:
> > 
> > f71882fg: Found f71862fg chip at 0x220, revision 18
> > ACPI: I/O resource f71882fg [0x220-0x227] conflicts with ACPI region
> > IP__ [0x225-0x226]
> > ACPI: If an ACPI driver is available for this device, you should use it
> > instead of the native driver
> > ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region
> > SOR1 [0xb00-0xb0f]
> > ACPI: If an ACPI driver is available for this device, you should use it
> > instead of the native driver
> > 
> > 
> > No other sensor-related modules are loaded.
> > 
> > What could be wrong?

See lm-sensors FAQ Chapter3 #39:

  http://www.lm-sensors.org/wiki/FAQ/Chapter3#Mysensorshavestoppedworkinginkernel2.6.31

Regards,
Andre

  reply	other threads:[~2010-03-04  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 18:21 2.6.33 on jetway nc81-lf board Udo van den Heuvel
2010-03-03  5:37 ` Andrew Morton
2010-03-04  9:17   ` Andre Prendel [this message]
2010-03-04 14:34     ` [lm-sensors] " Udo van den Heuvel
2010-03-05  2:09       ` 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=20100304091741.GA1995@andre-laptop \
    --to=andre.prendel@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=udovdh@xs4all.nl \
    /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