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

[ifrit05]

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.

Yes, you can disable daemons through launchctl, or use LaunchControl app for a GUI.

 

[JedNZ]

Anyone else have success using MyBootMgr? Any special steps you have to make? Can't seem to bless my ESP - not sure if it's to do with 0.7.3b or something else, but if others have made it work and have ideas then that will help me problem solve.

 

[startergo]

I updated my Big Sur to the 'Device Support Update' on my MacMini3,1. I had latebloom and it always panicked afterwards on boot. I had an external drive with 11.1 through which I booted and installed latest nightly OCLP, which included SurPlus alongside other updates and was able to boot again.

 

[avro707]

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).

Houston - we have ignition and lift-off! ?

I've got 11.6 Big Sur running on the Samsung 980 Pro NVME drive (which is using the Sonnet controller card).

What changed is I did the NVRAM trick, Command+Opt+P+R.

This had the effect of making the Opencore boot picker appear much faster - and got rid of the forbidden sign I was getting before. I also put in the old Radeon 5870 so I could see the standard Apple grey boot-up screens.

Then ran the 11.6 update from within 11.2.3 on the NVME drive. This did its required restarts and ran smoothly. Amazing.

Syncretic, h9826790 and others who assisted, amazing - this is a 2010 computer and it's running the latest available Mac OS. Wow. Thanks.

 

