This is something I have noticed happening for a long time now, and I see it in various flavours of Ubuntu. At the moment I happen to be using Ubuntu Studio.
As the system boots past grub, you get a nice graphical Ubuntu Studio animated logo for a while, but then, just before the login screen appears, it drops back to the text console, where you see various things at different times (like system startup logging - as you'd see if you pressed escape while Plymouth is displaying the logo, and even a login prompt at times), but typically it at least shows the filesystem status (as clean usually), then it switches back to graphical mode for the login dialog.
It would look very much neater if it didn't flash the text console on screen like this. I am just wondering why it does this, and would like a fix? I know it's no biggy. I just get curious about odd things :)
You will always get a black screen between Plymouth and Login, unless you are using Windows 10. For myself in Ubuntu 16.04 it lasts about four seconds. In Ubuntu 18.04 it only lasts 1 or 2 seconds. You can however eliminate all text that appears on that screen.
There are a number of different things you can do for a smoother boot experience:
I've purchased a tripod for my cellphone to make videos of the various grub booting scenarios but have run into technical difficulties creating GIF to post here.
1. Reduce console messages
Based on Arch Linux's Silent Boot article you can add three extra options after
quiet splash
boot parameters:The full article references
systemd
in boot in which case this can be used:touch ~/.hushlogin
to remove the Last login message.2. Reduce screen resetting
From this Q&A: What is vt.handoff=7 parameter in grub.cfg? it says:
If you are grub with a graphics background image add these lines in
/etc/default/grub
:3. Eliminate Grub messages
After selecting a menu option, or the countdown timer expires grub sometimes issues these messages:
To eliminate these message edit
/etc/grub.d/10_linux
and change these lines to comments:And a page down these lines too:
4. Reduce
fsck
during bootIn your
/etc/fstab
ensure passno is set to0
to prevent[email protected]
from running. More details from the manpage.Change the frequency of
fsck
to every 30 boots or once a month: My Ubuntu is running fsck on every bootupfsck
is run by default by the initramfs. By removing it and having systemd runfsck
you will be able to redirect the output.systemd-fsck-root.service
and[email protected]
located in/lib/systemd/system
will need to be copied to/etc/systemd/system/
and edit them, configuring StandardOutput and StandardError like this::Your question has already been answered on Ask Ubuntu Here