Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,046
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
I don't recall, to be honest. I'm guessing not? Clover tells me it is 4934.

Update to the latest EFI from post #1.
Copy/paste your Serial, Board Serial, and UUID from your old config.plist to the one included in the new EFI.
 
Joined
May 3, 2019
Messages
67
Motherboard
Gigabyte Z390 Gaming X
CPU
i9-9900K
Graphics
RX 5700 XT
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. iOS
Since a few day I am struggling with Big Sur 11.3.1. I get following kernel panic and the system freezes. How could I possibly fix it ?

panic(cpu 0 caller 0xffffff8002ac2838): nvme: "Fatal error occurred. CSTS=0x3 US[1]=0x0 US[0]=0x4a VID=0x144d DID=0xa808
. FW Revision=2B2QEXE7\n"@/System/Volumes/Data/SWE/macOS/BuildRoots/2288acc43c/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-557.100.13/Common/IONVMeController.cpp:5499
Backtrace (CPU 0), Frame : Return Address
0xffffffa109053960 : 0xffffff800028e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa1090539b0 : 0xffffff80003d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa1090539f0 : 0xffffff80003c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa109053a40 : 0xffffff8000232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa109053a60 : 0xffffff800028d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa109053b80 : 0xffffff800028db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa109053bf0 : 0xffffff8000a9d68a mach_kernel : _panic + 0x54
0xffffffa109053c60 : 0xffffff8002ac2838 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController14CommandTimeoutEP16AppleNVMeRequest.cold.1
0xffffffa109053c80 : 0xffffff8002aa7433 com.apple.iokit.IONVMeFamily : __ZN16IONVMeController13FatalHandlingEv + 0x1af
0xffffffa109053de0 : 0xffffff80009f54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa109053e50 : 0xffffff80009f53f6 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc6
0xffffffa109053e80 : 0xffffff80002d44b5 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffa109053ef0 : 0xffffff80002d5424 mach_kernel : _thread_call_delayed_timer + 0x1414
0xffffffa109053fa0 : 0xffffff800023213e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IONVMeFamily(2.1)[2A44DC48-B629-386C-985E-3BE03CCA48F2]@0xffffff8002aa0000->0xffffff8002ac9fff
dependency: com.apple.driver.AppleEFINVRAM(2.1)[C6EE02AA-79D2-3EF8-83A6-9E52549E16D9]@0xffffff80016fe000->0xffffff8001707fff
dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[9B4B41D7-B68F-33D5-80A4-2C4C4A649F6D]@0xffffff80018b8000->0xffffff80018cdfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[B99B3B05-71B8-3178-8C27-E0A0ACA9F16E]@0xffffff8002d5f000->0xffffff8002d87fff
dependency: com.apple.iokit.IOReportFamily(47)[3F7604AB-EA65-3904-A1F4-AFEB25D288A7]@0xffffff8002d96000->0xffffff8002d98fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[58EA4506-4E6B-3AC3-A70D-ED35EE2C381D]@0xffffff8002e62000->0xffffff8002e73fff

Process name corresponding to current thread: kernel_task
Boot args: -alcid=18 -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta brcmfx-country=DE darkwake=0

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 390329616930
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000005ae1754e87
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001f0c97230c 0x0000000000000000
I had the same issue with the 970 EVO 1TB on my z390 Gaming X. I went away when I switched my SSDs. I moved the 970 from the secondary slot (bottom one) to the primary (top one) and the 960 vice versa. It went away after that. No idea it is was a lucky shot but worth a try.
 
Joined
Jun 17, 2011
Messages
45
Motherboard
Gigabyte z390 m gaming
CPU
i5-9600k
Graphics
Vega 56
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Ok. I've downloaded the efi-clover-5134-z390m-zip file. I assume that is the most current, having the highest build number?

Using the config.plist in your file, I mounted my EFI partition, navigated to EFI/Clover/ and opened the config.plist there. It is dated Oct 20, 2019, which seems like about when I originally tried to update MacOS.

In the SMBIOS section, I show iMac19,2 and an IM192.whatever Bios Version, and an SN under System.

Everything under 'board' is blank, and smUUID is also blank.

Am I looking in the wrong place?

Is the system serial number and hardware UUID I show in the Hardware Overview in System Report the SN/UUID that I want? Or do I need to generate new if I'm switching profiles to iMac Pro 1,1?
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,046
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Ok. I've downloaded the efi-clover-5134-z390m-zip file. I assume that is the most current, having the highest build number?

Using the config.plist in your file, I mounted my EFI partition, navigated to EFI/Clover/ and opened the config.plist there. It is dated Oct 20, 2019, which seems like about when I originally tried to update MacOS.

In the SMBIOS section, I show iMac19,2 and an IM192.whatever Bios Version, and an SN under System.

Everything under 'board' is blank, and smUUID is also blank.

Am I looking in the wrong place?

Is the system serial number and hardware UUID I show in the Hardware Overview in System Report the SN/UUID that I want? Or do I need to generate new if I'm switching profiles to iMac Pro 1,1?

Use either iMac19,1 or iMacPro1,1.

If you want to keep using iMac19,2, you will have to redo the USB ports kext.
 
Joined
Jun 17, 2011
Messages
45
Motherboard
Gigabyte z390 m gaming
CPU
i5-9600k
Graphics
Vega 56
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Use either iMac19,1 or iMacPro1,1.

If you want to keep using iMac19,2, you will have to redo the USB ports kext.
Got it. I don't mind switching.

Does that mean I just need to generate a new SN and SmUUID in your config.plist, generate config, and then copy/paste the contents of your EFI folder into my EFI folder, reboot, and continue the os install? Or is there something more I need to do?
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,046
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Got it. I don't mind switching.

Does that mean I just need to generate a new SN and SmUUID in your config.plist, generate config, and then copy/paste the contents of your EFI folder into my EFI folder, reboot, and continue the os install? Or is there something more I need to do?

Yes, I always suggest generating new Serial, Board Serial, UUID when switching system definitions.

Nothing else to do.
 
Joined
Jan 5, 2020
Messages
202
Motherboard
Gigabyte Z390 Gaming M
CPU
i9-9900K
Graphics
RX 590
Mac
  1. MacBook Pro
I have been having issues with "Bluetooth Not Available" when my machine wakes from sleep. It wouldn't happen every time, but usually once a day. I would either need to restart or let the machine go back to sleep and usually that would resolve it. It seems like it started happening at some point and I couldn't pinpoint when. Anyways, long story short, I disabled the USBWakeFixup.kext and SSDT-USBW.dsl and it hasn't happened in 12 days. Now I have to click on the mouse a couple times to wakeup the screen, but that is much better than not having my bluetooth keyboard or mouse not available at random times. I have the Fenvi bluetooth/wifi card. Just throwing this out there in case anyone else is having this issue. I am not using pastry chef's EFI, but one I created myself from scratch following the dortania guide(I wanted to boost my mackintosh knowledge).

I am going to see if I can hit 14 days of uptime. If I do, I'll try reenabling the SSDT-USBW.aml and USBWakeFixup.kext and see if the problem reappears.

Screen Shot 2021-05-23 at 12.25.49 PM.png
 
Joined
Jun 17, 2011
Messages
45
Motherboard
Gigabyte z390 m gaming
CPU
i5-9600k
Graphics
Vega 56
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Ok - updated clover and 10.15.7 installed, I'm running, but I have a few issues:

1. Clover says there is a problem in config.plist, checking the log:

0:105 0:000 Using config.plist at path: \EFI\CLOVER
0:105 0:000 There is problems in plist '\EFI\CLOVER\config.plist'
0:106 0:000 Warning: Boolean value contained in a string. Please use <true/> instead of <string>yes</string> for tag '/SystemParameters/InjectKexts:679'
0:107 0:001 Use CloverConfigPlistValidator or look in the log
3:108 3:000 Cannot find smbios.plist at path '\EFI\CLOVER' : Not Found
3:108 0:000 '\EFI\CLOVER\smbios.plist' not loaded. Efi error Not Found

Once I've booted up, I have these issues:

2. I think it borked my USB 3.1 port on the back of the motherboard and one of the ports on the top of my case. The other two ports on the back, and three of the four on the top of the case work fine.
3. wi-fi is working, but bluetooth has gone offline - it says not available in the top bar, and no information found in system report. MY BT/Wi-fi card is a FENVI FV-HB1200 that worked perfectly beforehand, including iMessage.

Suggestions on where I should start to fix this?
 
Last edited:

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,046
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
I have been having issues with "Bluetooth Not Available" when my machine wakes from sleep. It wouldn't happen every time, but usually once a day. I would either need to restart or let the machine go back to sleep and usually that would resolve it. It seems like it started happening at some point and I couldn't pinpoint when. Anyways, long story short, I disabled the USBWakeFixup.kext and SSDT-USBW.dsl and it hasn't happened in 12 days. Now I have to click on the mouse a couple times to wakeup the screen, but that is much better than not having my bluetooth keyboard or mouse not available at random times. I have the Fenvi bluetooth/wifi card. Just throwing this out there in case anyone else is having this issue. I am not using pastry chef's EFI, but one I created myself from scratch following the dortania guide(I wanted to boost my mackintosh knowledge).

I am going to see if I can hit 14 days of uptime. If I do, I'll try reenabling the SSDT-USBW.aml and USBWakeFixup.kext and see if the problem reappears.

View attachment 519455

I still have the USBWakeFix and SSDT. Everything's working fine here.

Screen Shot 2021-05-23 at 3.55.39 PM.png
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,046
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
Ok - updated clover and 10.15.7 installed, I'm running, but I have a few issues:

1. Clover says there is a problem in config.plist: Warning Boolean value contained in a string, please use <true/> instead of <string>yes</string>.... I didn't catch all of it, but it ends in Parameters/InjectKexts:679 and says 'use cloverconfigplistvalidator or look in the log.'

I'm guessing perhaps that has something to do with the following:

2. I think it borked my USB 3.1 port on the back of the motherboard.
3. wi-fi is working, but bluetooth has gone offline - it says not available in the top bar, and no information found in system report. I have a FENVI FV-HB1200, that worked perfectly beforehand, including iMessage and so on.

Suggestions on where I should start to fix this?

Try using latest version of Clover Configurator or using a plist editor.
 
Top