All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: Problem status (ABIT NV7m)
Date: Thu, 19 May 2005 06:24:01 +0000	[thread overview]
Message-ID: <3EF48B5C.9080504@paradyne.com> (raw)
In-Reply-To: <20030616210337.1874dc27.khali@linux-fr.org>

Don't recall seeing the original mail, guess I was busy.
In the original mail referenced below, the nforce driver is totally whacked.
It's giving a response to every address. Either the driver or the bus itself is hosed.
Power-cycle and try again.
Since you say you have a 83627hf, your best bet is to use the new ISA-only w83627hf driver
in CVS. Then you can bypass whatever problem you're having with nforce or its i2c bus.
mds

Jean Delvare wrote:
> (MARK, PLEASE READ THIS)
> 
> Hi Yann,
> 
> It has been quite a while since we last discussed about the problem you
> had with lm_sensors 2.7.0 and your Abit NV7m motherboard. I'm coming
> back to you for three reasons.
> 
> 1* We are about to release lm_sensors 2.8.0. I'd like to see your
> problem solved before this happen.
> 
> 2* We have had another user reporting a problem that seems to be similar
> to yours. Maybe this will help understand what happens.
> 
> 3* I hope that MDS will be more available than last time. I think he
> will be more able to help you than I was.
> 
> So, did you manage to solve your problem? (Mark, see
> http://archives.andrew.net.au/lm-sensors/msg02219.html for a reminder)
> 
> Could you try i2c & lm_sensors CVS to see wether the problem is still
> there or not? This would be more than helpful.
> 

  reply	other threads:[~2005-05-19  6:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 Problem status (ABIT NV7m) Jean Delvare
2005-05-19  6:24 ` Mark D. Studebaker  [this message]
2005-05-19  6:24 ` 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=3EF48B5C.9080504@paradyne.com \
    --to=mds@paradyne.com \
    --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.