Contribute
Register

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

Any idea on what could be causing CPU halt or what to look for in verbose to figure it out? I see the gioscrren 3 prior then it halts.

Attached some screenshots of the video I got of the verbose.
Are you installing again from scratch? If not, I would strongly recommend to abandon the sunken ship and start again. The procedure and the install files have all been modified so you won’t be repeating the same thing.
 
The BIOS config guide for F8 doesn't mention clocking down the RAM to 2666 in order to get external drives to eject on sleep. Is this still necessary with BIOS f8 w/ Mojave?
 
I installed from another PC that I have because Clover crash when I want to boot from USB or SSD in SATA. I've never been able to boot on this motherboard.

Yes this dump is done by booting from the USB flash drive.

Here is my clover folder.
I see that you've tried to follow KGP's X299 build guide. I did the same for my Asus X99 system. Based on the X299 guide, I see some issues with your CLOVER configuration:
  • TSCAdjustReset.kext
    • IOCPUNumber should be 19 instead of 9 because your i9-9820X is a 10-core, 20-thread processor.
    • IOCPUNumber is set to number of threads minus 1, or 20 - 1 = 19.
    • I've modified the kext accordingly (attached).
  • The ACPI section of your config.plist does not contain any CPxx --> PRxx modifications. For example:
    Code:
    Comment: Find*[Hex] Replace [Hex]
    CP00 -> PR00 43503030 50523030
    CP01 -> PR01 43503031 50523031
    CP02 -> PR02 43503032 50523032
    CP03 -> PR03 43503033 50523033
    CP04 -> PR04 43503034 50523034
    CP05 -> PR05 43503035 50523035
    CP06 -> PR06 43503036 50523036
    CP07 -> PR07 43503037 50523037
    CP08 -> PR08 43503038 50523038
    CP09 -> PR09 43503039 50523039
    CP0E -> PR10 43503045 50523130
    CP0F -> PR11 43503046 50523131
    CP10 -> PR12 43503130 50523132
    CP11 -> PR13 43503131 50523133
    CP12 -> PR14 43503132 50523134
    CP13 -> PR15 43503133 50523135
    CP14 -> PR16 43503134 50523136
    CP15 -> PR17 43503135 50523137
    CP1C -> PR18 43503143 50523138
    CP1D -> PR19 43503144 50523139
    • Were these omitted intentionally?
  • The Kernel and Kext Patches --> KernelToPatch section does not contain the xcpm_core_scope_msrs patch.
    • This is OKAY if MSR 0xE2 is unlocked.
    • KGP has stated that all Gigabyte X299 motherboards have unlocked MSR 0xE2 registers, but you have the Gigabyte X299X Designare motherboard.
    • On the Gigabyte Z390 Designare, the MSR 0xE2 register is locked and there's no BIOS parameter for changing it. So we patch the firmware to manually unlock 0xE2.
    • Are you sure that your motherboard's 0xE2 register is unlocked?
      • Two ways to check MSR 0xE2:
        • Option 1:
          • At the Clover Boot Menu, press F2 to save the Preboot Log.
          • Move the USB flash disk to your working Mac and Mount EFI partition.
          • In the CLOVER/misc folder will be a file called preboot.log. Upload that file.
        • Option 2:
          • Please see this guide for checking your motherboard's CFG_LOCK parameter (MSR 0xE2). Only look at the sections labeled:
            • Background
            • Purpose
            • Preparation
            • Procedure
          • Do not follow Modifying the Firmware.
          • After the last step in Procedure, please provide a screenshot such as the one shown in Step 5 of that section.
    • The boot process will crash if MSR 0xE2 is locked, so we must determine its state.
      • If we cannot unlock MSR 0xE2, we must apply xcpm_core_scope_msrs.
  • The ACPI section has a number of settings shown below. Are they needed?
    Screen Shot 2019-12-12 at 7.16.24 PM.png
  • You're also using older versions of Lilu and WhateverGreen. Catalina requires WhateverGreen 1.3.4 or newer, with the latest being 1.3.5.
 

