Gigabyte Z390 M Gaming build with working NVRAM

[nottooshabby]

Pastrychef - I built an EFI from scratch following the Open Core guide. I have the bare minimum in terms of EFIs and Kexts loaded. One thing that is missing is when I plug an external drive in, I do not get the yellow icon that indicates it's an external drive. Which EFI or Kext enables that functionality?

 

[jiffyslot]

Yes. Enter that without the colons.

One more question about that ROM value in the OC EFI: On these Gigabyte Z390 systems, should we be using the native Intel i219 ethernet hardware address as opposed to, say the Intel i211 Pro/1000?

This is for the EFI<OC<Config<PlatformInfo<Generic<ROM<Data = colonless hardware address such as b22s93d713m.

Thanks for the clarity.

 

[pastrychef]

One more question about that ROM value in the OC EFI: On these Gigabyte Z390 systems, should we be using the native Intel i219 ethernet hardware address as opposed to, say the Intel i211 Pro/1000?

This is for the EFI<OC<Config<PlatformInfo<Generic<ROM<Data = colonless hardware address such as b22s93d713m.

Thanks for the clarity.

Look in System Information > Network. Use EN0.

 

[pastrychef]

Pastrychef - I built an EFI from scratch following the Open Core guide. I have the bare minimum in terms of EFIs and Kexts loaded. One thing that is missing is when I plug an external drive in, I do not get the yellow icon that indicates it's an external drive. Which EFI or Kext enables that functionality?

I never had to do anything to make external drives appear as external with OpenCore. It always just worked...

 

[nottooshabby]

All the sudden my computer, if I turn off the power supply, then turn it back on again and power up the machine, all the lights and fans come on for a second, then they all turn off, then they all come back on again and the computer boots up normally. It's like it is doing some kind of hardware check, similar to when you update bios. I don't know if this started after upgrading to F9L or something to do with trying out a different open core setups. I am back to my normal open core setup but it still does it. Any ideas? Is it something with F9L? Could one of my bioses be corrupt and it's falling back to the backup?

I plugged in a speaker to the motherboard. I am getting one short beep on boot up. Is that Normal or a Memory error? I looked up motherboard beeps and for the AMI bios one short beep is a memory error. For the AWARD bios, one short beep is normal. The manual states we have the AMI bios. Is that right? Is one short beep normal?

 

[pastrychef]

I plugged in a speaker to the motherboard. I am getting one short beep on boot up. Is that Normal or a Memory error? I looked up motherboard beeps and for the AMI bios one short beep is a memory error. For the AWARD bios, one short beep is normal. The manual states we have the AMI bios. Is that right? Is one short beep normal?

I always have a short beep on boot. This is also true for my Asus z370 motherboard.

 

[LiveSorcerer]

@pastrychef , the Opencore 0.6.3 stuck in this screen.

 

[pastrychef]

@pastrychef , the Opencore 0.6.3 stuck in this screen.

That's the same thing @esse has been hitting. I don't know the cause... Have you tried booting in to recovery and re-installing macOS on top of your current installation?

 

[BrooklynHack]

BIOS F9l won't POST if I change settings from optimized

I just built a new system using most of the components that pastrychef recommended. After a few fails, I managed to update the BIOS to F9l from the original F8. After I change the BIOS settings to those listed in the first posting for the Gigabyte Z 390 M Gaming mobo:

Advanced Mode > Settings > IO Ports > Initial Display Output > PCIe 1 Slot
Advanced Mode > Settings > IO Ports > Above 4G Decoding > Enabled
Advanced Mode > Settings > IO Ports > USB Configuration > XHCI Hand-off > Enabled
Advanced Mode > Boot > CSM Support > Disabled
Settings > IO Ports > Super IO Configuration > Serial Port > Disabled
Boot > CFG Lock > Disabled (MSR unlock)

the system will not boot up, just hangs at black screen no text even if verbose is on. The only recovery is to turn off computer, short out the Clear CMOS mobo pins, reset bios, and reload optimized settings. If I boot with those optimized settings, I can get to the MacOS loading screen but that gets stuck at about 10%. I used my MBP to copy the EFI folder from one of the most recent Clover uploads provided in original posting to the 970 EVO. And I used Clover Configurator to change some of the settings (iMacPro1,1 system definition, Serial, Board Serial, UUID) before installing it in the new HackPro.

Any ideas?

 

[LiveSorcerer]

I removed the Disable driver, and the reset returned to work, but the shutdown, instead of shutting down, restarts.