grub2 still hands off to blank tty7 on non-Server command-line-only systems and some Server systems
On Natty and Oneiric non-Server command-line only systems (which can be installed from the Alternate and Minimal CD's), grub2 hands off to blank tty7 (as in bug 700686). As a consequence, a blank black (or purple) terminal is shown, and the system does not appear to be functional. This can be particularly confusing to novices, who sometimes assume that the system has not successfully booted. Switching to an active virtual console (for example, by pressing Alt+F1) yields a login screen and makes it possible to use the machine.
This also happens on a few Natty and Oneiric Server systems. It seems to happen on all such server systems running on VMware virtual machines and installed using the VMware Easy Install automatically installation facility (but it does not seem to occur with VMware when the OS is installed manually). The most obvious explanations specific to that feature do not seem to apply (see https:/
Please see bug 700686, bug 695658, and this bug's original description for some (incomplete) details about the cause of this behavior (and why it did not occur in previous releases). See original description and comments for details substantiating the above generalizations.
- grub2 still starts up blank on command-line system, configured with
+ grub2 still starts up blank on non-Server command-line-only system
- grub2 still starts up blank on non-Server command-line-only system
+ grub2 still hands off to blank tty7 on non-Server command-line-only
|Akkana Peck (akkzilla) wrote : Re: grub2 still hands off to blank tty7 on non-Server command-line-only systems||#12|
|Changed in grub2 (Ubuntu):|
|importance:||Undecided → Low|
grub2 still hands off to blank tty7 on non-Server command-line-only
+ systems and some Server systems
|tags:||added: amd64 oneiric|