Attachments

  • TSCAdjustReset.kext.zip
    12 KB · Views: 55
Last edited:
Thanks @CaseySJ. Hackintool screenshot attached. I'm running SMBIOS iMac19,1
This looks normal. Are you using VideoProc to determine whether hardware acceleration is available for H.264 and HEVC?
 
The BIOS config guide for F8 doesn't mention clocking down the RAM to 2666 in order to get external drives to eject on sleep. Is this still necessary with BIOS f8 w/ Mojave?
This is optional. It's a tradeoff between memory performance and disk-eject. I use the Jettison utility to auto-eject disks prior to sleep, and, therefore, keep my memory running at full XMP speed.
 
This looks normal. Are you using VideoProc to determine whether hardware acceleration is available for H.264 and HEVC?
Thanks @CaseySJ. I installed VideoProc. Is this what I'm looking for? It doesn't say anything about my 5700 XT
 

Attachments

  • Screen Shot 2019-12-12 at 7.30.28 PM.png
    Screen Shot 2019-12-12 at 7.30.28 PM.png
    138.5 KB · Views: 73
Thanks @CaseySJ. I installed VideoProc. Is this what I'm looking for? It doesn't say anything about my 5700 XT
H.264 and HEVC are fully operational. When there are multiple GPUs, VideoProc (and several other apps) will pick the GPU whose name comes first alphabetically. These are the default names:
  • Intel UHD 630
  • Radeon RX 5700 XT
Because "I" comes before "R" you are seeing the result from Intel UHD 630. To prioritize the RX 5700 XT, we have to rename it to something like:
  • AMD RX 5700 XT
This can be done through device renaming as described here:
 
Are you installing again from scratch? If not, I would strongly recommend to abandon the sunken ship and start again. The procedure and the install files have all been modified so you won’t be repeating the same thing.

Just went all the way thru with new files and all from mini guide installer started, went all the way thru rebooted, came into the second time count no issues, then rebooted, brought me to clover again to start up macos welcome gui and getting CPU halted again..

F8 BIOS
and everything from mini guide new new hard drives too, flashed BIOS both of them, new drive and all its when i tried to open the Welcome GUI for the first time im getting cpu halted i cant recall how i fixed this last time or whats causing it.


Bottom half of verbose before shutdowN
 

Attachments

  • 8B851AEB-8FDF-4622-B4A5-D7E8A9EB39DC.png
    8B851AEB-8FDF-4622-B4A5-D7E8A9EB39DC.png
    11.6 MB · Views: 56
  • C1A1620F-F5C6-4C31-A3D7-8EC1DCFDC1F2.png
    C1A1620F-F5C6-4C31-A3D7-8EC1DCFDC1F2.png
    11.2 MB · Views: 52
  • 9C46A0AE-C0C0-4FCF-81E0-38AA83EF2F93.png
    9C46A0AE-C0C0-4FCF-81E0-38AA83EF2F93.png
    11 MB · Views: 54
Last edited:
@CaseySJ

Thank you very much for you reply, I will try all you said.
My preboot.log said " MSR 0xE2 before patch 00000400" and I don't have CFG_Unlock in the BIOS so I thinkmy motherboard is locked.
 
In addition to Inject Intel, please add the fake ID in Devices (IntelGFX = 0x12345678) and set ig-platform-id to 0x3E9B0007 from the pop-up menu in the Graphics section of Clover Configurator and try again.

If it still fails, add the boot argument -wegoff and try again.

Hey, sorry for the late reply, haven't gotten a chance to revisit until tonight.

Unfortunately it still is not working. A bunch of new lines appear in the startup, but then it hits the same line as before and the screen shuts off. I usually give it ~10 minutes before I force shut down and try again with an updated config.

I will say that, even though they stop at the same exact time, when I don't have wegoff in my boot arguments, the screen kind of glitches out and then shuts off. When I do have wegoff, it just goes black. Not sure if this is useful or useless info...
 
Back
Top