- Joined
- Feb 26, 2011
- Messages
- 127
- Motherboard
- ASUS PRIME X299-A II
- CPU
- i9 10940X
- Graphics
- AMD Radeon RX 6800 XT
- Mac
- Mobile Phone
So today I started to look at getting Emulated NVRAM working due to my broken NVRAM - mainly just for convenience of setting my default startup volume to MacOS instead of windows but I don't think this is working correctly on Big Sur either, I could be wrong.
So, as always, followed the Dortania guide to the letter, set config.plist variables for Emulated NVRAM, saved the LogoutHook.command, "sudo default write com.apple...." etc.
It does successfully create an nvram.plist but on inspection this appears to be missing the expected variables for saving boot order items.
I then ran the command directly in terminal and seems that it cannot find those boot variables - I don't know if this is expected because the command is only designed to run during logout not from a user session, or whether Big Sur is storing them differently somehow causing it not to work.
Anyway here is the command being run and the resulting nvram.plist missing those variables. And also the nvram.plist looks same if I delete it, then let the LogoutHook.command create it during a normal shutdown:
My guess is that Big Sur stores these variables either somewhere else or in a different format?
Also @TheBloke possibly of separate interest here is that the LogoutHook.command seems to create an "msu-product-url" key like we use to manually work around our broken NVRAM on install - do you think that once installed, with working Emulated NVRAM that this may ensure future upgrades will work correctly if they end up requiring this key?
Edit: Running "sudo nvram -p" after reboot confirms that Opencore is successfully writing the nvram.plist variables to nvram - so I think the emulated NVRAM process itself is working, just that LogoutHook.command isn't successfully retrieving the variables.
So, as always, followed the Dortania guide to the letter, set config.plist variables for Emulated NVRAM, saved the LogoutHook.command, "sudo default write com.apple...." etc.
It does successfully create an nvram.plist but on inspection this appears to be missing the expected variables for saving boot order items.
I then ran the command directly in terminal and seems that it cannot find those boot variables - I don't know if this is expected because the command is only designed to run during logout not from a user session, or whether Big Sur is storing them differently somehow causing it not to work.
Anyway here is the command being run and the resulting nvram.plist missing those variables. And also the nvram.plist looks same if I delete it, then let the LogoutHook.command create it during a normal shutdown:
My guess is that Big Sur stores these variables either somewhere else or in a different format?
Also @TheBloke possibly of separate interest here is that the LogoutHook.command seems to create an "msu-product-url" key like we use to manually work around our broken NVRAM on install - do you think that once installed, with working Emulated NVRAM that this may ensure future upgrades will work correctly if they end up requiring this key?
Edit: Running "sudo nvram -p" after reboot confirms that Opencore is successfully writing the nvram.plist variables to nvram - so I think the emulated NVRAM process itself is working, just that LogoutHook.command isn't successfully retrieving the variables.
Last edited: