Jump to content

[Guide] Mojave / High Sierra on Gigabyte H370 HD3 (Rev. 1.0)

Gymnae

By Gymnae,
in Installation Guides

 Share
119 posts in this topic

Recommended Posts

  • 1 month later...
Guillaume92
Guillaume92
Posted
Posted

Hi all,

 

Sorry for my english, I'm french.

 

It's my first attempt to build an hackintosh with my config : GygaByte H370 HD3, Intel I5 8400, 2x8Go Corsair LPX 2666 Mhz, IGPU Intel UHD 630 for OSX and GeForce GTX 1660Ti for Windows, Crucial P1 1 To NvME for OSX Samsung 1 To 860QVO for Windows

 

After 50-70 tries, the best i can do is to begin OSX install which is stop at 'end randomseed" in verbose mode with an automatic reboot. Before I had an "unallocated memory error" fixed by a CMOS reset and a new clover version.

 

My unsupported GPU and all unessential hardware are unmounted, and I have tried these solutions : 

 

- Clover configurator, [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url], Vanilla Config.plist...

- five differents Memfix drivers

- a lot of kexts (whatevergreen, USBInject, SMC Helper...)

- different SMBIOS 18'1, 18'2, 19'1....

- Slide=0

- Slide calculated with memmap in shell mode

- All the USB ports testedon my MB

- Change memory slots for RAM

-  Reset CMOS

- Bios settings from at least 3 guides

 

My current BIOS is F13.

 

You'll find in attachement my last EFI file, if someone more expert can have a look, it wil be really great.

 

Regards

 

Guillaume

 

EFI.zip

Link to comment
Share on other sites
blazewater
blazewater
Posted
Posted (edited)

hi, @Gymnae, today we can use ssdt get native NVRAM, just follow this post on redit: nvram for all 300 series users rejoice

Well Clover would like to give a quick "{censored} you" first if you installed RC scripts, as you may need to mount Catalina as R/W with SIP off before you can even clean up its mess. What garbage do you need to clean? Well see the following:

  • /Volumes/EFI/EFI/CLOVER/drivers/UEFI/EmuVariableUefi-64.efi
  • /Volumes/EFI/nvram.plist
  • /etc/rc.clover.lib
  • /etc/rc.boot.d/10.save_and_rotate_boot_log.local
  • /etc/rc.boot.d/20.mount_ESP.local
  • /etc/rc.boot.d/70.disable_sleep_proxy_client.local.disabled
  • /etc/rc.shutdown.d/80.save_nvram_plist.local
Edited by blazewater
  • Like 1
Link to comment
Share on other sites
  • 7 months later...
radius
radius
Posted
Posted (edited)

It's BigSur time!

 

I'm currently on Catalina with Clover r5107, I don't except to upgrade to BigSur until first or second patch release but I started to be prepared.

The goal of this post is to guide, with my finding, whoever would like to upgrade to BigSur.

As of today, I was able to do a from scratch install on a new partition. (I'm not ready to upgrade yet)

 

First steps..

To be able to boot BigSur, you will need Clover r5126[1] or newer. In Clover r5124, there is a major change, the inclusion of OpenCore

OpenCore[2] is an alternative bootloader that I discovered while working on BigSur upgrade, this bootloader is mandatory to boot BigSur, that's why it has been included in Clover. But OpenCore can be used standalone (but it doesn't have a nice GUI like clover to change boot parameter directly from the boot screen)

So I upgraded to Clover r5126, and guess what, it did not worked. This is because the inclusion of OpenCore adds new parameters in a section called Quirks. The latestest Clover Configurator[3] release have the needed GUI to configure this section.

But the question is "what need to be enabled and disabled in this section" ?

To know what the options means, we need to read OpenCore documentation[4]. At this point, I told myself "let's first try to use OpenCore alone (without Clover)" because OpenCore documentation[5] is very very good (and clover add stuff on top of OpenCore, so my guess is that it can only add problems)

The documentation is good, it's long but with time and by doing step by step, it's easy. I followed everything and ended up with something not booting (Kernel Panic right after starting Mac OS). I check the troubleshooting guide, etc.. nothing.

 

Solution

So I looked for help and found a GitHub repository[6] with OpenCore config for Gigabyte H370 HD3. And it works out of the box to boot Catalina and BigSur installer. On the repo ktg5 mention Sleep/Shutdown/Restart that I also face in some rare case, but that I guess I fixed (see Update 2)


 

Update 1

I got clover r5126 to works. I  just had to add the following Quirks section to my existing config.plist
Note that on my OpenCore install, I used VirtualSMC (as suggested in the documentation), with Clover VirtualSMC give me a kernelpanic, so I stayed with FakeSMC 

    <key>Quirks</key>
    <dict>
        <key>RebuildAppleMemoryMap</key>
        <true/>
        <key>DisableSingleUser</key>
        <false/>
        <key>SyncRuntimePermissions</key>
        <true/>
        <key>AvoidRuntimeDefrag</key>
        <true/>
        <key>SignalAppleOS</key>
        <false/>
        <key>DisableVariableWrite</key>
        <false/>
        <key>DisableLinkeditJettison</key>
        <false/>
        <key>DisableRtcChecksum</key>
        <false/>
        <key>DiscardHibernateMap</key>
        <false/>
        <key>DevirtualiseMmio</key>
        <true/>
        <key>KernelCache</key>
        <string>Auto</string>
        <key>EnableSafeModeSlide</key>
        <true/>
        <key>ProvideCustomSlide</key>
        <false/>
        <key>ForceExitBootServices</key>
        <true/>
        <key>MmioWhitelist</key>
        <array>
            <dict>
                <key>Address</key>
                <integer>4275159040</integer>
                <key>Comment</key>
                <string>Haswell: SB_RCBA is a 0x4 page memory region, containing SPI_BASE at 0x3800 (SPI_BASE_ADDRESS)</string>
                <key>Enabled</key>
                <false/>
            </dict>
            <dict>
                <key>Address</key>
                <integer>4278190080</integer>
                <key>Comment</key>
                <string>Generic: PCI root is a 0x1000 page memory region used by some firmwares</string>
                <key>Enabled</key>
                <false/>
            </dict>
        </array>
        <key>FuzzyMatch</key>
        <false/>
        <key>AppleXcpmForceBoost</key>
        <false/>
        <key>ProtectSecureBoot</key>
        <false/>
        <key>DisableIoMapper</key>
        <true/>
        <key>PowerTimeoutKernelPanic</key>
        <true/>
        <key>ProvideConsoleGopEnable</key>
        <true/>
        <key>ProtectUefiServices</key>
        <false/>
        <key>ProtectMemoryRegions</key>
        <false/>
        <key>DummyPowerManagement</key>
        <false/>
        <key>AppleXcpmExtraMsrs</key>
        <false/>
        <key>IncreasePciBarSize</key>
        <false/>
        <key>ProvideMaxSlide</key>
        <integer>0</integer>
        <key>EnableWriteUnprotector</key>
        <true/>
        <key>ThirdPartyDrives</key>
        <false/>
        <key>SetupVirtualMap</key>
        <false/>
        <key>ExternalDiskIcons</key>
        <false/>
        <key>XhciPortLimit</key>
        <true/>
    </dict>

 

