Contribute
Register

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

Joined
Sep 6, 2020
Messages
51
Motherboard
Gigabyte Designare Z390
CPU
i9 9900k
Graphics
Ati rx 580 nitro
Mobile Phone
  1. Android
Does the ATC700 contain a USB connector?
  • Because it supports RGB Fusion, it should be connectable to any RGB Fusion header (3-pin Addressable RGB) on motherboard (Z390 Designare does not have this).
Or does the Gigabyte C300 Glass contain a RGB lighting controller into which the ATC 700 is plugged?
  • If so, is the RGB lighting controller connected via USB to the F_USB header on Designare?
One workaround is to connect the RGB lighting controller to an External USB port on the rear IO panel. We can use a 9 pin USB to USB 2.0 cable to do this. Then if you run IORegistryExplorer and export the IOReg file (File --> Save As...), we can help you disable that external USB port in macOS. This allows Windows to control RGB effects, but hides the device from macOS.
Thank you very much for your help, the case and cooler have usb and both are connected to f_usb, tomorrow I will find out which of them does not let the computer fall asleep and let you know
 
Joined
Mar 21, 2011
Messages
811
Motherboard
GA-Z390-Designare
CPU
i7-9700K
Graphics
RX 590
I know that Apple TB displays aren't supported here, but I thought CaseySJ might have had another high-intensity workout this morning, haha.
On my Z390 Aorus Pro, I am using an unflashed GC-Alpine Ridge. I'm using the AR SSDT from HackinDROM, which is attached.

After either a cold or warm boot, the display and its USB functions (camera, display audio) work fine. Upon wake from sleep, I get a notification that one of the USB devices is using too much power and USB ports have been disabled. What gets disabled are the display USB functions and the USB 2 internal hub to which are connected the 4 rear USB ports.

I certainly can live with this, as I have plenty of other USB ports so as to not have to use the USB2 ports, and I have a webcam connected in case I need to have camera and no time to reboot (such as very important FaceTime from my grandson!!).

Attached are IOReg from a warm boot, IOReg upon wake from sleep, and the SSDT I'm using.

What I was hoping is that there is some control over USB power that could be tweaked to tell OS not to worry.

Thanks.

Screen Shot 2021-02-12 at 10.32.39 AM.png
.
 

Attachments

  • SSDT-TB3-HackinDROM.aml
    2.1 KB · Views: 20
  • IOReg after bootup.ioreg
    7.8 MB · Views: 13
  • IOReg after wake.ioreg
    8.3 MB · Views: 12

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,297
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
I know that Apple TB displays aren't supported here, but I thought CaseySJ might have had another high-intensity workout this morning, haha.
As luck would have it, I did in fact have another high-intensity working this morning! So I suppose a proper response is justified...

On my Z390 Aorus Pro, I am using an unflashed GC-Alpine Ridge. I'm using the AR SSDT from HackinDROM, which is attached.

After either a cold or warm boot, the display and its USB functions (camera, display audio) work fine. Upon wake from sleep, I get a notification that one of the USB devices is using too much power and USB ports have been disabled. What gets disabled are the display USB functions and the USB 2 internal hub to which are connected the 4 rear USB ports.

I certainly can live with this, as I have plenty of other USB ports so as to not have to use the USB2 ports, and I have a webcam connected in case I need to have camera and no time to reboot (such as very important FaceTime from my grandson!!).

Attached are IOReg from a warm boot, IOReg upon wake from sleep, and the SSDT I'm using.

What I was hoping is that there is some control over USB power that could be tweaked to tell OS not to worry.

Thanks.

View attachment 508989
.
Because these USB ports are remote devices hidden behind a Thunderbolt controller running inside the monitor itself, we don't have ACPI (SSDT) control over them like we do with motherboard USB ports.

If you have a real Mac with Thunderbolt ports, does the problem occur there as well (after waking from sleep)?

There is more to the Thunderbolt Monitor story than we've tackled in the past, but it gets quite complicated. A simple description of it goes like this:
  • Real Macs configure Thunderbolt monitors with firmware (BIOS). They contain a handful of Thunderbolt EFI drivers that manage those monitors from the earliest stages of system startup to the point at which macOS takes over.
  • These drivers also send configuration details to macOS through "Device Path Properties". This allows macOS drivers to seamlessly take over and manage those components more effectively.
  • Hackintoshes do not contain any of this capability. Some motherboard BIOSes are better than others at managing Thunderbolt peripherals, but none provides the same level of functionality as Apple's own firmware.
This is part of the reason we often say that Thunderbolt device behavior on a Hackintosh should mostly be taken on an as-is basis. Apple owns all the source code, of course, so they have the power to fix anything. But we on the other hand have to make the most of the hand we're dealt.

However, let me ask whether disconnecting and reconnecting the Thunderbolt monitor fixes this problem after wake-from-sleep?
 
Joined
Mar 21, 2011
Messages
811
Motherboard
GA-Z390-Designare
CPU
i7-9700K
Graphics
RX 590
As luck would have it, I did in fact have another high-intensity working this morning! So I suppose a proper response is justified...


