OpenCore boot menu strange issue

[alliance]

Hi,

having a strange issue, on the boot menu selection, it defaults to macos (fine), sometimes when I select windows (up arrow) too quickly, without waiting a second, it'll press my selection arrow twice, I.E. instead of going to Windows above macos, it'll end up at the bottom of the list?

Anything I can do to change this?

It never occured on previous macos versions/older OpenCore versions?

 

[Edhawk]

Sounds like you are using the Text based Picker List on the OpenCore boot screen. Switching to the OpenCore GUI boot screen might help with the problem, as it is less likely you will double hit the left arrow when selecting the Windows icon.

See this section of the Dortania guide for details on how tow to change from the Picker List to the GUI boot screen.

OpenCore beauty treatment | OpenCore Post-Install

 

[Edhawk]

ClearNvram requires a manual reboot of the system for the action to occur. It is why it is better to use ResetNvram, as the system is automatically rebooted as part of the action to remove the old NVRAM entries.

Follow the Dortania instructions provided in the link above, but make sure you have the ResetNvramEntry.efi in your OC setup, along with the other essential OC Drivers.

 

[Edhawk]

I assume the following:

That you have the OpenCanopy.efi driver in your /EFI/OC/Drivers folder with a corresponding entry in your config.plist?

That you have a populated Resources folder in your EFI folder? If not use the link below, select the green CODE button and download the OcBinaryData folder. In this folder is a populated Resources folder.

GitHub - acidanthera/OcBinaryData

Contribute to acidanthera/OcBinaryData development by creating an account on GitHub.

github.com

That you have changed Misc > Boot > PickerVariant from Builtin to External in your config.plist?

You may find that changing Misc > Boot > LauncherOption from Disabled to Full helps. This config option adds a a boot entry called ‘OpenCore’ to the Bios, which you can select as the default boot drive. It is resilient against use of the ResetNvram option from the OpenCore boot screen.

That you have Misc > Security > AllowSetDefault set as True/Enabled in your config.plist. As this option allows you to set one of the entries on the OC boot screen as your default boot partition. To set the macOS drive as the default boot partition simply press and hold the cmd+Enter buttons (left Win key+Enter on PC keyboard) while the desired partition icon is selected. The arrow icon below the drive icon should change to a circular arrow to indicate the drive has been set as the OC default drive.

 

[Edhawk]

No, this I think is going to be caused by an error on your part. Something in your EFI or config.plist is most likely set incorrectly.

I use the OC GUI on all my Hacks (approx 26 at last count) and don’t have any issues setting the default disk in Bios or the OC boot loader, using the settings I mentioned above.

I have never had any issues moving the boot selection from the macOS icon to the Windows icon, or selecting one of the hidden OC Drivers or Tools.

 

[Edhawk]

Try this revised EFI-2.

I am not sure using the SMBIOS for an iMac20,1 is the best when running an AMD Hack. You might be better served using the iMacPro1,1 or MacPro7,1. I found I had issues when using the iMac20,1 SMBIOS on my mini PC AMD hacks, which didn't occur once I changed the SMBIOS to iMacPro1,1.

I have made a few changes:
Deleted the DeviceProperties entries, as these are known to clash with NootedRed.kext.
Made a few minor changes to Quirks, to better follow the Dortania guide.
Re-ordered a few kexts in the config.plist, to help with the initial OC boot.

See if this revised EFI helps.

I would try with your existing SMBIOS data initially, but if the same issues persist then try replacing the iMac20,1 with the iMacPro1,1 SMBIOS in the config.plist.

 

[Edhawk]

There is a simple fix for the Mac Pro memory issue, using RestrictEvents and adding revpatch=auto boot argument to your config.plist.

 

[Edhawk]

I removed apfs_aligned.efi because I have never needed that driver on any of the AMD Hacks I have built. Including a couple of B450 systems for my nephew’s.

Not sure what else to suggest.