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

[NC12]

I do have an updated bluetooth card - a BCM43602CDP though @tsialex recommends a BCM43602CD. Look at this post for all the pieces/parts - you might feel comfortable building your own "kit" for less than you might buy it all in one piece - Post #740

Thanks! I had looked into the individual parts before but the ones they linked were at much more reasonable price.

 

[flaubert]

So, unfortunately I had just updated to 12.3 after doing a fresh install of OC 0.7.9 on my dual processor cMP 5,1 when the concerns arose in this thread about the 12.3 OTA filling up the NVRAM. I'm guessing that I should do the deep NVRAM clean (cmd option P R until the fourth chime) as a precaution, then boot into the native El Capitan disk (with OC disabled) that I have with MacSchrauber's rom dump tool to compare what it says now, with what it said in February?

The Macschrauber tool previously generated a .bin file; can that be used to re-flash the NVRAM back to what it was back in February?

Where would I find the instructions on how re-flash the NVRAM?

Thank you for your advice. I'm enclosing the log of what the dump tool generated the first time.

 

[tsialex]

So, unfortunately I had just updated to 12.3 after doing a fresh install of OC 0.7.9 on my dual processor cMP 5,1 when the concerns arose in this thread about the 12.3 OTA filling up the NVRAM. I'm guessing that I should do the deep NVRAM clean (cmd option P R until the fourth chime) as a precaution, then boot into the native El Capitan disk (with OC disabled) that I have with MacSchrauber's rom dump tool to compare what it says now, with what it said in February?

The Macschrauber tool previously generated a .bin file; can that be used to re-flash the NVRAM back to what it was back in February?

Where would I find the instructions on how re-flash the NVRAM?

Thank you for your advice. I'm enclosing the log of what the dump tool generated the first time.

To flash a backup BootROM image you will use ROMTool (zip file password is rom) from a supported macOS (10.9 to 10.14, don't use Yosemite) and SIP needs to be disabled. Never flash booted from OpenCore.

First enter Firmware Programming Mode correctly.​

1. Shutdown your Mac,
2. Press and keep pressed the power button,
3. You will hear a loud beep, keep pressed,
4. You will hear the startup chime (if your Mac still has it, some Macs lost the chime with MP51.0087.B00), release the power button when it ends or when starts loading macOS (if your Mac lost the chime).

Boot your supported macOS install, after you login you can proceed to the flashing process with ROMTool.

Open ROMTool:​

1. Click "Flash System ROM",
2. Open your back-up BootROM dump.
3. Flash it*,
4. Shutdown your Mac Pro.
5. Remove the power cable for at least 20 seconds to reset the SMC controller.
6. Connect the power cable and power on your Mac Pro.

*If ROMTool asks you to confirm what is the model of your SPI flash, it's the 8-pin SOIC flash memory next to the PCIe AUX-B power connector, label U8700 - see the photos below. The model of the SPI flash memory is usually related to the model year:​

• with early-2009 almost all backplanes have SST25VF032B,
• with mid-2010 usually is Macronix MX25L3205A or MX25L3205D, sometimes can be MX25L3206E with mid-2010s made in the 1st half of 2012, very rarely is SST25VF032B,
• with mid-2012 usually is Macronix MX25L3206E, it's not common to see mid-2012 with MX25L3205A or MX25L3205D.
• If ROMTool don’t ask you the SPI model at all, Apple used a SST25VF032B.

 

[PeterHolbrook]

The built in USB 2 ports weren’t working when I was spoofing the iMac Pro and running Monterey but they started working again after switching to the Mac Pro 7,1. Might just be me though

I haven’t had any USB issues while spoofing the iMac Pro 1,1.

 

[cdf]

I haven’t had any USB issues while spoofing the iMac Pro 1,1.

While the recommendation is to use the MacPro7,1 board ID, the iMac Pro board ID is perfectly fine. To my knowledge, the only advantage of the MacPro7,1 board ID for standard setups is having fully functional display outputs without the agdpmod device property or boot argument.

 

[macguru9999]

While the recommendation is to use the MacPro7,1 board ID, the iMac Pro board ID is perfectly fine. To my knowledge, the only advantage of the MacPro7,1 board ID for standard setups is having fully functional display outputs without the agdpmod device property or boot argument.

I had usb issues , sometimes, with m lo's 077 and 078 on my 5,1. I have gone back to dosdude catalina.

 

[cdf]

I had usb issues , sometimes, with m lo's 077 and 078 on my 5,1. I have gone back to dosdude catalina.

What you experienced was likely due to the lack of USB 1.x support in Big Sur and later, a well-known limitation solved by either connecting concerned devices before booting or connecting them through a USB hub. MacPro7,1 vs iMac Pro board ID model shouldn’t matter here.

 

[macguru9999]

What you experienced was likely due to the lack of USB 1.x support in Big Sur and later, a well-known limitation solved by either connecting concerned devices before booting or connecting them through a USB hub. MacPro7,1 vs iMac Pro board ID model shouldn’t matter here.

No, that would not be it, a 5,1 does not have usb 1 ... anyway I have given up for now, i'm happy with dosdude catalina and ill get a mac studio in the future

 

[cdf]

No, that would not be it, a 5,1 does not have usb 1 ... anyway I have given up for now, i'm happy with dosdude catalina and ill get a mac studio in the future

Actually, each USB port on the classic Mac Pro not only has a USB 2.0 interface (EHCI) but also a USB 1.1 one (OHCI). The issue occurs because low speed devices are automatically connected through the latter, support for which is lacking in Big Sur and later. Anyway, enjoy your new setup!

 

[macguru9999]

Actually, each USB port on the classic Mac Pro not only has a USB 2.0 interface (EHCI) but also a USB 1.1 one (OHCI). The issue occurs because low speed devices are automatically connected through the latter, support for which is lacking in Big Sur and later. Anyway, enjoy your new setup!

Good reason to stick with catalina then ... thats a good explanation thanks

 

[flaubert]

I'm having trouble creating a rescue CD under MacOS 12.3; I successfully created one back at OC 0.7.6, but it is only partly functional now (it can't boot into 12.3 it seems, probably because it is missing the ASPP-Override.kext). Here is the error I get:

