Contribute
Register

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

I am using the latest MultiBeast

MultiBeast 11.3.0

MB.png
 
Thanks, I might have to try a different version of CCC. I have installed the current version twice, but still no go.

Thaigyver
Hello @Thaigyver,

Which version of CCC are you running and was it downloaded from the Mac App Store or directly from Bombich? If you’re certain you have the latest copy and it is registered, then Bombich Tech Support is an option. Due to security/sandbox requirements in macOS, Apps either need explicit permission to access system resources, or they need to secure private copies of selected resources.

Update: Please check if you see this:
Screen Shot 2019-06-09 at 2.39.32 PM.png
 
Last edited:
Was just about to pull the trigger on CaseySJ's build and then Wow Intel's new Ice lake. Guess I can wait a little longer although I was quite looking forward to an i9 build. Got to be worth the wait by the sound of it.
I am quite interested in building a next-generation system that competes with and democratizes the new Mac Pro. I absolutely do not blame Apple for building and pricing the new Mac Pro well out of the reach of individuals. The new Mac Pro is intended to be purchased by corporations of all sizes, not by individuals. It aims at the extreme high end.

But Apple has left a glaring hole in its modular lineup that is as wide as the Pacific and as deep as the Mariana.

That’s where my interest lies. A system that competes with the modularity and scalability of the new Mac Pro by employing Intel’s HEDT or Server class chips and chipsets starting with nothing less than the rumored X499, hopefully with support for PCIe 4.0 and significantly more PCIe lanes. (Whether macOS will support PCIe 4.0 remains an unknown.)

The new Mac Pro’s NVMe SSDs are benchmarking rather poorly at this time (2700-2800 MB/s). If you tuned in to Computex you no doubt saw benchmarks of single (non-RAID) PCIe 4.0 x4 NVMe SSDs exceeding 5000 MB/s in Read and Write! This alone puts the new Mac Pro to shame.

But the big question is when?

The best answer I can provide at this time is at least 9 months from now unless something changes in Intel’s roadmap.
 
Last edited:
Wow
I'd be interested to see what kind of scores you'll get.
Will you able to post a BruceX benchmark?

Ok got this to work. This is benchmarking the save time ? It was almost instant
 
Last edited:
The best answer I can provide at this time is at least 9 months from now unless something changes in Intel’s roadmap.
To be Honest I was going too get a Mac Pro but not at $6K. PCIe 4.0 and Ice lake is more than a tempting wait. I've been happily getting on for a while with my trusty 4790K build waiting for something worth the upgrade, These past few years have been slow in the Intel processor development market.
 
Wow
I'd be interested to see what kind of scores you'll get.
Will you able to post a BruceX benchmark?
Hi,
Sharing the same mobo and CPU (GA-Z390 Designare and i7-9700K, and a Sapphire RX 580 8GB Nitro+ Lite) as CaseySJ. Found my benchmarks be to be slightly higher than the ones I've occasionally encountered so far. Might be due to me using the Designare R6 and Scythe Mugen 5 pcgh.
If you could point me to the relevant "Bruce X benchmark" you're referring to, I'd be glad to help and share my results with you.

Edit:So, just tried the tonymacx86 Bruce X zip/topic (1st hit on google) using fxp 10.4.2 (10.4.4 kept crashing, not yet sure why). Score was pretty abysmal, ~60 seconds or so. Wondering if the recent posts about RX 580 vs "A"md RX 580 would make a significant difference..

Edit2:Dear CaseyMJ,
Even though video is only of secondary importance to me, this brief test made me wonder about this build's compatibility with FCPX. Fwiw, I'm on SMBIOS iMac19,1, i7-9700K and RX 580 8GB. All working as per your guide, videoproc showing HVEC and H264 check signs, etc. Could my slow Bruce X results be due to the iMac19,1 definition? And if so, would you have any suggestions as to how to get things sorted out properly? Thanks!
 
Last edited:
Thanks again. I have changed the RX 570 HD-AUDIO from SSDT to the arbitrary property and it works well.

I'm attaching my IORef file, if you could have a look that would be great.
View attachment 410355
On your motherboard, Thunderbolt is attached to device PCI0.PEG0 instead of PCI0.RP05. And there's an AMD graphics card at PCI0.RP05.

Therefore:
  • Mount EFI partition of your Mojave SSD and delete the existing CLOVER/ACPI/patched/SSDT-Z390-DESIGNARE-TB3HP-V4.aml
  • Copy the attached SSDT-THUNDERBOLT-HP-PEG0-V4.aml in its place.
  • Reboot and then see if you can insert and remove Thunderbolt and USB-C devices properly.
 

Attachments

  • SSDT-THUNDERBOLT-HP-PEG0-V4.aml
    6.1 KB · Views: 82
Hello @Thaigyver,

Which version of CCC are you running and was it downloaded from the Mac App Store or directly from Bombich?
Hello @CaseySJ

Just to follow up. I have the latest registered version of CCC, 5.1.9. I downloaded it directly from Bombich. Your Update was the answer for my issue.

410451


I had to go through a quick process to Grant Full Disk Access to CCC that was easy to follow. Once I completed that, your guide was fast and easy and worked perfectly with a bootable copy of my system. Thanks for providing the answer. I never found that during my search on the internet. Thanks so much for your time and your help.

Thaigyver
 
On your motherboard, Thunderbolt is attached to device PCI0.PEG0 instead of PCI0.RP05. And there's an AMD graphics card at PCI0.RP05.

Therefore:
  • Mount EFI partition of your Mojave SSD and delete the existing CLOVER/ACPI/patched/SSDT-Z390-DESIGNARE-TB3HP-V4.aml
  • Copy the attached SSDT-THUNDERBOLT-HP-PEG0-V4.aml in its place.
  • Reboot and then see if you can insert and remove Thunderbolt and USB-C devices properly.

Hi Casey,
I've already changed the SSDT for Thunderbolt from RP05 to PEG0 before.
But, when I compare your version and my version, there is still slight difference.
You have
External (_SB_.PCI0.PEG0.PXSX, DeviceObj)
I have
External (_SB_.PCI0.PEG0.PEGP, DeviceObj)
Can you please explain why you have PXSX in there?

Is there also any guide that would explain what which property in SDDT is? Or how you came up with it? I'd like to understand it more :)
 
Hi Casey,
I've already changed the SSDT for Thunderbolt from RP05 to PEG0 before.
But, when I compare your version and my version, there is still slight difference.
You have
External (_SB_.PCI0.PEG0.PXSX, DeviceObj)
I have
External (_SB_.PCI0.PEG0.PEGP, DeviceObj)
Can you please explain why you have PXSX in there?

Is there also any guide that would explain what which property in SDDT is? Or how you came up with it? I'd like to understand it more :)
Your version is correct! It should be PEG0.PEGP (for PCEe graphics processor). PXSX is Gigabyte’s default device under RP05 so we have to replace it.

Edit: The closest thing to a guide I’ve found is this 1000+ page PDF. I wish you good reading! :)
 
Last edited:
Back
Top