From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1ME7sW-0002A0-LN for mharc-grub-devel@gnu.org; Tue, 09 Jun 2009 16:25:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ME7sU-00028P-SZ for grub-devel@gnu.org; Tue, 09 Jun 2009 16:25:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ME7sP-00022Q-De for grub-devel@gnu.org; Tue, 09 Jun 2009 16:25:01 -0400 Received: from [199.232.76.173] (port=47761 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ME7sP-00022I-6d for grub-devel@gnu.org; Tue, 09 Jun 2009 16:24:57 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:51300) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ME7sO-0002fv-Lv for grub-devel@gnu.org; Tue, 09 Jun 2009 16:24:57 -0400 Received: from [85.180.43.154] (e180043154.adsl.alicedsl.de [85.180.43.154]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MKsym-1ME7sN24bN-000dAA; Tue, 09 Jun 2009 22:24:55 +0200 From: Felix Zielcke To: The development of GRUB 2 In-Reply-To: <1244067102.3407.51.camel@fz.local> References: <1244022215.3429.17.camel@fz.local> <1244062540.20653.11.camel@mj> <1244067102.3407.51.camel@fz.local> Content-Type: text/plain; charset="UTF-8" Date: Tue, 09 Jun 2009 22:24:54 +0200 Message-Id: <1244579094.3477.18.camel@fz.local> Mime-Version: 1.0 X-Mailer: Evolution 2.26.2 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V01U2FsdGVkX19P1TA6hpUX1YAducvsM2QDS7g07zyy4bod8QW cJMSt0abCCRElt1NMkwybEROHA0yHIPsYAE0Yh6ngHv7TyBzBo Vj8+Va4Yh+a7vPlsZ5jL73GLjW5VnQI X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: grub-mkconfig fails on every non i386-pc because of gfxterm/vbe X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jun 2009 20:25:03 -0000 Am Donnerstag, den 04.06.2009, 00:11 +0200 schrieb Felix Zielcke: > 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] > > >=20 > > > It fails with `No suitable backend could be found for gfxterm.' > > > The problem is that gfxterm is used when nothing is explicitly specif= ied > > > and the fonts were compiled, but the fails because vbe.mod only gets > > > compiled for i386-pc whereas gfxterm.mod gets compiled for every arch= es. > >=20 > > 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. > >=20 > > Or maybe Debian sets GRUB_TERMINAL_OUTPUT to gfxterm somewhere. >=20 > No, by default we don't set GRUB_TERMINAL_OUTPUT at all. >=20 > > > I suggest as Jordi to just change the `exit 1' to =C2=B4exit 0' and t= elling > > > the user that it falls back to native terminal: > >=20 > > I believe it's a wrong fix, as it would not prevent adding the gfxterm > > code to grub.cfg. >=20 > Yes it won't. It would only prevent it from completely failing if > gfxterm isn't avaible. >=20 > > 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. >=20 > So you would prefer something like the attached patch? > Though then we'll need to tell people to explicit enable gfxterm. Pavel? Seems like you missed my mail. --=20 Felix Zielcke