It looks like he used a 0.7.3 validation tool to check a 0.7.2 config. If that’s the case, then not valid.So is not valid?
It looks like he used a 0.7.3 validation tool to check a 0.7.2 config. If that’s the case, then not valid.So is not valid?
Does the order in which the surplus fix is insterted matter? I wouldn't know but why don't you trying pasting it before the IONVMeFamily Patch?I tried it with installing Monterey Beta 6 (installed from a USB) on NVME drive using a Sonnet card (and Samsung 980 Evo).
This wasn't successful. Installer got to about 80%, did a restart and that was it, black screen, system wouldn't boot up and powered down. I took the Sonnet card out and then the system eventually started up on my normal 11.2.3 but without the Opencore bootscreen. So it looks like that went.
I'm just running the bless script again and about to restart and hoping I get my boot screen back.
My Config plist is attached.
I loaded up my old Mojave drive and formatted that NVME again to get rid of Monterey Beta and now it's working again on 11.2.3.It looks like he used a 0.7.3 validation tool to check a 0.7.2 config. If that’s the case, then not valid.
Does the order in which the surplus fix is insterted matter? I wouldn't know but why don't you trying pasting it before the IONVMeFamily Patch?
You are not booting from OC.I loaded up my old Mojave drive and formatted that NVME again to get rid of Monterey Beta and now it's working again on 11.2.3.
If there are any further ideas I'll try them again tomorrow night - but it's a bit of a fuss having to put the old Mojave in and change to the old Radeon 5870 graphics card so I can see the old bootmenu (to boot into that).
When I did try and let it run (before formatting the NVME) it just gave me the dreaded round circle with the slash through it then switched off.
And yes, I have 0.7.2 config.
I have swapped the order around now.
That’s a sign that you aren’t booting via OpenCore.I loaded up my old Mojave drive and formatted that NVME again to get rid of Monterey Beta and now it's working again on 11.2.3.
If there are any further ideas I'll try them again tomorrow night - but it's a bit of a fuss having to put the old Mojave in and change to the old Radeon 5870 graphics card so I can see the old bootmenu (to boot into that).
When I did try and let it run (before formatting the NVME) it just gave me the round circle with the slash through it then switched off.
And yes, I have 0.7.2 config.
That’s a sign that you aren’t booting via OpenCore.
Anyway, do you want to try my pre-configured 0.7.3 V2 package?
This is a known good package. As long as you don’t mod anything, SurPlus should works.
Also, I recommend you completely re-install OC (including run the bless tool) to make sure OC can be activated properly.
Yes, I'd like to try that tomorrow. It's midnight now so I've got to get some sleep.That’s a sign that you aren’t booting via OpenCore.
Anyway, do you want to try my pre-configured 0.7.3 V2 package?
This is a known good package. As long as you don’t mod anything, SurPlus should works.
Also, I recommend you completely re-install OC (including run the bless tool) to make sure OC can be activated properly.
CorrectReinstall opencore would be mount the EFI partition, completely remove the files and folders from opencore, put the new one in and run the bless tool.
Where can I find it?
@Syncretic , I was working hard on tweaking OpenCore's config.plist today. But in the end I couldn't find the cause. So I decided to revert to the Latebloom version. For the Latebloom version, Cold/Warm boot is successfully booted within two times. However, SurPlus requires 5 to 10 forced reboots.Theconfig.plist
you attached looks correct - it passes plutil validation, and the SurPlus patch appears to be in the correct place. Maybe one of our resident OpenCore experts could have a look?
@m1ndless , I also did a PRAM reset and OpenCore started behaving strangely. As a result, I gave up on SurPlus. Perhaps I could have used SurPlus without any problems if I had not done the PRAM reset.Was able to install it successfully and removed latebloom – however today when I did a triple PRAM reset it seems to have gotten stuck booting into MacOS (similar to the boot hang that is caused by the race condition). Force restarting it made it boot up normally. Is there anyway PRAM reset would re introduce the race condition?
Wow, great work (again!).I've posted my findings about the MacOS 11.3+ "race condition" bug, along with a patch I'm calling SurPlus, in a github repository. All the details are there, and I'm not sure there's any benefit in reposting them all here. (Yes, I had to write my own debugger; the boot hangs generally happened before the boot was far enough along for MacOS' remote debugging facility to work, so drastic measures were required.)
This thread will serve for questions (hopefully with answers), comments, and discussion regarding SurPlus.
In a nutshell: our Classic Macs will live to fight another day. As of now, latebloom is deprecated. Install the three-byte SurPlus patch in your OpenCore config.plist and boot Big Sur or Monterey just as you would Catalina or Mojave.
PLEASE: If you're going to post in this thread because you're having trouble getting the patch to work, please include your OpenCore config.plist
file as an attachment. Without that, it's very difficult to offer assistance.
Will this patch work with opencore 0,6,8
Coldboot
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version REL-073-2021-09-06
Real model decoded from serial number: Mac Pro 2012 (MP5,1)
1 x Intel(R) Xeon(R) CPU W3680 @ 3.33GHz
DGxxxxxF4MG
Radeon RX 560
running at 11.6 20G165 Kernel 20.6.0
boot-args -lilubetaall -no_compat_check -v
Hardware:
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 3,33 GHz
Number of Processors: 1
Total Number of Cores: 6
L2 Cache (per Core): 256 KB
L3 Cache: 12 MB
Hyper-Threading Technology: Enabled
Memory: 32 GB
System Firmware Version: 9144.0.7.3.0
SMC Version (system): 1.39f11
SMC Version (processor tray): 1.39f11
System Software Overview:
System Version: macOS 11.6 (20G165)
Kernel Version: Darwin 20.6.0
Network:
Type: Ethernet
Hardware: Ethernet
Service Order: 0
Type: Ethernet
Hardware: Ethernet
Service Order: 1
Type: AirPort
Hardware: AirPort
Service Order: 2
Type: Ethernet
Hardware: Ethernet
Service Order: 3
Wi-Fi:
Card Type: AirPort Extreme (0x14E4, 0x14A)
Firmware Version: Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1680.8)
Storage:
File System: NTFS
BSD Name: disk1s2
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk2s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
File System: APFS
BSD Name: disk7s1
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: APFS
BSD Name: disk7s5
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk4s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk5s2
Medium Type: SSD
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk6s2
Medium Type: Rotational
Protocol: SATA
Internal: Yes
File System: Journaled HFS+
BSD Name: disk8s2
Protocol: USB
Internal: No
File System: APFS
BSD Name: disk2s5s1
Medium Type: SSD
Protocol: PCI-Express
Internal: Yes
Physical Interconnect: SATA
Physical Interconnect: SATA
BSD Name: disk3
File System: MS-DOS FAT32
BSD Name: disk3s1
Content: EFI
BSD Name: disk3s2
Content: Apple_APFS
Physical Interconnect: SATA
BSD Name: disk6
File System: MS-DOS FAT32
BSD Name: disk6s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk6s2
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk4
File System: MS-DOS FAT32
BSD Name: disk4s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk4s2
Content: Apple_HFS
Physical Interconnect: SATA
BSD Name: disk5
File System: MS-DOS FAT32
BSD Name: disk5s1
Content: EFI
File System: Journaled HFS+
BSD Name: disk5s2
Content: Apple_HFS
PCI:
Name: ATY,AMD,RadeonFramebuffer
Type: Display Controller
Bus: PCI
Slot: Slot-1
Type: Audio Device
Bus: PCI
Slot: Slot-1
Type: NVM Express Controller
Bus: PCI
Slot: Slot-2@8,0,0
Type: USB eXtensible Host Controller
Bus: PCI
Slot: Slot-3
Type: NVM Express Controller
Bus: PCI
Slot: Slot-2@10,0,0
NVMExpress:
Generic SSD Controller:
Samsung SSD 970 EVO Plus 2TB:
Capacity: 2 TB (2 000 398 934 016 bytes)
TRIM Support: Yes
Model: Samsung SSD 970 EVO Plus 2TB
Revision: 2B2QEXM7
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table)
Removable Media: No
S.M.A.R.T. status: Verified
Volumes:
EFI:
Capacity: 209,7 MB (209 715 200 bytes)
File System: MS-DOS FAT32
BSD Name: disk0s1
Content: EFI
disk0s2:
Capacity: 2 TB (2 000 189 177 856 bytes)
BSD Name: disk0s2
Content: Apple_APFS
Generic SSD Controller:
Samsung SSD 970 EVO Plus 1TB:
Capacity: 1 TB (1 000 204 886 016 bytes)
TRIM Support: Yes
Model: Samsung SSD 970 EVO Plus 1TB
Revision: 2B2QEXM7
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk1
Partition Map Type: GPT (GUID Partition Table)
Removable Media: No
S.M.A.R.T. status: Verified
Volumes:
EFI:
Capacity: 209,7 MB (209 715 200 bytes)
File System: MS-DOS FAT32
BSD Name: disk1s1
Content: EFI
Windows:
Capacity: 899,97 GB (899 973 906 432 bytes)
Free: 335,18 GB (335 184 228 352 bytes)
Writable: No
File System: NTFS
BSD Name: disk1s2
Mount Point: /Volumes/Windows
Content: Microsoft Basic Data
USB:
USB 3.1 Bus:
Host Controller Driver: AppleASMediaUSBXHCI
Product ID: 0x085e
Speed: Up to 480 Mb/s
Location ID: 0x00300000 / 2
Product ID: 0x55aa
Speed: Up to 5 Gb/s
Manufacturer: USB3.1
Location ID: 0x00200000 / 1
USB Interface: 0
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
Product ID: 0x1006
Speed: Up to 480 Mb/s
Location ID: 0xfd300000 / 1
Product ID: 0x5036
Speed: Up to 12 Mb/s
Location ID: 0xfd310000 / 2
Product ID: 0x0250
Speed: Up to 1.5 Mb/s
Location ID: 0xfd320000 / 3
USB 2.0 Bus:
Host Controller Driver: AppleUSBEHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Product ID: 0x0101
Speed: Up to 12 Mb/s
Location ID: 0x1a200000 / 1
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Bluetooth USB Host Controller:
Product ID: 0x8294
Location ID: 0x5a100000
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
USB Bus:
Host Controller Driver: AppleUSBUHCIPCI
Bluetooth:
Bluetooth Low Energy Supported: Yes
Handoff Supported: Yes
Instant Hot Spot Supported: Yes
Manufacturer: Broadcom
Composite Class Of Device: 0x380104
Connected: Yes
Manufacturer: Apple (0x3, 0x31C)
Class of Device: 0x05 0x20 0x2580
EDR Supported: No
eSCO Supported: No
SSP Supported: No
Connected: No
Class of Device: 0x00 0x00 0x0000
Memory:
Upgradeable Memory: Yes
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
Size: 8 GB
Type: DDR3
Speed: 1333 MHz
@m1ndless , I also did a PRAM reset and OpenCore started behaving strangely. As a result, I gave up on SurPlus. Perhaps I could have used SurPlus without any problems if I had not done the PRAM reset.
After I did the PRAM reset, nothing showed up on the display until the desktop view. Whether it's SurPlus or Latebloom.
Before the PRAM reset, I could see the Apple logo and the progress bar. What's your situation?
Im not sure what "VMM" is, can you explain? in case I need to update mineI was able to update from Monterey Beta 7 to Beta 8 using SurPlus. Worked flawlessly! I'm still buzzing about this patch. In order to get the update, I had to turn on VMM. Seems like that's going to be the way moving forward.
View attachment 1851234
This is not the thread to really discuss this. I suggest you read the OpenCore on the Mac Pro first post (Catalina requires this as well).Im not sure what "VMM" is, can you explain? in case I need to update mine
Thanks! I meant what does VMM stand for. Ill be sure to look that thread over tooThis is not the thread to really discuss this. I suggest you read the OpenCore on the Mac Pro first post (Catalina requires this as well).
Force shutdown, wait a few seconds, then start up again, see if the installation can continue after that.Hi, just updated my mac pro 5,1 from 11.2.3 to 11.6 with Martin Lo’s package and now im stuck in a reboot loop. Bootpicker comes up, then i see apple logo followed by progress bar and reboot. Has been going on for a couple of hours now. Probably just something i overlooked. Any help would be appreciated.