From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Michal Zatloukal <myxal.mxl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Can't read DIMM SPD info (DDR2)
Date: Sun, 11 Sep 2011 10:09:45 +0200 [thread overview]
Message-ID: <20110911100945.73fffa6a@endymion.delvare> (raw)
In-Reply-To: <op.v1lxasq616tawo@esprimo>
Hi Michal,
On Sat, 10 Sep 2011 21:19:30 +0200, Michal Zatloukal wrote:
> I'm unable to get decode-dimms to display SPD info from my memory modules.
> Can someone please advise on finding the problem? The eeprom module is
> loaded. This is on both my main system (Kubuntu 10.10) - 2.6.35 kernel,
> i2c-tools 3.0.3-5 - and "latest" (Kubuntu 11.10 daily) - linux 3.0,
> lm-sensors 3.3.0-4 and i2c-tools 3.0.3-5). The HW is a Fujitsu Esprimo
> Mobile U9200 laptop (intel GM965). FWIW, the memtest that ships with
> 'buntu 11.10 (4.20 I think) reads the SPD info successfully.
Preliminary note: the version of lm-sensors doesn't matter, as
lm-sensors has nothing to do with reading SPD information.
Second preliminary note: as far as I know, memtest86 reads SPD
information using a BIOS call, while decode-dimms gets the information
over the SMBus, assuming that SPD EEPROMs are connected to the SMBus
and reachable at run time. This difference in access methods can
explain why memtest86 can see information and decode-dimms not on the
same system.
Third preliminary note: it is very common to not see SPD EEPROMs on
the SMBus on laptops (or not all of them). On my Thinkpad T60p, SPD
EEPROMs aren't visible on the SMBus at run time, so decode-dimms
doesn't work.
First thing to check is if the SMBus on your system is properly found
and supported:
# modprobe i2c-dev
# i2cdetect -l
On an Intel system you should see an entry like:
i2c-8 smbus SMBus I801 adapter at 0400 SMBus adapter
Then you can check if devices are seen on the bus:
# i2cdetect 8
If you see anything in address range 0x50 to 0x55, this is likely to be
SPD EEPROMs. Then you have to make sure that the eeprom module is
loaded:
# modprobe eeprom
$ decode-dimms
If you do not see anything in address range 0x50 to 0x55, then this
means you are in the same situation as me, i.e. SPD EEPROMs not
reachable at run time (most likely because they are behind an I2C
multiplexer or switch and the bus segment(s) with the SPD EEPROMs are
disabled by the BIOS before handing control to the OS. Unfortunately
the mux/switch control is not standard, so without detailed
documentation from the hardware manufacturer, it's very difficult to
restore access to the SPD EEPROMs at run time.
--
Jean Delvare
next prev parent reply other threads:[~2011-09-11 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 19:19 Can't read DIMM SPD info (DDR2) Michal Zatloukal
2011-09-11 8:09 ` Jean Delvare [this message]
[not found] ` <20110911100945.73fffa6a-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-09-11 9:50 ` Michal Zatloukal
2011-09-11 11:08 ` Jean Delvare
[not found] ` <20110911130823.2dff3fab-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-09-11 12:11 ` Michal Zatloukal
2011-09-11 12:40 ` 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=20110911100945.73fffa6a@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=myxal.mxl-Re5JQEeQqe8AvxtiuMwx3w@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).