- Joined
- Feb 28, 2020
- Messages
- 18
- Motherboard
- Asus X99 Deluxe
- CPU
- E5 1660 v3
- Graphics
- Asus 5700XT reference model
Hello everyone,
My build is based on Asus X99 Deluxe which does have a nvram but not compatible with Mac. As a result, I need to do the emulated NVRAM.
I followed this guide "https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/extras/nvram"
and BTW I'm installing Catalina with Opencore 0.5.6.
The guide instructs me to have a precheck on the native NVRAM and surely it doesn't work as I mentioned it's not compatible with Mac as most X99 board.
"
sudo -s
sudo nvram -c
sudo nvram myvar=test
exit
Now reboot and run this:
nvram -p | grep -i myvar
"
After that, I followed all the steps to modify my config.plist(please notice I didn't touch anything under LegacySchema section) and use LogoutHook.command as well.
Now I see the nvram.plist is generated right under my EFI partition and it is getting updated every boot. (you can check the created timestamp & modified timestamp below)
However, if I perform the test again:
sudo nvram myvar=test
then restart and run:
nvram -p | grep -i myvar
It still shows nothing to me. But the interesting part is the property "myvar" is actually in the nvram.plist if you mount the EFI folder and check the content.
And finally, if I perform a reboot again and check the nvram.plist content, the "myvar" disapears from the list.
At this stage, I'm not sure if the emulated nvram is working or not and currently I don't have extra disks to select the startup disk to demostrate it's working.
Anyone knows this is the expected behavior or still there is something wrong?
My build is based on Asus X99 Deluxe which does have a nvram but not compatible with Mac. As a result, I need to do the emulated NVRAM.
I followed this guide "https://khronokernel-2.gitbook.io/opencore-vanilla-desktop-guide/extras/nvram"
and BTW I'm installing Catalina with Opencore 0.5.6.
The guide instructs me to have a precheck on the native NVRAM and surely it doesn't work as I mentioned it's not compatible with Mac as most X99 board.
"
sudo -s
sudo nvram -c
sudo nvram myvar=test
exit
Now reboot and run this:
nvram -p | grep -i myvar
"
After that, I followed all the steps to modify my config.plist(please notice I didn't touch anything under LegacySchema section) and use LogoutHook.command as well.
Now I see the nvram.plist is generated right under my EFI partition and it is getting updated every boot. (you can check the created timestamp & modified timestamp below)
However, if I perform the test again:
sudo nvram myvar=test
then restart and run:
nvram -p | grep -i myvar
It still shows nothing to me. But the interesting part is the property "myvar" is actually in the nvram.plist if you mount the EFI folder and check the content.
And finally, if I perform a reboot again and check the nvram.plist content, the "myvar" disapears from the list.
At this stage, I'm not sure if the emulated nvram is working or not and currently I don't have extra disks to select the startup disk to demostrate it's working.
Anyone knows this is the expected behavior or still there is something wrong?