It doesn't matter. OpenCore is not tied to any OS.You said I should get rid of one of the two copies of OpenCore that I have on my system. Does it make a difference as to which I keep?
It doesn't matter. OpenCore is not tied to any OS.You said I should get rid of one of the two copies of OpenCore that I have on my system. Does it make a difference as to which I keep?
Could I go about reverting from 0.7.0 to 0.6.8 by uninstalling my current OpenCore and then reinstalling the older version?It doesn't matter. OpenCore is not tied to any OS.
Yes, delete your current /EFI and replace it with your 0.6.8 one.Could I go about reverting from 0.7.0 to 0.6.8 by uninstalling my current OpenCore and then reinstalling the older version?
Like is clearly stated on the first post of the thread, Big Sur only works reliably with a MacPro5,1 up to 11.2.3.Question: Should I try to bypass 11.3 and install 11.4?
With a upgraded Mac Pro, OCLP is just a easy way to install OpenCore and won't change at all the Big Sur reliability issues with a MacPro5,1.Does anyone have 11.4 working correctly with OCLP?
OCLP is focused only with Big Sur, while the first post of this thread is applicable to Mojave/Catalina/BigSur and with some tweaks on the first post config you can boot successfully most previous macOS releases supported on a MacPro5,1.Or, should I just reinstall Catalina using OCLP? I figure my mac pro has about 2 years left on Catalina according to Apple support cycles.
Thanks for all the info. I might try the OCLP for Big Sur and see how it comes out. I’d like to consolidate into one machine for a daily driver. My Ryzentosh is great but no sleep and photoshop issues are forcing me out of that pocket.Like is clearly stated on the first post of the thread, Big Sur only works reliably with a MacPro5,1 up to 11.2.3.
If/when a workaround is found the first post will be updated, use 11.2.3 or Catalina until it.
With a upgraded Mac Pro, OCLP is just a easy way to install OpenCore and won't change at all the Big Sur reliability issues with a MacPro5,1.
Read this post below:
![]()
Mac OS 11.3 has broken support for older Mac Pros
I can confidently say that OpenCore Legacy patcher has no benifit over following the MacRumor's guide besides making it simpler for the end user. You'll end up with basically the same product if you put the time and work in. If you want to nitpick, we do add patches some might not care about...forums.macrumors.com
OCLP is focused only with Big Sur, while the first post of this thread is applicable to Mojave/Catalina/BigSur and with some tweaks on the first post config you can boot successfully most previous macOS releases supported on a MacPro5,1.
If this is your production mac, please read trough the link @tsialex gave you, before you do. There are some worst case scenarios you need to know about.Thanks for all the info. I might try the OCLP for Big Sur and see how it comes out. I’d like to consolidate into one machine for a daily driver. My Ryzentosh is great but no sleep and photoshop issues are forcing me out of that pocket.
Big Sur 11.2.3?Hi everyone. I've installed OC 0.7 on a cMP5,1 and installed Big Sur. Great job to everyone involved BTW. I have one minor issue. None of my USB ports work. There's power, but it doesn't detect if anything is connected. I've tried installing USBInjectAll.kext and USB-Mapper.kext but whenever I plug in my wired mouse, it won't even recognise it. I'm pretty sure it's loading OC 0.7 because I see the boot screen and NightShift is working. Has anyone else had the same issue and how did you fix it. I tried looking on the thread for issues similar, but couldn't see anything. Any help is much appreciated.
11.4Big Sur 11.2.3?
Please elaborate?Then it´s normal it doesn´t work in some aspects.
There is a extremely simple way (simple here as in not need to know how the NVRAM works/check free space indicators/validate checksums and etc) to check if the garbage collection failed and the need to reflash with the clean dump:
- Dump the BootROM with ROMTool
No need. Just read previous posts. After 11.2.3 sucks.Please elaborate?
You can read the chip type by inspecting the chip visually.Hello, I tried to verify my NVRAM Garbage Collector, but i'm facing multiples chip ID's...
I have to choose a specific one?
Thanks
Is it possible to help me too, to flash with a clean bootRom (and do like tsialex later, every 3 months, flashing with a clean bootRom) ?PM sent.
No, see why:
- First you can't re-flash the same firmware version or downgrade it. efiflasher checks the EFI version before doing anything.
- Second, the generic image doesn't even have a NVRAM volume, just FFs where the NVRAM is stored. Apple efiflasher completely ignores the NVRAM area of the BootROM image and keep it as is inside the SPI flash memory.
Btw, not just the NVRAM area, but the boot loader, the Firmware Recuperation module and the BootBlock. Just the EFI component of the BootROM image is ever upgraded.
Hi! Thank you for your great tool, i am concern about the free VVS space, my free space was 51000 but after boot to windows downs to 33000 and then after to reboot to windows and return to MacOs was down dramatically to 5200 this is a normal behavior?You can read the chip type by inspecting the chip visually.
but it dont depends with reading.
you can use my dumper what detects the type by trying and with the knowledge what type is in what machine. Also it can calculate free space and some other data points.
![]()
Mac OS 11.3 has broken support for older Mac Pros
for general reference here is a working boot / dump / analyze circle what run thru a garbage collection. #525 I dumped after every boot und did a basic anaylizing with my little dumper / analyze tool. (https://www.dropbox.com/s/gohk7sm6syzeatp/Macschrauber's CMP Rom Dump.zip?dl=0) this was a...forums.macrumors.com
Hi! Thank you for your great tool, i am concern about the free VVS space, my free space was 51000 but after boot to windows downs to 33000 and then after to reboot to windows and return to MacOs was down dramatically to 5200 this is a normal behavior?
Read this and have fun!Please elaborate?
Why people can´t do a minimal effort, @Ausdauersportler ???Read this and have fun!
This is actually a well-known issue. Hot plugging USB 1.x devices into a Mac Pro 5,1 is broken in Big Sur. The workaround is to connect devices through a USB hub. USB 2.0 devices work fine.When I plug in my iPhone, it detects it; when I plug in a wired keyboard, it works; when I plug in a wired mouse, it does nothing. Very odd.
This is probably due to some device. Wake from sleep should work fine even without that kext.I also found that when I put the machine to sleep, it doesn't wake up; even with the HibernateFix kext.
Read this (and have fun, obviously)Hi everyone, Mac Pro 5,1 here, successfully updated to Big Sur, OC updated to 0.7.0.
Everything works great, System Preferences sees the Big Sur 11.4 update, but "cannot" to download it, as if i wasn't connected to internet ... Followed OP full tut, Hybridation technique used, VMM flag off ... What can i do ?