All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98324] amd-staging-4.7: problems with unblanking displays when monitors are switched off
Date: Wed, 19 Oct 2016 17:23:32 +0000	[thread overview]
Message-ID: <bug-98324-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1403 bytes --]

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

            Bug ID: 98324
           Summary: amd-staging-4.7: problems with unblanking displays
                    when monitors are switched off
           Product: DRI
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: bugspam@moreofthesa.me.uk

Created attachment 127405
  --> https://bugs.freedesktop.org/attachment.cgi?id=127405&action=edit
Kernel log extract, showing the unblanking failure.

Setup: RX 470 with two monitors attached – one via DVI-and one via HDMI. (Both
are AOC monitors.)

* Ensure that outputs are blanked (via xset, time-out or similar).
* Switch off the monitors.
* Unblank the outputs.
* Switch on the monitors.

Invariably, in this situation, the DVI-connected monitor is unblanked and
displaying what it should be, but the HDMI-connected monitor is receiving no
signal (or at least nothing to display) and is therefore displaying nothing.

The HDMI-connected monitor can be restored by using xrandr to change mode or by
blanking and unblanking – so long as it's switched on while doing so.

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

[-- Attachment #1.2: Type: text/html, Size: 2905 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-10-19 17:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 17:23 bugzilla-daemon [this message]
2016-10-19 17:34 ` [Bug 98324] amd-staging-4.7: problems with unblanking displays when monitors are switched off bugzilla-daemon
2017-08-20 23:23 ` bugzilla-daemon
2017-08-22  6:43 ` [Bug 98324] [DC] " bugzilla-daemon
2017-08-22 14:54 ` bugzilla-daemon
2017-08-22 14:56 ` bugzilla-daemon
2017-08-22 14:58 ` bugzilla-daemon
2017-08-22 22:34 ` bugzilla-daemon
2017-08-23  1:12 ` bugzilla-daemon
2017-09-14 15:32 ` bugzilla-daemon
2017-09-28 13:02 ` bugzilla-daemon
2017-10-01 13:11 ` bugzilla-daemon
2018-05-03 20:51 ` bugzilla-daemon
2018-05-03 20:52 ` bugzilla-daemon
2018-05-05  0:32 ` bugzilla-daemon
2018-06-16 21:40 ` bugzilla-daemon
2019-11-19  8: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-98324-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 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.