Contribute
Register

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

Hey everyone,

Can't thank you all enough for this massive thread and of course, @CaseySJ for the incredible guide/resource. I've got just about everything working great except for a strange issue where the Fenvi T919 card causes weird power issues with my computer. It will either:
A. Power on and immediately shut back off.
B. Power on and shut down about 3 times in a row before hitting bios which will say there was a problem that caused the restart. After that it is able to run normally until next shut down, when it usually goes back to A.

I've gone through and removed my components one by one to isolate it to the T919 card. RMA'd it and the system was running/powering on flawlessly all week without the T919. Just got my new one and the same issues are now back. I have tried other PCI slots as well.

Any thoughts or ideas? I tried my best to search the thread but didn't see much about it. I can provide whatever info might help! Thank you so much.

More info about the system:
Screen Shot 2020-05-08 at 8.39.58 PM.png


Motherboard: Z390 Designare
SSD system drive: Samsung 970 Pro M.2
Power supply: Corsair RM850x
Ram: G.Skill Trident Z 3200MHz DDR4
Case: NZXT H510
 
Last edited:
@jiffyslot
@CaseySJ

Not much luck. The screen shots show what comes up when I run sudo kextcache -i / in terminal.

The weird thing is that I have a clone of my current system drive and my Audio works fine every time I boot from that drive.
Invalid Signature is fine and nothing to worry about.

However you have 1 rejected kext, LILU, because it is in the wrong folder. Move it from S/L/E to L/E.
Both Lilu and AppleALC are in /System/Library/Extensions. They must be removed from there and moved to /Library/Extensions. Then rebuild kernel cache and reboot.
 
Hey everyone,

Can't thank you all enough for this massive thread and of course, @CaseySJ for the incredible guide/resource. I've got just about everything working great except for a strange issue where the Fenvi T919 card causes weird power issues with my computer. It will either:
A. Power on and immediately shut back off.
B. Power on and shut down about 3 times in a row before hitting bios which will say there was a problem that caused the restart. After that it is able to run normally until next shut down, when it usually goes back to A.

I've gone through and removed my components one by one to isolate it to the T919 card. RMA'd it and the system was running/powering on flawlessly all week without the T919. Just got my new one and the same issues are now back. I have tried other PCI slots as well.

Any thoughts or ideas? I tried my best to search the thread but didn't see much about it. I can provide whatever info might help! Thank you so much.

More info about the system:
View attachment 468315

Motherboard: Z390 Designare
SSD system drive: Samsung 970 Pro M.2
Power supply: Corsair RM850x
Ram: G.Skill Trident Z 3200MHz DDR4
Case: NZXT H510
At this point you might as well try connecting power to PEG as indicated in green. Normally we use that with two or more GPUs, but it doesn't hurt to try. Also ensure that the 12V_2x4 port in red is connected.

Screen Shot 2020-05-08 at 6.26.46 PM.png

Also try disabling X.M.P. Profile 1 for DRAM.
 
Of course :) No flash - no Thunderbolt Bus.
For Alpine Ridge it's not strictly necessary to flash the firmware in order to activate Thunderbolt Bus. A properly configured SSDT-TbtOnPCH.aml can do the job for on-board controllers.
 
Both Lilu and AppleALC are in /System/Library/Extensions. They must be removed from there and moved to /Library/Extensions. Then rebuild kernel cache and reboot.
GOT IT!!! THANK YOU!!!
 
For Alpine Ridge it's not strictly necessary to flash the firmware in order to activate Thunderbolt Bus. A properly configured SSDT-TbtOnPCH.aml can do the job for on-board controllers.
@CaseySJ @Elias64Fr

Some observations with both the modified DROM and the SSDT method on my board. I use a TS3 dock with the system with all my devices including the primary monitor connected to the dock.

When I wake the PC from sleep , the Thunderbolt dock disappears from the System Information > Thunderbolt section. The devices connected to the dock work fine. I can pullout and TB cable from the Mobo and replug it without issues. This may explain why some people are seeing devices getting ejected after sleep. There are no error logs.
Since it does not affect the functionality, I'm not bothered much. But it'll be good to know why this happens.


