[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <000701cf4e5f$5ac1be60$10453b20$@lucidpixels.com>
Date: Wed, 2 Apr 2014 06:36:06 -0400
From: "Justin Piszcz" <jpiszcz@...idpixels.com>
To: 'Bruno Prémont' <bonbons@...ux-vserver.org>
Cc: <linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>
Subject: RE: X.org doesn't start with 3.14: [KMS] drm report modesetting isn't supported
> -----Original Message-----
> From: Bruno Prémont [mailto:bonbons@...ux-vserver.org]
> Sent: Tuesday, April 01, 2014 4:22 PM
> To: Justin Piszcz
> Cc: linux-kernel@...r.kernel.org; dri-devel@...ts.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists