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

 

[alliance]

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

Ironically, it was doing exactly that with OpenCanopy
It kept selecting ClearNVRAM everytime I selected Windows!

So I've reverted back to text-based, and it still does it?

Any ideas? I changed Pickermode: 17 to 1, as it had the same issue when using 'Builtin', PickerVariant: Auto, and that made no difference.

 

[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.

 

[alliance]

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.

Just tried that, both options just wipe out my bootloader and take me to Windows, where I have to re-add the macos boot EFI in the bootloader entries
I've never personally had NVRAM do anything, bar on a real mac TBH

Problem is still exactly the same

It never did this on Sequoia with the same version of OpenCore

 

[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.

 

[alliance]

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.

Yeah I did all that originally and have double checked

As I said before, it does the same thing and moves the the selection too far whenever I select Windows, on both OpenCanopy and the text based default.

CMD+Enter/Windows+Enter didn't do anything BTW...

It doesn't add anything to my BIOS entries for boot.

CleanNVRAM/ResetNVRAM/ResetNVRam all do the same thing, and wipe out my MacOS bootloader entry and put a duplicate Windows loader entry in - they seem to literally do nothing, and always have on every hackintosh I've tried. Only on a real Mac has it ever done what it's supposed to.

This is also a clean install on the new Samsung SSD, and it does the same thing as the last SSD did at the boot menu, be it OpenCanopy or normal text based boot menu

AllowSetDefault, is already set to True.

 

[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.

 

[alliance]

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.

Have a look at the EFI I've attached, see what you think. I've removed the obvious serials etc.

I've personally never had this issue, so I'm rather confused as to why it's occured now

It doesn't 'always' do it. But if I try and select it immediately, upon the boot picker selection, then it will often cycle twice, verus once, upon the key being pressed - i.e. it does it whatever direction that you press twice - hopefully that makes sense?

Here's my EFI

Have a look and tell me what I've missed

Thanks

 

[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.

 

[alliance]

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.

Thank you so much for your help

I'll give that a go tomorrow

I didn't use a MacPro SMBIOS, due to previously trying it on Sequoia, and it constantly telling me my ram was in the wrong slots upon every boot into macos
The motherboard only has 2 slots as it's MITX

Will that still happen? If so, I'll just use the iMacPro1,1 I don't personally mind what it shows up as in the about me section.

Thanks again, please let me know regarding the above, but I'll try the revised EFI first, as recommended
It's so close to being the perfect system for my use case!