From: CaT <cat@zip.com.au> To: Greg KH <greg@kroah.com>, sensors@stimpy.netroedge.com, frodol@dds.nl Cc: linux-kernel@vger.kernel.org, phil@netroedge.com Subject: Re: 2.6.0-t1: i2c+sensors still whacky Date: Fri, 18 Jul 2003 01:33:48 +1000 [thread overview] Message-ID: <20030717153348.GO4612@zip.com.au> (raw) In-Reply-To: <20030716225452.GA3419@kroah.com> 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. > If so, I suggest you ask the sensors developers on their mailing list as > this is a driver specific issue, and doesn't sound like a problem due to > the 2.5 port. I've added them to To/Cc. (Hey folks :) The full thread is available here: http://marc.theaimsgroup.com/?t=105826046600003&r=1&w=2 If you could have a look I'd really appreciate it. > > i2c_adapter i2c-0: found normal i2c_range entry for adapter 0, addr 0018 > > i2c_adapter i2c-0: Transaction (pre): CNT=00, CMD=09, ADD=30, DAT0=ff, DAT1=ff > > i2c_adapter i2c-0: Error: no response! > > It's really looking like the driver is trying to talk to a device that > isn't present, hence the timeouts. I tried the other drivers and they all failed nicely and without hassle. I looked through my past .config files and this is the driver that appears the most in use. -- "How can I not love the Americans? They helped me with a flat tire the other day," he said. - http://tinyurl.com/h6fo
WARNING: multiple messages have this Message-ID (diff)
From: cat@zip.com.au (CaT) To: Greg KH <greg@kroah.com>, sensors@stimpy.netroedge.com, frodol@dds.nl Cc: linux-kernel@vger.kernel.org, phil@netroedge.com Subject: 2.6.0-t1: i2c+sensors still whacky Date: Thu, 19 May 2005 06:24:05 +0000 [thread overview] Message-ID: <20030717153348.GO4612@zip.com.au> (raw) In-Reply-To: <20030716225452.GA3419@kroah.com> 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. > If so, I suggest you ask the sensors developers on their mailing list as > this is a driver specific issue, and doesn't sound like a problem due to > the 2.5 port. I've added them to To/Cc. (Hey folks :) The full thread is available here: http://marc.theaimsgroup.com/?t\x105826046600003&r=1&w=2 If you could have a look I'd really appreciate it. > > i2c_adapter i2c-0: found normal i2c_range entry for adapter 0, addr 0018 > > i2c_adapter i2c-0: Transaction (pre): CNT\0, CMD , ADD0, DAT0ÿ, DAT1ÿ > > i2c_adapter i2c-0: Error: no response! > > It's really looking like the driver is trying to talk to a device that > isn't present, hence the timeouts. I tried the other drivers and they all failed nicely and without hassle. I looked through my past .config files and this is the driver that appears the most in use. -- "How can I not love the Americans? They helped me with a flat tire the other day," he said. - http://tinyurl.com/h6fo
next prev parent reply other threads:[~2003-07-17 15:20 UTC|newest] Thread overview: 16+ 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 ` CaT [this message] 2005-05-19 6:24 ` 2.6.0-t1: i2c+sensors still whacky CaT 2003-07-18 2:33 ` Greg KH 2005-05-19 6:24 ` Greg KH 2003-07-21 7:37 ` CaT 2005-05-19 6:24 ` CaT 2003-07-21 7:58 ` CaT 2005-05-19 6:24 ` 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=20030717153348.GO4612@zip.com.au \ --to=cat@zip.com.au \ --cc=frodol@dds.nl \ --cc=greg@kroah.com \ --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: linkBe 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.