Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

This is great intel! Appreciate the quick responses for the community! Been living without a modded Titan Ridge card until now but the benefits to have Thunderbolt are worthwhile considering how much more devices continue to use it and the roadblocks I have been hit with.

In essence, the EFI that Pastrychef has provided should be sufficient enough for the thunderbolt which means I simply need to mod the Titan card firmware following the SPI flash post instructions. I have had some experience flashing with SPI in the past when soldering 8 pins from a Prius 2004-2009 odometer cluster board and programing the mileage to correct spec by modifying hex digits for replaced dashboards. It literally follows the same similar protocol with 3.3v and 5v scenarios.

Used "HiLetgo 51 Microcontroller Programmer SP200SE USB Burner Support AT89C52 24C02 93C46 300 Variety of Chips" from amazon as well as "AiTrip CH341A 24 25 Series EEPROM Flash BIOS USB Programmer + SOIC8 SOP8 Clip Adapter Module".

This is truly the Hackintosh community when you go about "hacking" the hardware and tinkering with stuff :D

If you flash your Thunderbolt card, replace the SSDT with one that's needed with flashed Thunderbolt cards.
 
Hi @pastrychef , could you ask a question?
After switching from SSD to NVMe I'm still having kernel panic from NVME.
panic(cpu 6 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x316 VID=0x144d DID=0xa808
So, what is happening is that there would be a possibility that the GPU is interfering with NVMe, because it is using the same PCIe channel?
Because what is happening here, my Vega 56 is giving white screen in Windows 10, freeze a few times, having to restart manually.
And I noticed that the GPU has some corrosion points.
The chances of this kernel panic happening on MacOS and freeze on Windows 10 due to this?
 
Hi @pastrychef , could you ask a question?
After switching from SSD to NVMe I'm still having kernel panic from NVME.
panic(cpu 6 caller 0xffffff8002ace860): nvme: "Fatal error occurred. CSTS=0xffffffff US[1]=0x0 US[0]=0x316 VID=0x144d DID=0xa808
So, what is happening is that there would be a possibility that the GPU is interfering with NVMe, because it is using the same PCIe channel?
Because what is happening here, my Vega 56 is giving white screen in Windows 10, freeze a few times, having to restart manually.
And I noticed that the GPU has some corrosion points.
The chances of this kernel panic happening on MacOS and freeze on Windows 10 due to this?

If your system is freezing in Windows too, it's possible there's some sort of hardware issue. The GPU should not be using the same PCE-e lanes as the NVMe SSD.

Maybe try running with IGPU only for a bit and see if you still get the freezes.
 
Hey all, I'll be building one of these this weekend, but I'm having trouble locating the official f9l bios download... I found one on a random online site, but I don't trust it. I've searched this thread over and over, and can't find where on Gigabyte's site you can download an older version...obviously, only f9k is posted there (and in post#1 here).
Thanks in advance!
J
 
Hey all, I'll be building one of these this weekend, but I'm having trouble locating the official f9l bios download... I found one on a random online site, but I don't trust it. I've searched this thread over and over, and can't find where on Gigabyte's site you can download an older version...obviously, only f9k is posted there (and in post#1 here).
Thanks in advance!
J

I got this from the Gigabyte website when it was still the latest version...
 

Attachments

  • Z390MGAMING.F9l.zip
    6.7 MB · Views: 32
I got this from the Gigabyte website when it was still the latest version...
That's much appreciated, thanks! Having (mostly) followed along Casey's Designare thread over the years, I expect I'll be here frequently... I wonder how much applies given they're both Gigabyte z390 boards?

Also, I hope you don't mind I ask a couple of clarity questions:

I'll probably weed out some things in drivers and kexts -- especially the deactivated ones (this will be an open core build of course), but I'm wondering about all the fancy DeviceProperty definitions you have. I see a TON of "Cannon Lake" PCH items, and (admittedly not knowing as much as you) I wonder how those all came about as they're pretty custom. I also have no idea what the PCI bridge, Xeon E3-1200 one does.

Further, you have some boot arguments that are unfamiliar to me (specifically all the "beta" arguments).

I'll keep googling all this stuff to better educate myself, but appreciate any and all clarification.

Thank you so very much for creating this, and following through with helping all of us hay-seeds!

Best,
Jason
 
That's much appreciated, thanks! Having (mostly) followed along Casey's Designare thread over the years, I expect I'll be here frequently... I wonder how much applies given they're both Gigabyte z390 boards?

Also, I hope you don't mind I ask a couple of clarity questions:

I'll probably weed out some things in drivers and kexts -- especially the deactivated ones (this will be an open core build of course), but I'm wondering about all the fancy DeviceProperty definitions you have. I see a TON of "Cannon Lake" PCH items, and (admittedly not knowing as much as you) I wonder how those all came about as they're pretty custom. I also have no idea what the PCI bridge, Xeon E3-1200 one does.

Further, you have some boot arguments that are unfamiliar to me (specifically all the "beta" arguments).

I'll keep googling all this stuff to better educate myself, but appreciate any and all clarification.

Thank you so very much for creating this, and following through with helping all of us hay-seeds!

Best,
Jason

The stuff that's disabled is just me being lazy and not cleaning it up. If it's disabled, it's not doing anything anyway.

The PCI stuff is all from Hackintool.

All the "beta" boot arguments just allow the kexts to work even with non-whitelisted macOS versions.
 
Hello ! Thanks for your hardwork and update, i have almost the same build as you and your EFI but i have a problem. When my mac is on lockscreen for fews hours without use and i wake up its crash after 5-10 mins, i have this error :
panic(cpu 0 caller 0xffffff8000a89d2a): Wake transition timed out after 180 seconds while calling power state change callbacks. Suspected bundle: com.apple.iokit.IOPCIFamily. Thread 0x1f0ef.
Failure code:: 0x00000200 00000027

Backtracing specified thread
Backtrace (CPU 0), Frame : Return Address
0xffffffc0f35fb848 : 0xffffff80003e878b mach_kernel : _machine_switch_context + 0xcb
0xffffffc0f055bc60 : 0xffffff80002de972 mach_kernel : _thread_unstop + 0x14d2
0xffffffc0f055bcd0 : 0xffffff80002dd40f mach_kernel : _thread_block_reason + 0xaf
0xffffffc0f055bd20 : 0xffffff80002cd478 mach_kernel : _lck_mtx_sleep + 0x68
0xffffffc0f055bd60 : 0xffffff8002c26e94 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge11tunnelsWaitEP11IOPCIDevice + 0xa4
0xffffffc0f055bd80 : 0xffffff8002c26d1a com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19setDevicePowerStateEP11IOPCIDevicejmm + 0x1d6
0xffffffc0f055bdd0 : 0xffffff8002c31b53 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice13setPowerStateEmP9IOService + 0x77
0xffffffc0f055bdf0 : 0xffffff80009fcda1 mach_kernel : __ZN9IOService19driverSetPowerStateEv + 0x1f1
0xffffffc0f055be60 : 0xffffff80009fcb3a mach_kernel : __ZN9IOService15pmDriverCalloutEPS_ + 0x2a
0xffffffc0f055be80 : 0xffffff80002ff725 mach_kernel : _thread_call_delayed_timer + 0x4a5
0xffffffc0f055bef0 : 0xffffff8000300634 mach_kernel : _thread_call_delayed_timer + 0x13b4
0xffffffc0f055bfa0 : 0xffffff800025f13e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[BF2C5E86-1E8F-3FD4-9874-7738178FA73B]@0xffffff8002c1f000->0xffffff8002c46fff

Process name corresponding to current thread: kernel_task
Boot args: -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta

Mac OS version:
20D80

Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x0000000000000000
KernelCache base: 0xffffff8000200000
Kernel slide: 0x0000000000010000
Kernel text base: 0xffffff8000210000
__HIB text base: 0xffffff8000100000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 20598742028592
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000012bc04b39355
Sleep : 0x0000129154116358 0x00000010e2dfb608 0x0000000000000000
Wake : 0x000012919ce95c27 0x00000000ad3b62b2 0x000012919b0280fc

Thanks for your help !
 
Hello ! Thanks for your hardwork and update, i have almost the same build as you and your EFI but i have a problem. When my mac is on lockscreen for fews hours without use and i wake up its crash after 5-10 mins, i have this error :


Thanks for your help !


What PCI-e cards do you have installed. The panic mentions a problem with PCI bridge... This may be due to the Vega 56 which I know uses a PCI bridge...

Do you have config.plist > DeviceProperties for your Vega? Maybe try deleting it.
 
Back
Top