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.
Ok so my firmware features and mask config is the following:

<key>FirmwareFeatures</key>
<data>
</data>
<key>FirmwareFeaturesMask</key>
<data>
</data>

VMM is disabled. Why is my Software Update still trying to push Big Sur on me when booted into OpenCore??
 
eicca said:
Ok so my firmware features and mask config is the following:

<key>FirmwareFeatures</key>
<data>
</data>
<key>FirmwareFeaturesMask</key>
<data>
</data>

VMM is disabled. Why is my Software Update still trying to push Big Sur on me when booted into OpenCore??
Click to expand...
Because you spoof the board-id
 
startergo said:
Yes in Platform Info, SMBIOS
Click to expand...
Ok here's my SMBIOS section.

<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string></string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string></string>
<key>BoardAssetTag</key>
<string></string>
<key>BoardLocationInChassis</key>
<string></string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>BoardSerialNumber</key>
<string></string>
<key>BoardType</key>
<integer>0</integer>
<key>BoardVersion</key>
<string></string>
<key>ChassisAssetTag</key>
<string></string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string></string>
<key>ChassisType</key>
<integer>0</integer>
<key>ChassisVersion</key>
<string></string>
<key>FirmwareFeatures</key>
<data>
</data>
<key>FirmwareFeaturesMask</key>
<data>
</data>
<key>PlatformFeature</key>
<integer>0</integer>
<key>ProcessorType</key>
<integer>1281</integer>
<key>SmcVersion</key>
<data>
</data>
<key>SystemFamily</key>
<string></string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string></string>
<key>SystemSKUNumber</key>
<string></string>
<key>SystemSerialNumber</key>
<string></string>
<key>SystemUUID</key>
<string></string>
<key>SystemVersion</key>
<string></string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>

Am I correct that Mac-7BA5B2D9E42DDD94 means it's spoofing a 2017 iMac Pro?
 
eicca said:
Ok here's my SMBIOS section.

<key>SMBIOS</key>
<dict>
<key>BIOSReleaseDate</key>
<string></string>
<key>BIOSVendor</key>
<string></string>
<key>BIOSVersion</key>
<string></string>
<key>BoardAssetTag</key>
<string></string>
<key>BoardLocationInChassis</key>
<string></string>
<key>BoardManufacturer</key>
<string></string>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>BoardSerialNumber</key>
<string></string>
<key>BoardType</key>
<integer>0</integer>
<key>BoardVersion</key>
<string></string>
<key>ChassisAssetTag</key>
<string></string>
<key>ChassisManufacturer</key>
<string></string>
<key>ChassisSerialNumber</key>
<string></string>
<key>ChassisType</key>
<integer>0</integer>
<key>ChassisVersion</key>
<string></string>
<key>FirmwareFeatures</key>
<data>
</data>
<key>FirmwareFeaturesMask</key>
<data>
</data>
<key>PlatformFeature</key>
<integer>0</integer>
<key>ProcessorType</key>
<integer>1281</integer>
<key>SmcVersion</key>
<data>
</data>
<key>SystemFamily</key>
<string></string>
<key>SystemManufacturer</key>
<string></string>
<key>SystemProductName</key>
<string></string>
<key>SystemSKUNumber</key>
<string></string>
<key>SystemSerialNumber</key>
<string></string>
<key>SystemUUID</key>
<string></string>
<key>SystemVersion</key>
<string></string>
</dict>
<key>UpdateDataHub</key>
<false/>
<key>UpdateNVRAM</key>
<false/>
<key>UpdateSMBIOS</key>
<true/>
<key>UpdateSMBIOSMode</key>
<string>Create</string>
</dict>

Am I correct that Mac-7BA5B2D9E42DDD94 means it's spoofing a 2017 iMac Pro?
Click to expand...
Imacpro
 
Ok so the wiki says the VMM flag is what's responsible for Software Update seeing unsupported OS releases.

</array>
<key>Block</key>
<array/>
<key>Emulate</key>
<dict>
<key>Cpuid1Data</key>
<data>
AAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>Cpuid1Mask</key>
<data>
AAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>DummyPowerManagement</key>
<false/>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
</dict>

My VMM flag is OFF, according to the wiki.

So what's going on here??
 
eicca said:
Ok so the wiki says the VMM flag is what's responsible for Software Update seeing unsupported OS releases.

</array>
<key>Block</key>
<array/>
<key>Emulate</key>
<dict>
<key>Cpuid1Data</key>
<data>
AAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>Cpuid1Mask</key>
<data>
AAAAAAAAAAAAAAAAAAAAAA==
</data>
<key>DummyPowerManagement</key>
<false/>
<key>MaxKernel</key>
<string></string>
<key>MinKernel</key>
<string></string>
</dict>

My VMM flag is OFF, according to the wiki.

So what's going on here??
Click to expand...
You are using VideoToolbox compression/decompression acceleration for AMD GPUs? Seems you are and when spoofing iMac Pro or 2019 Mac Pro for the hardware acceleration to be enabled, you will see the software updates available for the Mac that you are spoofing.
 
tsialex said:
You are using VideoToolbox compression/decompression acceleration for AMD GPUs? Seems you are and when spoofing iMac Pro or 2019 Mac Pro for the hardware acceleration to be enabled, you will see the software updates.
Click to expand...
I used the RefindPlus configurator to set up OpenCore, and I said "yes" to all the AMD hardware acceleration options for my RX580, so I assume that means "yes" for VideoToolbox.

Is there a specific way to verify, either through terminal command or config file entry?
 
eicca said:
I used the RefindPlus configurator to set up OpenCore, and I said "yes" to all the AMD hardware acceleration options for my RX580, so I assume that means "yes" for VideoToolbox.

Is there a specific way to verify, either through terminal command or config file entry?
Click to expand...
You are spoofing the iMac Pro, it's on the config you posted:

Code: 
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
 
  • Like
Reactions: Dayo
So it seems the verdict is:

Even with the VMM flag turned off, using AMD hardware acceleration in Mojave will still make Software Update think the computer is eligible for Big Sur.

Funny that I've been running OpenCore for two months now and only this past week has it decided to tell me to upgrade.
 
eicca said:
Ok so the wiki says the VMM flag is what's responsible for Software Update seeing unsupported OS releases.
Click to expand...
In general, for both Catalina and Big Sur, yes. But since 11.1, it seems that Big Sur has become more permissive.
 
amstel78 said:
So if that is set to <false/>, where are settings actually stored?
Click to expand...
Was temporarily confused in the other discussion and couldn't recollect reasons for going with false in MyBootMgr which is why that one version had true. Ultimately recollected and have since reverted.
 
forgive me if this is the wrong thread for this... i wasn't sure if i should post here or in the "PCIe SSDs - NVMe & AHCI" thread.

for those of you who are using NVMe SSDs with PCIe adaptors that support bifurcation in your cMPs running OC, is it possible to install different OSes on different SSDs? for example, using two NVMe SSDs, could i install macOS Mojave on one NVMe and Big Sur on the other? ideally, i would like to use Big Sur as the primary OS and Mojave (the last OS natively supported by my cMP 5,1) as a backup in teh event that something goes wrong.

thanks in advance!
 
erll said:
forgive me if this is the wrong thread for this... i wasn't sure if i should post here or in the "PCIe SSDs - NVMe & AHCI" thread.

for those of you who are using NVMe SSDs with PCIe adaptors that support bifurcation in your cMPs running OC, is it possible to install different OSes on different SSDs? for example, using two NVMe SSDs, could i install macOS Mojave on one NVMe and Big Sur on the other? ideally, i would like to use Big Sur as the primary OS and Mojave (the last OS natively supported by my cMP 5,1) as a backup in teh event that something goes wrong.

thanks in advance!
Click to expand...
Yes. You can even install Windows in UEFI mode.
 
cdf said:
No, and due to the fragility of the flash of the cMP, I would recommend setting WriteFlash to false.
Click to expand...
Thank you. I'll adjust the config files for both standard OC and alternate instances.
Dayo said:
Was temporarily confused in the other discussion and couldn't recollect reasons for going with false in MyBootMgr which is why that one version had true. Ultimately recollected and have since reverted.
Click to expand...
v066c is still defaulting to <true/> for the WriteFlash flag. Will you alter that for future releases?
 
cdf said:
In general, for both Catalina and Big Sur, yes. But since 11.1, it seems that Big Sur has become more permissive.
Click to expand...
Interesting. That explains why it hasn't ever asked to upgrade until now.

Any alterations that can be made to prevent the upgrade prompt without losing my hardware acceleration or Night Shift?
 
Changed WriteFlash to <false/>. Here are the resultant logs. I assume OC makes no distinction between RAM and NVRAM in the logs as to where OC variables are actually getting written to?
Code: 
01:009 00:065 OC: OcLoadNvramSupport...
01:076 00:066 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures - Success
01:143 00:066 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask - Success
01:201 00:058 OC: Not deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale, matches add
01:267 00:065 OC: Deleting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:DefaultBackgroundColor - Not Found
01:334 00:066 OC: Not deleting NVRAM 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:rtc-blacklist, matches add
01:406 00:072 OC: Deleting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:SystemAudioVolume - Success
01:451 00:044 OC: Not deleting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args, matches add
01:517 00:066 OC: Not deleting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:run-efi-updater, matches add
01:584 00:066 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:DefaultBackgroundColor - Success
01:651 00:066 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures - Success
01:701 00:049 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask - Success
01:768 00:066 OC: Setting NVRAM 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:UIScale - ignored, exists
01:834 00:066 OC: Setting NVRAM 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:rtc-blacklist - Not Found
01:901 00:066 OC: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:SystemAudioVolume - Success
01:951 00:049 OC: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args - ignored, exists
02:018 00:066 OC: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config - ignored, exists
02:085 00:066 OC: Setting NVRAM 7C436110-AB2A-4BBB-A880-FE41995C9F82:run-efi-updater - ignored, exists
02:134 00:049 OC: Current version is DBG-066-2021-02-02
 
TECK said:
Thanks for letting me know how the setting works. I got confused because you had that set to 2 previously in 0.6.5 config, fixed with #61.
Click to expand...
Happy to clarify. The reason for adding this setting is to facilitate mounting the EFI volume (see the spoilers under the steps entitled "Mount the EFI volume of Disk A" from Part 2 onwards in the guide).
 
  • Like
Reactions: TECK
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