From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210849] Black screen after resume from long suspend. Open/Close lid. AMDGPU
Date: Sun, 27 Dec 2020 03:03:20 +0000 [thread overview]
Message-ID: <bug-210849-2300-qGk70k4pF2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210849-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210849
JerryD (jvdelisle@charter.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle@charter.net
--- Comment #5 from JerryD (jvdelisle@charter.net) ---
There is an old bug report that has been closed related to
/usr/lib/firmware/amdgpu/raven_dmcu.bin. This file was being incorrectly
loaded or has a probelm. To correct this, I renamed the file to
raven_dmcu.bin.old so that it would not load. The problem would return every
time firmware updates would come through that supplied a new raven_dmcu.bin.
I had no problems until recently when the kernel was bumped from
5.8.18-200.fc32.x86_64 to the first instance of 5.9.
The previous fix was accomplished y uninstalling the kernel, rename the
troublesome file, and then reintall the kernel.
I took another look today and see there is a new raven_dmcu.bin so I will
repeat the procedure again. It may not be the same problem, but I will give it
a try.
--
You may reply to this email to add a comment.
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-12-27 3:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 11:15 [Bug 210849] New: Black screen after resume from long suspend. Open/Close lid. AMDGPU bugzilla-daemon
2020-12-22 11:18 ` [Bug 210849] " bugzilla-daemon
2020-12-22 11:18 ` bugzilla-daemon
2020-12-22 11:20 ` bugzilla-daemon
2020-12-22 11:25 ` bugzilla-daemon
2020-12-22 11:28 ` bugzilla-daemon
2020-12-23 18:36 ` bugzilla-daemon
2020-12-27 3:03 ` bugzilla-daemon [this message]
2020-12-27 3:31 ` bugzilla-daemon
2020-12-30 20:53 ` bugzilla-daemon
2021-01-01 18:04 ` bugzilla-daemon
2021-01-05 20:43 ` bugzilla-daemon
2021-02-05 4:35 ` bugzilla-daemon
2021-02-05 15:40 ` bugzilla-daemon
2021-02-05 17:46 ` bugzilla-daemon
2021-02-05 18:37 ` bugzilla-daemon
2021-02-05 19:01 ` bugzilla-daemon
2021-02-06 16:52 ` bugzilla-daemon
2021-02-09 4:40 ` bugzilla-daemon
2021-02-13 1:30 ` bugzilla-daemon
2021-03-08 3:01 ` 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-210849-2300-qGk70k4pF2@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 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.