Contribute
Register

Native NVRAM Available?

Status
Not open for further replies.
Seems like latest Clover emulates Nvram by having a .plist file in the EFI partition - do I understand it correctly?
If so, does it mean I can remove EmuVariableUefi-64.efi from the drivers directory?

EmuVariableUefi-64.efi overrides UEFI NVRAM services to provide working emulated NVRAM.
The "RC scripts" are responsible for writing nvram.plist on your EFI partition when using EmuVariableUefi-64.efi.
If you remove EmuVariableUefi-64.efi, you will revert to native NVRAM services.
With AptioMemoryFix.efi instead of OsxAptioFix*.efi, you can likely get native NVRAM working (eg. working NVRAM without EmuVariableUefi-64.efi).
 
EmuVariableUefi-64.efi overrides UEFI NVRAM services to provide working emulated NVRAM.
The "RC scripts" are responsible for writing nvram.plist on your EFI partition when using EmuVariableUefi-64.efi.
If you remove EmuVariableUefi-64.efi, you will revert to native NVRAM services.
With AptioMemoryFix.efi instead of OsxAptioFix*.efi, you can likely get native NVRAM working (eg. working NVRAM without EmuVariableUefi-64.efi).
Thank you! I used to have EmuVariableUefi-64.efi since without Nvidia drivers won't load.
However during last upgrade I removed it and yet the drivers still load. Last I checked I don't have AptioMemoryFix.efi, only OsxAptioFix3Drv-64.efi in my Clover/drivers64UEFI folder.
Do the drivers still load because nvram.plist is still there? Basically my question is, should I put EmuVariableUefi-64.efi back?
 
Thank you! I used to have EmuVariableUefi-64.efi since without Nvidia drivers won't load.
However during last upgrade I removed it and yet the drivers still load. Last I checked I don't have AptioMemoryFix.efi, only OsxAptioFix3Drv-64.efi in my Clover/drivers64UEFI folder.
Do the drivers still load because nvram.plist is still there? Basically my question is, should I put EmuVariableUefi-64.efi back?

OsxAptioFix3Drv-64.efi is older version of AptioMemoryFix.efi. You can detele EmuVar and NVRAM.plist, if OsxAptioFix3Drv-64 or AptioMemoryFix.efi(Prefered) is giving you native NVRAM support.

I have a question too, why shouldn’t we just all use emulated since it works fine, why should we use native NVRAM, and is it more dangerous than emulated NVRAM, potentially?
 
I have a question too, why shouldn’t we just all use emulated since it works fine, why should we use native NVRAM, and is it more dangerous than emulated NVRAM, potentially?

Native NVRAM is a bit better as it works even when the system crashes before the RC scripts that save nvram.plist can be run.
So, if you have KP on shutdown or other KP while running you can get a backtrace (as KP data is written to NVRAM).
 
Asus H170 Pro Gaming (early bios?) nvram is native now.

EDIT: I am using OsxAptioFix3Drv-64.ef, installed through Clover.

Should I use AptioMemoryFix.efi? For now I have no troubles with Aptio.
 
Last edited:
Asus H170 Pro Gaming (early bios?) nvram is native now.

EDIT: I am using OsxAptioFix3Drv-64.ef, installed through Clover.

Should I use AptioMemoryFix.efi? For now I have no troubles with Aptio.
You should, OsxAptioFix3Drv-64.efi is older version of AptioMemoryFix
 
EmuVariableUefi-64.efi overrides UEFI NVRAM services to provide working emulated NVRAM.
The "RC scripts" are responsible for writing nvram.plist on your EFI partition when using EmuVariableUefi-64.efi.

How do I install these? I don't think my VRAM is working.
 
Just tested my NVRam as per Tony's instructions in his post and Terminal says its working correctly after reboot. However my computer is not auto-booting like my Clover settings say. It's as if my settings don't actually stick :(.

Any help is greatly appreciated.
 
Status
Not open for further replies.
Back
Top