Jump to content
Gymnae

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

90 posts in this topic

Recommended Posts

On 4/22/2019 at 4:00 PM, poles89 said:

Hi,

 

I'm using the same motherboard (H370-HD3) with i5-8600 & RX 570 GB on Mojave 10.14.4. I have the same problem  "When I press shutdown it restarts the machine"

 

Things that I have tried:

 

1. Remove all usb connections as shutdown clicks

2. APCI-> FixShtdown = true /

3. Renaming FixShutdown to Fix_Shutdown_004 or FixShutdown_004

4. darkwake=2 or darkwake=8 in clover flags

 

Using AptioMemoryFix-64.efi in Clover/drivers64UEFI with EmuVariableUefi-64.efi though I didn't install RC scripts volume.

 

Can anybody help me to fix it? Thanks in advance.

 

Please check my initial post, you need to do some either DSDT or SSDT hotpatching to avoid this. 

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
13 hours ago, Gymnae said:

 

Please check my initial post, you need to do some either DSDT or SSDT hotpatching to avoid this. 

Thanks.

I used your DSDT file and also used slide=0 in clover bootflags to fix this issue. But one front usb port isn't working. I have 2 usb 2.0 & 1 usb 3.0 front usb ports. I think your Cabinet have different combination of in front usb ports...right?

 

I also noticed we really need to use AptioMemoryFix-64.efi & EmuVariableUefi-64.efi with  "install RC scripts volume" option as H370-HD3 doesn't support NVRAM.

Edited by poles89

Share this post


Link to post
Share on other sites

Yes, so far I haven't found a way to use native NVRAM :(

 

Regarding USB:

Recently I tested a new method with hackintool. The tool comes with its own manual. Following its procedure, you create either a kext or an .aml file which injects only your usb ports. I would give this a try and follow the documentation it provides.

 

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/16/2018 at 11:26 PM, Gymnae said:

1.4 Check BIOS and install

I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.

Thank you so much for your detailed guides.

Could I ask some question?

I hope to find the "hack2" file what you mentioned.

How can I find it?

Edited by kbright0912

Share this post


Link to post
Share on other sites
On 4/13/2019 at 2:09 AM, Gymnae said:

 

I gave up. Better to sell it.

Thank you very much!

I have throw it out of my window; // haha

And I have buy one DW1560, awesome, too easy to drive it!

now my wifi and bluetooth is OK.

thanks again.

Share this post


Link to post
Share on other sites
Posted (edited)

Guys, I'm testing something out, maybe you can test it to. This should both

a) lower our idle speed and make the system more responsive while reserving more power 

b) fully activate the iGPU for usage in mac os, making things smoother and more efficient

 

Here's how to do it:

  1. Change SMBIOS to Macmini8,1 (It's a coffee lake platform)
  2. Remove all iGPU injections, including any set IDs from config.plist
  3. Uncheck "KernelPm" if it was checked
  4. Make sure you have Whatevergreen.kext and lilu.kext installed
  5. Use hackintool to adjust our config.plist:
    1. "Framebuffer" menu, either select Mojave or High Sierra, depending on what you are using right now
    2. Select "Patch" -> "System Config" -> Gigabyte -> H370M-D3H
    3. This should lead to Platform-ID 0x3E9B0007 and device ID 0x3E9B
    4. Select "File" -> Export -> Clover config.plist and select your config.plist
  6. Upon reboot enter BIOS setup and select "Initialize display first: iGPU" (no matter if you have a dGPU installed)
  7. Have a display attached to iGPU and dGPU. If you only have one screen, move it to the iGPU. I think acceleration via dGPU will still happen...

My patch looks like this:

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Devices</key>
    <dict>
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>layout-id</key>
                <data>
                AQAAAA==
                </data>
                <key>model</key>
                <string>Cannon Lake PCH cAVS</string>
            </dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,GfxYTile</key>
                <data>
                AQAAAA==
                </data>
                <key>AAPL,ig-platform-id</key>
                <data>
                BwCbPg==
                </data>
                <key>AAPL,slot-name</key>
                <string>Internal</string>
                <key>device-id</key>
                <data>
                mz4AAA==
                </data>
                <key>device_type</key>
                <string>VGA compatible controller</string>
                <key>enable-hdmi20</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con0-alldata</key>
                <data>
                AQUSAAAEAADHAwAAAgISAAAIAADHAwAAAwQSAAAIAADH
                AwAA
                </data>
                <key>framebuffer-con0-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>model</key>
                <string>UHD Graphics 630 (Mobile)</string>
            </dict>
        </dict>
    </dict>
</dict>
</plist>
 

 

Side effect:

  • iGPU measurements gone from Intel Power Gadget, but still available in iStat Menu
  • My Idle dropped to 1.27GHz
  • Not checked it max speed is capped, it goes up to 3.80GHz right now

It if works for you too, I'll add it to the guide.

Edited by Gymnae

Share this post


Link to post
Share on other sites

Hi, thanks for this guide... I'm glad to see others using this mainboard for Hackintosh. I've been using Macmini8,1 SMBIOS and Platform-ID 0x3E9B0007 for about a month now and I can confirm that it's stable and no glitches with iGPU as I've seen with other SMBIOS id's. I have an I3 8100 which has a UHD 630 iGPU that's a little different, as I understand, than the others UHD 630's in the CPUs family. I have patched the framebuffer in order to get all 3 display ports of the MB (DVI, HDMI and even VGA... with a little workaround). I currently am using dual display with DVI and VGA. In idle the CPU goes down to 1.3-1.7GHz according to Power Gadget, 1.3GHz according to RehabMan's HWMonitor and maximum of 3.6GHz as you can see in the screenshot.

Stil... I'm not really sure if it's ok to use this platform ID if you have dGPU installed. I think it's better to use headless platform ID (0x3E920003 or 0x3E910003) and SMBIOS (imac18,x for Coffee Lake). It's closest to how real Mac works. 

Screenshot 2019-05-06 at 22.24.35.png

Share this post


Link to post
Share on other sites

iMac18,x are not Coffee lake - I noticed much better power management with macmini8,1 SMBIOS compared to iMac18,1 or iMac18,2

 

I use a dGPU with macmini8,1 and the only thing I need to do is to set the BIOS to initialize and use the iGPU first. Otherwise I get severe artifacts for all graphically accelerated apps and random KPs. The iGPU doesn't show up in Power gadget, but it is used for acceleration.

 

I have not tried a headless Coffee lake platform-id, I might do that before changing the guide to recommend a native Coffee lake SMBIOS.

Share this post


Link to post
Share on other sites
On 5/16/2018 at 7:56 PM, Gymnae said:

2018030711412939_m.png.9a96f3243c3af986d53e0934230cdd50.png

Introduction

The H370 chipset powers 8th generation Intel Core-i CPUs. Even though the name H370 rings comparable to Z370, the H370 is based on newer silicon. This it also requires some new approaches compared to the Z370. An example would be on-die USB 3.1 and WiFi support.

 

Since this guide is not a "hold-your-hand-every-step" guide, I assume you know:

  1. Clover installation and configuration
  2. How to create an install medium for MacOS
  3. Access and configure the BIOS
  4. Have heard of ACPI patching (I'm a newb at this myself)

 

What works

  • Sleep (via DSDT edits and emulated NVRAM)
  • On-board Audio (via AppleALC and native AppleHDA)
  • Native power management (without any kext or patch)
  • All USB ports (and only those present are active)
  • iGPU for both acceleration and display
  • dGPU (I'm running an Nvidia GTX 1080)

 

Untested

  • NIC --> I'm using WiFi only

 

What doesn't work

  • Native NVRAM via AptioMemoryFix.efi
  • DMVT Pre-alloc higher than 64MB (but not necessary)

 

Community additions

User @Panzerschiffe added a helpful post, altering this guide for user with AMD cards and not needing on-board sound.

He also runs Mojave, which I don't run yet.

 

 

Changes to the guide:

22.5.18: Added SSDT hot-patching to enable sleep, replacing DSDT static patching as an alternative.

23.5.18: Add iMac18,1 as alternative SMBIOS config for those relying on the iGPU for output

25.6.18: Added update info

28.8.18: Small changes for clarity, changed info for afps loading & updated USB patch for 13.6

04.10.18: Update to Mojave will come once Mojave is more mature

02.12.18: Removed unnecessary patches, fakepciid and audio patch method & linked to AMD post & added whatevergreen.kext as replacement for previous GPU kexts

02.03.19: Removed unnecessary fakeid and ig_platform_id injections, ACPI patches - this is all handled by whatevergreen & lilu. In testing is a Framebuffer patch, see this post.

04.03.19: Added Germany keyboard layout and updated pre-patched DSDT.aml removed DSDT patching

 

 

1. Installation

This guide heavy inspired by the work of /u/corpnewt of /r/hackintosh and his (sorta) Vanilla guide

 

1.1 Create the install media for MacOS

Follow this, if you are using a Mac to start off with. If you are totally new to MacOS, then please check the basic guide Creation of an installer media in windows or linux

 

1.2 Install Clover on the install media

Using the Clover installer, ensure you are installing to the USB medium you are using for the installer.

Chose the following options, leaving the others on default: 

 

  • UEFI driver: AptioMemoryFix
  • UEFI driver: ApfsDriverLoader
  • UEFI booting only
  • Install to ESP

 

You have to get your hands on an apfs.efi. A google search can help, or extracting it from the Installer package. Make sure you procure a version matching the MacOS version you are about to install. Place the apfs.efi in drivers64UEFI.

 

1.2 Adjust the config.plist for the installer

You can use the config.plist attached as a guideline, but take a look at it before and at least adjust the SMBIOS - otherwise it won't boot.

Attention: The attached plist contains audio patches introduced by a post-install step. If you run into problems, you might remove those. It also contains a manual slide value, which should normally not be needed, but works fine for me. It is also tuned for usage with an Nvidia Pascal dGPU as main GPU.

 

The config you create now should serve you nicely for install and running the system.

 

Take care of adding the following basics:

  • SMBIOS: iMac18,3 - You can generate a serial number via Clover Configurator. The creation of a proper SMBIOS is covered in many guides to good extend
    • Note: If you aim at using the iGPU for output, a user reported that iMac18,1 works better - since iMac18,3 produces severe flicker. I'm now also testing 18,1
  • Look at the graphics section and adjust the injection for Intel to your situation

 

Fixes

  Reveal hidden contents


<key>Fixes</key>
			<dict>
				<key>AddDTGP</key>
				<false/>
				<key>AddMCHC</key>
				<true/>
				<key>AddPNLF</key>
				<true/>
				<key>FixHPET</key>
				<true/>
				<key>FixIPIC</key>
				<true/>
				<key>FixRTC</key>
				<true/>
				<key>FixShutdown</key>
				<true/>
				<key>FixTMR</key>
				<true/>
			</dict>

 


Patches

  Reveal hidden contents

 



<key>Patches</key>
			<array>
				<dict>
					<key>Comment</key>
					<string>change SAT0 to SATA</string>
					<key>Disabled</key>
					<false/>
					<key>Find</key>
					<data>
					U0FUMA==
					</data>
					<key>Replace</key>
					<data>
					U0FUQQ==
					</data>
				</dict>
				<dict>
					<key>Comment</key>
					<string>Rename HDAS to HDEF</string>
					<key>Disabled</key>
					<false/>
					<key>Find</key>
					<data>
					SERBUw==
					</data>
					<key>Replace</key>
					<data>
					SERFRg==
					</data>
				</dict>
			</array>

 

 

 


Devices

  Reveal hidden contents

 



<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>1</string>
			<key>ResetHDA</key>
			<true/>
		</dict>
		<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>
	</dict>

 

 

 


Graphics

Important:

Change 0x59120003 to 0x59120000 if you don't use a dGPU as your main display Driver and instead use the iGPU for output.

Also note. SMBIOS iMac18,1 has been reported to work better in this configuration. But 18,3 works fine for me.

  Reveal hidden contents

Change 0x59120003 to 0x59120000 if you don't use a dGPU as your main driver and instead use the iGPU for output. Also note that SMBIOS iMac18,1 has been reported to work better in this configuration.



<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<true/>
			<key>NVidia</key>
			<false/>
		</dict>
		<key>NvidiaSingle</key>
		<false/>
	</dict>

 

 

 


Kernel and Kext patches

  Reveal hidden contents

 



<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleIntelCPUPM</key>
		<true/>
		<key>AppleRTC</key>
		<true/>
		<key>Debug</key>
		<false/>
		<key>KernelCpu</key>
		<false/>
		<key>KernelLapic</key>
		<false/>
		<key>KernelPm</key>
		<true/>
		<key>KernelXCPM</key>
		<false/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>External icons patch</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				RXh0ZXJuYWw=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.13.x</string>
				<key>Name</key>
				<string>com.apple.driver.AppleAHCIPort</string>
				<key>Replace</key>
				<data>
				SW50ZXJuYWw=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>change 15 port limit to 26 in XHCI kext (credit FredWst)</string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				g32UDw+DlwQ=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.13.x</string>
				<key>Name</key>
				<string>com.apple.driver.usb.AppleUSBXHCI</string>
				<key>Replace</key>
				<data>
				g32UGg+DlwQ=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>Prevent AGDP from loading (credit: vit9696) </string>
				<key>Disabled</key>
				<false/>
				<key>Find</key>
				<data>
				ugUAAAA=
				</data>
				<key>InfoPlistPatch</key>
				<false/>
				<key>MatchOS</key>
				<string>10.13.x </string>
				<key>Name</key>
				<string>com.apple.driver.AppleGraphicsDevicePolicy </string>
				<key>Replace</key>
				<data>
				ugAAAAA=
				</data>
				<key>true</key>
				<false/>
			</dict>
            <dict>
            <key>Comment</key>
            <string>USB 10.13.6 by PMHeart</string>
            <key>Disabled</key>
            <false/>
            <key>Find</key>
            <data>
            g32IDw+DpwQAAA==
            </data>
            <key>InfoPlistPatch</key>
            <false/>
            <key>MatchOS</key>
            <string>10.13.x</string>
            <key>Name</key>
            <string>com.apple.driver.usb.AppleUSBXHCI</string>
            <key>Replace</key>
            <data>
            g32ID5CQkJCQkA==
            </data>
        </dict>
		</array>
	</dict>

 

 

 

 

1.3 kexts and friends

Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.

 

Required kexts on "Other":

 

We are leaving sound out at the moment, this is something for post-install.

 

1.4 Check BIOS and install

You should be ready for install. But before you reboot, please take a look at your BIOS and set it up accordingly (copied from the aforementioned guide and adapted):

  1. Load Optimized Defaults
  2. Disable VT-d setting
  3. If your system has Secure Boot Mode, disable it
  4. Enable CSM - This is sometimes needed to dual screens to work
  5. Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference
  6. Turn off internal Serial and Parallel port
  7. Turn off Network stack for boot
  8. Turn off wake-on-lan (for now)
  9. Set XHCI Handoff to enabled
  10. Don't enable decode over 4G
  11. Depending on your GPU, set priority for boot
  12. Set internal GPU (iGPU) to enable - not auto or disabled
  13. Set DMVT pre-alloc min to 64MB and max to 128MB. For this selection to appear you might need to reboot after setting iGPU to enable
  14. Set USB legacy to enabled
  15. Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually)
  16. Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)

 

I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.

 

The install itself should be like other MacOS Hackintosh installs with it several reboots and ensuring to select the correct boot device in Clover.

 

2. Post-install

 

2.1 Install clover on target

This is a no-brainer, but install a fresh copy of Clover on your target medium.

 

During install select again AptioMemoryFix but also additionally

  • EmuVariableUefi-64.efi
  • Install RC scripts on target volume

because otherwise NVRAM doesn't seem to work

 

After the install, copy

  • config.plist
  • contents of "Other"
  • content of "patched"

to your new clover install.

 

2.2 Edit ACPI for slumber

Choose one option, not both. The hot-patch is experimental, but for the moment it is stable.

 

2.2.1 Edit DSDT

No more need for manual DSDT patching. If you still do it, you might run into unstable sleep. SSDT hot-patching + sane clover.config edits are enough

 

This is necessary only once on initial install and every time, you edit or upgrade the BIOS. The DSDT.aml attached to this post might work for your system or give you a file to compare to. Don't expect it to work for you, though.

EDIT: Since moving from F2 BIOS to F12 I did not repatch and sleep is still somewhat reliable. But to be 100% sure, you can still follow these steps.

I won't go into the details of DSDT extraction and patching. There are better guides (the linked guide is a rip-off of rehabman's guide from a different forum). Please follow such a guide to extract your ACPI data.

 

