You erratically put a space before "disk3s1".
From the first picture you should've mounted disk3s1, from the last pic disk2s1. Apparently you mounted the install image, then tried to bless an unmounted image of EFI.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
From the first picture you should've mounted disk3s1, from the last pic disk2s1. Apparently you mounted the install image, then tried to bless an unmounted image of EFI.
Just wanted to thank everyone here for the easy to follow post in setting up OpenCore. I’ve got Big Sur setup on my Mac Pro 5 1 and it’s running great.
I do have a quick question about hardware acceleration. I have an RX 580. What added benefits will I see if I add hardware acceleration to my setup? I mainly use the machine as a HTPC hub and web browsing. I do some Photoshop and Lightroom work from time to time and some light editing in FCP a few times a year.
I do have a quick question about hardware acceleration. I have an RX 580. What added benefits will I see if I add hardware acceleration to my setup? I mainly use the machine as a HTPC hub and web browsing. I do some Photoshop and Lightroom work from time to time and some light editing in FCP a few times a year.
The guide has been updated to OpenCore version 0.6.4.
I'm having trouble running Catalina as a default Startup disk. Booting to the blessed EFI only Big Sur and Mojave are showing up. Catalina is on my NVMe. Doing an Option boot and then selecting EFI enumerates Catalina.
I can run it with boot-args="-no_compat-check" without OpenCore, but lose some of its features like Radeon-RX-580 acceleration and updates.
I should note the EFI partition used is on a std SSD attached to a PCiE controller that also holds Big Sur.
I can run it with boot-args="-no_compat-check" without OpenCore, but lose some of its features like Radeon-RX-580 acceleration and updates.
I should note the EFI partition used is on a std SSD attached to a PCiE controller that also holds Big Sur.
This makes no sense. EFI boot loader searches for files in /ESP/EFI/BOOTx64.efi. Catalina's boot loader is boot.efi in the CoreServices folder on the APFS/HFS+ partition. You have to inspect your EFI folders and see what is where. I would label every folder containing BOOTx64.efi to something meaningful with the disklabel program from OC.
What this means is that Option boot from Cold Start uses the std EFI enumeration and all disks show up. If I then select EFI containing OpenCore to boot next, OpenCore enumerates all disks correctly and shows the Catalina volume with the other ones in the boot selector.
If I let the system boot into the "blessed" EFI openCore boot directly, the Catalina disk does not show up in the boot selector screen. It does show as mouted after one of the enumerated systems like Big Sur boots.
Is there a cache file on the EFI volume that tracks OpenCore NVRAM emulation?
Do you use the Startup Disk in Preferences to set the default or does OpenCore just select the last disk used in its Boot Selector?
Last edited:
Still not clear what you do, but I will recommend you the following:
If you boot with MVC flashed card it tends to hide APFS volumes with OC or RefindPlus. As a workaround I load APFS.efi driver with OC or RefindPlus and it fixes the APFS drives.
Last edited:
Thow speakest in code:
- with MVC flashed card I presume your mean Radeon-RX-580? If yes I have one of those.
- "I load AFFS.efi driver with OC or RefindPlus" and it fixes the APFS drives. - Can you point me where that is described?
I just described it. It was an extensive trial/error workflow which led me to this conclusion. As to why is it so, you better ask @netkas as one of the developers of that ROM.
Thanks. Where is the installation of either described? I just googled but did not see anything not requiring extensive further search.
Have there been any significant changes in OC 0.6.4 that might likely cause a functioning 0.6.3 config.plist to fail? Are there any practical improvements, in regards to lilu, whatevergreen and appleALC for Catalina and/or Big Sur? Any changes related to spoofing the computer model and sensor detection? Any other improvements that might be noteworthy for the average user?
The developers provide a configuration differences file.
The one for v0.6.3 to v0.6.4 is here: https://github.com/acidanthera/Open...f79c8c5a949a/Docs/Differences/Differences.pdf
Nothing new there. I was aware of it and I had previously looked at the relevant information. I didn't notice anything noteworthy, but something might have escaped my attention. After all, there are more expert users here. But, hey, if you don't want to point out noteworthy improvements, no problem.
No idea what you might consider noteworthy but bear in mind that your question had many parts and I only answered the bit about differences that might cause a failure of which the only way to know is to go through that document which I am currently doing and doesn't need expertise.
For instance, I just saw that the "PlayChime" token has been changed from Boolean to String. So I will change my config accordingly.
On the other parts of your question, I don't have an answer hence not quoted in my response but hey, its ok if you feel as you feel.
For instance, I just saw that the "PlayChime" token has been changed from Boolean to String. So I will change my config accordingly.
On the other parts of your question, I don't have an answer hence not quoted in my response but hey, its ok if you feel as you feel.
Configs are generally not compatible between versions.
BlacklistAppleUpdate to block obviously incompatible firmware updates.
Installation of what exactly the APFS.efi driver? You just put it inside the drivers folder and select it in the OC configuration file. You can generate it following this instructions:
RefindPlus/BUILDING.md at GOPFix · dakanji/RefindPlus (github.com)
After you compile RefindPlus you will find the driver in the same folder as the generated refind.efi file.
On the SSD running Big Sur connected via a PCiE eSATA card. I also tried it on the NVMe holding Catalina, but it did not make a difference in drive detection and is not recommended.
Dayo, you mentioned the other day somewhere, that something in 0.6.4 was going to make it possible to copy OC folders in order to create more OC alt setups (with RefindPlus), but it wasn't clear to me what you meant by that or why it would not have been possible with 0.6.3 but would be possible with 0.6.4. Can you elaborate?
Versions up to v0.6.3 needed to be run from a foder named "OC". So in MyBootMgr, I patched the code to allow using an "OC_ALT" folder and the resulting OpenCore.efi could similarly only work out of an "OC_ALT" folder.
You can use any folder name with v0.6.4 following changes made by the devs.
This is as long as you boot through the Bootstrap.efi file in the new folder or boot the Opencore.efi in the new folder directly. The OpenCore BOOTx64.efi file still operates as before and will always use the files in the "OC" folder
Last edited:
I built Refindplus.efi and it does not include AFFS.efi. I also could not find any source googling.
"As a workaround I load AFFS.efi driver with OC or RefindPlus and it fixes the APFS drives."
Sorry be such a pain.