From: Matthias Lange <matthias.lange@kernkonzept.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: phcoder@gmail.com, nd@arm.com, fedora.dm0@gmail.com
Subject: Re: About text mode on EFI when booting Linux
Date: Thu, 9 Nov 2017 11:43:17 +0100 [thread overview]
Message-ID: <20171109104317.GA30899@triton> (raw)
In-Reply-To: <20171109094950.GA19652@arm.com>
Hi,
On 2017-1109 at 17:49:53 +0800, Dennis Chen wrote:
> Hi Vladimir,
>
> We encounter an error message "no suitable video mode found" when
> booting a VM on i386 platform. Though I think this is not a big problem,
> but the LinuxKit guys(we use grub2 in LinuxKit project) have some
> concerns about this error message, so I submit a patch[1] try to
> eliminate this message. Would you please take a look at that patch?
>
> I also dig into the commit logs of the grub2 git tree, and found below
> commit:
>
[...]
>
> I am very curious about the context/background of this commit here, what's
> the reason leads us not to accept a text modes on EFI when booting Linux?
it appears that (U)EFI dos not feature any text services. See also this thread
[1] from the help-grub mailing list.
As far as I have understood things, UEFI has the "Console I/O Protocol" API
which can be used to output to a console without caring about what the console
actually is (serial port or something). To output something on the screen the
"Graphics Output Protocol" is used which doesn't support any text mode.
Best,
Matthias.
[1] https://lists.gnu.org/archive/html/help-grub/2011-12/msg00023.html
> [1] https://lists.gnu.org/archive/html/grub-devel/2017-10/msg00031.html
>
> Thanks,
> Dennis
prev parent reply other threads:[~2017-11-09 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 9:49 About text mode on EFI when booting Linux Dennis Chen
2017-11-09 10:43 ` Matthias Lange [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=20171109104317.GA30899@triton \
--to=matthias.lange@kernkonzept.com \
--cc=fedora.dm0@gmail.com \
--cc=grub-devel@gnu.org \
--cc=nd@arm.com \
--cc=phcoder@gmail.com \
/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).