From: Paul Menzel <paulepanter@users.sourceforge.net>
To: grub-devel@gnu.org
Subject: Problems with loadfont and loading
Date: Mon, 11 Sep 2017 20:40:11 +0200 [thread overview]
Message-ID: <1505155211.1825.24.camel@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Dear GRUB folks,
Using coreboot with the GRUB payload, the font file is not found.
I build GRUB as a coreboot payload, but only tell the configuration
file in the memdisk to load the configuration file from the hard disk.
(root is the partition mounted to `/boot`.)
configfile /grub/grub.cfg
That file is generated by the operating system (`update-grub` from
Debian 9 (Stretch/stable)).
From the header configuration files, the Debian GRUB configuration file
contains the code below.
```
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
[…]
```
But `loadfont` uses the variable `prefix`, which differs between the
GRUB payload and GRUB in the MBR. So the font is not found on the hard
disk.
Is there a general solution for this problem? Can the header be
adapted, or `loadfont` be improved?
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
reply other threads:[~2017-09-11 18:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1505155211.1825.24.camel@users.sourceforge.net \
--to=paulepanter@users.sourceforge.net \
--cc=grub-devel@gnu.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).