I tried with explicit resolution, but doesn’t work. Only hdmi works fine.
I've made all the configurations, step by step and now it's all done and works fine. Display port works fine.
Type
dh in the EFI Shell. Near the end should be a handle for the EFI Shell. Before that should be a handle for OpenCore (it might be called bootx64.efi).dh -d -v b0 to get the full path. Use map to get a list of file systems, find the one that matches the first part of the full path, type the name of the matching filesystem followed by a colon to change the current directory to that file system (e.g. fs0:), then type vol to get the volume name. It will probably be EFI which is not very specific if you have more than one disk (which all probably have an EFI partition). Therefore, type ls to get a list of files in the file system. What I do is add a folder to every EFI partition to describe it's location (e.g. EFIBay1) so when I see it with the ls command, I know what file system I'm looking at.<key>Tools</key>
<array/><key>Tools</key>
<array>
<dict>
<key>Arguments</key>
<string></string>
<key>Auxiliary</key>
<true/>
<key>Comment</key>
<string>UEFI Shell</string>
<key>Enabled</key>
<true/>
<key>Name</key>
<string>UEFI Shell</string>
<key>Path</key>
<string>OpenShell.efi</string>
</dict>
</array>
Your best best is to simply disable the backup version and reboot.
It also helps to not eject drives accidentally! Or have them clutter up the desktop if that's a feature you're using.
@joevt That's very helpful indeed, thank you! I have actually now managed to pull myself up by my bootlaces for EDK2 development already, using the extremely useful VisualUefi, which has built in QEMU integration - in Windows. (My next step is to figure out the EDK2 meta-data files, and the QEMU integration which I understand exists in EDK2 for Xcode, so that I can move my code back to compiling on any OS.) Thanks again!
From looking at your image it looks like it has 2 dvi-D connectors and 1 HDMI connector.
OpenCore can certainly help you get bootscreen but you need to have a suitable GPU.
The question is actually not about upsides or downsides.
See above. There is no right or wrong in it. It is just about whether you want something it gives or not.
Take a look at this Alternative Implementation Process.
So this RefindPlus would give me a boot screen and hardware acceleration?
I think it may be easier to just install opencore alone.
Always a good idea to back things up before attempting changes.
Sorry, I really can't watch the video and it doesn't matter what it does as such.
AFAIK SSDT will be loaded only when using OC. How to add SSDT with OC:
github.com
<dict>
<key>BoardProduct</key>
<string>Mac-7BA5B2D9E42DDD94</string>
<key>FirmwareFeatures</key>
<data>A1QM4A==</data>
<key>FirmwareFeaturesMask</key>
<data>P/8f/w==</data>
</dict>A1QMwA==. For some reason, the changed bit fixes the "Your Mac needs a firmware update in order to install to this volume..." issue. (Interestingly, this bit has been documented as the one for enabling proper UEFI bootability for Windows...)hi cdf, I usually change the config.plist in order to complete spoofing an iMac Pro 1,1 for Big Sur upgrade purposes.
Yes I know, in fact the first thing that I do is to exit from Apple ID with my original hybridization config.plist. Then I overwrite the existing config.plist with the full spoofing one (with a a random generated serial with clover configurator) and (after a reboot) I use it to check for updates and to do them.