MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[cdf]

Can someone confirm if VMM should remain off in Big Sur?

Off.

 

[weckart]

Trying to update my Catalina volume to Big Sur from within Catalina. The installer is telling me it needs a firmware update to do so but I can install to a clean HFS+ volume. Not sure what extra firmware update it needs since Catalina was installed to an APFS volume. Is this a bug, a "feature" or have I missed something blindingly obvious?

 

[paulogilmour]

Hello everyone! My bootable USB installer from Big Sur does not appear in the Opencore 0.63 boot selector. If I add the Hfsplus.efi driver, Opencore will not start. What can this be?

 

[cdf]

Trying to update my Catalina volume to Big Sur from within Catalina. The installer is telling me it needs a firmware update to do so but I can install to a clean HFS+ volume. Not sure what extra firmware update it needs since Catalina was installed to an APFS volume. Is this a bug, a "feature" or have I missed something blindingly obvious?

See post #4,399.

 

[paulogilmour]

Guys, did I do something wrong here on the Forum? Why does it seem like everyone here ignores my questions. If I did something wrong I apologize.

 

[Appler007]

i´m running opencore 0.6.3 with a cMP 5.1 and Big Sur Final. But I have problems (red screen) with playing Amazon Prime Video!

 

[startergo]

i´m running opencore 0.6.3 with a cMP 5.1. But I have problems (red screen) with playing Amazon Prime Video!

What operating system?

 

[startergo]

That is funny. I have just installed fresh BigSur 20B29 on a separate disk from a Catalina partition. I did not log in to any Apple services. When logged into the desktop I saw my trashcan full. Those were the trashcan files from the drive I installed BigSur (Catalina).

 

[TECK]

That is funny.

Here are my clean install findings so far.

Since I have OpenCanopy off by default, I wanted to make sure I always boot into Mojave disk, so I checked is default into Preferences (Big Sur disk was already formatted at this point):

When I tried to format the OC disk (previously APFS) to same type APFS, it was failing. I had to format it with previous Journaled format to destroy the data, then I was able to format it back to APFS. Obviously OC files were gone, but I rebuild them in 2 seconds with the plistlib generator, here it is the Big Sur PR:

Big Sur update by fmunteanu · Pull Request #25 · axivo/opencore

github.com

For some reason I could not copy the Big Sur installer I downloaded yesterday from USB to disk, so I'm downloading it again on my Mojave disk with gibMacOS. Once the download is completed, I will reboot into recovery to make sure the the Big Sur disk is properly blessed then I will install Big Sur.

@cdf I will update this post, once I'm done with the clean install, for now I will experiment with the Windows disk in place:

 

[startergo]

Here are my clean install findings so far. If I format the OC disk (previously APFS) to same type APFS, it will fail.

I had BS beta installed and this is what I did:
Deleted the BS beta APFS container:

diskutil list
diskutil apfs deleteContainer diskXsY (as shown in the diskutil list)

Erase disk in Disk Utility (and rename to something meaningful)
Install BS on that disk.

 

[cdf]

Hello everyone! My bootable USB installer from Big Sur does not appear in the Opencore 0.63 boot selector. If I add the Hfsplus.efi driver, Opencore will not start. What can this be?

Guys, did I do something wrong here on the Forum? Why does it seem like everyone here ignores my questions. If I did something wrong I apologize.

You did nothing wrong except for asking hard questions I guess (why a USB installer or HfsPlus.efi? Most users are updating Catalina to Big Sur or clean installing from Catalina or Mojave). Don't worry, if somebody knows how to help, I'm sure they will chime in.

 

[johnwillsey]

I had BS beta installed and this is what I did:
Deleted the BS beta APFS container:

diskutil list
diskutil apfs deleteContainer diskXsY (as shown in the diskutil list)

Erase disk in Disk Utility (and rename to something meaningful)
Install BS on that disk.

I did something similar but via disk utility gui.. Big sur has 3 entries under it's container. Right click on each one and say delete APFS Volume. I then erased the container as hfs extended. Then erased the container as APFS.

This provided a fresh APFS container for fresh install.

 

[w1z]

You did nothing wrong except for asking hard questions I guess (why a USB installer or HfsPlus.efi? Most users are updating Catalina to Big Sur or clean installing from Catalina or Mojave). Don't worry, if somebody knows how to help, I'm sure they will chime in.

You beat me to it, thanks cdf.

I believe BridgeOS/T2 is required to perform a clean install of Big Sur as no combination of variables, hybridization etc. is able to boot the USB installer on cMP. Full spoofing might work but I’m not going down that route.

Startup Disk can only recognize the USB installer in Recovery but fails to bless it properly.


For now, and to those that are interested in carrying out clean installs, find a spare disk, install Mojave or Catalina on it then wipe the drive you want to use to install Big Sur on and start Big Sur install from within Mojave/Catalina.

Updated: See here

 

[Gr1f]

Hey Folks,
I'm running Catalina on CMP 5,1 via Dosdude patch. I only have a radeon RX580 in it.
I'm using a NVMe2 SSD as my boot drive.

I'd like to switch to OpenCore and get Big Sub up and running on a spare Sata SSD.

