From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Jeremy Murphy
<jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Monitor's EDID not recognised
Date: Fri, 7 Mar 2008 11:06:10 +0100 [thread overview]
Message-ID: <20080307110610.3a48021d@hyperion.delvare> (raw)
In-Reply-To: <200803071923.32035.jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Jeremy,
On Fri, 7 Mar 2008 19:23:31 +1100, Jeremy Murphy wrote:
>
> Apologies for what might be a frequently asked question, but I haven't found
> an answer on the web yet.
>
> I have a Sony CPD-G520 (21" CRT monitor) for which I would like to be able to
> read the EDID. However, sensors-detect finds SPD EEPROM where the EDID
> EEPROM probably, and typically, is.
>
> This is an edit from sensors-detect output:
>
> Next adapter: SMBus I801 adapter at 0400 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x44
> Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
> Client found at address 0x50
> Probing for `Analog Devices ADM1033'... No
> Probing for `Analog Devices ADM1034'... No
> Probing for `SPD EEPROM'... Yes
> (confidence 8, not a hardware monitoring chip)
> Probing for `EDID EEPROM'... No
>
> It then gives the same output for 0x50 at 0x51, 0x52 and 0x53. When I load
> the eeprom module it says that it is handling it. The problem is that there
> are no valid EDIDs at those addresses, as reported by decode-edid.pl (it's a
> 64-bit system so no get-edid). So I'm not sure whether a) the EDID is
> corrupt, or b) it's not actually accessing the EDID. Any ideas?
What does decode-dimms.pl say? If you have 4 memory modules on this
system then it is expected that sensors-detect (or i2cdetect) will see
4 SPD EEPROMs at 0x50, 0x51, 0x52 and 0x53.
> The graphics card is an NVIDIA 7600GS, motherboard chipset is the Intel ICH7
> family. Hardware monitoring of CPU and motherboard temperature via I2C works
> fine. Thanks!
I'm not sure why you would expect the EDID EEPROM on the ICH7 SMBus.
I've never seen an EDID EEPROM there. The EDID EEPROM is typically
accessed through an I2C bus on the graphics adapter. You will need a
driver for this. The binary nvidia X11 driver should work, the nvidiafb
framebuffer driver should work as well (that's what I am using myself).
After loading the driver, 2 or 3 additional I2C buses should be listed
by "i2cdetect -l" (don't forget to load i2c-dev beforehand), and
decode-edid.pl (or the more user-friendly ddcmon script) should find
the EDID on one of them.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-03-07 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 8:23 Monitor's EDID not recognised Jeremy Murphy
[not found] ` <200803071923.32035.jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-03-07 10:06 ` Jean Delvare [this message]
[not found] ` <20080307110610.3a48021d-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-07 11:37 ` Jeremy Murphy
[not found] ` <200803072237.36693.jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-03-07 12:11 ` Jean Delvare
[not found] ` <20080307131120.4891f78e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-07 13:39 ` Jeremy Murphy
[not found] ` <200803080039.55332.jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-03-07 14:08 ` Jean Delvare
[not found] ` <20080307150827.0cfa9b5c-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-03-09 6:08 ` Jeremy Murphy
[not found] ` <200803091708.21053.jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-03-09 14:45 ` 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=20080307110610.3a48021d@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=jeremy.william.murphy-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