Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I'll add that and try it. I might reinstall Big Sur, I have a feeling something got messed up during the update.
 
startergo said:
Yes there is an error. @cdf SecureBootModel needs to be either properly set (not only through the config file) or disabled.
Click to expand...

With SecureBootModel set to default, I have no trouble booting. The manual indicates that outdated manifests on the preboot partition can cause boot failure. Perhaps faulty (or patched) installs could be at cause here.
 
  • Like
Reactions: jackluke
cdf said:
With SecureBootModel set to default, I have no trouble booting. The manual indicates that outdated manifests on the preboot partition can cause boot failure. Perhaps faulty (or patched) installs could be at cause here.
Click to expand...
Interesting. Is this with the latest BigSur?
 
startergo said:
Yes there is an error. @cdf SecureBootModel needs to be either properly set (not only through the config file) or disabled. So for BigSur you will also need the board-id. The attached config file should let you boot. Let me know if it does not.
Click to expand...
Will check tomorrow. It does sound VERY reasonable. For the time being, I've added, without testing it, the "Disabled" parameter to "my" 0.6.1 config.plist. Would there be any benefits in setting it to something different, like "Default"? If so, what other settings, kexts or whatever should be added to config.plist or to OC itself?
 
startergo said:
Code: 
OCS: Missing key SysReport, context <Debug>!
Click to expand...

I reinstalled Big Sur and then used SMB spoofing to download the update to Beta 8. Downloaded the update and restarted. When it goes to the updater the Apple logo shows up and then it begins it's loop. Booted into Catalina and toggled VMM on. Update installed. Booted into Beta 8 and it was fine. Then I turned off VMM. Have the same issue. Apple logo shows and then screen goes black and OpenCore restarts.

Has anyone had any issues updating to Beta 8?
 
HuRR said:
I reinstalled Big Sur and then used SMB spoofing to download the update to Beta 8. Downloaded the update and restarted. When it goes to the updater the Apple logo shows up and then it begins it's loop. Booted into Catalina and toggled VMM on. Update installed. Booted into Beta 8 and it was fine. Then I turned off VMM. Have the same issue. Apple logo shows and then screen goes black and OpenCore restarts.

Has anyone had any issues updating to Beta 8?
Click to expand...

Starting in Big Sur beta 7, the VMM flag in the config.plist for the Mac Pro 4,1/5,1 needs to be turned on. If turned off, the boot won't complete and it will crash and ask you to restart. Same in beta 8. Beta 6 does not have such issue.
 
i.am.not.a.hipster said:
Starting in Big Sur beta 7, the VMM flag in the config.plist for the Mac Pro 4,1/5,1 needs to be turned on. If turned off, the boot won't complete and it will crash and ask you to restart. Same in beta 8. Beta 6 does not have such issue.
Click to expand...

Really? Hmm. I don't think I had VMM on when I updated to Beta 7. I wonder if it'll change in the future OpenCore and Big Sur releases.
 
HuRR said:
I reinstalled Big Sur and then used SMB spoofing to download the update to Beta 8. Downloaded the update and restarted. When it goes to the updater the Apple logo shows up and then it begins it's loop. Booted into Catalina and toggled VMM on. Update installed. Booted into Beta 8 and it was fine. Then I turned off VMM. Have the same issue. Apple logo shows and then screen goes black and OpenCore restarts.

Has anyone had any issues updating to Beta 8?
Click to expand...
Can you provide a debug log?
 
i.am.not.a.hipster said:
Starting in Big Sur beta 7, the VMM flag in the config.plist for the Mac Pro 4,1/5,1 needs to be turned on. If turned off, the boot won't complete and it will crash and ask you to restart. Same in beta 8. Beta 6 does not have such issue.
Click to expand...
You can add iMacPro in the SMBIOS instead of the VMM flag
 
startergo said:
Yes there is an error. @cdf SecureBootModel needs to be either properly set (not only through the config file) or disabled. So for BigSur you will also need the board-id. The attached config file should let you boot. Let me know if it does not.
Click to expand...
I can now confirm that OC 0.6.1 became fully functional for me immediately after setting SecureBootModel to "Disabled". Many thanks! I suppose that, in order to set that to "Default" or some other value, something extra should be added to config.plist. What would the benefits of doing so be? If there is a plus side to such a change, can you provide the relevant parameters and explain what they would achieve?
 
  • Like
Reactions: roobarb! and kcarney81
cdf said:
No. As explained above, "Default" works with unmodified installations. That is kind of the point of the security model.
Click to expand...
You are probably right, but there's something that doesn't add up. You see, in all my previous failed attempts (at least a couple dozens) at booting OC 0.6.1, the Boot Picker offered me the choice to boot Catalina (installed by dosdude1's patcher, although, other than NightShift, it didn't actually patch anything), High Sierra (entirely vanilla) and Snow Leopard (not modified in any way). No matter what operating system I chose on the Boot Picker, it looped back to itself. If the Picker was fussy about the way Catalina was initially installed, I might understand why it rejected that operating system and looped back to itself, but I can't understand why it would behave exactly the same way when trying to boot High Sierra or Snow Leopard.
 
Aloha together,

maybe I forgot to read something but today the following happen:

I use the OC 0.6.1 Folder from @h9826790 and it worked perfect. Today I edit the config.plist (only the VMM flag) to update from 10.15.6 to 10.15.7. It worked. After the install and reboot I go open up the Terminal to make some folder visible (SetFile -a v) but I got a:

--($:/)-- sudo mount -uw /
mount_apfs: volume could not be mounted: Operation not permitted
mount: / failed with 77
Click to expand...

I remember then (10 sec. after) that I had see this long time ago... I verify it:

--($:/)-- csrutil status
System Integrity Protection status: enabled.
Click to expand...

...and see that the macos 10.15.7 Updater has made also a SIP Update of my machine - or I made something wrong but yesterday SIP was disabled - definitely.
 
PeterHolbrook said:
You are probably right, but there's something that doesn't add up. You see, in all my previous failed attempts (at least a couple dozens) at booting OC 0.6.1, the Boot Picker offered me the choice to boot Catalina (installed by dosdude1's patcher, although, other than NightShift, it didn't actually patch anything), High Sierra (entirely vanilla) and Snow Leopard (not modified in any way). No matter what operating system I chose on the Boot Picker, it looped back to itself. If the Picker was fussy about the way Catalina was initially installed, I might understand why it rejected that operating system and looped back to itself, but I can't understand why it would behave exactly the same way when trying to boot High Sierra or Snow Leopard.
Click to expand...

There are apparently two things going on here: The default option sets the hardware model to iMac Pro for secure boot. That means that even vanilla installations of macOS versions predating the iMac Pro will not boot.
 
  • Like
Reactions: PeterHolbrook
cdf said:
There are apparently two things going on here: The default option sets the hardware model to iMac Pro for secure boot. That means that even vanilla installations of macOS versions predating the iMac Pro will not boot.
Click to expand...
Since it is more complicated actually to set up properly a bulletproof securebootmodel isn't it better to leave it as optional in the WIKI and the default to be disabled? For me this is really an option just like HWA or VMM spoofing.
 
cdf said:
There are apparently two things going on here: The default option sets the hardware model to iMac Pro for secure boot. That means that even vanilla installations of macOS versions predating the iMac Pro will not boot.
Click to expand...
Yes, that explains it perfectly.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back