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

[6DecadesLater]

Have installed Monterey 12.5 via OTA after OC0.8.3 update.
Used:

• SecureBootModel is set to Default
• Hybridization is used
• Firmware features are updated

Update was smooth and all looks good so far.

As always, many thanks for all the effort.

Update: Everything was fine for awhile. Sometime last night it had a panic. If I try and check if voice control is on, it panics once I click on the Voice Control in Accessibility. I can't seem to boot into safe mode. Anyone know how to turn Voice Control off via command line or in Recovery? I don't use it but I guess it may be on from other reports here.

Spoiler: Latest Panic Report

mp_kdp_enter() timed-out on cpu 8, NMI-ing
mp_kdp_enter() NMI pending on cpus: 0 1 2 3 5 7 9 11
mp_kdp_enter() timed-out during locked wait after NMI;expected 24 acks but received 17 after 29066221 loops in 1462999813 ticks
panic(cpu 8 caller 0xffffff80003d0773): Kernel trap at 0xffffff800188efe9, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff905ae0e004, CR3: 0x000000000498b000, CR4: 0x00000000000226e0
RAX: 0x0000000000000016, RBX: 0xffffff905ae07d00, RCX: 0x00000000000060a0, RDX: 0x0000000000000000
RSP: 0xfffffff3f1c7bd00, RBP: 0xfffffff3f1c7bd00, RSI: 0x000000000000060a, RDI: 0xffffff905ae07d00
R8: 0x00000000000022b8, R9: 0x0000000000000001, R10: 0xfffffff3f1d05258, R11: 0xfffffff3f1d051e0
R12: 0xffffff8b8f037000, R13: 0xffffff80010a34c0, R14: 0xffffff8b8f037108, R15: 0xffffff8b8f037108
RFL: 0x0000000000010006, RIP: 0xffffff800188efe9, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff905ae0e004, Error code: 0x0000000000000000, Fault CPU: 0x8, PL: 1, VF: 5
Panicked task 0xffffff99f272c670: 210 threads: pid 0: kernel_task
Backtrace (CPU 8), panicked thread: 0xffffff95268c2000, Frame : Return Address
0xfffffff3f1c7b6b0 : 0xffffff800027fd6d
0xfffffff3f1c7b700 : 0xffffff80003e1016
0xfffffff3f1c7b740 : 0xffffff80003d0383
0xfffffff3f1c7b790 : 0xffffff800021fa70
0xfffffff3f1c7b7b0 : 0xffffff800028013d
0xfffffff3f1c7b8d0 : 0xffffff800027f8f6
0xfffffff3f1c7b930 : 0xffffff8000b14d93
0xfffffff3f1c7ba20 : 0xffffff80003d0773
0xfffffff3f1c7bba0 : 0xffffff80003d0456
0xfffffff3f1c7bbf0 : 0xffffff800021fa70
0xfffffff3f1c7bc10 : 0xffffff800188efe9
0xfffffff3f1c7bd00 : 0xffffff800189aba1
0xfffffff3f1c7bd60 : 0xffffff800189a53e
0xfffffff3f1c7bda0 : 0xffffff800189a457
0xfffffff3f1c7be00 : 0xffffff8001899d40
0xfffffff3f1c7be60 : 0xffffff80018873c6
0xfffffff3f1c7bf20 : 0xffffff80003d2986
0xfffffff3f1c7bf40 : 0xffffff80002af86a
0xfffffff3f1c7bf80 : 0xffffff80002afa69
0xfffffff3f1c7bfa0 : 0xffffff800021f19e
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCPUPowerManagement(222.0)[C265571C-16EE-355B-9076-7A25CB15A73F]@0xffffff8001885000->0xffffff80018a1fff

Process name corresponding to current thread (0xffffff95268c2000): kernel_task
Boot args: -x chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
21G72
Kernel version:
Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
Kernel UUID: E3E2BC4D-7B6F-39CC-8890-73A6FB513830
KernelCache slide: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 12446700111
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000002e5e19b54
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000026b989be92 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: 0xffffff8057af5000 - 0xffffffa057af5000
. PGZ : 0xffffff8057af5000 - 0xffffff805daf6000
. VM : 0xffffff805daf6000 - 0xffffff852995c000
. RO : 0xffffff852995c000 - 0xffffff86c2e28000
. GEN0 : 0xffffff86c2e28000 - 0xffffff8b8ec8e000
. GEN1 : 0xffffff8b8ec8e000 - 0xffffff905aaf4000
. GEN2 : 0xffffff905aaf4000 - 0xffffff952695a000
. GEN3 : 0xffffff952695a000 - 0xffffff99f27c1000
. DATA : 0xffffff99f27c1000 - 0xffffffa057af5000
Metadata: 0xffffffa097b05000 - 0xffffffa0b7b05000
Bitmaps : 0xffffffa0b7b05000 - 0xffffffa0c9b05000
last started kext at 11445573159: >X86PlatformShim 1.0.0 (addr 0xffffff7f993d6000, size 24576)
loaded kexts:
com.khronokernel.FeatureUnlock 1.0.9
as.vit9696.WhateverGreen 1.6.1
as.vit9696.Lilu 1.6.2
>X86PlatformShim 1.0.0
@filesystems.autofs 3.0
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>!ALPC 3.1
>!AGraphicsDevicePolicy 6.5.7
>!ADiskImages2 126.141.2
>ACPI_SMC_PlatformPlugin 1.0.0
@kext.AMD9500!C 4.0.8
>!UDisplays 380
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 583.100.10
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
|SCSITaskUserClient 456.140.3
@filesystems.apfs 1934.141.2
>!I82574LEthernet 2.7.2
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 351.100.4
@private.KextAudit 1.0
>!ARTC 2.0.1
>!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 402
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
>!A!ICPUPowerManagement 222.0.0
@kec.!AEncryptedArchive 1
@kext.triggers 1.0
>!AHIDKeyboard 228.2
>!ASMBus!C 1.0.18d1
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.5.7
|IONDRVSupport 597
>IOPlatformPluginLegacy 1.0.0
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@!AGPUWrangler 6.5.7
@kext.AMDSupport 4.0.8
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
>!UHIDMouse 196
>!AHIDMouse 196
>usb.IOUSBHostHIDDevice 1.
|IOAHCIBlock!S 333.140.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!ABSDKextStarter 3
|IOSurface 302.14
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 456.140.3
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>!AXsanScheme 3
|IOAHCISerialATAPI 270
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IONVMe!F 2.1.0
|IOAHCI!F 297
>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
|IOTimeSync!F 1040.3
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 533.120.2
|IOUSBMass!SDriver 210.120.3
|IOSCSIBlockCommandsDevice 456.140.3
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 456.140.3
>!AMobileFileIntegrity 1.0.5
$!AImage4 4.2.0
@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.Libm 1
@kec.corecrypto 12.0

 

[tsialex]

Update: Everything was fine for awhile. Sometime last night it had a panic. If I try and check if voice control is on, it panics once I click on the Voice Control in Accessibility. I can't seem to boot into safe mode. Anyone know how to turn Voice Control off via command line or in Recovery? I don't use it but I guess it may be on from other reports here.

Spoiler: Latest Panic Report

mp_kdp_enter() timed-out on cpu 8, NMI-ing
mp_kdp_enter() NMI pending on cpus: 0 1 2 3 5 7 9 11
mp_kdp_enter() timed-out during locked wait after NMI;expected 24 acks but received 17 after 29066221 loops in 1462999813 ticks
panic(cpu 8 caller 0xffffff80003d0773): Kernel trap at 0xffffff800188efe9, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff905ae0e004, CR3: 0x000000000498b000, CR4: 0x00000000000226e0
RAX: 0x0000000000000016, RBX: 0xffffff905ae07d00, RCX: 0x00000000000060a0, RDX: 0x0000000000000000
RSP: 0xfffffff3f1c7bd00, RBP: 0xfffffff3f1c7bd00, RSI: 0x000000000000060a, RDI: 0xffffff905ae07d00
R8: 0x00000000000022b8, R9: 0x0000000000000001, R10: 0xfffffff3f1d05258, R11: 0xfffffff3f1d051e0
R12: 0xffffff8b8f037000, R13: 0xffffff80010a34c0, R14: 0xffffff8b8f037108, R15: 0xffffff8b8f037108
RFL: 0x0000000000010006, RIP: 0xffffff800188efe9, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff905ae0e004, Error code: 0x0000000000000000, Fault CPU: 0x8, PL: 1, VF: 5
Panicked task 0xffffff99f272c670: 210 threads: pid 0: kernel_task
Backtrace (CPU 8), panicked thread: 0xffffff95268c2000, Frame : Return Address
0xfffffff3f1c7b6b0 : 0xffffff800027fd6d
0xfffffff3f1c7b700 : 0xffffff80003e1016
0xfffffff3f1c7b740 : 0xffffff80003d0383
0xfffffff3f1c7b790 : 0xffffff800021fa70
0xfffffff3f1c7b7b0 : 0xffffff800028013d
0xfffffff3f1c7b8d0 : 0xffffff800027f8f6
0xfffffff3f1c7b930 : 0xffffff8000b14d93
0xfffffff3f1c7ba20 : 0xffffff80003d0773
0xfffffff3f1c7bba0 : 0xffffff80003d0456
0xfffffff3f1c7bbf0 : 0xffffff800021fa70
0xfffffff3f1c7bc10 : 0xffffff800188efe9
0xfffffff3f1c7bd00 : 0xffffff800189aba1
0xfffffff3f1c7bd60 : 0xffffff800189a53e
0xfffffff3f1c7bda0 : 0xffffff800189a457
0xfffffff3f1c7be00 : 0xffffff8001899d40
0xfffffff3f1c7be60 : 0xffffff80018873c6
0xfffffff3f1c7bf20 : 0xffffff80003d2986
0xfffffff3f1c7bf40 : 0xffffff80002af86a
0xfffffff3f1c7bf80 : 0xffffff80002afa69
0xfffffff3f1c7bfa0 : 0xffffff800021f19e
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelCPUPowerManagement(222.0)[C265571C-16EE-355B-9076-7A25CB15A73F]@0xffffff8001885000->0xffffff80018a1fff

Process name corresponding to current thread (0xffffff95268c2000): kernel_task
Boot args: -x chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
21G72
Kernel version:
Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
Kernel UUID: E3E2BC4D-7B6F-39CC-8890-73A6FB513830
KernelCache slide: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 12446700111
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000002e5e19b54
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000026b989be92 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: 0xffffff8057af5000 - 0xffffffa057af5000
. PGZ : 0xffffff8057af5000 - 0xffffff805daf6000
. VM : 0xffffff805daf6000 - 0xffffff852995c000
. RO : 0xffffff852995c000 - 0xffffff86c2e28000
. GEN0 : 0xffffff86c2e28000 - 0xffffff8b8ec8e000
. GEN1 : 0xffffff8b8ec8e000 - 0xffffff905aaf4000
. GEN2 : 0xffffff905aaf4000 - 0xffffff952695a000
. GEN3 : 0xffffff952695a000 - 0xffffff99f27c1000
. DATA : 0xffffff99f27c1000 - 0xffffffa057af5000
Metadata: 0xffffffa097b05000 - 0xffffffa0b7b05000
Bitmaps : 0xffffffa0b7b05000 - 0xffffffa0c9b05000
last started kext at 11445573159: >X86PlatformShim 1.0.0 (addr 0xffffff7f993d6000, size 24576)
loaded kexts:
com.khronokernel.FeatureUnlock 1.0.9
as.vit9696.WhateverGreen 1.6.1
as.vit9696.Lilu 1.6.2
>X86PlatformShim 1.0.0
@filesystems.autofs 3.0
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>!ALPC 3.1
>!AGraphicsDevicePolicy 6.5.7
>!ADiskImages2 126.141.2
>ACPI_SMC_PlatformPlugin 1.0.0
@kext.AMD9500!C 4.0.8
>!UDisplays 380
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.lifs 1
@filesystems.hfs.kext 583.100.10
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
|SCSITaskUserClient 456.140.3
@filesystems.apfs 1934.141.2
>!I82574LEthernet 2.7.2
>AirPort.BrcmNIC 1400.1.1
>!AAHCIPort 351.100.4
@private.KextAudit 1.0
>!ARTC 2.0.1
>!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 402
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
@Dont_Steal_Mac_OS_X 7.0.0
>!A!ICPUPowerManagement 222.0.0
@kec.!AEncryptedArchive 1
@kext.triggers 1.0
>!AHIDKeyboard 228.2
>!ASMBus!C 1.0.18d1
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.5.7
|IONDRVSupport 597
>IOPlatformPluginLegacy 1.0.0
>X86PlatformPlugin 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@!AGPUWrangler 6.5.7
@kext.AMDSupport 4.0.8
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
>!UHIDMouse 196
>!AHIDMouse 196
>usb.IOUSBHostHIDDevice 1.
|IOAHCIBlock!S 333.140.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!ABSDKextStarter 3
|IOSurface 302.14
@filesystems.hfs.encodings.kext 1
|IOSCSIMultimediaCommandsDevice 456.140.3
|IOBD!S!F 1.8
|IODVD!S!F 1.8
|IOCD!S!F 1.8
>!AXsanScheme 3
|IOAHCISerialATAPI 270
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IONVMe!F 2.1.0
|IOAHCI!F 297
>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
|IOTimeSync!F 1040.3
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 9.0.0
|IOReport!F 47
$quarantine 4
$sandbox 300.0
@Kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 533.120.2
|IOUSBMass!SDriver 210.120.3
|IOSCSIBlockCommandsDevice 456.140.3
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 456.140.3
>!AMobileFileIntegrity 1.0.5
$!AImage4 4.2.0
@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.Libm 1
@kec.corecrypto 12.0

NMI crashes with AppleIntelCPUPowerManagement are usually related to the northbridge overheating, did you checked it?

Also, while you are inspecting, check the BR2032 RTC battery voltage with a voltmeter/multimeter and replace it if below 3.00V.

 

[6DecadesLater]

NMI crashes with AppleIntelCPUPowerManagement are usually related to the northbridge overheating, did you checked it?

Also, while you are inspecting, check the BR2032 RTC battery voltage with a voltmeter/multimeter and replace it if below 3.00V.

Thanks. NB doesn't seem too hot but installed a fan control (TG Pro) to cool it down. I will redo heatsink and clean very soon. I tried a number of things:

1. Fan control
2. Went after anything with voice activity
   1. Command + F5 to toggle Voice Over on and off
   2. Turned off Siri via preferences
   3. Turned off dictation via Keyboard preferences
   4. killed com.apple.SpeechRecognitionCore.brokerd (it restarts on its own)
3. Rebooted

Now can access the preferences pane for voice control and see it is off

Seems stable for the moment. Will update if that changes.
Edit: Interesting that when I first searched for speech related items in activity monitor I only found
corespeechd and com.apple.SpeechRecognitionCore.brokerd (former could not be killed)
Now that it seems more stable, I have those plus more after turning of speech related control items
com.apple.siri.embeddedspeech
com.apple.speech.speechsynthesized
localspeechrecognition
com.apple.preference.speech.remoteservices (System Preferences)
Expected less not more with turning things off

 

[Ermine8]

I'll give a brief description of the file replacement process:
Firstly, you'll want to grab the os.dmg image from an M1 preboot volume. If you look into this image, you'll see the x86_64 caches (non-h variant).
Copy this disk image to a USB drive in preparation for the replacement.
Then you'll want to get Ventura "installed" onto your CMP. macOS will eventually stall at a point during the verbose portion of the first "installed" boot.
Once macOS stalls, reboot and ensure that macOS is still stalled.
Then you can reboot again into the recovery environment
From the recovery, you can open up a terminal window and mount the fresh install's preboot volume (diskutil list, diskutil mount disk#s#)
Once you get the preboot mounted, you'll want to navigate to /Volumes/Preboot/Long-UUID(check this using ls)/cryptex1/current/
Run an ls command here, and you should see the os.dmg file
Now run a cp command and replace the Preboot's os.dmg with the M1 os.dmg
Once that's done, reboot your machine and Ventura should boot to either a loading bar at ~60% with a cursor or a grey screen with a beachball.
Now you'll need to remove the Ventura drive from your cMP and install it/boot from it in another mac that is Ivy Bridge+.
This is done because the Ventura setup assistant does not play well with Non-AVX1 machines
Once you get through the Ventura Setup assistant, remove the drive and reinstall it in your cMP
If all things go to plan, you should boot into the Ventura desktop!
Oh, that wasn't very brief
Well, good luck!
Edit: oh, and this should be done with the EFI I sent, or at least with the "APFS Disable Patch thingy" from the config.plist
Edit 2: for convenience, here's the M1 os.dmg image: https://drive.google.com/uc?export=download&id=12vCE0MAzcRqN7zJu5EbbzsZeroeI_Gsm

There is no Recovery option to enter and make necessary procedures in terminal after verbose booting interuption. Forcefully? Please make your description more explicit as for example those commands like "cp" what for what, you know.

 

[Ermine8]

I'll give a brief description of the file replacement process:
Firstly, you'll want to grab the os.dmg image from an M1 preboot volume. If you look into this image, you'll see the x86_64 caches (non-h variant).
Copy this disk image to a USB drive in preparation for the replacement.
Then you'll want to get Ventura "installed" onto your CMP. macOS will eventually stall at a point during the verbose portion of the first "installed" boot.
Once macOS stalls, reboot and ensure that macOS is still stalled.
Then you can reboot again into the recovery environment
From the recovery, you can open up a terminal window and mount the fresh install's preboot volume (diskutil list, diskutil mount disk#s#)
Once you get the preboot mounted, you'll want to navigate to /Volumes/Preboot/Long-UUID(check this using ls)/cryptex1/current/
Run an ls command here, and you should see the os.dmg file
Now run a cp command and replace the Preboot's os.dmg with the M1 os.dmg
Once that's done, reboot your machine and Ventura should boot to either a loading bar at ~60% with a cursor or a grey screen with a beachball.
Now you'll need to remove the Ventura drive from your cMP and install it/boot from it in another mac that is Ivy Bridge+.
This is done because the Ventura setup assistant does not play well with Non-AVX1 machines
Once you get through the Ventura Setup assistant, remove the drive and reinstall it in your cMP
If all things go to plan, you should boot into the Ventura desktop!
Oh, that wasn't very brief
Well, good luck!
Edit: oh, and this should be done with the EFI I sent, or at least with the "APFS Disable Patch thingy" from the config.plist
Edit 2: for convenience, here's the M1 os.dmg image: https://drive.google.com/uc?export=download&id=12vCE0MAzcRqN7zJu5EbbzsZeroeI_Gsm

I would like you to record a video about how to make this all.

 

[David403]

I would like you to record a video about how to make this all.

If you have to ask this question you should not be attempting this.

Instead of making requests like this why don't you simply follow the advice at post# 1 and # 502 on the 'macOS 13 Ventura on Unsupported Macs Thread' - "Please read the first post before installing...Ventura DOES NOT WORK PROPERLY on ANY unsupported mac!!!" You will save yourself and everyone else both time and space

 

[hwojtek]

Please make your description more explicit as for example those commands like "cp" what for what, you know.

This is not exactly the place for such demands.

 

[Ermine8]

If you have to ask this question you should not be attempting this.

Instead of making requests like this why don't you simply follow the advice at post# 1 and # 502 on the 'macOS 13 Ventura on Unsupported Macs Thread' - "Please read the first post before installing...Ventura DOES NOT WORK PROPERLY on ANY unsupported mac!!!" You will save yourself and everyone else both time and space

Yes. I've written here by mistake.

 

[jsts]

Anyone having issues with bluetooth BCM943602 in BS and Monterey?

I have. Same situation: bluetooth (bought in 2018 on Ebay) BCM943602 CD PAX on the Monterey 12.4 does not work, shows "off", the "Enable" button in the system settings does not react (on Mojave, it works).

Bluetooth Controller: Address: NULL State: Off Chipset: BCM_4350C2 Discoverable: Off Firmware Version: v0 c0 Product ID: 0x0001 Supported services: 0x382039 < HFP AVRCP A2DP HID Braille AACP GATT Serial > Transport: USB Vendor ID: 0x004C (Apple)

At the same time Wi-Fi works successfully. Did you have a solution?

 

[jsts]

Did you have a solution?

Ah, I found the answer (1, 2, 3). The problem is that Monterey removed support for the old USB 1.1 bus used in the MacPro5.1 for Bluetooth data (BT is connected to the USB 1.1 port). Now I'm trying to figure out if OpenCore can be used to solve this issue.

 

[MacHosehead]

Ah, I found the answer (1, 2, 3). The problem is that Monterey removed support for the old USB 1.1 bus used in the MacPro5.1 for Bluetooth data (BT is connected to the USB 1.1 port). Now I'm trying to figure out if OpenCore can be used to solve this issue.

With my MP4,1->5,1, I have replaced wifi/bt card and still use the onboard bluetooth USB port. Many of the bluetooth chipsets that worked in Big Sur were dropped in Monterey. Some chipsets can be patched by OCLP or else you need to replace wifi/bt module with one that Monterey supports. The BCM94360CD card is popular.

I use a USB 3.0 PCIe card that is Apple compatible and I have tried connecting bluetooth USB to it. It will work but anything connected to it will not wake Mac from sleep. So I only use the Mac USB for bluetooth and I have not had any issues so far. It is more like a real Mac.

Running Monterey 12.5 with OCLP 4.7

 

[amarmot]

Ah, I found the answer (1, 2, 3). The problem is that Monterey removed support for the old USB 1.1 bus used in the MacPro5.1 for Bluetooth data (BT is connected to the USB 1.1 port). Now I'm trying to figure out if OpenCore can be used to solve this issue.

I've had good luck in Big Sur and Monterey (5,1) with OSXWiFi BCM94360CD under OCLP 0.4.9 (as well as Martin Lo's package 0.80). I've read that the BCM943602CDP (Bluetooth 4.2) has been problematic for some people, but don't remember the details.

 

[PeterHolbrook]

I have. Same situation: bluetooth (bought in 2018 on Ebay) BCM943602 CD PAX on the Monterey 12.4 does not work, shows "off", the "Enable" button in the system settings does not react (on Mojave, it works).

I don't know about the "PAX" part, but I have a Broadcom BCM943602CDP and it works just fine. However, you should be aware of an oddity, which I think is related to how the NVRAM is read and/or written in different macOS iterations. If I boot Mojave, I'll have Bluetooth, but the FIRST time I go back to either Big Sur or Monterey, there'll be no Bluetooth on the BCM943602CDP and possibly similar cards. To get Bluetooth back on, simply reboot once again into Big Sur or Monterey. Done. Naturally, you'll need to repeat the double boot each time you boot Mojave.

 

[jsts]

I don't know about the "PAX" part, but I have a Broadcom BCM943602CDP and it works just fine. However, you should be aware of an oddity, which I think it's related to how the NVRAM is read and/or written in different macOS iterations. If I boot Mojave, I'll have Bluetooth, but the FIRST time I go back to either Big Sur or Monterey, there'll be no Bluetooth on the BCM943602CDP and possibly similar cards. To get Bluetooth back on, simply reboot once again into Big Sur or Monterey. Done. Naturally, you'll need to repeat the double boot each time you boot Mojave.

You're right. After several restarts the bluetooth itself is back in place and successfully working. Miracle! %)

Thank you.

 

[Gustav Holdoff]

The guide has been updated to OpenCore version 0.8.3. There are just a few minor changes (see the Maintenance section).

Thanks to the hard work of @Bmju, a notable addition to this version of OC is emulated NVRAM (useful not only for those with firmware chip issues but for touvlophobics as well). Configuration steps will be added to the guide as time permits.

I ordered radeon proW6800
and before I start any bios manipulation I need to understand:

syncretic wrote:
IMPORTANT NOTE: apparently, for the RX6x00(XT) to work with MacOS, you'll need to be running OpenCore, WhateverGreen, Lilu, and include agdpmod=pikera in your boot-args. Failure to do this will almost certainly result in a black screen after booting. (Again, I don't have a card to play with, so any questions regarding the boot-args or the specific configuration of OpenCore, WhateverGreen, and/or Lilu need to be asked of someone else.)

As i can find:
you use boot argument pikera for mojave only
"For macOS Mojave
The best board ID in this case is the iMacPro's. In the spoofing steps above, replace "Mac-27AD2F918AE68F61" by "Mac-7BA5B2D9E42DDD94". Because of this change, you'll also need an extra device property:

Find ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀	Replace ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀ ⠀
<key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key> <dict> ⋮ </dict> </dict> <key>Delete</key> ⠀ ⠀	<key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)</key> <dict> ⋮ <key>agdpmod</key> <string>pikera</string> </dict> </dict> <key>Delete</key>

Again, make sure to replace "PciRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)" with the actual path of your graphics card."

And as You recommended:
If you're using OpenCore to boot only Catalina and later, then you can clean up the NVRAM:
and I deleted all boot arguments
and nowhere else can I find a boot argument
Will a patched RX6800 graphics card work in Monterey 12.5 with your config?

My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb+msata crucial 1tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.3, mac os 12.5

 

[ThiagodlT]

Hi CDF,
Hadn't updated my OC in a while and this week I upgraded from BigSur to Monterey 12.5 using h9826790's 8.0.0 (and 8.0.2 plist) pack for upgrading it quickly, and now I'm re-reading your guide and changelogs form OC realeases to get up to date in everything and make my own 8.3.0 .plist again by fusing your guide with h9826790's plist.
Since I don't use previous OS's anymore and the new option of the OC-CD, which I already made and tested succesfully, having a Mojave backup drive seems reduntant for me so many config options from his plist are not needed anymore since it's made for maximung compatibility in hardware and OS's.

There are some things that I'm not sure if they still apply or not (I have a lot to read and search still) but I wanted to ask about some of them that I cannot find a lot of info on if they apply to this machines.
I like the approach of h9826790's of not having to set the deviceproperties of the pcie devices (graphics and harddrives) since I sometimes move things around or change graphics cards and previously had problems booting after changing things with your aproach of device properties, and h9826790's just works no matter the order so i'm using his approach through bootargs (removing shikigva and pikera and others I dont need) and IONVMEfamily patch.

My fused .plist is working great right now, my machines is booted and working fine (graphics acceleration working, DRM working, drives showing internal)

But

I bumped into this somewhat old post of yours mentioning to remove the ionvmefamily patch because of it beign deprecated (it still works to date though)and instead use deviceproperties with PCIE paths.

This shouldn't happen. I would try recreating a fresh setup by following the instructions in Basic setup. Make sure to redownload all the files and use the basic config in post #1 without any modifications. Once you get the boot menu working properly, you can move on to customizing your config.


Some comments and recommendations:

1. agdpmod device property isn't necessary when spoofing Mac-27AD2F918AE68F61
2. double check the path of your graphics card with gfxutil (this might explain your issues with DRM)
3. use device properties to make your PCIe drives internal (if you have any) and remove the IONVMeFamily patch and set ExternalDiskIcons to false (these patches can be considered deprecated)
   ....

Why do you recommend this? Is there any fundamental difference or thing I should be aware about? (for drives and/or graphics cards)
My card is an XFX RX5500XT and is currently showing link speed as x16 although it is x8 and previously showed as x8 so I see that as something's not right.

I'm also wondering if the following kexts, besides the basics, are still required for just running Monterey or if some of them are also redundant betwen them:
- Bluetooth-Spoof.kext
- BlueToolFixup.kext
- NVMeFix.kext
- HibernationFixup.kext

I want to have an unclutered and not reduntat EFI and .plist to reduce chances of problems but with maximun "native" Mac functions so I wanted to see if you could give some advice.

Also I had read somewhere theres is an AVX emulator of sorts being worked on, but I can't find anything besides AVXpel, wonder if you can point me in the right direction. (want to use some AVX dependant audio software)

My machines is a 4,1 -> 5,1 single CPU x5675 64gb RAM with pcie sata card, nvme pcie adaptar and XFX RX5500xt , if it changes anything. I'm planning on some future USB3/TB3 updates so thats why my .plist still has those options.

Thanks in advance.

 

[William4673]

Hi all,

I hope this is the right place for this. Please forgive me if I need to provide more info.

Last night I installed stock macOS 12.5 Monterey on a separate SSD from my open core blessed drive, which includes Mojave on it.

My config is h9826790’s 0.8.0 package, i have a 5,1 dual processor and an rx580 pulse with a new upgraded Bluetooth card (4.0 wifi) that is compatible with the modern operating systems. My main open core boot drive is a SATA ssd in my first drive slot. My Monterey OS is also on an internal SSD slot.

So far, everything works fine. I’ve tested basic functionality. iMessage works as well as other apps, no kernel panics yet. But I’m curious about a couple things.

Is 12.5 able to corrupt the rest of the drive it’s stored on? I remember reading that it was taking over machines and blocking the boot picker from seeing any other OSes older than it.

My Bluetooth is not able to be turned on. Where in the plist do I need to edit to reenable this? as I would like to continue using continuity features.

What are some steps to take, and optimizations to make to keep my NVRAM healthy (avoiding KPs) , make it run smooth, and not trash my machine? What are the risks and potential negative effects of running it under 0.8.0, and what can I do to mitigate them? What are good practices or changes I should make to my plist? The above posts says you should make your OWN modified plist?

Thank you all so much for your time. The knowledge this community has is truly stunning. Take care. Any advice or direction would be incredible.

-W

 

[TECK]

@cdf I re-installed Windows with your procedure posted into OP. Everything works as expected, except the Bluetooth Apple Magic keyboard/mouse behave erratically, like they were in Windows 10. More exactly, keyboard and mouse work fine with default Microsoft drivers, but if you want to use the Magic Mouse scroll feature, you need to install the missing HID drivers with brigadier. The devices are detected fine in Windows 11, however, when I switch back to Monterey, the keyboard/mouse are unusable. I have to plug a wired keyboard/mouse, delete the devices from Bluetooth Preferences and add them back, then everything is back to normal. However, this will break the keyboard/mouse in Windows.

Here some install suggestions I recommend you update into your guide, to visually recognize you are working with correct disk (you should never deal with Finder, only terminal):

Validate the Windows disk:

~$ diskutil list /dev/disk0
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data Windows                 499.9 GB   disk0s2

Mount Windows EFI partition:

~$ sudo diskutil mount /dev/disk0s1
Password:
Volume EFI on /dev/disk0s1 mounted

Create EFI directory and copy Microsoft directory from USB drive into Windows EFI mounted partition:

~$ install -d /Volumes/EFI/EFI
~$ cp -a /Volumes/USB/EFI/Microsoft /Volumes/EFI/EFI/

Unmount Windows EFI partition:

~$ sudo diskutil unmount /dev/disk0s1
Volume EFI on disk0s1 unmounted

After install, select the default Startup Disk in Monterey, as it defaults to Windows:

Optional brigadier instructions:

Brigadier PowerShell commands in Windows 11 executed as Administrator (to get the Apple drivers for cMP5,1):

Set-ExecutionPolicy Unrestricted
brigadier.ps1 -m 'iMacPro1,1'
Set-ExecutionPolicy Restricted

I also tried model 'MacPro7,1' but it does not contains the old 'white' model Magic drivers.

Open Device Manager and point any unrecognized device to /$WinPEDriver$ directory created by brigadier, to install the drivers. Make sure you use a wired keyboard and mouse, using the Bluetooth models will freeze them. To fix the Magic Mouse scrolling, right click on /$WinPEDriver$/AppleWirelessMouse/AppleWirelessMouse.inf and install the driver. Switch on the Magic devices and add them into Bluetooth section.

 

[startergo]

@cdf I re-installed Windows with your procedure posted into OP. Everything works as expected, except the Bluetooth Apple Magic keyboard/mouse behave erratically, like they were in Windows 10. More exactly, keyboard and mouse work fine with default Microsoft drivers, but if you want to use the Magic Mouse scroll feature, you need to install the missing HID drivers with brigadier. The devices are detected fine in Windows 11, however, when I switch back to Monterey, the keyboard/mouse are unusable. I have to plus a wired keyboard/mouse, delete the devices from Bluetooth Preferences and add them back, then everything is back to normal. However, this will break the keyboard/mouse in Windows.

Here some install suggestions I recommend you update into your guide, to visually recognize you are working with correct disk (you should never deal with Finder, only terminal):

Validate the Windows disk:

~$ diskutil list /dev/disk0
/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data Windows                 499.9 GB   disk0s2

Mount Windows EFI partition:

~$ sudo diskutil mount /dev/disk0s1
Password:
Volume EFI on /dev/disk0s1 mounted

Create EFI directory and copy Microsoft directory from USB drive into Windows EFI mounted partition:

~$ install -d /Volumes/EFI/EFI
~$ cp -a /Volumes/USB/EFI/Microsoft /Volumes/EFI/EFI/

Unmount Windows EFI partition:

~$ sudo diskutil unmount /dev/disk0s1
Volume EFI on disk0s1 unmounted

After install, select the default Startup Disk in Monterey, as it defaults to Windows:

View attachment 2039928

Optional brigadier instructions:

Brigadier PowerShell commands in Windows 11 executed as Administrator (to get the Apple drivers for cMP5,1):

Set-ExecutionPolicy Unrestricted
brigadier.ps1 -m 'iMacPro1,1'
Set-ExecutionPolicy Restricted

I also tried model 'MacPro7,1' but it does not contains the old 'white' model Magic drivers.

Open Device Manager and point any unrecognized device to /$WinPEDriver$ directory created by brigadier, to install the drivers. Make sure you use a wired keyboard and mouse, using the Bluetooth models will freeze them. To fix the Magic Mouse scrolling, right click on /$WinPEDriver$/AppleWirelessMouse/AppleWirelessMouse.inf and install the driver. Switch on the Magic devices and add them into Bluetooth section.

I never boot Windows from OC. Always through RP (on cMP's) or rEFInd on PC. This way Windows boots natively and UUID's or NVRAM settings are not mixed with OC.
If i have to use OC i chain load from RP or rEFInd.

 

[TECK]

Always through RP (on cMP's)

I don't know what RP is, do you have a link or tutorial? You are probably referring to RefindPlus, if you have a chance please post the instructions link for cMP. I thought the instructions posted into OP are the recommended ones.

 

[startergo]

I don't know what RP is, do you have a link or tutorial? You are probably referring to RefindPlus, if you have a chance please post the instructions link for cMP. I thought the instructions posted into OP are the recommended ones.

@Dayo created automatic chain load solution. The link is in his signature.

 

[Bmju]

The devices are detected fine in Windows 11, however, when I switch back to Monterey, the keyboard/mouse are unusable.

Just for interest, does it work in Monterey again without requiring workarounds if you power down completely between Windows and Monterey? (I have seen several devices (audio, keyboard, trackpad, etc.) and systems where this applies, i.e. Windows driver leaves device in a state macOS does not expect - or sometimes vice versa - in which case cold booting into the other OS resolves the issue.)

 

[cdf]

syncretic wrote:
IMPORTANT NOTE: apparently, for the RX6x00(XT) to work with MacOS, you'll need to be running OpenCore, WhateverGreen, Lilu, and include agdpmod=pikera in your boot-args. Failure to do this will almost certainly result in a black screen after booting. (Again, I don't have a card to play with, so any questions regarding the boot-args or the specific configuration of OpenCore, WhateverGreen, and/or Lilu need to be asked of someone else.)

Based on this, you should include agdpmod=pikera even in Monterey, at least initially. For the initial setup, it's best to include this as a boot argument rather than a device property (just add it like the -no_compat_check argument in the basic config) and determine whether it is actually needed. If you've determined that it is indeed needed, then you can try including it as a device property and clean up your NVRAM variables for a more permanent setup (note that with some graphics cards, device properties don't work, so you can test this as well with your card).

Make sure to keep us posted on how things go!

 

[cdf]

Why do you recommend this? Is there any fundamental difference or thing I should be aware about? (for drives and/or graphics cards)

The IONVMEfamily patch is superficial: drives already identified as external in the I/O Registry are treated in some cases as internal. While it's unclear whether such discrepancy can cause adverse effects, it's certainly not how macOS expects things. In contrast, using the built-in device property is exactly how Apple does it on supported hardware.

As for using boot arguments instead of device properties, there is no difference for WEG. However, boot arguments are intended to be used for testing because they can be cleared by resetting the NVRAM. Using them in a more permanent way requires overriding native NVRAM behavior, which is something that should be considered undesirable.

I'm also wondering if the following kexts, besides the basics, are still required for just running Monterey or if some of them are also redundant betwen them:
- Bluetooth-Spoof.kext
- BlueToolFixup.kext
- NVMeFix.kext
- HibernationFixup.kext

These aren't generally required for running any version of macOS, though the bluetooth ones might be useful if you haven't upgraded your bluetooth card.

I want to have an unclutered and not reduntat EFI and .plist to reduce chances of problems but with maximun "native" Mac functions so I wanted to see if you could give some advice.

Because you've prepared an OC-CD, you can now easily recover from a misconfiguration, so you can experiment (for example, you can verify whether you actually need the kexts mentioned above), and obtain a clean deliberate setup that you understand and can maintain.

Also I had read somewhere theres is an AVX emulator of sorts being worked on, but I can't find anything besides AVXpel, wonder if you can point me in the right direction. (want to use some AVX dependant audio software)

Unfortunately, there is no AVX solution available at this point.

 

[cdf]

Is 12.5 able to corrupt the rest of the drive it’s stored on? I remember reading that it was taking over machines and blocking the boot picker from seeing any other OSes older than it.

I am not aware of such an issue.

My Bluetooth is not able to be turned on. Where in the plist do I need to edit to reenable this? as I would like to continue using continuity features.

Your Bluetooth module may be too old. The recommendation here is to update it. I've had no issues with the BCM94360CD. The BCM943602CDP is another possibility but it might be trickier to use, especially when multi-booting (see post #11,388 above).

What are some steps to take, and optimizations to make to keep my NVRAM healthy (avoiding KPs) , make it run smooth, and not trash my machine?

A good way to keep your NVRAM healthy is to periodically reflash a clean BootROM image. If you are having issues, you may benefit from @tsialex's reconstruction service. An additional protection is using a Matt card.

In the mean time, you can also use the emulated NVRAM feature available in OC 0.8.3 (when I get the chance, I'll add some instructions in the guide).

What are the risks and potential negative effects of running it under 0.8.0, and what can I do to mitigate them?

Using OC 0.8.0 is perfectly fine. You just won't have the latest features (like emulated NVRAM).

What are good practices or changes I should make to my plist? The above posts says you should make your OWN modified plist?

The reason for creating your own config is to have a clean deliberate setup that is easy for you to maintain. The first post of this thread provides an up-to-date guide on how to achieve this.