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

[cdf]

In my case, it seems that the background is gray by default and the boot menu is erasing part of it (making that part black) where it needs to display text...

 

[startergo]

and the boot menu is erasing part of it

Is you resolution 100 or 200? Mine is 100.

 

[cdf]

Is you resolution 100 or 200? Mine is 100.

Same result with 100 and 200.

 

[startergo]

WEG 1.3.7 has new arguments. Please read Readme. For instance:
"`ngfxpatch=pikera` replaces `board-id` with `board-ix` "

 

[vit9696]

OpenCore (FwRuntimeServices module, ProtectSecureBoot quirk) now has the fix for Windows UEFI certificate issues. Thanks @w1z for testing.

@startergo, this is not correct, you got confused in git log history.

 

[w1z]

@vit9696 I believe something broke with the recently implemented SafeFileOpen loading feature as I am no longer able to boot into recovery via OC with AppleBootPolicy enabled.

01:735 00:003 OCB: Short-form DP could not be expanded
01:739 00:004 OCB: Failed to match a default boot option
01:743 00:003 OCB: Initial default is 0, fallback
06:485 04:741 OCB: Should boot from Recovery 10.15.3 (T:2|F:1|DEF:0)
06:624 00:139 OCRAM: Extent allocation of 691435795 bytes (A) gave 100000000
13:860 07:236 OCRAM: SHA-256 Digest is: 5C532B8F905625CEBDF288DC627E79AF3DE8FD2F35360613121F0CE4EC5ABA9C
13:865 00:004 OCB: Found chunklist BaseSystem.chunklist for DMG BaseSystem.dmg[10]
13:970 00:104 DMG has been altered
13:974 00:003 OCB: Failed to retrieve boot file from DMG
13:978 00:003 OCB: LoadImage failed - Unsupported

Full log attached.

Thank you.

Edit: Can someone else confirm this?

 

[h9826790]

@vit9696 I believe something broke with the recently implemented SafeFileOpen loading feature as I am no longer able to boot into recovery via OC with AppleBootPolicy enabled.

01:735 00:003 OCB: Short-form DP could not be expanded
01:739 00:004 OCB: Failed to match a default boot option
01:743 00:003 OCB: Initial default is 0, fallback
06:485 04:741 OCB: Should boot from Recovery 10.15.3 (T:2|F:1|DEF:0)
06:624 00:139 OCRAM: Extent allocation of 691435795 bytes (A) gave 100000000
13:860 07:236 OCRAM: SHA-256 Digest is: 5C532B8F905625CEBDF288DC627E79AF3DE8FD2F35360613121F0CE4EC5ABA9C
13:865 00:004 OCB: Found chunklist BaseSystem.chunklist for DMG BaseSystem.dmg[10]
13:970 00:104 DMG has been altered
13:974 00:003 OCB: Failed to retrieve boot file from DMG
13:978 00:003 OCB: LoadImage failed - Unsupported

Full log attached.

Thank you.

I can enter recovery partition via OC (in my case, press number 1 blindly since I can't see the boot picker with Radeon VII yet).

And that's with AppleBootPolicy = true

 

[w1z]

I can enter recovery partition via OC (in my case, press number 1 blindly since I can't see the boot picker).

And that's with AppleBootPolicy = true

Thanks for the confirmation - strange though as this is happening on a fresh install of macOS after my previous installation was borked enabling filevault, which by the way works great now.

What's the easiest way to rebuild the recovery parition without carrying out a full reinstallation?

 

[h9826790]

Thanks for the confirmation - strange though as this is happening on a fresh install of macOS after my previous installation was borked enabling filevault, which by the way works great now.

What's the easiest way to rebuild the recovery parition without carrying out a full reinstallation?

Carbon Copy Cloner may able to do it

 

[lowendlinux]

4 months on I made a thing with open core...

It has no boot screens nor HEVC encode/decode but it's a 10.15.3 machine..

Thanks to all those that built this, if there's a tip page let me know.

 

[rroumen]

@vit9696 I believe something broke with the recently implemented SafeFileOpen loading feature as I am no longer able to boot into recovery via OC with AppleBootPolicy enabled.

01:735 00:003 OCB: Short-form DP could not be expanded
01:739 00:004 OCB: Failed to match a default boot option
01:743 00:003 OCB: Initial default is 0, fallback
06:485 04:741 OCB: Should boot from Recovery 10.15.3 (T:2|F:1|DEF:0)
06:624 00:139 OCRAM: Extent allocation of 691435795 bytes (A) gave 100000000
13:860 07:236 OCRAM: SHA-256 Digest is: 5C532B8F905625CEBDF288DC627E79AF3DE8FD2F35360613121F0CE4EC5ABA9C
13:865 00:004 OCB: Found chunklist BaseSystem.chunklist for DMG BaseSystem.dmg[10]
13:970 00:104 DMG has been altered
13:974 00:003 OCB: Failed to retrieve boot file from DMG
13:978 00:003 OCB: LoadImage failed - Unsupported

Full log attached.

Thank you.

Edit: Can someone else confirm this?

@w1z I also have issues booting into recovery but since I hadn't used this feature before I didn't know if it worked before. Both Mojave and Catalina recovery give me the LoadImage failed - Unsupported error.

 

[Nick_P]

4.1>5.1
2x 3.46 CPU
Saphire Pulse Radeon RX 580

Hello, I have been messing around with the AMD hw acceleration instruction in the other thread (and that did work except the bootpicker), today I wiped all the drives and tried the instruction in this thread.

Everything from this thread post #1 works properly, except the bootpicker does not show up, my screen stays black until the logon.

However, as others reported, if I press 1 during the blackout period, it boots into 10.15. If I press 3, it boots into 10.14. If I press 2, it boots into 10.15 Recovery.

-I tried two different 4k monitors. I tried display port cable, and hdmi cable, and tried all 4 ports on the GPU (2 hdmi, 2 displayport).
-I tried a second gpu I have, "Zotac GT 710 Zone". It had the same black screen.
-I then put in my Apple OEM GPU, and it showed the bootpicker screen properly, and booted according to the pick properly.

I kind of have the feeling there is no signal going to the monitor until right before the logon screen. This is just my gut, I don't have any evidence. The progress bar shows up at the bottom for a split second right before the logon screen. I don't recall if that progress bar showed up at all when I was running plain 10.14 without any mods whatsoever.

If there is any testing I can do to help, I'd be happy to. (although this is all new to me. I did read both threads in their entirety over the past two weeks).

Edit: I just checked the ebay add I got the used Rx580 from a few weeks back. It said "Has ETH mod bios installed". I don't know if this is significant or not, but figured it was worth mentioning.

Thanks,
Nick

 

[startergo]

4.1>5.1
2x 3.46 CPU
Saphire Pulse Radeon RX 580

Hello, I have been messing around with the AMD hw acceleration instruction in the other thread (and that did work except the bootpicker), today I wiped all the drives and tried the instruction in this thread.

Everything from this thread post #1 works properly, except the bootpicker does not show up, my screen stays black until the logon.

However, as others reported, if I press 1 during the blackout period, it boots into 10.15. If I press 3, it boots into 10.14. If I press 2, it boots into 10.15 Recovery.

-I tried two different 4k monitors. I tried display port cable, and hdmi cable, and tried all 4 ports on the GPU (2 hdmi, 2 displayport).
-I tried a second gpu I have, "Zotac GT 710 Zone". It had the same black screen.
-I then put in my Apple OEM GPU, and it showed the bootpicker screen properly, and booted according to the pick properly.

I kind of have the feeling there is no signal going to the monitor until right before the logon screen. This is just my gut, I don't have any evidence. The progress bar shows up at the bottom for a split second right before the logon screen. I don't recall if that progress bar showed up at all when I was running plain 10.14 without any mods whatsoever.

If there is any testing I can do to help, I'd be happy to. (although this is all new to me. I did read both threads in their entirety over the past two weeks).

Edit: I just checked the ebay add I got the used Rx580 from a few weeks back. It said "Has ETH mod bios installed". I don't know if this is significant or not, but figured it was worth mentioning.

Thanks,
Nick

Boot screen works on RX-580. If it does not work for you then you need to troubleshoot it. Perhaps something in the configuration is missing.

 

[Ludacrisvp]

Edit: I just checked the ebay add I got the used Rx580 from a few weeks back. It said "Has ETH mod bios installed". I don't know if this is significant or not, but figured it was worth mentioning.

You will need to download and flash the correct BIOS on the GPU.
Modded VBIOS breaks the ability to use GOP from what I understand.
If your GPU has a dual BIOS switch, it is possible they didn't flash both and you can simply flip the switch.
Else look for your GPU's ROM on techpowerup and flash the OEM ROM.

 

[rroumen]

Edit: I just checked the ebay add I got the used Rx580 from a few weeks back. It said "Has ETH mod bios installed". I don't know if this is significant or not, but figured it was worth mentioning.

Thanks,
Nick

That is significant, it has a modded bios for mining ETHerium which probably breaks GOP. Find the bios for your exact card @techpowerup and flash it to stock firmware first.

 

[w1z]

@w1z I also have issues booting into recovery but since I hadn't used this feature before I didn't know if it worked before. Both Mojave and Catalina recovery give me the LoadImage failed - Unsupported error.

Are you using latest OC compiled from master branch and do you have filevault enabled? Also, can you share with me your config.plist?

Thank you.

 

[w1z]

Quick update, and fix, on the unbootable recovery -

@vit9696 Please ignore my previous bug report as the issue is with the catalina patcher usb installer, already raised with @dosdude1, and not OC.

The catalina patcher is creating unbootable recovery partitions, with a larger parition size of 708.8MB vs 523.5MB, and the only way I could repair recovery is by using Catalina Recovery HD Partition app - thank you @chris1111

Doesn't boot -

Boots

Tested with and without OC - recovery 10.15.3 now boots perfectly.

Hope this helps all those impacted by this.

Cheers

 

[vit9696]

@w1z, OpenCore verifies cryptographical signatures of recovery images like modern Macs do, so corrupted recoveries will indeed not launch.

 

[h9826790]

4.1>5.1
2x 3.46 CPU
Saphire Pulse Radeon RX 580

Hello, I have been messing around with the AMD hw acceleration instruction in the other thread (and that did work except the bootpicker), today I wiped all the drives and tried the instruction in this thread.

Everything from this thread post #1 works properly, except the bootpicker does not show up, my screen stays black until the logon.

However, as others reported, if I press 1 during the blackout period, it boots into 10.15. If I press 3, it boots into 10.14. If I press 2, it boots into 10.15 Recovery.

-I tried two different 4k monitors. I tried display port cable, and hdmi cable, and tried all 4 ports on the GPU (2 hdmi, 2 displayport).
-I tried a second gpu I have, "Zotac GT 710 Zone". It had the same black screen.
-I then put in my Apple OEM GPU, and it showed the bootpicker screen properly, and booted according to the pick properly.

I kind of have the feeling there is no signal going to the monitor until right before the logon screen. This is just my gut, I don't have any evidence. The progress bar shows up at the bottom for a split second right before the logon screen. I don't recall if that progress bar showed up at all when I was running plain 10.14 without any mods whatsoever.

If there is any testing I can do to help, I'd be happy to. (although this is all new to me. I did read both threads in their entirety over the past two weeks).

Edit: I just checked the ebay add I got the used Rx580 from a few weeks back. It said "Has ETH mod bios installed". I don't know if this is significant or not, but figured it was worth mentioning.

Thanks,
Nick

Did you ever flash your card? Or if you buy it used (the last user may flashed it)?

Modification of the VBIOS can break the GOP. e.g. Downvolt the card, or OC the card.

Update: Just saw that's a mining card. And the others already pointed out that's the problem.

 

[astonius86]

Quick update, and fix, on the unbootable recovery -

@vit9696 Please ignore my previous bug report as the issue is with the catalina patcher usb installer, already raised with @dosdude1, and not OC.

The catalina patcher is creating unbootable recovery partitions, with a larger parition size of 708.8MB vs 523.5MB, and the only way I could repair recovery is by using Catalina Recovery HD Partition app - thank you @chris1111

Doesn't boot -

View attachment 893589

Boots

View attachment 893590

Tested with and without OC - recovery 10.15.3 now boots perfectly.

Hope this helps all those impacted by this.

Cheers

Thanks for posting @w1z. I noticed I couldn't launch Recovery from the OC boot picker, so I gave this a shot. It seemed to run successfully, but unfortunately I still get a panic when I select Recovery on the boot menu. I've attached a log from an attempt.

 

[startergo]

Thanks for posting @w1z. I noticed I couldn't launch Recovery from the OC boot picker, so I gave this a shot. It seemed to run successfully, but unfortunately I still get a panic when I select Recovery on the boot menu. I've attached a log from an attempt.

This is not showing the KP. Can you upload the KP system log?

 

[astonius86]

This is not showing the KP. Can you upload the KP system log?

Sorry about that... here it is:

{"timestamp":"2020-02-11 11:38:30.22 -0600","bug_type":"210","os_version":"Mac OS X 10.15.3 (19D76)"}


{"macOSProcessedStackshotData":"bm8gb24gZGlzayBvciBzbGVlcC93YWtlIGZhaWx1cmUgcGFuaWMgc3RhY2tzaG90IGZvdW5k","macOSPanicString":"panic(cpu 18 caller 0xffffff7f86e9fc02): NightShiftUnlocker: nsu @ failed to initialize the mach info\n\nBacktrace (CPU 18), Frame : Return Address\n0xffffff8a9836b510 : 0xffffff800313bb2b \n0xffffff8a9836b560 : 0xffffff80032734d5 \n0xffffff8a9836b5a0 : 0xffffff8003264f4e \n0xffffff8a9836b5f0 : 0xffffff80030e2a40 \n0xffffff8a9836b610 : 0xffffff800313b217 \n0xffffff8a9836b710 : 0xffffff800313b5fb \n0xffffff8a9836b760 : 0xffffff80038d2aa9 \n0xffffff8a9836b7d0 : 0xffffff7f86e9fc02 \n0xffffff8a9836b810 : 0xffffff7f86cc74b4 \n0xffffff8a9836b8f0 : 0xffffff7f86cc9649 \n0xffffff8a9836b900 : 0xffffff80038bce7d \n0xffffff8a9836b990 : 0xffffff8003674ce1 \n0xffffff8a9836bd20 : 0xffffff800367c56e \n0xffffff8a9836bda0 : 0xffffff800367d702 \n0xffffff8a9836be40 : 0xffffff800367dc9b \n0xffffff8a9836beb0 : 0xffffff8003642b3d \n0xffffff8a9836bed0 : 0xffffff800369c250 \n0xffffff8a9836bf20 : 0xffffff8003133599 \n0xffffff8a9836bf60 : 0xffffff80030e2a0c \n Kernel Extensions in backtrace:\n as.vit9696.Lilu(1.4.1)[81A9C8D0-23F6-3579-96D1-264515ADC521]@0xffffff7f86cc3000->0xffffff7f86ce9fff\n com.nsuteam.NightShiftUnlocker(2.3)[0BBCB2B9-EA71-31B5-A8B5-A0670BA0256E]@0xffffff7f86e9e000->0xffffff7f86ea5fff\n dependency: as.vit9696.Lilu(1.4.1)[81A9C8D0-23F6-3579-96D1-264515ADC521]@0xffffff7f86cc3000\n\nBSD process name corresponding to current thread: init\nBoot args: -no_compat_check -wegtree shikigva=80\n\nMac OS version:\nNot yet set\n\nKernel version:\nDarwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1\/RELEASE_X86_64\nKernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE\nKernel slide: 0x0000000002e00000\nKernel text base: 0xffffff8003000000\n__HIB text base: 0xffffff8002f00000\nSystem model name: MacPro5,1 (Mac-27AD2F918AE68F61)\nSystem shutdown begun: NO\nPanic diags file unavailable, panic occurred prior to initialization\n\nSystem uptime in nanoseconds: 5524446622\nlast loaded kext at 4667912094: >!ATopCaseHIDEventDriver\t3430.1 (addr 0xffffff7f866e2000, size 61440)\nloaded kexts:\ncom.nsuteam.NightShiftUnlocker\t2.3.0\ncom.innieteam.Innie\t1.2.0\nas.vit9696.!AALC\t1.4.6\nas.vit9696.WhateverGreen\t1.3.6\nas.vit9696.Lilu\t1.4.1\n>!ATopCaseHIDEventDriver\t3430.1\n>!UTopCaseDriver\t3430.1\n|IO!BUSBDFU\t7.0.3f5\n>!AFileSystemDriver\t3.0.1\n>DiskImages.ReadWriteDiskImage\t493.0.0\n>DiskImages.SparseDiskImage\t493.0.0\n>DiskImages.UDIFDiskImage\t493.0.0\n>DiskImages.HTTPBackingStore\t493.0.0\n>DiskImages.FileBackingStore\t493.0.0\n>DiskImages.RAMBackingStore\t493.0.0\n@filesystems.hfs.kext\t522.0.9\n@BootCache\t40\n@!AFSCompression.!AFSCompressionTypeDataless\t1.0.0d1\n@!AFSCompression.!AFSCompressionTypeZlib\t1.0.0\n>!AVirtIO\t1.0\n|SCSITaskUserClient\t422.0.2\n@filesystems.apfs\t1412.81.1\n>!I82574LEthernet\t2.7.2\n>AirPort.BrcmNIC\t1400.1.1\n>!AAHCIPort\t341.0.2\n@private.KextAudit\t1.0\n>!AHPET\t1.8\n>!ARTC\t2.0\n>!AACPIButtons\t6.1\n>!ASMBIOS\t2.1\n>!AACPIEC\t6.1\n>!AAPIC\t1.7\n>!A!ICPUPowerManagementClient\t222.0.0\n$!AImage4\t1\n@nke.applicationfirewall\t303\n$TMSafetyNet\t8\n@!ASystemPolicy\t2.0.0\n>!A!ICPUPowerManagement\t222.0.0\n|EndpointSecurity\t1\n>!AHS!BDriver\t3430.1\n>IO!BHIDDriver\t7.0.3f5\n>!AHIDKeyboard\t209\n>!AMultitouchDriver\t3430.1\n>!AInputDeviceSupport\t3430.1\n>usb.IOUSBHostHIDDevice\t1.2\n>usb.cdc\t5.0.0\n>usb.networking\t5.0.0\n>usb.!UHostCompositeDevice\t1.2\n>usb.!UHub\t1.2\n>DiskImages.KernelBacked\t493.0.0\n|IOSurface\t269.6\n@filesystems.hfs.encodings.kext\t1\n|IOAudio!F\t300.2\n@vecLib.kext\t1.2.0\n|IOSerial!F\t11\n|IOSCSIMultimediaCommandsDevice\t422.0.2\n|IOBD!S!F\t1.8\n|IODVD!S!F\t1.8\n|IOCD!S!F\t1.8\n>!AXsanScheme\t3\n|IOAHCIBlock!S\t316.80.1\n|IOAHCISerialATAPI\t268\n|IO80211!F\t1200.12.2b1\n>mDNSOffloadUserClient\t1.0.1b8\n>corecapture\t1.0.4\n|IOSkywalk!F\t1\n>usb.!UEHCIPCI\t1.2\n>usb.!UUHCIPCI\t1.2\n>usb.!UUHCI\t1.2\n>usb.!UEHCI\t1.2\n|IOAHCI!F\t290.0.1\n>usb.!UHostPacketFilter\t1.0\n|IOUSB!F\t900.4.2\n>!AEFINVRAM\t2.1\n>!AEFIRuntime\t2.1\n|IOSMBus!F\t1.1\n|IOHID!F\t2.0.0\n$quarantine\t4\n$sandbox\t300.0\n@kext.!AMatch\t1.0.0d1\n>!AKeyStore\t2\n>!UTDM\t489.80.2\n|IOSCSIBlockCommandsDevice\t422.0.2\n>!ACredentialManager\t1.0\n>KernelRelayHost\t1\n>!ASEPManager\t1.0.1\n>IOSlaveProcessor\t1\n>!AFDEKeyStore\t28.30\n>!AEffaceable!S\t1.0\n>!AMobileFileIntegrity\t1.0.5\n@kext.CoreTrust\t1\n|CoreAnalytics!F\t1\n|IOTimeSync!F\t810.1\n|IONetworking!F\t3.4\n>DiskImages\t493.0.0\n|IO!B!F\t7.0.3f5\n|IO!BPacketLogger\t7.0.3f5\n|IOUSBMass!SDriver\t157.40.7\n|IOSCSIArchitectureModel!F\t422.0.2\n|IO!S!F\t2.1\n|IOUSBHost!F\t1.2\n>usb.!UCommon\t1.0\n>!UHostMergeProperties\t1.2\n>!ABusPower!C\t1.0\n|IOReport!F\t47\n>!AACPIPlatform\t6.1\n>!ASMC\t3.1.9\n>

 

[startergo]

Disable the nightshiftunlocker and try again.

 

[astonius86]

Disable the nightshiftunlocker and try again.

That did it! @cdf can you glean any info from my log to see if NightShiftUnlocker can be patched for this?
[automerge]1581447032[/automerge]
Still working on setting Windows 10 in Startup Disk. I made a little progress. Before I wasn't seeing Windows at all in the disk list. I discovered it is because I had SIP enabled. Once I disabled SIP it started to appear again. Is this expected behavior? Can an OC tweak make Windows appear in Startup Disk without disabling SIP?

Unfortunately even though it appears I get this message when I select Windows as the new startup disk.

 

[cdf]

That did it! @cdf can you glean any info from my log to see if NightShiftUnlocker can be patched for this?

Yes, I actually addressed this on my own (unreleased) build. I will provide an update soon.