Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

Joined
Jan 19, 2019
Messages
24
Motherboard
Gigabyte Z390 M GAMING
CPU
i7-8700K
Graphics
RX 560
Mac
  1. iMac
  2. MacBook Pro
Mobile Phone
  1. iOS
If it's a 970 EVO, it's fine. I also use one of these.

If it's a 970 EVO Plus, make sure you have the latest firmware installed on the SSD.
Thanks. Any Idea why my sistem crashes? Any kextnor driver maybe? Could it be related tonthe temperature of the nvme?
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,479
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
Thanks. Any Idea why my sistem crashes? Any kextnor driver maybe? Could it be related tonthe temperature of the nvme?

I don't see any problems with your kexts or drivers. It's definitely NVMe SSD related.

Please see:
 
Joined
Sep 10, 2017
Messages
320
Motherboard
Gigabyte Z590M GAMING X
CPU
i9-10900
Graphics
Vega 56+UHD 630
Mac
  1. MacBook Pro
  2. Mac Pro
Classic Mac
  1. Power Mac
Mobile Phone
  1. Android
  2. iOS
Find which USB port it is on and disable the USB port in your USB kext.
So, in this case the BT USB dongle is working. What is not working is the BT 5.0 of the Intel AC9560 CNVi connector.
The way will be to remove this Wifi Card, as it is still limited by speed.
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,479
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
The way will be to remove this Wifi Card, as it is still limited by speed.

No. Just disable the USB port where the Intel bluetooth is connected.
 
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
Would someone be so kind as to assume (not-incorrectly) that I have little idea of what I'm doing, and walk me through the updating process?

In mid 2019 I built an i5-9600K on the Gigabyte Z390 M Gaming board, and a Radeon Vega 56. I got it running 10.15, and for a variety of reasons never quite figured out how to run the update. The 10.15 install is on its own M.2 drive. It runs fine, but I've finally gotten really tired of the OS complaining that I have updates that need run.

I made it through the installation of the update for.... I think 10.15.1 or whatever the first sequential update was. I downloaded it, started the install process but never could get past that first or second reboot to finish the install.

Currently, when I boot into clover, I have 5 partitions visible on this M.2 drive.
1. APFS - Boot macOS Install prebooter from preboot.
2. APFS - Boot FileVault prebooter from preboot.
3. APFS - Boot MacOS install from Hackintosh HD - Data.
4. Recovery - Boot Recovery from Recovery.
5. Boot macOS from Hackintosh HD. (This is the one I booted into in order to write this post).

Where do I go from here?

Thanks.
 
Last edited:

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,479
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
Would someone be so kind as to assume (not-incorrectly) that I have little idea of what I'm doing, and walk me through the updating process?

In mid 2019 I built an i5-9600k on the Gigabyte z390 M Gaming board, and a Radeon Vega 56. I got it running 10.15, and for a variety of reasons never quite figured out how to run the update. The 10.15 install is on its own m2 drive. It runs fine, but I've finally gotten really tired of the OS complaining that I have updates that need run.

I made it through the installation of the update for.... I think 10.15.1 or whatever the first sequential update was. I downloaded it, started the install process but never could get past that first or second reboot to finish the install.

Currently when I boot into clover, I have 5 partitions visible on this m2 drive.
1. APFS - Boot macOS Install prebooter from preboot.
2. APFS - Boot FileVault prebooter from preboot.
3. APFS - Boot MacOS install from Hackintosh HD - Data.
4. Recovery - Boot Recovery from Recovery.
5. Boot macOS from Hackintosh HD. (This is the one I booted into in order to write this post).

Where do I go from here?

Thanks.

Assuming you've already updated your Clover EFI, just keep selecting APFS - Boot macOS Install rebooter from preboot until it's no longer there.
 
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
Assuming you've already updated your Clover EFI, just keep selecting APFS - Boot macOS Install rebooter from preboot until it's no longer there.
I don't recall, to be honest. I'm guessing not? Clover tells me it is 4934.
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
17,479
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
69
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?
 
Top