The problem appears to be with the new boot manager, Plymouth
but those irritated by it are mostly those who run servers
and people like me who find beauty in order
(rather than a haphazardly flickering screen)
and like to see what is going on.
There is much discussion about how to fix it, eg
And I tried much of it, in particular:
Code:
GRUB_CMDLINE_LINUX="vga=795 loglevel=7"
GRUB_CMDLINE_LINUX="vga=795 console=tty7 loglevel=7"
GRUB_CMDLINE_LINUX="vga=795 loglevel=7 noplymouth"
GRUB_CMDLINE_LINUX="vga=795 loglevel=7 noplymouth INIT_VERBOSE=yes init=/sbin/init -v"
GRUB_CMDLINE_LINUX="vga=795 loglevel=7 nomodeset noplymouth INIT_VERBOSE=yes init=/sbin/init -v"
GRUB_CMDLINE_LINUX="vga=795 loglevel=7 nomodeset noplymouth init=/sbin/init -v"
GRUB_CMDLINE_LINUX="vga=795 loglevel=7 nomodeset noplymouth"
plus I tried
Code:
sudo mv /etc/init/plymouth* /init/temphold/
which also did nothing nothing.
key points:
- noplymouth does not work
- loglevel=7 makes no difference
- there was still a long period of black screen with no messages, nothing.
- INIT_VERBOSE=yes init=/sbin/init -v gives lots of useless init messages but not the useful kernel messages.
Of course you can get the kernel messages after logging in from /var/log/kern.log,
but that is not the point.
I plan to file a launchpad bug against it.
Bookmarks