From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 205521] 5.3.11 update broke AMDGPU Raven Ridge
Date: Thu, 14 Nov 2019 13:56:16 +0000 [thread overview]
Message-ID: <bug-205521-2300-usCNi1kNRc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205521-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205521
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #3 from Alex Deucher (alexdeucher@gmail.com) ---
(In reply to Luya Tshimbalanga from comment #0)
>
> nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Direct firmware load for
> amdgpu/raven_gpu_info.bin failed with error -2
> nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Failed to load gpu_info
> firmware "amdgpu/raven_gpu_info.bin"
> nov 13 13:53:55 kernel: amdgpu 0000:03:00.0: Fatal error during GPU init
The kernel is not able to find the firmware image. If you are using an initrd,
please make sure to includes the firmwares in the initrd. If you are building
the diver into the kernel, you need to build the firmware into the kernel as
well.
--
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:[~2019-11-14 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 6:15 [Bug 205521] New: 5.3.11 update broke AMDGPU Raven Ridge bugzilla-daemon
2019-11-14 6:16 ` [Bug 205521] " bugzilla-daemon
2019-11-14 6:16 ` bugzilla-daemon
2019-11-14 7:40 ` bugzilla-daemon
2019-11-14 13:56 ` bugzilla-daemon [this message]
2019-11-14 16:58 ` bugzilla-daemon
2019-11-15 16:07 ` 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-205521-2300-usCNi1kNRc@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.