Plymouth boot is still being shown even though in /etc/default/grub I have disabled it on a dual-boot...

Why did House of Representatives need to condemn Trumps Tweets?

GNU sort stable sort when sort does not know sort order

Why does aggregate initialization not work anymore since C++20 if a constructor is explicitly defaulted or deleted?

Why is it "on the inside" and not "in the inside"?

How to have poached eggs in "sphere form"?

My employer is refusing to give me the pay that was advertised after an internal job move

Piece of chess engine, which accomplishes move generation

Classic vs Modern Experience

Can a US President, after impeachment and removal, be re-elected or re-appointed?

How do I make my photos have more impact?

Is SecureRandom.ints() secure?

What is a good example for artistic ND filter applications?

What clothes would flying-people wear?

Why did Windows 95 crash the whole system but newer Windows only crashed programs?

How do I find the FamilyGUID of an exsting database

What are the closest international airports in different countries?

Why did some Apollo missions carry a grenade launcher?

Rampant sharing of authorship among colleagues in the name of "collaboration". Is not taking part in it a death knell for a future in academia?

How to season a character?

Have two feature in matrix command

Why does Canada require bilingualism in a lot of federal government posts?

What is the reason for cards stating "Until end of turn, you don't lose this mana as steps and phases end"?

Why put copper in between battery contacts and clamps?

Unknown indication below upper stave



Plymouth boot is still being shown even though in /etc/default/grub I have disabled it on a dual-boot machine


Why do most distributions chain UEFI and grub?Why is it that my initrd only has one directory, namely, 'kernel'?GRUB error- no suitable video mode foundwhy is grub2 ignoring kernel options when boot from el torito on CD?How to boot via grub2 rescue promt on UEFI system?linuz-linux can't be found in efi-bootmanager on iMacWhy don't we include File System drivers in the kernel itself instead of using Initrd/InitramfsCan't get grub2 menu to displayWhy am I not able to insmod or run any GRUB commands from a Debian Stretch DVD?How to put GRUB2 on a CD reading the boot configuration file from harddisk?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















I have disabled plymouth and it was working good/great till recently.



Sharing the contents of /etc/default/grub



$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=500
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


Just to be sure it was taking the right entries I did -



$ sudo update-grub
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-4.19.0-5-amd64
Found initrd image: /boot/initrd.img-4.19.0-5-amd64
Found linux image: /boot/vmlinuz-4.19.0-4-amd64
Found initrd image: /boot/initrd.img-4.19.0-4-amd64
Found memtest86 image: /memtest86.bin
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration


But still the plymouth splash-screen is coming on. I am much more happier seeing the boot and kernel messages etc. just in case something goes wrong somewhere.



I also had a look at man pages of both plymouth and plymouthd to see if I could get any idea of what changed but came up empty.



For what it's worth I'm running plymouth 0.9.4-1.1










