dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49747] dpms on only works on DP0 on a hd5700
Date: Thu, 10 May 2012 20:39:27 +0000	[thread overview]
Message-ID: <bug-49747-502-Fuqb5T3UDz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49747-502@http.bugs.freedesktop.org/>

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

--- Comment #12 from Daniel Vetter <daniel@ffwll.ch> 2012-05-10 13:39:27 PDT ---
Ok, more throughrough testing on all ports. The screens are both the same
model, but different manufacturing dates (and firmware revision according to
osd).

DP0 seems to work in all cases, although when I switch off the screeen or
unplug the cable, I need to do a vt switch to get a picture on the screen.

DP1-4 seem to work with the hdmi cable for a dpms off/on cycle, but not with
the dp cable.

DP1-4 doesn't work at all (either hdmi or dp) when the monitor got switched off
or the cable freshly plugged in while linux is running. Even xrandr
--off/--auto doesn't help, only rebooting.

The entire thing seems pretty flaky, even switching the input selection on the
screen between hdmi and dp is enough to loose the dp signal. With this round of
playing I've also seen new noise in dmesg:

[ 1275.106268] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid,
remainder is 44
[ 1275.106271] Raw EDID:
[ 1275.106272]          00 ff ff ff ff ff ff 00 22 f0 f9 26 01 01 01 01
[ 1275.106274]          0b 13 01 04 a5 36 23 78 ee ce 50 a3 54 4c 99 26
[ 1275.106275]          77 0f 50 54 a5 6b 80 81 40 a9 00 a9 40 b3 00 d1
[ 1275.106276]          00 01 01 01 01 01 01 28 3c 80 a0 70 b0 23 40 30
[ 1275.106277]          20 36 00 22 60 21 00 00 1a 77 00 00 fc 00 48 50
[ 1275.106278]          20 4c 50 32 34 37 35 77 0a 20 20 00 00 00 fd 00
[ 1275.106279]          30 55 1e 5e 15 04 11 50 d2 f8 58 f0 00 00 00 00
[ 1275.106280]          ff 00 43 5a 43 39 31 31 30 30 39 34 0a 20 20 00

and similar corrupted EDIDs. xrandr always displayed the correct modelist
though, afact. I'll do the radeontool dump now.

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

  parent reply	other threads:[~2012-05-10 20:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 17:57 [Bug 49747] New: dpms on only works on DP0 on a hd5700 bugzilla-daemon
2012-05-10 17:58 ` [Bug 49747] " bugzilla-daemon
2012-05-10 17:58 ` bugzilla-daemon
2012-05-10 17:59 ` bugzilla-daemon
2012-05-10 17:59 ` bugzilla-daemon
2012-05-10 18:01 ` bugzilla-daemon
2012-05-10 18:18 ` bugzilla-daemon
2012-05-10 18:29 ` bugzilla-daemon
2012-05-10 20:12 ` bugzilla-daemon
2012-05-10 20:13 ` bugzilla-daemon
2012-05-10 20:14 ` bugzilla-daemon
2012-05-10 20:17 ` bugzilla-daemon
2012-05-10 20:18 ` bugzilla-daemon
2012-05-10 20:39 ` bugzilla-daemon [this message]
2012-05-10 20:44 ` bugzilla-daemon
2012-05-10 20:54 ` bugzilla-daemon
2012-05-10 20:55 ` bugzilla-daemon
2012-05-10 20:56 ` bugzilla-daemon
2012-05-10 20:58 ` bugzilla-daemon
2012-05-10 20:58 ` bugzilla-daemon
2012-05-10 22:45 ` bugzilla-daemon
2012-05-11  6:09 ` bugzilla-daemon
2014-01-17  6:48 ` 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-49747-502-Fuqb5T3UDz@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;
as well as URLs for NNTP newsgroup(s).