From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107072] 4k hdmi monitor stays black on kaveri [regression]
Date: Fri, 29 Jun 2018 19:49:19 +0000 [thread overview]
Message-ID: <bug-107072-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107072
Bug ID: 107072
Summary: 4k hdmi monitor stays black on kaveri [regression]
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: linuxhippy@gmail.com
After updating Fedora 28 on my Kaveri System (A8-7650K) with AMDGPU enabled
from 4.16.16 to 4.17.2 my 4K HDI display stays black (the FHD display connected
via HDMI continues to work as expected).
Please let me know what kind of information is required find the root cause.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2127 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
next reply other threads:[~2018-06-29 19:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 19:49 bugzilla-daemon [this message]
2018-06-29 19:50 ` [Bug 107072] 4k hdmi monitor stays black on kaveri [regression] bugzilla-daemon
2018-06-29 19:55 ` bugzilla-daemon
2018-06-29 19:55 ` bugzilla-daemon
2018-06-29 19:57 ` bugzilla-daemon
2018-06-29 20:15 ` bugzilla-daemon
2018-07-02 8:06 ` bugzilla-daemon
2018-07-05 13:07 ` bugzilla-daemon
2018-07-05 13:10 ` bugzilla-daemon
2018-08-14 19:24 ` bugzilla-daemon
2018-08-15 18:03 ` bugzilla-daemon
2018-08-15 18:07 ` bugzilla-daemon
2018-08-15 18:08 ` bugzilla-daemon
2018-08-15 18:11 ` bugzilla-daemon
2018-08-15 18:22 ` bugzilla-daemon
2019-11-19 8:42 ` 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-107072-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 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).