Daniel, I cannot reproduce your issues but I do have some thoughts: 1) I didn't catch this, but we have actually been using SimpleDRM already since kernel 6.9 where the simple-framebuffer device path changed (the same change that triggered bug 2083329 and bug 2115451) making plymouth unaware that it is dealing with SimpleDRM and thus use it as if it were any real DRM driver. The git snapshot we imported "fixes" this, meaning that without UseSimpledrm=1 or plymouth.use-simpledrm=1 plymouth will actually avoid SimpleDRM for 8s again.
2) It is possible that your EFI framebuffer is coming up with one of the blacklisted resolutions (640x480, 800x600, 1024x768), which plymouth from the new git snapshot will ignore while the previous version didn't -- although it does seem weird that multiple of your machines would hit that and none of my machines does. To confirm, check what happens after setting: [Daemon] UseSimpledrm=2 in /etc/plymouth/plymouthd.conf (running `update-initramfs -u` or equivalent to regen initrd) 3) Please collect verbose logs with the `plymouth.debug=stream:/run/plymouth.log` kernel cmdline option (you'll probably see 2 new lines of text in between BIOS and splash, but afaics that doesn't really affect the graphical splash logic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869655 Title: Boot splash starts too late to be useful - Use SimpleDRM by default To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/1869655/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
