> > Well, 80x25 is the only text mode which must be supported by the
> > firmware. Supporting larger modes is optional.
> >
> > I think the firmware is also free to choose the default text mode,
> > and the implementations I've seen so far seem to be conservative
> > and use 80x25 or 80x50 by def
On Tue, 10 May 2022 13:57:08 +0200
Gerd Hoffmann wrote:
> On Fri, May 06, 2022 at 07:59:15PM -0500, Glenn Washburn wrote:
> > Hi Gerd,
> >
> > Thanks for taking a look at the patch.
> >
> > On Fri, 6 May 2022 12:39:52 +0200
> > Gerd Hoffmann wrote:
> >
> > > Hi,
> > >
> > > > On some buggy
On Fri, May 06, 2022 at 07:59:15PM -0500, Glenn Washburn wrote:
> Hi Gerd,
>
> Thanks for taking a look at the patch.
>
> On Fri, 6 May 2022 12:39:52 +0200
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > > On some buggy EFI firmwares, GRUB is started with the console resolution
> > > set to the max
Hi Gerd,
Thanks for taking a look at the patch.
On Fri, 6 May 2022 12:39:52 +0200
Gerd Hoffmann wrote:
> Hi,
>
> > On some buggy EFI firmwares, GRUB is started with the console resolution
> > set to the maximum but the output console EFI object has the mode set as
> > 0, which is the minimum
Hi,
> On some buggy EFI firmwares, GRUB is started with the console resolution
> set to the maximum but the output console EFI object has the mode set as
> 0, which is the minimum supported mode of 80x25 characters. This causes
> strange behavior at the GRUB shell where output can fill the scree
On some buggy EFI firmwares, GRUB is started with the console resolution
set to the maximum but the output console EFI object has the mode set as
0, which is the minimum supported mode of 80x25 characters. This causes
strange behavior at the GRUB shell where output can fill the screen, but
the prom
