Menu

Not booting to OS picked in Refind menu after restart

free2be
2018-07-24
2018-09-12
  • free2be

    free2be - 2018-07-24

    After upgrading to 0.11.3 lost the function whereas the OS you chose to boot to rebooted to the same OS after restart.
    Background.. I triple boot(OS X, BOOTCAMP, Linux) and as an example if I boot to BOOTCAMP it use to reboot to BOOTCAMP.
    Now when I'm in BOOTCAMP and want to reboot to BOOTCAMP it boots to OS X. Did anthing change between versions that I should be aware of to FIX this like it was before?

     

    Last edit: free2be 2018-07-24
  • Roderick W. Smith

    Thanks for reporting this bug. I've fixed it in the interim git version; or you can download a binary here:

    http://www.rodsbooks.com/refind-bin-0.11.3.1.zip

    Alternatively, you can edit your refind.conf file: Uncomment the default_selection line and ensure that the first value within the quotes is +.

     
    • Chad Myers

      Chad Myers - 2018-09-05

      I tried both 0.11.3 and 0.11.3.1, and I can't get the default selection behavior of the last choice to work. I tried with the default_selection commented out (the default), and with default_selection "+", and neither seem to work in my environment. I dropped back to 0.11.2 and the last choice option is working again.

      My environment is a Mac Pro (5,1) that was running refind 0.10.8 and upgraded to 0.11.3 (and 0.11.3.1). refind was originally installed using --ownhfs, and I didn't change much in refind.conf when going from 0.10.8 to 0.11.3.

      Also, I noticed that 0.11.3 & 0.11.2 are picking up refind installed in the EFI partition on other drives, whereas 0.10.8 didn't. It isn't a problem, it was just unexpected. It's in the ESP as well --ownhfs from when I was testing different installation methods before I settled on using --ownhfs so I could more easily work with refind.conf.

      Cheers!

      -Chad

       
      • Roderick W. Smith

        rEFInd should detect redundant installations of itself on other drives, so your second problem sounds like correct behavior in the new version and a bug in the old one. I've made a number of small changes in the scanning code between 0.10.8 and 0.11.2. Any one of these code changes might account for the change you've seen, although none was intended to change this particular thing.

        As to the main problem, please check refind.conf for a use_nvram option. If it's present, be sure it's set to true. If it's not present, that should work; but you might try adding it and setting it to true. This new token (added with version 0.11.3) gives the choice of using NVRAM vs. disk files to store rEFInd-specific variables. It defaults to true, which should cause rEFInd to store its variables in NVRAM, which is what it always did in earlier versions. Storing variables on hard disk is intended to reduce wear and tear on NVRAM, and to enable rEFInd to work a little better on systems with flaky NVRAMs; however, if you've stored rEFInd on an HFS+ volume, you can't use disk storage for these variables, since rEFInd needs read/write access to its own directory, and Apple's EFI HFS+ implementation is read-only.

         
  • free2be

    free2be - 2018-07-26

    Thanks Rod.
    Working fine again!

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.