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

[TECK]

Are there still plans to run Sonoma with a 5,1?

macOS Sonoma and OpenCore Legacy Patcher Support · Issue #1076 · dortania/OpenCore-Legacy-Patcher

With the unveiling of macOS 14, Sonoma, Apple has continued their march towards removal of older Intel Macs. And with this, many more critical drivers used by our older systems have been changed or...

github.com

 

[MrScratchHook]

Are there still plans to run Sonoma with a 5,1?

macOS Sonoma and OpenCore Legacy Patcher Support · Issue #1076 · dortania/OpenCore-Legacy-Patcher

With the unveiling of macOS 14, Sonoma, Apple has continued their march towards removal of older Intel Macs. And with this, many more critical drivers used by our older systems have been changed or...

github.com

Fook Yeah. lol. unfortunately for me protools or any of my 3rd party plugins arent compatible yet, maybe by the summer of 2024

 

[PeterHolbrook]

Has OpenCore 0.9.6 been delayed?

 

[cdf]

Yes, it's scheduled for next month.

 

[kkinto]

I am unable to install the latest version of Adobe After Effects as it gives an incompatibility error: "Processor with Advanced Vector Extensions 2 (AXX2) support required".

Is something this going to be solved by OpenCore at some point or is this something one needs to switch to OCLP for (assuming that is able to meet requirements)?

 

[sveng]

i used OpenCore Legacy Patcher 1.0.1 to install Ventura on my MacPro 5,1 (RX 580). Everything worked so far, when booting i see the OCLP Bootloader and can select the Ventura drive etc..
Now i tried to install Windows 11, but i cannot get the USB Installer (made with the Guide) to show up in the OCLP Bootlader Screen. But i only see the Venture drive (and Recovery Paritions). I tried adjusting the config, but no luck. Any help on what i can try?
USB Works on other machines, just here on the MacPro 5,1 OpenCore it does not show up.

 

[spacedcadet]

I am unable to install the latest version of Adobe After Effects as it gives an incompatibility error: "Processor with Advanced Vector Extensions 2 (AXX2) support required".

Is something this going to be solved by OpenCore at some point or is this something one needs to switch to OCLP for (assuming that is able to meet requirements)?

Wild guess, you (we) need a new Mac. No amount of messing about with kexts is going to provide that functionality in a reliable way? Best case scenario OCLP somehow emulate AVX stuff in a patch? AE already runs pretty slowly on such old hardware, I can't imagine it's going to run well in that scenario. I say this as someone who is still running a 5,1 with Adobe apps as a work computer. Very soon she will be retired.

 

[ZNDK]

I installed Ventura using OpenCore Legacy Patcher 1.0.1. Then it seems to freeze if I leave my Mac on for more than an hour. I have the Mac set to not sleep and it still happens. The front LED on the Mac Pro stays on, it is not a slow blink, the Mac does not seem to go into sleep.

I have no choice but to force the Mac to shut down. Then the next boot always causes a kernel panic right after the BootPicker in OC. And at that time I always cannot use the built-in Bluetooth mouse. I am able to use the USB 1.1 keyboard at that time; restart the Mac and it will work.
When I learned of this problem, I re-enabled/disabled the "Resume" feature in macOS and this problem ended. However, recently the problem has reappeared even though I have not changed any settings.
I have done PRAM resets and SMC resets but no improvement. Is there any way to improve it?

 

[zzzachi]

Sorry, still on Big Sur here, thinking about updating the System.
but the #1 Post here only mentions Monterey ...
that probably means Venture and Sonoma are not supported by this method?

 

[MacNB2]

Sorry, still on Big Sur here, thinking about updating the System.
but the #1 Post here only mentions Monterey ...
that probably means Venture and Sonoma are not supported by this method?

Correct. Ventura and Sonoma require the old drivers and Frameworks to be added to those OS's. And it is no longer a simple matter of injecting those into the OS via OpenCore as those OS's have been secured in such a way that they cannot be simply hacked like Monterey or previous versions.
Instead the seal of the root volume has to be broken and then those drivers/frameworks inserted. That currently requires the use of OCLP tool which is out of the scope of this thread.
See this thread instead.

 

[cdf]

Ventura and Sonoma require the old drivers and Frameworks to be added to those OS's.

More specifically: With the classic Mac Pro’s lack of AVX, the entire OS.dmg cryptex must be replaced by the AVX-less Rosetta counterpart (which, interestingly, is free of AVX because of licensing restrictions). Unfortunately, this replacement doesn’t cover everything. In particular, the graphics stack remains AVX-dependent and therefore must be replaced by the Monterey version.

In fact, this is where things get very ugly: Many of the old drivers are extracted from the Monterey dyld cache and reassembled (with modifications as it turns out…) into functioning binaries (in a form never intended by Apple) for inclusion in OCLP. It may also be worth noting that this key process—while partly accomplished with an open-sourced tool (dsce)⁠—is effectively closed (not part of OCLP’s open source).

 

[ZNDK]

I installed Ventura using OpenCore Legacy Patcher 1.0.1. Then it seems to freeze if I leave my Mac on for more than an hour. I have the Mac set to not sleep and it still happens. The front LED on the Mac Pro stays on, it is not a slow blink, the Mac does not seem to go into sleep.

I may only be able to keep it for a short period of time, but I have found a solution. I am able to prevent this problem by setting "gpuswitch 0" with the pmset command. I did not have this set.
I wrote "for a short period of time" because previously I could prevent the problem by "disabling the Reopen", but after a few days that did not work and the problem returned.

 

[Bmju]

More specifically: With the classic Mac Pro’s lack of AVX, the entire OS.dmg cryptex must be replaced by the AVX-less Rosetta counterpart (which, interestingly, is free of AVX because of licensing restrictions). Unfortunately, this replacement doesn’t cover everything. In particular, the graphics stack remains AVX-dependent and therefore must be replaced by the Monterey version.

In fact, this is where things get very ugly: Many of the old drivers are extracted from the Monterey dyld cache and reassembled (with modifications as it turns out…) into functioning binaries (in a form never intended by Apple) for inclusion in OCLP. It may also be worth noting that this key process—while partly accomplished with an open-sourced tool (dsce)⁠—is effectively closed (not part of OCLP’s open source).

Hmm - despite the additional, accurate information given, as ever, it's possibly worth adding...

The notion of doing things that were never as Apple intended is not foreign to OC itself, of course!

Even OC includes multiple (optional) quirks, applying binary patches (in memory, in this case), where the exact what and why of the patch is not explicitly documented. It is not easy to document the logic behind binary patches; specifically, it's not like there would already exist a closed source documentation of what was done and why, for the OCLP patched binaries, which could 'just' be open sourced, for instance.

