I’ve been running systems up to Buster and have always had the ‘quiet’ option in the grub settings to show the regular service startup messages (the colored ones showing [ok] and such but not all the dmesg stuff). I just upgraded a server to bullseye and there are zero messages being displayed now except an immediate message about not being able to use IRQ 0. Worse, google can’t seem to find any information on this. If I remove the quiet option from grub then I see those service messages again, along with all the other stuff I don’t need.

What is broken and how do I fix this issue? I assumed it would be safe to upgrade by now but this seems like a pretty big problem if I ever need to troubleshoot a system.

[Edit] In case anyone else finds this post searching for the same issue… Apparently the trick is that now you MUST install plymouth, even on systems that do not have a desktop environment. For whatever reason plymouth has taken over the job of displaying the text startup messages now. Keep your same grub boot parameters (quiet by itself, without the splash option) and you will get the old format of startup messages showing once again. It’s been working fine the old way for 20+ years but hey let’s change something just for the sake of confusing everyone.

[Edit 2] Thanks to marvin below, I now have a final solution that no longer requires plymouth to be installed. Edit /etc/default/grub and add systemd.show_status=true to GRUB_CMDLINE_LINUX_DEFAULT. In my case to full line is:

GRUB_CMDLINE_LINUX_DEFAULT="quiet systemd.show_status=true"

Don’t forget to run update-grub after you save your changes.

  • marvin@lemmy.sdf.org
    3·
    1 year ago

    Hi.

    I’m actually amazed how many people comment without having a clue what they are talking about.

    What you’re describing is not an issue but the fix of an issue 😃

    When the kernel boots with the parameter quiet, systemd should get the option systemd.show_status=auto. With this option it should only inform about failures and such like. In current releases this finally works.

    To get the old behaviour you just have to add systemd.show_status=true to your kernel parameters.

    • Shdwdrgn@mander.xyzOPEnglish
      2·
      1 year ago

      I finally had a chance to get back to this build, and wanted to thank you for this solution. It does indeed work even after removing plymouth and I’ll update the OP as the best solution.

    • Shdwdrgn@mander.xyzOPEnglish
      1·
      1 year ago

      Interesting, I’ll have to try that! It would be nice to not need the plymouth package installed for this functionality as it did seem rather counter-intuitive to have to install something just to see information that used to be displayed.

  • suprjami@lemmy.sdf.orgEnglish
    11·
    1 year ago

    Perhaps quiet has been made quieter. Try removing quiet and see if you get the messages you want?

    I remove quiet from all my systems.

    • Shdwdrgn@mander.xyzOPEnglish
      1·
      1 year ago

      Sorry, last line of the first paragraph above… If I remove quiet then I get ALL of the info, the service starts as well as all the stuff you see in dmesg. I don’t want the dmesg stuff, I only want the lines showing each service starting, like it did on buster.