Admins-cMP-DP1:~ adminkurt$ hdiutil create -size 200MiB -srcfolder OC-CD -format UDTO -fs FAT32 OC-CD.iso

.....could not access /Volumes/OC-CD/EFI/OC/config.plist - Invalid argument


hdiutil: create failed - Invalid argument

I turned on verbose and then get this:

Spoiler: Verbose error output from Terminal when creating the ISO

Admins-cMP-DP1:~ adminkurt$ hdiutil create -verbose -size 200MiB -srcfolder OC-CD -format UDTO -fs FAT32 OC-CD.iso
2022-03-19 11:18:55.422 diskimages-helper[991:15645] *useEffectiveIDs**** euid/egid changed to 501,20 (uid/gid is 501,20)
2022-03-19 11:18:55.423 diskimages-helper[991:15645] *useRealIDs******** euid/egid changed to 501,20 (uid/gid is 501,20)
Initializing…
2022-03-19 11:18:55.424 diskimages-helper[991:15645] *useEffectiveIDs**** euid/egid changed to 501,20 (uid/gid is 501,20)
2022-03-19 11:18:55.431 copy-helper[992:15648] estimating /Users/adminkurt/OC-CD
2022-03-19 11:18:56.447 diskimages-helper[991:15645] *useRealIDs******** euid/egid changed to 501,20 (uid/gid is 501,20)
Creating…
DIDiskImageCreatorProbe: interface 1, score -1000, CSparseBundleDiskImage
DIDiskImageCreatorProbe: interface 2, score -1000, CSparseDiskImage
DIDiskImageCreatorProbe: interface 3, score 1000, CRawDiskImage
DIDiskImageCreatorProbe: interface 4, score -1000, CWOUDIFDiskImage
DIDiskImageCreateWithCFURL: CRawDiskImage
DIFileEncodingCreatorProbe: interface 0, score -1000, CEncryptedEncoding
DIBackingStoreCreatorProbe: interface 0, score 100, CBSDBackingStore
DIBackingStoreCreatorProbe: interface 1, score -1000, CBundleBackingStore
DIBackingStoreCreatorProbe: interface 2, score 0, CRAMBackingStore
DIBackingStoreCreatorProbe: interface 4, score -100, CCURLBackingStore
DIBackingStoreCreateWithCFURL: CBSDBackingStore
DIBackingStoreCreateWithCFURL: creator returned 0
DIDiskImageCreateWithCFURL: creator returned 0
DI_kextWaitQuiet: about to call IOServiceWaitQuiet...
DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000005 seconds
DI_kextWaitQuiet: about to call IOServiceWaitQuiet...
DI_kextWaitQuiet: IOServiceWaitQuiet took 0.000005 seconds
2022-03-19 11:18:56.750 diskimages-helper[991:15674] DIHelperHDID serveImage: attaching drive
{
autodiskmount = 0;
"hdiagent-drive-identifier" = "AF9347C1-8169-4730-A3E5-8E007D554911";
"skip-auto-fsck-for-system-images" = 1;
"system-image" = 1;
"unmount-timeout" = 0;
}
2022-03-19 11:18:56.752 diskimages-helper[991:15674] DIHelperHDID serveImage: connecting to myDrive 0x440B
2022-03-19 11:18:56.752 diskimages-helper[991:15674] DIHelperHDID serveImage: register _readBuffer 0x7fb277000000
2022-03-19 11:18:56.752 diskimages-helper[991:15674] DIHelperHDID serveImage: activating drive port 16907
2022-03-19 11:18:56.752 diskimages-helper[991:15674] DIHelperHDID serveImage: set cache enabled=TRUE returned FAILURE.
2022-03-19 11:18:56.752 diskimages-helper[991:15674] DIHelperHDID serveImage: set on IO thread=TRUE returned SUCCESS.
2022-03-19 11:18:56.752 diskimages-helper[991:15674] -processKernelRequest: will sleep received
2022-03-19 11:18:56.836 diskimages-helper[991:15645] _mountDevEntries: disk4s1 aborting mountpoint postflight because disk image has no band size specified.
2022-03-19 11:18:56.837 diskimages-helper[991:15643] _postflightMountPointsAfterDAMount: disk4s1 aborting because disk image has no band size specified.
2022-03-19 11:18:56.838 diskimages-helper[991:15643] _postflightMountPointsAfterDAMount: disk4 aborting because no mount point found.
2022-03-19 11:18:56.838 diskimages-helper[991:15645] *useEffectiveIDs**** euid/egid changed to 501,20 (uid/gid is 501,20)
2022-03-19 11:18:56.848 diskimages-helper[991:15645] *useRealIDs******** euid/egid changed to 501,20 (uid/gid is 501,20)
Copying…
2022-03-19 11:18:56.849 diskimages-helper[991:15645] *useEffectiveIDs**** euid/egid changed to 501,20 (uid/gid is 501,20)
2022-03-19 11:18:56.857 copy-helper[1006:15713] copying /Users/adminkurt/OC-CD to /Volumes/OC-CD
2022-03-19 11:18:56.857 copy-helper[1006:15713] About to copy "/Users/adminkurt/OC-CD".
2022-03-19 11:18:57.664 copy-helper[1006:15713] copy error (canceling): /Volumes/OC-CD/EFI/OC/config.plist: Invalid argument
2022-03-19 11:18:57.665 copy-helper[1006:15713] Copy finished with error 22 (Invalid argument).
.....Error 22 (Invalid argument).
could not access /Volumes/OC-CD/EFI/OC/config.plist - Invalid argument

