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

[Elias64Fr]

It's a bit confounding as to why an Alpine Ridge controller isn't facing nearly the same hurdles as we are with Titan Ridge. @Elias64Fr's Asus Maximum IX Extreme Z270 already has:

• Thunderbolt Local Node
• Thunderbolt Bus
• Full 40 Gb/s bandwidth
• eGPU support with functional menu bar icon to connect/disconnect eGPU
• Hot plug

C'est la vie!

One more information, Also on my Asus Zenbook with onboard TI PD TPS65988 .. it seems that macOS drivers nicely deal with it... without any Firmware patches.

 

[Elias64Fr]

Sure:

• TNODE/TBUS appears --> then --> MUST() is called

instead of:

• MUST() is called --> then --> TNODE/TBUS appears

So far we see the following behavior:

• Cold Boot --> no devices attached --> No TNODE/TBUS
• Cold Boot --> TB3 and/or USB-C attached --> No TNODE/TBUS
• Warm Boot --> no devices attached --> No TNODE/TBUS
• Warm Boot --> TB3 and/or USB-C attached --> No TNODE/TBUS

But then...

1. Hot plug or hot unplug a TB3 device --> system hang
2. Then press physical reset button with TB3 device connected
3. When system boots up --> TNODE/TBUS appears --> MUST() appears

So Step 1 "triggers" something important...

In order to confirm that system Hang is the cause of "correct" config to let appear TNode/TBus .. You can boot with same state and instead of Hot-Unplugging TB3 device, you can press reset button to have a look after reboot !
We should know if "triggers" is related to Hot Plug or something else.

 

[CaseySJ]

In order to confirm that system Hang is the cause of "correct" config to let appear TNode/TBus .. You can boot with same state and instead of Hot-Unplugging TB3 device, you can press reset button to have a look after reboot !
We should know if "triggers" is related to Hot Plug or something else.

Agreed. Placed on to-do list for this evening.

 

[CaseySJ]

macOS Catalina 10.15.4 appears to contain references to unannounced AMD CPUs (not GPUs). This, of course, invites all kinds of speculation! These appear to be APUs (CPUs with on-board graphics).

New References to AMD Processors Discovered in macOS 10.15.4 Beta

Over the last few months, an increasing number of references to AMD processors have been uncovered in macOS Catalina code, starting with the 10.15.2...

www.macrumors.com

P.S. Discussion of AMD Hackintoshes is not permitted per site rules.

 

[djx8605]

OK, I have another question for my Pro-Audio/DAW brethren.
I am using Digital performer, and I am seeing clicks and pops at low buffer settings even though the CPU is barely taxed at all.
Like I only have a single track with an amp sim on it.
44k with buffers set at 128.
The CPU meter in DP is like 10% but every so often I get a click and the "overload" light comes on.
I have been trying to isolate what is causing it.
Disabled wifi, Bluetooth, ethernet...
But it still happens.
It has me wondering if I have something misconfigured and I am just too dumb to know it.
Maybe its something grabbing the PCIe bus too often.

Hey did you get the problem figured out? May have a few suggestions but don't want to waste your time if you've figured it out; I'm still playing catch up on the thread... reading this stuff is addicting!

 

[DJ4MC]

New one for me. My system will hang looking for the boot drive if I leave my Thunderbolt Raid arrays connected. IF I turn them off, I go right to the clover boot menu, and it boots normally. Is this maybe a clover boot entry thing? it started happening when I updated Clover a few weeks back. Interestingly, I leave the TB3 drives off when I do updates to system etc. And I don't reboot that much. System sleeps well and I keep it on about 90% of the time.

Jules

 

[z4k]

I tried the combination and got no luck. Running 10.14.6, switched iGPU to Auto and tried 80. That made the iGPU disappear in Intel Power Gadget so it may be a 10.15/weg specific thing?

Seems that Auto setting was a mistake.

So in the last days I've been playing around with BIOS Internal Graphics setting and FCPX usage (shikigva=80 for all tests). Got some pretty interesting results with insane differences in render times. Check out the following:

Internal Graphics Disabled: 2:39 export time
Internal Graphics Auto: 2:39 export time
Internal Graphics Enabled: 0:38 export time

Yes! Having Internal Graphics Enabled in BIOS my export time was more than 4 x faster!!

Also, Preview, Netflix on Safari all working with all three settings.

All testing was done using a 45 second 4k clip.
H.264 Better Quality, 4k export.
Added an Aged Paper filter.
Background Render OFF, before each test I deleted all Generated Event Media.
Each test was run 3 times in a row producing IDENTICAL results so I'm pretty sure about the results.

 

[phillg]

Hi @CaseySJ . Loving the build. Random Waking every 20mins or so. Any thoughts? Have seen"proximitywake" to "0" in Hackintool.app. Also removed USB gear to see if that is causing issues - no change.

 

[z4k]

So I wrote about an issue one or two days ago I still haven't figured out:

Turning CSM: Disabled in BIOS and rebooting causes my Windows boot Drive to disappear (from both BIOS Setup AND BIOS Boot Menu). I can only see my MacOS drive and boot from that. Inside MacOS I can see the Windows drive just fine.

Turning CSM: Enabled makes all my drives reappear and boots from whichever I select just fine.

I'm asking since all guides specifically say OC needs CSM: Disabled. Is this a setting that can cause a crash in the long-term? Should I try fix my Windows drive so that it also appears with CSM: Disabled somehow?

Or since I can boot in MacOS with CSM: Enabled as well it is just fine for my setup and I don't need to mess with it any more?

A few maybe-useful notes: My macOS installation was made on a fresh NVME drive and an all new pc build (the one I'm currently using). My Windows drive is on a SATA3 SSD drive, the installation was made while on a different, quite older system running a Gigabyte P67A-UD3 MoBo, intel i7 2600k.

 

[edunon]

So I wrote about an issue one or two days ago I still haven't figured out:

Turning CSM: Disabled in BIOS and rebooting causes my Windows boot Drive to disappear (from both BIOS Setup AND BIOS Boot Menu). I can only see my MacOS drive and boot from that. Inside MacOS I can see the Windows drive just fine.

Turning CSM: Enabled makes all my drives reappear and boots from whichever I select just fine.

I'm asking since all guides specifically say OC needs CSM: Disabled. Is this a setting that can cause a crash in the long-term? Should I try fix my Windows drive so that it also appears with CSM: Disabled somehow?

Or since I can boot in MacOS with CSM: Enabled as well it is just fine for my setup and I don't need to mess with it any more?

A few maybe-useful notes: My macOS installation was made on a fresh NVME drive and an all new pc build (the one I'm currently using). My Windows drive is on a SATA3 SSD drive, the installation was made while on a different, quite older system running a Gigabyte P67A-UD3 MoBo, intel i7 2600k.

What BIOS version are you using? Have you tried with a different one?