MP 1,1-5,1 SurPlus - The Big Sur/Monterey fix you've been waiting for.

[TECK]

Any tips how to fix this?

The only time I disable SIP is when I refresh the BootROM. I never disabled SIP for OC bootloader or any macOS upgrades, have you asked the question on @h9826790's thread? Just curious, where did you read you need to disable SIP? I have not installed yet the 2 patches, I'm waiting for OC 0.7.4 next week.

 

[cdf]

The only time I disable SIP is when I refresh the BootROM. I never disabled SIP for OC bootloader or any macOS upgrades, have you asked the question on @h9826790's thread? Just curious, where did you read you need to disable SIP? I have not installed yet the 2 patches, I'm waiting for OC 0.7.4 next week.

There is no need to have SIP disabled for SurPlus.

Off topic: In fact, SIP should generally remain enabled just like on a supported Mac, and if there is reason for disabling it, it should be managed using Recovery as intended by Apple, and not through OpenCore, which can override the setting and cause confusion.

 

[Conzpiral]

today i update my "handmade" oc install via Martin Lo's latest package (0.7.3 V2).
After everything went fine, i wanted to reenable sip. I did this and now i see the following if checking sip is enabled or not.

In my custom Martin Lo's config plist I just 'commented out' his SIP configuration an enabled the 'AllowToggleSip' instead. Works perfect, you disable SIP on boot when you need it, and it will automatically fall back to disabled on next reboot.

You comment out parts of the config with '<!--' and '-->'. So find the 'csr-active-config' (the first one in Martins config.plist, not the second) and add those so it looks like this:

<!--
<key>csr-active-config</key>
<data>fwgAAA==</data>
-->

Then you find 'AllowToggleSip' and change it from 'false' to 'true':

<key>AllowToggleSip</key>
<true/>

This should give you a new icon on the right side in OC boot menu where you can toggle SIP on or off... this is a lot quicker than have to boot into Recovery mode first to disable SIP.

 

[The Spirit]

In my custom Martin Lo's config plist I just 'commented out' his SIP configuration an enabled the 'AllowToggleSip' instead. Works perfect, you disable SIP on boot when you need it, and it will automatically fall back to disabled on next reboot.

You comment out parts of the config with '<!--' and '-->'. So find the 'csr-active-config' (the first one in Martins config.plist, not the second) and add those so it looks like this:

<!--
<key>csr-active-config</key>
<data>fwgAAA==</data>
-->

Then you find 'AllowToggleSip' and change it from 'false' to 'true':

<key>AllowToggleSip</key>
<true/>

This should give you a new icon on the right side in OC boot menu where you can toggle SIP on or off... this is a lot quicker than have to boot into Recovery mode first to disable SIP.

i did like you wrote.
but it makes no difference if i turn sip on or of via oc menu.
if i boot into big sur and run "crsutil status" within terminal, the output stays the same.

 

[paalb]

but it makes no difference if i turn sip on or of via oc menu.
if i boot into big sur and run "crsutil status" within terminal, the output stays the same.

It is in your OpenCore configuration, see: https://dortania.github.io/OpenCore...oting/extended/post-issues.html#disabling-sip This has nothing to do with SurPlus.

 

[TECK]

There is no need to have SIP disabled for SurPlus.

That’s what I thought, I was thinking macOS 12 has some new security feature enabled.

 

[Conzpiral]

i did like you wrote.
but it makes no difference if i turn sip on or of via oc menu.
if i boot into big sur and run "crsutil status" within terminal, the output stays the same.

Did you try a cold reboot, or just warm?
Edit: Like @internetzel mention in next post, maybe you need a (3x) NVRAM reset?

 

[internetzel]

today i update my "handmade" oc install via Martin Lo's latest package (0.7.3 V2).
After everything went fine, i wanted to reenable sip. I did this and now i see the following if checking sip is enabled or not.

View attachment 1853085
Any tips how to fix this?
Thanks

I experienced that issue as well. And if I remember correctly I had to reset the NVRAM.

 

[Fawzi]

I mistakenly updated my 5,1 to Big Sur 11.6. I'm running my old mac as a headless server and didn't notice I was still screen sharing and not on my local Mac. Anyway, the update went fine even with OC 0.6.6. I just didn't touch anything nor have I rebooted since then.
Just installed OC 0.7.3 (v2). Rebooted. Enabled WiFi. Rebooted. Runs as smoothly as ever !
Thanks for your tireless efforts. Where's that donation link again ? ?

 

[GSXB]

Update to this post, I’ve installed 0,7,3 v2 and big sur booted right up and finished it installation but no Bluetooth. I’ve applied the surplus patch to 0,6,8 now I have Bluetooth and all booting correctly. However upgrading Catalina to Monterey throws a firmware error ???

Update 3 created a usb installer from the app booted up and after two false starts it read the usb 7 reboots later I’m on montereys desktop
Many thanks to martin lo and syncretic
???

 

[Nekapsule]

Used Surplus on another Hackintosh (also using a CPU that doesn't have the rdrand instructions, an i7-950) and it works flawlessly. The Xeon 5690 based one still boots without missing a beat either. Thanks again!

 

[KevinClark]

Using Martin Lo 073 V2 + SSDT Titan Ridge + Nighshift + Mac Pro 2019 Spoof works great for Big Sur 11.6
Is there any risk to update the Os now from apple software update ?

 

[quad121]

I’ve just updated Catalina to Big Sur 11.6 on a cMP 5,1 On a nvme. It works perfectly, just waiting on a restore from Time capsule backup which is taking forever!
a big thank you to Martin and Syncretic for all there hard work and we all appreciate you very much

 

[The Spirit]

I experienced that issue as well. And if I remember correctly I had to reset the NVRAM.

i did a NVRAM reset, but it did not work.
i pressed cmd+alt+p+r until i heard the chime 5 times.
but still the same problem.
any other ideas?

 

[PeterHolbrook]

^You need to bless the OC EFI boot!!!

 

[shadow_999]

Updated to 11.6 thanks to surplus. Many thanks. I did the update through vnc and it works flawlesly. My cMP was unable to boot it using latebloom.

 

[tjod]

I applied the patch yesterday to my (early, pre-race condition) 11.3 beta, and was able to upgrade to 11.6 (non-beta).

Now trying to get back into beta and install Monterey but seem to be stuck in a loop where upon reboot after a seemingly good install sequence, I'm left back at 11.6. I'll be checking the state of the EFI later today, and re-bless after checking the config.plist.

 

[JohnD]

today i update my "handmade" oc install via Martin Lo's latest package (0.7.3 V2).
After everything went fine, i wanted to reenable sip. I did this and now i see the following if checking sip is enabled or not.

View attachment 1853085
Any tips how to fix this?
Thanks

RTFM! - It's perfectly normal and expected.

Since you've downloaded Martin's config, you scrolled by all the instructions and videos he provided. Go back and look for his SIP video. Martin's config disables SIP within OpenCore. You need SIP disabled to bless a new OpenCore EFI, but can enable it again if you choose. You just have to... RTFM.

 

[JohnD]

Okay, did two tests:

1. Tried to install Big Sur 11.6 on the NVME - this failed in the same way, ended with the forbidden symbol. Removed that.
2. Installed Big Sur 11.2.3 on the NVME - this worked without any issues and I'm using it now to reply to you. The installer migrated everything across no issues.

Both these were done using the downloaded installers and creating a USB installer from them and attempting to install a fresh copy. The only other thing to note is I have csrutil disabled, probably unrelated.


I've definitely got the 0.7.3 installer running as provided, the PLIST is attached. I can't pick what's going on - it's a bit beyond my abilities I'm afraid. But I'm happy to keep trying.

System report shows:

Hardware Overview:

  Model Name:    Mac Pro
  Model Identifier:    MacPro5,1
  Processor Name:    6-Core Intel Xeon
  Processor Speed:    3.46 GHz
  Number of Processors:    2
  Total Number of Cores:    12
  L2 Cache (per Core):    256 KB
  L3 Cache (per Processor):    12 MB
  Hyper-Threading Technology:    Enabled
  Memory:    128 GB
  System Firmware Version:    9144.0.7.3.1
  SMC Version (system):    1.39f11
  SMC Version (processor tray):    1.39f11
  Serial Number (system):    (removed)
  Hardware UUID:    44B9E501-9C11-561C-B8D9-11A75B185A17
  Provisioning UDID:    44B9E501-9C11-561C-B8D9-11A75B185A17

Looks like you have Martin's 0.7.3 V2 config running. Interesting your 980 NVMe doesn't like 11.6, but then again, the manufacturer (Samsung) even says it shouldn't work in PCIe v2.0 so... maybe you've been lucky thus far?

When you installed 11.2.3, were you using Martin's 0.7.3 V2 config? To test if this is SurPlus related, you could reduce the minimum kernel version and re-install 11.2.3 (with SurPlus enabled).

 

[quad121]

After the restore I installed the latest updates and restarted.
Now I'm in a Boot loop it starts up goes to the log in screen then immediately reboots
If someone can steal me in the right direction to correct what ever is happening greatfully appreciated
Here is the Error Log:
panic(cpu 20 caller 0xffffff801e5c4996): Kernel trap at 0xffffff7fbb1bd1c8, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff801ee20000, CR3: 0x0000001049452022, CR4: 0x00000000000226e0
RAX: 0xffffff801ee20000, RBX: 0xffffffa1aa445000, RCX: 0xffffff8000000000, RDX: 0x0000000000000000
RSP: 0xffffffa1a5e43b50, RBP: 0xffffffa1a5e43b90, RSI: 0xffffffa14711f000, RDI: 0xffffff7fbb1d2e34
R8: 0xffffff93d5bc6e90, R9: 0x0000000000001000, R10: 0x0000000000000000, R11: 0x0000000029cfd000
R12: 0x26bf12e3af1400c6, R13: 0xffffffa1aa445000, R14: 0xffffff7fbb1d2e34, R15: 0xffffffa14711f000
RFL: 0x0000000000010286, RIP: 0xffffff7fbb1bd1c8, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff801ee20000, Error code: 0x0000000000000000, Fault CPU: 0x14, PL: 0, VF: 2

Backtrace (CPU 20), Frame : Return Address
0xffffffa1a5e43570 : 0xffffff801e48cfdd
0xffffffa1a5e435c0 : 0xffffff801e5d3fd3
0xffffffa1a5e43600 : 0xffffff801e5c45ca
0xffffffa1a5e43650 : 0xffffff801e431a2f
0xffffffa1a5e43670 : 0xffffff801e48c7fd
0xffffffa1a5e43790 : 0xffffff801e48caf3
0xffffffa1a5e43800 : 0xffffff801ec9cdca
0xffffffa1a5e43870 : 0xffffff801e5c4996
0xffffffa1a5e439f0 : 0xffffff801e5c467d
0xffffffa1a5e43a40 : 0xffffff801e431a2f
0xffffffa1a5e43a60 : 0xffffff7fbb1bd1c8
0xffffffa1a5e43b90 : 0xffffff7fbb1c9db5
0xffffffa1a5e43bc0 : 0xffffff7fbb1cb142
0xffffffa1a5e43be0 : 0xffffff7fbb1c6548
0xffffffa1a5e43c60 : 0xffffff7fbb1c629f
0xffffffa1a5e43c90 : 0xffffff7fbb1bc9bd
0xffffffa1a5e43ce0 : 0xffffff801ec262f3
0xffffffa1a5e43d40 : 0xffffff801e57f26f
0xffffffa1a5e43d90 : 0xffffff801e49265d
0xffffffa1a5e43e00 : 0xffffff801e468cd5
0xffffffa1a5e43e60 : 0xffffff801e4801e2
0xffffffa1a5e43ef0 : 0xffffff801e5a869d
0xffffffa1a5e43fa0 : 0xffffff801e432216
Kernel Extensions in backtrace:
com.eltima.kext.vusb(102.0)[4FC4F8F1-AF3D-3B72-92F5-6A870DE69A28]@0xffffff7fbb1ba000->0xffffff7fbb1d3fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[4E85D41F-6AD7-3C24-911C-A8B80B599F86]@0xffffff8020f6c000->0xffffff8020f94fff
dependency: com.apple.iokit.IOUSBFamily(900.4.2)[046C4128-958C-3B22-A62C-EDB1883C124B]@0xffffff80211e3000->0xffffff8021248fff
dependency: com.apple.iokit.IOUSBHostFamily(1.2)[854E579F-B284-3221-B1FC-D4A0FDC1F056]@0xffffff802128a000->0xffffff8021318fff

Process name corresponding to current thread: eveusbd
Boot args: -lilubetaall -wegbeta agdpmod=pikera shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0

Mac OS version:
20G165

Kernel version:
Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64
Kernel UUID: C2591F4E-EE82-33CC-8C59-DB81D9AD80DD
KernelCache slide: 0x000000001e200000
KernelCache base: 0xffffff801e400000
Kernel slide: 0x000000001e210000
Kernel text base: 0xffffff801e410000
__HIB text base: 0xffffff801e300000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 34131166573
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000007f2605040
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000025868a78d4 0x0000000000000000
last started kext at 33357096153: com.eltima.kext.vusb 102.0 (addr 0xffffff7fbb1ba000, size 106496)
loaded kexts:
com.eltima.kext.vusb 102.0
com.eltima.kext.vic 102.0
com.malwarebytes.mbam.rtprotection 4.0.30
com.parallels.virtualsound 1.0.36 36
com.eltima.kext.elogger 102.0
com.Perfect.Driver.SystemAudioRecorder 1.0.0
com.Cycling74.driver.Soundflower 1.6.7
at.obdev.nke.LittleSnitch 5430
com.metakine.handsoff.driver 4.0.1
com.intel.driver.EnergyDriver 2.0
as.vit9696.WhateverGreen 1.5.3
as.vit9696.Lilu 1.5.6
>!A!BMultitouch 99
>AGPM 122.1
@filesystems.autofs 3.0
@fileutil 20.036.15
@filesystems.ntfs 3.14.3
>!AUpstreamUserClient 3.6.8
>!AMCCSControl 1.14
@kext.AMDFramebuffer 4.0.6
@kext.AMDRadeonServiceManager 4.0.6
>AudioAUUC 1.70
>!AMikeyHIDDriver 131
@kext.AMDRadeonX4000 4.0.6
>!AGraphicsDevicePolicy 6.3.5
@AGDCPluginDisplayMetrics 6.3.5
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
|IO!BSerialManager 8.0.5d7
>!AHDAHardwareConfigDriver 283.15
@Dont_Steal_Mac_OS_X 7.0.0
>!AHV 1
>!AMikeyDriver 283.15
>!AHDA 283.15
>!ADiskImages2 1
@kext.AMD9500!C 4.0.6
>!AFWOHCI 5.7.4
>!AGFXHDA 100.1.433
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!IMCEReporter 115
>!ALPC 3.1
>!AFIVRDriver 4.1.0
>!A!ISlowAdaptiveClocking 4.0.0
|IO!BUSBDFU 8.0.5d7
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.100.11
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
|SCSITaskUserClient 436.140.1
@filesystems.apfs 1677.141.2
>!AAHCIPort 346.100.2
>!I82574LEthernet 2.7.2
@private.KextAudit 1.0
>!ARTC 2.0
>!AHPET 1.8
>!AACPIButtons 6.1
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 311
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
>IO!BHIDDriver 8.0.5d7
>!AMultitouchDriver 4440.3
>!AInputDeviceSupport 4400.35
>!UAudio 405.39
@kext.triggers 1.0
@kext.AMDRadeonX4000HWLibs 1.0
|IOAccelerator!F2 442.9
@kext.AMDRadeonX4000HWServices 4.0.6
>!AGraphicsControl 6.3.5
|IOSerial!F 11
|IOAVB!F 940.4
|IOEthernetAVB!C 1.1.0
>DspFuncLib 283.15
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
@!AGPUWrangler 6.3.5
>!ASMBusPCI 1.0.14d1
@kext.AMDSupport 4.0.6
@!AGraphicsDeviceControl 6.3.5
|IOFireWire!F 4.8.3
|IONDRVSupport 585.1
>IOPlatformPluginLegacy 1.0.0
>!AHDA!C 283.15
|IOHDA!F 283.15
|IOGraphics!F 585.1
|IOAudio!F 300.6.1
@vecLib.kext 1.2.0
>IOPlatformPlugin!F 6.0.0d8
@plugin.IOgPTPPlugin 985.2
|IOSlowAdaptiveClocking!F 1.0.0
|Broadcom!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CUSBTransport 8.0.5d7
|IO!BHost!CTransport 8.0.5d7
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
|IOAHCIBlock!S 332
>!ABSDKextStarter 3
|IOSurface 290.8.1
|IOSkywalk!F 1
>mDNSOffloadUserClient 1.0.1b8
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 436.140.1
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
|IOAHCISerialATAPI 268
>!AXsanScheme 3
|IOAHCI!F 294.100.1
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>usb.!UEHCIPCI 1.2
|IONVMe!F 2.1.0
>usb.!UUHCIPCI 1.2
>usb.!UUHCI 1.2
>usb.!UEHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 985.2
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.5d7
|IOReport!F 47
|IO!BPacketLogger 8.0.5d7
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.141.1
|IOUSBMass!SDriver 184.140.2
|IOSCSIBlockCommandsDevice 436.140.1
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.140.1
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 11.1
@kec.Libm 1

 

[ifrit05]

[...]
Kernel Extensions in backtrace:
com.eltima.kext.vusb(102.0)[4FC4F8F1-AF3D-3B72-92F5-6A870DE69A28]@0xffffff7fbb1ba000->0xffffff7fbb1d3fff

Seems like you have FlexiHub's USB over Network Kext installed (com.eltima.kext.vusb) and is causing Kernel Panics on boot.

 

[mode11]

Incredible work Syncretic and others. I can finally upgrade from Catalina!

Does this patch require the latest OC (0.7.3), or is 0.7.1 OK?

 

[quad121]

Seems like you have FlexiHub's USB over Network Kext installed (com.eltima.kext.vusb) and is causing Kernel Panics on boot.

where can this Kext be accessed to disable?

 

[ifrit05]

Does this patch require the latest OC (0.7.3), or is 0.7.1 OK?

I'm currently using OC 6.9 and it works perfect.

where can this Kext be accessed to disable?

Driver Installation (macOS version)

Drivers for Virtual USB Devices FlexiHub Redistributable archive contains three packages with the drivers for various versions of Mac OS: Flexihub_Driver-10_09.pkg - drivers for Mac OS 10.9 Mavericks Flexihub_Driver-10_10.pkg - drivers for Mac OS 10.10 Yosemite Flexihub_Driver-10_11.pkg -...

wiki.eltima.com

 

[quad121]

Thankyou ifrit05, I have now managed to get Big Sur to boot, I did notice that it asked if i wanted to enable 'eltima daemon' which i rejected.
is there a way to remove this 'Altima' Daemon from popping up?

edit: I think I've found it under /Library/LaunchDaemons.