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.
@cdf If you are available -- I need some help getting 0.7.7 to work 100%

Update: Ok, I turned on DirectGopRendering (I thought this wasn't req'd for the 5700xt?!), and now i've got the graphic/verbose boot picker (at top left corner), but still no icons. Updated config attached.

I've got it running, however am having a weird issue...

When I power up, right after the chime, my screen powers on normally, however, where the OC boot picker icons would appear, I just get a black screen. I press enter on keyboard, and apple logo/mac boots. The thing is, I can't see the icons for the boot picker.

I know it must have something to do with my config -- so just wondering if anyone can help me pinpoint where on the config I messed up/where to fix to get the icons showing again?
 

Attachments

  • config.plist.zip
    4.3 KB · Views: 101
Last edited:
prefuse07 said:
@cdf If you are available -- I need some help getting 0.7.7 to work 100%

Update: Ok, I turned on DirectGopRendering (I thought this wasn't req'd for the 5700xt?!), and now i've got the graphic/verbose boot picker (at top left corner), but still no icons. Updated config attached.
Click to expand...
That's what I was going to recommend. Regarding the missing icons, make sure that you have the required files in EFI/OC/Resources/. You can also try changing PickerVariant to Default.
 
  • Like
Reactions: prefuse07
cdf said:
That's what I was going to recommend. Regarding the missing icons, make sure that you have the required files in EFI/OC/Resources/. You can also try changing PickerVariant to Default.
Click to expand...

Confirmed, I do have the icons in EFI/OC/Resources/Images/Acidanthera/GoldenGate

Changed PickerVariant to Default, but still no luck.

I thought perhaps the stuff in NVRAM might be trying to override, so I got rid of all of this stuff:
Code: 
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
            </dict>

Still just boots to the BuiltIn/verbose/simple boot picker on top left of screen (no icons)

Just spent the past 28 minutes reading the Dortania configurator, making sure I have everything right, and I believe I do. This is so weird....

I wonder if it is PickerAttributes? The Dortania configurator pdf is kinda hard to understand on that part, but I think "17" is a safe value?

Updated config is attached, in case you wanna take a look.
 

Attachments

  • config.plist.zip
    4.2 KB · Views: 52
Last edited:
cdf said:
If you want, post your config, so that we can take a look. With the proper settings, VMM is now only really necessary for macOS Catalina, which more aggressively blocks MacPro5,1.
Click to expand...
Thanks very much for that offer cdf, config attached.
 

Attachments

  • config.plist.zip
    5.2 KB · Views: 81
prefuse07 said:
Confirmed, I do have the icons in EFI/OC/Resources/Images/Acidanthera/GoldenGate

Changed PickerVariant to Default, but still no luck.

I thought perhaps the stuff in NVRAM might be trying to override, so I got rid of all of this stuff:
Code: 
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
            </dict>

Still just boots to the BuiltIn/verbose/simple boot picker on top left of screen (no icons)

Just spent the past 28 minutes reading the Dortania configurator, making sure I have everything right, and I believe I do. This is so weird....

I wonder if it is PickerAttributes? The Dortania configurator pdf is kinda hard to understand on that part, but I think "17" is a safe value?

Updated config is attached, in case you wanna take a look.
Click to expand...
Dumb question but you do have opencanopy.efi installed right? How did you upgrade to 0.7.7? Is it possible that all your files are not from 0.7.7?
 
  • Like
Reactions: cdf
kkinto said:
Thanks very much for that offer cdf, config attached.
Click to expand...
The reason you can't boot without the VMM flag is that SMBIOS spoofing is turned off. Under UpdateSMBIOS, replace false by true.

Other important notes:
  1. The DataHub section is missing. Without it properly configured you'll get random boot failures in Monterey, even with SMBIOS spoofing.
  2. SecureBootModel is disabled. In this case, you won't get a vanilla macOS experience. Updates will always require the VMM flag.
 
cdf said:
The reason you can't boot without the VMM flag is that SMBIOS spoofing is turned off. Under UpdateSMBIOS, replace false by true.