Finishing…
2022-03-19 11:18:58.702 diskimages-helper[991:15674] -processKernelRequest: flush received
2022-03-19 11:18:58.743 diskimages-helper[991:15674] -processKernelRequest: flush received
2022-03-19 11:18:58.751 diskimages-helper[991:15645] *useEffectiveIDs**** euid/egid changed to 501,20 (uid/gid is 501,20)
DIHLDiskImageCreate() returned 22
hdiutil: create: returning 22
hdiutil: create failed - Invalid argument
Admins-cMP-DP1:~ adminkurt$

It looks like the command could not mount the constructed image at /Volumes/OC-CD because no band size was specified? And then the subsequent copy failed, with config.plist being the first file it tries to copy?

Anyone else having this problem in 12.3?

 

[cdf]

Here is the error I get:

Admins-cMP-DP1:~ adminkurt$ hdiutil create -size 200MiB -srcfolder OC-CD -format UDTO -fs FAT32 OC-CD.iso

.....could not access /Volumes/OC-CD/EFI/OC/config.plist - Invalid argument


hdiutil: create failed - Invalid argument

This has come up before: the command is particularly picky about how the config file is modified prior to being executed. Search this thread for “Invalid argument”.

 

[ZNDK]

I have been able to boot my Mac stably since then, and macOS 12.3 seems to be working without any obstacles at this point. Now there are no more freezes or screen flickers. I'm currently on OC 0.7.8 and am trying OC 0.7.9. However, OC 0.7.9 cannot start. After the startup sound, it will not proceed. I switch to GTX680 and the screen remains black. It is not even entirely white. When I would fail to boot with OC, the screen would display all white when I installed the GTX680 and booted it.
I used ocvalidate to validate the config.plist and the results are fine. I'm currently fine with 0.7.8, but would like to find out the cause for the future. Which items should I suspect?
I had tried modifying the config.plist attached to a previous post, editing the sample.plist, and modifying the OCLP config.plist. I have failed to start in any of them.

 

