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