[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
I now have Monterey installed and running albeit with no WiFi and no Bluetooth, time for some more upgrades. Beta 7 onwards requires the VMM flag to be enabled to stop the firmware error

 

[avro707]

Update 3
I now have Monterey installed and running albeit with no WiFi and no Bluetooth, time for some more upgrades. Beta 7 onwards requires the VMM flag to be enabled to stop the firmware error

If you've not done it already, I'd recommend using the WIFI and bluetooth upgrade kit:

Mac Pro 4,1 5,1 Genuine Apple WiFi Upgrade Kit 802.11ac a/b/g/n/ac Bluetooth 4.0 | eBay

Mac Pro 2009 2010 2012 Wifi & Bluetooth Upgrade Kit Genuine Apple WiFi 802.11 a/b/g/n/ac and Bluetooth 4.0 card. Upgrade to802.11ac faster WiFi. For Mac Pro 4,1 or 5,1. Bluetooth data cable. Bluetooth antenna extension cable.

www.ebay.com

I applied this to my 5,1. Just watch the various videos on Youtube that deal with this and you should be able to upgrade as well. Not only will you get wireless back, but you get things like Airdrop and other conveniences that make your classic Mac Pro feel a bit less classic. Less reliance on workarounds too.

But that's not for this topic, this is more for Opencore and the SurPlus effort.

 

[MacRumors3590]

If you've not done it already, I'd recommend using the WIFI and bluetooth upgrade kit:

Mac Pro 4,1 5,1 Genuine Apple WiFi Upgrade Kit 802.11ac a/b/g/n/ac Bluetooth 4.0 | eBay

Mac Pro 2009 2010 2012 Wifi & Bluetooth Upgrade Kit Genuine Apple WiFi 802.11 a/b/g/n/ac and Bluetooth 4.0 card. Upgrade to802.11ac faster WiFi. For Mac Pro 4,1 or 5,1. Bluetooth data cable. Bluetooth antenna extension cable.

www.ebay.com

I applied this to my 5,1. Just watch the various videos on Youtube that deal with this and you should be able to upgrade as well. Not only will you get wireless back, but you get things like Airdrop and other conveniences that make your classic Mac Pro feel a bit less classic. Less reliance on workarounds too.

with OCLP 0.3.0 i have WIFI/BT working without replacing the cards.

 

[Appler007]

The Nightly download of OCLP v0.3.0 is working great and includes SurPlus!!!!!!!!!!
THANK YOU DEVELOPERS!!!!!! ?

Where can I find the OCLP v0.3.0?

 

[MacRumors3590]

Where can I find the OCLP v0.3.0?

This is a SurPlus thread,
Go here for OpenCore-Legacy-Patcher

 

[Appler007]

Sorry for OffTopic. But this 0.25 !

 

[MacRumors3590]

Sorry for OffTopic. But this 0.25 !

Scroll down on that page and download the "Nightly Builds"

 

[Ausdauersportler]

Sorry for OffTopic. But this 0.25 !

To end your off topic agony here:

Check the OLCP GitHub download page and scroll down until you find the links to the nightly builds - these are experimental versions offering new features and sometimes new challenges. If you want to get help about OCLP check the Support statement on the very same page a few lines above.

 

[Appler007]

Thank you all!

 

[minomac]

Hallo,
I tried the SurPlus fix to try booting from my Mac Pro 5.1, on a Big Sur SSD.

A little of brief: I managed to get an accelerated H265 OC Mojave using the "dual core package" from this these two guys:

(every other method failed).

Then i created a full backup on a separate HDD, and started to try the Big Sure update.
I tried Open-Core Patcher, then tried the manual method with the OC release
but I tend to get black loading screen with the Apple and the progress bar at 0%.
Maybe the dual CPU configuration (actually 8 core) of my mac pro creates issues?

Note /1: this latest config.plist should be cleaned from Latebloom
Note /2: the above two did a little error placing the content of EFI folder directly in the EFI Volume...


Thanks

 

[Conzpiral]

Hello @avro707 - The Samsung 980 series NVMe SSD's are not compatible with the Mac Pro. Per a Samsung support agent I spoke with, the 980 is a PCIe v4.0 NVMe, and is not backwards compatible with PCIe v2.0. What's likely happening is your machine only sees the drive on a cold boot, but it won't survive a warm boot. Is it new? Have you previously installed an OS to it?

Beaware, it seems I too got that warm boot problem but with a Samsung SSD 870 EVO SATA 2.5" 2TB (Firmware SVT01B6Q) drive in my Bay 4 (did not try to change bay yet). Drive only works after cold start even if it shows up in OC boot menu on warm boot.
When installing/updating OS on this drive I have to make sure I power off my computer from OC boot menu on each warm boots it does, then everything goes fine.

My Samsung SSD 860 EVO SATA 2.5" 2TB (Firmware RVT04B6Q) in Bay 1 is working like it should.

I also got a Ableconn PEXM2-130 Dual PCIe card with two 1TB/2TB Samsung SSD 970 EVO Plus NVMe (Firmware 2B2QEXM7) which is working great and with incredible speed.

 

[Broadw3ll]

im having problems to boot the installer it gets recognized by opencore and it loads but then the loading bar crash before getting through the middle then the screen goes black and the machine restarts but without chime sound I have to do a pram reset to get the chime back, I start my daily driver and I get the notification of a problem had occur and the machine had to power off, im gonna attach the report that I get but its kinda weird talks about a panic related to the cpu I use this machine almost every day without any problem in Catalina 10.15.7 (19H524)

panic(cpu 0 caller 0xffffff8012c00940): "root image authentication failed (err = 22)\n"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.81.3/bsd/kern/imageboot.c:1015
Backtrace (CPU 0), Frame : Return Address
0xffffffa0504fb840 : 0xffffff80126bab4d
0xffffffa0504fb890 : 0xffffff80127fd7e3
0xffffffa0504fb8d0 : 0xffffff80127ede1a
0xffffffa0504fb920 : 0xffffff801265fa2f
0xffffffa0504fb940 : 0xffffff80126ba3ed
0xffffffa0504fba60 : 0xffffff80126ba6d8
0xffffffa0504fbad0 : 0xffffff8012ebef9a
0xffffffa0504fbb40 : 0xffffff8012c00940
0xffffffa0504fbe70 : 0xffffff80126e8343
0xffffffa0504fbfa0 : 0xffffff801265f13e


Process name corresponding to current thread: kernel_task
Boot args: -lilubetaall -wegbeta agdpmod=pikera shikigva=80 unfairgva=1 mbasd=1 -wegtree -no_compat_check no32exec=0 root-dmg=file:///BaseSystem/BaseSystem.dmg
Mac OS version:
Not yet set
Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x0000000012400000
KernelCache base: 0xffffff8012600000
Kernel slide: 0x0000000012410000
Kernel text base: 0xffffff8012610000
__HIB text base: 0xffffff8012500000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0


System uptime in nanoseconds: 31902887738
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000000076d8f779b
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000257742eecc 0x0000000000000000
last started kext at 2505947345: |IO!BUSBDFU 8.0.3d9 (addr 0xffffff8014c60000, size 8192)
loaded kexts:
as.vit9696.WhateverGreen 1.5.3
as.vit9696.Lilu 1.5.6
|IO!BUSBDFU 8.0.3d9
@filesystems.apfs 1677.81.1
|SCSITaskUserClient 436.40.6
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.60.1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@private.KextAudit 1.0
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 346
>!I82574LEthernet 2.7.2
>!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 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
|Broadcom!BHost!CUSBTransport 8.0.3d9
|IO!BHost!CUSBTransport 8.0.3d9
|IO!BHost!CTransport 8.0.3d9
>usb.IOUSBHostHIDDevice 1.2
|IOSCSIMultimediaCommandsDevice 436.40.6
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>!AXsanScheme 3
|IOAHCIBlock!S 332
|IOAHCISerialATAPI 268
>usb.!UHub 1.2
>!AThunderboltPCIDownAdapter 4.1.1
>!AThunderboltDPOutAdapter 8.1.4
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!A!ILpssI2C 3.0.60
>!A!ILpssDmac 3.0.60
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!ABSDKextStarter 3
|IOSurface 289.3
@filesystems.hfs.encodings.kext 1
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IOAHCI!F 294
>usb.!UEHCIPCI 1.2
>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 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.3d9
|IOReport!F 47
--------------------------------------------------------------
Does someone had an idea what's going on ?

 

[ifrit05]

im having problems to boot the installer [...]

Might want to boot in verbose mode (cmd-v) to get a better idea what's happening when it hangs/crashes.

 

[minomac]

Hallo,
I tried the SurPlus fix to try booting from my Mac Pro 5.1, on a Big Sur SSD.

A little of brief: I managed to get an accelerated H265 OC Mojave using the "dual core package" from this these two guys:

(every other method failed).

Then i created a full backup on a separate HDD, and started to try the Big Sure update.
I tried Open-Core Patcher, then tried the manual method with the OC release
but I tend to get black loading screen with the Apple and the progress bar at 0%.
Maybe the dual CPU configuration (actually 8 core) of my mac pro creates issues?

Note /1: this latest config.plist should be cleaned from Latebloom
Note /2: the above two did a little error placing the content of EFI folder directly in the EFI Volume...


Thanks

Bump

 

[KvR]

Bump

Impatient much? Rewarding bad behaviour: You've added the patch on the wrong place in your plist. Just follow the instructions at the beginning of the thread.

 

[internetzel]

Regarding Sandy Bridge CPUs not being affected by the race condition, I researched a little bit and found out the following:

• According to the the public kernel sources, a private SHA-256 is used to initialize the PRNG - @Syncretic found SHA-1, and that's what appears in the sources until including Mojave. Do binaries and released sources match here?
• According to some older CoreCrypto sources Apple seems to have deleted later, the (potentially deadlock causing) CoreCrypto SHA256 algorithm is accelerated by the AVX1 instruction set on Sandy Bridge and Ivy Bridge CPUs, and by AVX2 on all later generations. On the deadlock affected CPUs SSSE3 is used.

Now one potentially interesting difference I could find is the fact that the usage of AVX instructions make the kernel allocate a larger memory zone for saving the FPU/SIMD context and registers (in fpu_module_init()).
That would be one difference in the code path taken - or are the Sandy/Ivy bridge Macs just lucky because their hardware causes the deadlock to never happen?
Edit: The allocation for the extra AVX registers is not only larger but the saving/restoring is also done using different instructions.

 

[PeterHolbrook]

At long last, I'm finally in front of my cMP 5,1. No issues whatsoever using SurPlus and OC 0.7.4. Absolute perfection.

 

[MacRumors3590]

At long last, I'm finally in front of my cMP 5,1. No issues whatsoever using SurPlus and OC 0.7.4. Absolute perfection.

same here with my OCLP v0.3.0 and my SurPlus!!! Awesome!!!!!!

 

[6DecadesLater]

I am dependent on my MP5,1 for working from home (which I have been for 18 months) so I have to sit back a bit and watch the threads before diving in. With the current torrent of upgrade successes I jumped in. I used OC 0.7.4 including hybridization and SurPlus. I used the regular system update after upgrading OC (VMM off). It worked like a charm. No reboot interventions at all - it just worked as if it was a supported Mac. I am now at BS 11.6. Everything looks great. Configuration in signature. Thank you so much for the dedicated work. Next step is donation.

 

[avro707]

I am dependent on my MP5,1 for working from home (which I have been for 18 months) so I have to sit back a bit and watch the threads before diving in. With the current torrent of upgrade successes I jumped in. I used OC 0.7.4 including hybridization and SurPlus. I used the regular system update after upgrading OC (VMM off). It worked like a charm. No reboot interventions at all - it just worked as if it was a supported Mac. I am now at BS 11.6. Everything looks great. Configuration in signature. Thank you so much for the dedicated work. Next step is donation.

My situation is the same, I'm using my dual X5960 5,1 full time every day now with the work from home because of the lockdowns we still have, it's a far better machine than my work computers. I'm under pressure to get stuff done with impossible deadlines. Once I did the command-option-P-R with mine then tried the surplus patch it just worked, 11.6 is good so far.. I'm pretty sure Monterey beta versions would now work too but I won't try them because this is the machine I use for work.

I kept the previous Big Sur installation just in case (and even a Mojave install on classic 1TB HDD), but it seems fine. Not a single problem. The biggest issue I'll face is going back to the office and the work computers will all be so slow and under powered in comparison.

 

[trifero]

Mine situation is the same, I'm using my dual X5960 5,1 full time every day now with the work from home because of the lockdowns we still have, it's a far better machine than my work computers. I'm under pressure to get stuff done with impossible deadlines. Once I did the command-option-P-R with mine then tried the surplus patch it just worked. I'm pretty sure Monterey beta versions would now work too but I won't try them because this is the machine I use for work.

I kept the previous Big Sur installation just in case (and even a Mojave install on classic 1TB HDD), but it seems fine. Not a single problem. The biggest issue I'll face is going back to the office and the work computers will all be so slow and underpowered in comparison.

Anyway, Catalina patched works like a charm. Still more than one year of official support.