Comment 18 for bug 1970069

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.