[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:

Key​	Type​	Value​
Comment​	String​	change Method(GPRW,2,N) to XPRW, pair with SSDT-GPRW.aml​
Disabled​	Bool​	False​
Find​	Data​	4750525702​
Replace​	Data​	5850525702​

But it has not worked from Catalina anymore.

Each time OpenCore is updated I update my system (now on 0.7.7), but It's always impossible to enter sleep mode.

I have an internal USB hub splitter, and there I connect the Fenvi Bluetooth and the Corsair Usb Cooler.

Even if I unplug the Corsair Cooler the no sleeping issue is there, so it has to be something related to the Fenvi Bluetooth... But I need it.

I also tried the USB config method, also without success.

Any clue to solve it?

Thank you!
Fernando

 

[wiiwelshman]

How do I check if it is properly configured?

@CaseySJ I keep getting this error as well, and now only one Thunderbolt port works.

 

[SuDoDmz]

Hey @CaseySJ couple of quick questions: The BIOS experiment has been put on halt, until further notice (resp. @Elias64Fr is still experimenting), did I get that right?

From what I understood enabling Apple VT-d yields a Blackscreen under Windows. Does that happen to everyone? Any workarounds in the works aside from disabling it?

With the newer Operating Systems on the market are the framebuffer patches for UHD still necessary? Is the RadeonBoost still necessary?

Anything else I've missed, while biding my time with my beloved X58?

 

[CaseySJ]

@CaseySJ I keep getting this error as well, and now only one Thunderbolt port works.

If you go through the 0.7.7 Mini-Guide, this problem will not occur. Please give that guide a try (read all the warnings and notes) and see if the problem gets resolved.

 

[CaseySJ]

Hey @CaseySJ couple of quick questions: The BIOS experiment has been put on halt, until further notice (resp. @Elias64Fr is still experimenting), did I get that right?

Correct.

From what I understood enabling Apple VT-d yields a Blackscreen under Windows. Does that happen to everyone? Any workarounds in the works aside from disabling it?

It has not happened on any of my Intel-based Macs so I'm still puzzled why it happens to others. Haven't identified the cause.

With the newer Operating Systems on the market are the framebuffer patches for UHD still necessary? Is the RadeonBoost still necessary?

Latest versions of macOS still need patches for iGPU to operate over HDMI port, but not for operating over Thunderbolt (DisplayPort). For output only through Thunderbolt (DisplayPort) we need to set Platform ID to 0x3E9B0007 without using any frame buffer patches.

RadeonBoost was not shown to provide meaningful acceleration in real-world apps, but only in synthetic benchmarks. Hence I stopped recommending it a long time ago.

Anything else I've missed, while biding my time with my beloved X58?

It's always good to glance at the Quick Reference to Mini-Guides and Micro-Guides for any new entries to the table of contents. For instance, we're now on OpenCore 0.7.7 and there's a reference to the 0.7.7 mini-guide that contains important information.

 

[SuDoDmz]

Correct.

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.

It has not happened on any of my Intel-based Macs so I'm still puzzled why it happens to others. Haven't identified the cause.

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

Latest versions of macOS still need patches for iGPU to operate over HDMI port, but not for operating over Thunderbolt (DisplayPort). For output only through Thunderbolt (DisplayPort) we need to set Platform ID to 0x3E9B0007 without using any frame buffer patches.

RadeonBoost was not shown to provide meaningful acceleration in real-world apps, but only in synthetic benchmarks. Hence I stopped recommending it a long time ago.

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.

It's always good to glance at the Quick Reference to Mini-Guides and Micro-Guides for any new entries to the table of contents. For instance, we're now on OpenCore 0.7.7 and there's a reference to the 0.7.7 mini-guide that contains important information.

Done already, but with close to 3500 pages there is always information you miss (for example, that the ModBIOS of @Elias64Fr is still under development, I picked up in an entirely different conversation between you and another user), so it's always good to ask.

So, any differences between Thunderbolt 4 and 3, that I should be aware of? Any development? Same problems? What else is new? And btw. how are you doing?

 

[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 Motherboards and Alder Lake CPU

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?