All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49
Date: Tue, 14 Jun 2005 15:18:46 +0000	[thread overview]
Message-ID: <pr6PyFKP.1118754459.8623930.khali@localhost> (raw)
In-Reply-To: <2ef564dc05061302175b8427fd@mail.gmail.com>


Hi Sukhdeep,

> Our motherboard is a custom one (used for our(Symbol) wireless switches )
> They are similar to the kt400 is what i know.
>
> Here is the i2cdump :

This looks like two distinct Winbond W83782D chips to me, one at 0x29 and
one at 0x2d.

> The warning went after loading with :
>        #modprobe w83781d init=0 force_subclients=0,0x29,0x4a,0x4b

Yes, the two chips previously had their subclients colliding (BIOS
didn't intialize them properly). The force_sublients option let you fix
that.

> But, I now see that the sensors command gives _TWO_ results :

Well, there are two chips, what did you expect?

> The second output seems quite vague.

Looks like the voltage inputs are not wired. Fans and temperatures may be
though.

> I also see two directories created in the /proc -
>
> WS5K #cat /proc/sys/dev/sensors/
> chips             w83782d-i2c-0-29  w83782d-i2c-0-2d

One directory per chip. What's the problem?

> Can you make out what's going wrong ?

Nothing is going wrong (anymore). Once the subclient addresses are fixed
not to collide, you get two working chips. You said it was a custom
board, if you are the one building it, you *should* know which chips are
on it and how they are wired. Don't expect us to tell you, that's not
something we can guess.

As for strange temperature values, you may try changing the sensor types
(/proc/sys/dev/sensors/w83782d-i2c-0-*/sensor* or /etc/sensors.conf).
Maybe your board uses thermal diodes rather than thermistors.

--
Jean Delvare

  parent reply	other threads:[~2005-06-14 15:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 11:17 [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
2005-06-13 11:44 ` Jean Delvare
2005-06-13 12:25 ` Jean Delvare
2005-06-13 12:41 ` Sukhdeep Johar
2005-06-13 19:15 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
2005-06-13 22:25 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
2005-06-13 22:34 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
2005-06-13 23:01 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Yani Ioannou
2005-06-13 23:11 ` [lm-sensors] w83781d.o: Subclient 0 registration at address Jean Delvare
2005-06-14  8:09 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 0x49 Sukhdeep Johar
2005-06-14  8:18 ` Sukhdeep Johar
2005-06-14  8:53 ` Yani Ioannou
2005-06-14 10:20 ` Jean Delvare
2005-06-14 15:18 ` Jean Delvare [this message]
2005-06-14 17:13 ` Sukhdeep Johar
2005-06-14 20:46 ` [lm-sensors] w83781d.o: Subclient 0 registration at address 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=pr6PyFKP.1118754459.8623930.khali@localhost \
    --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.