Contribute
Register

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

Ok new problem...

I'm now at the stage of Post install. Booting off Mojave SSD, but stalling in the boot screen 75% of the way through.

I'm at this step:
"After making the preceding changes, reboot the computer. After logging back in, we can take another look at the system configuration. Let's start with System Information --> Audio. We can see our built-in audio devices have appeared thanks to AppleALC 1.3.4 or later. (OWC Thunderbolt Audio devices are from my OWC 14-port Thunderbolt 3 dock.)"

When I run it in Verbose mode this I get this message:
Start RandomSeed
End RandomSeed
Error allocating 0x11c94 pages at 0x0000000021f23000 alloc type 2
Couldn't allocate runtime area


I've attached a picture of the Verbose for reference.

Any and all help, thoughts and suggestions are appreciated! I can't wait to get this up and be a part of the hackintosh fam.


My build:

MB: Gigabyte Z390 Designare
CPU: i9-9900k
GPU: MSI Aero 1070 Ti
SSD's: Samsung 970 Evo NVMe M2 Internal SSD 1tb, + 500tb (for OS)
RAM: Ballistix Sport LT 64GB Kit (16GBx4) DDR4 2400 MT/s (PC4-19200) DIMM 288-Pin - BLS4K16G4D240FSB (Gray)
Wifi: Fenvi T919 BCM94360CD Native Airport WiFi BT 4.0 1750Mbps 5GHz/2.4GHz MIMO
 

Attachments

  • Screen Shot 2020-03-26 at 10.36.19 PM.png
    Screen Shot 2020-03-26 at 10.36.19 PM.png
    5.7 MB · Views: 91
Try disconnecting your GPU. I was told Nvidia wouldn't work with this build, as there are no Mojave drivers for it. I was getting similar errors until tried just booting the internal graphics with no video card connected.
Ok new problem...

I'm now at the stage of Post install. Booting off Mojave SSD, but stalling in the boot screen 75% of the way through.

I'm at this step:
"After making the preceding changes, reboot the computer. After logging back in, we can take another look at the system configuration. Let's start with System Information --> Audio. We can see our built-in audio devices have appeared thanks to AppleALC 1.3.4 or later. (OWC Thunderbolt Audio devices are from my OWC 14-port Thunderbolt 3 dock.)"

When I run it in Verbose mode this I get this message:
Start RandomSeed
End RandomSeed
Error allocating 0x11c94 pages at 0x0000000021f23000 alloc type 2
Couldn't allocate runtime area


I've attached a picture of the Verbose for reference.

Any and all help, thoughts and suggestions are appreciated! I can't wait to get this up and be a part of the hackintosh fam.


My build:

MB: Gigabyte Z390 Designare
CPU: i9-9900k
GPU: MSI Aero 1070 Ti
SSD's: Samsung 970 Evo NVMe M2 Internal SSD 1tb, + 500tb (for OS)
RAM: Ballistix Sport LT 64GB Kit (16GBx4) DDR4 2400 MT/s (PC4-19200) DIMM 288-Pin - BLS4K16G4D240FSB (Gray)
Wifi: fenvi T919 BCM94360CD Native Airport WiFi BT 4.0 1750Mbps 5GHz/2.4GHz MIMO
 
Think you could help me get my Apollo working? did you just use the SSDT-Z390-DESIGNARE-TB3HP-V4 patch and it worked? did you have to flash the TB Controller in windows?

I can do exactly what you did in the video, but I get no sound through console or on the out meters on the Apollo 16 when I play audio from Live.
 
Last edited:
I followed ** MacOS Catalina 10.15.4 Update ** to update from 10.15.3 to 10.15.4, I did everything except “At the Clover Boot Menu press F11 to clear NVRAM.” Because nothing happened when I press F11. Then I booted into 10.15.3, and it full works,. So I went to settings to update. The update went well, but I could not login into the new 10.15.4. It shows memory panic as show in the picture. Any help would appreciated!

16592C1C-BF7E-4A6F-BCC3-6EF082C118F7.jpeg
 
The upgrade is quite straightforward, but there is one manual post-upgrade step we have to perform:
  • Make a full bootable backup first.
  • Run the Clover 5xxx .pkg installer.
  • Choose your Install Location. This is the existing macOS internal SSD.
  • Then click the Customize button on the lower left.
  • Check on only the following:
    • Clover for UEFI booting only
    • Install Clover in the ESP
  • All other options in the Customize section should be unchecked.
  • If you see a warning about the software not being supported on the current platform, select Continue Anyway.
  • When installation is complete, quit the installer.
Now we'll perform the manual post-upgrade steps:
  • First, you will notice that the EFI partition of the macOS SSD has already been mounted for you.
  • Navigate to the CLOVER folder.
  • You will now find two "drivers" directories:
    • drivers64UEFI -- this is the old one from Clover 4xxx
    • drivers/UEFI -- this is the new one from Clover 5xxx
  • Copy everything from the old drivers64UEFI folder to the new drivers/UEFI folder.
  • Open the new drivers folder (drivers/UEFI) and check that all the necessary drivers are present there.
    • What are the "necessary drivers"? They're the ones that are currently in the old drivers64UEFI folder.
  • Now we need to delete the old drivers64UEFI folder.
  • Reboot.

This is perfect - thank you so much!!
 
think you could help me get my apollo working? did you just use the SSDT-Z390-DESIGNARE-TB3HP-V4 patch and it worked? did you have to flash the TB Controller in windows?

I can do exactly what you did in the video,but I get no sound through console or on the out meters on the Apollo 16 when I play audio from Live.
I am on an X299 build with GC-Titan Ridge, and I used the TB SSDT from the KGP guide. I used the same SSDT on my buddies Z390 Aorus Master because he used the GC-Titan Ridge as well. So I am not sure and have never seen that issue. Maybe it has to do with your BIOS settings?
 
I'm an X299 user. GC-Titan Ridge is a DROM for Thunderbolt that has been changed to SSDT, but Thunder cannot be hot-plugged, and the computer freezes when the external hard disk is inserted into the Thunderbolt port. I'm using iMac Pro 1.1. Can you help me see what's going on. This is my SSDT.
I didn’t calculate CRC-32. Is this the problem? I still don’t know how he calculated it.

截屏2020-03-27 下午4.17.29.png

截屏2020-03-27 下午4.17.37.png
 

Attachments

  • SSDT-TB3HP.aml
    2.1 KB · Views: 100
Last edited:
You may try the attached modified firmware for the Gigabyte X299X Designare if you so choose. All disclaimers apply:
  • Flashing the chip incurs risk of damage.
  • The new firmware may not work at all.
  • You assume all responsibility / liability for the decision to flash the modified firmware.
We should always start by attempting 3 consecutive read attempts and making sure that all three checksums are identical (shasum <filename>). Then attempt to flash the chip.

If it's successful, read the chip once again just to be sure and compare checksum of the new file.

If everything is okay, perform a cold start (power cable removed or switch on PSU turned off for 10 seconds). On the first attempt, no Thunderbolt SSDT should be used.
I will give this a go asap and report back! Thank you very much @CaseySJ
 
Ok new problem...

I'm now at the stage of Post install. Booting off Mojave SSD, but stalling in the boot screen 75% of the way through.

I'm at this step:
"After making the preceding changes, reboot the computer. After logging back in, we can take another look at the system configuration. Let's start with System Information --> Audio. We can see our built-in audio devices have appeared thanks to AppleALC 1.3.4 or later. (OWC Thunderbolt Audio devices are from my OWC 14-port Thunderbolt 3 dock.)"

When I run it in Verbose mode this I get this message:
Start RandomSeed
End RandomSeed
Error allocating 0x11c94 pages at 0x0000000021f23000 alloc type 2
Couldn't allocate runtime area


I've attached a picture of the Verbose for reference.

Any and all help, thoughts and suggestions are appreciated! I can't wait to get this up and be a part of the hackintosh fam.


My build:

MB: Gigabyte Z390 Designare
CPU: i9-9900k
GPU: MSI Aero 1070 Ti
SSD's: Samsung 970 Evo NVMe M2 Internal SSD 1tb, + 500tb (for OS)
RAM: Ballistix Sport LT 64GB Kit (16GBx4) DDR4 2400 MT/s (PC4-19200) DIMM 288-Pin - BLS4K16G4D240FSB (Gray)
Wifi: fenvi T919 BCM94360CD Native Airport WiFi BT 4.0 1750Mbps 5GHz/2.4GHz MIMO
You have an aptio fix problem, check your drivers on EFI, perhaps you are using the wrong combo. You should use EmuVariables.efi along the posted OcQuirks from first post, also check BIOS settings, perhaps Above4G decoding is off?
 
Back
Top