From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31943] drm EDID checking is too strict
Date: Tue, 4 Jan 2011 15:04:38 -0800 (PST) [thread overview]
Message-ID: <20110104230438.30E0813004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31943-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31943
--- Comment #6 from Alex Deucher <agd5f@yahoo.com> 2011-01-04 15:04:38 PST ---
Created an attachment (id=41654)
View: https://bugs.freedesktop.org/attachment.cgi?id=41654
Review: https://bugs.freedesktop.org/review?bug=31943&attachment=41654
add edid strict option
The drm EDID checker is pretty strict about what EDIDs it will accept. Try
this patch and add drm.edid_strict=0 to your kernel command line.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-01-04 23:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-31943-502@http.bugs.freedesktop.org/>
2010-11-29 15:08 ` [Bug 31943] [drm:radeon_dvi_detect] *ERROR* HDMI Type A-1: probed a monitor but no|invalid EDID bugzilla-daemon
2010-11-29 15:09 ` bugzilla-daemon
2010-12-04 4:06 ` bugzilla-daemon
2010-12-13 15:32 ` [Bug 31943] drm EDID checking is too strict bugzilla-daemon
2011-01-04 23:04 ` bugzilla-daemon [this message]
2011-01-08 17:33 ` bugzilla-daemon
2011-01-08 17:37 ` bugzilla-daemon
2011-01-10 19:16 ` bugzilla-daemon
2011-02-05 17:39 ` bugzilla-daemon
2011-04-08 15:25 ` bugzilla-daemon
2011-04-08 16:05 ` bugzilla-daemon
2011-05-05 16:14 ` bugzilla-daemon
2011-05-09 8:58 ` bugzilla-daemon
2011-05-09 8:59 ` bugzilla-daemon
2011-05-09 9:27 ` bugzilla-daemon
2011-05-09 9:29 ` bugzilla-daemon
2011-11-02 21:27 ` bugzilla-daemon
2019-10-14 13:20 ` 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=20110104230438.30E0813004E@annarchy.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;
as well as URLs for NNTP newsgroup(s).