Sidebar Sidebar
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

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
hwojtek said:
Same card with different branding here.
Which slot did you put it in? What ssds do you use?
I had to move the card from slot #2 to #3 because of the RX 6800XT I installed, however previously, when in slot #2 in synthetic benchmarks my Adata SX8200 Pros were as close to ~3000 as the rest of the hardware permits.
In slot #3 I get around half that, which is fully expected.
View attachment 2225715

I was obviously disappointed I had to move the drives to a slower slot, tried using a ribbon breakout cable which proved fairly useless, however the speed difference actually makes zero impact on daily use and is perfectly unnoticeable.
Click to expand...

Over the past 2 months I invoked every troubleshooting step I could think of. Removed all PCIe add-on cards, SATA drives in bays 2-4, external USB accessories and peripherals, optical audio, leaving only a graphics card and PCIe card with SSDs. Switched those two cards between slots 1 and 2 multiple times, NVRAM reset, updated the OC configuration, result was no change--read/write speeds on NVMes maxed at 1400MB/s. Next, I poured over my OC config.plist to see that there were no extraneous things installed or enabled; tried booting without installing NVMeFixUP; skipped FeaturesUnlock; etc. Last week I removed everything again, reseated the graphics card, put a blank SATA SSD in Bay 1, and via USB installer, I installed OC 9.1 to EFI of the SATA SSD/ Bay 1 and a clean install of Monterey 12.6.7 on the SATA drive. Next, installed 1 NVME on IOCrest PCIe card, as a storage-only, HFS+ volume, and inserted in slot 2. NVRAM reset. PCIe and NVME recognized, no change. Updated OC configuration to include card, no change. Re-installed 2nd NVME blade, with 12.6.7 as boot volume. Updated OC configuration, no change. Even tried reverting the blades to external drives, as they were under Mojave, but no change. Installed PCIUtilites to confirm PCI IDs of the blades and ASMedia chip, and PCI Tree.

So I'm fascinated that you got full read/write function on your SSD with no special action taken, before upgrading to the RX 6800 XT. And I find it odd that I can find no mention of these PCIe switch cards either working or failing to work with OC. (Here, Reddit, Discord, Facebook.)

I have RX 5600 XT. I opted for a dual slot card so I could maintain use of slot 2. SK Hynix Gold P31 1TB SSD NVME. Samsung 970 EVO 500GB SSD NVME. Under Mojave, I used the Hynix as a boot drive; erased and used as storage volume/scratch disk. Full 3000+MB/s read/write speeds in both cases. I did the same with the 970 EVO, for a while as scratch disk, then as boot volume. Under Monterey with OC, I've installed one blade only, set it as a scratch disk, also tried both installed as storage volumes, no OS. And currently using 970 EVO as my boot volume, with OC installed on EFI of SATA HDD in Bay 1. Read/write maxes at 1400MB/s in every case with Monterey + OC.

Actually, under Big Sur (which I otherwise really liked--stable and then some) the problem was the same. No real function of the PCIe switch. I had hoped the issue would get sorted in Monterey.

Edit (9 July 23)
I heard back from a developer who said OC has no plans to address this issue, so apparently no one using Open Core has PCIe switch enabled on these smart cards.
 
Last edited:
Trying Monterey, and I can get everything going and seemingly working perfectly, but graphics acceleration is not working on my photo editors. It’s an RX 480, and it passes as Metal compliant, and the OS appears to use the GPU for everyday GUI functions (like scrolling). However, things like DXOPureRAW won’t engage the GPU at all and take ages to complete in CPU-only mode. Is it just that RX480 is too old for Monterey? I have the issue whether I make my own OC or use OCLP. Kicker is, the same OC setup has these GPU functions working just fine with Catalina and Big Sur. Ironically, if I stick with Big Sur, Safari will keep it from entering sleep, so I’m stuck on Catalina. Is it just my GPU being too old? I don’t want to upgrade it if it doesn’t solve anything.
 
Hi. I'm here because it's a nasty day for me. Something went wrong on my 2009 (5,1) MacPro. All started when I installed Parallels Desktop that tried to make a VM using my Windows SSD (that previously booted windows through OpenCore). Parallels simply braked it... after Parallels filed try, Windows wasn't able to boot anymore. This about two mounts ago... In the meantime, I discovered that trying to get OpenCore version through nvram command caused “nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found”. This didn't happen when I installed OpenCore 0.8.3. In any case, Mac booted normally in macOS 11.7.8 (updated the last two times OTA without the need to enable VMM flag).

Two days ago I decided to give a look and try to repair both… first of all OpenCore nvram variable and Windows boot too.

I booted in my Mojave partition (on another disk) and configured OpenCore to load ExFAT as described in first page (I guess I removed it last time I upgraded OpenCore, but I’m pretty sure that windows booted anyway) and tried to boot form Windows installer on USB flash. None… The Mac didn’t see it at all. I made more than one try, with other flash memory and Windows versions too (even the first one booted my MacBook Pro without problems.

Every time I mounted (with diskutil) and blessed my EFI volume to boot back in BigSur and do some work.

Today, I booted again in Mojave, but I get a strange message that said theres an incompatible disk… I thought it meant USB, but didn’t… It meant my EFI volume. I got confirmation trying to mount it, that gave me a massage that volume was unreadable. So I tried SOS from Disk Utility, until command line repair from Recovery. I reset PRAM, I flashed a previously backed up ROM (February 2022… before I upgraded to BigSur, with about 50K free space in EFISystemNvDataFvGUID) to the Mac too. But nothing to do, I’m unable to mount EFI partition again. Not form normal booted Mojave, and not from Mojave Recovery.

But while I was writing this message, I got even the idea to try to mount the EFI volume from Mojave drive… and form a third drive too, and got the same “Volume on disk… failed to mount” message! So what could cause all this?! What kind of troubleshoot should I perform? How can I recover my MacPro?!

Edit: I was able to mount EFI in Mojave trough EFI mounter (even if diskutil continues to say it can't), so I could backup EFI to external drive (BigSur partition is still cloned daily to a mechanical drive), and after reboot in Mojave recovery, I was able to mount EFI with diskutil, and still bless it and reboot in BigSur through OpenCore. But most problems are even here: from BigSur I'm still unable to mount EFI partition through diskutil (EFI Mounter seems to do the job without issues), and nvram command continues to give me the "data was not found" message instead of OpenCore version.
 
Last edited:
Upgraded to Monterey a couple of days ago. All going fine apart from two panics, both times while the machine was idle.

panic(cpu 0 caller 0xffffff8019629d31): IOSCSIPeripheralDeviceType05::setPowerState(0xffffff9cb967c2e0 : 0xffffff801ba81aea, 1 -> 4) timed out after 100738 ms @IOServicePM.cpp:5524
Panicked task 0xffffff97ed500670: 284 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff97eec12000, Frame : Return Address
0xffffffffff36ba30 : 0xffffff8018e7befd
0xffffffffff36ba80 : 0xffffff8018fdeb96
0xffffffffff36bac0 : 0xffffff8018fcdf03
0xffffffffff36bb10 : 0xffffff8018e1ba70
0xffffffffff36bb30 : 0xffffff8018e7c2cd
0xffffffffff36bc50 : 0xffffff8018e7ba86
0xffffffffff36bcb0 : 0xffffff8019715103
0xffffffffff36bda0 : 0xffffff8019629d31
0xffffffffff36be00 : 0xffffff80196294f9
0xffffffffff36be10 : 0xffffff80196438ae
0xffffffffff36be50 : 0xffffff8019628338
0xffffffffff36be70 : 0xffffff8018ecef75
0xffffffffff36bee0 : 0xffffff8018ed0042
0xffffffffff36bfa0 : 0xffffff8018e1b19e

Process name corresponding to current thread (0xffffff97eec12000): kernel_task
Boot args: -no_compat_check

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: 0x0000000018c00000
KernelCache base: 0xffffff8018e00000
Kernel slide: 0x0000000018c10000
Kernel text base: 0xffffff8018e10000
__HIB text base: 0xffffff8018d00000
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: 11183016416840
Last Sleep: absolute base_tsc base_nano
Uptime : 0x00000a2bbfb89fd6
Sleep : 0x00000913cb54ba66 0x0000000077f4e0bc 0x0000090fc6341e4f
Wake : 0x00000913cd9f2996 0x0000000077db4e64 0x00000913cc17b217
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: 0xffffff8cb8266000 - 0xffffffacb8266000
. PGZ : 0xffffff8cb8266000 - 0xffffff8cbb267000
. VM : 0xffffff8cbb267000 - 0xffffff9187800000
. RO : 0xffffff9187800000 - 0xffffff9320f33000
. GEN0 : 0xffffff9320f33000 - 0xffffff97ed4cc000
. GEN1 : 0xffffff97ed4cc000 - 0xffffff9cb9a65000
. GEN2 : 0xffffff9cb9a65000 - 0xffffffa185ffe000
. GEN3 : 0xffffffa185ffe000 - 0xffffffa652598000
. DATA : 0xffffffa652598000 - 0xffffffacb8266000
Metadata: 0xffffff8c8f256000 - 0xffffff8caf256000
Bitmaps : 0xffffff8caf256000 - 0xffffff8cb8256000

last started kext at 23596383820: >driverkit.serial 6.0.0 (addr 0xffffff7fb20ae000, size 28672)
last stopped kext at 776006292120: >X86PlatformPlugin 1.0.0 (addr 0xffffff7fb1fba000, size 77824)
loaded kexts:
com.khronokernel.FeatureUnlock 1.1.5
as.vit9696.WhateverGreen 1.6.5
as.vit9696.Lilu 1.6.6
>!A!BMultitouch 100
>AudioAUUC 1.70
>PioneerSuperDrive 533.120.2
>Oxford_Semi 533.120.2
>!AUpstreamUserClient 3.6.9
>!AMCCSControl 1.16
@kext.AMDFramebuffer 4.0.8
>AGPM 129
@filesystems.autofs 3.0
@kext.AMDRadeonX4000 4.0.8
>!AMikeyHIDDriver 131
>!AHDA 340.2
>!AMikeyDriver 340.2
@kext.AMDRadeonServiceManager 4.0.8
>!AGraphicsDevicePolicy 6.5.7
@AGDCPluginDisplayMetrics 6.5.7
>pmtelemetry 1
|IOUserEthernet 1.0.1
>usb.!UUserHCI 1
>!ALPC 3.1
>!AFWOHCI 5.7.5
>!AHV 1
>!ADiskImages2 126.141.2
>!A!ISlowAdaptiveClocking 4.0.0
>!A!IMCEReporter 115
>ACPI_SMC_PlatformPlugin 1.0.0
@kext.AMD7000!C 4.0.8
>!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
>AirPort.BrcmNIC 1400.1.1
>!I82574LEthernet 2.7.2
>!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
>IO!BHIDDriver 9.0.0
>!AMultitouchDriver 5460.1
>!AInputDeviceSupport 5460.1
|IOAVB!F 1040.6
@plugin.IOgPTPPlugin 1040.3
|IOEthernetAVB!C 1.1.0
|IOFireWireSerialBusProtocolTransport 2.5.1
|IOFireWireSBP2 4.4.3
>!AHIDKeyboard 228.2
@kext.AMDRadeonX4030HWLibs 1.0
@kext.triggers 1.0
|IOAccelerator!F2 462.9
@kext.AMDRadeonX4000HWServices 4.0.8
>DspFuncLib 340.2
@kext.OSvKernDSPLib 529
>!AAudioClockLibs 140.1
|IONDRVSupport 597
>!ASMBus!C 1.0.18d1
>!AHDA!C 340.2
|IOHDA!F 340.2
|IOAudio!F 340.2
@vecLib.kext 1.2.0
>!AGraphicsControl 6.5.7
>!ASMBusPCI 1.0.14d1
|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
|IOFireWire!F 4.8.3
>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
@!AGPUWrangler 6.5.7
|IOSlowAdaptiveClocking!F 1.0.0
>IOPlatformPluginLegacy 1.0.0
>IOPlatformPlugin!F 6.0.0d8
@kext.AMDSupport 4.0.8
@!AGraphicsDeviceControl 6.5.7
|IOGraphics!F 597
>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
|IOAHCISerialATAPI 270
|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
|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

I have the AVXpel patch configured - pre-emptively rather than due to necessity. Any pointers to what is causing the panic would be appreciated.
 
Solved most problems... but I can't see windows USB installer in OpenCore. The installer boots without problems my 2014 MacBook Pro.
 
Last edited:
Ivan Shpak said:
The question is, can I make the Snow Leopard (10.6.8) boot in 32-bit mode in the OpenCore settings?
Click to expand...
I think you'll be better with a Virtual Machine. Snow Leopard is pretty light and fast to run in VM. Officially you'l need a SL server, but there's a trick to spoof SnowLeopard Client installer in Server version
 
borgo1971 said:
Solved most problems... but I can't see windows USB installer in OpenCore. The installer boots without problems my 2014 MacBook Pro.
Click to expand...
I discovered that the problem was the USB stick I was using (Transcend JetFlash 16GB) and instead with a bulk 8GB stick everything seems to work. I have already installed Windows 10, but I saw that now I can also boot with Windows 11. Can someone tell me how Windows 11 works on the MacPro? Is it worth trying to install it, or is it just trouble?
 
Last edited:
Just updated macos to 12.6.8
but despite the fact that a week ago I flashed system ROM by recreated BootROM image ( made by tsialex)
I again could not update using method 2
macos installer rebooted the computer without completing the installation procedure (and the macos installer option remained available in the opencore bootpicker)
I experimented - disconnected all ssd and hdd, except for the system one - the installer did not want to complete the installation
then I changed the config to Martin's config - it can be considered as method 1 - the installer also did not work - it means that the installer on my cMP when downloading the update using method 2 apparently is corrupted or incomplete
I had to repeat the procedure for downloading the update according to method 1
in this case the update was successful
starting from 12.6.7 and into 12.6.8 disk indexing by mds processes is much faster on my computer than before.
EDITED
i double checked and found, that there was wrong argument in firmwareFeatures in my config (I missed 2 symbols the first "A" and the last "=" during copy/paste)
but even in this case, I don’t understand why I couldn’t update from the installed installer if I replaced the config during the installation process
does this mean that the installer got corrupted due to an invalid argument in firmwareFeatures?
 
Last edited:
12.6.8 worked fine for me using the "second" method - SecureBootModel set to default, Hybridization, and Firmware Features updated on my 2010 cMP5,1.
 
The update to 12.6.8 was flawless. In addition, it was amazingly fast for me. I've recently installed, at long last, a 4TB NVMe M2 blade on a PCI card. It almost looks like a new computer. If only we got a new BootROM capable of adding AVX/AVX2 instructions, the cMP could then have a new lease on life.
 
  • Like
Reactions: Gustav Holdoff
Gustav Holdoff said:
it means that the installer on my cMP when downloading the update using method 2 apparently is corrupted or incomplete
Click to expand...
EDITED
i double checked and found, that there was wrong argument in firmwareFeatures in my config (I missed 2 symbols the first "A" and the last "=" during copy/paste)
but even in this case, I don’t understand why I couldn’t update from the installed installer if I replaced the config during the installation process
does this mean that the installer got corrupted due to an invalid argument in firmwareFeatures?
Click to expand...

Malformed FirmwareFeatures (particularly those lacking the large-base-system bit) can affect the "seal" for the staged update. See also:

Signed system volume security

SSV not only helps prevent tampering with any Apple software that’s part of the operating system, it also makes macOS software update more reliable and much safer.
support.apple.com
 
  • Like
Reactions: Bmju and Gustav Holdoff
I've been running Mojave on a 5,1 succesfully for a couple of years now. I used OCLP to do the upgrades etc. I never had boot screen, but never really needed it.... until now.

I wish to create a new Monterey drive, and following the steps on OCLP, but not having Boot screen seems to be hurting me. I can't open Boot picker or recovery even using terminal prompts. I was able to complete previous upgrades using the old Mac GPU, but my current rx580 can't be taken out as I'm already on MOjave and my non-metal card won't work will it?

After several hours reading and searching, I have a few options and don't know which way to proceed?

I can use Martin lo's version of open core, or flash the GPU but the more I read, the more confused I get. What might be my "safest" option ?
 
The safest option is making an OpenCore CD. See post 1.

I prefer adding EnableGop into the Mac firmware. Also see post 1.

My tool makes all the checks to make this a safe as possiblle. See my signature.
 
Thankyou Macschrauber.
I'm sorry, I'm still somewhat confused but let me know if Ive got this wrong?

1) Make the open core CD - I think this is the same as making a USB yes?
I've got my USB with plain MOnterey on it. I can use and flash it with OCLP but without boot picker, I can't launch it. I've tried this already. I applied the OCLP package to the USB disk or should it go on my currently-in-use-boot drive?

2)If I do an install of plain open core or use Martin Lo's package I need to disable SIP - but I can't do that as I can't boot into recovery?
Same thing for trying to EnableGOP: I need to disable SIP which I can't do?

