rEFInd Boot Manager stopped working after installing Ubuntu 17- MacBook Pro Dual Boot

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I just installed Ubuntu 17 on my mid-2012 MacBook Pro to dual boot with MacOS X. I'm new to Ubuntu. During installation I used rEFInd as a boot manager and it worked perfectly while testing Ubuntu on my computer, but after installing Ubuntu, rEFInd no longer works. I now have to use the option key to choose which OS to boot, and if I don't hold down the option key at startup, the computer automatically boots Ubuntu. Any help to get rEFInd working again as my boot manager would be appreciated.










share|improve this question

























    up vote
    1
    down vote

    favorite












    I just installed Ubuntu 17 on my mid-2012 MacBook Pro to dual boot with MacOS X. I'm new to Ubuntu. During installation I used rEFInd as a boot manager and it worked perfectly while testing Ubuntu on my computer, but after installing Ubuntu, rEFInd no longer works. I now have to use the option key to choose which OS to boot, and if I don't hold down the option key at startup, the computer automatically boots Ubuntu. Any help to get rEFInd working again as my boot manager would be appreciated.










    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I just installed Ubuntu 17 on my mid-2012 MacBook Pro to dual boot with MacOS X. I'm new to Ubuntu. During installation I used rEFInd as a boot manager and it worked perfectly while testing Ubuntu on my computer, but after installing Ubuntu, rEFInd no longer works. I now have to use the option key to choose which OS to boot, and if I don't hold down the option key at startup, the computer automatically boots Ubuntu. Any help to get rEFInd working again as my boot manager would be appreciated.










      share|improve this question













      I just installed Ubuntu 17 on my mid-2012 MacBook Pro to dual boot with MacOS X. I'm new to Ubuntu. During installation I used rEFInd as a boot manager and it worked perfectly while testing Ubuntu on my computer, but after installing Ubuntu, rEFInd no longer works. I now have to use the option key to choose which OS to boot, and if I don't hold down the option key at startup, the computer automatically boots Ubuntu. Any help to get rEFInd working again as my boot manager would be appreciated.







      dual-boot macbook-pro refind






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Mar 29 at 17:45









      Mitch Romney

      61




      61




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          1
          down vote













          I had the same issue as you.
          Resolved it by changing BootOrder using efibootmgr from within Ubuntu.



          Before



          # sudo efibootmgr 
          BootCurrent: 0000
          Timeout: 5 seconds
          BootOrder: 0000,0080
          Boot0000* ubuntu
          Boot0080* Mac OS X
          Boot0081* Recovery OS
          Boot0082*
          BootFFFF*


          Change order



          # sudo efibootmgr -o 0080,0000


          After



          # sudo efibootmgr 
          BootCurrent: 0080
          Timeout: 5 seconds
          BootOrder: 0080,0000
          Boot0000* ubuntu
          Boot0080* Mac OS X
          Boot0081* Recovery OS
          Boot0082*
          BootFFFF*





          share|improve this answer



























            up vote
            0
            down vote













            I experienced this. What worked for me was to re install rEFInd every time I installed a new OS. You may do so by launching a terminal inside the recovery mode and navigating to the rEFInd folder (usually on an external dev) where the installation file is, then you can run the installation file. Good luck.






            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',
              convertImagesToLinks: true,
              noModals: false,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              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%2f1020340%2frefind-boot-manager-stopped-working-after-installing-ubuntu-17-macbook-pro-dual%23new-answer', 'question_page');

              );

              Post as a guest






























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              1
              down vote













              I had the same issue as you.
              Resolved it by changing BootOrder using efibootmgr from within Ubuntu.



              Before



              # sudo efibootmgr 
              BootCurrent: 0000
              Timeout: 5 seconds
              BootOrder: 0000,0080
              Boot0000* ubuntu
              Boot0080* Mac OS X
              Boot0081* Recovery OS
              Boot0082*
              BootFFFF*


              Change order



              # sudo efibootmgr -o 0080,0000


              After



              # sudo efibootmgr 
              BootCurrent: 0080
              Timeout: 5 seconds
              BootOrder: 0080,0000
              Boot0000* ubuntu
              Boot0080* Mac OS X
              Boot0081* Recovery OS
              Boot0082*
              BootFFFF*





              share|improve this answer
























                up vote
                1
                down vote













                I had the same issue as you.
                Resolved it by changing BootOrder using efibootmgr from within Ubuntu.



                Before



                # sudo efibootmgr 
                BootCurrent: 0000
                Timeout: 5 seconds
                BootOrder: 0000,0080
                Boot0000* ubuntu
                Boot0080* Mac OS X
                Boot0081* Recovery OS
                Boot0082*
                BootFFFF*


                Change order



                # sudo efibootmgr -o 0080,0000


                After



                # sudo efibootmgr 
                BootCurrent: 0080
                Timeout: 5 seconds
                BootOrder: 0080,0000
                Boot0000* ubuntu
                Boot0080* Mac OS X
                Boot0081* Recovery OS
                Boot0082*
                BootFFFF*





                share|improve this answer






















                  up vote
                  1
                  down vote










                  up vote
                  1
                  down vote









                  I had the same issue as you.
                  Resolved it by changing BootOrder using efibootmgr from within Ubuntu.



                  Before



                  # sudo efibootmgr 
                  BootCurrent: 0000
                  Timeout: 5 seconds
                  BootOrder: 0000,0080
                  Boot0000* ubuntu
                  Boot0080* Mac OS X
                  Boot0081* Recovery OS
                  Boot0082*
                  BootFFFF*


                  Change order



                  # sudo efibootmgr -o 0080,0000


                  After



                  # sudo efibootmgr 
                  BootCurrent: 0080
                  Timeout: 5 seconds
                  BootOrder: 0080,0000
                  Boot0000* ubuntu
                  Boot0080* Mac OS X
                  Boot0081* Recovery OS
                  Boot0082*
                  BootFFFF*





                  share|improve this answer












                  I had the same issue as you.
                  Resolved it by changing BootOrder using efibootmgr from within Ubuntu.



                  Before



                  # sudo efibootmgr 
                  BootCurrent: 0000
                  Timeout: 5 seconds
                  BootOrder: 0000,0080
                  Boot0000* ubuntu
                  Boot0080* Mac OS X
                  Boot0081* Recovery OS
                  Boot0082*
                  BootFFFF*


                  Change order



                  # sudo efibootmgr -o 0080,0000


                  After



                  # sudo efibootmgr 
                  BootCurrent: 0080
                  Timeout: 5 seconds
                  BootOrder: 0080,0000
                  Boot0000* ubuntu
                  Boot0080* Mac OS X
                  Boot0081* Recovery OS
                  Boot0082*
                  BootFFFF*






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 6 at 13:51









                  klippo

                  111




                  111






















                      up vote
                      0
                      down vote













                      I experienced this. What worked for me was to re install rEFInd every time I installed a new OS. You may do so by launching a terminal inside the recovery mode and navigating to the rEFInd folder (usually on an external dev) where the installation file is, then you can run the installation file. Good luck.






                      share|improve this answer
























                        up vote
                        0
                        down vote













                        I experienced this. What worked for me was to re install rEFInd every time I installed a new OS. You may do so by launching a terminal inside the recovery mode and navigating to the rEFInd folder (usually on an external dev) where the installation file is, then you can run the installation file. Good luck.






                        share|improve this answer






















                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          I experienced this. What worked for me was to re install rEFInd every time I installed a new OS. You may do so by launching a terminal inside the recovery mode and navigating to the rEFInd folder (usually on an external dev) where the installation file is, then you can run the installation file. Good luck.






                          share|improve this answer












                          I experienced this. What worked for me was to re install rEFInd every time I installed a new OS. You may do so by launching a terminal inside the recovery mode and navigating to the rEFInd folder (usually on an external dev) where the installation file is, then you can run the installation file. Good luck.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Apr 7 at 18:26









                          Reza Rahemi

                          10911




                          10911



























                               

                              draft saved


                              draft discarded















































                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020340%2frefind-boot-manager-stopped-working-after-installing-ubuntu-17-macbook-pro-dual%23new-answer', 'question_page');

                              );

                              Post as a guest













































































                              Popular posts from this blog

                              pylint3 and pip3 broken

                              Missing snmpget and snmpwalk

                              How to enroll fingerprints to Ubuntu 17.10 with VFS491