From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111261] Screen remains black when 2 monitors are connected
Date: Tue, 30 Jul 2019 13:56:15 +0000 [thread overview]
Message-ID: <bug-111261-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111261
Bug ID: 111261
Summary: Screen remains black when 2 monitors are connected
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu-pro
Assignee: dri-devel@lists.freedesktop.org
Reporter: fabstz-it@yahoo.fr
With 2 monitors (one on VGA, one on DVI-D), screen turns black while loading
system in console
When only 1 monitor connected to VGA everything is fine.
There is no problem with kernel 5.2 or with amdpgu-dkms 19.10 on debian buster
(linux 4.19)
It happens only with amdpgu-dkms 19.20 or 19.30 (on debian buster - kernel
4.19)
For 19.20 I applied my patch from
https://bugs.freedesktop.org/show_bug.cgi?id=111103, which is merely the same
as the code in 19.30
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2523 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-07-30 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 13:56 bugzilla-daemon [this message]
2019-08-18 8:04 ` [Bug 111261] Screen remains black when 2 monitors are connected bugzilla-daemon
2019-08-19 13:18 ` bugzilla-daemon
2019-08-19 14:17 ` bugzilla-daemon
2019-08-19 14:30 ` bugzilla-daemon
2019-08-19 15:29 ` bugzilla-daemon
2019-08-20 10:43 ` bugzilla-daemon
2019-11-19 8:00 ` 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-111261-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