Because these USB ports are remote devices hidden behind a Thunderbolt controller running inside the monitor itself, we don't have ACPI (SSDT) control over them like we do with motherboard USB ports.

If you have a real Mac with Thunderbolt ports, does the problem occur there as well (after waking from sleep)?

There is more to the Thunderbolt Monitor story than we've tackled in the past, but it gets quite complicated. A simple description of it goes like this:
  • Real Macs configure Thunderbolt monitors with firmware (BIOS). They contain a handful of Thunderbolt EFI drivers that manage those monitors from the earliest stages of system startup to the point at which macOS takes over.
  • These drivers also send configuration details to macOS through "Device Path Properties". This allows macOS drivers to seamlessly take over and manage those components more effectively.
  • Hackintoshes do not contain any of this capability. Some motherboard BIOSes are better than others at managing Thunderbolt peripherals, but none provides the same level of functionality as Apple's own firmware.
This is part of the reason we often say that Thunderbolt device behavior on a Hackintosh should mostly be taken on an as-is basis. Apple owns all the source code, of course, so they have the power to fix anything. But we on the other hand have to make the most of the hand we're dealt.

However, let me ask whether disconnecting and reconnecting the Thunderbolt monitor fixes this problem after wake-from-sleep?
thanks for taking a look at my question.

when connected to a MacBook Pro, the display works properly after wake from sleep.
on the Aorus pro, unplugging/replugging the display doesn't bring back the USB ports.

as I said, I have an acceptable workaround.

thanks
 
Joined
Jan 19, 2019
Messages
248
Motherboard
Z390 M Gaming
CPU
i9-9900
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,297
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Am I the only person who feels it would be entirely appropriate for everyone here to buy @CaseySJ a beer? The time and effort he puts into this forum is astounding.
Thank you for the sentiment! To be fair I've been a bit rough on some users for various reasons that I hope are not considered spiteful. This forum is a more pleasant and informative place to be when:
  • We describe the issues logically and include some background information.
  • We do a reasonable amount of search. Many issues have been reported and resolved in the past.
  • We rely more on bullet lists (such as this bullet list) to structure the problem statement. Long paragraphs can be difficult to read and parse.
Some Internet forums perpetuate the worst of humanity. We make a conscious effort here not to let that happen.

P.S. Casey does not drink beer. :)
 
Joined
Jan 19, 2019
Messages
248
Motherboard
Z390 M Gaming
CPU
i9-9900
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
@CaseySJ, I have to disagree with you here since I think you might be too nice in some situation rather than rough:
* I may sound harsh here, I think people who ask questions here need to do some homework: reading the 1st post at least for example. Many questions were already answered in post#1.
* People should have the right expectation regarding Hackintosh: at the end of the day, we spend a fraction of Apple's price tag to achieve the same/similar performance, more flexibility/upgradeability, dual/triple boot capability etc. So if something are not 1000% perfect, especially something very minor, we might let it go.
* In all fairness, if we are talking about some real technical problem, say general TB3 firmware topic then I think it makes perfect sense to go deeper; but for things like TB3 minitors and EVO plus (to a lesser degree), we should let new players know that avoiding those behind the back no-look pass is a smarter choice.




Thank you for the sentiment! To be fair I've been a bit rough on some users for various reasons that I hope are not considered spiteful. This forum is a more pleasant and informative place to be when:
  • We describe the issues logically and include some background information.
  • We do a reasonable amount of search. Many issues have been reported and resolved in the past.
  • We rely more on bullet lists (such as this bullet list) to structure the problem statement. Long paragraphs can be difficult to read and parse.
Some Internet forums perpetuate the worst of humanity. We make a conscious effort here not to let that happen.

P.S. Casey does not drink beer. :)
 
Last edited:
Joined
Dec 13, 2013
Messages
117
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
RX 6900 XT
Mac
  1. MacBook Pro
  2. Mac mini
  3. Mac Pro
Mobile Phone
  1. iOS
Thank you for the sentiment! To be fair I've been a bit rough on some users for various reasons that I hope are not considered spiteful. This forum is a more pleasant and informative place to be when:
  • We describe the issues logically and include some background information.
  • We do a reasonable amount of search. Many issues have been reported and resolved in the past.
  • We rely more on bullet lists (such as this bullet list) to structure the problem statement. Long paragraphs can be difficult to read and parse.
Some Internet forums perpetuate the worst of humanity. We make a conscious effort here not to let that happen.

P.S. Casey does not drink beer. :)
Well then @CaseySJ name your poison. I'd be interested to know your favorite adult beverage. Mine happens to be Bumbu Rum on the rocks. :)
 
Joined
Aug 17, 2019
Messages
125
Motherboard
Gigabyte Z390 Aorus Xtreme
CPU
i9-9900K
Graphics
RX 5700 XT
@Snoots @CaseySJ
Hi guys did you still need my EFI, I'm so sorry for the late reply, I haven't been on in a few days due to a death in the family.
 
Top