Locate and disassemble the DSDT with the newest iasl binary you can put your hands on, then open it with MacIASL in its newest version you can find (Hint: Here is a good source) You can check if the version is new enough if MacIASL doesn't throw error upon compiling a freshly extracted DSDT.aml or DSDT.dst

 

Add rehabmans repo (as per linked guide) and apply the following patches:

  • Rename _DSM to _XDSM
  • Fix _WAK Arg0 v2
  • USB3 _PRW 0x6D Skylake (instant wake)

Find the CNVW device and remove the _PWR function there.

 

Compile the DSDT and place it in "patched".

 

2.2.2 Use SSDT hot-patching

Instead of having to re-extract and re-patch the DSDT on every BIOS change or update, Hardware change one can also use ACPI hot-patching.

It's a combination of config.plist patches and an SSDT, which is hot-patched into the ACPI (if I understand the process correctly)

 

  1. You need to add this SSDT-GPRW.aml to your Clover folder in the designated position at Clover/ACPI/patched
  2. You need to add this patch to your config.plist. It goes into the DSDT patch section
      Reveal hidden contents

     

    
    
    	<dict>
    					<key>Comment</key>
    					<string>change Method(GPRW,2,N) to XPRW, pair with SSDT-GPRW.aml</string>
    					<key>Disabled</key>
    					<false/>
    					<key>Find</key>
    					<data>
    					R1BSVwI=
    					</data>
    					<key>Replace</key>
    					<data>
    					WFBSVwI=
    					</data>
    				</dict>

     

     

