public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Murphy <jeremy.william.murphy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: Monitor's EDID not recognised
Date: Sun, 9 Mar 2008 17:08:20 +1100	[thread overview]
Message-ID: <200803091708.21053.jeremy.william.murphy@gmail.com> (raw)
In-Reply-To: <20080307150827.0cfa9b5c-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

On Sat, 8 Mar 2008 01:08:27 am Jean Delvare wrote:
>
> BTW, note that you should NOT access the nvidia I2C buses created by
> the binary nvidia X11 driver while not under X.

OK, thanks.  I did look for them outside of X, but they weren't there.


> OK. Two more things you can try:
>
> * Get rid of the binary nvidia driver for a moment, and try the
> nvidiafb driver. If it gets better, it suggests that the binary nvidia
> driver is at fault. If you get the same noise, it has to be a hardware
> issue.

There are no nVidia I2C buses visible with the nvidiafb driver, i2cdetect 
reports only the SMBus.  Here's a snippet from the X log, though:

(II) Loading sub module "i2c"
(II) LoadModule: "i2c"(II) Module already built-in
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module already built-in
(II) NV(0): I2C bus "DDC" initialized.
(II) NV(0): Probing for analog device on output A...
(--) NV(0):   ...found one
(II) NV(0): Probing for analog device on output B...
(--) NV(0):   ...can't find one
(II) NV(0): Probing for EDID on I2C bus A...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0):   ... none found
(II) NV(0): Probing for EDID on I2C bus B...
(II) NV(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) NV(0): I2C device "DDC:ddc2" removed.
(II) NV(0):   ... none found
(--) NV(0): CRTC 0 appears to have a CRT attached
(II) NV(0): Using CRT on CRTC 0

Address 0xA0?  Should that be 0x50?  


> * Did you try another video cable? The I2C bus signal is carried over 2
> dedicated pins on the VGA connector (12 and 15), if your cable happens
> to not have them wired properly for some reason, this could explain
> your problem.

OK, I'll have to ask around for one.  Thanks for your help.

Jeremy

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-03-09  6:08 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
     [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 [this message]
     [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=200803091708.21053.jeremy.william.murphy@gmail.com \
    --to=jeremy.william.murphy-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@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