From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe
Date: Thu, 04 Jun 2009 00:11:42 +0200 [thread overview]
Message-ID: <1244067102.3407.51.camel@fz.local> (raw)
In-Reply-To: <1244062540.20653.11.camel@mj>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
Am Mittwoch, den 03.06.2009, 16:55 -0400 schrieb Pavel Roskin:
> On Wed, 2009-06-03 at 11:43 +0200, Felix Zielcke wrote:
> > I wonder why nobody on this list noticed this yet.
> > Jordi reported this already on Debian a while ago [0]
> >
> > It fails with `No suitable backend could be found for gfxterm.'
> > The problem is that gfxterm is used when nothing is explicitly specified
> > and the fonts were compiled, but the fails because vbe.mod only gets
> > compiled for i386-pc whereas gfxterm.mod gets compiled for every arches.
>
> It looks like a conflict between grub-mkconfig and 00_header.
> grub-mkconfig sets GRUB_TERMINAL_OUTPUT to gfxterm because gfxterm.mod
> is present, but 00_header refuses to use it because vbe.mod is absent.
>
> Or maybe Debian sets GRUB_TERMINAL_OUTPUT to gfxterm somewhere.
No, by default we don't set GRUB_TERMINAL_OUTPUT at all.
> > I suggest as Jordi to just change the `exit 1' to ´exit 0' and telling
> > the user that it falls back to native terminal:
>
> I believe it's a wrong fix, as it would not prevent adding the gfxterm
> code to grub.cfg.
Yes it won't. It would only prevent it from completely failing if
gfxterm isn't avaible.
> I believe the fix belongs to grub-mkconfig (if it's not a Debian
> specific issue). Setting defaults in grub-mkconfig should be done very
> carefully, as the numbered scripts treat those defaults as explicit
> requests by the user.
So you would prefer something like the attached patch?
Though then we'll need to tell people to explicit enable gfxterm.
--
Felix Zielcke
[-- Attachment #2: mkconfig-gfxterm.patch --]
[-- Type: text/x-patch, Size: 754 bytes --]
2009-06-03 Felix Zielcke <fzielcke@z-51.de>
* util/grub-mkconfig.in: Don't use gfxterm by default if not
explicit specified by the user.
diff --git a/util/grub-mkconfig.in b/util/grub-mkconfig.in
index ff92590..8f84074 100644
--- a/util/grub-mkconfig.in
+++ b/util/grub-mkconfig.in
@@ -137,13 +137,7 @@ if [ "x${GRUB_TERMINAL}" != "x" ] ; then
fi
case x${GRUB_TERMINAL_OUTPUT} in
- x)
- # If this platform supports gfxterm, try to use it.
- if test -e ${grub_prefix}/gfxterm.mod ; then
- GRUB_TERMINAL_OUTPUT=gfxterm
- fi
- ;;
- xconsole | xserial | xofconsole | xgfxterm) ;;
+ x | xconsole | xserial | xofconsole | xgfxterm) ;;
*) echo "Invalid output terminal \"${GRUB_TERMINAL_OUTPUT}\"" >&2 ; exit 1 ;;
esac
next prev parent reply other threads:[~2009-06-03 22:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 9:43 grub-mkconfig fails on every non i386-pc because of gfxterm/vbe Felix Zielcke
2009-06-03 20:55 ` Pavel Roskin
2009-06-03 22:11 ` Felix Zielcke [this message]
2009-06-09 20:24 ` Felix Zielcke
2009-06-12 1:09 ` Pavel Roskin
2009-08-14 6:44 ` Felix Zielcke
2009-08-18 17:58 ` Pavel Roskin
2009-08-18 18:09 ` Felix Zielcke
2009-08-18 18:25 ` Michal Suchanek
2009-06-11 16:09 ` Vladimir 'phcoder' Serbinenko
2009-07-22 11:04 ` Felix Zielcke
2009-08-18 17:44 ` Pavel Roskin
2009-08-18 17:53 ` Vladimir 'phcoder' Serbinenko
2009-08-18 18:11 ` Pavel Roskin
2009-08-19 15:18 ` Robert Millan
2009-08-20 22:18 ` Pavel Roskin
2009-08-20 22:45 ` Vladimir 'phcoder' Serbinenko
2009-08-21 11:14 ` Michal Suchanek
2009-08-23 8:22 ` Felix Zielcke
2009-08-23 11:03 ` Robert Millan
2009-08-25 19:35 ` Robert Millan
2009-08-25 19:47 ` Felix Zielcke
2009-09-11 21:54 ` Pavel Roskin
2009-09-12 12:58 ` Robert Millan
2009-09-12 13:17 ` Felix Zielcke
2009-09-12 20:44 ` Michal Suchanek
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=1244067102.3407.51.camel@fz.local \
--to=fzielcke@z-51.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.