With your change Fedora and Ubuntu are now behaving relatively similarly.
* Both have a deficiency where the handoff from BGRT logo to Plymouth is doing 
a modeset for some reason.  
* Due to something in Fedora's GRUB it's a little clearer when GRUB starts.

Here's various artifacts if you want to be able to compare anything since I 
have both on the same hardware.
I ran the same kernel binary that has your patches on both (but on Fedora it 
behavedthe same with a stock one).

Ubuntu booting (video): https://youtu.be/1J0_Vg1pScQ
Kernel config: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-kernel-config-both
Ubuntu /etc/default/grub: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-etc-default-grub
Ubuntu journal: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-journal
Fedora booting (video): https://youtu.be/IzesNHpM-nw
Fedora journal: 
https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-fedora-journal

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  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) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions


-- 
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to     : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help   : https://help.launchpad.net/ListHelp

Reply via email to