`quiet splash` breaks 20.04.1 server image boot process, but not desktop?

[Liam Proven]

On Fri, 25 Sep 2020 at 08:15, Loopend via ubuntu-users
<ubuntu-users at lists.ubuntu.com> wrote:
>
> Hi everyone!
>
> On a fresh 20.04.1 Server installation (no additional packages installed, absolute installer-default minimum set), just adding `quiet splash` to the GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (which is empty by default),

AFAIK, it should not be empty...

> breaks the boot process. Splash is shown and hangs there forever.

If you press Esc, can you see the boot messages? Can you switch to
another terminal with Alt+F[2-6]?

>  No console login possible. Adding `nomodeset`has no effect.

Very odd!

And you are reinstalling GRUB each time with `update-grub`?

>  2. Tips on how to debug this? As the issue only occurs with `quiet splash` set, I'm not able to see any logs from boot.

One thing... You realize that `quiet` is an option and `splash` is a
different, independent option, right? They are not a pair.

`quiet` tells the kernel not to print the full list of boot messages
to the console. `splash` tells it to display whatever loading screen
is configured -- usually `plymouth` I think. `plymouth` in turn
requires a graphics mode, and that by default on modern kernels uses
the Kernel Modesetting module if it is present and available. KMS
needs the kernel to have a graphics driver for your graphics adaptor.
`nomodeset` tells the kernel _not_ to use KMS even if it's available.


-- 
Liam Proven – Profile: https://about.me/liamproven
Email: lproven at cix.co.uk – gMail/gTalk/gHangouts: lproven at gmail.com
Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven
UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053