Contribute
Register

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

@c0c0p0ps,

First of all, congratulations for beating Covid-19. I hope you're on the way to a full recovery.

The various issues you raised are all well known. So far all patched firmware on add-in-cards suffers from these issues. I wouldn't necessarily call them 'problems', but issues that can be worked around. Patched firmware on the Designare Z390's on-board controller (and on the Gigabyte Z390 Aorus Xtreme) is nearly perfect and does not suffer from these 'issues'.

The file SSDT-DTPG is necessary because it provides a helper function used by the Thunderbolt SSDT. Without SSDT-DTPG, the Thunderbolt SSDT will not function. The two files can be combined, but I do not recommend that practice because SSDT-DTPG can be used by other SSDTs only if it's in a separate file.

In System Information --> PCI, "Slot-4" is merely cosmetic. You may change this to your liking by downloading and running MaciASL from the Acidanthera GitHub website. It's just a matter of searching for "Slot-4" and replacing the "4" with something else.

Despite the small 'issues' with NVM23 on GC-Titan Ridge, I would gladly live with that because it allows my eGPU to function properly for the first time! In fact, I have a flashed GC-Titan Ridge installed on the Designare Z390 Test Bench right now. I therefore have 4 fully-functional Thunderbolt 3 ports on two Thunderbolt Buses!

Screen Shot 2020-04-07 at 7.57.03 AM.png
 
Hey @CaseySJ I have been following all the Thunderbolt developments keenly for the last few weeks while recovering from Coronavirus and what you and the other guys on here have achieved is pretty amazing. My build is based off the @Stork Asus Maximus Hero X so I never thought Thunderbolt was going to be a possibility until I saw what first DSM then @Elias64Fr achieved with the firmware.

So... I have managed to flash the TitanRidge card with the patched NVM23 from your repository, jumped the header cable and am very pleased to say that I

I’m going to be attempting this in a week or so, is jumping the header a necessary procedure for gc-titan ridge aic?
 
I’m going to be attempting this in a week or so, is jumping the header a necessary procedure for gc-titan ridge aic?
  • If your motherboard has a THB_C header, then connect the supplied cable to that header.
  • If your motherboard does not have a THB_C header, then tie pins 3 and 5 together using a simple F/F jumper wire.
 
I’m going to be attempting this in a week or so, is jumping the header a necessary procedure for gc-titan ridge aic?
I am using the AIC in a Z370 Asus Hero X motherboard which has no thunderbolt header or BIOS functionality. I never thought I would be able to add it to the system without a new board or system build but now I have it working perfectly well enough for my needs. What has been achieved in this thread really is amazing!
 
  • Does this problem occur after a clean installation of 10.15.4 (no third-party apps or drivers)?
  • Does this problem occur if all other USB devices are disconnected (except keyboard and mouse)?
  • Does this problem occur if you temporarily disable the 2.4GHz WiFi band on your router?

Thanks for the quick answer!
  1. Does this problem occur after a clean installation of 10.15.4 (no third-party apps or drivers)? --> YES
  2. Does this problem occur if all other USB devices are disconnected (except keyboard and mouse)? --> YES
  3. Does this problem occur if you temporarily disable the 2.4GHz WiFi band on your router? --> YES, no changes here either...
Should I reinstall Catalina 10.15.4 with SMBIOS: iMacPro1,1? (Sorry if it's nonsense, I'm rather inexperienced in the topic "Hackintosh")
 
@FormerUser-50757,

When we select Load Optimized Defaults, IOAPIC 24-119 Entries is automatically set to Enabled. Did you have to Disable it to obtain system stability?
Yes I did. But I enabled it again afterwards and stability continued. Maybe there’s a need to switch it manually in some cases? Maybe loading defaults doesn’t always work.
 
@c0c0p0ps,

First of all, congratulations for beating Covid-19. I hope you're on the way to a full recovery.

The various issues you raised are all well known. So far all patched firmware on add-in-cards suffers from these issues. I wouldn't necessarily call them 'problems', but issues that can be worked around. Patched firmware on the Designare Z390's on-board controller (and on the Gigabyte Z390 Aorus Xtreme) is nearly perfect and does not suffer from these 'issues'.

The file SSDT-DTPG is necessary because it provides a helper function used by the Thunderbolt SSDT. Without SSDT-DTPG, the Thunderbolt SSDT will not function. The two files can be combined, but I do not recommend that practice because SSDT-DTPG can be used by other SSDTs only if it's in a separate file.

In System Information --> PCI, "Slot-4" is merely cosmetic. You may change this to your liking by downloading and running MaciASL from the Acidanthera GitHub website. It's just a matter of searching for "Slot-4" and replacing the "4" with something else.

Despite the small 'issues' with NVM23 on GC-Titan Ridge, I would gladly live with that because it allows my eGPU to function properly for the first time! In fact, I have a flashed GC-Titan Ridge installed on the Designare Z390 Test Bench right now. I therefore have 4 fully-functional Thunderbolt 3 ports on two Thunderbolt Buses!

View attachment 460339
Thanks for the info on the SSDT-DTPG. I wasn't sure if it was something specific for your Designare board and could be problematic for me on an Asus Hero X, but now I know it is a 'helper' file I have no concerns keeping it in my boot folder.

I am actually really amazed at just how well the firmware and SSDT seems to be working. I know other users had reported that only slot 1 worked or the USB didn't seem to, but so far other than needing to do an unplug / replug everything seems to be working.

If the "Slot-4" in PCI is merely cosmetic is this something that could be removed from the SSDT completely and instead populated using Hackintool and Clover, Devices? Or do you think it would be better to change "Slot-4" for the correct PCI address? Did everything from the screenshots and IOReg I uploaded look correct to you?

Are you using the NVM23 firmware on your GC-TitanRidge or the NVM43? I also see some people have flashed them with the Designare NVM33 but I figured the NVM23 would be best place to start!
 
Thanks for the quick answer!
  1. Does this problem occur after a clean installation of 10.15.4 (no third-party apps or drivers)? --> YES
  2. Does this problem occur if all other USB devices are disconnected (except keyboard and mouse)? --> YES
  3. Does this problem occur if you temporarily disable the 2.4GHz WiFi band on your router? --> YES, no changes here either...
Should I reinstall Catalina 10.15.4 with SMBIOS: iMacPro1,1? (Sorry if it's nonsense, I'm rather inexperienced in the topic "Hackintosh")
If you're contemplating a reinstallation, it would be better to install 10.15.3 because the problem did not exist there (per your earlier post).

Have you already tried bringing the mice close to the antenna/USB-transceiver?
 
HI
This will happen if we don't select View --> Show all devices and then click the parent name of the USB flash disk on the left side. When you click Erase in Disk Utility, if you don't see three fields (Name, Format, Scheme) then the parent name has not been selected.

  • Are you running Mojave or Catalina?
  • Did you follow a different guide to setup macOS?
  • If so, open the CLOVER/drivers/UEFI folder. Which memory driver are you using? And do you have slide=0 in Boot Arguments?
HI Casey

Attempting to install Catalina - I take it will be 10.15.1 since I dowloaded installer from app store some while ago.

Attached are screen shots of my UEFI Drivers folder on 3 different memory sticks all Toshiba 32GB:- 2 of them are made using Unibeast from this site, and one made manually using the CreateinstallMedia command on Apples website followed by manual install of Clover boot loader. Thereafter experimenting with Aptio..Free2K, wRuntime and OSquirks following another guide.
Te one stick with AptioMemeoryfix.efi throws an error OABC Legacy version of AptioMemoryFix, and then stops.

The other 2 versions give me the Runtime allocation ....Type 2 error.

I have used slide set to zero and a few other values - no difference.

Lastly - I managed to create another bootable stick for EFI MSR - this time it created the refi partition, image of resulting page from grub - got a little further this time, but unsure where I'm at. I also learned that Disk Utility from earlier version of Mac OS Mavericks, and I'm currently using El Capitan, don't have the view all button available, they show everything by default.

Any further advice yo can give would be much appreciated
 

Attachments

  • UEFI_Screenshos 5.zip
    2.9 MB · Views: 69
Back
Top