dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 10:35:29 +0000	[thread overview]
Message-ID: <bug-196791-2300-91ZMZGcGda@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 #7 from Walther Pelser (w.pelser@web.de) ---
(In reply to Takashi Iwai from comment #5)
> It doesn't matter what zypper says.  Simply check initrd content via
> lsinitrd.
> If the target firmware file is found there, it's OK.  If not, that's the
> problem.

As I said in my description kernel 4.13.0-rc2-1.gb545b87 was booting with out
any problems.
So my conclusion is, that radeon.ko has become broken in the meantime, and that
is. what dracut printed out for me.

-- 
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

  parent reply	other threads:[~2017-08-29 10: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 [this message]
2017-08-29 14:09 ` bugzilla-daemon
2017-08-29 15:15 ` bugzilla-daemon
2017-08-29 16:35 ` bugzilla-daemon
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-91ZMZGcGda@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