Note: This works for me, but the patch removes the _PRW method from all devices in the DSDT. This could have side-effects. So far, I have seen none. At the moment I'm also not applying any other patch, compared with the additional edits I made to the DSDT method before.

 

2.3 Install kexts to system

As mentioned in the install section, it's better to follow rehabman's instruction and install USBinjectAll.kext to /L/E:


sudo cp -R Release/USBInjectAll.kext /Library/Extensions 
sudo touch /System/Library/Extensions && sudo kextcache -u /

2.4 Enable onboard Audio - Install AppleALC kext

Make sure your EFI partition is mounted and that you have a vanilla AppleHDA kext available. See below for a guide how to get a vanilla AppleHDA if needed

Note: Our Audio codec is ALC887 and it's running with layout ID 1.

Download the newest AppleALC kext from here and install it together with lilu.kext from here into your usual /clover/kexts/others location. Done. No scripts or config.plist patches necessary.

Add layout ID 1 to config.plist, if it's not there yet:


<key>Audio</key>
		<dict>
			<key>Inject</key>
			<integer>1</integer>
			<key>ResetHDA</key>
			<true/>
		</dict>

If you previously  installed any  audio patches, please follow this guide to "vanilla-ize" your install.

 

2.5 Optional steps for Graphics

If you have a dGPU, now it's the time to install its drivers and adjust the config.plist for it. The detaisl are specific to your GPU and thus of scope of this guide. Yet, my supplied config.plist is ready to be used with Nvidia Pascal cards and using the Nvidia web driver.

