help-grub
[Top][All Lists]
Advanced

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

Re: Grub hangs if no key is pressed


From: Jürgen Bausa
Subject: Re: Grub hangs if no key is pressed
Date: Sat, 30 Dec 2017 13:10:40 +0100
User-agent: KMail/5.2.3 (Linux/4.9.0-3-amd64; KDE/5.28.0; x86_64; ; )

I just checked it. 1920x1080 is listed with 8, 16 and 32 bit depth.

Juergen

Am Freitag, 29. Dezember 2017, 17:19:38 CET schrieb Randy Goldenberg:
> You mention that grub makes use of your laptop's native resolution,
> 1920x1080. Have you confirmed that that resolution is supported by the VESA
> BIOS video driver?  To do so, get a grub command prompt by typing "c" at
> the grub menu display, then type:
> 
> set pager=1
> vbeinfo
> 
> HTH,
> 
> Randy
> 
> On Friday December 29, 2017, Jürgen Bausa wrote:
> >Using
> >
> >     GRUB_GFXMODE=1920x1080
> >
> >I have the same behaviour as without the option: grub is slow and hangs
> >after "loading initial ramdisk" if no key is pressed.
> >
> >In the meantime I found out that grub sometimes (not often, maybe 1 of 10)
> >hangs with 1280x1024. I am now using 1024x768, which seems to work
> >reliable.
> >
> >My system uses legacy mode, not uefi. I dont know if this is related.
> >
> >Juergen
> >
> >> Did you try with GRUB_GFXMODE=1920x1080 ?
> >> 
> >> Am Donnerstag, 28. Dezember 2017, 20:06:41 CET schrieben Sie:
> >>> Some additional information and a workaround I found:
> >>> 
> >>> Grub is extremely slow. When I press a key, it takes more than 2 seconds
> >>> before I see the result on the screen. Another information that might be
> >>> important is that the Laptop has a high resolution (1920 x 1080) and
> >>> grub
> >>> makes use of this.
> >>> 
> >>> The workaround I found is to either use a textual grub screen
> >>> 
> >>>   GRUB_TERMINAL=console
> >>>   GRUB_GFXPAYLOAD_LINUX=text
> >>> 
> >>> or to use a fixed and lower resolution like
> >>> 
> >>>   GRUB_GFXMODE=800x600
> >>> 
> >>> or
> >>> 
> >>>   GRUB_GFXMODE=1024x768
> >>> 
> >>> Setting either a textual screen or the fixed resolution solves the
> >>> problem:
> >>> grub is more responsive and starting the default kernel via timeout
> >>> works.
> >>> 
> >>> As this is only a workaround and grub should work without it, I am still
> >>> interested in a solution.
> >>> 
> >>> Regards,
> >>> 
> >>> Juergen
> >>> 
> >>> Am Mittwoch, 27. Dezember 2017, 22:22:16 CET schrieben Sie:
> >>> >> I have a Xiaomi Air 12 with deiban stretch (amd64) installed. Grub
> >>> >> (2.02~beta3-5) works in principle but I found out, that it hangs very
> >>> >> often, if no key is pressed (timeout for selecting the boot option).
> >>> >> 
> >>> >> In this case the default option is correctly selected. Then, the
> >>> >> screen
> >
> >is
> >
> >>> >> cleared, the name of the selected kernel is displayed and the message
> >>> >> "loading initial ram disk". Then the screen gets black and nothing
> >
> >happens
> >
> >>> >> anymore. It seems that the system is never started (nothing is
> >>> >> written
> >
> >to
> >
> >>> >> the logs).
> >>> >> 
> >>> >> If I select the default boot option by pressing <Enter>> on the first
> >
> >grub
> >
> >>> >> screen, everything works fine and the system boots up normally.
> >>> >> 
> >>> >> I have no idea how to debug this. Is there a debug option for grub
> >>> >> that
> >>> >> enables some output on the screen?
> >>> >> 
> >>> >> Any other hints?
> >>> >> 
> >>> >> Regards,
> >>> >> 
> >>> >> Jürgen
> >
> >_______________________________________________
> >Help-grub mailing list
> >address@hidden
> >https://lists.gnu.org/mailman/listinfo/help-grub





reply via email to

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