Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Does anyone know how to zero in on which process or device is causing this? If I revert to my vanilla Mojave install it never happens but with my OC/Monterey install it is a daily occurrence - usually overnight. I've stripped it down to a single SSD and graphics card - no other peripheral plugged in (including the WiFi/BT card) - with 3 different graphics cards and it panics every day. I have another dual-proc cMP that I've tried out all of the peripherals with and the dual-proc machine never panics.
panic(cpu 0 caller 0xffffff8001629d31): IOSCSIPeripheralDeviceType05::setPowerState(0xffffff8b92a772e0 : 0xffffff8003a81aea, 1 -> 4) timed out after 102293 ms @IOServicePM.cpp:5524
Panicked task 0xffffff8b9270c670: 333 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff8b93257aa0, Frame : Return Address
0xffffffac35e73a30 : 0xffffff8000e7befd
0xffffffac35e73a80 : 0xffffff8000fdeb96
0xffffffac35e73ac0 : 0xffffff8000fcdf03
0xffffffac35e73b10 : 0xffffff8000e1ba70
0xffffffac35e73b30 : 0xffffff8000e7c2cd
0xffffffac35e73c50 : 0xffffff8000e7ba86
0xffffffac35e73cb0 : 0xffffff8001715103
0xffffffac35e73da0 : 0xffffff8001629d31
0xffffffac35e73e00 : 0xffffff80016294f9
0xffffffac35e73e10 : 0xffffff80016438ae
0xffffffac35e73e50 : 0xffffff8001628338
0xffffffac35e73e70 : 0xffffff8000ecef75
0xffffffac35e73ee0 : 0xffffff8000ed0042
0xffffffac35e73fa0 : 0xffffff8000e1b19e
Process name corresponding to current thread (0xffffff8b93257aa0): kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
21G651
Kernel version:
Darwin Kernel Version 21.6.0: Thu Jun 8 23:57:12 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_X86_64
Kernel UUID: 0260200C-8B24-3AA3-AC23-7BD6AC6CF3E2
KernelCache slide: 0x0000000000c00000
KernelCache base: 0xffffff8000e00000
Kernel slide: 0x0000000000c10000
Kernel text base: 0xffffff8000e10000
__HIB text base: 0xffffff8000d00000
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: 8133398693660
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000765b45710f1
Sleep : 0x000007445c652f9d 0x000000007a62b7cc 0x0000073616b7e341
Wake : 0x000007445ea86b86 0x00000000786c1370 0x000007445d20c24c
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: 0xffffff805d47a000 - 0xffffffa05d47a000
. PGZ : 0xffffff805d47a000 - 0xffffff806047b000
. VM : 0xffffff806047b000 - 0xffffff852ca14000
. RO : 0xffffff852ca14000 - 0xffffff86c6147000
. GEN0 : 0xffffff86c6147000 - 0xffffff8b926e0000
. GEN1 : 0xffffff8b926e0000 - 0xffffff905ec79000
. GEN2 : 0xffffff905ec79000 - 0xffffff952b212000
. GEN3 : 0xffffff952b212000 - 0xffffff99f77ac000
. DATA : 0xffffff99f77ac000 - 0xffffffa05d47a000
Metadata: 0xffffffac5677d000 - 0xffffffac7677d000
Bitmaps : 0xffffffac7677d000 - 0xffffffac7f77d000
last started kext at 134089387286: @filesystems.smbfs 4.0 (addr 0xffffff7f9a331000, size 483328)
loaded kexts:
com.khronokernel.FeatureUnlock 1.1.5
as.vit9696.WhateverGreen 1.6.6
as.vit9696.Lilu 1.6.7
@filesystems.smbfs 4.0
>!ATopCaseHIDEventDriver 5450.8
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>AudioAUUC 1.70
>AGPM 129
@filesystems.autofs 3.0
>!AMikeyHIDDriver 131
@kext.AMDRadeonX4000 4.0.8
@kext.AMDRadeonServiceManager 4.0.8
>!AMikeyDriver 340.2
>!AHDAHardwareConfigDriver 340.2
>!AHDA 340.2
>!AGFXHDA 140.3
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>!ALPC 3.1
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHV 1
>!ADiskImages2 126.141.2
>!AFWOHCI 5.7.5
@kext.AMD9500!C 4.0.8
>!AFIVRDriver 4.1.0
>ACPI_SMC_PlatformPlugin 1.0.0
@UVCService 1
>!A!IMCEReporter 115
>!A!ISlowAdaptiveClocking 4.0.0
>!ARAID 5.1.0
>!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
>driverkit.serial 6.0.0
|IOSerial!F 11
>!AMultitouchDriver 5460.1
>!AInputDeviceSupport 5460.1
>!AHS!BDriver 5450.8
>IO!BHIDDriver 9.0.0
|IOAVB!F 1040.6
@plugin.IOgPTPPlugin 1040.3
|IOEthernetAVB!C 1.1.0
>!AHIDKeyboard 228.2
@kext.triggers 1.0
@kext.AMDRadeonX4000HWLibs 1.0
|IOAccelerator!F2 462.9
@kext.AMDRadeonX4000HWServices 4.0.8
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
>!UAudio 416.2
>!AAudioClockLibs 140.1
>!AHDA!C 340.2
|IOHDA!F 340.2
|IOAudio!F 340.2
@vecLib.kext 1.2.0
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.5.7
|IO!BSerialManager 9.0.0
|IO!BPacketLogger 9.0.0
|IO!BHost!CUSBTransport 9.0.0
|IO!BHost!CUARTTransport 9.0.0
|IO!BHost!CTransport 9.0.0
>IO!BHost!CPCIeTransport 9.0.0
|CSR!BHost!CUSBTransport 9.0.0
|Broadcom!BHost!CUSBTransport 9.0.0
|Broadcom!B20703USBTransport 9.0.0
>!AIPAppender 1.0
|IONDRVSupport 597
|IOFireWire!F 4.8.3
@kext.AMDSupport 4.0.8
>X86PlatformPlugin 1.0.0
>IOPlatformPluginLegacy 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@!AGPUWrangler 6.5.7
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
|IOSlowAdaptiveClocking!F 1.0.0
>!UHIDMouse 196
>!AHIDMouse 196
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!ABSDKextStarter 3
|IOSurface 302.15
@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
|IOAHCIBlock!S 333.140.2
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IOAHCISerialATAPI 270
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|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
Panicked task 0xffffff8b9270c670: 333 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff8b93257aa0, Frame : Return Address
0xffffffac35e73a30 : 0xffffff8000e7befd
0xffffffac35e73a80 : 0xffffff8000fdeb96
0xffffffac35e73ac0 : 0xffffff8000fcdf03
0xffffffac35e73b10 : 0xffffff8000e1ba70
0xffffffac35e73b30 : 0xffffff8000e7c2cd
0xffffffac35e73c50 : 0xffffff8000e7ba86
0xffffffac35e73cb0 : 0xffffff8001715103
0xffffffac35e73da0 : 0xffffff8001629d31
0xffffffac35e73e00 : 0xffffff80016294f9
0xffffffac35e73e10 : 0xffffff80016438ae
0xffffffac35e73e50 : 0xffffff8001628338
0xffffffac35e73e70 : 0xffffff8000ecef75
0xffffffac35e73ee0 : 0xffffff8000ed0042
0xffffffac35e73fa0 : 0xffffff8000e1b19e
Process name corresponding to current thread (0xffffff8b93257aa0): kernel_task
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev
Mac OS version:
21G651
Kernel version:
Darwin Kernel Version 21.6.0: Thu Jun 8 23:57:12 PDT 2023; root:xnu-8020.240.18.701.6~1/RELEASE_X86_64
Kernel UUID: 0260200C-8B24-3AA3-AC23-7BD6AC6CF3E2
KernelCache slide: 0x0000000000c00000
KernelCache base: 0xffffff8000e00000
Kernel slide: 0x0000000000c10000
Kernel text base: 0xffffff8000e10000
__HIB text base: 0xffffff8000d00000
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: 8133398693660
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000765b45710f1
Sleep : 0x000007445c652f9d 0x000000007a62b7cc 0x0000073616b7e341
Wake : 0x000007445ea86b86 0x00000000786c1370 0x000007445d20c24c
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: 0xffffff805d47a000 - 0xffffffa05d47a000
. PGZ : 0xffffff805d47a000 - 0xffffff806047b000
. VM : 0xffffff806047b000 - 0xffffff852ca14000
. RO : 0xffffff852ca14000 - 0xffffff86c6147000
. GEN0 : 0xffffff86c6147000 - 0xffffff8b926e0000
. GEN1 : 0xffffff8b926e0000 - 0xffffff905ec79000
. GEN2 : 0xffffff905ec79000 - 0xffffff952b212000
. GEN3 : 0xffffff952b212000 - 0xffffff99f77ac000
. DATA : 0xffffff99f77ac000 - 0xffffffa05d47a000
Metadata: 0xffffffac5677d000 - 0xffffffac7677d000
Bitmaps : 0xffffffac7677d000 - 0xffffffac7f77d000
last started kext at 134089387286: @filesystems.smbfs 4.0 (addr 0xffffff7f9a331000, size 483328)
loaded kexts:
com.khronokernel.FeatureUnlock 1.1.5
as.vit9696.WhateverGreen 1.6.6
as.vit9696.Lilu 1.6.7
@filesystems.smbfs 4.0
>!ATopCaseHIDEventDriver 5450.8
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>AudioAUUC 1.70
>AGPM 129
@filesystems.autofs 3.0
>!AMikeyHIDDriver 131
@kext.AMDRadeonX4000 4.0.8
@kext.AMDRadeonServiceManager 4.0.8
>!AMikeyDriver 340.2
>!AHDAHardwareConfigDriver 340.2
>!AHDA 340.2
>!AGFXHDA 140.3
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>!ALPC 3.1
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHV 1
>!ADiskImages2 126.141.2
>!AFWOHCI 5.7.5
@kext.AMD9500!C 4.0.8
>!AFIVRDriver 4.1.0
>ACPI_SMC_PlatformPlugin 1.0.0
@UVCService 1
>!A!IMCEReporter 115
>!A!ISlowAdaptiveClocking 4.0.0
>!ARAID 5.1.0
>!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
>driverkit.serial 6.0.0
|IOSerial!F 11
>!AMultitouchDriver 5460.1
>!AInputDeviceSupport 5460.1
>!AHS!BDriver 5450.8
>IO!BHIDDriver 9.0.0
|IOAVB!F 1040.6
@plugin.IOgPTPPlugin 1040.3
|IOEthernetAVB!C 1.1.0
>!AHIDKeyboard 228.2
@kext.triggers 1.0
@kext.AMDRadeonX4000HWLibs 1.0
|IOAccelerator!F2 462.9
@kext.AMDRadeonX4000HWServices 4.0.8
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
>!ASMBus!C 1.0.18d1
>!UAudio 416.2
>!AAudioClockLibs 140.1
>!AHDA!C 340.2
|IOHDA!F 340.2
|IOAudio!F 340.2
@vecLib.kext 1.2.0
>!ASMBusPCI 1.0.14d1
>!AGraphicsControl 6.5.7
|IO!BSerialManager 9.0.0
|IO!BPacketLogger 9.0.0
|IO!BHost!CUSBTransport 9.0.0
|IO!BHost!CUARTTransport 9.0.0
|IO!BHost!CTransport 9.0.0
>IO!BHost!CPCIeTransport 9.0.0
|CSR!BHost!CUSBTransport 9.0.0
|Broadcom!BHost!CUSBTransport 9.0.0
|Broadcom!B20703USBTransport 9.0.0
>!AIPAppender 1.0
|IONDRVSupport 597
|IOFireWire!F 4.8.3
@kext.AMDSupport 4.0.8
>X86PlatformPlugin 1.0.0
>IOPlatformPluginLegacy 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@!AGPUWrangler 6.5.7
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
|IOSlowAdaptiveClocking!F 1.0.0
>!UHIDMouse 196
>!AHIDMouse 196
>usb.IOUSBHostHIDDevice 1.2
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>usb.!UHub 1.2
>!ABSDKextStarter 3
|IOSurface 302.15
@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
|IOAHCIBlock!S 333.140.2
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
|IOAHCISerialATAPI 270
|IO80211!FLegacy 1200.12.2b1
|IOSkywalk!F 1.0
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|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
You'll get information that is more useful if you inject "keepsyms=1" into the boot string area of the config. See the "Alternative to device properties" section under "Complete your setup" in post #1.
That being said, the crash appears to happen while trying to set the power state of some device that appears as a SCSI device to the system - perhaps your SSD? Do your system preferences have the box checked that says put hard drives to sleep when idle (or something to that effect)? You might report back with the type of SSD and the interface it is on (SATA or NVME, if NVME is it via a passive card, or a switched card that gives you PCIe 3.0). Presumably when you run Mojave you are booting from a different SSD, and perhaps that other SSD handles the sleep request gracefully.
Booting the Recovery partition does not work after update to latest OpenCore 0.9.6 with macOS Monterey 12.7.1 on my mid 2012 Mac Pro 5.1.
I have a little custom config.plist based on Martin's Package, but Martin's Package 0.9.6 has same problem and show black screen before falling back to main screen (boot picker) when choosing Recovery partition.
OpenCore 0.9.5 has not this problem, and the recovery partition is all good, even deleted and rebuilt it to make sure.
Did you guys try to boot your Recovery partition with 0.9.6, any similar problems? @
Edit: I will try a build of 0.9.7 from the OpenCore build page when I get home, there is a mention of a '- Updated recovery_urls.txt' in the OpenCore Changelog for 0.9.7.
Edit II: I tried two builds of 0.9.7 and it did not solve my problem. I'm back to OC 0.9.5 were recovery mode from boot picker is working as it is supposed to.
I have a little custom config.plist based on Martin's Package, but Martin's Package 0.9.6 has same problem and show black screen before falling back to main screen (boot picker) when choosing Recovery partition.
OpenCore 0.9.5 has not this problem, and the recovery partition is all good, even deleted and rebuilt it to make sure.
Did you guys try to boot your Recovery partition with 0.9.6, any similar problems? @
h9826790?
Edit: I will try a build of 0.9.7 from the OpenCore build page when I get home, there is a mention of a '- Updated recovery_urls.txt' in the OpenCore Changelog for 0.9.7.
Edit II: I tried two builds of 0.9.7 and it did not solve my problem. I'm back to OC 0.9.5 were recovery mode from boot picker is working as it is supposed to.
Last edited:
This is a known bug in 0.9.6. There is a PR up to fix it.
Last edited:
You're right that the one thing that is different is the SSD I have the OC build on is different to the the disk my Mojave build is on. I did think of that but couldn't figure out a way to isolate that as a variable. The SSD is a Samsung 870 EVO in bay 1.
I stumbled across a thread on tonymacx86.com about Catalina shutdown panics where someone mentioned the OC flag "PowerTimeoutKernelPanic" in Kernel->Quirks. I tried setting that to true and haven't had any panics since. No idea what that flag is intended to do, but it seems to have fixed my problem. Touch wood.
I discovered a strange issue with my cMacPro... issue that I guess is related with OC upgrade (from 0.91 to 0.96) and/or macOS upgrade (from BigSur to latest Monterey), even I can't really figure how they are related with the issue. The issue happens with Skype, where I can't see video from remote cam. I did many tries, with more then one person, but with none I can see their video. I hear them, they hear and see me... I even see myself and they see them self as well. Using my MacBook Pro with same version of macOS and Skype, there are no problems.
I verified all Skype settings more than once, I reinstalled macOS twice (one time booting with BigSur, once form inside Monterey), I did a complete maintenance with Onyx, I uninstalled ad reinstalled Skype from scratch (deleting all components that AppCleaner could find).
I verified all Skype settings more than once, I reinstalled macOS twice (one time booting with BigSur, once form inside Monterey), I did a complete maintenance with Onyx, I uninstalled ad reinstalled Skype from scratch (deleting all components that AppCleaner could find).
I'm stuck. Downloaded OCLP patcher 1.2.1. Clean install of High Sierra, then Download OpenCore. Everything goes smooth as expected through the process, EFI build and all. Until I'm asked to reboot and hold down the (option) key I hear the chime and held down the option key for over 30 minutes and nothing, done three times and no boot?
Please help. I followed this process step by step from Mr. McIntosh and it's great step by step.
I'm using a NVMe PCI drive. Maybe that's why ?
Please help. I followed this process step by step from Mr. McIntosh and it's great step by step.
I'm using a NVMe PCI drive. Maybe that's why ?
Last edited:
Hi. Since my intention is to use method 2, can you tell me where you saw this?
As I did many tries to troubleshoot the issue, all unsuccessful, I'm wondering if this:
May be related to this:
But after patching my oversight by placing FirmwareFeatures and FirmwareFeaturesMask in the right place, I reinstalled macOS Monterey twice times, and I can't explain this strange problem. Btw, Skype works normally If I boot my cMP with BigSur, placed in an APFS container on the same SSD, with the same OC version and config file. But even Skype is the same version, and I controlled all Skype and SystemPreference settings, even they was imported from the same installation through Migration Assistant.
@basslik:
Have you read post #1 of this thread? You won't find much support for OCLP here. Post #1 will direct you to the relevant OCLP thread. Significantly, this current thread is titled "MANUALLY Configured OpenCore on the Mac Pro". That should tell you it isn't about OCLP, since OCLP is an AUTOMATED OpenCore installer.
Have you read post #1 of this thread? You won't find much support for OCLP here. Post #1 will direct you to the relevant OCLP thread. Significantly, this current thread is titled "MANUALLY Configured OpenCore on the Mac Pro". That should tell you it isn't about OCLP, since OCLP is an AUTOMATED OpenCore installer.
Before saying another word ... THANK YOU to all of you in the Hackintosh community and here who have made OpenCore a reality and have helped so many to use it. I just performed my first OC installation yesterday and had the pleasure of watching my 5,1 boot into Monterey with almost all of the basic bells and whistles. Again, THANK YOU!!
I wanted to reset my NVRAM but found that this no longer occurs by pressing Cmd-Opt-P-R. I have viewed quite a few posts and a number of videos and as far as I can tell:
• AllowNvramReset needs to be in the config file (It is not, AFAIK, in the guide's config file)
• ResetNVRAMEntry.efi needs to be in EFI > OC > Drivers.
• If HideAuxiliary is enabled in the config file, the space bar must be pressed in order to see the reset NVRAM option
• If LauncherOption is set to Full or Short then the OpenCore boot entry is protected.
• If RequestBootVarRouting is enabled in config, resetting NVRAM should not "unbless" the EFI volume.
• If the EFI is "unblessed" by an NVRAM reset, Ctrl-Clicking it in the bootpicker should "re-bless" it.
I haven't found a comprehensive treatment of this subject; these are bits and pieces I've gleaned from various postings, articles and videos and may be outdated or inaccurate. If AllowNvramReset needs to be in the config file, I have no idea where it should live. I'd like to know how to implement NVRAM resets with OpenCore installations, how to perform them and what to expect. Any advice would be greatly appreciated.
I wanted to reset my NVRAM but found that this no longer occurs by pressing Cmd-Opt-P-R. I have viewed quite a few posts and a number of videos and as far as I can tell:
• AllowNvramReset needs to be in the config file (It is not, AFAIK, in the guide's config file)
• ResetNVRAMEntry.efi needs to be in EFI > OC > Drivers.
• If HideAuxiliary is enabled in the config file, the space bar must be pressed in order to see the reset NVRAM option
• If LauncherOption is set to Full or Short then the OpenCore boot entry is protected.
• If RequestBootVarRouting is enabled in config, resetting NVRAM should not "unbless" the EFI volume.
• If the EFI is "unblessed" by an NVRAM reset, Ctrl-Clicking it in the bootpicker should "re-bless" it.
I haven't found a comprehensive treatment of this subject; these are bits and pieces I've gleaned from various postings, articles and videos and may be outdated or inaccurate. If AllowNvramReset needs to be in the config file, I have no idea where it should live. I'd like to know how to implement NVRAM resets with OpenCore installations, how to perform them and what to expect. Any advice would be greatly appreciated.
Last edited:
My own experimentation while developing the configuration strategies in post #1.
Regarding your issue with Skype: You could perhaps test your webcam in FaceTime or QuickTime to make sure that it’s working in Monterey (recall that USB 1.x devices are problematic in modern versions of macOS on the classic Mac Pro). You could also test with the browser version of Skype. Application permissions also come to mind. Good luck!
On a real Mac, regardless of OC, you should always be able to reset the NVRAM natively, either by holding Option-Command-P-R at startup, or by setting
sudo nvram ResetNVRam=1. While the key combination doesn’t work reliably on all keyboards (Apple wired keyboards seem to be the best), the NVRAM variable should always work.Resetting the NVRAM natively will also reset your boot selection, so OC will no longer be blessed, even with RequestBootVarRouting=true. However:
- With EnableGop, it’s possible to access the native boot picker, so it’s just a matter of pressing Control-Enter to rebless.
- If OC is installed on a disk that gets boot priority (this can be identified by experimentation), then OC will automatically start up again, and with LauncherOption=Full, it will automatically be reblessed.
- ResetNVRAMEntry will appear as an auxiliary boot entry. It also responds to Option-Command-P-R but only once OC starts.
- With LauncherOption=Full, resetting the NVRAM through OC keeps OC blessed. This may or may not be desired depending on what you want to achieve.
- ResetNVRAMEntry can optionally be configured with
--preserve-bootto force preservation of boot selection and--appleto preform a native reset with the NVRAM variable as described above.
Thanks, cdf; that's just what I needed! I penned that query because I could not seem to reset NVRAM using the key combination with a wired keyboard but I was in the middle of experimenting and there may have been other conditions I wasn't considering. I will explore these options. Again, many thanks!
My webcam seems to work properly, while I see my self, and even the others see me. What it won't work, is that I can't see other video (even I here them). With all other systems I tried, I didn't get this problem. Btw, the cam I'm using is a Microsoft LifeCam VX2000 and has USB2 connection.
But I'm realizing that after updating to Monterey, my cMacPro has other strange behaviors (besides the lack of Skype video), which I hadn't previously noticed. Between these:
- The Finder which randomly presents the following message (Finder is downloading a file from...):
- emails that do not automatically load remote contents;
- the trash can that takes an eternity to empty a few kB files (like an hour or more);
- even if I open trash, to display his content with 2-3 files, needs 10-15 seconds;
- GDrive which seems unable to synchronize files of a few kB...;
For the rest, the MacPro seems to work pretty well with Monterey.
Could these behaviors be an indication of a faulty macOS installation?
Last edited:
Maybe that's not the case... as time goes, the problems seem to increase. Among other things, I saw that Disk Utility reports a problem on the EFI partition from my nvme SSD (where I have OC and the two APFS containers with BigSur and Monterey), but I don't know if it's "normal" since there is OpenCore and Disk Utility doesn't recognize it.
However, I also saw that the Firmware was not entirely healthy (29K free bytes in VSS Store), but even after replacing it with the backup one (50K free bytes), things did not change.
Last edited:
As discussed several times in this thread, concurrent APFS installations have proven to be especially problematic (even on separate disks). The reason is that APFS is actually different in different versions of macOS.
I would recommend clean installations on separate disks with careful management using something like /etc/fstab to prevent different versions of APFS from affecting “incompatible” volumes.
Maybe this is the origin of all the problems I experiencing with my cMP, but I did the same on my MBP and haven't any issue.
At this point, I guess it should be the best solution. But just now, I'm still with cMP in boot loop after the first reboot with Monterey installer. I've previously backed up my EFI partition, cloned both containers on a mechanical hard drive, initialised the nvme SSD, copied back OC to EFI partition and blessed it.
But after the installer restarted cMP from nvme SSD, it appears Apple logo for few seconds and reboots again.
EDIT: After restarting the installer and initialising the nvme SSD from there (previously I initialised it with Mojave), Monterey installed successfully. Now I'm importing data from clone with Migration Assistant (hoping it won't import problems too...).
EDIT 2: most of the above strange behaviors seems to be gone after the re-installation of Monterey (alone on nvme SSD). But not the Skype issue (I can't see remote video... tried even with a new user), for which I don't understand if and how much it concerns OpenCore. The problem didn't occur with BigSur, but didn't occur with my MacBook Pro with Monterey either... could the problem be related to the lack of SSE2? Can anyone test if Skype works correctly on his cMP with Monterey?
In addition to that I have a new annoyance, namely the name of the Monterey volume, which I had named SSD980EVO during installation, and now, even after renaming it in Finder and with Disk Utility (for data), in the OpenCore Picker it appears with the name I initialised the drive. Does anyone know if there is a possibility of having this name updated or changed in some way?
EDIT 3: as some of the the above strange behaviors has returned (slow trash empty, problems with GDrive, ecc... ) i got the idea to try to put back an older MacPro's firmware, without GOP enabled... and bingo!!! After restarted the cMP with the original firmware, Skype is turned to work normally! And from the other strange behaviors I haven't signs until now... I don't want to speak too soon, but something is certainly changed (hope other strange behaviors are gone at all too!). I can't explain it, since I've been using the firmware with GOP for months (with BigSur), but since I installed Monterey it's the first time that Skype works as it should. Is there someone that uses Monterey with GOP modded firmware here?
Last edited:
Since I have received a lot of help from this forum, I want to give my small contribution by posting a bash script to put in the EFI partition next to the EFI folder. It helps speed up OpenCore bless, without the need to remember and write entry command. With this script in EFI partition, you need only to mount the partition and then call the script trough the command:
Maybe, you'll need to make it executable again before using it.
Code:
/Volume/EFI/blessme.shMaybe, you'll need to make it executable again before using it.
Last edited:
Seems you have a very messed up BootROM, your issue is not with EnableGop itself - everyone else using it would have the same issues - the most probable is that you injected it to a BootROM image with issues or even double injected it.
Original BootROM I used to inject EnableGop is the same that I saved as backup BootROM, and both have less more then 50k of free space in VSS. The firmware with EnableGop worked without issues as long I used BigSur (and OC 0.91).
Last edited:
You shouldn't ever post your BootROM image in the open, there are lot's of personal info inside…
Anyway, it's a cross-flashed early-2009 with base-19 hardware descriptor and BootBlock
AAPLEFI1.88Z.0005.I00.1010071430 that is extremely buggy, this alone explains some of your problems, but not the Skype one. Also, not double EnableGop injected.
Hi @borgo1971 - As @tsialex said on the EnableGop thread, it is very unlikely to be EnableGop. I believe lots of people are using it now, and no one else is reporting these problems.
Cloning disks is easy to get wrong :-/ sometimes a clean install is much easier to do.
And yes, with multiple macOS versions co-existing, a flaw in macOS makes different APFS versions compete with each other and cause nasty slow downs at least. The best bet is indeed to set up /etc/fstab to prevent the volumes of other macOS installs from auto-mounting (you can Google how to do this).
Cloning disks is easy to get wrong :-/ sometimes a clean install is much easier to do.
And yes, with multiple macOS versions co-existing, a flaw in macOS makes different APFS versions compete with each other and cause nasty slow downs at least. The best bet is indeed to set up /etc/fstab to prevent the volumes of other macOS installs from auto-mounting (you can Google how to do this).
OK, I assumed there was no personal data inside. At this point I removed it.
So, what do you suggest to do? I can try to patch again the BootROM I saved before inject EnableGop (and I'm using now, seems without any of the above issues), but I've not the skills to do much more.
I have upated my mac pro 5.1 to Ventura using ocl all good apert from bluetooth My apple keyboard is seen in the settings bluetooth whenI cick connect I get the 6 digit number that I enter on the apple keyboard and press enter, bluetooth settings shows connected but the keyboards greeen light keeps flashing and after a whie the light goes off and blutooth settings says not connected.
any help please ?
thanks
any help please ?
thanks