dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71461] monitor doesn't get detected after boot or disconnection
Date: Tue, 08 Apr 2014 17:16:31 +0000	[thread overview]
Message-ID: <bug-71461-2300-I8sufchCnG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71461-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=71461

--- Comment #19 from Tom Yan <tom.ty89@gmail.com> ---
(In reply to Alex Deucher from comment #18)
> It's required to re-establish the DP link if you physically disconnect and
> reconnect an active display since DP requires link training while other
> digital links do not, otherwise you'd end up with a blank display after
> disconnecting and reconnecting a DP display.  It sounds like may have a
> problem with the hpd interrupts on your board.

Unfortunately it doesn't work as intended but only cause some side effect, at
least for my case. FYR my board is Sapphire HD5850 Toxic, and my monitor is
EIZO EV2336W.

> How are you turning it off in X vs console?  Are you physically powering the
> monitor off or triggering dpms (e.g., xset dpms force off)?

All "turning it off" mean physically powering it off. I even tried unplugging
the power today.

> Are you physically powering off the TV or do you mean dpms?
In the case that I found out the problem, I was nuking a disk in console, so I
physically powered off the TV after I ran the command. When I turn on my TV
again after a long time, I can't get back the display.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-04-08 17:16 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03  8:06 [Bug 71461] New: monitor doesn't get detected after boot bugzilla-daemon
2014-03-03 12:45 ` [Bug 71461] monitor doesn't get detected after boot or disconnection bugzilla-daemon
2014-03-03 12:47 ` bugzilla-daemon
2014-03-03 14:54 ` bugzilla-daemon
2014-03-03 15:22 ` bugzilla-daemon
2014-03-03 15:23 ` bugzilla-daemon
2014-03-03 15:25 ` bugzilla-daemon
2014-03-03 15:36 ` bugzilla-daemon
2014-03-03 15:41 ` bugzilla-daemon
2014-03-03 15:43 ` bugzilla-daemon
2014-03-03 17:16 ` bugzilla-daemon
2014-03-03 17:25 ` bugzilla-daemon
2014-03-11 17:07 ` bugzilla-daemon
2014-03-11 18:14 ` bugzilla-daemon
2014-03-12 17:10 ` bugzilla-daemon
2014-03-23 20:34 ` bugzilla-daemon
2014-03-23 20:54 ` bugzilla-daemon
2014-04-07 18:21 ` bugzilla-daemon
2014-04-07 18:41 ` bugzilla-daemon
2014-04-07 19:26 ` bugzilla-daemon
2014-04-08 17:16 ` bugzilla-daemon [this message]
2014-04-08 18:47 ` bugzilla-daemon
2014-04-08 19:15 ` bugzilla-daemon
2014-04-09  6:00 ` bugzilla-daemon
2014-04-09  6:10 ` bugzilla-daemon
2014-04-09  6:10 ` bugzilla-daemon
2014-04-09  6:12 ` bugzilla-daemon
2014-04-09  7:01 ` bugzilla-daemon
2014-04-09  7:07 ` bugzilla-daemon
2014-04-09 18:40 ` bugzilla-daemon
2014-04-09 18:53 ` bugzilla-daemon
2014-04-09 20:00 ` bugzilla-daemon
2014-04-12  2:14 ` bugzilla-daemon
2014-04-12  2:44 ` bugzilla-daemon
2015-10-30 23:34 ` 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-71461-2300-I8sufchCnG@https.bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox