Bug 468865

Summary:	Where did my grub splash screen go?
Product:	[Fedora] Fedora	Reporter:	Andrew Cagney <cagney>
Component:	grub	Assignee:	Peter Jones <pjones>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10	CC:	ebachalo, lex.lists, pjones, s.adam, wwoods
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-02 16:09:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andrew Cagney 2008-10-28 14:20:29 UTC

(this probably isn't grub but grub does make for a good starting point, anaconda? :-)

When F-10 boots I don't see some sort of initial grub splash screen at which I know I can hit the space-bar and get to the menu to select/edit the kernel and/or boot parameters.

While it turned out that just repeatedly tapping the space-bar as the machine goes through the boot process will bring up the menu, that doesn't exactly give one warm fuzzies - hey tap the space-bar when the screen goes blank ... :-)

The machine was installed using the beta live cd [usb].

Comment 1 Will Woods 2008-10-28 17:27:48 UTC

You can hit/hold a key at boot (holding Shift or Ctrl works well) to bring up the GRUB menu. This is the expected behavior - see http://fedoraproject.org/wiki/Features/BetterStartup for details.

Yes, it will be in the release notes.

Comment 2 Andrew Cagney 2008-10-30 17:26:56 UTC

(In reply to comment #1)
> You can hit/hold a key at boot (holding Shift or Ctrl works well) to bring up
> the GRUB menu. This is the expected behavior - see
> http://fedoraproject.org/wiki/Features/BetterStartup for details.
> 
> Yes, it will be in the release notes.

Can I plead for this new boot process to display a message indicating that this is possible?

Not making this clear is, from my point of view, a usability problem - the only way for a user to "obviously" know that CNTRL can be hit is for there to be a message indicating such.  Further, I think addressing it will go a long way towards smoothing out the transition to this new way.  As a user I don't care that the boot process has changed radically;  however, I do think it is reasonable for the new process to make how to escape it obvious.

If this isn't considered a reasonable request; then please just re-close.

Comment 4 Bug Zapper 2008-11-26 04:22:05 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 lexual 2009-03-01 09:55:49 UTC

*** Bug 473319 has been marked as a duplicate of this bug. ***

Comment 6 lexual 2009-03-01 09:57:50 UTC

So is this a bug or a feature?

http://docs.fedoraproject.org/release-notes/f10/en_US/What_is_New_for_Installation_and_Live_Images.html#sn-Fedora_10_boot-time

Comment 7 Will Woods 2009-03-02 16:09:55 UTC

It's a feature. Bootup is now 5 seconds faster *and* involves two less monitor mode-switches. If you need the menu, just hold down Shift or Ctrl - or, in fact, press any key at all - after the BIOS finishes its work.

If you want the old behavior just use system-config-boot (System->Administration->Bootloader) or edit /etc/grub.conf to change the timeout back to 5.