I'm finally looking at this again. Theories tested today: * Disabling PLY_ENABLE_SYSTEMD_INTEGRATION didn't fix anything. Seems we're dealing with kernel messages and not just systemd logging.
* Reducing device_timeout to 0.1 (seconds) in ubuntu-default- devicetimeout.patch helps a lot and hides most of the problem by not waiting in the background for DRM startup. But not all of the problem is fixed with that and presumably would be a regression of bug 1838725 on some machines. New ideas for next week: * The "quiet" kernel parameter is too noisy(!?). Perhaps "loglevel=0" would be better. I can't tell because I just broke the machine I was using to test. * Would "boot_delay" be a way of hiding the early messages? * "bgrt_disable": Why does this exist in the kernel and is it somehow interfering? * Find out if plymouth's initramfs integration is capable of rendering a splash screen before kernel startup. If it ever was then it's sure not now. * Go back and try focal on the same machine(s) to get a better idea of what it looked like when it was working before. * Wait and try the proposed plymouth update for Noble that other people are working on. Upstream might have just fixed things. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in plymouth package in Ubuntu: In Progress Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
