10.15.7 update went fine. VMM on - I leave it on as don't feel the small performance hit is a big deal. SecureBootModel is set to Disabled. Catalina initially installed as per first post in this thread. All seems good.
Last edited:
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
I'm an upgrade junky so always have to have the latest OS so maybe not the most unbiased opinion. I do stay away from betas though just because my home computer has become my work computer with COVID and I need it running on a solid platform. I will go to Big Sur once it is officially released and the great OC team puts out the how to wiki. That said, Catalina is working well so you may want to start there and do the OC 0.6.1 install to see how it goes. Once that is done, the Big Sur step should be easy.
this adapter is the problem,
probably is not dual-link DVI capable as needed to run the full 30 "ACD resolution
I've never used clover configurator before. I've only used mac tools and Opencore editing with TextEdit
Can you explain how to let it create a “unique random” serial for an iMac Pro 1.1?
thanks
Hello everyone!
I have a Mac Pro 4,1 flashed to 5,1. I have a Xeon X5680 and AMD Sapphire Radeon RX 560 Video Card.
I want to install OpenCore on a new 120GB SSD I got, but my GPU doesn’t have a boot screen. I am already on Mojave. I still have my old card that isn’t metal-support. I am not sure what to do. Please send help.
I have a Mac Pro 4,1 flashed to 5,1. I have a Xeon X5680 and AMD Sapphire Radeon RX 560 Video Card.
I want to install OpenCore on a new 120GB SSD I got, but my GPU doesn’t have a boot screen. I am already on Mojave. I still have my old card that isn’t metal-support. I am not sure what to do. Please send help.
Does this mean we will have a "simple" installation route (like Catalina is now) for Big Sur with OC when the final version drops?
* Big thank you to everyone working on OC and cMP customizations keeping these great machines humming along with the latest OSes.
Hi David, just download latest clover configurator than on SMBIOS section select iMac Pro 1.1 from the list and click on generate new near the "serial number" field.
Then just pick up one of those for install/update purpose.
attached a screenshot
Attachments
I can confirm, just updated to Big Sur beta 9 and without the VMM flag it works perfectly.
this latest build for me has also resolved the Opencore boot "issue" when on older releases I saw "preboot" entry under the Big Sur partition instead of the real partition name.
can you write what you did to install BigSur?
I have MP 5.1 OpenCore 0.6.1and Catalina 10.15.7 and everything works as it should,
unfortunately, attempts to install BigSur have no effect
Last edited:
I installed Big Sur Beta 9 last night on my MacPro4,1(5,1) running OpenCore 0.6.1 with RX580.
Odd thing is that HEVC hardware acceleration is now listed as unavailable by VideoProc. Only H264 is listed as available.
To troubleshoot, I booted into macOS Catalina with the same exact hardware and OpenCore configuration, and Video Proc reported that both HEVC and H264 hardware acceleration are available.
Does anyone know how to resolve this and get HEVC hardware acceleration back? I have not encountered this issue in the prior Big Sur betas, so I assume Apple did something to Beta 9.
Odd thing is that HEVC hardware acceleration is now listed as unavailable by VideoProc. Only H264 is listed as available.
To troubleshoot, I booted into macOS Catalina with the same exact hardware and OpenCore configuration, and Video Proc reported that both HEVC and H264 hardware acceleration are available.
Does anyone know how to resolve this and get HEVC hardware acceleration back? I have not encountered this issue in the prior Big Sur betas, so I assume Apple did something to Beta 9.
Attachments
You right!!!
They might have done something this time, because I have the same... Well I am gonna have to look into it too, or maybe because video proc needs an update I do not know.
Looking into now...
Well updating VideoProc did not do anything but they then they really did something this time...
Apple when you hold us!!!!
I don't actually KNOW, but I strongly suspect that a new version of whatevergreen.kext may be required.
How I'll be home to throw you my EFI folder to install Big Sur.
Thanks for the reply. I got OpenCore installed. Finally got the boot selector to show up. So now I am trying to install Windows 10. I followed the steps and tried 3 different USB drives, but none of them show up in the boot selector.
I used Mac to format the USB into the exFat MBR, copied the windows iso with rsync to the USB. Updated the config and copied over the exFatDxeLegacy.efi to the drivers folder and added the line to the drivers array in config. Not sure what I am doing wrong.
Edit: I figured it out, there is a mistake for following the copy command too closely.
I used Mac to format the USB into the exFat MBR, copied the windows iso with rsync to the USB. Updated the config and copied over the exFatDxeLegacy.efi to the drivers folder and added the line to the drivers array in config. Not sure what I am doing wrong.
Edit: I figured it out, there is a mistake for following the copy command too closely.
Last edited:
Hi, just want to add some findings about SecureBootModel and big sur beta 9 (maybe other betas too?) that maybe you didn't notice.
I don't have a mac pro, but this should be the same..If you are able to boot with "Disabled" or "Default" you will notice that with Disabled you are booting from a snapshot, with Default you are not booting from a snapshot, but directly from the big sur system disk.
I noticed this during the upgrade from beta8 to beta9, because I received Download failed error and I noticed that with SecureBootModel Default mounting / for read and write returned error 77 (because of sip enabled) instead of error 66.
Setting it to Disabled returned error 66.
I don't know if this is an expected behavior, but as far as I remember with the setting to Default I was able to update from beta 7 to beta 8.
I don't have a mac pro, but this should be the same..If you are able to boot with "Disabled" or "Default" you will notice that with Disabled you are booting from a snapshot, with Default you are not booting from a snapshot, but directly from the big sur system disk.
I noticed this during the upgrade from beta8 to beta9, because I received Download failed error and I noticed that with SecureBootModel Default mounting / for read and write returned error 77 (because of sip enabled) instead of error 66.
Setting it to Disabled returned error 66.
I don't know if this is an expected behavior, but as far as I remember with the setting to Default I was able to update from beta 7 to beta 8.
Last edited:
I guess you referred to a previous opencore version 0.6.0 , but seems from 0.6.1 setting SecureBootModel Disabled is required to boot BigSur on unsupported Mac, and either with Disabled you can have a snapshot booting and OTA update, while to disable snapshot booting this should work to fix "sudo mount -uw /":
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28958380
while to make a new bootable snapshot simply:
I add also that from recent BigSur releases to disable SIP without a "Custom Configuration" this value for OpenCore worked csr-active-config:
https://forums.macrumors.com/thread...unsupported-macs-thread.2242172/post-28958380
while to make a new bootable snapshot simply:
sudo bless --folder /System/Library/CoreServices --create-snapshotI add also that from recent BigSur releases to disable SIP without a "Custom Configuration" this value for OpenCore worked csr-active-config:
fwgAAA== , for @startergo and @Dayo customised refindGOP this new value 0x87F for BigSur correctly disabled SIP.
Last edited: