[SOLVED] Nvram.plist file in Update volume

[miliuco]

I have Big Sur beta 10 on my system. I also have native NVRAM thanks to SSDT-PMC.aml file. I have seen that a nvram.plist file appears in /System/Volumes/Update volume root folder.


This file has many keys, very different of keys founded in Hackintool or with nvram -p command.

If I delete it, everything seems to work fine. It is not created again at next boot.
It happens to someone else? Is it something new in Big Sur? Does it mean that maybe I don't have native NVRAM although I think I do?

 

[miliuco]

I have observed that this file appears after installing or reinstalling Big Sur, most of its keys are related to the installation or update process. It appears to be a file to save NVRAM settings during Big Sur install process.
With nvram -p command, when Big Sur installation is finished, it shows same keys that are in the nvram.plist file on the Update volume.

% /Users/yo > nvram -p
efi-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>783E0B07-E853-45BF-BC26-32199C279DE8</string></dict></dict><key>BLLastBSDName</key><string>disk2s4</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\6288F631-B83F-4ABD-A0DE-6A37070DEF95\System\Library\CoreServices\boot.efi</string></dict></array>%00
boot-args 
efi-backup-boot-device    <array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>783E0B07-E853-45BF-BC26-32199C279DE8</string></dict></dict><key>BLLastBSDName</key><string>disk2s4</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\6288F631-B83F-4ABD-A0DE-6A37070DEF95\System\Library\CoreServices\boot.efi</string></dict></array>
GPUROM    NUPD
ota-controllerVersion    SUMacController-1.10%00
ota-updateType    incremental%00
auto-boot    true
bluetoothInternalControllerInfo    %8d%82%ac%05%000b%14%88c%df%8a'%c7
prev-lang:kbd    %00
run-efi-updater    No%00
multiupdater-state    %01%00%00%00%00%00%00%00%00%00%00%00
multiupdater-retry-limits    %01%00%00%00%00%00%00%00
IONVRAM-FORCESYNCNOW-PROPERTY    auto-boot
fmm-computer-name    BigSUR2
bluetoothActiveControllerInfo    %8d%82%ac%05%00%00%000b%14%88c%df%8a'%c7
csr-active-config    %00%00%00%00
SystemAudioVolume    %14
efi-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00 %19%16%1d%00%00%00%009)%d2H%07%82%a8M%ae%9e%9c%9a%08[%09%18%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%07%0b>xS%e8%bfE%bc&2%19%9c'%9d%e8%04%04%9a%00\%006%002%008%008%00F%006%003%001%00-%00B%008%003%00F%00-%004%00A%00B%00D%00-%00A%000%00D%00E%00-%006%00A%003%007%000%007%000%00D%00E%00F%009%005%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00
efi-backup-boot-device-data    %02%01%0c%00%d0A%03%0a%00%00%00%00%01%01%06%00%00%17%03%12%0a%00%00%00%00%00%00%00%04%01*%00%02%00%00%00(@%06%00%00%00%00%00 %19%16%1d%00%00%00%009)%d2H%07%82%a8M%ae%9e%9c%9a%08[%09%18%02%02%04%03$%00%f7%fct%be|%0b%f3I%91G%01%f4%04.hB%07%0b>xS%e8%bfE%bc&2%19%9c'%9d%e8%04%04%9a%00\%006%002%008%008%00F%006%003%001%00-%00B%008%003%00F%00-%004%00A%00B%00D%00-%00A%000%00D%00E%00-%006%00A%003%007%000%007%000%00D%00E%00F%009%005%00\%00S%00y%00s%00t%00e%00m%00\%00L%00i%00b%00r%00a%00r%00y%00\%00C%00o%00r%00e%00S%00e%00r%00v%00i%00c%00e%00s%00\%00b%00o%00o%00t%00.%00e%00f%00i%00%00%00%7f%ff%04%00

But after cleaning NVRAM with the command sudo nvram -c or from the OpenCore menu, nvram -p shows the expected values even though nvram.plist still exists in Update.