Logs are from the SSDT method

Code:
2020-05-09 08:40:22.054823+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::prePCIWake()> 37306462947us AppleThunderboltNHIType3::prePCIWake - took 1 us
2020-05-09 08:40:22.054824+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::prePCIWake()> AppleThunderboltNHIType3::prePCIWake - took 1 us
2020-05-09 08:40:22.054858+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::publishPCILinkData()> Thunderbolt 0 PCI - LS=0x7023 LC=0x0040 SS=0x0140 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001
2020-05-09 08:40:22.054865+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::publishPCILinkData()> Thunderbolt 0 PCI - LS=0x7023 LC=0x0040 SS=0x0140 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001
2020-05-09 08:40:24.067126+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltGenericHAL::earlyWake()> 37308475250us AppleThunderboltGenericHAL::earlyWake - complete - took 2011 milliseconds
2020-05-09 08:40:24.067127+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltGenericHAL::earlyWake()> AppleThunderboltGenericHAL::earlyWake - complete - took 2011 milliseconds
2020-05-09 08:40:33.639157+0800  localhost kernel[0]: (AppleUserHIDDrivers) [AppleUserHIDEventDriver.cpp:93][0x1003dc4f5] CalDigit Thunderbolt 3 Audio usagePage: 12 usage: 1 vid: 8584 pid: 25907
2020-05-09 09:11:36.068893+0800  localhost kernel[0]: IOPlatformSleepAction -> AppleThunderboltHAL
2020-05-09 09:11:41.188385+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::waitForOk2Go2Sx()> AppleThunderboltNHIType3::waitForOk2Go2Sx - retries = 0
2020-05-09 09:11:41.188389+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltGenericHAL::lateSleep()> AppleThunderboltGenericHAL::lateSleep - complete - took 5119 milliseconds
2020-05-09 09:11:42.644706+0800  localhost kernel[0]: IOPlatformWakeAction -> AppleThunderboltHAL
2020-05-09 09:23:13.033382+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::prePCIWake()> 39186367365us AppleThunderboltNHIType3::prePCIWake - took 1 us
2020-05-09 09:23:13.033383+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::prePCIWake()> AppleThunderboltNHIType3::prePCIWake - took 1 us
2020-05-09 09:23:13.033408+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::publishPCILinkData()> Thunderbolt 0 PCI - LS=0x3023 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001
2020-05-09 09:23:13.033415+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltNHIType3::publishPCILinkData()> Thunderbolt 0 PCI - LS=0x3023 LC=0x0040 SS=0x0040 SC=0x0008 PMCSR=0x0000 RT=0xffffffff NLRT=0xffffffff LWRT=0xffffffff PRRT=0xffffffff TRT=0x0000 TNLRT=0x0000 TLWRT=0x0000 TPRRT=0x0000 TLUP=0x0001
2020-05-09 09:23:15.049909+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltGenericHAL::earlyWake()> 39188383893us AppleThunderboltGenericHAL::earlyWake - complete - took 2015 milliseconds
2020-05-09 09:23:15.049910+0800  localhost kernel[0]: (AppleThunderboltNHI) <AppleThunderboltNHI`AppleThunderboltGenericHAL::earlyWake()> AppleThunderboltGenericHAL::earlyWake - complete - took 2015 milliseconds
2020-05-09 09:23:15.613106+0800  localhost kernel[0]: (IOUSBFamily) <IOUSBFamily`AppleUSBDevice::start(IOService*)> 039188.947086 CalDigit Thunderbolt 3 Audio@00200000: AppleUSBDevice::start: failed to open _deviceClient
2020-05-09 09:23:15.614414+0800  localhost kernel[0]: CalDigit Thunderbolt 3 Audio: bad busy count (0,-1)
 

Attachments

  • Screenshot 2020-05-08 at 1.23.38 PM.png
    Screenshot 2020-05-08 at 1.23.38 PM.png
    36.3 KB · Views: 78
  • Screenshot 2020-05-08 at 1.24.35 PM.png
    Screenshot 2020-05-08 at 1.24.35 PM.png
    34.8 KB · Views: 76
Bonjour,

- PCIe slot 1 : Gigabyte RTX 2070
- PCIe slot 2 : MSI Radeon 580

Everything works, both cards are detected when I boot in Windows, and If I select macOS (Catalina 10.15.4), I can use my MSI Radeon 580 (and not the Nvidia card as expected). Basically not issue with the OS when both cards are installed.

BUT ... I if I set my BIOS with the initial display set to "PCIe slot 2" (my Radeon), I can't see the Gigabyte boot screen and the Clover menu ...

If I remove the graphic card in PCIe slot 1, it works !! And yes I had only one cable, connected to the card in PCIe slot 2 (my Radeon).


Why I want this setup ? My RTX 2070 is for gaming in Windows , ideally it should stay in PCIe slot 1. 90% of the time I'm on macOS, so I want to boot with the display on PCIe slot 2.


Thanks ... hopefully I'm not alone with this setup ;)
 
Hello Guys.

Good News. Antelope Thunderbolt Audio works :)

@CaseyCZ @qthegaijin .

As i have said in my other comments, I have an Asus X299 Prime Deluxe with a Titan Ridge Card Pcie and a Radeon VII.
I had problems with the Zeb Tour after add the VII to my system, having drops in audio and glitches, so as i have read somewhere that Asus X299 is so buggy, i had bought in Amazon a Gigabyte X299X Aorus Master.
I changed mine for the X299X and after booting i found a lot of problems with Clover. When you accesed into the usb , the computer restarts and bios says that have found an error and "it have reset to default options".
So, after of looking at @dolgarrenan post of his X299X, i used his folder and just changed the SMBIOS to iMacPro 1,1 (because i have Mojave. For audio Catalina stills a wrong option)

So, after of add his folder, i have only "sometimes" reboots.

i flashed the modified firmware for my titan Ridge Card (GC-TITAN-RIDGE-NVM23-Elias64Fr.bin)
with firmware ready, TH Card was inserted in PCie16_2 with cable connected.

Then , you know, as i have said in the other post, i had 20 segs of sound and then it disconnected.
knowing that "audio worked" i decided to go back to my Asus X299 and get a try with the thunderbolt and send back X299X to Amazon.... But after mounting X299 Asus , i didnt have skills to get Antelope recognized .
So i have paused X299 and as i have other i9 9940x processor and some components, i have mounted in the table the x299x just to investigate thunderbolt, and when everything gets clear, send it back to Amazon xDDD.

desktop.jpeg


Ok, so now, we have the machine again as how it have worked 3 days ago...
I have find an nvme here with High Sierra, so could boot, after im going to test mojave and catalina also...

First of all, booting video verbose:

I have used @dolgarrenan x299x Clover folder with a random iMac Pro 1,1 SMBIOS. (attached before)

After of booting, system recognize "perfectly" the Antelope Zen Tour via thunderbolt.
It appears in system preferences and in audio devices.
And the signal now works without a problem (the first time 3 days ago , remember that after 20 segs it disconnected, now works all the time without disconnections)
1.png
2.png
3.png
4.png

*The SMBIOS Number is random, not important to hide.

So, now that we have the zen tour working its time to do the tests reports that @qthegaijin said.

here is:
USER:~ USERNAME$ log show --last boot --style compact --predicate 'senderImagePath contains "Antelope"' --info --debug


Filtering the log data using "senderImagePath CONTAINS "Antelope""


Timestamp Ty Process[PID:TID]


2020-05-09 02:57:32.695 Df kernel[0:1f1] (AntelopeUnifiedDriver) Antelope Thunderbolt Audio (Version:3.33 Build:3478b17 2020-02-27/18:08): starting for device 1d4b a180


2020-05-09 02:57:33.001 Df kernel[0:1f1] (AntelopeUnifiedDriver) AntelopeAudioDevice::setPluginPartition() -- partition 0 32 32 --> 00000000


