If you are using the XhciDxe.efi that comes with OC, an ExFat bootable drive won't appear in the OC Picker. For that to work you need an older version. See if the attached works for you. No guarantees.
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
I'm not using it, i only use ExFatDxeLegacy, in case something hapening to the Windows drive so i can reinstall from my backup.
I've a Fresco PCI-E with 1xUSB-C and 3xUSB3 ports, and i can't seem to view any connected Bootable USB while booting or in OpenCore picker.
My problem, is i've lost my last config settings from OC 0.7.9, now i'm on 0.8.3, and just fiew seconds ago, after trying your suggestion, and it completely freezed OC.
I was able to see the ExFat Windows USB, after disabling OpenLinux....efi from the config, but once i disconnected the drive from the USB 2 port and reconnected it just to know if it was correctly set up, ooops, not able to see it in the OC picker again.
Hello everyone.
I am having a problem with my Mac Pro 5,1 2010 - it won’t boot. It was working well, then just stopped. I am not a Mac expert and just followed recipes to upgrade it via OpenCore.
The original specs of the 5,1 (2010) BEFORE upgrading:
48Gb RAM
NVIDA GTX780
SSD boot drive with OSX 10.13.6
================
What I then did:
Exchanged the GTX 780 for an AMD Radeon 7950
Upgraded to 10.14.6
Then used Martin Lo OpenCore 0.8.0 and his online video to upgrade to OSX 11.6.8
Had a bad RAM chip (associated light on the backboard lit up and RAM info said 40Gb RAM instead of 48Gb) so I removed it and Installed 96 Gb RAM (4 x 8 and 4 x 16). All was well.
Then upgraded to OSX 12.3.1 and installed an AMD 6900XT from MacVidCards Europe powered by an external Corsair CS 750M PSU.
Everything worked perfectly and I was able to use the latest version of Blender and render on the AMD card (this was the goal of upgrading). YAY!
After a few days, the Mac Pro internal power supply suddenly started clicking and was rapidly turning off and on in about half a second intervals. I can tell it was turning off and on because the side light of the AMD GPU was flashing on and off in synch with the clicking. The Mac Pro was not bootable. I replaced the power supply with another used one and the clicking stopped but the Mac is still not bootable. Pressing the front ‘on’ button does nothing other than a ‘click’, which seems to be coming from the power supply. No power button front light comes on.
================
What I then tried:
Besides replacing the power supply - I have another Mac Pro 5,1 (2010) (Mac Pro B) running Martin Lo OpenCore 0.8.0, OSX 11.6.8 on an SSD and another GTX780. I put that SSD into the non-booting Mac Pro ‘A’ - and removed all other hard drives - still won’t boot.
Checked the battery - it’s good.
Unplugged for 1 minute and re-booted … nothing.
Pushed the DIAG button on the back-plane board - the 5V STBY LED turns amber.
Exchanged the RTX 6900XT for the old AMD Radeon 7950 … same. It clicks with the original power supply no matter the GPU and doesn’t click with the new power supply. But in either case the Mac Pro will not power on - no light at the front of the power button and if the AMD 6900XT is in, it does not light up with the new power supply.
Not sure what I can try next. Any help would be appreciated.
I am having a problem with my Mac Pro 5,1 2010 - it won’t boot. It was working well, then just stopped. I am not a Mac expert and just followed recipes to upgrade it via OpenCore.
The original specs of the 5,1 (2010) BEFORE upgrading:
48Gb RAM
NVIDA GTX780
SSD boot drive with OSX 10.13.6
================
What I then did:
Exchanged the GTX 780 for an AMD Radeon 7950
Upgraded to 10.14.6
Then used Martin Lo OpenCore 0.8.0 and his online video to upgrade to OSX 11.6.8
Had a bad RAM chip (associated light on the backboard lit up and RAM info said 40Gb RAM instead of 48Gb) so I removed it and Installed 96 Gb RAM (4 x 8 and 4 x 16). All was well.
Then upgraded to OSX 12.3.1 and installed an AMD 6900XT from MacVidCards Europe powered by an external Corsair CS 750M PSU.
Everything worked perfectly and I was able to use the latest version of Blender and render on the AMD card (this was the goal of upgrading). YAY!
After a few days, the Mac Pro internal power supply suddenly started clicking and was rapidly turning off and on in about half a second intervals. I can tell it was turning off and on because the side light of the AMD GPU was flashing on and off in synch with the clicking. The Mac Pro was not bootable. I replaced the power supply with another used one and the clicking stopped but the Mac is still not bootable. Pressing the front ‘on’ button does nothing other than a ‘click’, which seems to be coming from the power supply. No power button front light comes on.
================
What I then tried:
Besides replacing the power supply - I have another Mac Pro 5,1 (2010) (Mac Pro B) running Martin Lo OpenCore 0.8.0, OSX 11.6.8 on an SSD and another GTX780. I put that SSD into the non-booting Mac Pro ‘A’ - and removed all other hard drives - still won’t boot.
Checked the battery - it’s good.
Unplugged for 1 minute and re-booted … nothing.
Pushed the DIAG button on the back-plane board - the 5V STBY LED turns amber.
Exchanged the RTX 6900XT for the old AMD Radeon 7950 … same. It clicks with the original power supply no matter the GPU and doesn’t click with the new power supply. But in either case the Mac Pro will not power on - no light at the front of the power button and if the AMD 6900XT is in, it does not light up with the new power supply.
Not sure what I can try next. Any help would be appreciated.
Hi, from my experience, i had the same problem with two towers, one 2010 and the other 2009, the two had backplane issue. It first begin with powering on and off, suddenly stopped from working. You may unplug the power cable for a day, then plug it on and start your Mac, maybe it will power on, but if so, then after a minutes or hours or maximum a day you'll have the same problem, but this time, it will not power on anymore! This was the problem on my 2010! After the first symptoms, i left it for a day, then powered it on, and it does, then the next day, it stopped, then after that just powering on and off then suddenly off and no on anymore! They two had backplane issue!
The other thing i was suspecting are, the GPUS that are power hangry, you'll have to do the pixlas mod or another PSU like you did, this to keep the backplane a little bit with more life!
And i could be wrong, but this was my experience with My 4 Mac Pro towers that i had, with this current fifth, i'm taking care too much, i've pixlas mod and putted a X5675 that consumes less power than the X5695, and i only work with single processor tray hhhhh, just in case to reduce the costs of any damage to the board. For the 2009 that i had, i swapped two times the backplane, and two times the dual CPU tray, yes for only one Mac Pro, in a average of a year HHhH, yeah it was so ridiculous, but i had that ridiculous experience that took me to take a precious care of that machine, because it's not like normal PC's, doing extreme thing and they are still alive HHhH.
I would not expect adding or removing OpenLinuxBoot.efi to hide other entries (unless you were changing values concerning which filesystems to scan, at the same time).
I am running 12.5 and OC0.8.3. Has been pretty stable except for panic shutdowns have occurred twice while idle overnight. Panic report below.
Related to AppleFSCompressionTypeZlib? Saw threads about AVXpel replacing NoAVXFSCompressionTypeZlib.kext. Still the case? Any problem using both as a test?
Have also lost being able to unlock with Apple watch but all other BT functionality is there.
Thanks
Related to AppleFSCompressionTypeZlib? Saw threads about AVXpel replacing NoAVXFSCompressionTypeZlib.kext. Still the case? Any problem using both as a test?
panic(cpu 2 caller 0xffffff800ddd0773): Kernel trap at 0xffffff800f1e7090, type 6=invalid opcode, registers:
CR0: 0x0000000080010033, CR2: 0x0000000103ecd19a, CR3: 0x0000000194812164, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000000194, RCX: 0x0000000000000000, RDX: 0xffffffa072e30a14
RSP: 0xffffffe86e3f3520, RBP: 0xffffffe86e3f39e0, RSI: 0x0000000000000200, RDI: 0xffffffe86e3f3980
R8: 0xffffff9a16706008, R9: 0x0000000000000000, R10: 0x0000000000000702, R11: 0x0000000000000702
R12: 0xffffffa072e30a14, R13: 0x00000000000003f7, R14: 0xffffff9a16706008, R15: 0xffffffe86e3f3780
RFL: 0x0000000000010246, RIP: 0xffffff800f1e7090, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000103ecd19a, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0
Panicked task 0xffffff95455f69c0: 4 threads: pid 6090: mdworker_shared
Backtrace (CPU 2), panicked thread: 0xffffff9540ce4aa0, Frame : Return Address
0xffffffe86e3f2ed0 : 0xffffff800dc7fd6d
0xffffffe86e3f2f20 : 0xffffff800dde1016
0xffffffe86e3f2f60 : 0xffffff800ddd0383
0xffffffe86e3f2fb0 : 0xffffff800dc1fa70
0xffffffe86e3f2fd0 : 0xffffff800dc8013d
0xffffffe86e3f30f0 : 0xffffff800dc7f8f6
0xffffffe86e3f3150 : 0xffffff800e514d93
0xffffffe86e3f3240 : 0xffffff800ddd0773
0xffffffe86e3f33c0 : 0xffffff800ddd0456
0xffffffe86e3f3410 : 0xffffff800dc1fa70
0xffffffe86e3f3430 : 0xffffff800f1e7090
0xffffffe86e3f39e0 : 0xffffff800f1ea4c2
0xffffffe86e3f39f0 : 0xffffff800f1f2429
0xffffffe86e3f3ab0 : 0xffffff800f1f1b25
0xffffffe86e3f3b40 : 0xffffff800df753a2
0xffffffe86e3f3cc0 : 0xffffff8010f5e808
0xffffffe86e3f3d70 : 0xffffff800df4eb02
0xffffffe86e3f3df0 : 0xffffff800df4d870
0xffffffe86e3f3e50 : 0xffffff800e286882
0xffffffe86e3f3ee0 : 0xffffff800e286660
0xffffffe86e3f3f40 : 0xffffff800e38911b
0xffffffe86e3f3fa0 : 0xffffff800dc20236
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[0D0C8D80-A104-3C70-BBE8-C5E3F9EEE82C]@0xffffff8010f07000->0xffffff8011085fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[7201FB4A-CE2A-3EDA-92DE-053285346974]@0xffffff800f1b2000->0xffffff800f1bbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[53D12D3C-8326-3B2E-8FD6-204D97AEEF08]@0xffffff800f1c8000->0xffffff800f1cdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[752EFEA5-C07D-3246-AC42-A2C447402B68]@0xffffff800f6d3000->0xffffff800f6dafff
dependency: com.apple.iokit.IOStorageFamily(2.1)[24743B95-072D-31C4-A59D-7FF38502C0C4]@0xffffff8010978000->0xffffff801098efff
dependency: com.apple.kec.corecrypto(12.0)[864DE2A3-7343-32A3-AC76-68DF89128C87]@0xffffff80110bf000->0xffffff801113ffff
dependency: com.apple.security.AppleImage4(4.2.0)[EEFE7C11-D7D5-39E5-A778-4A107A0BDABA]@0xffffff800f24f000->0xffffff800f267fff
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0)[17ECF0E6-341A-3549-BC4D-CD00D0CFAB9F]@0xffffff800f1e5000->0xffffff800f1f6fff
Process name corresponding to current thread (0xffffff9540ce4aa0): mdworker_shared
Boot args: 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: E3E2CB4D-7B6F-39BB-8890-73C6FC513930
KernelCache slide: 0x000000000da00000
KernelCache base: 0xffffff800dc00000
Kernel slide: 0x000000000da10000
Kernel text base: 0xffffff800dc10000
__HIB text base: 0xffffff800db00000
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: 13906480574334
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000ca5dad5baf0
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000022f389e49e 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: 0xffffff8073078000 - 0xffffffa073078000
. PGZ : 0xffffff8073078000 - 0xffffff8079079000
. VM : 0xffffff8079079000 - 0xffffff8544edf000
. RO : 0xffffff8544edf000 - 0xffffff86de3ab000
. GEN0 : 0xffffff86de3ab000 - 0xffffff8baa211000
. GEN1 : 0xffffff8baa211000 - 0xffffff9076077000
. GEN2 : 0xffffff9076077000 - 0xffffff9541edd000
. GEN3 : 0xffffff9541edd000 - 0xffffff9a0dd44000
. DATA : 0xffffff9a0dd44000 - 0xffffffa073078000
Metadata: 0xffffff8041068000 - 0xffffff8061068000
Bitmaps : 0xffffff8061068000 - 0xffffff8073068000
last started kext at 129087240169: @filesystems.smbfs 4.0 (addr 0xffffff7fa7138000, size 483328)
loaded kexts:
io.macfuse.filesystems.macfuse 2112.20
com.AndreaElectronics.driver.SamsonUSBAudioPlugin 2.0.1
com.khronokernel.FeatureUnlock 1.0.9
as.vit9696.WhateverGreen 1.6.1
as.vit9696.Lilu 1.6.2
@filesystems.smbfs 4.0
>!ATopCaseHIDEventDriver 5450.8
>AGPM 129
>AudioAUUC 1.70
@filesystems.autofs 3.0
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
@UVCService 1
>!AHDAHardwareConfigDriver 340.2
>!AMikeyHIDDriver 131
>!AHDA 340.2
>!AMikeyDriver 340.2
@kext.AMDRadeonX4000 4.0.8
@kext.AMDRadeonServiceManager 4.0.8
>!AGFXHDA 140.3
>!ALPC 3.1
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>!AFWOHCI 5.7.5
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHV 1
>!ADiskImages2 126.141.2
@kext.AMD9500!C 4.0.8
>!AFIVRDriver 4.1.0
>!A!IMCEReporter 115
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!ISlowAdaptiveClocking 4.0.0
>!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
>!AHPET 1.8
>!ARTC 2.0.1
>!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
>!A!BHIDKeyboard 228.2
>!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
@kext.triggers 1.0
>!AHIDKeyboard 228.2
@kext.AMDRadeonX4000HWLibs 1.0
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
|IOAccelerator!F2 462.8
>!UAudio 416.2
>!AAudioClockLibs 140.1
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX4000HWServices 4.0.8
>!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
|IOFireWire!F 4.8.3
|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
@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
|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
CR0: 0x0000000080010033, CR2: 0x0000000103ecd19a, CR3: 0x0000000194812164, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x0000000000000194, RCX: 0x0000000000000000, RDX: 0xffffffa072e30a14
RSP: 0xffffffe86e3f3520, RBP: 0xffffffe86e3f39e0, RSI: 0x0000000000000200, RDI: 0xffffffe86e3f3980
R8: 0xffffff9a16706008, R9: 0x0000000000000000, R10: 0x0000000000000702, R11: 0x0000000000000702
R12: 0xffffffa072e30a14, R13: 0x00000000000003f7, R14: 0xffffff9a16706008, R15: 0xffffffe86e3f3780
RFL: 0x0000000000010246, RIP: 0xffffff800f1e7090, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000103ecd19a, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0
Panicked task 0xffffff95455f69c0: 4 threads: pid 6090: mdworker_shared
Backtrace (CPU 2), panicked thread: 0xffffff9540ce4aa0, Frame : Return Address
0xffffffe86e3f2ed0 : 0xffffff800dc7fd6d
0xffffffe86e3f2f20 : 0xffffff800dde1016
0xffffffe86e3f2f60 : 0xffffff800ddd0383
0xffffffe86e3f2fb0 : 0xffffff800dc1fa70
0xffffffe86e3f2fd0 : 0xffffff800dc8013d
0xffffffe86e3f30f0 : 0xffffff800dc7f8f6
0xffffffe86e3f3150 : 0xffffff800e514d93
0xffffffe86e3f3240 : 0xffffff800ddd0773
0xffffffe86e3f33c0 : 0xffffff800ddd0456
0xffffffe86e3f3410 : 0xffffff800dc1fa70
0xffffffe86e3f3430 : 0xffffff800f1e7090
0xffffffe86e3f39e0 : 0xffffff800f1ea4c2
0xffffffe86e3f39f0 : 0xffffff800f1f2429
0xffffffe86e3f3ab0 : 0xffffff800f1f1b25
0xffffffe86e3f3b40 : 0xffffff800df753a2
0xffffffe86e3f3cc0 : 0xffffff8010f5e808
0xffffffe86e3f3d70 : 0xffffff800df4eb02
0xffffffe86e3f3df0 : 0xffffff800df4d870
0xffffffe86e3f3e50 : 0xffffff800e286882
0xffffffe86e3f3ee0 : 0xffffff800e286660
0xffffffe86e3f3f40 : 0xffffff800e38911b
0xffffffe86e3f3fa0 : 0xffffff800dc20236
Kernel Extensions in backtrace:
com.apple.filesystems.apfs(1934.141.2)[0D0C8D80-A104-3C70-BBE8-C5E3F9EEE82C]@0xffffff8010f07000->0xffffff8011085fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[7201FB4A-CE2A-3EDA-92DE-053285346974]@0xffffff800f1b2000->0xffffff800f1bbfff
dependency: com.apple.driver.AppleEffaceableStorage(1.0)[53D12D3C-8326-3B2E-8FD6-204D97AEEF08]@0xffffff800f1c8000->0xffffff800f1cdfff
dependency: com.apple.iokit.CoreAnalyticsFamily(1)[752EFEA5-C07D-3246-AC42-A2C447402B68]@0xffffff800f6d3000->0xffffff800f6dafff
dependency: com.apple.iokit.IOStorageFamily(2.1)[24743B95-072D-31C4-A59D-7FF38502C0C4]@0xffffff8010978000->0xffffff801098efff
dependency: com.apple.kec.corecrypto(12.0)[864DE2A3-7343-32A3-AC76-68DF89128C87]@0xffffff80110bf000->0xffffff801113ffff
dependency: com.apple.security.AppleImage4(4.2.0)[EEFE7C11-D7D5-39E5-A778-4A107A0BDABA]@0xffffff800f24f000->0xffffff800f267fff
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib(1.0)[17ECF0E6-341A-3549-BC4D-CD00D0CFAB9F]@0xffffff800f1e5000->0xffffff800f1f6fff
Process name corresponding to current thread (0xffffff9540ce4aa0): mdworker_shared
Boot args: 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: E3E2CB4D-7B6F-39BB-8890-73C6FC513930
KernelCache slide: 0x000000000da00000
KernelCache base: 0xffffff800dc00000
Kernel slide: 0x000000000da10000
Kernel text base: 0xffffff800dc10000
__HIB text base: 0xffffff800db00000
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: 13906480574334
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000ca5dad5baf0
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x00000022f389e49e 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: 0xffffff8073078000 - 0xffffffa073078000
. PGZ : 0xffffff8073078000 - 0xffffff8079079000
. VM : 0xffffff8079079000 - 0xffffff8544edf000
. RO : 0xffffff8544edf000 - 0xffffff86de3ab000
. GEN0 : 0xffffff86de3ab000 - 0xffffff8baa211000
. GEN1 : 0xffffff8baa211000 - 0xffffff9076077000
. GEN2 : 0xffffff9076077000 - 0xffffff9541edd000
. GEN3 : 0xffffff9541edd000 - 0xffffff9a0dd44000
. DATA : 0xffffff9a0dd44000 - 0xffffffa073078000
Metadata: 0xffffff8041068000 - 0xffffff8061068000
Bitmaps : 0xffffff8061068000 - 0xffffff8073068000
last started kext at 129087240169: @filesystems.smbfs 4.0 (addr 0xffffff7fa7138000, size 483328)
loaded kexts:
io.macfuse.filesystems.macfuse 2112.20
com.AndreaElectronics.driver.SamsonUSBAudioPlugin 2.0.1
com.khronokernel.FeatureUnlock 1.0.9
as.vit9696.WhateverGreen 1.6.1
as.vit9696.Lilu 1.6.2
@filesystems.smbfs 4.0
>!ATopCaseHIDEventDriver 5450.8
>AGPM 129
>AudioAUUC 1.70
@filesystems.autofs 3.0
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
@UVCService 1
>!AHDAHardwareConfigDriver 340.2
>!AMikeyHIDDriver 131
>!AHDA 340.2
>!AMikeyDriver 340.2
@kext.AMDRadeonX4000 4.0.8
@kext.AMDRadeonServiceManager 4.0.8
>!AGFXHDA 140.3
>!ALPC 3.1
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>!AFWOHCI 5.7.5
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!AHV 1
>!ADiskImages2 126.141.2
@kext.AMD9500!C 4.0.8
>!AFIVRDriver 4.1.0
>!A!IMCEReporter 115
>ACPI_SMC_PlatformPlugin 1.0.0
>!A!ISlowAdaptiveClocking 4.0.0
>!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
>!AHPET 1.8
>!ARTC 2.0.1
>!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
>!A!BHIDKeyboard 228.2
>!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
@kext.triggers 1.0
>!AHIDKeyboard 228.2
@kext.AMDRadeonX4000HWLibs 1.0
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
|IOAccelerator!F2 462.8
>!UAudio 416.2
>!AAudioClockLibs 140.1
>!ASMBus!C 1.0.18d1
@kext.AMDRadeonX4000HWServices 4.0.8
>!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
|IOFireWire!F 4.8.3
|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
@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
|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
Have also lost being able to unlock with Apple watch but all other BT functionality is there.
Thanks
looks like panic due to mdworker- the part of disk indexing, check what you use - syncretic patch?
check MaxKernel value has to be changed to 21.6.0 in order for it to work
sometimes is useful to disable SIRI
also check that you add to drivers (<key>Drivers</key>)
.....
<key>LoadEarly</key>
<false/>
my experience:
or try to use no_AVX kext instead
or my experience with shrunked NVME ssd
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.0, mac os 12.5
Last edited:
Weeks ago I had three or four panics. Someone suggested they were caused precisely for having AppleFSCompressionTypeZlib alongside AVXpel. I got rid of AppleFSCompressionTypeZlib. There haven't been any issues ever since.
I did have the older setting in AVXpel of MaxKernel 21.5.0. I usually do a full walk through of the post #1 steps but this last time OC.0.8.2 --> OC0.8.3 I did the maintenance route. Such changes aren't documented there. I will go back to full walk throughs. Gives me a chance to check settings.
I changed the AVXpel MaxKernel setting so we will see what happens. I do have a shrunk NVMe to fix the extremely long startup due to trim but will only change the one thing for now.
Does MaxKernel need to be updated elsewhere? I notice that the MaxKernel is blank for many kext and for ASPP-override it is 21.4.0
Hi Ammoune78, thanks very much for taking the time to reply. I appreciate it.
So - this is indirectly an OpenCore problem in that OpenCore allows harware modification that might stress the Mac Pro to levels beyond what it can handle well. I added the external PSU for that very reason - thinking it might be better to power the 6900XT in that manner since I was going to use the modded Mac Pro for Blender ... and while rendering, Blender will definitely max the GPU and draw watts.
I have a CPU tray that has Dual X5690 6 Cores @ 3.46Ghz with turbo boost to 3.73Ghz ... so that could also be part of the problem, though the Mac Pro worked for years with this CPU and only gave me trouble after I upgraded the OS from 10.14 to 12.3.1 via OpenCore and then added the 6900XT to use for 3D rendering.
I'll try another backpane board, but if it eventually does the same thing, then I'll know this combination is just too much for the Mac Pro 'frame'.
Thanks again for your reply.
Theres no such added stress. Mac Pro can handle what can handle. There is no more. Boards fail from time time. In more than ten years, just once happened to me.
1. there are 6 times replacement in syncretic patch
You can use parameters compatible with all future MacOS versions:
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.5.0</string>
OR CHECK other possible parameters in @cdf post - this parameter is for 12.5 only:
<key>MaxKernel</key>
<string>21.6.0</string>
<key>MinKernel</key>
<string>21.5.0</string>
2. I'm not sure about ASPP-Override , but with 21.4.0 my archicad hung for a few seconds before loading, I changed the parameter to 21.6.0 and in a strange way the loading became correct
3. in new versions OC problem of long boot for some kind SSD resolved (or you can set trim timeout to max - as you need)
as i found 12.5 didn't work correctly with shrunked NVME ssd
i use "sudo diskutil apfs resizeContainer disk2s2 0" - where you need replace disc name to correct one
what happens when apple mds process tries to do indexing on a shrunked ssd i described in my post
My CMP 4.1/5.1 dual cpu xeon 5680, 96gb RAM, radeonpro w5700, nvme crucial 2tb, evo plus 1tb, TB3 alpine ridge, oc 0.8.3, mac os 12.5
Great thank you, it helped me a lot, because i was having some things not needed.
For sure, it was other entries that let it to work, but i know that my OC folder was a little bit buggy.
==============================================================
Is there guys anyway to use my custom Background.icns? Wherever i put it, i got Internal OC BootPicker with blackscreen and labels like terminal
Trifero: Thanks for the message and the reassurance.
3D rendering is tough on computers. A render can take from minutes to days and all the while, the GPU is loaded and calculating at maximum capacity (Blender has an option to use the GPU, or the CPU or the CPU+GPU for rendering. I use only the GPU for rendering to avoid stressing the CPU). Most Mac Pro users are probably not stressing their computer to the same extent. Whether by bad luck or simply stressing an old computer, since I upgraded to OpenCore and put the 6900XT in, I have had a bad 8 Gb RAM stick, a failed power supply and now a failed backpane board; that is actually most of the computer failing in some manner; other than the CPU.
So far my Mac Pro / OpenCore experience has been the opposite of yours. But it is still early for me as I have made these upgrades in the past month and I have my fingers crossed you are right!
You can't blame a boot loading software for hardware issues. OC is simply a boot loader operating only during the boot process. It s the same as to blame A gun for killing people. Without a person holding that gun it will not kill a single person.
Yes of course - no blame applied. Without emotion, I am pondering the ramifications of furthering a system via software that allows powerful hardware far beyond what was intended. All of these modifications are running on original hardware. And on top of this I am using a software program that pushes the whole system.
Your analogy is not very apt though, because I am musing about the fragility of a system in terms of old and new. An extreme analogy would be more akin to putting a 500 horsepower V8 (6900XT and Blender 3D software) into a slightly modified Model T Ford (Mac Pro with OpenCore) and hoping the frame (unmodified hardware) is not going to bend or break when you push the accelerator to the floor.
I have been using OpenCore for a couple years no problem, as have many here. I use software that regularly pushes the whole system. If your PSU was about ready to give up the ghost, that was going to happen with or without OpenCore involved.
I find it extremely unlikely that OpenCore enabled blender to fry your computer. Barking up the wrong tree on that one. Pushing on the accelerator did not fry your computer.
Sorry to hear you are having problems, but I would recommend you get to the bottom of your hardware issues and then also try to get more informed about how to setup your computer for OpenCore...instead of relying on something "automatic" like MartinLo's one-size-fits-all open core installer.
I would also recommend you get in touch with @tsialex to have a look at your ROM, to get a backup of your ROM, which you should have done before attempting to install OpenCore...and even better get a never-booted rom image from Alex..
The one area where we need to be careful with OpenCore is related to our ROM and NVRAM, as the NVRAM size is very small compared to modern PC and modern MacOS and especially modern Windows, makes a lot of use of NVRAM... it can easily fill it up and even cause a certain design flaw to fill up the NVRAM in a way that could be problematic. That could actually happen without OpenCore also, but anyway, I don't know what your OpenCore configuration looked like, its certainly possibly you did something there, which is what people are referring to when they talk about your "back plane". That is not about Blender frying anything...
Dewdman42
Thanks for your reply. I appreciate your helpful explanations and the time you took to explain.
Since you and a few others have now mentioned the combination of Bender and a maxed 6900XT would not fry a Mac Pro, this is actually quite heartening to know.
I had not realized Martin Lo’s OpenCore installer is a ‘one size fits all’ solution. I chose it because it is supposedly specific for the Mac Pro 5,1 … but I think what you are saying is, it’s better to be more careful and use a custom install that is geared for the specific end use … though at this point, I have no idea what that entails or should be like for my intended Mac Pro use.
I am not sure how to get to the ROM of anything because the Mac Pro will not boot. With a new (used) PSU, it makes a single click sound when the front button power is pressed. The power button does not light up and nothing happens, though the 5V standby LED on the back pane does light amber when the Diag button is pressed.
I have a vague recollection after installing OpenCore and Monterey 12.3.1, the boot ROM version was something like 9144.0.0.x.0. I cannot remember the exact location or number of the ‘x’ but it was definitely a numeral … maybe a ‘3’ or an ‘8’ and the location was either where I put the ‘x’ or one position to the left.
Thanks again for the suggestions and info.
Your boot rom version Reading that number is simply caused by open core. Mac pros never get a firmware with that number, but when macOS boots with open core that numeral version appears. That’s normal
William 4673,
Thanks for the info. So ... I guess that boot ROM version being displayed is an indentifier for OpenCore.
Dewdman42,
Yes - my Mac Pro is slowly changing from silver to a kinda brick red colour.
So - you mentioned backpane issues and I am assuming that is were the ROM chips reside. A few days ago I bought a used back pane with the same identifier number along the bottom lower corner as my ailing Mac Pro. Still in transit at this point.
I've been following the guide for my MacPro5,1 but there are a couple of things that aren't clear.
If these questions are already addressed elsewhere, please just point me there. (There's so much about OpenCore in MacRumors, and spread out so far, that finding the right search incantation is difficult.)
- To make PCIe drives appear as internal, the guide says:
My two paths are:
PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)
PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)
At face value, the guide seems to mean that I should have this:
Followed by the final </dict> (the one that isn't one of the seven lines to copy).
But two keys both named built-in looks wrong. If I keep it unaltered and then open config.plist with ProperTree, the second one doesn't show up, as I'd expect for what appears to be improper XML. If I try to enter another built-in in ProperTree, it renames it to something like built-in 2.
But two keys both named built-in looks wrong. If I keep it unaltered and then open config.plist with ProperTree, the second one doesn't show up, as I'd expect for what appears to be improper XML. If I try to enter another built-in in ProperTree, it renames it to something like built-in 2.
- The config.plist referred to in the guide has DirectGOPRendering enabled, though the guide says it should usually be disabled except in cases where there's a specific reason to enable it. For my flashed AMD Radeon R9 280x with 3 GB, is there any documented reason that I should not disable it?
What you have is correct. Each device has its own built-in property. Here's what your entire DeviceProperties dictionary should look like (excluding any graphics card properties that you may have added):
XML:
<key>DeviceProperties</key>
<dict>
<key>Add</key>
<dict>
<key>PciRoot(0x0)/Pci(0x7,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>
AA==
</data>
</dict>
<key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x2,0x0)/Pci(0x0,0x0)</key>
<dict>
<key>built-in</key>
<data>
AA==
</data>
</dict>
</dict>
<key>Delete</key>
<dict/>
</dict>This setting is included in the sample config because having it is fine for all cards (although not ideal), whereas not having it can break pre-boot video for cards that really need it. You can probably disable it for your card. In any case, if you lose pre-boot video, you can just re-enable the setting.
Hope this helps!
Last edited: