Boot / Shutdown splash screen not displayed with linux-kernel-latest v4.16.2-1

[jharveyb]

Qubes OS version:

4.0 testing

Affected component(s):

Plymouth

---

Steps to reproduce the behavior:

Install linux-kernel-latest v4.16.2-1 from testing
Shutdown and boot with kernel 4.16.2-1
Shutdown after boot

Expected behavior:

Plymouth loads after selecting kernel, showing Qubes logo with disk password prompt and progress bar below. On shutdown Qubes logo is displayed with progress bar below.

Actual behavior:

Plymouth does not load during either boot or shutdown so disk password prompt is shown in text mode, followed by kernel messages that are normally shown after pressing Home / Escape from Plymouth splash screen.

General notes:

Was running linux-kernel-latest v4.15.6-1 before this and Plymouth behaved as expected, could switch to view kernel messages per boot without issue for subsequent boots or shutdowns. After installing linux-kernel-latest v4.16.2-1, booting linux-kernel-latest v4.15.6-1 still presents the Plymouth splash screen correctly.

---

Related issues:

QubesOS/updates-status#483

[jharveyb]

The same issue is present with QubesOS/updates-status#542

rebuilding the initramfs using sudo plymouth-set-default-theme qubes-dark -R does not change the behavior.

However, the tribar theme does work on boot, even though the system still defaults to text mode (have to explicitly switch back to graphical mode to display the tribar). The same behavior is seen on shutdown, though there is no tribar and just a empty screen with black background.

[strugee]

I can reproduce this problem on kernel-latest 4.19.2-3. Let me know if there's any debugging information I can provide.

[opposablebrain]

+1

[marmarek]

Similar issue in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572
I don't think it's exactly the same (holding backspace does not bring proper luks prompt), but it may be related.

[fepitre]

I tested to revert the commit referenced in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572 (fepitre/qubes-linux-kernel@0abdd79) but it had not effect. Also, newer version of plymouth does not have any effect as I encounter the same problem in testing dom0 under fc29 for R4.1.

[fepitre]

I also found in plymouth debug that in kernel above 4.14, it detects now hvc0 as console : kernel-4.14 log https://gist.github.com/fepitre/2e19f000393dcb7e12ca8f3d55db0aa4#file-plymouth-debug-kernel-4-14-L35, kernel-4.19 log https://gist.github.com/fepitre/33edf64428b6c5b986a8c7486eb3eed7#file-plymouth-debug-kernel-4-19-L34.

[marmarek]

In 4.19 log:

serial consoles detected, managing them with details forced

in old log:

creating objects for drm devices

This looks like a good lead. I'd look for some option to disable serial consoles in plymouth. Is there anything in some config file? Or maybe on kernel command line?

[fepitre]

@marmarek @andrewdavidwong : it has also a positive solution for me for installing 4.0.1. Indeed, as it ships kernel-4.19, I never reached the anaconda startup (first menu of selecting language). It was staying idle in black screen with blinking cursor. I just tested to add """plymouth.ignore-serial-consoles""" at the grub installer boot menu right after """quiet rhgb"""" and it solved the problem. I can now install 4.0.1. Maybe we should add this somewhere in the troubleshooting? This could be a same problem encountered by other users.

[andrewdavidwong]

it has also a positive solution for me for installing 4.0.1. Indeed, as it ships kernel-4.19, I never reached the anaconda startup (first menu of selecting language). It was staying idle in black screen with blinking cursor. I just tested to add """plymouth.ignore-serial-consoles""" at the grub installer boot menu right after """quiet rhgb"""" and it solved the problem. I can now install 4.0.1. Maybe we should add this somewhere in the troubleshooting? This could be a same problem encountered by other users.

Sounds good. I could see it being added to either of these:

• https://www.qubes-os.org/doc/releases/4.0/release-notes/#known-issues
• https://www.qubes-os.org/doc/#troubleshooting

Mind submitting a PR?

[marmarek]

Since this applies to installation image, it may be a reason to release new one. If this indeed solve some common issue. Can anyone else confirm this?
@fepitre I understand you mean legacy boot (since you have grub there). Have you tried UEFI too?
But still, adding it to documentation is a good idea anyway.

[fepitre]

@marmarek, indeed it was with legacy boot. I did not retry with UEFI because I lack the time to do that currently. That would be great if anyone could confirm this too. In my case, it is not a problem with nouveau module because disabling it produced the same result: blinking cursor. Only the method described above solved the graphical boot.

[strugee]

I can confirm that this workaround works under UEFI.

[qubesos-bot]

Automated announcement from builder-github

The package kernel-latest-4.20.16-1.pvops.qubes has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package kernel-latest-4.20.16-2.pvops.qubes has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package kernel-latest-5.0.2-1.pvops.qubes has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package kernel-latest-5.0.7-1.pvops.qubes has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[tlaurion]

Heads on headless systems (servers outputting to console) consequently requires that kernel parameter to be removed as pointed in this issue

[marmarek]

On the other hand, on laptop systems this option is needed, otherwise plymouth treats /dev/hvc0 (a console to Xen) as a serial console and disable graphical screen. Removing that option in a board config seems like a good compromise for me.

[qubesos-bot]

Automated announcement from builder-github

The package kernel-5.4.21-1.qubes has been pushed to the r4.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package kernel-5.4.38-1.qubes has been pushed to the r4.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[tlaurion]

@marmarek

followed by kernel messages that are normally shown after pressing Home / Escape from Plymouth splash screen.

Those are still not present for me when pressing escape at boot:

May 27 21:55:03 dom0 systemd-journald[209]: Runtime journal (/run/log/journal/) is 8.0M, max 196.2M, 188.2M free.
May 27 21:55:03 dom0 kernel: Linux version 4.19.107-1.pvops.qubes.x86_64 (user@build-fedora4) (gcc version 6.4.1 20170727 (Red Hat 6.4.1-1) (GCC)) #1 SMP Sat Feb 29 16:04:42 UTC 2020
May 27 21:55:03 dom0 kernel: Command line: placeholder root=/dev/mapper/qubes_dom0-root ro rd.luks.uuid=luks-a35bb850-778b-46d7-9814-7a105669960e rd.luks.options=discard rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap i915.alpha_support=1 plymouth.ignore-serial-consoles intel_iommu=igfx_off fromiso=/dev/disk/by-uuid/2f00bca5-dd3c-4a39-98f2-4e0ffeeae9f8/Qubes-R4.0.3-x86_64.iso iso-scan/filename=/Qubes-R4.0.3-x86_64.iso rhgb quiet rd.qubes.hide_all_usb intel_iommu=on intel_iommu=igfx_off