All of lore.kernel.org
 help / color / mirror / Atom feed
From: mwesten <mwesten-H+0wwilmMs3R7s880joybQ@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Monitor with corrupted EDID
Date: Thu, 07 Feb 2013 14:37:41 -0500	[thread overview]
Message-ID: <51140285.4000108@verizon.net> (raw)
In-Reply-To: <CAAs+i9J0jFhD1==NYEGtwJDUPCH4oaxH7_9rdOsgU-R7iu=Gtg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 02/07/2013 10:16 AM, Flavio Castelli wrote:
> For an unknown reason both my monitors ended up with a corrupted EDID.
> They both provide VGA and DVI input. The VGA input works fine, while
> DVI is broken because of the EDID issue.
>
> Using these [1] instructions I have been able to read the EDID and fix
> it. Unfortunately I'm not able to write it back to the eeprom.
> I always get this message:
>    i2c i2c-1: sendbytes: NAK bailout.
>
> This is what I usually see in /var/log/message
> [dump of the EDID]
> nouveau 0000:01:00.0: DVI-D-1: EDID block 0 invalid.
> [drm] nouveau 0000:01:00.0: DDC responded, but no EDID for DVI-D-1
>
> Do you know why writing to the monitor does not work? I suspect the
> eeprom is write protected
>
> Googling a bit I noticed the nvidia driver allows to ignore the EDID
> returned by the monitor and use a custom one. I looks like the nouveau
> drivers do not offer this feature. Am I wrong?
>
> These are my specs:
>    * kernel: 3.4.11-2.16-desktop
>    * architecture: x86_64
>    * distribution: openSUSE 12.2
>    * xorg-x11-driver-video-nouveau-0.0.16_20120321_ab7291d-3.5.1.x86_64
>    * X.Org X Server 1.12.3
>    * NVIDIA Corporation G84M [Quadro FX 570M]
>    * Monitor 1: lenovo l220x wide
>    * Monitor 2: lenovo l2440p
>
>
> What should I do?
>
> Thanks in advance
> Flavio
> _______________________________________________
> Nouveau mailing list
> Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
> http://lists.freedesktop.org/mailman/listinfo/nouveau
>

I recently used a DOS program called ddcw.exe to fix the corrupted EDID 
on one of my monitors.

See this site, http://byuu.org/articles/computing/edid
and get it here, http://www.komeil.com/download/2984

If that doesn't work, the drm_kms_helper module in newer kernels should 
have a parameter to get around the problem.

See https://www.osadl.org/Single-View.111+M50eaf2f2c66.0.html

-Mike

  parent reply	other threads:[~2013-02-07 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 15:16 Monitor with corrupted EDID Flavio Castelli
     [not found] ` <CAAs+i9J0jFhD1==NYEGtwJDUPCH4oaxH7_9rdOsgU-R7iu=Gtg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-07 19:34   ` Marcin Slusarz
2013-02-07 19:37   ` mwesten [this message]
     [not found]     ` <51140285.4000108-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2013-02-08  8:23       ` Flavio Castelli
     [not found]         ` <5114B61C.40308-2uVk4PVEUg6lnMjI0IkVqw@public.gmane.org>
2013-02-08 10:44           ` mwesten
     [not found]             ` <5114D712.4060600-H+0wwilmMs3R7s880joybQ@public.gmane.org>
2013-02-08 13:11               ` Flavio Castelli
     [not found]                 ` <5114F991.3030703-2uVk4PVEUg6lnMjI0IkVqw@public.gmane.org>
2013-02-10 23:33                   ` Dave Airlie

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=51140285.4000108@verizon.net \
    --to=mwesten-h+0wwilmms3r7s880joybq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 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.