I think I need to continue researching being able to activate recovery somehow.
 
benny gsr said:
I think this is the same as making a USB yes?
Click to expand...
No. As you’ve already observed, you can’t (easily) select your USB drive for booting without the boot picker. The point of the CD is to be able to boot from it on demand by holding C during startup. Please see Maintenance in post #1.

With the CD, you’ll be able to easily bless your main OC install (with Control+Enter) without needing to disable SIP. You’ll also be able to easily select Recovery if you want. Again please see post #1 for more details.
 
  • Like
Reactions: Macschrauber
benny gsr said:
I need to disable SIP - but I can't do that as I can't boot into recovery?
Click to expand...

You can also disable SIP via any macOS createinstallmedia USB installer since El Capitan, even without a GPU with pre-boot configuration support.

If you remove all other disks from the Mac Pro (SATA/PCIE/FW/USB) but the createinstallmedia USB installer, the Mac Pro firmware will boot the createinstallmedia USB installer after scanning everything else since USB drives have the least priority at boot, so, after 3 or 4 minutes after power up, you will have the macOS Installer Assistant on the screen, then is just necessary to open Terminal and disable SIP with csrutil disable.
 
  • Like
Reactions: O.N.Y.X and Bmju
Thankyou for your help.
Before reading your posts I found an old topic where tsialex told someone else to remove everything and do a clean install of Mojave.
I did this on a separate drive.

I was then able to access a Recovery partition which I then used to install OCLP - the GUI of this is so easy, I couldn't resist it over the other options. I'm now running MOnterey and it appears to be going well so far. No NVME drives just yet.
Only issue is the boot picker is still not working... probably because in all my excitement, I forgot to disable SIP. Despite this, the install went well but possibly I'll just have to disable SIP, reinstall a new OCLP configuration onto the Monterey boot drive.
I've fiddled around a bit on the OCLP settings section, but nothing I "activate" seems to make any difference
 
Hello,

I've updated my opencore from 0.7.6 to 0.9.3 and when I run the commande to check which OpenCore version I've it return this
Code: 
4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version    UNK-000-0000-00-00
I'm attaching my plist file.

I've updated the plist file using both the Macrumor thread, the plist available in the first post and dortania's PDF.
My original PLIST has been built using OCLP first and today I've done it manually.

Thanks!
 

Attachments

  • config-plist-093.zip
    6.4 KB · Views: 54
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back