From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198513] New: [DRM] amdgpu fails to load firmware on boot
Date: Fri, 19 Jan 2018 03:41:12 +0000 [thread overview]
Message-ID: <bug-198513-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=198513
Bug ID: 198513
Summary: [DRM] amdgpu fails to load firmware on boot
Product: Drivers
Version: 2.5
Kernel Version: 4.15rc7.git4.1 and above
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: m.mcnutt@gmail.com
Regression: No
on Fedora kernel 4.15rc7git4.1 and above with R9 NANO (Fiji) GPU dmesg shows a
failure to load the firmware. cloned the latest firmware from
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
still fails to load.
[ 2.423859] amdgpu 0000:26:00.0: Direct firmware load for
amdgpu/fiji_pfp.bin failed with erro
r -2
[ 2.423860] amdgpu 0000:26:00.0: gfx8: Failed to load firmware
"amdgpu/fiji_pfp.bin"
[ 2.423897] [drm:gfx_v8_0_sw_init [amdgpu]] *ERROR* Failed to load gfx
firmware!
[ 2.423924] [drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block
<gfx_v8_0> failed -2
[ 2.423926] amdgpu 0000:26:00.0: amdgpu_init failed
dropping back to 4.15rc7git0.1 and all loads correctly, no longer drops back to
llvmpipe as a fallback.
--
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 reply other threads:[~2018-01-19 3:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 3:41 bugzilla-daemon [this message]
2018-01-19 3:42 ` [Bug 198513] [DRM] amdgpu fails to load firmware on boot bugzilla-daemon
2018-01-19 7:16 ` bugzilla-daemon
2018-01-19 11:20 ` bugzilla-daemon
2018-01-19 11:21 ` 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-198513-2300@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.