MP 1,1-5,1 Healthy NVRAM normal behaviour on 4,1->5,1 machines

[basslik]

I would strip those down to just a fresh and empty user. To keep for tests.

But what has this to do with firmware and NVRAM ???

I read post #178,

You mentioned something about heavy use of the NVRAM running Opencore or Multiple OS.

I'm running both, multiple OS's and OpenCore.

Please forgive me it was not firmware related.

 

[Macschrauber]

I read post #178,

You mentioned something about heavy use of the NVRAM running Opencore or Multiple OS.

I'm running both, multiple OS's and OpenCore.

Please forgive me it was not firmware related.

View attachment 2521474

This is a general data point, the more variables are in the NVRAM, the more often Garbage Collection runs.

Using multiple OS will fill the NVRAM more, a more populated NVRAM will do Garbage Collection more often than running a single, even supported, OS.

I refer to crossflashes, from 4,1 to 5,1 with the Netkas script / method. They tend to suffer more from NVRAM damage. More GC, more risk, GC could fail.

This is the logic behind that.

If you have a bootscreen capable GPU (EnableGop or EFI doesnt matter) and you are concerned about filling the NVRAM with a lot of variables, just do a deep NVRAM Reset (hold cmd-alt-p-r continuously until it chimes 3 times) before changing OS.

You will need to re-select OpenCore as initial bootloader, after a deep NVRAM reset, so the bootscreen helps a lot.

There is no general need for that, but it will keep the amount of Garbage Collections as low as possible.


Here is the post, showing what NVRAM Garbage Collection is: https://forums.macrumors.com/posts/32100306/