[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[Errabundo]

Hello.
Just to ask your advice:
Since my first configuration I always had problems with "sleep".
Just in the moment the system enters into the Sleep mode, in just a second it wakes up.

I updated at the time they appeared to Mojave, BigSur, Monterey... and always the same issue.

Previously, in Catalina (if I well remember) I fixed it with that method, and was successful:

I answer to myself:

It's amazing, but it's solved. The faulty device was the original apple wired extended keyboard!!
I've been using it from my first Hack , and there was no problem at all.

Investigating this morning, I read an advice from someone stating that the Logitech mouse and keyboard are recommended, I change the wired Apple keyboard for a wired Hp keyboard, and... Magic! The Wake up issue has disappeared!!

I recovered the Sleep mode after one year of problems!

I never read something related to the wired apple keyboard causing the non sleeping issue.

Thanks!

 

[CaseySJ]

Cool. Any Updates any time soon? First I heard of it I got giddy as a child, but after the VT-d discovery I didn't hear anything since.

We succeeded in injecting and enabling Apple's Thunderbolt EFI drivers into Gigabyte's BIOS. The results were quite promising, with all Thunderbolt device properties being injected by the EFI driver instead of a Thunderbolt SSDT. But alas this did not improve Thunderbolt monitor support. @gandem has reported good results with on-board Maple Ridge on the Asus Z690 ProArt Creator coupled to an LG UltraFine:

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

Hi guys. I believe my IP address is being blocked as I'm unable to view the site without a vpn or air card. Hoping an administrator can get me fixed.

www.tonymacx86.com

Ok, then I have to make my own discovery through trial and error

Damn! I hoped I could get past as many property injections as possible. I'm still doing it the hard way over ACPI and (to be honest I haven't started debugging yet, but I'm 99.9% sure it's got to do something with property injection, had it already on my X58) Windows gives me BSOD with ACPI_BIOS_ERROR.

All of the SSDTs we use are wrapped around an If statement that enables them only in macOS. But the DMAR table is an exception. I wonder if this problem occurs if Windows boots from a master boot record instead of EFI partition, but I am far from a Windows expert...

There's been a fair bit of discussion on Thunderbolt 4 (Maple Ridge) in Z590 and Z690 threads. If you search for "Maple Ridge" you'll find quite a bit of information, but alas Maple Ridge is not natively supported in macOS and is much less reliable overall than Titan Ridge.

Much of the recent excitement in the land of Hackintosh was in the Alder Lake thread!

Z690 Chipset and Alder Lake CPUs

This is the Z690 Chipset Motherboards and Alder Lake CPU general compatibility thread. Please note these are just released and have no Intel Mac counterpart for compatibility. For reference here are some links to parts on Amazon: Intel Alder Lake CPUs: https://amzn.to/3ksGFre Z690...

www.tonymacx86.com

 

[SuDoDmz]

All of the SSDTs we use are wrapped around an If statement that enables them only in macOS. But the DMAR table is an exception. I wonder if this problem occurs if Windows boots from a master boot record instead of EFI partition, but I am far from a Windows expert...

There's been a fair bit of discussion on Thunderbolt 4 (Maple Ridge) in Z590 and Z690 threads. If you search for "Maple Ridge" you'll find quite a bit of information, but alas Maple Ridge is not natively supported in macOS and is much less reliable overall than Titan Ridge.

Much of the recent excitement in the land of Hackintosh was in the Alder Lake thread!

I'm already checking the loaded OS, but still, there seems to be something Windows doesn't like...

Good, that I'm still on Titan Ridge then

I skimmed through the first few pages, but I can't really say I see that much excitement, much less share it.
Still one question lingers in my mind: where'd you be able to get a dGPU for that price? Here in Germany a "good" dGPU costs 1500-2000€ and I'm not confident it'll change anytime soon, alas...

We succeeded in injecting and enabling Apple's Thunderbolt EFI drivers into Gigabyte's BIOS. The results were quite promising, with all Thunderbolt device properties being injected by the EFI driver instead of a Thunderbolt SSDT. But alas this did not improve Thunderbolt monitor support. @gandem has reported good results with on-board Maple Ridge on the Asus Z690 ProArt Creator coupled to an LG UltraFine:

This, somehow, seems to defy the natural order of things I still hope for a mod-BIOS

 

[brousseau6933]

Unfortunately there's no simple way to downgrade
You have to flash an old version manually by serial communication

You mean with the help of the mouse/keyboard PS2 port?

 

[mcnb]

Howdy, all. Recently updated to Monterey and OpenCore 0.7.7 on this system, and am having issues with Bluetooth losing connection with keyboard and mouse after wake. My WiFi/BT board is an older Broadcom board (BRCM20702) in a PCI adapter. Anyone else having these issues? Probably time for a hardware upgrade to something more recent but thought I would survey the room. (will add this started on 12.1, now running 12.3 beta)

 

[Inqnuam]

You mean with the help of the mouse/keyboard PS2 port?

haha not that serial but connecting directly to the chip

 

[SuDoDmz]

@CaseySJ A few other questions popped into my mind:

1: you said the framebuffer patch isn't necessary anymore. But we'd still have to define the ports, right? Say, for example HDMI?

2: I saw in your EFI a file, SSDT-DMAC.aml. I was under the impression DMA was no real deal, or at least not usable, or feasible under OS X? Could you elaborate? Where did you get that? Where did you get the idea?

3. I noticed I'm incorporating an SSDT for SMBus, but you don't. Why?

4. Any recent and reliable hardware for WiFi 6 and BT5?

And I think there was a 5th question, but I've forgotten I'll poke you again, if it pops into my mind, 'd that be OK?

 

[DeBilbao]

I'm currently running my Z390 Designare with OpenCore 0.7.7 and the latest macOS Monterey 12.2 update. Everything running smooth, with no issues at all.

System is using the F9i BIOS modified by @Elias64Fr (thanks, mate!)

I compared it with the official F9i BIOS that Gigabyte removed from their website, and I saw the 4 microcodes entries, on the left the official F9i dated April 23, 2020 and on the right F9i from Elias64Fr, updated to Jan 05, 2021



I've also compared the new official F9 BIOS file from Gigabyte dated November 29, 2021 with the one from Elias64Fr and the 4 microcode entries are identical, so regarding microcode patches, they are the same.



But running from Windows the Intel Converged Security and Management Engine Version Detection Tool, the program reports that my system is vulnerable, so maybe there are more security fixes unreleased from Gigabyte.



I've tried to run the Linux version of the CSME Detection Tool in macOS, but it gives me an error and the Intel documentation states that "The Detection Tool does not support MacOS".

The documentation also remarks that the following security issues are checked by the Tool.

• SA-00086 • SA-00125 • SA-00213 • SA-00241 • SA-00295 • SA-00404 • SA-00391 • SA-00459

And I'm wondering how well protected we are from this vulnerabilities.

Comments welcomed.

 

[Perdomo15]

@CaseySJ quick question my friend. Is there any guide on how to downgrade BIOS flashing the chip method? I don’t know if you understand where I'm going. (From F9 to F9i) xD

 

[tsamy]

I just updated to Monterey 12.2 in my hackintosh build, and I cant use built in AirPlay option. I gave another MacBook Pro running 12.2, and then I’m able to use AirPlay and can see Macbook in my iPhone.