All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: Problmem report
Date: Thu, 19 May 2005 06:24:00 +0000	[thread overview]
Message-ID: <20030616091453.5df69e51.khali@linux-fr.org> (raw)
In-Reply-To: <3EEB9F68.4040308@yahoo.fr>


> > Should be, unless Mandrake used the patched-kernel possibility (in
> > which case i2c is included in the kernel, so to say). Please make
> > sure however, using the following command:
> > rpm -qa | grep i2c
> > (and you can also try the same for "sensors", just in case)
> >
> no answer for i2c
> 
> For sensors :
> ksensors-0.7.2-4mdk
> liblm_sensors1-2.7.0-2mdk
> lm_sensors-2.7.0-2mdk

So we can assume Mandrake's kernel is i2c-patched. This will make our
job a bit harder, since you won't be able to upgrade i2c and lm_sensors
to CVS (and lm_sensors CVS won't work with i2c 2.7.0).

> > You can also check from which package do i2cdump and i2cdetect come
> > from, providing they're installed on your system.
> > 
> I do have i2cdump, i2cdetect, and i2cset.
> package , they all come form lm_sensors

Good news. At least we have some tools to work with.

The first thing I'd like you to try is an updated version of
sensors-detect. You can grab it from there:
http://www2.lm-sensors.nu/~lm78/cvs/lm_sensors2/prog/detect/sensors-detect

If possible, i'd be better if you could perform a cold reboot prior to
running the script. I'd like to make sure your hardware (I2C bus for
that matter) is peaceful and no nasty module is lurking.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 Problmem report Pierre AUSSAGUEL
2005-05-19  6:24 ` Pierre AUSSAGUEL
2005-05-19  6:24 ` Pierre AUSSAGUEL
2005-05-19  6:24 ` Pierre AUSSAGUEL
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare [this message]
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Pierre AUSSAGUEL
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Pierre AUSSAGUEL
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Pierre AUSSAGUEL
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=20030616091453.5df69e51.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --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.