dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38364] New: Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1
Date: Thu, 16 Jun 2011 03:43:54 -0700 (PDT)	[thread overview]
Message-ID: <bug-38364-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=38364

           Summary: Ignoring invalid EDID block 1 do entire edid is
                    invalid and not just block 1
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: General
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: zaverel@free.fr


Hello ,

All is fine except i can't change resolution on my second monitor vga
,tv in fact, (reported as DVI-I-2 ) anymore with my 9400gt.


Now , i'm on :

linux-2.6.39-gentoo-r1
xorg-server-1.10.2
xf86-video-nouveau-0.0.16_pre20110323
libdrm-2.4.25

Errors in dmesg  are:

nouveau 0000:02:00.0: DVI-I-2: Ignoring invalid EDID block 1.
[drm:drm_edid_block_valid] *ERROR* Raw EDID:
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
<3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................




whatever i valid with xrandr is not really do on my tv
although xrandr say it's good , my tv always report 1202x670 50hz

I tried with and without xorg.conf

My last kernel working is linux-2.6.36-gentoo-r6.



If, i tweak drm_edid.c from kernel-2.6.39-gentoo-r1 like this:

--- drm_edid.c    2011-06-10 22:37:36.605848000 +0200
+++ linux/drivers/gpu/drm/drm_edid.c    2011-06-13 13:04:43.136786102 +0200
@@ -292,7 +292,7 @@
                   block + (valid_extensions + 1) * EDID_LENGTH,
                   j, EDID_LENGTH))
                 goto out;
-            if (drm_edid_block_valid(block + (valid_extensions + 1) *
EDID_LENGTH)) {
+            if (drm_edid_block_valid(block + (valid_extensions + 0) *
EDID_LENGTH)) {
                 valid_extensions++;
                 break;
             }

  that work good  like before but i'm not sure that is safe.

More info in 
http://lists.freedesktop.org/archives/nouveau/2011-June/008548.html

I can post logs here too , just tell me.

See you

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-06-16 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 10:43 bugzilla-daemon [this message]
2019-10-14 13:20 ` [Bug 38364] Ignoring invalid EDID block 1 do entire edid is invalid and not just block 1 bugzilla-daemon

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=bug-38364-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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