[Bug 1869655] Re: Boot animations start too late to be useful
Launchpad Bug Tracker
1869655 at bugs.launchpad.net
Wed Mar 27 17:59:27 UTC 2024
This bug was fixed in the package initramfs-tools - 0.142ubuntu23
---------------
initramfs-tools (0.142ubuntu23) noble; urgency=medium
[ Daniel van Vugt ]
* hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to
limit the size of initrd when FRAMEBUFFER=y is soon enabled for desktop
installations (LP: #1970069, #1869655).
[ Benjamin Drung ]
* autopkgtest: Increase QEMU timeouts on arm64/armhf
* hooks/framebuffer:
- Move adding framebuffer drivers into auto_add_modules
- Drop looking in $MODULESDIR/initrd/ for kernel modules
- Support MODULES=dep in framebuffer hook
initramfs-tools (0.142ubuntu22) noble; urgency=medium
* autopkgtest: update systemd-udevd path from /lib to /usr/lib
initramfs-tools (0.142ubuntu21) noble; urgency=medium
[ Benjamin Drung ]
* configure_networking:
- Increase minimum timeout to 30 seconds
- Fix configuring BOOTIF when using iSCSI (LP: #2056187)
- Set interface MTU if provided by the DHCP server (LP: #2056194)
- log sleep durations before retries
* Copy /etc/passwd into the initramfs to allow dhcpcd running as dhcpcd user
* Replace obsolete pkg-config build-dependency by pkgconf
[ Dan Bungert ]
* Restore nvdimm and dax pmem-related modules (LP: #1981385)
-- Benjamin Drung <bdrung at ubuntu.com> Thu, 21 Mar 2024 10:57:54 +0100
** Changed in: initramfs-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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:
In Progress
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
More information about the foundations-bugs
mailing list