Arch/Grub - Disable booting message












2















I just installed Arch Linux for the first time. I'd like to achieve just a black screen when booting until I'm asked for the login. I'm using grub as a boot loader. And added the line:



GRUB_CMDLINE_LINUX_DEFAULT="vga=current quiet loglevel=3 rd.udev.log-priority=3 splash



to the /etc/default/grub and updated grub, but I still see the message like




Booting >>Arch Linux<<




for a split second on startup (actually the text is german). I'm not 100% sure, whether this is printed by grub, but that's my current guess.



Does anybody have an idea how to troubleshoot this/hide the message?










share|improve this question



























    2















    I just installed Arch Linux for the first time. I'd like to achieve just a black screen when booting until I'm asked for the login. I'm using grub as a boot loader. And added the line:



    GRUB_CMDLINE_LINUX_DEFAULT="vga=current quiet loglevel=3 rd.udev.log-priority=3 splash



    to the /etc/default/grub and updated grub, but I still see the message like




    Booting >>Arch Linux<<




    for a split second on startup (actually the text is german). I'm not 100% sure, whether this is printed by grub, but that's my current guess.



    Does anybody have an idea how to troubleshoot this/hide the message?










    share|improve this question

























      2












      2








      2








      I just installed Arch Linux for the first time. I'd like to achieve just a black screen when booting until I'm asked for the login. I'm using grub as a boot loader. And added the line:



      GRUB_CMDLINE_LINUX_DEFAULT="vga=current quiet loglevel=3 rd.udev.log-priority=3 splash



      to the /etc/default/grub and updated grub, but I still see the message like




      Booting >>Arch Linux<<




      for a split second on startup (actually the text is german). I'm not 100% sure, whether this is printed by grub, but that's my current guess.



      Does anybody have an idea how to troubleshoot this/hide the message?










      share|improve this question














      I just installed Arch Linux for the first time. I'd like to achieve just a black screen when booting until I'm asked for the login. I'm using grub as a boot loader. And added the line:



      GRUB_CMDLINE_LINUX_DEFAULT="vga=current quiet loglevel=3 rd.udev.log-priority=3 splash



      to the /etc/default/grub and updated grub, but I still see the message like




      Booting >>Arch Linux<<




      for a split second on startup (actually the text is german). I'm not 100% sure, whether this is printed by grub, but that's my current guess.



      Does anybody have an idea how to troubleshoot this/hide the message?







      linux boot grub arch-linux hid






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jun 24 '16 at 14:36









      Joe DoeJoe Doe

      1613




      1613






















          1 Answer
          1






          active

          oldest

          votes


















          3














          In order to remove that message, go into /boot/grub/grub.cfg. Scroll down until you see the line ### BEGIN /etc/grub.d/10_linux ###. Right below, you'll see something like this:



          menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2' {
          load_video
          set gfxpayload=keep
          insmod gzio
          insmod part_gpt
          insmod fat
          set root='hd1,gpt1'
          if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 AAF7-73DC
          else
          search --no-floppy --fs-uuid --set=root AAF7-73DC
          fi
          echo 'Loading Linux linux-selinux ...'
          linux /vmlinuz-linux-selinux root=UUID=cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2 rw cryptdevice=/dev/sdb3:root security=selinux selinux=1 init=/usr/bin/e4rat-lite-preload
          echo 'Loading initial ramdisk ...'
          initrd /intel-ucode.img /initramfs-linux-selinux.img
          }


          Remove the lines that begin with echo and that boot message will be gone. Add quiet to your kernel parameters to disable boot messages in the kernel.






          share|improve this answer


























          • the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

            – Rainer Verteidiger
            Feb 8 at 1:39













          • This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

            – Tamás Barta
            Mar 15 at 22:19











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fsuperuser.com%2fquestions%2f1093157%2farch-grub-disable-booting-message%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          3














          In order to remove that message, go into /boot/grub/grub.cfg. Scroll down until you see the line ### BEGIN /etc/grub.d/10_linux ###. Right below, you'll see something like this:



          menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2' {
          load_video
          set gfxpayload=keep
          insmod gzio
          insmod part_gpt
          insmod fat
          set root='hd1,gpt1'
          if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 AAF7-73DC
          else
          search --no-floppy --fs-uuid --set=root AAF7-73DC
          fi
          echo 'Loading Linux linux-selinux ...'
          linux /vmlinuz-linux-selinux root=UUID=cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2 rw cryptdevice=/dev/sdb3:root security=selinux selinux=1 init=/usr/bin/e4rat-lite-preload
          echo 'Loading initial ramdisk ...'
          initrd /intel-ucode.img /initramfs-linux-selinux.img
          }


          Remove the lines that begin with echo and that boot message will be gone. Add quiet to your kernel parameters to disable boot messages in the kernel.






          share|improve this answer


























          • the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

            – Rainer Verteidiger
            Feb 8 at 1:39













          • This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

            – Tamás Barta
            Mar 15 at 22:19
















          3














          In order to remove that message, go into /boot/grub/grub.cfg. Scroll down until you see the line ### BEGIN /etc/grub.d/10_linux ###. Right below, you'll see something like this:



          menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2' {
          load_video
          set gfxpayload=keep
          insmod gzio
          insmod part_gpt
          insmod fat
          set root='hd1,gpt1'
          if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 AAF7-73DC
          else
          search --no-floppy --fs-uuid --set=root AAF7-73DC
          fi
          echo 'Loading Linux linux-selinux ...'
          linux /vmlinuz-linux-selinux root=UUID=cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2 rw cryptdevice=/dev/sdb3:root security=selinux selinux=1 init=/usr/bin/e4rat-lite-preload
          echo 'Loading initial ramdisk ...'
          initrd /intel-ucode.img /initramfs-linux-selinux.img
          }


          Remove the lines that begin with echo and that boot message will be gone. Add quiet to your kernel parameters to disable boot messages in the kernel.






          share|improve this answer


























          • the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

            – Rainer Verteidiger
            Feb 8 at 1:39













          • This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

            – Tamás Barta
            Mar 15 at 22:19














          3












          3








          3







          In order to remove that message, go into /boot/grub/grub.cfg. Scroll down until you see the line ### BEGIN /etc/grub.d/10_linux ###. Right below, you'll see something like this:



          menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2' {
          load_video
          set gfxpayload=keep
          insmod gzio
          insmod part_gpt
          insmod fat
          set root='hd1,gpt1'
          if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 AAF7-73DC
          else
          search --no-floppy --fs-uuid --set=root AAF7-73DC
          fi
          echo 'Loading Linux linux-selinux ...'
          linux /vmlinuz-linux-selinux root=UUID=cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2 rw cryptdevice=/dev/sdb3:root security=selinux selinux=1 init=/usr/bin/e4rat-lite-preload
          echo 'Loading initial ramdisk ...'
          initrd /intel-ucode.img /initramfs-linux-selinux.img
          }


          Remove the lines that begin with echo and that boot message will be gone. Add quiet to your kernel parameters to disable boot messages in the kernel.






          share|improve this answer















          In order to remove that message, go into /boot/grub/grub.cfg. Scroll down until you see the line ### BEGIN /etc/grub.d/10_linux ###. Right below, you'll see something like this:



          menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2' {
          load_video
          set gfxpayload=keep
          insmod gzio
          insmod part_gpt
          insmod fat
          set root='hd1,gpt1'
          if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt1 --hint-efi=hd1,gpt1 --hint-baremetal=ahci1,gpt1 AAF7-73DC
          else
          search --no-floppy --fs-uuid --set=root AAF7-73DC
          fi
          echo 'Loading Linux linux-selinux ...'
          linux /vmlinuz-linux-selinux root=UUID=cdb0b113-f657-4b1b-a8e9-3fd0fb2c55d2 rw cryptdevice=/dev/sdb3:root security=selinux selinux=1 init=/usr/bin/e4rat-lite-preload
          echo 'Loading initial ramdisk ...'
          initrd /intel-ucode.img /initramfs-linux-selinux.img
          }


          Remove the lines that begin with echo and that boot message will be gone. Add quiet to your kernel parameters to disable boot messages in the kernel.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 29 '16 at 3:21









          oldmud0

          3,12631536




          3,12631536










          answered Dec 29 '16 at 1:12









          h313h313

          177119




          177119













          • the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

            – Rainer Verteidiger
            Feb 8 at 1:39













          • This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

            – Tamás Barta
            Mar 15 at 22:19



















          • the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

            – Rainer Verteidiger
            Feb 8 at 1:39













          • This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

            – Tamás Barta
            Mar 15 at 22:19

















          the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

          – Rainer Verteidiger
          Feb 8 at 1:39







          the answer given by @h313 does not actually achieve what was asked for. Note that the two echo statements begin with "Loading", and not with "Booting". That one is hard-coded into GRUB and in order to remove it, GRUB will need to be patched and recompiled. Alternatively, you may get lucky with github.com/ccontavalli/grub-shusher, which doesn't seem to be maintained, though.

          – Rainer Verteidiger
          Feb 8 at 1:39















          This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

          – Tamás Barta
          Mar 15 at 22:19





          This file starts with "DO NOT EDIT THIS FILE". Because it is auto-generated. Look in /etc/grub.d/ for the files from which it is generated, but I guess those belong to packages, and those may be overwritten as well.

          – Tamás Barta
          Mar 15 at 22:19


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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%2fsuperuser.com%2fquestions%2f1093157%2farch-grub-disable-booting-message%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

          How to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

          is 'sed' thread safe

          How to make a Squid Proxy server?