grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe


From: Felix Zielcke
Subject: Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe
Date: Wed, 22 Jul 2009 13:04:21 +0200

Am Donnerstag, den 11.06.2009, 18:09 +0200 schrieb Vladimir 'phcoder'
Serbinenko:
> On Thu, Jun 4, 2009 at 12:11 AM, Felix Zielcke<address@hidden> wrote:
> > 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.
> The correct solution would be to check the presence of graphical
> backend and base the default on it. Or even better is to make the
> default depend on platform. It would solve the situations in which
> video backend is available but known to cause problems

Pavel already wanted that gfxterm isn't anymore the default but didn't
replied yet to my other mail about it.

> >
> >> > 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
> >
> > _______________________________________________
> > Grub-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/grub-devel
> >
> >
> 
> 
> 


-- 
Felix Zielcke





reply via email to

[Prev in Thread] Current Thread [Next in Thread]