linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Michael Fuckner <michael-iWcS09LKDTLR7s880joybQ@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Decode dimms on dual socket machines
Date: Tue, 12 Apr 2011 13:26:11 +0200	[thread overview]
Message-ID: <20110412132611.045ace21@endymion.delvare> (raw)
In-Reply-To: <4DA4250A.3060907-iWcS09LKDTLR7s880joybQ@public.gmane.org>

Hallo Michael,

On Tue, 12 Apr 2011 12:10:18 +0200, Michael Fuckner wrote:
> I have a Dual-Socket Machine with Supermicro Motherboard (X8DTH-iF) and 
> I'd like to use decode-dimms, but it just decodes the modules on one 
> socket (dmidecode -t 17 and ipmitool sdr show all 6 modules on both 
> sockets).
> 
> 
> Does anybody have a clue how to access those other 3 modules?

Odds are that your SMBus is multiplexed and the other memory sockets
are connected to a different bus segment. Unfortunately there are
various ways to achieve multiplexing, this can't be detected
automatically and it is rarely documented in the board manual. So you
will have to ask the vendor for technical details on this point.
Multiplexing can be done through GPIO pins (either on the south bridge
or the Super-I/O chip) or with a chip on the SMBus itself.

Note that you will need a recent enough kernel (>= 2.6.36) to have
support for SMBus multiplexing.

> this is what I can see right now:
> test24:/media/i2c-tools # ./tools/i2cdetect 0
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-0.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- -- -- -- 08 -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- UU -- UU -- UU -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2e 2f
> 30: 30 -- 32 -- 34 -- -- -- -- -- -- -- -- -- 3e --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: UU -- UU -- UU -- -- -- -- -- -- -- -- -- -- --
> 60: -- 61 62 -- -- -- -- -- -- 69 -- -- -- -- -- --
> 70: 70 -- -- -- -- -- -- --

FWIW, address 0x70 is used by the PCA954x multiplexers, so maybe this
is what you have (and a driver is available).

At 0x2f is probably a W83793 or W83795 monitoring chip, supported by
the w83793 and w83795 drivers, respectively. Only use these dedicated
drivers if you do not intend to use the IPMI features of the board.

> 18,1a,1c: jc42 temperature sensors
> 50,52,54: eeproms

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

  parent reply	other threads:[~2011-04-12 11:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-12 10:10 Decode dimms on dual socket machines Michael Fuckner
     [not found] ` <4DA4250A.3060907-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-12 11:26   ` Jean Delvare [this message]
     [not found]     ` <20110412132611.045ace21-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-12 12:52       ` Michael Fuckner
     [not found]         ` <4DA44B05.906-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-12 13:53           ` Jean Delvare
     [not found]             ` <20110412155345.4644e51c-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-13  6:13               ` Michael Lawnick
     [not found]                 ` <4DA53F22.5020105-Mmb7MZpHnFY@public.gmane.org>
2011-04-13  8:39                   ` Jean Delvare
     [not found]                     ` <20110413103952.68bdb6fa-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-04-13 10:06                       ` Michael Fuckner
     [not found]                         ` <4DA575C3.1050100-iWcS09LKDTLR7s880joybQ@public.gmane.org>
2011-04-13 11:45                           ` Jean Delvare
2011-04-19 12:24                           ` Jean Delvare
2011-04-14 11:42                       ` Michael Lawnick

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=20110412132611.045ace21@endymion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael-iWcS09LKDTLR7s880joybQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).