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

[Stewie23]

So I have tired updates my OS X again to be faced with the same issue if a Kernel panic. last time you guys asked for a video to scrub through so that is attached, any help would be great, I have updated to the latest version of Clover before updating

 

[CaseySJ]

Thank you for your guide.My graphic fan does not whirl after entering the system.I folllow all your guide and use SSDT-Z390-VEGA64.aml to replace SSDT-Z390-DESIGNARE-RX580-V2.aml . so how to solve this issue?

This is normal because the AMD driver implements a fan curve that typically spins up the fans when GPU temp hits 50C or higher.

 

[gundogg9999]

I may have some not-so-good news regarding the ABWB card. Please see the top of this reply:

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

Hi, @CaseySJ I purchased your same 9 pin USB splitter but even if I configured my port with in 15 port actually for test at moment I have only 2 USB 2.0 in the back panel for mouse and keyboard and one internal USB 2.0 so total 4 port hs , when I connect the splitter in the internal port...

www.tonymacx86.com

If you follow the two links provided, you'll see that this card is not recommended because of the troubles people have reported. The Fenvi FV-T919 is the preferred choice.

The second issue occurs on real Macs as well. USB drives will not eject and reconnect before and after sleep. Third-party tools such as Jettison can help. Please see the spoiler labeled External Disks Not Ejected During Sleep:

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

CaseySJ's Coffee Lake in Phanteks Evolv X ATX Case: Gigabyte Designare Z390 - i7-9700K - UHD 630 - AMD RX 580 (Please do not quote this build guide in its entirely. Post a link instead.) (See this post for how to refer to a Guide or Mini-Guide.) URGENT: Please avoid Clover 5123 and newer for...

www.tonymacx86.com

Thanks a lot - any second choices, as I live in Germany and I cant seem to find the Fenvi FV-T919 so easily.. unless i wait 2 weeks for it..

 

[CaseySJ]

Hi everyone
I've been following this thread for weeks now and have successfully built a similar system, albeit with a Radion VII GPU - A huge thank you to everyone involved!

Looking at my log files I can see the following errors, but I've been unable to figure out what's causing them. The build seems to work perfectly, but there must be something not quite right (unless the errors are quite normal)

Could one of you geniuses spare a few minutes and take a look for me?

Many many thanks

Log files ETC attached



2019-08-08 09:21:17.286572+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) No Local Variables are initialized for method [_STA]
2019-08-08 09:21:17.287659+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform)
2019-08-08 09:21:17.287659+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform)
2019-08-08 09:21:17.287687+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) No Arguments are initialized for method [_STA]
2019-08-08 09:21:17.287688+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) No Arguments are initialized for method [_STA]
2019-08-08 09:21:17.288654+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform)
2019-08-08 09:21:17.288654+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform)
2019-08-08 09:21:17.288683+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-08-08 09:21:17.288683+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-08-08 09:21:17.288927+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-08-08 09:21:17.288927+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method parse/execution failed
2019-08-08 09:21:17.289545+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_TZ.TZ10._STA] (Node ffffff8051c06b10)
2019-08-08 09:21:17.289545+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_TZ.TZ10._STA] (Node ffffff8051c06b10)
2019-08-08 09:21:17.290397+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_AML_UNINITIALIZED_LOCAL
2019-08-08 09:21:17.290398+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_AML_UNINITIALIZED_LOCAL
2019-08-08 09:21:17.290987+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psparse-632)
2019-08-08 09:21:17.290987+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/psparse-632)
2019-08-08 09:21:17.291486+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-08-08 09:21:17.291486+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI Error:
2019-08-08 09:21:17.291738+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method execution failed
2019-08-08 09:21:17.291738+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) Method execution failed
2019-08-08 09:21:17.292246+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_TZ.TZ10._STA] (Node ffffff8051c06b10)
2019-08-08 09:21:17.292247+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) [\_TZ.TZ10._STA] (Node ffffff8051c06b10)
2019-08-08 09:21:17.293081+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_AML_UNINITIALIZED_LOCAL
2019-08-08 09:21:17.293081+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) , AE_AML_UNINITIALIZED_LOCAL
2019-08-08 09:21:17.293648+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/uteval-183)
2019-08-08 09:21:17.293648+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) (20160930/uteval-183)
2019-08-08 09:21:18.172064+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: sleep states S3 S4 S5
2019-08-08 09:21:18.187375+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188098+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188105+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188127+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188133+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188155+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.188161+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.191206+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.191235+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.191263+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.191291+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14
2019-08-08 09:21:18.191319+0100 0x71 Default 0x0 0 0 kernel: (AppleACPIPlatform) ACPI: cannot translate ACPI object 14

The \_TZ.TZ10 device path refers to Thermal Zone, which is one of the temperature monitoring zones on the motherboard. Your VirtualSMC configuration looks correct. Some suggestions:

• Check the version of VirtualSMC and download/install latest build. Remember to also copy latest VirtualSMC.efi into the drivers/UEFI folder.
• Post a screenshot of the /Library/Extensions folder and run Kext Utility to rebuild kernel cache.

 

[CaseySJ]

I just successfully booted using a new Clover Memory Manager, named MemoryFix.efi. It replaces AptioMemoryFix. I downloaded from an adjacent X299 thread here. (Thanks mm2margaret!)

I was able to boot using latest Clover with iGPU enabled with SMBIOS of iMac19,1. Slide was not present as a Clover boot argument. MacOS is Mojave 10.14.6. In drivers folder besides the new MemoryFix.efi were ApfsDriverLoader, EmuVariableUefi.efi, HFSPlus, NTFS, and VirtualSmc efi files. There was no panic re-boot during shutdown.

(And it also allowed a successful boot with OpenCore (v0.0.4) on the Z390 Designare, despite the warning on above post that MemoryFix was only for Clover.)

Alas my system continues to reject everything but OsxAptioFix2Drv-free2000... C'est la vie.

 

[CaseySJ]

Any news on local node for target display mode n the z390 designare?

After experimenting with the Asus X99, my current thinking on this is as follows:

Observations from Asus X99 Deluxe II and Falcon Ridge TB2 Controller

• MacOS initializes the Thunderbolt Bus and Thunderbolt Local Node device trees in IORegistry without the need for an SSDT or EFI drivers.
• The PCI and Thunderbolt driver families in macOS are sufficient for this purpose.
• However, certain Thunderbolt NHI device path properties are not injected by the kexts:
  • ThunderboltDROM
  • ThunderboltUUID
  • pathcr
  • ThunderboltConfig
• These properties, we believe, are injected by Apple's ThunderboltNHI EFI Driver during boot. That driver does more than just inject these properties because simply copying-and-pasting them via a custom SSDT does not seem to have any effect.
• Hot plug does not work. On Titan Ridge and Alpine Ridge (Thunderbolt 3) it is sufficient to inject 2 properties in the SSDT:
  • PCI-Thunderbolt = 1 --> inject into UPSB
  • PCIHotPlugCapable = 1 or 0 --> inject into DSB0
  • But on Thunderbolt 2, this is not sufficient.
• Thunderbolt devices do function when connected during boot.
• For eGPU to work during boot, we must remove PCI-Thunderbolt property from UPSB. On a real Mac, this property is never removed, so there's more going on behind the scene.
• Connecting this Hack directly to a Mac over a Thunderbolt 2 cable has so far been unsuccessful in establishing a Thunderbolt link between the two.
  • Still testing/experimenting with this.
• Looking at the SSDT from a MacBook Air 7,1 (with Falcon Ridge chip) we see that a number of Thunderbolt ACPI methods rely on GPIO registers.
  • These GPIO registers and their physical mappings are most likely native to the design layout of the MacBook Air circuit board and cannot simply be copied-and-pasted.
  • Apple might be using these registers to aid in TB2 hot plug capability and in to provide a more complete Thunderbolt implementation.

Implications for Titan Ridge Thunderbolt 3

• On all currently shipping Macs, Thunderbolt 3 is implemented with a combination of Alpine Ridge and Titan Ridge controllers.
  • Alpine Ridge controls UPSB
  • Titan Ridge controls DSB0 and everything else
