Hide console messages while Plymouth is running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: plymouth
Since the removal of the /usr/share/
Restoring the FRAMEBUFFER=y option in /etc/initramfs-
It does however, nean that plymouth appears right after grub quits, and the boot is much more seamless.
As it statnds, the initramfs appears to be outputting text, and taking a non-negligable amount of time to get to the point where plymouth will be started by upstart. I'm not sure if this the initramfs at fault, or upstart not starting plymouth soon enough.
This is on an HP 6730b with intel GM45 graphics. (KMS), using xorg-edgers PPA (for decent libdrm), 2.6.33 DRM from the for-linus branch of the Intel-drm kernel. IE.. KMS is working properly.
tags: | added: kernel-series-unknown |
tags: | removed: kernel-series-unknown |
summary: |
- Plymouth starts late + Hide console messages while Plymouth is running |
Changed in plymouth (Ubuntu): | |
importance: | Undecided → Low |
Changed in plymouth (Ubuntu): | |
status: | Triaged → Fix Committed |
Thank you for taking the time to report this issue and help to improve Ubuntu.
What is the exact text that appears on your screen before plymouth starts? There should never be any text from fsck; plymouth is started from the root filesystem before mountall is started, and mountall drives all the fsck handling at boot.
plymouth will not be added back to the initramfs by default because it is not needed there and it slows down the boot overall. Anything that results in text output prior to plymouth starting when the 'quiet' boot option is used is buggy, and those components should be fixed.