Replies: 6 comments
-
Have you tried with https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/docs/TROUBLESHOOTING.md Also in the config file of OC make sure that you set delete on all Nvram options. I use chain loading on OC from rEFInd on a PC and I use 0.8.7 OC version and there is no hijacking. I disable |
Beta Was this translation helpful? Give feedback.
-
That is an OpenCore Boot Coup. Go to https://forums.macrumors.com/threads/2231693 and look for how to deal with such under
I have heard that a few times and always puzzled about what is so difficult about downloading and running a couple of apps or following an itemised list of actions.
Everything else on the page is background information as I have put virtually everything a user is likely to need on the page so that they don't need to rely on me to resolve most issues but I suppose people simply just don't like reading. They take one look at the stuff written and run away. I suppose I also quite prefer that at the end of the day as it filters a lot of problems out right off the bat. Bottomline is that if you were using MyBootMgr, put in 10 mins to read what is written and followed the instructions on absorbing third party configured OpenCore Ventura when running the MyBootMgr support is only provided on when used on Classic MacPro but it can be used with other units. You just need to replace the OpenCore it creates with yours in such cases. Anyway, you can just go to the hints and tips bit there, look for the boot coup items and sort the issue out. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I will try some suggestions and let you know if I can get it working. dakanji, 10 minutes? I have read that thread several times and spent hours studying it multiple times over the last month. I guess I am just one of the people that don’t get it. Btw, the machine is a 2014 Mac mini. |
Beta Was this translation helpful? Give feedback.
-
I agree that some don't get it indeed. I have found that the main reason for this is that people can struggle to simply follow the instructions and forget all sorts of other stuff they have come across that are swirling about in their minds:
I suppose it is a bit more difficult when not on a Classic MacPro. In such cases, especially for |
Beta Was this translation helpful? Give feedback.
-
I got it working fine on an iMac and Mini by setting BTW, startergo, you mentioned to make sure NVRAM was off but I only found two NVRAM options both were off by default. |
Beta Was this translation helpful? Give feedback.
-
I was referring to the add/delete sections for the NVRAM. If you disable RequestBootVarRouting |
Beta Was this translation helpful? Give feedback.
-
Just got OC to boot Ventura and it works fine. However, I have a bit of a headache and web searches were not fruitful. I have RP and Opencore installed in the same EFI, I just copied the OC directory from the USB to the EFI next to the Refind directory. When I boot into RP I see the OC boot entry fine, and if I select it, OC displays Ventura and that boots fine.
The problem is anytime I use the OC entry, for Ventura or Monterey, it resets booting from RP directly to OC, so the next time the machine boots it's into OC, not RP so no Linux. I looked for something that would stop this but found nothing. I did find on the OC site a mention that in a recent update this was done to prevent something else from booting! Not Good! This is obviously a royal pain since to fix it I have to boot to recovery to install Refind, then boot again to replace Refind with RP, then boot again to what I need. If this can't be resolved I will forgo Ventura. BTW, I also looked at mybootmgr which is way over my head. I was hoping OC had an option to not force itself each time it was booted. Thanks for any help.
see:
https://dortania.github.io/OpenCore-Post-Install/multiboot/bootstrap.html#prerequisites
If everything is set up correctly, the first boot will have OpenCore create a new boot option in our BIOS (pointing to EFI/OC/OpenCore.efi) and future boots will update the entry making sure it's correct and ensuring it is still present. This now allows us to remove BOOTx64.efi and not worry about other OSes overwriting the EFI/BOOT/BOOTx64.efi path.
Beta Was this translation helpful? Give feedback.
All reactions