From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208573] Black screen on boot if two displays plugged in with NAVI 10
Date: Mon, 10 Aug 2020 12:06:29 +0000 [thread overview]
Message-ID: <bug-208573-2300-TuPRLVf3K7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208573-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208573
--- Comment #6 from Thomas Langkamp (thomas.langkamp@medicalschool-hamburg.de) ---
(In reply to Thomas Langkamp from comment #5)
> Created attachment 290817 [details]
> reproducable error messages after suspend, then reboot
>
> This error message is reproducable if I boot
> - with 1 display
> - on KDE connect second display
> - suspend, then wakeup (both screens work normal until this point)
> - then reboot => error message, then black screen on one and green screen on
> secondary display.
>
> Because my Mainboard got a new Bios I tried that with no effect. But I
> realized, that I get the black screen only if I dial in the 3200 Mhz XMP
> Profile of my RAM. If not - there is no black screen with 2 displays on the
> new BIOS. On the old BIOS XMP Profile or not made no difference. Thus the
> mainboard may be part of the problem.
Still, Mainboard being part of the problem or not - all was fine til I switched
the Fury X to the 5700 XT (first an ASROCK, now a Gigabyte one).
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-10 12:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 18:36 [Bug 208573] New: Black screen on boot if two displays plugged in with NAVI 10 bugzilla-daemon
2020-07-15 18:50 ` [Bug 208573] " bugzilla-daemon
2020-07-15 19:01 ` bugzilla-daemon
2020-07-15 19:01 ` bugzilla-daemon
2020-07-16 17:07 ` bugzilla-daemon
2020-08-10 11:46 ` bugzilla-daemon
2020-08-10 11:47 ` bugzilla-daemon
2020-08-10 12:06 ` bugzilla-daemon [this message]
2020-08-10 12:10 ` bugzilla-daemon
2020-08-10 14:33 ` bugzilla-daemon
2020-08-10 15:55 ` bugzilla-daemon
2020-08-10 20:38 ` bugzilla-daemon
2020-08-10 21:14 ` bugzilla-daemon
2020-09-03 6:06 ` bugzilla-daemon
2021-05-23 2:34 ` bugzilla-daemon
2021-05-24 18:03 ` 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-208573-2300-TuPRLVf3K7@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;
as well as URLs for NNTP newsgroup(s).