Back to Mojave (my primary OS) now. Most likely will do more test in Big Sur in the next few days. Will check it out if there is any changes in the iMessage key (if I keep the same UUID).
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 was wrong about the previous thing I believed it was crashing my mac because it just frooze again a bit ago, but the console did not report any fail log at the exact minute the freezing happened (took the time)
Honestly I don't know what is causing the freeze anymore, I'm just hoping is a bug of 10.15.6
Here's the system log from the minute the freeze took place on
Honestly I don't know what is causing the freeze anymore, I'm just hoping is a bug of 10.15.6
Here's the system log from the minute the freeze took place on
Hi I'm stuck at
Bless the EFI volume of Disk A and reboot
Check that OpenCore has actually booted the system by entering: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
pencore-version
I used USB drive and I was able to install disk4s1/EFI/EFI/BOOT and disk4s1/EFI/EFI/OC as I can see the files in there.
How can I boot back into Mojave and perhaps check the opencore and config.plist file? I just downloaded whatever was written there above.
OpenCore 0.5.9
Download the release version. The uncompressed folder will be referred to as OpenCore.
Sample configuration file (updated June 1st, 2020)
The name of the uncompressed file is config.plist.
Bless the EFI volume of Disk A and reboot
- Bless the volume for booting by entering: bless --mount /Volumes/EFI --setBoot
Check that OpenCore has actually booted the system by entering: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102
pencore-versionI used USB drive and I was able to install disk4s1/EFI/EFI/BOOT and disk4s1/EFI/EFI/OC as I can see the files in there.
How can I boot back into Mojave and perhaps check the opencore and config.plist file? I just downloaded whatever was written there above.
OpenCore 0.5.9
Download the release version. The uncompressed folder will be referred to as OpenCore.
Sample configuration file (updated June 1st, 2020)
The name of the uncompressed file is config.plist.
So @startergo just looking at the SMBIOS generator on OpenCore Configurator, it appears that the values can be inserted directly into that as:
37E10FE8 00000000
3FFF1FFF 00000000
Screenshot:
Those translate into base64 encoded versions as:
While this was a good idea, I still seemed to get some trouble. The first video capture actually worked this time, but subsequent captures failed with:
37E10FE8 00000000
3FFF1FFF 00000000
Screenshot:
Those translate into base64 encoded versions as:
Code:
<key>FirmwareFeatures</key>
<data>N+EP6AAAAAA=</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/wAAAAA=</data>While this was a good idea, I still seemed to get some trouble. The first video capture actually worked this time, but subsequent captures failed with:
Code:
[recorder] Recording failed: Error Domain=AVFoundationErrorDomain Code=-11844 "Cannot Capture" UserInfo={NSLocalizedDescription=Cannot Capture, NSUnderlyingError=0x600002d820d0 {Error Domain=NSOSStatusErrorDomain Code=-67394 "(null)"}, AVErrorRecordingSuccessfullyFinishedKey=false, NSLocalizedFailureReason=There was an unexpected problem with the graphics sub-system that prevented screen capture.}
Last edited:
Remove your USB drive and reset the NVRAM.
There are various things at play here. Before blessing the volume, make sure to mount it with diskutil. Also, the bless command seems to fail on certain percentage of Mac Pros (I wonder if this has to do with a worn-out NVRAM volume). For that reason, the guide includes an alternative command (see the spoiler in that step). Moreover, some USB and PCIe drives seem to have trouble booting OpenCore. You might want to experiment with a regular SATA disk.
But in manual mode, unspecified variables should just not be set, so this shouldn't really matter.
The advantage of manual mode is that it allows us to change only a few things without affecting the rest. In fact, that's why we use manual mode to change just the board ID for hybridization. Anything that we don't specify remains unchanged. Upping the hybridization with the product name may be all that we need to move forward with Big Sur. Oddly, however, @startergo is seeing a change in iMessage keys. If you get a chance, perhaps you could check this. In my case, the keys remain unchanged...
See here:So @startergo just looking at the SMBIOS generator on OpenCore Configurator, it appears that the values can be inserted directly into that as:
37E10FE8 00000000
3FFF1FFF 00000000
Screenshot:
Those translate into base64 encoded versions as:
Code:<key>FirmwareFeatures</key> <data>N+EP6AAAAAA=</data> <key>FirmwareFeaturesMask</key> <data>P/8f/wAAAAA=</data>
While this was a good idea, I still seemed to get some trouble. The first video capture actually worked this time, but subsequent captures failed with:
Code:[recorder] Recording failed: Error Domain=AVFoundationErrorDomain Code=-11844 "Cannot Capture" UserInfo={NSLocalizedDescription=Cannot Capture, NSUnderlyingError=0x600002d820d0 {Error Domain=NSOSStatusErrorDomain Code=-67394 "(null)"}, AVErrorRecordingSuccessfullyFinishedKey=false, NSLocalizedFailureReason=There was an unexpected problem with the graphics sub-system that prevented screen capture.}
Capture setup | Apple Developer Documentation
Configure built-in cameras and microphones, and external capture devices, for media capture.
Requesting Authorization for Media Capture on macOS | Apple Developer Documentation
Prompt the user to authorize access to the camera and microphone.
Only when I used update NVRAM with PlatformNVRAM empty. If we only use update SMBIOS and add the product name to the board ID it should work.
Again, this shouldn't matter. Anyways, make sure to let us know if your iMessage keys remain unchanged after updating only the SMBIOS with product name and board ID.
That is what I do - I boot OC from a USB drive. You need to hold down the option key to get to the normal Apple boot picker menu then select the USB stick to boot from. You will then get the OC boot picker menu that you can use to boot into you OS of choice.
So why would I do that? I only use OC to boot into Catalina with the VMM flag set to perform updates (or to boot into Catalina Recovery mode). I have not moved my MacPro entirely over to OC so that I don't have to redo my windows 10 install as UEFI. I use the no compatibility boot arg to boot on a day to day basis into Catalina. At some point I'll install OC onto one of my drives and boot using it on a day to day basis but for now I have flexibility.
See here:
Capture setup | Apple Developer Documentation
Configure built-in cameras and microphones, and external capture devices, for media capture.developer.apple.com
Requesting Authorization for Media Capture on macOS | Apple Developer Documentation
Prompt the user to authorize access to the camera and microphone.
Only when I used update NVRAM with PlatformNVRAM empty. If we only use update SMBIOS and add the product name to the board ID it should work.
Thanks for pointing those out, unfortunately even resetting microphone and camera reset with tccutil doesn't help. It appears that -11844 is a AVErrorScreenCaptureFailed. I did a `tccutil reset All` and it still didn't resolve the problem. Sometime I'm also seeing error number -11805 which is AVErrorNoDataCaptured.
Again it goes back to "it's a hardware problem" from the developer.
If you have a MacPro5,1 can you test out CloudApp 6.2.1 and see if you can capture video screen recordings from here: https://www.getcloudapp.com/download/mac ?
Thank you so much - that's unbelievable... And you're on Catalina.6 or another OS release? So at least this rules out the "hardware problem" they keep attributing this to. Can you share your EFI folder so I can diff it against my own? You're welcome to PM me or reach me at Gmail same nick.
Thanks, NVRAM worked in being able to go back to Mojave.
For your 2nd point, I changed to a SATA HDD, formatted to APFS and now it's working. Just updated to Catalina. Thanks.
One question: Currently it looks like it doesn't boot off of OpenCore as default, but my old OS. How would I be able to change this?
Also, does GTX680 Mac Edition work in Catalina as default?
Thanks.
No longer over to install Beta 11.0 (20A5323l) use SMBIOS from iMacPro OpenCore by williambj1 RELEASE
Last edited:
Try blessing it as indicated in the guide. There's also the alternative command to try (which will also give a verbose output to help understand what's going on). If you can't get this to work even with disks in the drive bays, your firmware volume may be at fault: if you haven't already, back up your BootROM.
Yes.
To those who use BigSur through OpenCanopy boot menu, I noticed that BigSur is showed only as Preboot, I found a way to rename it (for OpenCore), and it consists in using this attached and copy it, from BigSur normal booting, on this path:
/System/Volumes/Preboot/YourBigSurUUID/System/Library/CoreServices/
then you can rename the "BigSur label" using this attached (it's an hidden file) with a plain text editor, it should work.
/System/Volumes/Preboot/YourBigSurUUID/System/Library/CoreServices/
then you can rename the "BigSur label" using this attached (it's an hidden file) with a plain text editor, it should work.
Not sure I really understand that. The file that you attached as to be moved to /System/Volumes/Preboot/YourBigSurUUID/System/Library/CoreServices/ correct?
Then you rename you rename this disk_label_contentDetails.zip to BigSur Label? Correct?
Thanks.
You actually click one of those disk, and successfully perform the installation?
I rephrase, you should unzip that attached in that BigSur Preboot path, then from that path you can edit with a plain text the content of this file
.disk_label.contentDetails
Yes
[automerge]1595775827[/automerge]
Do it like this and everything will be fine))
Code:
Last login: Sun Jul 26 17:32:56 on ttys001
apple@ALEXs-Mac-Pro ~ % diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *512.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk1 256.0 GB disk0s2
3: Apple_APFS Container disk2 241.0 GB disk0s3
4: Apple_HFS Install macOS Big Su... 14.7 GB disk0s4
(free space) 268.4 MB -
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +256.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 236.7 GB disk1s1
2: APFS Volume Preboot 25.4 MB disk1s2
3: APFS Volume Recovery 507.5 MB disk1s3
4: APFS Volume VM 20.5 KB disk1s4
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +241.0 GB disk2
Physical Store disk0s3
1: APFS Volume BigSur - Data 4.8 GB disk2s1
2: APFS Volume Preboot 273.3 MB disk2s2
3: APFS Volume Recovery 887.8 MB disk2s3
4: APFS Volume VM 1.1 MB disk2s4
5: APFS Volume BigSur 15.5 GB disk2s5
6: APFS Snapshot com.apple.os.update-... 15.5 GB disk2s5s1
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *15.6 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS USB 15.2 GB disk3s2
/dev/disk4 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.5 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_HFS HDD 1.5 TB disk4s2
apple@ALEXs-Mac-Pro ~ % sudo diskutil mount disk2s2
Password:
Volume Preboot on disk2s2 mounted
apple@ALEXs-Mac-Pro ~ % ls -l /System/Volumes/Preboot
total 0
drwxr-xr-x 11 root wheel 352 Jul 26 02:50 B78FCD7C-A366-4093-9C33-C78FF3AE61AF
apple@ALEXs-Mac-Pro ~ % sudo mv ~/Users/apple/Downloads/.disk_label.contentDetails /System/Volumes/Preboot/B78FCD7C-A366-4093-9C33-C78FF3AE61AF/System/Library/CoreServices/.disk_label.contentDetails
Last edited:
I made a fresh new install with his EFI folder that i boot first... works like a charme.
Interesting, so, the latest Big Sur installer go back to only need VMM flag on. That's actually a good news for us.