• From the experience on Asus X99, we know that the Thunderbolt Bus and Thunderbolt Local Node device trees can be created by macOS drivers alone, without assistance from EFI drivers.
  • But those kexts seem to be querying the Thunderbolt controller directly to determine their Device and Vendor IDs.
  • My guess is that macOS drivers will not create the Thunderbolt Bus and Local Node devices if they don't specifically see an Alpine Ridge controller at UPSB.
  • So I already tried to spoof the UPSB Device ID in the Thunderbolt SSDT by injecting the Alpine Ridge ID.
    • It didn't work.
  • So another theory is that Apple might be using some special circuit/chip to integrate the two Thunderbolt controllers, and macOS drivers could be specifically looking for this circuit/chip.
  • However, it may be possible to patch the appropriate kext so that it bypasses the check for either (a) Alpine Ridge at UPSB, or (b) a special circuit/chip. To do this, we need to:
    • Determine which kext is looking for this trigger
    • Disassemble the kext and determine the hex patch
  • But then again, experience from the Asus X99 tells us that just obtaining the Thunderbolt Bus and Local Node device trees is insufficient because we still need an EFI Driver to inject:
    • ThunderboltDROM
    • ThunderboltUUID
    • pathcr
    • ThunderboltConfig

Most owners of this system do not really need Thunderbolt Bus and Local Node. But if this is something you really do need, then a real Mac is the only solution at the moment.

 

[CaseySJ]

So I have tired updates my OS X again to be faced with the same issue if a Kernel panic. last time you guys asked for a video to scrub through so that is attached, any help would be great, I have updated to the latest version of Clover before updating

CPUSensor is reporting an Unsupported CPU and throwing a kernel panic. I wonder if you're installing an obsolete set of FakeSMC sensors.

If this is happening during macOS installation:
Please compress and upload the CLOVER folder from the EFI partition of USB install disk.

If this is happening after installation when booting into macOS desktop:
Compress and upload the CLOVER folder from EFI partition of Mojave SSD and also post a screenshot of the /Library/Extensions folder.

 

[CaseySJ]

Thanks a lot - any second choices, as I live in Germany and I cant seem to find the Fenvi FV-T919 so easily.. unless i wait 2 weeks for it..

A second option is the Fenvi FV-HB1200:

Fenvi FV-HB1200 Desktop Wireless AC1200 Wi-Fi Adapter - Newegg.com

Buy Fenvi FV-HB1200 Desktop Wireless-AC Dual Band 1200Mbps PCIE Wifi Card,support Hackintosh Wi-Fi Adapter, Bluetooth 4.0, Windows 7/10/11,compatible with mac OS Big Sur/Monterey/Catalina,Airdrop,Handoff with fast shipping and top-rated customer service. Once you know, you Newegg!

www.newegg.com

If neither Fenvi card is available in Germany, it may be worth the 2-week wait for an international order...

 

[kolyasapphire]

Hi, everyone!

Read many messages that LG 5K runs only at 4K, is there a way to know for sure?

I'm using Thunderbolt on Designare and see:
LG UltraFine:
Resolution: 5120x2880 (5K/UHD+ - Ultra High Definition Plus)
UI Looks like: 2560 x 1440

Update: I'm using the old 5K, not the new one just released

 

[svandive]

Just some info. I have 5K LG Ultrafine, Radeon VII 2 4K LG UltraFine. My setup now is:

• Radeon DP Out 1 -> Designare DP in -> Designare TB1 (top one) -> LG 5K
• Designare TB2 (bottom one) -> LG 4K 1
• Radeon DP Out 2 -> Gigabyte Alpine Ridge add-on card (slot 2) DP in -> LG 4K 2

I don't have to authorize in Windows anymore to get camera, audio etc from LG 5K but still 5K at 4K resolution since I have the older version of the LG 5K. Hope this helps

BTW - the Gigabyte boot screen AND clover is at 640x480 on LG 4K 1 - only real issue

Is your iGPU Disabled in the UEFI?