Then I hope to CCC it to the NVMe SSD.

I managed to copy over the Big Sur installer from my MacBookPro before it started the update process. So that's one thing... also SIPs is already off.

Any tips on the best way to go about this? Most of the video's I've watched seem to want to patch a fresh install of Mojave first then run the updates to Catalina. Just somewhat confused!

Can/Should I maybe begin with a fresh install of Big Sur on a USB from my MBP? Then go through the various Opencore steps on that?

All help appreciated as always!

 

[wickerstick]

I took the plunge to upgrade to big sure last night, fist i attempted clean install to a second NVMe drive, as well as updating my current drive, both installs took however i lost my second monitor in both. I wanted to move my opencore to the new Drive but the command "sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery" nolonger works in Big Sur. I really would like to have my second monitor working again so I'm going to try to figure out what i need to fix it. if anyone else has a fix let me know please

 

[TECK]

Install BS on that disk.

I formatted the disk, but when I start the BS install from Mojave disk, it fails at min 14 and the Mac shuts down completely, did this twice. I'm downloading again the BS installer, this time with:

curl -O -L https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py
sudo python installinstallmacos.py

Here it is my plist. cc @cdf

 

[startergo]

I formatted the disk, but when I start the BS install from Mojave disk, it fails at min 14 and the Mac shuts down completely, did this twice. I'm downloading again the BS installer, this time with:

curl -O -L https://raw.githubusercontent.com/munki/macadmin-scripts/main/installinstallmacos.py
sudo python installinstallmacos.py

Here it is my plist. cc @cdf

Try this one. I have to mention I am using latest OC and there are some additions to my config.plist like

BlacklistAppleUpdate

 

[TECK]

Try this one. I have to mention I am using latest OC and there are some additions to my config.plist

I’ll compare it, that option will be part of 0.6.4 release. How did you build the package from master?

 

[paulogilmour]

Hello again. It's all right . I did the clean install via Mojave on a second HD that I have. In the first tests I did here, Metal's performance dropped a lot. At least on Geekbench. I will do real tests of use.
Single core performance is poor on both systems. Is yours also that low ?? It's smaller than an i3 :-(

 

[startergo]

I’ll compare it, that option will be part of 0.6.4 release. How did you build the package from master?

I use @Dayo myOC.tool
It creates a folder under Documents called myCustomOC. the built OC folders are inside under:

STAGE G
Creating custom packages...
Placed REL-OpenCore-064[PreRelease].zip in /Users/<user>/Documents/myCustomOC/Build_0_VNL/000-Outputs
Placed DBG-OpenCore-064[PreRelease].zip in /Users/<user>/Documents/myCustomOC/Build_0_VNL/000-Outputs

Placed 064[PreRelease] REL-OpenCore.efi in /Users/<user>/Documents/myCustomOC/Build_0_VNL/000-Outputs
Placed 064[PreRelease] DBG-OpenCore.efi in /Users/<user>/Documents/myCustomOC/Build_0_VNL/000-Outputs
...OK

 

[nknudsen513]

Hello!

Been an open core user for a bit, but I'm still learning a lot. I'm on version 0.6.3 and running a stock configuration except I made the firmware changes mentioned in #4399. So I ran the update to Big Sur everything went smooth until I booted up and I no longer can run my second display off of the display port from my Rx 580. Is there anyway to fix this? The only other thing that's not working for me is my USB Wifi adapter, but I'm assuming that's not Big Sur's fault right? If there isn't a fix, what's the easiest way to downgrade back to catalina? Will it require a clean install? Thanks so much for the help, I've learned a lot from the people on here.

 

[TECK]

I use @Dayo myOC.tool

I’m going to reinstall Catalina and upgrade within, for now. I’ll wait for 0.6.4 release which should not be too far.

Edit: I cannot install Catalina, the disk is greyed out? VMM is Off.

$ diskutil list disk0
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         499.9 GB   disk0s2

 

[startergo]

I cannot install Catalina, the disk is greyed out? VMM is Off.

You need VMM on for Catalina install/updates.

 

[paulogilmour]

I’m going to reinstall Catalina and upgrade within, for now. I’ll wait for 0.6.4 release which should not be too far.

Edit: I cannot install Catalina, the disk is greyed out? VMM is Off.

View attachment 1664590

View attachment 1664597

$ diskutil list disk0
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         499.9 GB   disk0s2

I've been through this problem. I solved it when I removed the board-id from Imac Pro. And VMM on.

 

[tofa7a]

I’m going to reinstall Catalina and upgrade within, for now. I’ll wait for 0.6.4 release which should not be too far.

Edit: I cannot install Catalina, the disk is greyed out? VMM is Off.

$ diskutil list disk0
/dev/disk0 (internal):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                         500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         499.9 GB   disk0s2

Change this code in your config.plist from

<key>Cpuid1Mask</key>
<data>AAAAAAAAAAAAAAAAAAAAAA==</data>

to

<key>Cpuid1Mask</key>
<data>AAAAAAAAAAAAAACAAAAAAA==</data>

Reboot and I believe the installer will work.