From: Peter Jones <pjones@redhat.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: efifb not detected on Intel DQ67SW
Date: Thu, 26 May 2011 13:56:58 +0000 [thread overview]
Message-ID: <4DDE5C2A.7050006@redhat.com> (raw)
In-Reply-To: <BANLkTikxX577VKmPRVGcp_Chj-udCf-KaQ@mail.gmail.com>
On 05/26/2011 12:09 AM, Andrew Lutomirski wrote:
> On Wed, May 25, 2011 at 2:54 PM, Andrew Lutomirski <luto@mit.edu> wrote:
>> On Wed, May 25, 2011 at 2:32 PM, Matthew Garrett <mjg@redhat.com> 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. Peter, the git tree claims
>> that you maintain it. Are there any experiments you'd like me to do?
>> (Dumping boot_params, perhaps?)
>
> It's a bug in grub. If I have a splashimage then efifb works. If I
> don't, then efifb doesn't. If 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 currently
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. Of course it's slow.
--
Peter
next prev parent reply other threads:[~2011-05-26 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 18:21 efifb not detected on Intel DQ67SW Andrew Lutomirski
2011-05-25 18:32 ` Matthew Garrett
2011-05-25 18:54 ` Andrew Lutomirski
2011-05-26 4:09 ` Andrew Lutomirski
2011-05-26 13:56 ` Peter Jones [this message]
2011-05-26 14:12 ` Andrew Lutomirski
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=4DDE5C2A.7050006@redhat.com \
--to=pjones@redhat.com \
--cc=linux-fbdev@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;
as well as URLs for NNTP newsgroup(s).