[SUCCESS] Ongoing Status of Designare Z390 with i7-9700K

[CaseySJ]

it was my first hackintosh and I feel so happy that with your Guide I was able to run it .... the only little problem that I have is when I boot macOS the screen stop and I have to plug and unplug the hdmi cable ( another old cable that I have ) for one time....but after that it work without any problem for now....it look like rx580 hdmi not wake up on boot ... someone have any tips for this ??

In your BIOS, do you have this setting under Chipset:

• Internal Graphics: Enabled
• Initial Display Device: PCIe Slot 1

the cable that give me a lot of problem is this one ( noise, black screen, plug & unplug ) ...dont buy it
https://www.amazon.com/dp/B003VX42MA/?tag=tonymacx86com-20

Thanks!

the Geekbench is 28283 ...not great as your because I have 8700k & 32 gb 2666hz ...and I still have macos on ssd ... I will migrate on nvme 1tb tomorrow .... I have to buy a tb2 /tb3 adapter for my uad octo satellite ... and your bt /wifi adapter ...

The WiFi/BT module and PCIe x1 adapter (2 pieces) will complete your system. A lot of good Mojave features require this.

 

[CaseySJ]

I tried rebuilding the kernel cache then re-enabling internal graphics. Computer still hangs but the last line now says "Start UncompressKernelCache" instead of "Start ReadKernelCache". Strange.

That's really strange. Can you compress and upload your EFI folder from the Mojave disk (not USB)? Please remove your Serial Number and Board Serial Number from SMBIOS of config.plist prior to upload.

Some other things to try:

1. Shutdown the system and pull the power cable from the power supply for at least 10 seconds. Just shutting down the system is not sufficient. Either flip the power switch on the power supply or pull the power cable. Then insert power cable again and start machine.
2. Re-apply BIOS settings: BIOS Setup --> Load Optimized Defaults (from the Save/Exit menu) --> then apply BIOS settings per Post #1.
3. Connect HDMI cable to RX580 at all times. Do not use HDMI on motherboard.
4. Try to boot Mojave...does it still freeze? At same place?

 

[logritm]

In your BIOS, do you have this setting under Chipset:

• Internal Graphics: Enabled
• Initial Display Device: PCIe Slot 1

Thanks!


The WiFi/BT module and PCIe x1 adapter (2 pieces) will complete your system. A lot of good Mojave features require this.

Internal graphic is enabled and initial display device is set to pcie slot 1 as you said ...
I bought another 3 mt cable and it doesnt work too ... i am able to use only 1.5 mt cable that i have ... but i need a 3 mt cable that work ... i am getting mad ....what cable do you have?

 

[CaseySJ]

Internal graphic is enabled and initial display device is set to pcie slot 1 as you said ...
I bought another 3 mt cable and it doesnt work too ... i am able to use only 1.5 mt cable that i have ... but i need a 3 mt cable that work ... i am getting mad ....what cable do you have?

I've had good experience with Amazon Basics cables such as this one that supports 4K 60Hz and comes in multiple lengths. And also Cable Matters, such as this one.

 

[embasy]

@CaseySJ Question for you, sir....

Have you tried to overclock the 9700k on this motherboard yet? I got mine up to 5Ghz easily, but for some strange reason, it doesn't allow me to go any higher. I changed my CPU Clock Ratio from 36 (stock) to 50 (5.0 Ghz) no problem, but if I go higher than 50, the computer freezes after restart/Mojave login screen. By no means am I asking you to troubleshoot this – just curious what your experience has been with OC'ing this build (if applicable).

 

[CaseySJ]

@CaseySJ Question for you, sir....

Have you tried to overclock the 9700k on this motherboard yet? I got mine up to 5Ghz easily, but for some strange reason, it doesn't allow me to go any higher. I changed my CPU Clock Ratio from 36 (stock) to 50 (5.0 Ghz) no problem, but if I go higher than 50, the computer freezes after restart/Mojave login screen. By no means am I asking you to troubleshoot this – just curious what your experience has been with OC'ing this build (if applicable).

Good question! I have not overclocked the CPU yet. My thinking is as follows:

• I’ve installed a 280mm liquid cooler that can handle the extra thermals, BUT...
• I see the overclcking ability as a means of future speed upgrade rather than immediate speed upgrade.
• On my old MacPro 3,1 the CPUs (2 of them) were socketed. While they could not be overclocked, they could be replaced with faster ones over time.
• Intel has a nasty habit of changing socket layouts every year or two, so I don’t think we’ll be able to swap in new CPUs over time. But we should be able to overclock the CPU at any time.
• So as technology moves forward and new versions of macOS are released, I will then overclock the CPU to “upgrade” the CPU without physically upgrading the CPU.

So I’m leaving the processor at stock frequencies until the the first upgrade bug stings me...

P.S. Was the AirDrop problem just a software setup issue?

 

[ripe_md]

CaseySJ,

I just wanted to give you a summary about the status regarding finalizing step 2 of the installation process.

1. As mentioned in one of my earlier postings I have successfully installed a version of 10.14.2 on my NVME SSD. I made a full backup of this drive to an internal SATA SSD.
   
2. I've bought a new 32GB SanDisk Ultra USB 3.0 stick and tried to do a plain installation on another SATA drive. Independent of the used installation media (SanDisk 32GB USB 3.0, SanDisk 128 GB 3.1Gen1, NoName USB 2.0) the installation always fails with the same errors described in my posting #145. So at least I cannot perform a repeatable installation from scratch.

In parallel I've created a working SSDT for USBInjectAll.kext to support my case (Fractal Design Define R6 with Connect D1).

 

[CaseySJ]

CaseySJ,

I just wanted to give you a summary about the status regarding finalizing step 2 of the installation process.

1. As mentioned in one of my earlier postings I have successfully installed a version of 10.14.2 on my NVME SSD. I made a full backup of this drive to an internal SATA SSD.
   
2. I've bought a new 32GB SanDisk Ultra USB 3.0 stick and tried to do a plain installation on another SATA drive. Independent of the used installation media (SanDisk 32GB USB 3.0, SanDisk 128 GB 3.1Gen1, NoName USB 2.0) the installation always fails with the same errors described in my posting #145. So at least I cannot perform a repeatable installation from scratch.

In parallel I've created a working SSDT for USBInjectAll.kext to support my case (Fractal Design Define R6 with Connect D1).

While preparing the Build Guide, I performed 3 fresh installations of Mojave to an external USB 3.1 SSD. I tested a couple of different settings to observe their effects. Sure enough, I ran into a reboot error at 15-minutes remaining. I also ran into garbled screen issue. I also ran into "Couldn't allocate runtime area" issues. But the Build Guide I finally posted avoids all of these issues.

The EFI folder on the USB install disk contains:

• slide=0 in config.plist
• USB port limit patch
• External icons patch
• No USBInjectAll. No Lilu. No WhateverGreen.
• No custom SSDTs in the ACPI/patched folder.
• AptioMemoryFix-Drv (in post-install, we replace this with OsxAptioFix2Drv-free2000, but not in first install).
• DVMT-Pre-Alloc = 64MB in BIOS
• DVMT Max = 256MB in BIOS

In other words, I just used the EFI folder created by UniBeast 9.0.0 (bootloader = UEFI, nothing checked on for Graphics Configuration) and enabled "slide=0" and "verbose".

When I ran into the crash/reboot at 15-minutes remaining, it happened right after a garbled screen problem ("still waiting for root device") because I had accidentally omitted the port limit patch. However, I just ignored the error, moved the USB disk to a USB 2.0 port, and launched 2nd stage again, which completed without error.

But with the port limit patch in place and slide=0, I did not encounter any issues.

 

[ripe_md]

...

• No USBInjectAll. No Lilu. No WhateverGreen.

...
In other words, I just used the EFI folder created by UniBeast 9.0.0 (bootloader = UEFI, nothing checked on for Graphics Configuration) and enabled "slide=0" and "verbose".

I'm also using a plain UniBeast stick. Today I've created also a vanilla stick, with the same result

