More than rotated framebuffers, defaulting to simpledrm means Plymouth
doesn't know the physical monitor dimensions. So it uses heuristics and
that leads to the logo scale not matching the login screen which would
be a regression of bug 2054769. Actually it already happens on some slow
booting machines occasionally. But that too can be worked around with:
plymouth.force-scale={1,2}
And no, checking for rotation sensors is not a good idea because it
would give the wrong result for laptop/tablet convertibles that don't
have rotated framebuffers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1869655
Title:
Boot animations start too late to be useful
Status in Plymouth:
New
Status in grub2 package in Ubuntu:
Invalid
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in plymouth package in Ubuntu:
Triaged
Bug description:
Boot animations start too late to be useful
Modern systems spend all their boot time (a couple of seconds)
decompressing the kernel. During that time the user only sees the
static BIOS logo (ACPI BGRT). Then when Plymouth can finally start
animating, the startup process is already finished and there's
virtually no time left to show any useful animations.
This could be fixed in:
grub: By adding a splash under the BIOS logo to show some progress
_before_ a Linux kernel is even started
and/or
plymouth: By preferencing legacy framebuffer devices (like EFI) over
DRM, if we find those are available a few seconds sooner. That would
also fix bug 1868240 completely, and bug 1836858 mostly as the flicker
moves to when the login screen starts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1869655/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
