I've analysed a couple of Noble systems today and don't think initramfs-tools needs improving (although it might not hurt). On both systems, plymouth-start was within 1 second of simpledrm starting (same timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the bug ("fbcon: Taking over console") _before_ "Initialized simpledrm" due to kernel error-level messages.
2. After setting loglevel=3 (bug 2049390), it's a slight improvement but the "clean" message from fsck via systemd still interrupts the boot sequence.
So it looks like we need either:
* loglevel=3 (bug 2049390) and a systemd fix for fsck; or
* The kernel patch I've already proposed upstream.
I've analysed a couple of Noble systems today and don't think initramfs-tools needs improving (although it might not hurt). On both systems, plymouth-start was within 1 second of simpledrm starting (same timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the bug ("fbcon: Taking over console") _before_ "Initialized simpledrm" due to kernel error-level messages.
2. After setting loglevel=3 (bug 2049390), it's a slight improvement but the "clean" message from fsck via systemd still interrupts the boot sequence.
So it looks like we need either:
* loglevel=3 (bug 2049390) and a systemd fix for fsck; or
* The kernel patch I've already proposed upstream.