From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U
Date: Tue, 02 Jul 2019 13:41:52 +0000 [thread overview]
Message-ID: <bug-109206-502-RUONGmfNbW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109206-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #52 from Talha Khan <evo8800@gmail.com> ---
(In reply to Ondrej Lang from comment #50)
> I tested this yesterday with kernel 5.1.8 and if the file raven_dmcu.bin is
> present in the /lib/firmware/amdgpu/ folder when you are updating the kernel
> (or manually rebuilding the initramfs), the computer will boot with a blank
> screen next time.
>
> There are 2 pieces to this. The linux-firmware package provides the binary
> files (i.e. the raven_dmcu.bin) so every time this package gets updated, you
> should rename/move the file and rebuild the initramfs. The linux-firmware
> updates are not as frequent as the kernel updates so if you do the
> workaround, you might go through several kernel updates without issues, but
> once linux-firmware updates, you have to repeat the workaround...
>
> All the patch in the kernel will do is to ignore the raven_dmcu.bin file
> automatically (for raven 1 cpus) when building the initramfs so you don't
> have to rename/move it every time linux-firmware updates.
You're right, I had updated to 5.1.15 and it seemed the firmware files were
updated as well. I then had to perform the workaround in order to boot into the
system.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2245 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 prev parent reply other threads:[~2019-07-02 13:41 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 17:20 [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U bugzilla-daemon
2019-01-01 17:25 ` bugzilla-daemon
2019-01-04 15:08 ` bugzilla-daemon
2019-01-04 21:59 ` bugzilla-daemon
2019-01-04 22:00 ` bugzilla-daemon
2019-01-14 14:17 ` bugzilla-daemon
2019-01-29 13:41 ` bugzilla-daemon
2019-01-31 21:35 ` bugzilla-daemon
2019-02-02 11:47 ` bugzilla-daemon
2019-02-02 16:32 ` bugzilla-daemon
2019-02-08 15:21 ` bugzilla-daemon
2019-02-13 1:48 ` bugzilla-daemon
2019-02-19 5:38 ` bugzilla-daemon
2019-02-19 11:26 ` bugzilla-daemon
2019-02-19 19:27 ` bugzilla-daemon
2019-02-19 20:36 ` bugzilla-daemon
2019-02-20 5:06 ` bugzilla-daemon
2019-02-20 21:07 ` bugzilla-daemon
2019-02-22 17:33 ` bugzilla-daemon
2019-02-22 21:27 ` bugzilla-daemon
2019-03-03 20:22 ` bugzilla-daemon
2019-03-05 19:24 ` bugzilla-daemon
2019-03-07 6:08 ` bugzilla-daemon
2019-03-07 6:12 ` bugzilla-daemon
2019-03-07 6:18 ` bugzilla-daemon
2019-03-07 11:07 ` bugzilla-daemon
2019-03-12 4:41 ` bugzilla-daemon
2019-03-12 15:20 ` bugzilla-daemon
2019-04-04 14:13 ` bugzilla-daemon
2019-04-04 18:27 ` bugzilla-daemon
2019-04-04 18:35 ` bugzilla-daemon
2019-04-08 13:18 ` bugzilla-daemon
2019-04-08 13:18 ` bugzilla-daemon
2019-04-08 18:52 ` bugzilla-daemon
2019-04-09 17:45 ` bugzilla-daemon
2019-04-14 2:29 ` bugzilla-daemon
2019-04-15 13:57 ` bugzilla-daemon
2019-04-25 15:55 ` bugzilla-daemon
2019-04-25 19:10 ` bugzilla-daemon
2019-04-25 23:01 ` bugzilla-daemon
2019-05-01 21:05 ` bugzilla-daemon
2019-05-02 3:17 ` bugzilla-daemon
2019-05-02 6:36 ` bugzilla-daemon
2019-05-03 20:20 ` bugzilla-daemon
2019-05-22 8:42 ` bugzilla-daemon
2019-05-27 16:43 ` bugzilla-daemon
2019-06-06 15:13 ` bugzilla-daemon
2019-06-07 9:15 ` bugzilla-daemon
2019-06-07 13:52 ` bugzilla-daemon
2019-06-11 16:56 ` bugzilla-daemon
2019-06-12 9:47 ` bugzilla-daemon
2019-06-15 11:57 ` bugzilla-daemon
2019-07-02 13:41 ` bugzilla-daemon [this message]
2019-07-11 9:52 ` bugzilla-daemon
2019-07-12 3:39 ` bugzilla-daemon
2019-07-12 7:49 ` bugzilla-daemon
2019-07-12 13:10 ` bugzilla-daemon
2019-07-12 15:24 ` bugzilla-daemon
2019-07-12 23:09 ` bugzilla-daemon
2019-07-13 9:41 ` bugzilla-daemon
2019-07-14 20:21 ` Mihai
2019-07-14 20:22 ` bugzilla-daemon
2019-07-18 14:10 ` bugzilla-daemon
2019-07-18 18:17 ` bugzilla-daemon
2019-07-29 14:02 ` bugzilla-daemon
2019-11-14 7:38 ` bugzilla-daemon
2019-11-14 7:41 ` [Bug 109206] Kernel 5.3.11 and onward amdgpu fails to load firmware on Raven Ridge bugzilla-daemon
2019-11-14 13:58 ` bugzilla-daemon
2019-11-14 14:51 ` bugzilla-daemon
2019-11-14 14:51 ` [Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U bugzilla-daemon
2019-11-14 16:58 ` bugzilla-daemon
2019-11-16 12:27 ` 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-109206-502-RUONGmfNbW@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.