linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: CaT <cat@zip.com.au>
Cc: sensors@stimpy.netroedge.com, frodol@dds.nl,
	linux-kernel@vger.kernel.org, phil@netroedge.com
Subject: Re: 2.6.0-t1: i2c+sensors still whacky
Date: Thu, 17 Jul 2003 19:33:51 -0700	[thread overview]
Message-ID: <20030718023350.GA5902@kroah.com> (raw)
In-Reply-To: <20030717153348.GO4612@zip.com.au>

On Fri, Jul 18, 2003 at 01:33:48AM +1000, CaT wrote:
> On Wed, Jul 16, 2003 at 03:54:52PM -0700, Greg KH wrote:
> > On Thu, Jul 17, 2003 at 08:47:18AM +1000, CaT wrote:
> > > On Wed, Jul 16, 2003 at 12:31:35AM -0700, Greg KH wrote:
> > > > Then just load the i2c_piix4 module.  If things still work just fine,
> > > > then try the i2c-adm1021 driver.  See what the kernel log says then.
> > > 
> > > All went well till the last step of loading the adm1021 driver.
> > 
> > And you are sure you have this hardware device?  Is that what the
> 
> Yes. I am very definate that this worked in past 2.5 kernels. Remember
> how it used to turn my laptop off under load? I was able to read my
> temps and stuff though.
> 
> > sensors package for 2.4 uses?  And 2.4 works just fine, right?
> 
> I don't use 2.4. Haven't for ages.

I would _really_ encourage you to try this, and run the sensors_detect
program to have the scripts tell you what hardware you really have, and
see if the 2.4 drivers work properly for you.

Without that, I don't know how to debug the 2.5 problem.

Let us know how that works out.

thanks,

greg k-h

  reply	other threads:[~2003-07-18  2:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15  9:07 2.6.0-t1: i2c+sensors still whacky (hi Greg :) CaT
2003-07-15 16:11 ` Greg KH
2003-07-16  6:04   ` CaT
2003-07-16  6:10     ` Greg KH
2003-07-16  6:29       ` CaT
2003-07-16  7:31         ` Greg KH
2003-07-16 22:47           ` CaT
2003-07-16 22:54             ` Greg KH
2003-07-17 15:33               ` 2.6.0-t1: i2c+sensors still whacky CaT
2003-07-18  2:33                 ` Greg KH [this message]
2003-07-21  7:37                   ` CaT
2003-07-21  7:58                     ` CaT

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=20030718023350.GA5902@kroah.com \
    --to=greg@kroah.com \
    --cc=cat@zip.com.au \
    --cc=frodol@dds.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil@netroedge.com \
    --cc=sensors@stimpy.netroedge.com \
    /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;
as well as URLs for NNTP newsgroup(s).