Grub menu at boot time… “holding shift” not working












14















I read here at this thread that holding Shift during boot can bring up the GRUB menu. However I try holding one or the other Shift keys, tapping, tapping then holding, nothing works. Am I missing something? How does one access the GRUB menu during boot time?



No dual boot here, just standard Lubuntu 14.04 install.










share|improve this question




















  • 7





    It depends on the hardware. Sometimes ESC works.

    – Pilot6
    Sep 1 '15 at 10:17











  • Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

    – colorful-shirts
    Sep 1 '15 at 21:17






  • 1





    Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

    – clearkimura
    Oct 6 '15 at 14:54
















14















I read here at this thread that holding Shift during boot can bring up the GRUB menu. However I try holding one or the other Shift keys, tapping, tapping then holding, nothing works. Am I missing something? How does one access the GRUB menu during boot time?



No dual boot here, just standard Lubuntu 14.04 install.










share|improve this question




















  • 7





    It depends on the hardware. Sometimes ESC works.

    – Pilot6
    Sep 1 '15 at 10:17











  • Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

    – colorful-shirts
    Sep 1 '15 at 21:17






  • 1





    Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

    – clearkimura
    Oct 6 '15 at 14:54














14












14








14


5






I read here at this thread that holding Shift during boot can bring up the GRUB menu. However I try holding one or the other Shift keys, tapping, tapping then holding, nothing works. Am I missing something? How does one access the GRUB menu during boot time?



No dual boot here, just standard Lubuntu 14.04 install.










share|improve this question
















I read here at this thread that holding Shift during boot can bring up the GRUB menu. However I try holding one or the other Shift keys, tapping, tapping then holding, nothing works. Am I missing something? How does one access the GRUB menu during boot time?



No dual boot here, just standard Lubuntu 14.04 install.







boot grub2 lubuntu






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:23









Community

1




1










asked Sep 1 '15 at 10:15









colorful-shirtscolorful-shirts

71116




71116








  • 7





    It depends on the hardware. Sometimes ESC works.

    – Pilot6
    Sep 1 '15 at 10:17











  • Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

    – colorful-shirts
    Sep 1 '15 at 21:17






  • 1





    Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

    – clearkimura
    Oct 6 '15 at 14:54














  • 7





    It depends on the hardware. Sometimes ESC works.

    – Pilot6
    Sep 1 '15 at 10:17











  • Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

    – colorful-shirts
    Sep 1 '15 at 21:17






  • 1





    Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

    – clearkimura
    Oct 6 '15 at 14:54








7




7





It depends on the hardware. Sometimes ESC works.

– Pilot6
Sep 1 '15 at 10:17





It depends on the hardware. Sometimes ESC works.

– Pilot6
Sep 1 '15 at 10:17













Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

– colorful-shirts
Sep 1 '15 at 21:17





Gave ESC a try too. That key is used by my BIOS to enter its settings menu. I tried ESC after the BIOS splash screen just before the Ubuntu splash but no luck either. I just can't seem to get in there on this machine (ASUS X200M). No problem with other machines.

– colorful-shirts
Sep 1 '15 at 21:17




1




1





Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

– clearkimura
Oct 6 '15 at 14:54





Another factor would be timing to press. Press and hold Esc key after the BIOS splash screen worked for me. Pressing earlier would land me to CSM screen (since I have disabled Secure boot). I can just suggest timing.

– clearkimura
Oct 6 '15 at 14:54










3 Answers
3






active

oldest

votes


















12














I also cannot access the GRUB menu by any manner of pressing shift or esc on my Asus X205TA. To get the GRUB menu to display at boot, I had to modify the /etc/default/grub file. See this page.



To get the GRUB menu to display every time (until I change it back) I used nano to edit the file in the terminal. Type:



sudo nano /etc/default/grub


find the line that says GRUB_HIDDEN_TIMEOUT=0 or GRUB_TIMEOUT_STYLE=hidden
put # at the start of this line to comment it out



#GRUB_HIDDEN_TIMEOUT=0


or



#GRUB_TIMEOUT_STYLE=hidden


and make sure GRUB_TIMEOUT=10 or some other number bigger than zero. When done exit nano saving changes and run



sudo update-grub





share|improve this answer


























  • I'm very late getting back to this, but this worked for me too, thank you!

    – colorful-shirts
    Jun 9 '17 at 13:15






  • 1





    Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

    – Limok Palantaemon
    Jan 20 at 11:01






  • 1





    @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

    – Zanna
    Jan 20 at 20:11





















6














I have an X200MA. To enter the GRUB menu, you press Esc while booting. Choose Ubuntu to boot normally.



You may have problems if you installed Ubuntu not in UEFI mode. I did not test it that way.






share|improve this answer


























  • shift wasn't working for me, esc did work. thanks.

    – Alexander Mills
    Jun 12 '17 at 3:27



















1














I had the same problem. The system would boot directly and my monitor would be in out-of-range mode. I pressed repeatedly until I thought GRUB was waiting for a command, then I pressed , Enter, to select recovery mode.



It took a few tries or randomness, but when I entered recovery mode the display came back. I then:




  1. Selected root for a root prompt

  2. Ran mount -o rw,remount / to mount the filesystem in read-write mode

  3. Ran vi /etc/default/grub

  4. Removed # from GRUB_TERMINAL=console

  5. Saved the file

  6. Ran update-grub to update GRUB

  7. Ran exit to return to the menu and continue booting


GRUB would show up, the monitor would work, and then I could log in.






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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%2faskubuntu.com%2fquestions%2f668049%2fgrub-menu-at-boot-time-holding-shift-not-working%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    12














    I also cannot access the GRUB menu by any manner of pressing shift or esc on my Asus X205TA. To get the GRUB menu to display at boot, I had to modify the /etc/default/grub file. See this page.



    To get the GRUB menu to display every time (until I change it back) I used nano to edit the file in the terminal. Type:



    sudo nano /etc/default/grub


    find the line that says GRUB_HIDDEN_TIMEOUT=0 or GRUB_TIMEOUT_STYLE=hidden
    put # at the start of this line to comment it out



    #GRUB_HIDDEN_TIMEOUT=0


    or



    #GRUB_TIMEOUT_STYLE=hidden


    and make sure GRUB_TIMEOUT=10 or some other number bigger than zero. When done exit nano saving changes and run



    sudo update-grub





    share|improve this answer


























    • I'm very late getting back to this, but this worked for me too, thank you!

      – colorful-shirts
      Jun 9 '17 at 13:15






    • 1





      Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

      – Limok Palantaemon
      Jan 20 at 11:01






    • 1





      @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

      – Zanna
      Jan 20 at 20:11


















    12














    I also cannot access the GRUB menu by any manner of pressing shift or esc on my Asus X205TA. To get the GRUB menu to display at boot, I had to modify the /etc/default/grub file. See this page.



    To get the GRUB menu to display every time (until I change it back) I used nano to edit the file in the terminal. Type:



    sudo nano /etc/default/grub


    find the line that says GRUB_HIDDEN_TIMEOUT=0 or GRUB_TIMEOUT_STYLE=hidden
    put # at the start of this line to comment it out



    #GRUB_HIDDEN_TIMEOUT=0


    or



    #GRUB_TIMEOUT_STYLE=hidden


    and make sure GRUB_TIMEOUT=10 or some other number bigger than zero. When done exit nano saving changes and run



    sudo update-grub





    share|improve this answer


























    • I'm very late getting back to this, but this worked for me too, thank you!

      – colorful-shirts
      Jun 9 '17 at 13:15






    • 1





      Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

      – Limok Palantaemon
      Jan 20 at 11:01






    • 1





      @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

      – Zanna
      Jan 20 at 20:11
















    12












    12








    12







    I also cannot access the GRUB menu by any manner of pressing shift or esc on my Asus X205TA. To get the GRUB menu to display at boot, I had to modify the /etc/default/grub file. See this page.



    To get the GRUB menu to display every time (until I change it back) I used nano to edit the file in the terminal. Type:



    sudo nano /etc/default/grub


    find the line that says GRUB_HIDDEN_TIMEOUT=0 or GRUB_TIMEOUT_STYLE=hidden
    put # at the start of this line to comment it out



    #GRUB_HIDDEN_TIMEOUT=0


    or



    #GRUB_TIMEOUT_STYLE=hidden


    and make sure GRUB_TIMEOUT=10 or some other number bigger than zero. When done exit nano saving changes and run



    sudo update-grub





    share|improve this answer















    I also cannot access the GRUB menu by any manner of pressing shift or esc on my Asus X205TA. To get the GRUB menu to display at boot, I had to modify the /etc/default/grub file. See this page.



    To get the GRUB menu to display every time (until I change it back) I used nano to edit the file in the terminal. Type:



    sudo nano /etc/default/grub


    find the line that says GRUB_HIDDEN_TIMEOUT=0 or GRUB_TIMEOUT_STYLE=hidden
    put # at the start of this line to comment it out



    #GRUB_HIDDEN_TIMEOUT=0


    or



    #GRUB_TIMEOUT_STYLE=hidden


    and make sure GRUB_TIMEOUT=10 or some other number bigger than zero. When done exit nano saving changes and run



    sudo update-grub






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jan 20 at 20:08

























    answered Apr 7 '16 at 15:27









    ZannaZanna

    50.9k13137241




    50.9k13137241













    • I'm very late getting back to this, but this worked for me too, thank you!

      – colorful-shirts
      Jun 9 '17 at 13:15






    • 1





      Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

      – Limok Palantaemon
      Jan 20 at 11:01






    • 1





      @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

      – Zanna
      Jan 20 at 20:11





















    • I'm very late getting back to this, but this worked for me too, thank you!

      – colorful-shirts
      Jun 9 '17 at 13:15






    • 1





      Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

      – Limok Palantaemon
      Jan 20 at 11:01






    • 1





      @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

      – Zanna
      Jan 20 at 20:11



















    I'm very late getting back to this, but this worked for me too, thank you!

    – colorful-shirts
    Jun 9 '17 at 13:15





    I'm very late getting back to this, but this worked for me too, thank you!

    – colorful-shirts
    Jun 9 '17 at 13:15




    1




    1





    Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

    – Limok Palantaemon
    Jan 20 at 11:01





    Just commenting since I tried this: something may have been updated since this doesn't work for me (Ubuntu 18.04). My /etc/default/grub didn't have a GRUB_HIDDEN_TIMEOUT line, however this may have been replaced by GRUB_TIMEOUT_STYLE=hidden. Should I replace that with something else to mimic your solution, and do you know what that should be?

    – Limok Palantaemon
    Jan 20 at 11:01




    1




    1





    @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

    – Zanna
    Jan 20 at 20:11







    @LimokPalantaemon thank you for the extremely helpful comment! Every time the package maintainer has changed the /etc/default/grub file I have kept my edited version (because I use many boot parameters as well as forcing the GRUB menu to appear). Thanks to you I checked the new version and tested it, and updated my answer here. This version forces the menu successfully. Now I just need to try to find all the places where I mentioned this and correct those too O.O

    – Zanna
    Jan 20 at 20:11















    6














    I have an X200MA. To enter the GRUB menu, you press Esc while booting. Choose Ubuntu to boot normally.



    You may have problems if you installed Ubuntu not in UEFI mode. I did not test it that way.






    share|improve this answer


























    • shift wasn't working for me, esc did work. thanks.

      – Alexander Mills
      Jun 12 '17 at 3:27
















    6














    I have an X200MA. To enter the GRUB menu, you press Esc while booting. Choose Ubuntu to boot normally.



    You may have problems if you installed Ubuntu not in UEFI mode. I did not test it that way.






    share|improve this answer


























    • shift wasn't working for me, esc did work. thanks.

      – Alexander Mills
      Jun 12 '17 at 3:27














    6












    6








    6







    I have an X200MA. To enter the GRUB menu, you press Esc while booting. Choose Ubuntu to boot normally.



    You may have problems if you installed Ubuntu not in UEFI mode. I did not test it that way.






    share|improve this answer















    I have an X200MA. To enter the GRUB menu, you press Esc while booting. Choose Ubuntu to boot normally.



    You may have problems if you installed Ubuntu not in UEFI mode. I did not test it that way.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Jan 21 '18 at 6:49









    Chai T. Rex

    4,17711536




    4,17711536










    answered Sep 1 '15 at 21:30









    Pilot6Pilot6

    53k15108197




    53k15108197













    • shift wasn't working for me, esc did work. thanks.

      – Alexander Mills
      Jun 12 '17 at 3:27



















    • shift wasn't working for me, esc did work. thanks.

      – Alexander Mills
      Jun 12 '17 at 3:27

















    shift wasn't working for me, esc did work. thanks.

    – Alexander Mills
    Jun 12 '17 at 3:27





    shift wasn't working for me, esc did work. thanks.

    – Alexander Mills
    Jun 12 '17 at 3:27











    1














    I had the same problem. The system would boot directly and my monitor would be in out-of-range mode. I pressed repeatedly until I thought GRUB was waiting for a command, then I pressed , Enter, to select recovery mode.



    It took a few tries or randomness, but when I entered recovery mode the display came back. I then:




    1. Selected root for a root prompt

    2. Ran mount -o rw,remount / to mount the filesystem in read-write mode

    3. Ran vi /etc/default/grub

    4. Removed # from GRUB_TERMINAL=console

    5. Saved the file

    6. Ran update-grub to update GRUB

    7. Ran exit to return to the menu and continue booting


    GRUB would show up, the monitor would work, and then I could log in.






    share|improve this answer






























      1














      I had the same problem. The system would boot directly and my monitor would be in out-of-range mode. I pressed repeatedly until I thought GRUB was waiting for a command, then I pressed , Enter, to select recovery mode.



      It took a few tries or randomness, but when I entered recovery mode the display came back. I then:




      1. Selected root for a root prompt

      2. Ran mount -o rw,remount / to mount the filesystem in read-write mode

      3. Ran vi /etc/default/grub

      4. Removed # from GRUB_TERMINAL=console

      5. Saved the file

      6. Ran update-grub to update GRUB

      7. Ran exit to return to the menu and continue booting


      GRUB would show up, the monitor would work, and then I could log in.






      share|improve this answer




























        1












        1








        1







        I had the same problem. The system would boot directly and my monitor would be in out-of-range mode. I pressed repeatedly until I thought GRUB was waiting for a command, then I pressed , Enter, to select recovery mode.



        It took a few tries or randomness, but when I entered recovery mode the display came back. I then:




        1. Selected root for a root prompt

        2. Ran mount -o rw,remount / to mount the filesystem in read-write mode

        3. Ran vi /etc/default/grub

        4. Removed # from GRUB_TERMINAL=console

        5. Saved the file

        6. Ran update-grub to update GRUB

        7. Ran exit to return to the menu and continue booting


        GRUB would show up, the monitor would work, and then I could log in.






        share|improve this answer















        I had the same problem. The system would boot directly and my monitor would be in out-of-range mode. I pressed repeatedly until I thought GRUB was waiting for a command, then I pressed , Enter, to select recovery mode.



        It took a few tries or randomness, but when I entered recovery mode the display came back. I then:




        1. Selected root for a root prompt

        2. Ran mount -o rw,remount / to mount the filesystem in read-write mode

        3. Ran vi /etc/default/grub

        4. Removed # from GRUB_TERMINAL=console

        5. Saved the file

        6. Ran update-grub to update GRUB

        7. Ran exit to return to the menu and continue booting


        GRUB would show up, the monitor would work, and then I could log in.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jan 21 '18 at 6:45









        Chai T. Rex

        4,17711536




        4,17711536










        answered Jan 21 '18 at 5:24









        user254450user254450

        312




        312






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • 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%2faskubuntu.com%2fquestions%2f668049%2fgrub-menu-at-boot-time-holding-shift-not-working%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

            mysqli_query(): Empty query in /home/lucindabrummitt/public_html/blog/wp-includes/wp-db.php on line 1924

            How to change which sound is reproduced for terminal bell?

            Can I use Tabulator js library in my java Spring + Thymeleaf project?