At least to my understanding and verification using IORegistryExplorer you need USBInjectAll.kext in order to remove the USB port limit. Without USBInjectAll.kext the limit of 15 USB ports is still valid (in my case HS01-HS14 plus only SS01). That could also be the reason why you've succeeded using a USB 2.0 port (I guess HS09 or HS10), because all SS-ports except SS01 won't be mapped due to to the port limit.

In your user build description you have a screenshot (cc-kernel-args.png) showing the patch to remove the USB port limit. The shown value "83FB0F0F 83030500 00" is only valid for 10.14.0. For 10.14.1 and 10.14.2 it is "83FB0F0F 83030400 00". The same is valid for a screenshot in the section "Final Steps in Post-Installation". Just a minor remark to your excellent guide.

For the final configuration I have some questions:

• Is there a reason that you've installed certain kexts in /Library/Extensions? In my build (not the USB installer) I place all kexts within the Clover partition.
• What needs to be changed in "SSDT-Z390-DESIGNARE-RX580" if the RX 580 is installed in the central PCIe slot (#2)? Due to the fan size I cannot use slot #1.
• Currently I have issues with restart/shutdown/sleep. Tomorrow I have to follow up...

Thank you for your fantastic support to the community!

 

[CaseySJ]

At least to my understanding and verification using IORegistryExplorer you need USBInjectAll.kext in order to remove the USB port limit. Without USBInjectAll.kext the limit of 15 USB ports is still valid (in my case HS01-HS14 plus only SS01).

In the "Spoiler: System Status BEFORE Post-Installation", you can see that all ports are available without USBInjectAll.kext. Only the port limit patch is needed. Because I did the installation with 10.14.0, the port limit patch in the screenshots worked correctly.

That could also be the reason why you've succeeded using a USB 2.0 port (I guess HS09 or HS10), because all SS-ports except SS01 won't be mapped due to to the port limit.

I repeatedly installed Mojave from a USB 3.1 port without using USBInjectAll, but with only the port limit patch. In one particular case, however, I attempted the installation (also from a USB 3.1 port) without enabling the Port Limit Patch, and only then encountered the garbled screen. I did this intentionally to observe various outcomes and determine how to recover.

In your user build description you have a screenshot (cc-kernel-args.png) showing the patch to remove the USB port limit. The shown value "83FB0F0F 83030500 00" is only valid for 10.14.0. For 10.14.1 and 10.14.2 it is "83FB0F0F 83030400 00". The same is valid for a screenshot in the section "Final Steps in Post-Installation".

Good catch, thanks! I'll fix this by adding two port limit patches in the screenshot.

For the final configuration I have some questions:

• Is there a reason that you've installed certain kexts in /Library/Extensions? In my build (not the USB installer) I place all kexts within the Clover partition.

I have seen multiple posts from moderators of this forum recommending that all kexts be installed eventually into /Library/Extensions. I plan to fine-tune the system a bit more by applying more of the information presented by user KGP in his exhaustive work, spanning the following two threads:

• https://www.tonymacx86.com/threads/...c-pro-successful-build-extended-guide.229353/
  
• https://www.tonymacx86.com/threads/...o-x99-successful-build-extended-guide.227001/

Because of this, I don't consider my build final, so I haven't moved everything to /Library/Extensions. An advantage of keeping kexts in CLOVER is simply the ability to boot with all injected kexts turned off to aid in troubleshooting. But some kexts might not work reliably unless they're moved to /Library/Extensions. So it's a balancing act...

• What needs to be changed in "SSDT-Z390-DESIGNARE-RX580" if the RX 580 is installed in the central PCIe slot (#2)? Due to the fan size I cannot use slot #1.

If you search for "Slot-1" (using MaciASL), you can replace it with "Slot-2". If there's a SUN or _SUN field in the .AML file and it's set to 0x01, you should also change that to 0x02 or whatever slot you're using. SUN stands for Slot User Number. Fortunately, this SSDT is purely cosmetic so there's some room for trial and error. Because I'm on holiday vacation away from home, I don't have access to the hackintosh...