Other important notes:
  1. The DataHub section is missing. Without it properly configured you'll get random boot failures in Monterey, even with SMBIOS spoofing.
  2. SecureBootModel is disabled. In this case, you won't get a vanilla macOS experience. Updates will always require the VMM flag.
Click to expand...
Thank you cdf, appreciate your time and expertise. I will adjust accordingly. tbh I am pretty much relying on the config downloaded from Martin Lo's thread - I don't really understand most of that but this is incentive to learn a bit more!
 
sfalatko said:
Dumb question but you do have opencanopy.efi installed right? How did you upgrade to 0.7.7? Is it possible that all your files are not from 0.7.7?
Click to expand...

Yes, I have all the required files, and I got everything from new. My config is actually what @cdf posted in the bottom of the page 1 guide.

I upgrade by replacing my current OC (in my EFI volume) with the OC from 0.7.7.

I "move to trash" current 0.7.5 OC file and then copy over the 0.7.7 OC file, similarly with how Martin Lo's "how to upgrade OpenCore" video in post 53 of the AMD thread


Perhaps this is a better question, I was a bit confused on whether the FirmwareFeatures code between PlatformNVRAM and SMBIOS should match (searching this thread says they shouldn't, but then again those were specifically discussing Monterey, not Big Sur...)


Does my PlatformInfo code look correct for Big Sur:
Code: 
<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>CustomMemory</key>
        <false/>
        <key>DataHub</key>
        <dict>
            <key>ARTFrequency</key>
            <integer>0</integer>
            <key>BoardProduct</key>
            <string>Mac-27AD2F918AE68F61</string>
            <key>BoardRevision</key>
            <data></data>
            <key>DevicePathsSupported</key>
            <integer>0</integer>
            <key>FSBFrequency</key>
            <integer>0</integer>
            <key>InitialTSC</key>
            <integer>0</integer>
            <key>PlatformName</key>
            <string></string>
            <key>SmcBranch</key>
            <data></data>
            <key>SmcPlatform</key>
            <data></data>
            <key>SmcRevision</key>
            <data></data>
            <key>StartupPowerEvents</key>
            <integer>0</integer>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>Generic</key>
        <dict>
            <key>AdviseFeatures</key>
            <false/>
            <key>MLB</key>
            <string></string>
            <key>MaxBIOSVersion</key>
            <false/>
            <key>ProcessorType</key>
            <integer>0</integer>
            <key>ROM</key>
            <data></data>
            <key>SpoofVendor</key>
            <false/>
            <key>SystemMemoryStatus</key>
            <string>Auto</string>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>PlatformNVRAM</key>
        <dict>
            <key>BID</key>
            <string></string>
            <key>FirmwareFeatures</key>
            <data>A1QMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>MLB</key>
            <string></string>
            <key>ROM</key>
            <data></data>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string>9144.0.7.7.0</string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-27AD2F918AE68F61</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>AxQMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>PlatformFeature</key>
            <integer>-1</integer>
            <key>ProcessorType</key>
            <integer>0</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>
        <true/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
        <key>UseRawUuidEncoding</key>
        <false/>
    </dict>

also, is my UpdateXxxxx section correct?
 
Last edited:
cdf said:
For some reason, this seems to have stopped working for me. Have you tested this since upgrading to 0.7.7?
Click to expand...
I've simply verified that an external USB 3.1 device shows up in the OC Boot Picker, but I haven't actually tried to boot from it. Perhaps you inadvertently replaced the "good" XhciDxe.efi driver with the one provided by OC itself. You should avoid this. I'm attaching a ZIP file of the one I use. See if that works for you.
 

Attachments

  • XhciDxe.efi.zip
    16 KB · Views: 86
prefuse07 said:
Yes, I have all the required files, and I got everything from new. My config is actually what @cdf posted in the bottom of the page 1 guide.

I upgrade by replacing my current OC (in my EFI volume) with the OC from 0.7.7.

I "move to trash" current 0.7.5 OC file and then copy over the 0.7.7 OC file, similarly with how Martin Lo's "how to upgrade OpenCore" video in post 53 of the AMD thread


Perhaps this is a better question, I was a bit confused on whether the FirmwareFeatures code between PlatformNVRAM and SMBIOS should match (searching this thread says they shouldn't, but then again those were specifically discussing Monterey, not Big Sur...)


Does my PlatformInfo code look correct for Big Sur:
Code: 
<key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>CustomMemory</key>
        <false/>
        <key>DataHub</key>
        <dict>
            <key>ARTFrequency</key>
            <integer>0</integer>
            <key>BoardProduct</key>
            <string>Mac-27AD2F918AE68F61</string>
            <key>BoardRevision</key>
            <data></data>
            <key>DevicePathsSupported</key>
            <integer>0</integer>
            <key>FSBFrequency</key>
            <integer>0</integer>
            <key>InitialTSC</key>
            <integer>0</integer>
            <key>PlatformName</key>
            <string></string>
            <key>SmcBranch</key>
            <data></data>
            <key>SmcPlatform</key>
            <data></data>
            <key>SmcRevision</key>
            <data></data>
            <key>StartupPowerEvents</key>
            <integer>0</integer>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>Generic</key>
        <dict>
            <key>AdviseFeatures</key>
            <false/>
            <key>MLB</key>
            <string></string>
            <key>MaxBIOSVersion</key>
            <false/>
            <key>ProcessorType</key>
            <integer>0</integer>
            <key>ROM</key>
            <data></data>
            <key>SpoofVendor</key>
            <false/>
            <key>SystemMemoryStatus</key>
            <string>Auto</string>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>PlatformNVRAM</key>
        <dict>
            <key>BID</key>
            <string></string>
            <key>FirmwareFeatures</key>
            <data>A1QMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>MLB</key>
            <string></string>
            <key>ROM</key>
            <data></data>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSReleaseDate</key>
            <string></string>
            <key>BIOSVendor</key>
            <string></string>
            <key>BIOSVersion</key>
            <string>9144.0.7.7.0</string>
            <key>BoardAssetTag</key>
            <string></string>
            <key>BoardLocationInChassis</key>
            <string></string>
            <key>BoardManufacturer</key>
            <string></string>
            <key>BoardProduct</key>
            <string>Mac-27AD2F918AE68F61</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>AxQMwAgAAAA=</data>
            <key>FirmwareFeaturesMask</key>
            <data>P/8f/wgAAAA=</data>
            <key>PlatformFeature</key>
            <integer>-1</integer>
            <key>ProcessorType</key>
            <integer>0</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>
        <true/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
        <key>UseRawUuidEncoding</key>
        <false/>
    </dict>

also, is my UpdateXxxxx section correct?
Click to expand...
Well I am getting out of my depth but think @cdf or someone should look at your boot args in NVRAM as I don't think you need all of them though I don't think that will affect the boot menu.
 
PeterHolbrook said:
I've simply verified that an external USB 3.1 device shows up in the OC Boot Picker, but I haven't actually tried to boot from it. Perhaps you inadvertently replaced the "good" XhciDxe.efi driver with the one provided by OC itself.
Click to expand...
Thanks. I had the correct file. For some reason, OC doesn't see the SSD connected to my Thunderbolt display in 0.7.7. In fact, the boot picker is completely unresponsive as long as the drive is connected! The same is true if the drive is connected directly to the Titan Ridge card. On the other hand, everything is fine (including bootability) if I place a hub between the Titan Ridge card and the SSD. Strange.
 
  • Like
Reactions: JeDiGM
Wow.... the weirdest thing happened!

after 4 instances of just booting to a black screen after the chime (keyboard and nothing worked), on the 4th reboot, the 0.7.7 boot picker finally showed itself, and it seems to be working.

I guess my machine is just..... weird

Honestly, I can't wait until a direct replacement for this cMP comes out, getting semi tired of all this troubleshooting headache, and no, I am NOT willing to shell out $6k for the nMP
 
Last edited:
prefuse07 said:
Wow.... the weirdest thing happened!

after 4 instances of just booting to a black screen after the chime (keyboard and nothing worked), on the 4th reboot, the 0.7.7 boot picker finally showed itself, and it seems to be working.

I guess my machine is just..... weird

Honestly, I can't wait until a direct replacement for this cMP comes out, getting semi tired of all this troubleshooting headache, and no, I am NOT willing to shell out $6k for the nMP
Click to expand...
I've seen that the biggest handicap for cMP is the NVRAM being susceptible to corruption


forums.macrumors.com

MP5,1: BootROM thread | 144.0.0.0.0

For MacPro5,1 BootROM upgrades, please read the first post of the thread below to know how to do the firmware upgrade: https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave-bootrom-upgrade-instructions-thread.2142418/ For MP4,1 to MP5,1 cross firmware flashing...
forums.macrumors.com forums.macrumors.com
 
cdf said:
Thanks. I had the correct file. For some reason, OC doesn't see the SSD connected to my Thunderbolt display in 0.7.7. In fact, the boot picker is completely unresponsive as long as the drive is connected! The same is true if the drive is connected directly to the Titan Ridge card. On the other hand, everything is fine (including bootability) if I place a hub between the Titan Ridge card and the SSD. Strange.
Click to expand...
I have a hub myself!
 
Fastsavage said:
I've seen that the biggest handicap for cMP is the NVRAM being susceptible to corruption


forums.macrumors.com

MP5,1: BootROM thread | 144.0.0.0.0

For MacPro5,1 BootROM upgrades, please read the first post of the thread below to know how to do the firmware upgrade: https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave-bootrom-upgrade-instructions-thread.2142418/ For MP4,1 to MP5,1 cross firmware flashing...
forums.macrumors.com forums.macrumors.com
Click to expand...

Agreed, I had tsialex rebuild my ROM and even bought and installed a MATT card per his suggestions, but updating OpenCore has also been a headache for me (for example, I couldn't even get 0.7.6 to work, so just went back to 0.7.5, miraculously, I am now on 0.7.7, but again, check this thread for my troubles).

I love this machine, but the headaches are sometimes too annoying (not to mention the bottlecks, for it IS afterall a 13 year old machine)
 
sfalatko said:
Well I am getting out of my depth but think @cdf or someone should look at your boot args in NVRAM as I don't think you need all of them though I don't think that will affect the boot menu.
Click to expand...
prefuse07 said:
but updating OpenCore has also been a headache for me
Click to expand...
There's a lot going on in your config. The biggest issue for me is that you're adding boot-args for settings that you've already added as device properties... To avoid future headaches, I would really suggest that you start from scratch by going through post #1.

Since the beginning of this thread (and, in fact, the beginning of using OpenCore on the Mac Pro), I've urged users to go through the process step by step starting from a minimal configuration so that they could achieve a meaningful setup of their own. While this is perhaps unappealing at first (especially today, since in the very beginning, post #1 was the only solution, so you didn't have a choice ?), I believe it pays off in the long run!
 
  • Like
Reactions: Fastsavage, KeesMacPro, PeterHolbrook and 3 others
cdf said:
There's a lot going on in your config. The biggest issue for me is that you're adding boot-args for settings that you've already added as device properties... To avoid future headaches, I would really suggest that you start from scratch by going through post #1.

Since the beginning of this thread (and, in fact, the beginning of using OpenCore on the Mac Pro), I've urged users to go through the process step by step starting from a minimal configuration so that they could achieve a meaningful setup of their own. While this is perhaps unappealing at first (especially today, since in the very beginning, post #1 was the only solution, so you didn't have a choice ?), I believe it pays off in the long run!
Click to expand...

PM'd you
 
Last edited:
prefuse07 said:
I also looked at your "custom configuration" section within page 1, along with Dortania's latest PDF (to try and understand some of the variables). For the ones I couldn't figure out, I basically just used what Martin had in his 0.7.7beta 3, which is why I posed the question above about PlatformNVRAM and SMBIOS FirmwareFeatures matching.
Click to expand...
You only need to "update" the NVRAM firmware features (see Complete your setup). This is for macOS updates and installations. But for that to work, you also need to set SecureBootModel to Default (see macOS); you have it set to Disabled.

Now if you absolutely wanted to "update" the SMBIOS firmware features, you could (but there's no known reason to), and the value you have there is correct. I've explained this in another post, commenting on the discrepancy between the NVRAM and SMBIOS values.

ocvalidate threw 0 compiles errors
Click to expand...
To my knowledge, ocvalidate won't check for boot-arg or device property correctness.

Could you let me know which boot-args I should take out (that are covered elsewhere within device properties etc...)?
Click to expand...
For the setup described in post #1, boot-args aren't needed at all. In my opinion, boot-args should be reserved for temporary testing (or for exceptional cases where device properties can't be set).

I guess my problem is that I made my 0.7.7 config mimick that of Martin's
Click to expand...
Yes. Before you can mix and match from various approaches, you really need to be sure of the settings. Otherwise, it's best to stick to one approach.

Good luck!
 
  • Like
Reactions: prefuse07
cdf said:
The reason you can't boot without the VMM flag is that SMBIOS spoofing is turned off. Under UpdateSMBIOS, replace false by true.

Other important notes:
  1. The DataHub section is missing. Without it properly configured you'll get random boot failures in Monterey, even with SMBIOS spoofing.
  2. SecureBootModel is disabled. In this case, you won't get a vanilla macOS experience. Updates will always require the VMM flag.
Click to expand...
Hi cdf. I changed the UpdateSMBIOS to true, the VMM flag back to all A's.

Booted with no problem.

Then I changed SecureBootModel to "Default" from "Disabled"(hoping to get 'a vanilla MacOS experience' ;) ) and this resulted in Monterey 12.1 getting stuck at ~33% on the ramrod. BSur 11.6.2 booted without a problem though with that config.

The DataHub section - I looked over that in your post but at this point I don't understand at all what its about, nor what section exactly is missing so I have left that alone. Maybe this has something to do with it not booting into Monterey when SecureBootModel is set to Default.

Where can I find out more about the DataHub section? On reading through the OC doumentation regarding that seems too complex for me to understand at present, even its main function, plus there are two other DataHub mentions in the config. Adding chunks like the sections which activate Surplus etc. are relatively easy.

OCS: Missing key PointerPollMask, context <AppleInput>!
OCS: Missing key PointerPollMax, context <AppleInput>!
OCS: Missing key PointerPollMin, context <AppleInput>!
OCS: No schema for AudioOut at 2 index, context <Audio>!
OCS: No schema for MinimumVolume at 4 index, context <Audio>!
OCS: No schema for VolumeAmplifier at 8 index, context <Audio>!
OCS: Missing key AudioOutMask, context <Audio>!
OCS: Missing key DisconnectHda, context <Audio>!
OCS: Missing key MaximumGain, context <Audio>!
OCS: Missing key MinimumAssistGain, context <Audio>!
OCS: Missing key MinimumAudibleGain, context <Audio>!
Serialisation returns 11 errors!

Kernel->Emulate->Cpuid1Data requires Cpuid1Mask to be active for replaced bits!
CheckKernel returns 1 error!

Completed validating /Volumes/EFI/EFI/OC/config.plist in 2 ms. Found 12 issues requiring attention.
 
kkinto said:
The DataHub section - I looked over that in your post but at this point I don't understand at all what its about, nor what section exactly is missing so I have left that alone. Maybe this has something to do with it not booting into Monterey when SecureBootModel is set to Default.
Click to expand...
Randomly hanging on boot in Monterey is caused by not having DataHub>BoardProduct set. See post #9,938 and the link therein for more information. Perhaps the issue is exacerbated with SecureBootModel=Default. Interesting.

Where can I find out more about the DataHub section? On reading through the OC doumentation regarding that seems too complex for me to understand at present, even its main function, plus there are two other DataHub mentions in the config. Adding chunks like the sections which activate Surplus etc. are relatively easy.
Click to expand...
You'll want to add the following block above the Generic key under PlatformInfo.

XML: 
<key>DataHub</key>
        <dict>
            <key>ARTFrequency</key>
            <integer>0</integer>
            <key>BoardProduct</key>
            <string></string>
            <key>BoardRevision</key>
            <data></data>
            <key>DevicePathsSupported</key>
            <integer>0</integer>
            <key>FSBFrequency</key>
            <integer>0</integer>
            <key>InitialTSC</key>
            <integer>0</integer>
            <key>PlatformName</key>
            <string></string>
            <key>SmcBranch</key>
            <data></data>
            <key>SmcPlatform</key>
            <data></data>
            <key>SmcRevision</key>
            <data></data>
            <key>StartupPowerEvents</key>
            <integer>0</integer>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>

Then you'll want to set BoardProduct to the model you're spoofing. According to your SMBIOS section, that should be Mac-7BA5B2D9E42DDD94. To complete the spoofing, make sure that UpdateDataHub, UpdateNVRAM, UpdateSMBIOS are all set to true.

Regarding the ocvalidate report, it looks like your config hasn't been updated for 0.7.7 (see Maintenance in post #1).
 
PeterHolbrook said:
I have a hub myself!
Click to expand...
There's some weirdness going on with this. I've noticed that loading XhciDxe and UsbBusDxe will allow a USB 2.0 device to boot through a USB 3.x hub, even without ForgeUefiSupport. Booting from a USB 3.0 device, on the other hand, seems to be hit or miss, and sometimes can even freeze up the OpenCore boot picker (with and without ForgeUefiSupport). So at this point, I can't say that we have a fool-proof USB 3.x booting solution.

MacPro5,1 has it's own UsbBusDxe driver built in, so I wonder if there isn't some conflict here. It seems @Dayo is looking into comparing the drivers. They are in fact, different.
 
^Maybe so. I’m just happy that my limited choice of hardware (a USB 3.1 thumb drive attached to a 3.1 hub connected, via USB-C, to my flashed Titan-Ridge Thunderbolt card) always seems to work fine. Perhaps if I were to change one or more of such components, external booting would no longer be possible, or consistently possible (?).
 
cdf said:
Randomly hanging on boot in Monterey is caused by not having DataHub>BoardProduct set. See post #9,938 and the link therein for more information. Perhaps the issue is exacerbated with SecureBootModel=Default. Interesting.
You'll want to add the following block above the Generic key under PlatformInfo.

XML: 
<key>DataHub</key>
        <dict>
            <key>ARTFrequency</key>
            <integer>0</integer>
            <key>BoardProduct</key>
            <string></string>
            <key>BoardRevision</key>
            <data></data>
            <key>DevicePathsSupported</key>
            <integer>0</integer>
            <key>FSBFrequency</key>
            <integer>0</integer>
            <key>InitialTSC</key>
            <integer>0</integer>
            <key>PlatformName</key>
            <string></string>
            <key>SmcBranch</key>
            <data></data>
            <key>SmcPlatform</key>
            <data></data>
            <key>SmcRevision</key>
            <data></data>
            <key>StartupPowerEvents</key>
            <integer>0</integer>
            <key>SystemProductName</key>
            <string></string>
            <key>SystemSerialNumber</key>
            <string></string>
            <key>SystemUUID</key>
            <string></string>
        </dict>

Then you'll want to set BoardProduct to the model you're spoofing. According to your SMBIOS section, that should be Mac-7BA5B2D9E42DDD94. To complete the spoofing, make sure that UpdateDataHub, UpdateNVRAM, UpdateSMBIOS are all set to true.

Regarding the ocvalidate report, it looks like your config hasn't been updated for 0.7.7 (see Maintenance in post #1).
Click to expand...
Thank you for the detailed answer. I have made the maintenance changes and that killed all the validate errors except one about Cpuid1Mask not active. I'm assuming that's because its all A's again.

Other changes as suggested implemented. I really need to go and recreate this from scratch and understand what in here is about having "features" and whats there just to keep this thing running. It's kinda daunting though. This is some crazy left brain stuff for a right brain person!

When's "OC: The GUI" due?

Haven't restarted yet, ohboy the suspense!

Thanks for your patience and time. What you guys do is just incredible and appreciated. This is the true 'spirit' of Apple no matter where the corporate mothership spins off to.

--------------

General FA question: if you don't have OC EFI on any connected hard drives and you boot with a usb with OC on it - will the cMP will boot using that OC?
 
  • Like
Reactions: 0134168
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