Taking a slightly different tack, it was (and is) very nice to do (as close as possible to) the minimal patching required to a Mac, to bring back support (for some Macs, and some macOS, the required patching is very minimal) - and it's true that OCLP was never about minimal patching (though perhaps this community swayed them in that direction a little) - but the basic issue here is that there is no minimal patching approach to getting Ventura+ on this era of Mac (or, at least, not without the holy grail AVX2 emulator - if it's even possible to do that early and cleanly enough), so (perhaps unfortunately, but so be it) the only game in town (for now??; for these machines; for Ventura+ - if that's what you want, with the admitted downsides) is OCLP, and the patched binaries which a very small number of people put a very large amount of work into producing, to make this even close to possible.

 

[PeterHolbrook]

the basic issue here is that there is no minimal patching approach to getting Ventura+ on this era of Mac (or, at least, not without the holy grail AVX2 emulator - if it's even possible to do that early and cleanly enough), so (perhaps unfortunately, but so be it) the only game in town (for now??; for these machines; for Ventura+ - if that's what you want, with the admitted downsides) is OCLP.

There used to be a BootROM project by Syncretic that looked promising in precisely getting us that "holy grail" of AVX/AVX2 emulation, but we haven't heard from him in over seven months. Are you familiar with his project? If so, how close is he or did he get to his goal? If he can't continue his efforts due to more pressing issues, do you suppose someone else could complete the project he initiated?

 

[Bmju]

There used to be a BootROM project by Syncretic that looked promising in precisely getting us that "holy grail" of AVX/AVX2 emulation, but we haven't heard from him in over seven months. Are you familiar with his project? If so, how close is he or did he get to his goal? If he can't continue his efforts due to more pressing issues, do you suppose someone else could complete the project he initiated?

I don't really know very much else. Though, never mind the issue of getting AVX2 emulation working at all performantly (i.e. even say barely usable) on a machine without native support, and also correctly ofc (i.e. saves emulated registers, somewhere, and saves and restores everything around the emulation code, somewhere) I believe that I have understood that a further issue would getting the emulation started early enough and in the correct place to really trap everything that might use it. I'm not convinced anyone else will pull it out of the hat if Syncretic doesn't. Though I don't suppose it is technically impossible, it would certainly be a huge amount of work. For what I fear might (this is not based on any specific experience, I have not used any draft emulation of Syncretic or anyone else) be unpleasantly slow operation of anything which uses it. :-(

EDIT: That said, if someone - say Syncretic - proves my doom-laden predictions wrong, it will of course be happy days indeed!

 

[cdf]

The notion of doing things that were never as Apple intended is not foreign to OC itself, of course!

Even OC includes multiple (optional) quirks, applying binary patches (in memory, in this case), where the exact what and why of the patch is not explicitly documented. It is not easy to document the logic behind binary patches; specifically, it's not like there would already exist a closed source documentation of what was done and why, for the OCLP patched binaries, which could 'just' be open sourced, for instance.

You’re absolutely right! But just to clarify: By saying “in a form never intended by Apple” I was referring to the extracted kexts vs the original drivers in the cache.

Such an extraction is really non-trivial, and the end result depends on the particular cache build and any modifications applied, making comparisons with original drivers, in order to identify the patches, effectively intractable. With patches in memory, even if not documented (to the extent of Syncretic’s SurPlus patch, for instance), the differences (Find-Replace) are clear from the config or source, in which case a more informed decision can be made about using the patches.

 

[Gustav Holdoff]

Maybe it will be interesting for dev's and simple rumors
Today in the McPro upgrade community on FB MacPro users launched a challenge to measure memory speed
I also downloaded AmorphousMemoryMark this morning
I started the test, at first the result was 24.00
but the performance dropped sharply - in such cases I know that some process has turned on and is taking up resources
to understand the situation: every time I turn on the computer and before turning it off, I check the operation of all processes using Activity Monitor (there were no unusual processes before)
after the test I got a process: kernel task 57%
As always, I had to reset SMC and NVRAM several times,
MDS, MdWorker, Syspolisyd, and Secd appeared to work incorrectly
from 9-30 am to 15-30 I rebooted the computer, disconnected the disks, disconnected the processor tray
rewrote EFI, took out all the disks, booted into Mojave without opercore, reset SMC and nvram in Mojave
booted into recovery and back
I replaced my Efi with Martin's Efi - no result
then I in my config deactivated syncretic's patch and activated NoAVXFSCompressionTypeZlib.kext
I reset again the SMC and NVRAM again
By 15-00 my processes had returned to normal, but as soon as they returned to normal, the activity monitor froze the system.
froze so that the computer rebooted itself and apparently the nvme controller was damaged somewhere in the memory - because when rebooting it left me with the option to boot from sata ssd to windows, and macos on nvme is not available
again reset nvram and sms
I lost my whole working day

It is obvious that a finely tuned system on older processors without AVX will not work correctly if all sorts of unknown programs are allowed to interfere with memory addresses
after all, the program is written for the correct hardware
and we camouflage our hardware
memory addresses are not assigned natively due to the lack of avx, then the system cannot find memory addresses
I am attaching illustrations - although I have already posted them many times before
I am attaching a test that is not mine - from FB - mine was 24, but in the end it became 20 - and I didn’t take pictures of it, I started troubleshooting the problems

EDITED
I think it will be interesting for dev's to know
I installed oclp on my second computer (it has almost the same configuration - in the discription) in order to have Wi-Fi (on the second computer I have an atheros card)
negative experience - although bluetooth appears to be working, not any device is connected
although wifi works
But the most disgusting thing is that in the oclp something is seriously unfinished for the cMP - because of the patched MacOS and other kexts, the archicad periodically freezes and reboots macOS, the wheel appears often
while on my main computer with native Monterey and standard OC this has never happened
*the wheel appeared a long time ago, when the monterand problem first appeared it was not solved
That's why I'll remove patched Monterey and oclp

 

[solaris8x86]

Correct. Ventura and Sonoma require the old drivers and Frameworks to be added to those OS's. And it is no longer a simple matter of injecting those into the OS via OpenCore as those OS's have been secured in such a way that they cannot be simply hacked like Monterey or previous versions.
Instead the seal of the root volume has to be broken and then those drivers/frameworks inserted. That currently requires the use of OCLP tool which is out of the scope of this thread.
See this thread instead.

Yeah, I'd been a Opencore fan with Mac Pro 5,1 for years. Until ventura, the game ended. There's no way to enable hardware acceleration for the GPU since Ventura. As a result, I went to get a Mac Studio M1 Max at home and a Macbook Pro 2019 i9 at work instead. It is a grant leap for me to move forward since owning a Mac Pro 5,1. It's inevitable that we must forget the Mac Pro 5,1 and opencore things.

 

[sassmouth]

Howdy. I've got OpenCore 0.9.5 running on a Mac Pro 4,1 flashed to 5,1, using an AMD RX580 4GB, with Monterey 12.7. Everything's great and stable, but when I switched from HDMI to DisplayPort I discovered that I'm locked to 30Hz if I go above 1920x1080. I know the cable and monitor are fine and capable of 4k60 using my Windows computer, and HDMI also has no problem with 4k60. I tried using BetterDisplay to force it but could not find a way to do so. Tried changing monitor for DP 1.2 to 1.1, and HBR2 to HBR, but both of those changes reduce the monitor itself to 4k30.

I went back through the guide after updating from OC 0.9.4, but none of the changes made a difference. Any ideas?

 

[joevt]

Howdy. I've got OpenCore 0.9.5 running on a Mac Pro 4,1 flashed to 5,1, using an AMD RX580 4GB, with Monterey 12.7. Everything's great and stable, but when I switched from HDMI to DisplayPort I discovered that I'm locked to 30Hz if I go above 1920x1080. I know the cable and monitor are fine and capable of 4k60 using my Windows computer, and HDMI also has no problem with 4k60. I tried using BetterDisplay to force it but could not find a way to do so. Tried changing monitor for DP 1.2 to 1.1, and HBR2 to HBR, but both of those changes reduce the monitor itself to 4k30.

I went back through the guide after updating from OC 0.9.4, but none of the changes made a difference. Any ideas?

What display are you using? Use AllRez to see what macOS knows about the GPU, the display, and the connection between the two. Use it for both HDMI and DisplayPort connections. If the display uses the same product ID for both HDMI and DisplayPort, then a display override file (created by SwitchResX or whatever) made for one of the ports will get used for the other port as well.

 

[sassmouth]

What display are you using? Use AllRez to see what macOS knows about the GPU, the display, and the connection between the two. Use it for both HDMI and DisplayPort connections. If the display uses the same product ID for both HDMI and DisplayPort, then a display override file (created by SwitchResX or whatever) made for one of the ports will get used for the other port as well.

Well, color me confused... I used AllRez on the HDMI connection, then pulled the HDMI out and plugged in the DP cable, and when I got signal again I suddenly had the Refresh Rate dropdown complete with 60Hz option. Previously the dropdown was completely missing from System Prefs/Displays when on DP.

It's an NEC MultiSync EA275UHD monitor, and according to AllRez it uses 0x2baf for the Port 3 DP connection and 0x2bba for the Port 4 HDMI connection (I did also previously try the DP Port 1 and 2 to be sure). The only other change would be that I uninstalled BetterDisplay while HDMI was still plugged in. But, it's still working after a complete shut down and power on, so problem solved I guess?

 

[basslik]

Fook Yeah. lol. unfortunately for me protools or any of my 3rd party plugins arent compatible yet, maybe by the summer of 2024

MrScratchHook:, I got some down time and I'm ready to move from Mojave to perhaps Big Sur or Ventura. it appears I have the same 5,1 as you do. May I ask what OS you running with Pro Tools?

I'm currently running 2023.6, can't upgrade to the newest PT version on Mojave. THANKS

 

[kkinto]

I am getting stuck (twice now) during boot while attempting to update to 12.7.1 Its hanging about 2/3 along with white apple logo (no text). I have force restarted now and used my backup drive.

Is there any way to remove the "updating" status (and everything else created during this operation) from my main drive so that it will boot as it was? Thnks

-- EDIT Ran first aid on the APFS partition and then on all the volumes and it then finished the update, all seems good again!
-- EDIT 2 Nope, running but not all good. Twice Mac has just frozen, screen lost video and restarted itself silently with KP warning on reboot Probably off-topic but here are the two KP reports anyway if anyone has any ideas? They seem almost identical except for the CPU number. TIA

Spoiler: Panic report 1

Panic(cpu 2 caller 0xffffff8012bcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff90adc43670: 295 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff95793adaa0, Frame : Return Address
0xffffffc12f93b770 : 0xffffff800f879a3d
0xffffffc12f93b7c0 : 0xffffff800f9dca16
0xffffffc12f93b800 : 0xffffff800f9cbd83
0xffffffc12f93b850 : 0xffffff800f819a90
0xffffffc12f93b870 : 0xffffff800f879e0d
0xffffffc12f93b990 : 0xffffff800f8795c6
0xffffffc12f93b9f0 : 0xffffff8010114a83
0xffffffc12f93bae0 : 0xffffff8012bcaf19
0xffffffc12f93bb50 : 0xffffff8012bca39e
0xffffffc12f93bd00 : 0xffffff8012b9c1f8
0xffffffc12f93bfa0 : 0xffffff800f81919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff8012b0d000->0xffffff8012c8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff8010db2000->0xffffff8010dbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff8010dc8000->0xffffff8010dcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff80112d4000->0xffffff80112dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801257c000->0xffffff8012592fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff8012cc5000->0xffffff8012d45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff8010e4f000->0xffffff8010e67fff

Process name corresponding to current thread (0xffffff95793adaa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000000f600000
KernelCache base: 0xffffff800f800000
Kernel slide: 0x000000000f610000
Kernel text base: 0xffffff800f810000
__HIB text base: 0xffffff800f700000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3525863372067
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000334edd57f07
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000028aa7e1cee 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80a9d4b000 - 0xffffffa0a9d4b000
. PGZ : 0xffffff80a9d4b000 - 0xffffff80b1d4c000
. VM : 0xffffff80b1d4c000 - 0xffffff857d6e5000
. RO : 0xffffff857d6e5000 - 0xffffff8716a18000
. GEN0 : 0xffffff8716a18000 - 0xffffff8be23b1000
. GEN1 : 0xffffff8be23b1000 - 0xffffff90add4a000
. GEN2 : 0xffffff90add4a000 - 0xffffff95796e3000
. GEN3 : 0xffffff95796e3000 - 0xffffff9a4507d000
. DATA : 0xffffff9a4507d000 - 0xffffffa0a9d4b000
Metadata: 0xffffff8071d3b000 - 0xffffff8091d3b000
Bitmaps : 0xffffff8091d3b000 - 0xffffff80a9d3b000

Spoiler: Panic Report 2

panic(cpu 17 caller 0xffffff801ddcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff954c810670: 290 threads: pid 0: kernel_task
Backtrace (CPU 17), panicked thread: 0xffffff8bb4db5aa0, Frame : Return Address
0xffffffcb8ee03770 : 0xffffff801aa79a3d
0xffffffcb8ee037c0 : 0xffffff801abdca16
0xffffffcb8ee03800 : 0xffffff801abcbd83
0xffffffcb8ee03850 : 0xffffff801aa19a90
0xffffffcb8ee03870 : 0xffffff801aa79e0d
0xffffffcb8ee03990 : 0xffffff801aa795c6
0xffffffcb8ee039f0 : 0xffffff801b314a83
0xffffffcb8ee03ae0 : 0xffffff801ddcaf19
0xffffffcb8ee03b50 : 0xffffff801ddca39e
0xffffffcb8ee03d00 : 0xffffff801dd9c1f8
0xffffffcb8ee03fa0 : 0xffffff801aa1919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff801dd0d000->0xffffff801de8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff801bfb2000->0xffffff801bfbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff801bfc8000->0xffffff801bfcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff801c4d4000->0xffffff801c4dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801d77c000->0xffffff801d792fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff801dec5000->0xffffff801df45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff801c04f000->0xffffff801c067fff

Process name corresponding to current thread (0xffffff8bb4db5aa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000001a800000
KernelCache base: 0xffffff801aa00000
Kernel slide: 0x000000001a810000
Kernel text base: 0xffffff801aa10000
__HIB text base: 0xffffff801a900000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3679939410763
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000358cd7b4021
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001fc00947ae 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff807cf70000 - 0xffffffa07cf70000
. PGZ : 0xffffff807cf70000 - 0xffffff8084f71000
. VM : 0xffffff8084f71000 - 0xffffff855090a000
. RO : 0xffffff855090a000 - 0xffffff86e9c3d000
. GEN0 : 0xffffff86e9c3d000 - 0xffffff8bb55d6000
. GEN1 : 0xffffff8bb55d6000 - 0xffffff9080f6f000
. GEN2 : 0xffffff9080f6f000 - 0xffffff954c908000
. GEN3 : 0xffffff954c908000 - 0xffffff9a182a2000
. DATA : 0xffffff9a182a2000 - 0xffffffa07cf70000
Metadata: 0xfffffff553149000 - 0xfffffff573149000
Bitmaps : 0xfffffff573149000 - 0xfffffff58b149000

 

[h9826790]

Depends on The update usually can be stopped if you select the macOS boot drive in the OC boot picker.

I am getting stuck (twice now) during boot while attempting to update to 12.7.1 Its hanging about 2/3 along with white apple logo (no text). I have force restarted now and used my backup drive.

Is there any way to remove the "updating" status (and everything else created during this operation) from my main drive so that it will boot as it was? Thnks

-- EDIT Ran first aid on the APFS partition and then on all the volumes and it then finished the update, all seems good again!
-- EDIT 2 Nope, running but not all good. Twice Mac has just frozen, screen lost video and restarted itself silently with KP warning on reboot Probably off-topic but here are the two KP reports anyway if anyone has any ideas? They seem almost identical except for the CPU number. TIA

Spoiler: Panic report 1

Panic(cpu 2 caller 0xffffff8012bcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff90adc43670: 295 threads: pid 0: kernel_task
Backtrace (CPU 2), panicked thread: 0xffffff95793adaa0, Frame : Return Address
0xffffffc12f93b770 : 0xffffff800f879a3d
0xffffffc12f93b7c0 : 0xffffff800f9dca16
0xffffffc12f93b800 : 0xffffff800f9cbd83
0xffffffc12f93b850 : 0xffffff800f819a90
0xffffffc12f93b870 : 0xffffff800f879e0d
0xffffffc12f93b990 : 0xffffff800f8795c6
0xffffffc12f93b9f0 : 0xffffff8010114a83
0xffffffc12f93bae0 : 0xffffff8012bcaf19
0xffffffc12f93bb50 : 0xffffff8012bca39e
0xffffffc12f93bd00 : 0xffffff8012b9c1f8
0xffffffc12f93bfa0 : 0xffffff800f81919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff8012b0d000->0xffffff8012c8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff8010db2000->0xffffff8010dbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff8010dc8000->0xffffff8010dcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff80112d4000->0xffffff80112dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801257c000->0xffffff8012592fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff8012cc5000->0xffffff8012d45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff8010e4f000->0xffffff8010e67fff

Process name corresponding to current thread (0xffffff95793adaa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000000f600000
KernelCache base: 0xffffff800f800000
Kernel slide: 0x000000000f610000
Kernel text base: 0xffffff800f810000
__HIB text base: 0xffffff800f700000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3525863372067
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000334edd57f07
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000028aa7e1cee 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff80a9d4b000 - 0xffffffa0a9d4b000
. PGZ : 0xffffff80a9d4b000 - 0xffffff80b1d4c000
. VM : 0xffffff80b1d4c000 - 0xffffff857d6e5000
. RO : 0xffffff857d6e5000 - 0xffffff8716a18000
. GEN0 : 0xffffff8716a18000 - 0xffffff8be23b1000
. GEN1 : 0xffffff8be23b1000 - 0xffffff90add4a000
. GEN2 : 0xffffff90add4a000 - 0xffffff95796e3000
. GEN3 : 0xffffff95796e3000 - 0xffffff9a4507d000
. DATA : 0xffffff9a4507d000 - 0xffffffa0a9d4b000
Metadata: 0xffffff8071d3b000 - 0xffffff8091d3b000
Bitmaps : 0xffffff8091d3b000 - 0xffffff80a9d3b000

Spoiler: Panic Report 2

panic(cpu 17 caller 0xffffff801ddcaf19): "kind == NEW && refcnt = -1\n" @jobj.c:4068
Panicked task 0xffffff954c810670: 290 threads: pid 0: kernel_task
Backtrace (CPU 17), panicked thread: 0xffffff8bb4db5aa0, Frame : Return Address
0xffffffcb8ee03770 : 0xffffff801aa79a3d
0xffffffcb8ee037c0 : 0xffffff801abdca16
0xffffffcb8ee03800 : 0xffffff801abcbd83
0xffffffcb8ee03850 : 0xffffff801aa19a90
0xffffffcb8ee03870 : 0xffffff801aa79e0d
0xffffffcb8ee03990 : 0xffffff801aa795c6
0xffffffcb8ee039f0 : 0xffffff801b314a83
0xffffffcb8ee03ae0 : 0xffffff801ddcaf19
0xffffffcb8ee03b50 : 0xffffff801ddca39e
0xffffffcb8ee03d00 : 0xffffff801dd9c1f8
0xffffffcb8ee03fa0 : 0xffffff801aa1919e
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[721020CF-BF5F-3DEF-9F3A-AFE4205CD53E]@0xffffff801dd0d000->0xffffff801de8bfff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[6E6AB947-75F7-344F-97FE-F1A9A803D2F2]@0xffffff801bfb2000->0xffffff801bfbbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[DCCE5AA9-462A-34BB-A905-A4CEB8DF45E2]@0xffffff801bfc8000->0xffffff801bfcdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[0BBEF1B6-3879-3835-9993-30FB5B22F3A7]@0xffffff801c4d4000->0xffffff801c4dbfff
dependency: com.apple.iokit.IOStorageFamily(2.1)[63189A2A-E19C-3F1E-96EF-95B7DB154785]@0xffffff801d77c000->0xffffff801d792fff
dependency: com.apple.kec.corecrypto(12.0)[5C997179-2E95-341F-A88B-07977BCCB606]@0xffffff801dec5000->0xffffff801df45fff
dependency: com.apple.security.AppleImage4(4.2.0)[8E7BE283-81FC-3565-A114-F692370A8969]@0xffffff801c04f000->0xffffff801c067fff

Process name corresponding to current thread (0xffffff8bb4db5aa0): kernel_task
Boot args: -no_compat_check agdpmod=pikera chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G920

Kernel version:
Darwin Kernel Version 21.6.0: Wed Oct 4 23:55:28 PDT 2023; root:xnu-8020.240.18.704.15~1/RELEASE_X86_64
Kernel UUID: CA525A92-20FF-38D2-AB16-E64095531D5A
KernelCache slide: 0x000000001a800000
KernelCache base: 0xffffff801aa00000
Kernel slide: 0x000000001a810000
Kernel text base: 0xffffff801aa10000
__HIB text base: 0xffffff801a900000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3679939410763
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000358cd7b4021
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001fc00947ae 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff807cf70000 - 0xffffffa07cf70000
. PGZ : 0xffffff807cf70000 - 0xffffff8084f71000
. VM : 0xffffff8084f71000 - 0xffffff855090a000
. RO : 0xffffff855090a000 - 0xffffff86e9c3d000
. GEN0 : 0xffffff86e9c3d000 - 0xffffff8bb55d6000
. GEN1 : 0xffffff8bb55d6000 - 0xffffff9080f6f000
. GEN2 : 0xffffff9080f6f000 - 0xffffff954c908000
. GEN3 : 0xffffff954c908000 - 0xffffff9a182a2000
. DATA : 0xffffff9a182a2000 - 0xffffffa07cf70000
Metadata: 0xfffffff553149000 - 0xfffffff573149000
Bitmaps : 0xfffffff573149000 - 0xfffffff58b149000

If you can still boot.

As long as your OC settings allow you to install Monterey (if in doubt, I personally recommend you turn on VMM, and turn off SMBIOS spoofing. So far, this method is very reliable in my own test), you better boot to the Monterey recovery partition, then re-install Monterey from there.

No need to format anything, just install once more on top of the existing Monterey. It will fix all damaged system files. And usually can fix most strange issue.

 

[Gustav Holdoff]

With method #2, everything was as usual for me, maybe only the first boot after installation took an unusually long time, but I saw that something was being written to NVME system disk, I just waited. After loading the activity monitor showed all processes were normal