Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Try not opening the config.plist with OpenCore Configurator and just using the EFI as-is without your serial, board serial, or UUID.

Also try redoing your macOS installer USB flash drive.
Thanks,

I formatted a new USB drive and pasted your EFI folder (as it was with no changes and not opening the config file with anything) to the EFI partition on the drive. Booted from it after pressing F12 and the same OCS: No schema for SerialInit at 5 index, context <Debug>! error appeared at the top of the Gigabyte window. The OC picker window still loaded, and when I selected the Big Sur drive on the OC picker, the white bar under the apple logo went probably a third of the way along then the computer reset, as it had done previously.

Oddly, I tried exactly the same with OC 0.7.9 (the previous version you have supplied on page 1) and it worked fine on the same flash drive. I was able to update my serial numbers etc and it worked grand.

OC 0.8.0 is not liking my system for some reason.

I then checked the config file with PlistEdit pro (trial version that has expired so I cannot edit the file) and the SerialInit key is set to false. not sure what else to try!
 
Thanks,

I formatted a new USB drive and pasted your EFI folder (as it was with no changes and not opening the config file with anything) to the EFI partition on the drive. Booted from it after pressing F12 and the same OCS: No schema for SerialInit at 5 index, context <Debug>! error appeared at the top of the Gigabyte window. The OC picker window still loaded, and when I selected the Big Sur drive on the OC picker, the white bar under the apple logo went probably a third of the way along then the computer reset, as it had done previously.

Oddly, I tried exactly the same with OC 0.7.9 (the previous version you have supplied on page 1) and it worked fine on the same flash drive. I was able to update my serial numbers etc and it worked grand.

OC 0.8.0 is not liking my system for some reason.

Open the 0.8.0 config.plist with TextEdit and use Find to search for "SerialInit". Then delete the follow that's highlighted in blue.

Screen Shot 2022-05-27 at 6.48.22 PM.png

But that will not change anything that matters.
 
Hey Pastrychef,
I have a Clover build with a Z390 Designare and Radeon VII. I managed to get it working pretty good. However, this is my workhorse, and it needs to be as reliable and fast as possible. Is it possible to check my EFI folder to see if things are OK?

Second, how do I check if NVRAM is working?

Hoping to hear from you, Aris.
 
Hey Pastrychef,
I have a Clover build with a Z390 Designare and Radeon VII. I managed to get it working pretty good. However, this is my workhorse, and it needs to be as reliable and fast as possible. Is it possible to check my EFI folder to see if things are OK?

Second, how do I check if NVRAM is working?

Hoping to hear from you, Aris.

Yeah, please upload your EFI.

If you didn't disable CFG lock in BIOS, you can assume that NVRAM is not working.
 
Yeah, please upload your EFI.

If you didn't disable CFG lock in BIOS, you can assume that NVRAM is not working.
That's awesome man! It is attached. I'm getting pretty reasonable geek scores.
I use BIOS F6n, is it wise to flash it to F9?
Thanks again! Let me know if I can do something in return.

Aris
 

Attachments

  • EFI.zip
    4.5 MB · Views: 54
That's awesome man! It is attached. I'm getting pretty reasonable geek scores.
I use BIOS F6n, is it wise to flash it to F9?
Thanks again! Let me know if I can do something in return.

Aris

Not sure if the BIOS versions for your motherboard correspond to the Z390M Gaming... But F9L ran really good for me.

Also, please update your profile to show which motherboard, CPU, and GPU you are currently using.

What version of macOS are you running?
 
That's awesome man! It is attached. I'm getting pretty reasonable geek scores.
I use BIOS F6n, is it wise to flash it to F9?
Thanks again! Let me know if I can do something in return.

Aris

You were definitely using emulated NVRAM...

Update to a version of BIOS that allows you to disable CFG Lock and try the attached EFI from a USB flash drive.
 

Attachments

  • EFI.zip
    7 MB · Views: 53
Thanks a bunch! Will do.
 
You were definitely using emulated NVRAM...

Update to a version of BIOS that allows you to disable CFG Lock and try the attached EFI from a USB flash drive.
Apart from the Emulated NVRAM, were there bad settings/drivers/kexts that made performance worse?
 
Apart from the Emulated NVRAM, were there bad settings/drivers/kexts that made performance worse?

Not really. Most of the time, that sort of stuff shouldn't affect performance. Performance is more dependent on your hardware and BIOS settings.
 
Back
Top