Jump to content
2 posts in this topic

Recommended Posts

I am seeing some strange behavior in Clover and even the system

If I have more than one config file, when the Clover window open, and I choose a different config file than the default one, Clover is not reading the new file settings.

for example, I boot into the clover menu, and the default config.plist has for example, a change EHC1 to EH01 patch.

I then go to the config menu and select configtest.plist, which has that patch plus a new one. The new one does not load.

Clover use to be able to do this, now it doesn't. Am I not doing something, for example, is the a F key to reforce clover to reload the newly selected patch?

Pexplexing. Seems like it's been happening since about 5103 or sooner.

Well, just recently, when I installed clover on a legacy Motherboard, (non UEFI, and it works with Catalina 10.5.5, woo hoo!) The config file generated by Clover caused lightning bolt symbols in Clover configurator.

I've checked the syntax, and everything seems to line up. And it's been happening for a while now, ever since I started with 5103 or there about. Not all my config files could be bad, and as I said, even a clover generated config file had problems.

Could it be something with EmuVariableUefi.efi or related to the NVRAM?

×
×
  • Create New...