All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: i2c for Alpha
Date: Thu, 19 May 2005 06:24:22 +0000	[thread overview]
Message-ID: <20031027215823.1531b146.khali@linux-fr.org> (raw)
In-Reply-To: <200310121707.56799.jeff@jdfiles.org>


> > 1* Get sensors-detect from CVS and give it a try. It knows much more
> > than the one in 2.6.5. Of course it will make reference to drivers
> > that you don't have, but just don't care. Feel free to send us the
> > complete output of sensors-detect, it might help us helping you.
> 
> Still nothing detected. I am currently trying to work this out from
> the other end- finding documentation of what chips are on the
> mainboard. 
> 
> > 2* If the above doesn't give any result, please run "i2cdetect 0"
> > and send us the output of that command.
> 
> Strike 2. 
> 
> www root # i2cdetect 0
>   WARNING! This program can confuse your I2C bus, cause data loss and
>   worse! I will probe file /dev/i2c-0
>   You have five seconds to reconsider and press CTRL-C!
> 
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
> 70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

Well...Your bus looks damn empty. Either your bus driver is broken, or
there really isn't any chipset connected to it. Maybe there is another
I2C bus on your system?

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

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:24 i2c for Alpha Jeff Sacksteder
2005-05-19  6:24 ` Mark Studebaker
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Mark Studebaker
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Morris, John
2005-05-19  6:24 ` Philip Edelbrock
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` Jeff Sacksteder
2005-05-19  6:24 ` jeff
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare
2005-05-19  6:24 ` Jean Delvare [this message]

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=20031027215823.1531b146.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.