From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108780] Missing "hainan_mc.bin" firmware reference.
Date: Sat, 17 Nov 2018 19:46:13 +0000 [thread overview]
Message-ID: <bug-108780-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108780
Bug ID: 108780
Summary: Missing "hainan_mc.bin" firmware reference.
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: code@progandy.de
Original report: https://bbs.archlinux.org/viewtopic.php?id=241913
In drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c, a MODULE_FIRMWARE entry for
"amdgpu/hainan_mc.bin" is missing, but gmc_v6_0_init_microcode() tries to load
it if chip_name is "hainan".
As a result, some initramfs generators fail to pick up the required firmware
from the module metadata and do not include it in the generated image. During
boot, amdgpu now fails to load the firmware.
[ 1.517399] amdgpu 0000:03:00.0: si_mc: Failed to load firmware
"amdgpu/hainan_mc.bin"
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2510 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-11-17 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 19:46 bugzilla-daemon [this message]
2018-11-19 16:34 ` [Bug 108780] Missing "hainan_mc.bin" firmware reference bugzilla-daemon
2019-11-19 9:04 ` 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-108780-502@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.