Whatevergreen.kext helps with Intel iGPU and NVIDIA dGPU fixes.

 

At the moment I'm also testing out a special bootflag: 'shikigva=12' to enable faster rendering in Final Cut Pro X. Without whatevergreen.kext and a shikigva bootflag, rendering in final cut seem very slow.

 

2.5.1 Framebuffers

If you're facing problems with output from your internal GPU, you can try the framebuffer patches listed by @BackwardMac:

 

2.6 Install a proper keyboard layout

You might not be using a fancy Apple branded keyboard. If you use a PC keyboard, you might be annoyed by the differing layout and usage of keys. As a German, you might find yourself quitting applications, since alt gr + Q won't add an @, but quit your current application. To fix this, you can simply install a different keyboard layout. Copy it to /Library/Keyboard Layouts/ and chose the layout in System Preferences, Keyboard in the section "Other". Deleting the previously selecting layout makes sure that only this one is used. Nice little trick.

 

A keyboard layout for German keyboards is attached and works wonders

 

3. Updating

Updating inside 10.3.x/ 10.4.x point updates doesn't require much attention:

  1. Download the update from the AppStore as any Mac would do
  2. Allow the system to reboot
  3. Before booting MacOS with Clover, make sure to disable extra drivers for dGPUs which require non-native support.
    1. If using an Nvidia dGPU: Remove "nvda_drv=1"  from your boot arguments and disable Nvidia injection
    2. If using a non natively supported AMD card, do the same for AMD (I'm not using AMD, thus I cannot be specific)
  4. Boot into the newly created Install MacOS partition
  5. Repeat this process until the Install partition is gone
  6. Boot MacOS again, still following 3., and potentially install updated drivers
  7. Your Audio might require re-patching

 

4. ToDo

  • Move away from static DSDT patching to SSDT hotpatching --> requires my work
  • Native NVRAM --> requires developer work
  • Audio without AppleHDA patching --> requires developer work

 

5. Thanks to

@MaLd0nfor helping finding the right way with the DSDT

@RehabMan, for being a legend and helping me out patching

@toleda, for audio patches for the 300 series

/u/corpnewt, for his superb vanilla guide

@wmchris for his super XPS 9550 guide and introducing me to hot-patching

@Panzerschiffe for his addition to this guide

all the developers of clover and it's awesomeness

 

SSDT-UIAC.aml

 

 

 

win-germany.keylayout

 

 

@Gymnae

 

I have the same motherboard and tried to use the SSDT-UIAC.aml by placing in pathced folder of EFI but USB 3.0 & USB 3.1 ports only detects 2.0 usb drives. I tried USB 3 flash drives but its not being detected. The USB 3.0 flash drives only detetcted on fornt USB 2.0 ports.

 

Any help will be appriciated.

Share this post


Link to post
Share on other sites
24 minutes ago, poles89 said:

 

@Gymnae

 

I have the same motherboard and tried to use the SSDT-UIAC.aml by placing in pathced folder of EFI but USB 3.0 & USB 3.1 ports only detects 2.0 usb drives. I tried USB 3 flash drives but its not being detected. The USB 3.0 flash drives only detetcted on fornt USB 2.0 ports.

 

Any help will be appriciated.

 

Hi @poles89, first: Please, first don't quote the entire posts, it's massive and can be confusing.

 

Second, regarding USB. Please follow the instructions by hackintool to generate a .kext for driving your USB. Hackintool makes it easy. When you start following its tutorial, delete the SSDT-UIAC.aml - If you struggle to find hackintool or its for patching in your USB ports, then you might want to start with reading general starting guides about hackintoshs, because it's still more of a self-researching and self-teaching experience.

Share this post


Link to post
Share on other sites

@Gymnae thanks for your guide! can you please upload your config.plist and the SSDT-UAIC.aml so I can use them? I don't find the links or the links are not working. Thank you again :)

Share this post


Link to post
Share on other sites

@Donde, @poles89

USB patching may look intimidating but is not that hard to do and is better to do it yourself. Just follow @RehabMan 's guide. It's also a good exercise for what you will experience with building a hackintosh. Just in case I attach mine... Apart from the USB port at the back I have 2 front USB 2.0 (HS13 and HS14).

@Gymnae

I just installed a Nitro+ RX 480 so I started experimenting with headless mode. I'm using imac18,1 and 0x3E910003. For now everything seems ok. The card seems native... No extra kext and no clover change was required (except of course for the SMBIOS and Platform ID change for headless mode).

SSDT-UIAC.aml

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/16/2018 at 4:26 PM, Gymnae said:

 

1.3 kexts and friends

Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.

 

Required kexts on "Other":

 

 

@Gymnae seems XHCI-300-series-injector.kext is obsolete as per commit on the 20 Oct 2018 (https://github.com/RehabMan/OS-X-USB-Inject-All/commits/master)

The right kext to use is now XHCI-unsupported.kext and it can be found inside the zip https://github.com/RehabMan/OS-X-USB-Inject-All/archive/master.zip

 

 

About Macmini8,1 (take care it's Mac with M uppercase real mac mini, not sure if the difference has impact or not), I don't see much differnece in term of power management but I confirm it works as well as iMac18,3

 

About the "Kernel and Kext patches" section, the patch listed are for 10.13.x.

For people having trouble to have all USB port working, follow https://hackintosher.com/forums/thread/list-of-hackintosh-usb-port-limit-patches-10-14-updated.467/

There is the correct patch for 10.14.x. I got all my USB2 & USB3 ports working directly with USBInjectAll.kext + XHCI-unsupported.kext (but I'm not 100% it's useful, I haven't tried to remove it yet) + the patches for 10.14.x

Edited by radius

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By dracoflar
      So you've been reading the forum on this brand new boot loader called OpenCore hoping to try it out but you take one look at the configurations PDF and take a step back in shock at the complexity! Well if you've been feeling a bit intimidated by the DOCS well you've come to the right place:
       
      OpenCore Vanilla Desktop Guide
       
      If you have any issues or suggestions please feel free to comment
       
      - Your local neighbourhood Hackintosh Slav
    • By ignn
      Hello!
      I want install Hackintosh on my hardware
      Motherboard: Gigabyte B360M-HD3
      CPU: I3-8100
      GPU: Intel HD630
       
      Anyone has had experience installing on this hardware? Is there a guide? Thanks in advance
    • By JackBauer24
      Hello,
       
      I have installed OSx86 10.11 (El Capitan) on April 2016 on my Asus Z170 Deluxe system.
       
      For installation I used this Thread.
       
      I used it a lot and it worked well. Meanwhile I switched to Linux and I use Win10 time to time. So OSX was forgotten. Also it did not boot correctly anymore.
       
      Now I wanted to start with a fresh installation and use OSX more often again. I want to use OSX 10.13 High Sierra. Is it working on my Asus Z170 Deluxe? I have the same Hardware as of April 2016 only the graphics card was updated to a Nvidia GTX1080.
       
      My Hardware in detail: Asus Z-170-Deluxe (Bios 3801), i7-6700k, EVGA GeForce GTX 1080 SC GAMING ACX 3.0, Samsung 950 Pro/M2 NVME 512MB, HDD 4 TB)
      Can I use some of support files from the old thread for the installation (see attachment)? Can I still use  Clover 2.3k r3292 Special Edition v2 ? Or do I need a newer version?
       
      Has someone installed High Sierra successfully on the Asus Z170 Deluxe ?
       
      About some hints where to start I would be thankful.
       
      regards
      JackBauer24
       
      Z170DeluxeFiles.zip
    • By Amit Meena
      This card is working OOB, but it has some graphical issues as per attachments.

      If someone has a solution please share.






    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.13 installation on MBR partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.13 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.13 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. This patched MBR OSInstaller method works with both MBR and GPT partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.13 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?

      How to make 10.13 installer for MBR (MBR-Automatic-Method)?
      Just use 13MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, new for 10.13+.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.13.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       


       
×