I've installed the 20240410 iso on a couple of machines and this bug is
as good as fixed.
The systemd task would be nice to complete but that's more for the sake
of bug 1914409. Right now I have more important bugs to focus on...
** Changed in: systemd (Ubuntu)
Status: In Progress =>
In case anyone is wondering, you won't start to see an improvement until
you have at least:
linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
To
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6
---
plymouth (24.004.60-1ubuntu6) noble; urgency=medium
* Cherry-pick upstream fixes for consistent default scale selection
that matches what Mutter chooses on the login screen (LP: #2054769)
* plymouth.hook:
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
That commit is not meant to reflect the outcome of discussions that
happened after it (comment #93). It's just an intermediate "UNRELEASED"
commit reflecting intermediate development.
My intent with shared repos like this is to show what is being worked on
before anything is released to the
https://salsa.debian.org/ubuntu-dev-
team/plymouth/-/commit/bd9d0119fdbeb3b30c8d3caafdb8a31b23c188c4 does not
reflect the removal of the complete drm section.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks. I've reflected those changes in git:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot
** Changed in: plymouth (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
To
Sponsored plymouth 24.004.60-1ubuntu6 after dropping the complete drm
modules code and correcting the changelog entries. Unsubscribing
~ubuntu-sponsors.
** Patch added: "plymouth_24.004.60-1ubuntu6_sponsored.debdiff"
Daniel, please review and comment
https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462691 (see the description for the
two possible implementations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462690
** Merge proposal linked:
https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462691
--
You received this bug
That change is in plymouth, but hooks/framebuffer is in initramfs-tools.
If you're suggesting moving the code from plymouth into initramfs-tools
then I kind of understand, but it's not directly related to fixing this
bug.
--
You received this bug notification because you are a member of Ubuntu
If you are suggesting moving the logic from plymouth into initramfs-
tools then please start by duplicating the code you'd like moved into
initramfs-tools. That would be efficient since you have commit access to
initramfs-tools, and would mean I only have to deal with plymouth here.
--
You
Looking at the remaining "add drm modules (only if MODULES=dep)"
section: This logic should moved to hooks/framebuffer as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying
** Changed in: initramfs-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash
It seems unlikely my all-in-one kernel fix will be accepted upstream.
While I could propose it as an Ubuntu patch, another alternative is to
just let the linux task track bug 2049390 (Fix Committed). Then most
people will only need the above Plymouth patch to get a complete fix.
The remaining
Here's a fix for plymouth/noble.
The source is in:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/latest
We skipped ubuntu5 because that technically existed in bug 2054769 for
10 days already.
Also note this will cause some temporary initrd bloat while the
initramfs-tools
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462482
--
You received this bug
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel
Seems it's fairly easy to make a working solution in initramfs-tools
alone, but there's a compromise. If I only include tiny/simple
framebuffer drivers in initrd then i915 starts so late that Plymouth
doesn't use it, and bug 2054769 can occur on some machines. If I include
all the current drm
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think the delay I'm seeing is a feature of Plymouth, not a bug:
"ignoring since we only handle SimpleDRM devices after timeout"
As much as I dislike it perpetuating bug 1869655, this feature does
prevent bug 2054769 from reoccurring.
But this raises the question: is it worth putting i915,
Fedora 39:
CONFIG_FB_VESA=y
CONFIG_FB_EFI=y
Ubuntu 24.04:
# CONFIG_FB_VESA is not set
# CONFIG_FB_EFI is not set
In the kernel source, DRM_SIMPLEDRM recommends SYSFB_SIMPLEFB if you
want it to work on UEFI and VESA. And we do enable SYSFB_SIMPLEFB whose
help text says:
> you should still keep
Can you double check the framebuffer FB related conf options in your
kconfig against those in Fedora?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering
That might explain the strange behaviour I'm seeing where simpledrm
doesn't seem to be usable until a few seconds into the boot (maybe not
till i915drmfb is mentioned in the log?).
/boot/config-6.8.0-11-generic:# CONFIG_FB_EFI is not set
It was removed as part of bug 1965303. But I was hoping
The backend is a framebuffer driver. For example efifb which uses the
framebuffer set up by GOP in pre-boot.
If there are framebuffer drivers in tinydrm then maybe they matter for
those architectures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hopefully I'm wrong about the need for all the 'tiny' drivers and
simpledrm is in a class of its own. But I'd like to better understand
what the backend of simpledrm is and how much we can assume that it will
just work(tm).
--
You received this bug notification because you are a member of Ubuntu
Also hooks/plymouth is equally to blame and needs modifying, as
mentioned in comment #49 which I forgot.
Looking at my older 6.6 kernel however I'm reminded that some kernels
may have the drivers we need in the form of tiny drm (which is the
backend for simpledrm??):
> * hooks/framebuffer can be totally removed.
By chance I was testing on a desktop that has the Nvidia driver
installed (though no Nvidia card today, Intel only). Disabling
hooks/framebuffer had relatively little impact. In the end it was
hooks/framebuffer-nvidia that also needed disabling to
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
To
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
To manage
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe initramfs-tools does still need changing. plymouth-start.service
seems to run twice, and I get the feeling only the second instance is
actually succeeding in splashing on screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can test if the above suggestion will work for you by adding these
kernel parameters:
loglevel=3 fsck.mode=skip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools
AFAICT; these initramfs-tools package changes would cover it:
* hooks/framebuffer can be totally removed.
* scripts/init-top/framebuffer should probably stay
* conf/initramfs.conf needs FRAMEBUFFER=y added to it
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Plymouth only gets added to the initrd when LUKS is enabled or you mark
another reason for needing the framebuffer.
So the suggestion I have from comment #49 is to mark needing the
framebuffer by default, and then stop including any DRM modules because
simpledrm is built into the kernel.
--
You
It's a bit unclear to me what change we need now to take advantage of
simpledrm? Comment #49 state getting plymouth in the initrd but that should
already be the case today or luks encryption wouldn't be working no?
what change would trigger the include of extra drm modules?
--
You received
Noble is now shipping with SimpleDRM enabled in kernel 6.8, so the next
step is comment #49 (which would also resolve bug 1869655).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Also focal (20.04.6) does have the bug now, per comment #23.
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash screen
It looks like the above code might not need /dev/console at all. It
should be possible to modify it to use a private pipe for fsck's stdout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
I'm starting to suspect our patch (comment #39) isn't directly to blame
for the systemd issue. Disabling or otherwise breaking systemd-
fsckd.service doesn't stop fsck output from polluting the console and
triggering this bug. Only skipping fsck avoids it. You can skip fsck
using 'fastboot' or
** Changed in: systemd (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: systemd (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
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)
** Tags added: jammy
** Tags added: flicker-free-boot visual-quality
** Tags removed: flicker-free-boot
** Tags added: flickerfreeboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
** Attachment added: "Screencast from 24-04-2022 16:39:39.webm"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+attachment/5583142/+files/Screencast%20from%2024-04-2022%2016%3A39%3A39.webm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hello,
I have spin up two VMs with the exact same specs, one using the 20.04.4
Desktop ISO and other the 22.04 Desktop ISO.
Please check the attached file "Screencast from 24-04-2022
16:39:39.webm".
GRUB config for both VMs:
GRUB_DEFAULT=saved
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5
This is a bug. The 'splash' option is configured, but text messages
from the kernel are being shown.
** Changed in: plymouth (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but
52 matches
Mail list logo
