All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91202] Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors
Date: Sun, 28 Aug 2016 20:56:10 +0000	[thread overview]
Message-ID: <bug-91202-502-QrE3SVRpPS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91202-502@http.bugs.freedesktop.org/>


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

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

--- Comment #20 from jokeyrhyme@gmail.com ---
For a while there it looked like we might get the DAL work in Linux 4.9, but
now I'm wondering if this is more of a 4.10 or 4.11 thing.
- https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-Linux-4.9-First

It's actually a pretty exciting time for AMD GPUs on Linux, as it is right in
the middle of a massive overhaul. I purchased a Tonga specifically so I could
bear witness to this open-by-default turnaround for the AMD team.

And yeah, it's totally frustrating the multi-monitor is broken right now, but
at least we get re-clocking. Imagine how frustrating it must be for open-source
nVidia fans right now, with nVidia itself having long stymied the community
work in that area.

With my current setup, I have both monitors connected to my Intel GPU, and the
primary monitor also connected to the AMD one, with Intel being initialised by
EFI / BIOS first. In Linux, I switch the primary monitor to Intel, and for
Windows I switch it back to AMD. Not perfect of course, but this flow sort of
works for me.

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

[-- Attachment #1.2: Type: text/html, Size: 2146 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

  parent reply	other threads:[~2016-08-28 20:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  1:22 [Bug 91202] output to DVI-I is blank bugzilla-daemon
2015-07-03  1:23 ` bugzilla-daemon
2015-07-04 17:51 ` bugzilla-daemon
2015-07-25 18:47 ` bugzilla-daemon
2015-07-25 18:49 ` bugzilla-daemon
2015-07-25 18:50 ` bugzilla-daemon
2015-08-18 15:44 ` bugzilla-daemon
2015-11-07 18:01 ` bugzilla-daemon
2016-01-05 21:26 ` [Bug 91202] Output to DVI-I (or DVI-D) is blank on Tonga (R9 285 and 380X) with multiple monitors bugzilla-daemon
2016-01-06 11:26 ` bugzilla-daemon
2016-01-07 10:49 ` bugzilla-daemon
2016-01-07 12:12 ` bugzilla-daemon
2016-04-22 10:09 ` bugzilla-daemon
2016-04-22 10:18 ` bugzilla-daemon
2016-04-22 10:19 ` bugzilla-daemon
2016-05-09 17:36 ` bugzilla-daemon
2016-05-23 21:45 ` bugzilla-daemon
2016-06-03 14:42 ` bugzilla-daemon
2016-08-28 15:22 ` bugzilla-daemon
2016-08-28 18:14 ` bugzilla-daemon
2016-08-28 20:56 ` bugzilla-daemon [this message]
2016-08-28 21:52 ` bugzilla-daemon
2016-09-17 18:44 ` bugzilla-daemon
2016-09-26 11:08 ` bugzilla-daemon
2016-09-27 17:31 ` bugzilla-daemon
2016-11-14 23:03 ` bugzilla-daemon
2017-02-20  3:28 ` bugzilla-daemon
2017-02-21 11:25 ` bugzilla-daemon
2019-11-09  7:37 ` bugzilla-daemon
2019-11-19  8:06 ` 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-91202-502-QrE3SVRpPS@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.