From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Bruno Prémont'" <bonbons@linux-vserver.org>
Cc: <linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Subject: RE: X.org doesn't start with 3.14: [KMS] drm report modesetting isn't supported
Date: Wed, 2 Apr 2014 06:36:06 -0400 [thread overview]
Message-ID: <000701cf4e5f$5ac1be60$10453b20$@lucidpixels.com> (raw)
In-Reply-To: <20140401222152.10af8cdf@neptune.home>
> -----Original Message-----
> From: Bruno Prémont [mailto:bonbons@linux-vserver.org]
> Sent: Tuesday, April 01, 2014 4:22 PM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org; dri-devel@lists.freedesktop.org
> Subject: Re: X.org doesn't start with 3.14: [KMS] drm report modesetting
isn't
> supported
>
> Hi Justin,
>
> CC-ing dri-devel as more KMS/radeon people will see it there.
[ .. ]
My issue:
[ 0.623399] [drm] Loading CEDAR Microcode
[ 0.623461] r600_cp: Failed to load firmware "radeon/CEDAR_pfp.bin"
[ 0.623517] [drm:evergreen_init] *ERROR* Failed to load firmware!
[ 0.623573] radeon 0000:05:00.0: Fatal error during GPU init
[ 0.623629] [drm] radeon: finishing device.
Somehow this option became unselected in my kernel configuration, although I
almost always usually run make oldconfig-- so I am not sure how it happened:
[ ] Include in-kernel firmware blobs in kernel binary
Back to normal as per below:
-*- Userspace firmware loading support
[*] Include in-kernel firmware blobs in kernel binary
(radeon/CEDAR_me.bin radeon/CEDAR_pfp.bin radeon/CEDAR_rlc.bin
radeon/CYPRESS_uvd.bin)
External firmware (/lib/firmware) Firmware blobs root directory
# pwd
/lib/firmware/radeon
# ls -l *CEDAR*pfp*
-rw-r--r-- 1 root root 4480 Feb 22 16:50 CEDAR_pfp.bin
#
[ .. ]
Thank you && sorry for the noise!
Justin.
prev parent reply other threads:[~2014-04-02 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 22:27 X.org doesn't start with 3.14: [KMS] drm report modesetting isn't supported Justin Piszcz
2014-04-01 20:21 ` Bruno Prémont
2014-04-02 10:36 ` Justin Piszcz [this message]
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='000701cf4e5f$5ac1be60$10453b20$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=bonbons@linux-vserver.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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