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

[TECK]

I can´t understand you worries about power consumption. Really.

Me neither. @SnakeCoils, the sleep mode in Big Sur will do the same savings on x5690s. I want all the power I can get on my Mac, even if I just surf the Internet. One day I will need all the power I can get plus if I sell it, I will get a much higher resale value.

 

[SnakeCoils]

I can´t understand you worries about power consumption. Really.

Sure I do, and everyone should. If I realize that I can do the same job using less power, why I should waste more energy than I need? If, for example, I love reading books until late night, should I keep all the room lights turned on or wouldn't a simple desk lamp be enough? The resale value of our MacPros is falling quickly, the new M1 Minis and incoming ARM Macs are already wiping out every old (and also not so old) intel machine and I strongly dislike the idea to sell a machine that is still useful to me because Apple decided its obsolescence. Okay, sleep mode is great invention but if we start from a 60W CPU instead of a 130W one the convenience will be even more greater. Maybe I am missing something but from my point of view it works as I expected. I am doing the same things as before with less power and, more important, with the same configuration and the latest OSX which is, to be honest, the only reason that still keeps me in the Mac world.
In summary: a very big THANK YOU to OpenCore!

 

[tsialex]

Sure I do, and everyone should. If I realize that I can do the same job using less power, why I should waste more energy than I need? If, for example, I love reading books until late night, should I keep all the room lights turned on or wouldn't a simple desk lamp be enough? The resale value of our MacPros is falling quickly, the new M1 Minis and incoming ARM Macs are already wiping out every old (and also not so old) intel machine and I strongly dislike the idea to sell a machine that is still useful to me because Apple decided its obsolescence. Okay, sleep mode is great invention but if we start from a 60W CPU instead of a 130W one the convenience will be even more greater. Maybe I am missing something but from my point of view it works as I expected. I am doing the same things as before with less power and, more important, with the same configuration and the latest OSX which is, to be honest, the only reason that still keeps me in the Mac world.
In summary: a very big THANK YOU to OpenCore!

Please don’t say that you think that the CPU have a constant power draw of 130W. TDP is not power draw.

Let me say again - TDP is not power draw, but the (for this generation of Intel Xeon, the meaning changes with different generations) thermal design power that the heatsink needs to dissipate at the moment of maximum power usage.

Only when the processor is running at full clock with all cores your X5690 Xeon will reach the TDP of 130W. An idle processor have a fractional of usage of the 130W TDP. My single CPU X5680 with 48GB of RAM + a 24" display and 6 internal hard disks and 5 NVMe blades have a idle (Safari displaying a web page) power draw of ~111W on the display of my APC no-break.

 

[SnakeCoils]

Perfectly clear but may we say the idle consuption of an L5640 is lower than a X5690 in the same conditions?

 

[tsialex]

Perfectly clear but may we say an idle consuption of an L5640 is lower than a X5690 in the same conditions?

Intel product brief for Xeon 5600 series say that the idle power for any 56xx processor is 10W.

Intel® Processors for PC, Laptops, Servers, and AI | Intel®

Find Intel's processors and microprocessors including computer processors for PCs, desktops, laptops and servers. Designed to provide top processing power.

www.intel.com

While some processors are binned for lowest consumption at some clock and others for least amount of power dissipated at the maximum frequency, you can't really say that a L56xx will have a smaller power draw than a X56xx in the same conditions without testing.

You could be having the exactly same power draw right now.

 

[SnakeCoils]

While some processors are binned for lowest consumption at some clock and others for least amount of power dissipated at the maximum frequency, you can't really say that a L56xx will have a smaller power draw than a X56xx in the same conditions without testing.

You could be having the exactly same power draw right now.

At present I do not have any instruments to exactly measure this idle consumption so my best evaluation will be the next energy bill but I do expect an improvement, at least I will never exceed on the CPU side a power drain of 60W under full load (and this was my goal since the beginning). Many thanks for the technical explanations Alex!

EDIT: Looks like someone has made some really accurate measurement on idle and full CPU load just here and from what I can read the L5640 processors has the lowest drain of all the batch. Very nice!

 

[lumos]

Hi all, I was been able to install Big Sur 11.2.1 with OpenCore in my MacPro 3,1.
All work well except the headphones audio.
The audio work well through the Apple Cinema Display speakers but not from the front headphones jack.
I also see a long list of HDMI audio devices in my preferences (my Mac Pro specs are in my signature).

Please, anyone know how can I fix both of these issues?

Thanks

 

[amstel78]

Just wanted to report another successful installation of 11.2.1 via OC v0.6.6 on an MP5,1. Was pretty straightforward. I simply downloaded the 11.2.1 installer via system update on Mojave then installed with the VMM flag active and SMBios set to 9999.0.0.0.0.

After install completed, I tried booting into BS with VMM flag still activated, and it didn't like that; caused a reboot during 1st stage boot screen. It did boot to desktop just fine with VMM flag turned off though.

Not sure what the above implications would mean for updates, but will sort it out when the time comes.

In the meantime, this install appears stable. WIFI and audio works. Didn't have any problems installing Office 365 apps and Teams (which was a PITA on Catalina). Will test H264 and HEVC HW encode/decode later.

I've already tested OC v0.6.7 on my MP3,1 and am waiting for the master binary to be released before updating on the MP5,1.

 

[TECK]

Just wanted to report another successful installation of 11.2.1 via OC v0.6.6 on an MP5,1.

As a side note, you will get better performance if you use 6x16GB (96GB) of RAM instead of 8x16GB (128GB). I presume you use 16GB sticks.

 

[MacForumsUser]

In OC 0.6.6, is SecureBoot now blocked by default?

 

[cdf]

It did boot to desktop just fine with VMM flag turned off though.

The VMM flag should not be necessary for installing or updating Big Sur, provided that hybridization is configured with firmware features.

I've already tested OC v0.6.7 on my MP3,1 and am waiting for the master binary to be released before updating on the MP5,1.

OC 0.6.7 brings nice improvements, such as firmware features being set automatically through a failsafe (many thanks to @Bmju for comprehensively addressing the OEM failsafes!) and correct display of CPU frequency in About This Mac (a long-standing quibble).

 

[amstel78]

The VMM flag should not be necessary for installing or updating Big Sur, provided that hybridization is configured with firmware features.

This whole 'hybridization' thing is what's throwing me for a loop and I'm still trying to understand it in terms of OC's configuration. I basically have two OC instances configured; one with VMM turned off and reporting actual SMBIOS info as pulled from the board:

And the second OC instance has VMM active with what I assume is SMBIOS spoofing going on. You can see the differences circled in red:

With hybridization and VMM turned off, do I need to copy BIOSVersion as well as those keys circled in red back over to my standard OC instance with VMM disabled?

And when you say VMM is not needed with 11.2.1, that sounds different than 'VMM should not be activated otherwise will cause problems' sort of thing. I ask because I was able to perform a clean install with VMM turned on and SMBIOS keys set to what they are in the second screen shot.

OC 0.6.7 brings nice improvements, such as firmware features being set automatically through a failsafe (many thanks to @Bmju for comprehensively addressing the OEM failsafes!) and correct display of CPU frequency in About This Mac (a long-standing quibble).

I'm looking forward to trying the final build of 0.6.7. I was playing around with it quite a bit on my MP31, and working with Vitaly and Dayo on some UGA video card issues. Many thanks of course to @Bmju for his perseverance!

P.S. where is the key to enable/disable VMM in config.plist? I searched the file earlier but did not find the entry, unless I'm not searching with the right parameter.

 

[cdf]

This whole 'hybridization' thing is what's throwing me for a loop and I'm still trying to understand it in terms of OC's configuration.

Hybridization means spoofing only the board ID. This seems to be happening in both of your configurations. The first is spoofing the iMac Pro board ID and the second is spoofing the Mac Pro 5,1 (is this on a 3,1?). In Big Sur, it should be enough to use the first configuration with VMM off.

If you install or update Big Sur with the first configuration, you should set the BIOSVersion to 9999.0.0.0.0 as an extra precaution against unwanted firmware updates. Starting with 0.6.7, you can omit FirmwareFeatures and FirmwareFeaturesMask and rely on the failsafes.

For Catalina, the Mac Pro 5,1 still requires the VMM flag (the 5,1 is expressly blocked), which you can enable in the first configuration when needed (I'm not sure about the 3,1). Look for Cpuid1Data and Cpuid1Mask. The settings are described in the guide.

ProcessorType is explicitly set in both configurations. You may want to set it to 0 and verify if About This Mac displays the right information. If not, this should be reported to improve the automatic detection in OpenCore.

 

[amstel78]

Thank you @cdf for explaining that clearly. Makes full sense to me now.

And no, this version of OC is running on an actual MP5,1. Not sure why MyBootMgr decided to spoof an iMac for the first instance and insert my actual board information into the second instance with VMM enabled. I would have thought it'd be the other way around.

Will experiment with ProcessorType tomorrow.

 

[Dayo]

Not sure why MyBootMgr decided to spoof an iMac for the first instance and insert my actual board information into the second instance with VMM enabled. I would have thought it'd be the other way around.

Two things to note:

1. You have the roles of your two instances mixed up
2. MyBootMgr makes very few calls and you are responsible for 99% of variables. For instance, whether VMM is on or off is something you indicate directly. A hint is given but you answer yes or no to a direct question. That is, it was not MyBootMgr that decided to switch VMM on or off.

MyBootMgr does not just come with a big button that says "Run Me!", or similar, that you click, after which it goes off to do stuff and comes back to present you with configurations that you have not had input into.

What happens is that you make the decisions on what you want and you indicate these to it. What it actually does is take care of the mechanics of delivering what you indicated that you want.

For your first instance, you indicated that you wanted GPU Acceleration and DRM Streaming. To give you this, it spoofs the IMacPro1,1 Board ID. You additionally indicated that you wanted VMM Spoofing off and this was switched off.

For your second instance, you indicated that you did not want GPU Acceleration and DRM Streaming and hence your original board id was maintained. You additionally indicated that you wanted VMM Spoofing on and this was switched on.

You make the calls, not MyBootMgr.

In the second instance, your actual board id is added to the file. It is your actual board id and not being spoofed. As mentioned in an earlier response to you, it is not necessary and the field could be empty but specifying it explicitly was done in one of the early development cycles to make sure that your actual board id is passed through and that OC does not pick something else up as you need to bear in mind that not all OC auto detection items have always been reliable. Whether it is explicitly specified or OC automatically picks it up, you get the same outcome ... no board id spoofing is done for that second OC instance since what goes in is your actual board id.

The same applies to the ProcessorType. This was one item that used to fail to work properly when relying on automatic detection by OC and so, it was explictly specified. Again, it is your actual processor type and not changed.

Most of these gaps in OC have now been fixed and safer to rely on the automatic detection and MyBootMgr will start to do so to some degree or the other. It will not be jumping straight into relying on auto detection everywhere this is possible and will always err towards predictability (NB: Auto can sometimes be better for this).

Regardless of how it handles the mechanics though, you are the one that specifies what you want to achieve.

My suggestion is to leave things alone and pick up after the next release if you want to tinker as whether something is explicitly specified, or relies on OC to detect it, is not important.

Strong suggestion is to refer to the manual, a copy of which MyBootMgr conveniently provides, before messing with any settings.

 

[amstel78]

@Dayo thank you for clarifying and duly noted.

Just to be clear, I was not implying that MyBootMgr configured things on its own without user intervention. The wording in my earlier post could have been better.

What I didn't understand was why it chose to use an iMac board ID for the first instance and my MP5,1's board info for the second. Being relatively new to OC, I didn't make the connection that spoofing the iMac was needed for hardware acceleration and DRM. I was under the impression that functionality was covered by different key variables.

Now that you've taken the time to explain, it's perfectly clear. I'm sure you probably repeat this information quite frequently, so I do apologize for my ignorance. Due to work and family obligations, i don't have a lot of spare time for tinkering or studying, but I am learning slowly and will make a concerted effort to study the manual further. So, thank you for all you've done with MyBootMgr. Without it, I don't think I'd have ever experimented with OpenCore.

 

[shadow_999]

I've updated to 11.2.2 with OC 0.6.6 with no problem. Thanks

 

[MacForumsUser]

Same. 11.2.2 is working great! Many thanks! Question though: in OC 0.6.6, is SecureBoot now blocked by default?

 

[cdf]

Question though: in OC 0.6.6, is SecureBoot now blocked by default?

I'm not aware of such change. Could you elaborate?

 

[MacForumsUser]

I'm not aware of such change. Could you elaborate?

I was discussing with another user about how to safely and predictably boot macOS Big Sur via OC 0.6.6 with a Windows 10 disk in my system. Right now, every time I put my Windows 10 disk in the system, it boots to it, and there's no way to bypass it. This user mentioned that I need to block SecureBoot, and so we wondered if it was somehow implemented by default in OC 0.6.6. I was running 0.6.4, and I upgraded to 0.6.6 when it released. Apparently, the method for blocking SecureBoot changed between these two versions.

I also read through the thread about this specific issue, but it seems nobody has experienced implementing blocking SecureBoot using 0.6.6 yet.

I'm not 100% sure if I'm asking the correct question (or asking it correctly). If so, my apologies. I know enough about this stuff to be dangerous, so I may need to rephrase my question.

 

[cdf]

Right now, every time I put my Windows 10 disk in the system, it boots to it, and there's no way to bypass it.

This sounds like OC is not properly blessed. You might want to boot natively into Mojave, reset the NVRAM, and rebless OC. If you were previously using BootProtect (now LauncherOption), your Mac may be using a leftover bootstrap entry. The above steps should take care of that.

 

[sfalatko]

Hybridization means spoofing only the board ID. This seems to be happening in both of your configurations. The first is spoofing the iMac Pro board ID and the second is spoofing the Mac Pro 5,1 (is this on a 3,1?). In Big Sur, it should be enough to use the first configuration with VMM off.

If you install or update Big Sur with the first configuration, you should set the BIOSVersion to 9999.0.0.0.0 as an extra precaution against unwanted firmware updates. Starting with 0.6.7, you can omit FirmwareFeatures and FirmwareFeaturesMask and rely on the failsafes.

For Catalina, the Mac Pro 5,1 still requires the VMM flag (the 5,1 is expressly blocked), which you can enable in the first configuration when needed (I'm not sure about the 3,1). Look for Cpuid1Data and Cpuid1Mask. The settings are described in the guide.

ProcessorType is explicitly set in both configurations. You may want to set it to 0 and verify if About This Mac displays the right information. If not, this should be reported to improve the automatic detection in OpenCore.

@cdf - take a look at my config.plist and screenshot. I'm using the config.plist from the first post with spoofing of the BoardID to enable continuity and updates (worked for 11.2.1 and 11.2.2) and VMM off - my processor is "Unknown". You can see below that VMM is off.

Regards

StevesMacPro:~ steve$ sysctl machdep.cpu.features
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES PCID
StevesMacPro:~ steve$

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ACPI</key>
    <dict>
        <key>Add</key>
        <array/>
        <key>Delete</key>
        <array/>
        <key>Patch</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>FadtEnableReset</key>
            <false/>
            <key>NormalizeHeaders</key>
            <false/>
            <key>RebaseRegions</key>
            <false/>
            <key>ResetHwSig</key>
            <false/>
            <key>ResetLogoStatus</key>
            <false/>
        </dict>
    </dict>
    <key>Booter</key>
    <dict>
        <key>MmioWhitelist</key>
        <array/>
        <key>Patch</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>AllowRelocationBlock</key>
            <false/>
            <key>AvoidRuntimeDefrag</key>
            <false/>
            <key>DevirtualiseMmio</key>
            <false/>
            <key>DisableSingleUser</key>
            <false/>
            <key>DisableVariableWrite</key>
            <false/>
            <key>DiscardHibernateMap</key>
            <false/>
            <key>EnableSafeModeSlide</key>
            <false/>
            <key>EnableWriteUnprotector</key>
            <false/>
            <key>ForceExitBootServices</key>
            <false/>
            <key>ProtectMemoryRegions</key>
            <false/>
            <key>ProtectSecureBoot</key>
            <true/>
            <key>ProtectUefiServices</key>
            <false/>
            <key>ProvideCustomSlide</key>
            <false/>
            <key>ProvideMaxSlide</key>
            <integer>0</integer>
            <key>RebuildAppleMemoryMap</key>
            <false/>
            <key>SetupVirtualMap</key>
            <false/>
            <key>SignalAppleOS</key>
            <false/>
            <key>SyncRuntimePermissions</key>
            <false/>
        </dict>
    </dict>
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict/>
        <key>Delete</key>
        <dict/>
    </dict>
    <key>Kernel</key>
    <dict>
        <key>Add</key>
        <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>
        <key>Force</key>
        <array/>
        <key>Patch</key>
        <array/>
        <key>Quirks</key>
        <dict>
            <key>AppleCpuPmCfgLock</key>
            <false/>
            <key>AppleXcpmCfgLock</key>
            <false/>
            <key>AppleXcpmExtraMsrs</key>
            <false/>
            <key>AppleXcpmForceBoost</key>
            <false/>
            <key>CustomSMBIOSGuid</key>
            <false/>
            <key>DisableIoMapper</key>
            <false/>
            <key>DisableLinkeditJettison</key>
            <true/>
            <key>DisableRtcChecksum</key>
            <false/>
            <key>ExtendBTFeatureFlags</key>
            <true/>
            <key>ExternalDiskIcons</key>
            <false/>
            <key>ForceSecureBootScheme</key>
            <false/>
            <key>IncreasePciBarSize</key>
            <false/>
            <key>LapicKernelPanic</key>
            <false/>
            <key>LegacyCommpage</key>
            <false/>
            <key>PanicNoKextDump</key>
            <false/>
            <key>PowerTimeoutKernelPanic</key>
            <false/>
            <key>SetApfsTrimTimeout</key>
            <integer>9999999</integer>
            <key>ThirdPartyDrives</key>
            <false/>
            <key>XhciPortLimit</key>
            <false/>
        </dict>
        <key>Scheme</key>
        <dict>
            <key>FuzzyMatch</key>
            <false/>
            <key>KernelArch</key>
            <string>x86_64</string>
            <key>KernelCache</key>
            <string>Auto</string>
        </dict>
    </dict>
    <key>Misc</key>
    <dict>
        <key>BlessOverride</key>
        <array/>
        <key>Boot</key>
        <dict>
            <key>ConsoleAttributes</key>
            <integer>15</integer>
            <key>HibernateMode</key>
            <string>None</string>
            <key>HideAuxiliary</key>
            <true/>
            <key>LauncherOption</key>
            <string>Disabled</string>
            <key>LauncherPath</key>
            <string>Default</string>
            <key>PickerAttributes</key>
            <integer>0</integer>
            <key>PickerAudioAssist</key>
            <false/>
            <key>PickerMode</key>
            <string>External</string>
            <key>PickerVariant</key>
            <string>Auto</string>
            <key>PollAppleHotKeys</key>
            <true/>
            <key>ShowPicker</key>
            <true/>
            <key>TakeoffDelay</key>
            <integer>0</integer>
            <key>Timeout</key>
            <integer>10</integer>
        </dict>
        <key>Debug</key>
        <dict>
            <key>AppleDebug</key>
            <false/>
            <key>ApplePanic</key>
            <false/>
            <key>DisableWatchDog</key>
            <false/>
            <key>DisplayDelay</key>
            <integer>0</integer>
            <key>DisplayLevel</key>
            <integer>0</integer>
            <key>SerialInit</key>
            <false/>
            <key>SysReport</key>
            <false/>
            <key>Target</key>
            <integer>0</integer>
        </dict>
        <key>Entries</key>
        <array/>
        <key>Security</key>
        <dict>
            <key>AllowNvramReset</key>
            <false/>
            <key>AllowSetDefault</key>
            <false/>
            <key>ApECID</key>
            <integer>0</integer>
            <key>AuthRestart</key>
            <false/>
            <key>BlacklistAppleUpdate</key>
            <true/>
            <key>DmgLoading</key>
            <string>Signed</string>
            <key>EnablePassword</key>
            <false/>
            <key>ExposeSensitiveData</key>
            <integer>3</integer>
            <key>HaltLevel</key>
            <integer>2147483648</integer>
            <key>PasswordHash</key>
            <data></data>
            <key>PasswordSalt</key>
            <data></data>
            <key>ScanPolicy</key>
            <integer>0</integer>
            <key>SecureBootModel</key>
            <string>Disabled</string>
            <key>Vault</key>
            <string>Optional</string>
        </dict>
        <key>Tools</key>
        <array/>
    </dict>
    <key>NVRAM</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <dict>
                <key>DefaultBackgroundColor</key>
                <data>AAAAAA==</data>
                <key>UIScale</key>
                <data>AQ==</data>
            </dict>
        </dict>
        <key>Delete</key>
        <dict>
            <key>4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14</key>
            <array>
                <string>UIScale</string>
                <string>DefaultBackgroundColor</string>
            </array>
        </dict>
        <key>LegacyEnable</key>
        <false/>
        <key>LegacyOverwrite</key>
        <false/>
        <key>LegacySchema</key>
        <dict/>
        <key>WriteFlash</key>
        <false/>
    </dict>
    <key>PlatformInfo</key>
    <dict>
        <key>Automatic</key>
        <false/>
        <key>CustomMemory</key>
        <false/>
        <key>DataHub</key>
        <dict/>
        <key>Generic</key>
        <dict/>
        <key>Memory</key>
        <dict/>
        <key>PlatformNVRAM</key>
        <dict/>
        <key>SMBIOS</key>
        <dict>
            <key>BIOSVersion</key>
            <string>9999.0.0.0.0</string>
            <key>BoardProduct</key>
            <string>Mac-7BA5B2D9E42DDD94</string>
        </dict>
        <key>UpdateDataHub</key>
        <false/>
        <key>UpdateNVRAM</key>
        <false/>
        <key>UpdateSMBIOS</key>
        <true/>
        <key>UpdateSMBIOSMode</key>
        <string>Create</string>
        <key>UseRawUuidEncoding</key>
        <false/>
    </dict>
    <key>UEFI</key>
    <dict>
        <key>APFS</key>
        <dict>
            <key>EnableJumpstart</key>
            <false/>
            <key>GlobalConnect</key>
            <false/>
            <key>HideVerbose</key>
            <false/>
            <key>JumpstartHotPlug</key>
            <false/>
            <key>MinDate</key>
            <integer>0</integer>
            <key>MinVersion</key>
            <integer>0</integer>
        </dict>
        <key>Audio</key>
        <dict>
            <key>AudioCodec</key>
            <integer>0</integer>
            <key>AudioDevice</key>
            <string></string>
            <key>AudioOut</key>
            <integer>0</integer>
            <key>AudioSupport</key>
            <false/>
            <key>MinimumVolume</key>
            <integer>0</integer>
            <key>PlayChime</key>
            <string>Disabled</string>
            <key>SetupDelay</key>
            <integer>0</integer>
            <key>VolumeAmplifier</key>
            <integer>0</integer>
        </dict>
        <key>ConnectDrivers</key>
        <true/>
        <key>Drivers</key>
        <array>
            <string>OpenRuntime.efi</string>
            <string>OpenCanopy.efi</string>
        </array>
        <key>Input</key>
        <dict>
            <key>KeyFiltering</key>
            <false/>
            <key>KeyForgetThreshold</key>
            <integer>0</integer>
            <key>KeyMergeThreshold</key>
            <integer>0</integer>
            <key>KeySupport</key>
            <false/>
            <key>KeySupportMode</key>
            <string>Auto</string>
            <key>KeySwap</key>
            <false/>
            <key>PointerSupport</key>
            <false/>
            <key>PointerSupportMode</key>
            <string></string>
            <key>TimerResolution</key>
            <integer>0</integer>
        </dict>
        <key>Output</key>
        <dict>
            <key>ClearScreenOnModeSwitch</key>
            <false/>
            <key>ConsoleMode</key>
            <string></string>
            <key>DirectGopRendering</key>
            <true/>
            <key>ForceResolution</key>
            <false/>
            <key>IgnoreTextInGraphics</key>
            <false/>
            <key>ProvideConsoleGop</key>
            <true/>
            <key>ReconnectOnResChange</key>
            <false/>
            <key>ReplaceTabWithSpace</key>
            <false/>
            <key>Resolution</key>
            <string>Max</string>
            <key>SanitiseClearScreen</key>
            <false/>
            <key>TextRenderer</key>
            <string>BuiltinGraphics</string>
            <key>UgaPassThrough</key>
            <false/>
        </dict>
        <key>ProtocolOverrides</key>
        <dict>
            <key>AppleAudio</key>
            <false/>
            <key>AppleBootPolicy</key>
            <true/>
            <key>AppleDebugLog</key>
            <false/>
            <key>AppleEvent</key>
            <false/>
            <key>AppleFramebufferInfo</key>
            <false/>
            <key>AppleImageConversion</key>
            <false/>
            <key>AppleImg4Verification</key>
            <false/>
            <key>AppleKeyMap</key>
            <false/>
            <key>AppleRtcRam</key>
            <false/>
            <key>AppleSecureBoot</key>
            <false/>
            <key>AppleSmcIo</key>
            <false/>
            <key>AppleUserInterfaceTheme</key>
            <true/>
            <key>DataHub</key>
            <false/>
            <key>DeviceProperties</key>
            <false/>
            <key>FirmwareVolume</key>
            <false/>
            <key>HashServices</key>
            <false/>
            <key>OSInfo</key>
            <false/>
            <key>UnicodeCollation</key>
            <false/>
        </dict>
        <key>Quirks</key>
        <dict>
            <key>DisableSecurityPolicy</key>
            <false/>
            <key>ExitBootServicesDelay</key>
            <integer>0</integer>
            <key>IgnoreInvalidFlexRatio</key>
            <false/>
            <key>ReleaseUsbOwnership</key>
            <false/>
            <key>RequestBootVarRouting</key>
            <true/>
            <key>TscSyncTimeout</key>
            <integer>0</integer>
            <key>UnblockFsConnect</key>
            <false/>
        </dict>
        <key>ReservedMemory</key>
        <array/>
    </dict>
</dict>
</plist>

 

[amstel78]

@cdf - take a look at my config.plist and screenshot. I'm using the config.plist from the first post with spoofing of the BoardID to enable continuity and updates (worked for 11.2.1 and 11.2.2) and VMM off - my processor is "Unknown". You can see below that VMM is off.

What do you have for ProcessorType?

 

[MacForumsUser]

This sounds like OC is not properly blessed. You might want to boot natively into Mojave, reset the NVRAM, and rebless OC. If you were previously using BootProtect (now LauncherOption), your Mac may be using a leftover bootstrap entry. The above steps should take care of that.

I think I can do that, but I just want to make sure I have it straight, since the only way I can boot natively into Mojave is to remove all other drives from the system:

1. Remove all other drives except Mojave from the machine
2. Boot to Mojave
3. Restart the machine and hold Command + Option + P + R > let Mojave boot
4. Shut down the machine
5. Insert Big Sur/OC drive
6. Boot to recovery mode (or can I boot to Mojave again to bless the other drive?)
7. Bless the EFI partition on the Big Sur drive

 

[nocomprendo]

Is there a way to integrate the WiFi patch from Martin Lo's 0.6.3 OC package into 0.6.6?

Hey. I'm on the same situation. Big Sur, no wifi... And wondering if it would work with Martin Lo's OC package.
Did you find a way to do this?