[joebclash]

I'm sorry but english is second language, it's alittle hard to understand this thread. Are people saying do not upgrade to 12.3 because of problems?

 

[TECK]

Is there a way to erase all content and settings with OC and Monterey? That option is missing for me.

If this is not possible, can I re-install Monterey using the Apple procedure with OC enabled?

 

[trifero]

Is there a way to erase all content and settings with OC and Monterey? That option is missing for me.

View attachment 1977874

That just for macs with T2 chips or Silicon macs.

 

[TECK]

That just for macs with T2 chips or Silicon macs.

Thanks, I did not know. BTW you're too fast, I updated the post. Can I do an usual disk wipe, as instructed by Apple, with OC enabled?

 

[sfalatko]

I'm sorry but english is second language, it's alittle hard to understand this thread. Are people saying do not upgrade to 12.3 because of problems?

They are not saying do not upgrade to 12.3. There is a problem which requires some additional changes to the config.plist and an additional Kext (ASPP-Override.kext) for 12.3 to work. You can read post #1 under the "Complete your setup" section.

Regards,
sfalatko

 

[TECK]

There is a problem which requires some additional changes to the config.plist

There are no changes required to config.plist prior Monterey 12.3 upgrade, beside adding the new kext.

 

[sfalatko]

There are no changes required to config.plist prior Monterey 12.3 upgrade, beside adding the new kext.

Well the config.plist does need to be edited to activate the new kext which is what I mean. The appropriate text is in the first post.

 

[ZNDK]

Why can't I use OC 0.7.9? I read #1 and manually built config.plist. I have modified OCLP to 0.7.9 for processing and Built 0.7.9 using OC Plistlib Generator. All of these have the same behavior, nothing is displayed after the startup sound. I've experienced in the past that sometimes the OS is running just with nothing on the screen, but not this time.

• Martin's Package (one-size-fits-all solution)https://forums.macrumors.com/posts/29572277/

This was the only difference. Mac cannot be booted, but this is the only boot select screen that always appears. The boot select screen displays 'Macintosh SSD', 'EFI Boot', 'vm', 'Recovery', 'Macintosh SSD', and 'Update'. I get an error message no matter which one I select and am returned to the boot select screen, even with OpenCore which has no problems on the USB stick. Will I be able to use 0.8.0 or later in the future?

 

[TECK]

Built 0.7.9 using OC Plistlib Generator.

Post your setup.py into support thread, I will check it tomorrow.

 

[roobarb!]

I've experienced some trouble with a PCIe card I use from Blackmagic recently - the DeckLink Quad HDMI Recorder - and wanted to check whether this is a driver problem on their side, or something I need to look to replace due to DriverKit incompatibilities with MP5,1 systems.

In their v12.1 driver they use traditional kernel extensions. No problem, card works perfectly. From v12.2 they changed to using DriverKit system extensions. I accepted the extensions in System Preferences and reboot... no card. It's still there under PCI in System Information, but no driver is loaded. No degree of cajoling brings it to life.

What's the verdict, folks? Are my HDMI capture days nearing an end?

 

[Hamm3rdin]

Hi
I posted my question on other forum here, but maybe this is a better place
I installed Big Sur 11.6.4 and Windows 11 on my Mac Pro 5,1 with OpenCore (on separate SSD disks). Absolutely everything work ok, except I have no sound on any device in Windows... Whatever I connect is visible in Windows (speakers, microphones, external USB sound cards, by front and rear connectors), all (in system) is visible, connected, drivers ok and working. But... there is no sound I tried all versions of Realtek drivers found on Internet (also that originally from BootCamp) but with no success. But even without any good drivers, external USB sound cards should work? Maybe problem is hidden deeper, inside OpenCore itself, wrong kexts or sth similar? I searched many forums, tried many solutions but not one thing didn't work. Any help?

 

[hwojtek]

I installed Big Sur 11.6.4 and Windows 11 on my Mac Pro 5,1 with OpenCore (on separate SSD disks). Absolutely everything work ok, except I have no sound on any device in Windows... Whatever I connect is visible in Windows (speakers, microphones, external USB sound cards, by front and rear connectors), all (in system) is visible, connected, drivers ok and working. But... there is no sound I tried all versions of Realtek drivers found on Internet (also that originally from BootCamp)

You haven't tried the right ones, then. Google Realtek_High_Definition_Audio_64bit_Win7_Win8_Win81_Win10_R279.exe

Remove the audio devices, run the installer, reboot. Also, this actually off-topic, your issue belongs here.