From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lutomirski Date: Thu, 26 May 2011 14:12:26 +0000 Subject: Re: efifb not detected on Intel DQ67SW Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-fbdev@vger.kernel.org On Thu, May 26, 2011 at 9:56 AM, Peter Jones wrote: > On 05/26/2011 12:09 AM, Andrew Lutomirski wrote: >> On Wed, May 25, 2011 at 2:54 PM, Andrew Lutomirski wrote: >>> On Wed, May 25, 2011 at 2:32 PM, Matthew Garrett wrote: >>>> On Wed, May 25, 2011 at 02:21:17PM -0400, Andrew Lutomirski wrote: >>>> >>>>> Looking at the code, I'm a little confused how it's supposed to work. >>>>> AFAICT, unless there's a DMI match, then the driver will only load >>>>> ifthe boot code sets VIDEO_TYPE_EFI, but nothing sets that. >>>> >>>> grub should be setting that. >>> >>> It looks like grub-fedora (the git version, anyway) has a function >>> set_kernel_params that tries to do this. =A0Peter, the git tree claims >>> that you maintain it. =A0Are there any experiments you'd like me to do? >>> (Dumping boot_params, perhaps?) >> >> It's a bug in grub. =A0If I have a splashimage then efifb works. =A0If I >> don't, then efifb doesn't. =A0If I don't hear anything back soon, I'll >> file a bug against Fedora. > > That's expected, though I admit it's not the best thing ever. We're curre= ntly > working on not needing that bootloader at all any more, in favor of grub2, > which doesn't have this limitation. > >> FWIW, efifb seems really slow. > > It's a non-accelerated console. =A0Of course it's slow. Yes, but it's really really amazingly slow. It's so slow that merely enabling it doubles the time it takes to get i915 loaded. A one-liner to fix it is coming right now... --Andy