From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2
Date: Tue, 29 Aug 2017 16:35:26 +0000 [thread overview]
Message-ID: <bug-196791-2300-iq70Uzr8ru@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-196791-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=196791
--- Comment #10 from Walther Pelser (w.pelser@web.de) ---
(In reply to Alex Deucher from comment #8)
> The only reason the firmware would fail to load is if it's not available.
> From the log, it shows direct fw loading failed. Did you build radeon into
> your kernel rather than as a module? If so, you need to build the firmware
> into your kernel as well.
This is an argument, which belongs to my own kernel. I learned from
https://wiki.gentoo.org/wiki/Radeon that these 3 firmware files are needed to
be build-in in my own localyesconfig kernel. So far, I did not do so.
But i filed this bug, because I found an openSUSE kernel with the described
problems.
--
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:[~2017-08-29 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 16:17 [Bug 196791] New: load for radeon/RV71O_pfd.bin failed with error -2 bugzilla-daemon
2017-08-28 16:20 ` [Bug 196791] " bugzilla-daemon
2017-08-28 17:34 ` bugzilla-daemon
2017-08-28 17:36 ` bugzilla-daemon
2017-08-28 17:38 ` bugzilla-daemon
2017-08-28 18:20 ` bugzilla-daemon
2017-08-29 10:29 ` bugzilla-daemon
2017-08-29 10:35 ` bugzilla-daemon
2017-08-29 14:09 ` bugzilla-daemon
2017-08-29 15:15 ` bugzilla-daemon
2017-08-29 16:35 ` bugzilla-daemon [this message]
2017-08-29 18:29 ` 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-196791-2300-iq70Uzr8ru@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox