macOS 12 Monterey on Unsupported Macs Thread

[mwidjaya]

If I installed Catalina on a separated volume of my SSD as second OS (OCLP'd Monterey is on another volume of the same SSD) won't it affect in any way my existing Monterey installation and OpenCore status?

A good question and some trickiness involved mainly due to APFS differences in macOS 12 vs 10.15.

My thoughts, not 100% sure, could be wrong.

Single internal SSD, OCLP EFI installed on that SSD.

If you are thinking of two volumes sharing total space of SSD, I suspect it will not work. Catalina can't "see" newer Monterey created APFS volumes (newer APFS format).

I suspect you would have to:
- boot into Monterey recovery or USB installer
- use disk utility, shrink Monterey volume/container to free up some space, let's say 50GB
- reset NVRAM (like disabling OCLP EFI)
- boot into Catalina installer
- use disk utility, create new partition for Catalina (older APFS format that Catalina uses)
- install Catalina onto that new partition

In short, you need a separate disk partition instead of second volume (sharing total space).

To get back booting OCLP Monterey, just option boot, select OCLP EFI boot, CTRL select Monterey disk.

 

[K two]

Well, now it's my turn to ask a question If I installed Catalina on a separated volume of my SSD as second OS (OCLP'd Monterey is on another volume of the same SSD) won't it affect in any way my existing Monterey installation and OpenCore status?

Common practice

These are separate partitions.

 

[Tockman]

Common practice

So no harm or strings attached? All volumes are seen and no need to create partitions?

 

[K two]

So no harm or strings attached? All volumes are seen and no need to create partitions?

 

[K two]

.

 

[TigerA]

Well, now it's my turn to ask a question If I installed Catalina on a separated volume of my SSD as second OS (OCLP'd Monterey is on another volume of the same SSD) won't it affect in any way my existing Monterey installation and OpenCore status?

I've just added Catalina on a separate partition (APFS container) on my iMac13,2 FusionDrive containing Monterey as well on a separate partition. The System Firmware is now updated from 421 to 425. So far Monterey is running normal.

 

[TimmuJapan]

So no harm or strings attached? All volumes are seen and no need to create partitions?

K two’s installations are all on separate partitions, not separate volumes. I don’t know if you can use opencore with separate volumes, one volume being a native supported installation, another volume using the opencore magic, and all sharing the same partition.

K two’s disk has separate partitions for all of those macOSes—not separate volumes. It is a very important distinction.

K two— no offense meant, but if I look back at your comments to Tockman, it looks like you just rubberstamped installing multiple macOSes (maybe some supported , maybe some unsupported) divided by separate volumes on a single partition. Per my knowledge, that is not what works for you….Your installs each have their own partition. You clarified that in your first post to tockman, and then in your second post where he specifically asked “no need to create partitions?” You responded “works on my machine.” Oops!

It’s okay to say just “oops” btw…. 😉

 

[Tockman]

K two’s installations are all on separate partitions, not separate volumes. I don’t know if you can use opencore with separate volumes, one volume being a native supported installation, another volume using the opencore magic.

K two’s disk has separate partitions for all of those macOSes—not separate volumes. It is a very important distinction.

Just in time! ?

 

[TigerA]

Just in time! 👍

It has to be on a separate partition, not volume!

 

[borp99]

I'm documenting a few difficulties and workarounds over trying to install 12.3b1 and b2 on my MacPro5,1 during the past week, in case they help anyone else now or in the future:

1. Trying several OTA updates for B1 resulted in consistent first reboots and stalls at the message "A required firmware update could not be installed". Thankfully the B2 full installer then came along to save me from further unwelcome and unnecessary (...and surprising in that OCLP is supposed to suppress these on old hardware) firmware update issues.

2. Trying the full B2 installer with OCLP 0.4.2 (spoofing MacPro7,1) resulted in a consistent boot loop back to the Installer/Select HD [aka Recovery] process. While the progress bar did move glacially a little further on each 'reboot and select HD' redo, the auto formatting to APFS from HFS+ and the complete expansion of the Installer files never happened for me.

3. I changed the spoofing to iMacPro1,1 (changing the various MacPro7,1 name and BoardID instances in the config.plist to the iMacPro1,1 ones). After this, the B2 full installer properly formatted the test partition and successfully installed to the User creation screens and desktop.

4. The very first manual reboot after installing and running 12.3b2 (using OCLP 0.4.2 with MacPro7,1 OR iMacPro1,1 spoofing) crashed every time back to the OCLP drive selection [EFI] screen. The only way I could get B2 to manually (re)boot and fully load was to update to the latest 0.4.2 0.4.3 Nightly build.

 

[TigerA]

.

 

[makra]

K two’s installations are all on separate partitions, not separate volumes. I don’t know if you can use opencore with separate volumes, one volume being a native supported installation, another volume using the opencore magic, and all sharing the same partition.

K two’s disk has separate partitions for all of those macOSes—not separate volumes. It is a very important distinction.

K two— no offense meant, but if I look back at your comments to Tockman, it looks like you just rubberstamped installing multiple macOSes (maybe some supported , maybe some unsupported) divided by separate volumes on a single partition. Per my knowledge, that is not what works for you….Your installs each have their own partition.

It’s okay to say “oops” btw…. ?

I had Catalina (DosDude1) on my MBP8,1 and added Volumes with Big Sur and Monterey with OCLP. That didn't cause any problems.

 

[TimmuJapan]

I had Catalina (DosDude1) on my MBP8,1 and added Volumes with Big Sur and Monterey with OCLP. That didn't cause any problems.

Cool.

A MacBook Pro 8,1 will run high sierra natively. Were you able to / do you know if you could also have macOS high sierra on a separate volume that shares a single partition with dosdude1 Catalina, big sur, Monterey (each OS on a separate volume)? Is that possible? Can the unsupported macOSes that boot via dosdude1 or opencore that are divided up by volumes also sit next to a natively supported OS on a separate volume, and all of these OSes exist on the same partition, are divided up by volumes, and boot beautiful under the umbrella of open core?

In Tockman’s case, the Catalina will run natively on his machine, but the big sur and Monterey need open core. Can he have all of these OSes, supported and unsupported, divided up by volumes, instead of partitions, everything booting beautifully under opencore? I think most people go the partitions route because it seems more stable and safer, but if you can do it all with volumes, that is cool too… I just don’t know if it is possible…..

 

[TigerA]

Just like to clarify the partition vs volume discussion: If a seperate partition is to be created, the Disk Utility will also create a new volume. But this volume will reside under the newly created seperate container (partition), thus to seperate 2 different macOS. However the OCLP EFI can be accessed by both macOS during boot up. My iMac13,2 supports native Catalina though.

 

[makra]

Cool.

A MacBook Pro 8,1 will run high sierra natively. Were you able to / do you know if you could also have macOS high sierra on a separate volume that shares a single partition with dosdude1 Catalina, big sur, Monterey (each OS on a separate volume)? Is that possible? Can the unsupported macOSes that boot via dosdude1 or opencore that are divided up by volumes also sit next to a natively supported OS on a separate volume, and all of these OSes exist on the same partition, are divided up by volumes, and boot beautiful under the umbrella of open core?

In Tockman’s case, the Catalina will run natively on his machine, but the big sur and Monterey need open core. Can he have all of these OSes, supported and unsupported, divided up by volumes, instead of partitions?

I haven't tried that - and don't know enough about how the boot picker works. But why would a supported OS make a difference if I skip OCLP - as I did in case of Catalina/DD1 for several months?

 

[TimmuJapan]

I haven't tried that - and don't know enough about how the boot picker works. But why would a supported OS make a difference if I skip OCLP - as I did in case of Catalina/DD1 for several months?

It might…. I have no idea… opencore was designed to boot unsupported OSes, so the OSes that need opencore to boot might need to live on their own partition , separate from the OS that boots natively. I have no idea.

In my experience, I’ve always found it useful to have the last supported OS on a machine as the start line. Things like disk utility, recovery partition, etc. sometimes play nicer on supported OSes… Monterey is still a WIP at this point with opencore, albeit a wonderful WIP.

 

[makra]

It might…. I have no idea… opencore was designed to boot unsupported OSes, so the OSes that need opencore to boot might need to live on their own partition , separate from the OS that boots natively. I have no idea.

In my experience, I’ve always found it useful to have the last supported OS on a machine as the start line. Things like disk utility, recovery partition, etc. sometimes play nicer on supported OSes… Monterey is still a WIP at this point with opencore, albeit a wonderful WIP.

Start line: Does it make a difference, which OS was installed first? I can confirm that I had added HS as volume at some stage in order to trigger a firmware update. I learned from Ausdauersportler that a partition was needed for that. So I deleted it again. But again: I didn't let OCLP's EFI Boot start at all.

 

[mwidjaya]

I had Catalina (DosDude1) on my MBP8,1 and added Volumes with Big Sur and Monterey with OCLP. That didn't cause any problems.

Maybe it is possible. Maybe if these APFS volumes were created while in Catalina?

Boot into Catalina (DD1) and show us disk utility screen cap of these volumes all under 1 container.

 

[borp99]

0.4.3 Nightly build ?

Oops, yes 0.4.3 nightly (usually find it by looking under Issues Actions, then look under the most recent dates, on GitHub OCLP site).

 

[makra]

Maybe it is possible. Maybe if these APFS volumes were created while in Catalina?

Boot into Catalina (DD1) and show us disk utility screen cap of these volumes all under 1 container.

Two weeks late... Catalina's gone.

 

[TigerA]

Two weeks late... Catalina's gone.

Never too late: you can reinstall ….???????

 

[the.burn]

Hi,
finally, I managed to get Monterey installed... My "12 minutes remaining" issue was caused by a faulty HDD. Now Im using a new HDD and it works...

But, can anyone tell, what is wrong here? Monterey often crashes completely:

panic(cpu 3 caller 0xffffff7f8bf4c075): GPU Panic: mux-regs 3 3 7f 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:3 power-state 0 3D idle HDA idle system-state 1 power-level 20:20 power-retry 0 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffffd04ad15000 0x0a5480a2, D0, P2/4

Panicked task 0xffffff901c3d4a20: 10 threads: pid 161: WindowServer
Backtrace (CPU 3), panicked thread: 0xffffff901ce01540, Frame : Return Address
0xffffffd039c62ea0 : 0xffffff800ae85ffd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd039c62ef0 : 0xffffff800afe6035 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd039c62f30 : 0xffffff800afd5803 mach_kernel : _kernel_trap + 0x533
0xffffffd039c62f80 : 0xffffff800ae25a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd039c62fa0 : 0xffffff800ae863cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd039c630c0 : 0xffffff800ae85b86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd039c63120 : 0xffffff800b716409 mach_kernel : _panic + 0x54
0xffffffd039c63190 : 0xffffff7f8bf4c075 com.apple.driver.AppleMuxControl : _Debugger + 0x73b075
0xffffffd039c631f0 : 0xffffff7f8cb88441 com.apple.nvidia.classic.NVDAResmanTesla : _osWriteRegistryDword + 0x321
0xffffffd039c632b0 : 0xffffff7f8cc541ca com.apple.nvidia.classic.NVDAResmanTesla : _gpuExecRegOps + 0xeefd
0xffffffd039c632f0 : 0xffffff7f8cc54235 com.apple.nvidia.classic.NVDAResmanTesla : _gpuExecRegOps + 0xef68
0xffffffd039c63370 : 0xffffff7f8c9b37f0 com.apple.nvidia.classic.NVDANV50HalTesla : __ZN11NVDANV50HAL5probeEP9IOServicePi + 0x123d22
0xffffffd039c63490 : 0xffffff7f8cc75d35 com.apple.nvidia.classic.NVDAResmanTesla : _constructObjEHeap + 0x51d3
0xffffffd039c634b0 : 0xffffff7f8cb8f048 com.apple.nvidia.classic.NVDAResmanTesla : _NvRmDupObject + 0x3b5
0xffffffd039c63560 : 0xffffff7f8cb8ca84 com.apple.nvidia.classic.NVDAResmanTesla : _insert_registration_func + 0x240
0xffffffd039c63750 : 0xffffff7f8cb8db25 com.apple.nvidia.classic.NVDAResmanTesla : _NvRmAlloc + 0x84
0xffffffd039c63830 : 0xffffff7f8c46d3af com.apple.GeForceTesla : __ZN17nvEvoChannelTesla5FlushEP17nvPushBufferTesla + 0x57
0xffffffd039c63870 : 0xffffff7f8c47c824 com.apple.GeForceTesla : __ZN17nvPushBufferTesla9MakeSpaceEj + 0x74
0xffffffd039c638b0 : 0xffffff7f8c4a3439 com.apple.GeForceTesla : __ZN26nvTeslaDisplayManagerTesla35TriggerReleaseOfRenderableSemaphoreEjRj + 0x85
0xffffffd039c638f0 : 0xffffff7f8c4a34f4 com.apple.GeForceTesla : __ZN26nvTeslaDisplayManagerTesla19EmitChannelBeamSyncEP13__GLNVdataRecjjjjPj + 0x48
0xffffffd039c63920 : 0xffffff7f8c4822e1 com.apple.GeForceTesla : __ZN14nvSurfaceTesla12generateSyncEjjj + 0x15b
0xffffffd039c63970 : 0xffffff7f8c44fcaf com.apple.GeForceTesla : __ZN16IONVSurfaceTesla11submit_swapEj7eDoSwapjP18IONVGLContextTesla + 0x309
0xffffffd039c63a00 : 0xffffff7f8c44be83 com.apple.GeForceTesla : __ZN16IONVSurfaceTesla13flush_surfaceEjj + 0x7f
0xffffffd039c63a30 : 0xffffff7f8c449bd0 com.apple.GeForceTesla : __ZN16IONVSurfaceTesla13surface_flushEjj + 0x104
0xffffffd039c63a70 : 0xffffff800b68bce6 mach_kernel : _shim_io_connect_method_scalarI_scalarO + 0x306
0xffffffd039c63b10 : 0xffffff800b68a3d8 mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x278
0xffffffd039c63b60 : 0xffffff800b69460c mach_kernel : _is_io_connect_method + 0x3cc
0xffffffd039c63cc0 : 0xffffff800af8d0b4 mach_kernel : _iokit_server_routine + 0x4e94
0xffffffd039c63dd0 : 0xffffff800ae61048 mach_kernel : _ipc_kmsg_send + 0x468
0xffffffd039c63e60 : 0xffffff800ae77a8d mach_kernel : _mach_msg_overwrite_trap + 0x2bd
0xffffffd039c63ef0 : 0xffffff800afb8f7e mach_kernel : _mach_call_munger64 + 0x22e
0xffffffd039c63fa0 : 0xffffff800ae26246 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8cb37000->0xffffff7f8cd4ffff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8c6f9000->0xffffff7f8c727fff
dependency: com.apple.iokit.IONDRVSupport(593)[23ADBC95-22F8-3980-9A18-2708B931E7E7]@0xffffff7f8c741000->0xffffff7f8c749fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800d9d6000->0xffffff800da00fff
com.apple.nvidia.classic.NVDANV50HalTesla(10.0.4)[5DCF031B-F81F-32A3-ADCD-18E16EAC7CF0]@0xffffff7f8c88f000->0xffffff7f8ca5dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800d9d6000->0xffffff800da00fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8cb37000->0xffffff7f8cd4ffff
com.apple.driver.AppleMuxControl(6.4.12)[6815B044-FD1A-3500-9710-4B19325C45F4]@0xffffff7f8bf3c000->0xffffff7f8bf4dfff
dependency: com.apple.AppleGraphicsDeviceControl(6.4.12)[F167C5E6-A75A-3C49-B8BC-F8EBE9B75B08]@0xffffff7f8bf02000->0xffffff7f8bf05fff
dependency: com.apple.driver.AppleGraphicsControl(6.4.12)[A9311664-AA00-3427-944F-E8AE08FBBADE]@0xffffff7f8beea000->0xffffff7f8beeafff
dependency: com.apple.iokit.IOACPIFamily(1.4)[9AAF8737-B8CD-3A43-A654-69FD563A54CA]@0xffffff800d52f000->0xffffff800d530fff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8c6f9000->0xffffff7f8c727fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800d9d6000->0xffffff800da00fff
com.apple.GeForceTesla(10.0.4)[6DB35165-76BB-306C-BE87-E69580EAE417]@0xffffff7f8c42f000->0xffffff7f8c4b6fff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8c6f9000->0xffffff7f8c727fff
dependency: com.apple.iokit.IONDRVSupport(593)[23ADBC95-22F8-3980-9A18-2708B931E7E7]@0xffffff7f8c741000->0xffffff7f8c749fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800d9d6000->0xffffff800da00fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8cb37000->0xffffff7f8cd4ffff

Process name corresponding to current thread (0xffffff901ce01540): WindowServer
Boot args: keepsyms=1 debug=0x100

Mac OS version:
21D49

Kernel version:
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F
KernelCache slide: 0x000000000ac00000
KernelCache base: 0xffffff800ae00000
Kernel slide: 0x000000000ac10000
Kernel text base: 0xffffff800ae10000
__HIB text base: 0xffffff800ad00000
System model name: MacBookPro6,2 (Mac-F22586C8)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 2

System uptime in nanoseconds: 1545338849526
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000167cd5f95e5
Sleep : 0x000001590ffc3c74 0x0000000065238a7f 0x0000015727978b43
Wake : 0x00000159109ab552 0x0000000064657717 0x00000159102a1d87
Zone info:
Foreign : 0xffffff800fce2000 - 0xffffff800fcef000
Native : 0xffffff801c2c5000 - 0xffffffa01c2c5000
Readonly : 0xffffff84e8f91000 - 0xffffff8682925000
Metadata : 0xffffffd7419dc000 - 0xffffffd761aa2000
Bitmaps : 0xffffffd761aa2000 - 0xffffffd764aa2000

 

[the.burn]

Just after posting, yet another one:
Only Safari and Spotify apps were running.


panic(cpu 3 caller 0xffffff7f8c94c075): GPU Panic: mux-regs 3 3 7f 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:3 power-state 0 3D idle HDA idle system-state 1 power-level 20:20 power-retry 0 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffffd04b1ed000 0x0a5480a2, D0, P2/4

Panicked task 0xffffff94e99bd700: 10 threads: pid 161: WindowServer
Backtrace (CPU 3), panicked thread: 0xffffff8b4f538aa0, Frame : Return Address
0xffffffd03a142ec0 : 0xffffff800b885ffd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd03a142f10 : 0xffffff800b9e6035 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd03a142f50 : 0xffffff800b9d5803 mach_kernel : _kernel_trap + 0x533
0xffffffd03a142fa0 : 0xffffff800b825a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd03a142fc0 : 0xffffff800b8863cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd03a1430e0 : 0xffffff800b885b86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd03a143140 : 0xffffff800c116409 mach_kernel : _panic + 0x54
0xffffffd03a1431b0 : 0xffffff7f8c94c075 com.apple.driver.AppleMuxControl : _Debugger + 0x73b075
0xffffffd03a143210 : 0xffffff7f8d588441 com.apple.nvidia.classic.NVDAResmanTesla : _osWriteRegistryDword + 0x321
0xffffffd03a1432d0 : 0xffffff7f8d6541ca com.apple.nvidia.classic.NVDAResmanTesla : _gpuExecRegOps + 0xeefd
0xffffffd03a143310 : 0xffffff7f8d654235 com.apple.nvidia.classic.NVDAResmanTesla : _gpuExecRegOps + 0xef68
0xffffffd03a143390 : 0xffffff7f8d3b37f0 com.apple.nvidia.classic.NVDANV50HalTesla : __ZN11NVDANV50HAL5probeEP9IOServicePi + 0x123d22
0xffffffd03a1434b0 : 0xffffff7f8d675d35 com.apple.nvidia.classic.NVDAResmanTesla : _constructObjEHeap + 0x51d3
0xffffffd03a1434d0 : 0xffffff7f8d58f048 com.apple.nvidia.classic.NVDAResmanTesla : _NvRmDupObject + 0x3b5
0xffffffd03a143580 : 0xffffff7f8d58ca84 com.apple.nvidia.classic.NVDAResmanTesla : _insert_registration_func + 0x240
0xffffffd03a143770 : 0xffffff7f8d58db25 com.apple.nvidia.classic.NVDAResmanTesla : _NvRmAlloc + 0x84
0xffffffd03a143850 : 0xffffff7f8ce6d3af com.apple.GeForceTesla : __ZN17nvEvoChannelTesla5FlushEP17nvPushBufferTesla + 0x57
0xffffffd03a143890 : 0xffffff7f8ce7c8f3 com.apple.GeForceTesla : __ZN17nvPushBufferTesla5FlushEv + 0x19
0xffffffd03a1438b0 : 0xffffff7f8cea3498 com.apple.GeForceTesla : __ZN26nvTeslaDisplayManagerTesla35TriggerReleaseOfRenderableSemaphoreEjRj + 0xe4
0xffffffd03a1438f0 : 0xffffff7f8cea34f4 com.apple.GeForceTesla : __ZN26nvTeslaDisplayManagerTesla19EmitChannelBeamSyncEP13__GLNVdataRecjjjjPj + 0x48
0xffffffd03a143920 : 0xffffff7f8ce822e1 com.apple.GeForceTesla : __ZN14nvSurfaceTesla12generateSyncEjjj + 0x15b
0xffffffd03a143970 : 0xffffff7f8ce4fcaf com.apple.GeForceTesla : __ZN16IONVSurfaceTesla11submit_swapEj7eDoSwapjP18IONVGLContextTesla + 0x309
0xffffffd03a143a00 : 0xffffff7f8ce4be83 com.apple.GeForceTesla : __ZN16IONVSurfaceTesla13flush_surfaceEjj + 0x7f
0xffffffd03a143a30 : 0xffffff7f8ce49bd0 com.apple.GeForceTesla : __ZN16IONVSurfaceTesla13surface_flushEjj + 0x104
0xffffffd03a143a70 : 0xffffff800c08bce6 mach_kernel : _shim_io_connect_method_scalarI_scalarO + 0x306
0xffffffd03a143b10 : 0xffffff800c08a3d8 mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x278
0xffffffd03a143b60 : 0xffffff800c09460c mach_kernel : _is_io_connect_method + 0x3cc
0xffffffd03a143cc0 : 0xffffff800b98d0b4 mach_kernel : _iokit_server_routine + 0x4e94
0xffffffd03a143dd0 : 0xffffff800b861048 mach_kernel : _ipc_kmsg_send + 0x468
0xffffffd03a143e60 : 0xffffff800b877a8d mach_kernel : _mach_msg_overwrite_trap + 0x2bd
0xffffffd03a143ef0 : 0xffffff800b9b8f7e mach_kernel : _mach_call_munger64 + 0x22e
0xffffffd03a143fa0 : 0xffffff800b826246 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8d537000->0xffffff7f8d74ffff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8d0f9000->0xffffff7f8d127fff
dependency: com.apple.iokit.IONDRVSupport(593)[23ADBC95-22F8-3980-9A18-2708B931E7E7]@0xffffff7f8d141000->0xffffff7f8d149fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800e3d6000->0xffffff800e400fff
com.apple.GeForceTesla(10.0.4)[6DB35165-76BB-306C-BE87-E69580EAE417]@0xffffff7f8ce2f000->0xffffff7f8ceb6fff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8d0f9000->0xffffff7f8d127fff
dependency: com.apple.iokit.IONDRVSupport(593)[23ADBC95-22F8-3980-9A18-2708B931E7E7]@0xffffff7f8d141000->0xffffff7f8d149fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800e3d6000->0xffffff800e400fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8d537000->0xffffff7f8d74ffff
com.apple.nvidia.classic.NVDANV50HalTesla(10.0.4)[5DCF031B-F81F-32A3-ADCD-18E16EAC7CF0]@0xffffff7f8d28f000->0xffffff7f8d45dfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800e3d6000->0xffffff800e400fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(10.0.4)[F8258F0F-61AD-30F4-BDD5-B18CCAAE535A]@0xffffff7f8d537000->0xffffff7f8d74ffff
com.apple.driver.AppleMuxControl(6.4.12)[6815B044-FD1A-3500-9710-4B19325C45F4]@0xffffff7f8c93c000->0xffffff7f8c94dfff
dependency: com.apple.AppleGraphicsDeviceControl(6.4.12)[F167C5E6-A75A-3C49-B8BC-F8EBE9B75B08]@0xffffff7f8c902000->0xffffff7f8c905fff
dependency: com.apple.driver.AppleGraphicsControl(6.4.12)[A9311664-AA00-3427-944F-E8AE08FBBADE]@0xffffff7f8c8ea000->0xffffff7f8c8eafff
dependency: com.apple.iokit.IOACPIFamily(1.4)[9AAF8737-B8CD-3A43-A654-69FD563A54CA]@0xffffff800df2f000->0xffffff800df30fff
dependency: com.apple.iokit.IOGraphicsFamily(593)[212D9F00-4979-3ACB-9108-4BB19404BE85]@0xffffff7f8d0f9000->0xffffff7f8d127fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[897B72E0-B98F-30BA-8CB2-4E5E469CE4B6]@0xffffff800e3d6000->0xffffff800e400fff

Process name corresponding to current thread (0xffffff8b4f538aa0): WindowServer
Boot args: keepsyms=1 debug=0x100

Mac OS version:
21D49

Kernel version:
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F
KernelCache slide: 0x000000000b600000
KernelCache base: 0xffffff800b800000
Kernel slide: 0x000000000b610000
Kernel text base: 0xffffff800b810000
__HIB text base: 0xffffff800b700000
System model name: MacBookPro6,2 (Mac-F22586C8)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 1

System uptime in nanoseconds: 1872447839367
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000001b3f696a943
Sleep : 0x00000151125525ed 0x000000098335c980 0x0000000000000000
Wake : 0x0000015112f448ae 0x0000000064fcd21f 0x00000151128080b5
Zone info:
Foreign : 0xffffff80106e2000 - 0xffffff80106ef000
Native : 0xffffff801cde4000 - 0xffffffa01cde4000
Readonly : 0xffffff84e9ab0000 - 0xffffff8683444000
Metadata : 0xffffffddc3c7e000 - 0xffffffdde3d46000
Bitmaps : 0xffffffdde3d46000 - 0xffffffdde6d46000

 

[rehkram]

I ran Big Sur and Monterey on dynamic volumes for a few months. I stopped doing that because it was glitchy. My best guess for why it was glitchy was the dynamic space allocation and maybe NVRAM sharing. (?)

I could never quite get my head around the implications of booting different macOS versions off of dynamic volumes on the same drive. If I don't understand something so fundamental to a stable system I finally figured out I should not be doing it.

So I reserved the internal drive for production macOS versions only, and an external SSD for betas. Things have been a lot smoother ever since. YMMV

 

[makra]

Never too late: you can reinstall ….???????

I chose High Sierra instead... Both OSes (HS and Big Sur) start flawlessly.

EDIT: NOT. High Sierra startet twice without any issues. The third start ended halfway by suddenly showing a disturbing icon...