From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@redhat.com>,
Laurence Vanek <lvanek@charter.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Jean Delvare <khali@linux-fr.org>
Subject: Re: Kernel 2.6.16-1.2122_FC5 & lmsensors
Date: Mon, 22 May 2006 19:53:16 +0200 [thread overview]
Message-ID: <20060522175316.GC2979@elf.ucw.cz> (raw)
In-Reply-To: <20060522174818.GA8016@redhat.com>
On Po 22-05-06 13:48:18, Dave Jones wrote:
> On Mon, May 22, 2006 at 12:08:56PM -0500, Laurence Vanek wrote:
> > Upon updating to the latest kernel (2.6.16-1.2122_FC5) & rebooting I
> > find that I no longer have lmsensors. /var/log/messages gives this in
> > the suspect area:
> >
> > ==========
> > May 22 11:42:42 localhost kernel: i2c_adapter i2c-0: SMBus Quick command
> > not supported, can't probe for chips
> > May 22 11:42:42 localhost kernel: i2c_adapter i2c-1: SMBus Quick command
> > not supported, can't probe for chips
> > May 22 11:42:42 localhost kernel: i2c_adapter i2c-2: SMBus Quick command
> > not supported, can't probe for chips
> > =========
> >
> > something new in this release?
>
> Probably a side-effect of [PATCH] smbus unhiding kills thermal management
> merged in 2.6.16.17. Is this an ASUS board ?
You can disable CONFIG_ACPI_SLEEP, if it gets you lmsensors back, that
is it.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-05-22 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4471F028.4090803@charter.net>
2006-05-22 17:48 ` Kernel 2.6.16-1.2122_FC5 & lmsensors Dave Jones
2006-05-22 17:53 ` Pavel Machek [this message]
2006-05-22 18:38 ` 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=20060522175316.GC2979@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=akpm@osdl.org \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=chrisw@sous-sol.org \
--cc=davej@redhat.com \
--cc=gregkh@suse.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvanek@charter.net \
/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.