From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31154] New: EIZO S2242W has invalid extension block, no display
Date: Wed, 27 Oct 2010 01:33:47 -0700 (PDT) [thread overview]
Message-ID: <bug-31154-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31154
Summary: EIZO S2242W has invalid extension block, no display
Product: DRI
Version: unspecified
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: samtygier@yahoo.co.uk
i have a EIZO S2242W display, and radeon HD3650
with 2.6.34 it worked fine. only the base block of the EDID was read:
EDID:
00ffffffffffff0015c3042001010101
1113010380301e78eaf5c5a85337ae25
125054a10800a94081808140b3000101
010101010101283c80a070b023403020
3600da291100001a000000ff00323530
32363034390a20202020000000fd003b
3d1f4c11000a202020202020000000fc
005332323432570a2020202020200154
since 2.6.35 (i noticed at rc4) it will not display to the monitor past very
early boot messages. X wont display, neither will VTs. this is because
drm_edid.c now reads extension blocks, and the EZIO gives a block of zeros for
the extension block.
kernel: [ 6.371608] [drm:drm_edid_block_valid] *ERROR* Raw EDID:
kernel: [ 6.371644] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371646] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371648] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371650] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371652] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371654] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371656] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371658] <3>00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
kernel: [ 6.371660]
kernel: [ 6.371664] radeon 0000:08:00.0: DVI-I-1: EDID block 1 invalid.
booting with radeon.modeset=0 seems to by pass this so that i have a working
system.
i have bisected the change to:
61e57a8d72f2336faf39b5d940215cf085e01e6e is the first bad commit
commit 61e57a8d72f2336faf39b5d940215cf085e01e6e
Author: Adam Jackson <ajax <at> redhat.com>
Date: Mon Mar 29 21:43:18 2010 +0000
drm/edid: Fix secondary block fetch.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-10-27 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 8:33 bugzilla-daemon [this message]
2010-10-27 8:39 ` [Bug 31154] EIZO S2242W has invalid extension block, no display bugzilla-daemon
2010-10-27 8:40 ` bugzilla-daemon
2010-10-28 22:36 ` bugzilla-daemon
2010-11-03 11:37 ` bugzilla-daemon
2010-11-13 19:10 ` 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-31154-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