Update 2 (done with OpenCore, I start to get used to it, may be I'll no longer use clover)

I tried to install BigSur on a dedicated partition and it failed in a kind of boot loop issue (stage 1 of BigSur works, it reboot for stage 2 and reboot for stage 2 and so on)

This was because my nvram was not working. This is because ktg5 repo miss SSDT-PMC.aml [9] in the ACPI directory. By adding this SSDT, BigSur install works just fine.

I also added SSDT-PLUG-DRTNIA.aml [10], this seems to fix the few restart/shutdown issue I had some time, and SSDT-AWAC.aml [11] (even if it seems useless on the H370 HD3 according to the DSDT dump - but I'm not sure)
This list of required SSDT for a Desktop Coffee Lake plateform are in [12] and [13]. I did not used SSDT-EC-USBX-DESKTOP as USB seems to works perfectly.

I attach my EFI folder, don't forget to change the plateform info part [14]

My folder is based on DEBUG version of OpenCore 0.6.3

 

Important stuff: you probably (and I recommend), make all the EFI test/change on a USB Drive or something similar, not your main OS X drive.
If your motherboard, by default, boot the EFI folder of you main drive, when installing BigSur, be sure to either change your motherboard setting to boot first on the USB Drive (best option) or be sure to be next to the computer to be able to choose to boot on the USB Driver when the installer will do it's different reboot.

 

Next steps

Config.plist is not perfect, if you do a check of the config using OpenCore Sanity checker[8] you will notice a few issue like deprecated entries.

My next step will be to compare my current config.plist (based on ktg5 one) with the original one I've done with dortania guide, and adjust it to the original one I've done.

My step 2 might be to move back to Clover, will see..

 

Hope it helps!

 

[1] https://github.com/CloverHackyColor/CloverBootloader/releases

[2] https://github.com/acidanthera/OpenCorePkg/releases

[3] https://mackie100projects.altervista.org/

[4] https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

[5] https://dortania.github.io/OpenCore-Install-Guide/

[6] https://github.com/ktg5/H370-HD3-Hackintosh-OC/

[7] https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/userspace-issues.html#macos-installer-in-russian

[8] https://opencore.slowgeek.com/

[9] https://github.com/dortania/Opencore-Install-Guide/blob/master/extra-files/SSDT-PMC.aml

[10] https://github.com/dortania/Getting-Started-With-ACPI/blob/master/extra-files/compiled/SSDT-PLUG-DRTNIA.aml

[11] https://github.com/dortania/Getting-Started-With-ACPI/blob/master/extra-files/compiled/SSDT-AWAC.aml

[12] https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-prebuilt.html#desktop-coffee-lake

[13] https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#acpi

[14] https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#platforminfo

EFI_OC.zip

Edited by radius
  • Like 1
  • Thanks 1
Link to comment
Share on other sites
  • 2 months later...
samosas
samosas
Posted
Posted

Radius, I used your open core method, but I got stuck on "authenticate efi forwared roothash: 2633: apfs extract root hash and manifest failed with error: invalid argument (22)". Then, the screen got blurred, and it then it made the stop sign.

Link to comment
Share on other sites
radius
radius
Posted
Posted
11 hours ago, samosas said:

Radius, I used your open core method, but I got stuck on "authenticate efi forwared roothash: 2633: apfs extract root hash and manifest failed with error: invalid argument (22)". Then, the screen got blurred, and it then it made the stop sign.

Can you give more context please, is it when booting the installer or after installation ? from usb drive or from hard drive ? 

I never saw this error and google doesn't give much result about it. If you are at trying to boot the installer, I would say you're usb drive is probably corrupted. You may try to reset the nvram as well

Link to comment
Share on other sites
samosas
samosas
Posted
Posted (edited)

I was trying to boot the from the installer usb drive, I will try to reset the nvram now. If that doesn't work I will make a new copy of the installer on a different usb drive.

 

For the steps I did:

  • I created a usb drive with the createinstallmedia.
  • I downloaded your OpenCore efi folder, and then I mounted the efi drive, and copied it in.
  • Then, I booted from the drive on my desktop.
Edited by samosas
Link to comment
Share on other sites
radius
radius
Posted
Posted
15 hours ago, samosas said:

I have read online that if I use FakeSMC instead of VirtualSMC that I will be able to get rid of this problem. Do any of you know how to do this?

Get FakeSMC.kext in the .zip file from https://bitbucket.org/RehabMan/os-x-fakesmc-kozlek/downloads/

In the EFI Folder, in OC/Kexts, remove VirtualSMC.kext and add FakeSMC.kext

Link to comment
Share on other sites
radius
radius
Posted
Posted
On 1/27/2021 at 8:02 PM, samosas said:

I used a usb 2.0 drive instead of a usb C drive, but then I got this error.

 

apfs_module_start:2436: load: com.apple.filesystems.apfs, v1677.60.23, apfs-1677.60.23, 2020/12/02

 

This message is normal, if it doesn't go farther, it would be a graphic card issue, what GC do you use ?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...