Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

Just to be sure: when the system enters sleep, it actually shuts down instead? So that means it won't wake with keypress or mouse movement? Are you using SSDT-GPRW, which has the effect of waking only with power button?

When the system has allegedly gone to sleep and you press the power button, does the system go through a full start, which includes Gigabyte Splash Screen and OpenCore Picker Menu?
 
just upgraded to z490 Vision-D (bios F5) + i9-10900k and installed latest Catalina and then Big Sur, so all looks great, but no luck with thunderbolt 3 and Apollo UAD2 "no device found!" I use Apple TB3 to TB2 adapter it works years with others boards, on Windows 10 is same situation just "no device found!"
Very strange because connection to Monitor using usb3.1(TB3) to DP cable work great. What can I do now, any advice please. Maybe the board has some issue and I should to replace it?
Did the UAD Apollo work properly under Catalina? Please keep in mind that changes in Big Sur related to third-party kernel extensions may break a lot of existing device drivers. Big Sur is a public beta meant only for testing purposes and should ideally be installed on a separate dedicated SSD. But all real work must continue to be done on Catalina.
 
...
I also noticed that a Diff between the TB-Firmware-BIN of my first (broken) board and the modified Firmware-BIN from here showed a lot more differences than a Diff between the original TB-FW of my second board and the modified Firmware-BIN from here. So overall, returning the first board was the right choice I guess.
...
Hello @traeu,

Welcome to the forum!

My boot times are also in the neighborhood of 30 seconds (from power-up to OpenCore Picker), though I haven't timed it recently. It does not bother me at all, but I do recall it being faster before flashing the Thunderbolt firmware.

Regarding the differences between original firmware and the modified one, please check to see if most of the differences are in byte offset 0x0 to 0x3FFF. That region contains large "scratch" areas that appear to be different on each board. We noticed this a while ago, but it appears to have no negative effect.
 
Just to be sure: when the system enters sleep, it actually shuts down instead? So that means it won't wake with keypress or mouse movement? Are you using SSDT-GPRW, which has the effect of waking only with power button?

When the system has allegedly gone to sleep and you press the power button, does the system go through a full start, which includes Gigabyte Splash Screen and OpenCore Picker Menu?

@CaseySJ

I tried testing the Fenvi test this without the USB splitter. Connected Fenvi USB directly to MB and got the same results as before. When I disconnected the USB cable, but kept the Fenvi card in the PCIe slot the system successfully went to sleep in Windows and would wake up with USB Keyboard and mouse. In MacOS it goes to sleep, but does not wake up with mouse and keyboard. I have to push the power switch and it restarts, showing the bios screen and then goes to OpenCore picker. I'll try completely removing the Fenvi card to see if that fixes it for MacOS.

Here's the error log that is now popping up.

1598218322836.png



Where do I find SSDT-GPRW?

Also I noticed it takes around 15-20 seconds longer for the cpu to go to sleep in MacOS than Windows, not sure if this is normal?

Edit: Looks like it's the Fenvi card causing the problem. Sleep and wake work when it's completely uninstalled. Going to return it and try the Youbo one.
 
Last edited:
My boot times are also in the neighborhood of 30 seconds (from power-up to OpenCore Picker), though I haven't timed it recently. It does not bother me at all, but I do recall it being faster before flashing the Thunderbolt firmware.

Regarding the differences between original firmware and the modified one, please check to see if most of the differences are in byte offset 0x0 to 0x3FFF. That region contains large "scratch" areas that appear to be different on each board. We noticed this a while ago, but it appears to have no negative effect.

Hello @CaseySJ and thanks for your answer.
You are right, most of the differences are before 0x3FFF, good to know that this makes no difference.
Now I am a bit confused that you also experience long POST-times up to 30 seconds!
Is your board also waiting at a specific number at the boards display, like my first one was waiting at "80"?
I wonder why my board is faster after I exchanged it, even if the BIOS-Version, BIOS-Settings and the TB-Chip-FW-Version are the same like before. I hope that long boot-time is not needed somehow and my thunderbolt works! I see it under "Thunderbolt" in System Information, but I can't test it yet.

One more question: If Hotplug of USB3-Devices does not work on my Thunderbolt-Ports (USB2 works, USB3 works only if plugged in before booting) is this unrelated to thunderbolt, or could this be a sign of not properly working thunderbolt? I only have USB devices to test, no TB-device yet...
 
Last edited:
@CaseySJ

Edit: Looks like it's the Fenvi card causing the problem. Sleep and wake work when it's completely uninstalled. Going to return it and try the Youbo one.

Did you try a different USB header on the motherboard? Some have said that makes a difference.
 
@GMoney022 I stand corrected.
It is 10.15.6. (I have edited the response to reflect the correct OS version. Thank you.)

We have not implemented the latest macOS Catalina 10.15.6 Supplemental Update.

We are running PT 2020.5.

My apologies for the typo.

Tony

No worries! Thanks for the clarification!
 
My h..mac sleep then motherboard wake immediately(but no iGPU output, monitor does not wake).
maybe it's related the 943602CS card.
@CaseySJ

Edit: Looks like it's the Fenvi card causing the problem. Sleep and wake work when it's completely uninstalled. Going to return it and try the Youbo one.
 
Last edited:
Did the UAD Apollo work properly under Catalina? Please keep in mind that changes in Big Sur related to third-party kernel extensions may break a lot of existing device drivers. Big Sur is a public beta meant only for testing purposes and should ideally be installed on a separate dedicated SSD. But all real work must continue to be done on Catalina.
I have tried also on latest Catalina without luck and also on Windows 10 is same - the TB3 no work:) I have heard that TB3 from Gigabyte site in not enough and needs to be installed Microsoft "Thunderbolt Control center"
So, previously it was necessary that thunderbolt first properly under run under Windows and on the same PC, but what now? Did you install first TB3 driver on Windows?

and as I mentioned in the previous post TB3 connection between mainboard and monitor work just fine via cable TB3 type c to DP:)
 
Last edited:
Back
Top