From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42112] radeon driver (kms) fails to read EDID data from external LCD monitor with kernel 3.0.4 on a RV350 chip
Date: Tue, 30 Aug 2011 20:29:44 GMT [thread overview]
Message-ID: <201108302029.p7UKTiP1030760@demeter2.kernel.org> (raw)
In-Reply-To: <bug-42112-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42112
mrsteven@gmx.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #4 from mrsteven@gmx.de 2011-08-30 20:29:42 ---
Oh, it seems I have to apologize for my noise, because the problem was the
monitor itself: It somehow got confused and "forgot" its EDID data. The problem
was fixed by pulling its power line and then plugging it in again, i.e. doing a
hard reset of the monitor.
And yes, this makes perfect sense, because I see no commit relating to EDID
reading, parsing, or the handling of the data in the radeon driver. The only
one I see is a change for some HDMI connectors, which doesn't affect me.
Sorry for any inconvenience.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2011-08-30 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 19:09 [Bug 42112] New: radeon driver (kms) fails to read EDID data from external LCD monitor with kernel 3.0.4 on a RV350 chip bugzilla-daemon
2011-08-30 19:15 ` [Bug 42112] " bugzilla-daemon
2011-08-30 19:42 ` bugzilla-daemon
2011-08-30 20:11 ` bugzilla-daemon
2011-08-30 20:29 ` bugzilla-daemon [this message]
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=201108302029.p7UKTiP1030760@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.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 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.