All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 11 Jul 2019 09:52:55 +0000	[thread overview]
Message-ID: <bug-109206-502-P8GQAHBomH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109206-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109206

--- Comment #53 from Ondrej Lang <ondrej@lang.sk> ---
According to the linux kernel 5.2 changelog
(https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2), the fix for the
DMCU firmware issue on raven1 platform is included in that release.

I went ahead and tested this and can confirm that I was able to boot without a
blank screen into my machine with kernel 5.2 without needing to use the
workaround.

I tested with:
1.) re-installed latest linux-firmware package
2.) installed kernel 5.2
3.) re-generated the initramfs
4.) booted into linux using kernel 5.2 and had no blank screen, dmesg output is
clean with no erros for amdgpu

Tested on:
HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.21 04/29/2019

I guess if someone else can confirm my findings, maybe on different raven1
hardware, this ticket can be closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1846 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

  parent reply	other threads:[~2019-07-11  9:52 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
2019-07-11  9:52 ` bugzilla-daemon [this message]
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-P8GQAHBomH@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.