Plymouth costs 2 minutes of additional time according to systemd-analyze for me. And while I am indeed running Ubuntu on my 10-year-old HDD, it does seem to have an impact anyways, the impact just increases depending on your hardware.
What I am curious about though, is in the GRUB configuration file, do I simply remove quiet splash or do I replace it with fsck.mode = skip quiet. Because I saw both and I want to make sure what I should do!
Two minutes is huge, so that’s simply a bug that should be reported. Not a reason to disable Plymouth for everyone.
Please run:
ubuntu-bug plymouth
on the affected machine.
If you just need a workaround that disables Plymouth then removing splash is all it takes.
1 Like
so this line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
should become:
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
correct?
1 Like
Closing. Please ask for support in one of our many support venues.
That is their purpose. Ubuntu Discourse has a different purpose.