share|improve this question

































    1















    I have disabled plymouth and it was working good/great till recently.



    Sharing the contents of /etc/default/grub



    $ cat /etc/default/grub
    # If you change this file, run 'update-grub' afterwards to update
    # /boot/grub/grub.cfg.
    # For full documentation of the options in this file, see:
    # info -f grub -n 'Simple configuration'

    GRUB_DEFAULT=0
    GRUB_TIMEOUT=500
    GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
    GRUB_CMDLINE_LINUX=""

    # Uncomment to enable BadRAM filtering, modify to suit your needs
    # This works with Linux (no patch required) and with any kernel that obtains
    # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
    GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

    # Uncomment to disable graphical terminal (grub-pc only)
    #GRUB_TERMINAL=console

    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    #GRUB_GFXMODE=640x480

    # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
    #GRUB_DISABLE_LINUX_UUID=true

    # Uncomment to disable generation of recovery mode menu entries
    #GRUB_DISABLE_RECOVERY="true"

    # Uncomment to get a beep at grub start
    #GRUB_INIT_TUNE="480 440 1"


    Just to be sure it was taking the right entries I did -



    $ sudo update-grub
    Generating grub configuration file ...
    Found background image: /usr/share/images/desktop-base/desktop-grub.png
    Found linux image: /boot/vmlinuz-4.19.0-5-amd64
    Found initrd image: /boot/initrd.img-4.19.0-5-amd64
    Found linux image: /boot/vmlinuz-4.19.0-4-amd64
    Found initrd image: /boot/initrd.img-4.19.0-4-amd64
    Found memtest86 image: /memtest86.bin
    Found memtest86+ image: /memtest86+.bin
    Found memtest86+ multiboot image: /memtest86+_multiboot.bin
    Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
    Adding boot menu entry for EFI firmware configuration


    But still the plymouth splash-screen is coming on. I am much more happier seeing the boot and kernel messages etc. just in case something goes wrong somewhere.



    I also had a look at man pages of both plymouth and plymouthd to see if I could get any idea of what changed but came up empty.



    For what it's worth I'm running plymouth 0.9.4-1.1










    share|improve this question





























      1












      1








      1








      I have disabled plymouth and it was working good/great till recently.



      Sharing the contents of /etc/default/grub



      $ cat /etc/default/grub
      # If you change this file, run 'update-grub' afterwards to update
      # /boot/grub/grub.cfg.
      # For full documentation of the options in this file, see:
      # info -f grub -n 'Simple configuration'

      GRUB_DEFAULT=0
      GRUB_TIMEOUT=500
      GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
      GRUB_CMDLINE_LINUX=""

      # Uncomment to enable BadRAM filtering, modify to suit your needs
      # This works with Linux (no patch required) and with any kernel that obtains
      # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
      GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

      # Uncomment to disable graphical terminal (grub-pc only)
      #GRUB_TERMINAL=console

      # The resolution used on graphical terminal
      # note that you can use only modes which your graphic card supports via VBE
      # you can see them in real GRUB with the command `vbeinfo'
      #GRUB_GFXMODE=640x480

      # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
      #GRUB_DISABLE_LINUX_UUID=true

      # Uncomment to disable generation of recovery mode menu entries
      #GRUB_DISABLE_RECOVERY="true"

      # Uncomment to get a beep at grub start
      #GRUB_INIT_TUNE="480 440 1"


      Just to be sure it was taking the right entries I did -



      $ sudo update-grub
      Generating grub configuration file ...
      Found background image: /usr/share/images/desktop-base/desktop-grub.png
      Found linux image: /boot/vmlinuz-4.19.0-5-amd64
      Found initrd image: /boot/initrd.img-4.19.0-5-amd64
      Found linux image: /boot/vmlinuz-4.19.0-4-amd64
      Found initrd image: /boot/initrd.img-4.19.0-4-amd64
      Found memtest86 image: /memtest86.bin
      Found memtest86+ image: /memtest86+.bin
      Found memtest86+ multiboot image: /memtest86+_multiboot.bin
      Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
      Adding boot menu entry for EFI firmware configuration


      But still the plymouth splash-screen is coming on. I am much more happier seeing the boot and kernel messages etc. just in case something goes wrong somewhere.



      I also had a look at man pages of both plymouth and plymouthd to see if I could get any idea of what changed but came up empty.



      For what it's worth I'm running plymouth 0.9.4-1.1










      share|improve this question
















      I have disabled plymouth and it was working good/great till recently.



      Sharing the contents of /etc/default/grub



      $ cat /etc/default/grub
      # If you change this file, run 'update-grub' afterwards to update
      # /boot/grub/grub.cfg.
      # For full documentation of the options in this file, see:
      # info -f grub -n 'Simple configuration'

      GRUB_DEFAULT=0
      GRUB_TIMEOUT=500
      GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
      GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nomsi,noaer"
      GRUB_CMDLINE_LINUX=""

      # Uncomment to enable BadRAM filtering, modify to suit your needs
      # This works with Linux (no patch required) and with any kernel that obtains
      # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
      GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

      # Uncomment to disable graphical terminal (grub-pc only)
      #GRUB_TERMINAL=console

      # The resolution used on graphical terminal
      # note that you can use only modes which your graphic card supports via VBE
      # you can see them in real GRUB with the command `vbeinfo'
      #GRUB_GFXMODE=640x480

      # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
      #GRUB_DISABLE_LINUX_UUID=true

      # Uncomment to disable generation of recovery mode menu entries
      #GRUB_DISABLE_RECOVERY="true"

      # Uncomment to get a beep at grub start
      #GRUB_INIT_TUNE="480 440 1"


      Just to be sure it was taking the right entries I did -



      $ sudo update-grub
      Generating grub configuration file ...
      Found background image: /usr/share/images/desktop-base/desktop-grub.png
      Found linux image: /boot/vmlinuz-4.19.0-5-amd64
      Found initrd image: /boot/initrd.img-4.19.0-5-amd64
      Found linux image: /boot/vmlinuz-4.19.0-4-amd64
      Found initrd image: /boot/initrd.img-4.19.0-4-amd64
      Found memtest86 image: /memtest86.bin
      Found memtest86+ image: /memtest86+.bin
      Found memtest86+ multiboot image: /memtest86+_multiboot.bin
      Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi
      Adding boot menu entry for EFI firmware configuration


      But still the plymouth splash-screen is coming on. I am much more happier seeing the boot and kernel messages etc. just in case something goes wrong somewhere.



      I also had a look at man pages of both plymouth and plymouthd to see if I could get any idea of what changed but came up empty.



      For what it's worth I'm running plymouth 0.9.4-1.1







      debian boot grub2 boot-loader plymouth






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited 32 mins ago







      shirish

















      asked 40 mins ago









      shirishshirish

      3,9717 gold badges41 silver badges95 bronze badges




      3,9717 gold badges41 silver badges95 bronze badges

























          0






          active

          oldest

          votes














          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f533036%2fplymouth-boot-is-still-being-shown-even-though-in-etc-default-grub-i-have-disab%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f533036%2fplymouth-boot-is-still-being-shown-even-though-in-etc-default-grub-i-have-disab%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

          Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

          Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...