2020-05-09 02:58:04.975 Df kernel[0:1f4] (AntelopeUnifiedDriver) AntelopeTBUserClient/331: error: user-client send message 0000000a failed e00002db (once)


2020-05-09 02:58:06.985 Df kernel[0:14c2] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:58:07.843 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0c95030d 014b0133 022f022c 0050004c


2020-05-09 02:58:12.175 Df kernel[0:1532] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:58:13.034 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0c9e030d 014a0133 072a022d 004e004c


2020-05-09 02:58:16.447 Df kernel[0:1558] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:58:17.380 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0caf030d 014b0133 0794022f 004f004c


2020-05-09 02:58:56.936 Df kernel[0:1760] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:58:57.714 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0e52030d 014c0133 022f022c 004f004c


2020-05-09 02:59:01.749 Df kernel[0:17f3] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:59:02.643 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0d51030d 014c0133 0883022d 0050004c


2020-05-09 02:59:16.050 Df kernel[0:18e9] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:59:16.827 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0b830312 014b0133 025d0237 0050004c


2020-05-09 02:59:26.907 Df kernel[0:1a69] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 02:59:27.686 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0c9b0312 014b0133 025c0235 0054004c


2020-05-09 03:00:53.255 Df kernel[0:1da7] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 03:00:56.843 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0d71030d 014b0133 0735022f 0050004c


2020-05-09 03:02:38.797 Df kernel[0:2429] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 03:03:41.310 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0f44030d 01530133 0251022b 0054004c


2020-05-09 03:03:44.568 Df kernel[0:26bc] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: starting audio


2020-05-09 03:03:55.706 Df kernel[0:209] (AntelopeUnifiedDriver) AntelopeTBAudioEngine: audio stopped 0ee4030d 01530133 058e0232 0054004c

Here is a video that i have recorded to show you:



The main problem here is that Antelope Launcher App, don't see Antelope interface, so any of its features more than "play audio" would works.

I have tried to do the thunderbolt DROM Micro-Guide but im not totally shure about what have i need to do.
Before of doing anymore i was thinking to just say all this report and then continue :)

I attach also an ioreg log.

One question also, for what is the objetive of the Power cables and USB2 cable in the Titan Ridge Card??
I have all them disconected as you can see in the video.

Today, Saturday ill be here also. :)
 

Attachments

  • EFI.zip
    4.3 MB · Views: 102
  • srmusico ioreg.ioreg
    14.6 MB · Views: 75
Bonjour,

- PCIe slot 1 : Gigabyte RTX 2070
- PCIe slot 2 : MSI Radeon 580

Everything works, both cards are detected when I boot in Windows, and If I select macOS (Catalina 10.15.4), I can use my MSI Radeon 580 (and not the Nvidia card as expected). Basically not issue with the OS when both cards are installed.

BUT ... I if I set my BIOS with the initial display set to "PCIe slot 2" (my Radeon), I can't see the Gigabyte boot screen and the Clover menu ...

If I remove the graphic card in PCIe slot 1, it works !! And yes I had only one cable, connected to the card in PCIe slot 2 (my Radeon).


Why I want this setup ? My RTX 2070 is for gaming in Windows , ideally it should stay in PCIe slot 1. 90% of the time I'm on macOS, so I want to boot with the display on PCIe slot 2.


Thanks ... hopefully I'm not alone with this setup ;)
When we install a GPU in both the first and second PCIe slots, then both slots operate at x8. So there's no difference at all between them. Hence, you might try moving the Radeon 580 to slot 1 and the RTX 2070 to slot 2, then set Initial Display Output to PCie 1 Slot.
 
Today, Saturday ill be here also. :)

Holy!! That is a great start!!!! Farther than I have been able to get in terms of it actually sending audio.
Couple more questions for you:

- When you hit restart server on the control panel does the unit still not show?
- Are you able to change the sample rate in the Apple Audio/Midi settings app?
- You are also using the latest driver which was released today!!! USB has horrible clocking issues over usb with that driver but it may have fixed some of the TB errors???!!

I will be able to do my own tests tomorrow (Saturday) with the latest driver over thunderbolt too!
 
Back
Top