Jump to content
Gymnae

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

90 posts in this topic

Recommended Posts

On 9/28/2018 at 1:29 PM, ssrgw said:

我个人远离****交流工具,我强烈建议不要在这里讨论这些工具。如果您想使用这些工具,请在他们的论坛中提问。 

 

关于音频:您的音频ID应该是布局1,您也可以尝试3.不要混淆方法。ALC脚本也不会产生任何错误,除了你没有的音频布局7外,它看起来不错。如果您使用该脚本,请按照toleda提供的使用说明进行操作。您需要安装香草AppleHDA和EFI需求。 

 

您下次可以在一个答案中发帖而不是创建三个答案吗?这使事情变得更容易。你可以在这个伟大的论坛编辑自己的帖子 :)

 

These are beautiful letters. Would you also be able to write this in English?

22 hours ago, Courage said:

please say, CNVW - how to remove _PWR ?

 

Do you mean how to edit methods? There are great guides by @RehabMan on how to use IOREG to do edits to your ACPI files.

Share this post


Link to post
Share on other sites
Advertisement
3 hours ago, Gymnae said:

 

These are beautiful letters. Would you also be able to write this in English?

 

Do you mean how to edit methods? There are great guides by @RehabMan on how to use IOREG to do edits to your ACPI files.

may be you help me?

my usb work only after sleep mode

usb 2.0 work fine

Share this post


Link to post
Share on other sites
On 9/19/2018 at 5:08 AM, Gymnae said:

 

Seems like you are missing essential kexts. Does this occur when you wan to install, or after you installed to your SSD and try to boot from the SSD?

Are you loading FakeSMC.kext ?

 

You can updated to the newest Bios no Problem - it's a good idea to be up-to-date with the flaws in the Intel Chips. 

 

I personally stay away from to****ac tools, and I'd strongly suggest to not discuss These tools here. If you want to use these tools, please ask in their forum. 

 

Regarding Audio: Your Audio ID should be layout 1, you can also try 3. Don't mix up methods. The ALC script also doesn't produce any error, it looks fine to me apart from the Audio layout 7, which you don't have. If you use the script, please follow the instructions toleda has given for ist usage. You need a vanilla AppleHDA and EFI Needs to be mounted. 

 

Could you next time post in one answer instead of creating three? That makes Things easier. You can edit your posts in this great forum :)

 

Thank you, Gymnae. I was able to install after updating to the newest BIOS. Then I got stuck for a while trying to boot from the SSD but I eventually figured out. Now I'm stuck trying to make it recognize my i5 8600k. 

a7d3ecb0-98d3-478a-adc8-4d0f3d9434da.jpg.35ad2a755ae4aebc7785f8cf28c86fd5.jpg

 

That is my current kexts folder:

 

87e0c47d-f24a-4b9f-ab28-704c4b43b6c2.thumb.jpg.7e0e1d38537c2ad0eb056e455f0314bc.jpg

 

I have tried to use 18,1, 18,2 and 18,3 SMBIOS. Tried to use 0x59120000 or 0x59120003 with no luck for iGPU too.

 

 

Edited by interrock

Share this post


Link to post
Share on other sites
On 8/28/2018 at 1:09 PM, Gymnae said:

Could you maybe detail your changes? It might be valuable input for others.

 

Hi every one, here is how to play with framebuffer

Issue is that all port of the motherboard are recognised as DisplayPort or HDMI. so you need to correct that.

here is the scrennshot of the 3 patch to use.

 

 

Screenshot 2018-10-29 at 16.44.26.png

Share this post


Link to post
Share on other sites

Thanks for the guide shared @Gymnae;

 

Using Mojave 10.14.1 at the moment which started supporting 8th gen intel cpus. Original content can be upgraded accordingly.

 

I used this guide as a starting point and helped me sorting things easily. I want to share some tricks that might help newbies to make things much more "easier". (Includes selecting newbie friendly parts)

This system will only work with RX and Vega graphic cards.

 

I will start with sharing my system:

 

Motherboard: Gigabyte H370 HD3 Rev:1.0 (with bios revision F10)

Processor: Intel Core i5-8600 Coffee Lake 6-Core 3.1 GHz

Graphics Card: PowerColor Radeon RX 570 (Model: AXRX 570 8GBD5-DMV3) (Note: It has Sapphire Pulse RX 570 8GB BIOS on it which performs better and Sapphire RX 5xx series are what I recommend)

RAM: 4x AVEXIR Budget Series RAM DDR4 4GB 2400MHz (16GB Total Installed)

Storage:  KingFast F9 2.5" 512GB SSD

PSU: Thermaltake SMART Series SP-750PCBUS 750W

Sound: 2x USB Sound Card

 

Install Clover on the install media

Same settings used with Gymnae. Don't touch defaults and select listed ones below.

 

UEFI driver: AptioMemoryFix

UEFI driver: ApfsDriverLoader

UEFI booting only

Install to ESP

Copy "apfs.efi" from source machine and paste into drivers64UEFI

 

Configuring config.plist

What to remove and add on original kext shared by Gymnae with using Clover Configurator;

 

Boot > nvda_drv=1 > uncheck

Device > FakeID > IntelGFX > remove that ID

Device > Audio > Inject > No

Device > Audio > ResetHDA > Uncheck

Graphics > Inject Intel > Uncheck (Don't enable anything on this screen RX 570 or RX 580 will work out of box)

Graphics > ig-platform-id > 0x59120003

Kernel and Kext Patches > KextsToPatch > select disable for the first 4 line from the top

SMBIOS > iMac18,2 > select

System Parameters > NvidiaWeb > uncheck

 

Configuring kexts

 

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

 

Required kexts on "Other", as you can see we are using lesser kext file:

  • FakeSMC.kext
  • IntelMausiEthernet.kext in case you're running Ethernet
  • USBInjectAll.kext with the HCI-300-series-injector.kext --> These two should be installed to /L/E after install
  • ***FakeSMC_Sensors.kexts (You need that if you are going to use different graphic card from "Sapphire" I don't know why but you might have thermal throttle problem. Do a benchmark test with HWMonitor and Heaven Benchmark.)

Bios Settings

Bios settings which I use:

  1. Load Optimized Defaults
  2. Disable VT-d setting
  3. If your system has Secure Boot Mode, disable it (You have to disable CMS to do that, just don't disable CMS and skip this part)
  4. Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference
  5. Turn off internal Serial and Parallel port
  6. Turn off Network stack for boot
  7. Turn off wake-on-lan (for now)
  8. Set XHCI Handoff to Enabled
  9. Don't enable decode over 4G
  10. Depending on your GPU, set priority for boot
  11. Set internal GPU to enable (Set internal GPU to disable. You don't need internal graphics with RX graphic cards and you will have lesser kext files)
  12. Set DMVT pre-alloc to 64MB
  13. Set USB legacy to enabled
  14. Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually)
  15. Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)

Install clover on target

 

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"
  • apfs.efi from drivers64UEFI

to your new clover install.

 

Edit ACPI for slumber

 

I had no major issue with stock sleeping settings so far. You might use the process described by Gymnae, but i didn't even try.

 

Don't Enable Onboard Audio

 

I'm using 2 USB sound card. Hey... They are cheap and easy to maintain. Connected one of them to my monitor and the other one to my headset.

***My graphics card only has a Dvi-D slot so audio might be already working on HDMI.

 

Updating

 

Just do it like you regularly update your Macbook. Just press restart for update button. It will do a pre-update and clover will select "install" twice automatically and computer will start like nothing happened.

 

Not Working?

 

iTunes Videos are not working, someone told me that this happened after 10.14.1, I'm really no sure about that. I will share a way if I can find one.

 

Edited by Panzerschiffe

Share this post


Link to post
Share on other sites

Hi guys

 

first: Thank you very much for that detailled and very well written guide. Its now the third time i assemble a Hackintosh (last time its 8 years ago i must admit!) and i went thru some strange stuff, but this time its really annoying:

I followed exactly the described setup procedure to install Mojave on new hardware, but my setup seems to have some strange issues. 

1. BIOS is running fine on newest version F11

2. Keyboard and mouse are running fine in BIOS

 

First strange thing:

The system wont use an 8GB Verbatim USB Stick prepared with procedure described. The Bios recognize the stick, but wont boot from it. 

Second:

I took an SATA HDD and prepared it the same like the USB Stick and - violá - it starts Clover from that, but right after that, Keyboard and Mouse are dead. Nothing. 

 

I tried some other stuff with additional USB related .efi, tried with the BIOS setings and even older Clover versions. Once i had a keyboard in Clover, but only one time. And with this time i started intalling Mojave, but it get stuck and restarted so fast the system, that i could not figure out, where the problem was. Is there any chance to prevent this restart?

It looks to me like i forgot something or made a stupid mistake. Maybe you have an idea what this could be?

 

regards

Markus

EFI.zip

Share this post


Link to post
Share on other sites

I have the Asus H370 and I "think" I can use your hot patch as the chipset is the same.  Advice?  I am using USBinjectall now and working.  I have not tackled sleep or sound yet, but have a functioning system.  Oddly sound worked initially.  I have a USB sound device that is flawless so I have not spent much time on it.

 

How would you tweak your guid if you were using a maxwell card?  

Share this post


Link to post
Share on other sites
On 10/29/2018 at 4:44 PM, BackwardMac said:

 

Hi every one, here is how to play with framebuffer

Issue is that all port of the motherboard are recognised as DisplayPort or HDMI. so you need to correct that.

here is the scrennshot of the 3 patch to use.

 

 

Screenshot 2018-10-29 at 16.44.26.png

Hi,

 

First thanks to @Gymnae and @Panzerschiffe  for the detailed tutorial. I'm trying to install Mojave on my new build (Gigabyte H370 HD3 - Bios F4 / Intel i5 8400 / iGPU) but have a black screen when the installation start it's GUI. (verbose boot works fine).

I tried both HDMI and DVI ports. I've correctly (I hope, I attached a screenshot) configured clover to use the iGPU but I haven't try @BackwardMac suggestion yet because I don't know where to put these patch. Can someone give more details ?

I'm not new to hackintosh but my previous motherboard (Gigabyte Z87-UD3H) was working fine out of box without all the patching required here.

 

Thanks for your help

 

IMG_9733.jpg

Edited by radius

Share this post


Link to post
Share on other sites

I got the intel gpu to work (in HDMI at least, did not try DVI) but with ig-platform-id set to 0x3E9B0007 (found that with help of google).

But from what I see metal is not working.

My interest in getting the intel GPU to work is just to be sure to be able to boot/troubleshoot in case of issue with the dGPU (I will use a RX 580 in the coming days) so it doesn't matter but if you intent to use the intel GPU permanently it's a problem.

 

I have a small issue, when I do shutdown, what happen is a reboot not a shutdown. Not huge problem but still a problem.

Share this post


Link to post
Share on other sites

Dear all, I'm still waiting for NVIDIA to release their web drivers for mojave, so I'm still running with 10.13.6

I did make some changes to the guide today:

  • Removed fakepciid* kexts since I don't see their need and they clash with the new audio method
  • Simplified and modernized audio patching via AppleALC. Now it (should) work(s) with mojave and we don't touch AppleHDA anymore, yay :)

Share this post


Link to post
Share on other sites
On 12/1/2018 at 4:56 PM, radius said:

Hi,

 

First thanks to @Gymnae and @Panzerschiffe  for the detailed tutorial. I'm trying to install Mojave on my new build (Gigabyte H370 HD3 - Bios F4 / Intel i5 8400 / iGPU) but have a black screen when the installation start it's GUI. (verbose boot works fine).

I tried both HDMI and DVI ports. I've correctly (I hope, I attached a screenshot) configured clover to use the iGPU but I haven't try @BackwardMac suggestion yet because I don't know where to put these patch. Can someone give more details ?

I'm not new to hackintosh but my previous motherboard (Gigabyte Z87-UD3H) was working fine out of box without all the patching required here.

 

Thanks for your help

 

IMG_9733.jpgr

 

Hi Radius, just to let you know that if you are using a coffee Lake CPU with Mojave, then my patch is not the best way because it only patch the Kabylake FrameBuffer

Since Mojave (and 10.13.6) have new support for CoffeLake with dedicated CoffeLake Frame Bufer (AppleIntelCFLGrphicsFrameBuffer in System/Library/Extension). better to use it, hear it's how :

 

Normally, to use the UHD 630 on CoffeLake with Mojave you need :

- last version of clover

- Last version of whatevergreen and lilu. (really important)

- No more graphics kext relate as intelgraphicfixup or nvidiafixup (replace with new whatevergreen/Lilu)

 

Then in config.plist :

- no need for intelGFX fake id (replace with whatevergreen/Lilu)

- no addHdmi, no addIMEI, no FixDisplay, no disablefxfirmware (replace with new whatevergreen/Lilu)

- ig platform 0x3E9B0007 works good as Raduis said and should be use. (support by new whatevergreen/Lilu)

- Some people say that you don't need injectIntel checked anymore as Whatevergreen do the job, but for my Mobo, I'm unable to boot without it.

 

I use all of that with a display on the DP port of my Mobo since few weeks now, and it works really really well, all sleep work no kernel panic, no glitches even during progress bar a boot, BUT :

 

The mapping of the frameBuffer isn't really good, as all my port in IOReg are in HDMI mode. (my screen is connected to DP ans words well....)

So the UHD 630 need an other Framebuffer patch to change the port type on Mojave because it is on an other kext.

I actually trying doing it, but without success for now.

Will keep you in touch

 

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
On 11/26/2018 at 6:03 PM, blueridgedog said:

I have the Asus H370 and I "think" I can use your hot patch as the chipset is the same.  Advice?  I am using USBinjectall now and working.  I have not tackled sleep or sound yet, but have a functioning system.  Oddly sound worked initially.  I have a USB sound device that is flawless so I have not spent much time on it.

 

How would you tweak your guid if you were using a maxwell card?  

 

If thinks are running fine, I wouldn't tweak too much. All you tweak, can break. Sleep is important to me, both to my machine and myself ;) So I'd work on that. For this you might need to go through the USB port patching process.

 

On 12/1/2018 at 10:18 PM, radius said:

I got the intel gpu to work (in HDMI at least, did not try DVI) but with ig-platform-id set to 0x3E9B0007 (found that with help of google).

But from what I see metal is not working.

My interest in getting the intel GPU to work is just to be sure to be able to boot/troubleshoot in case of issue with the dGPU (I will use a RX 580 in the coming days) so it doesn't matter but if you intent to use the intel GPU permanently it's a problem.

 

I have a small issue, when I do shutdown, what happen is a reboot not a shutdown. Not huge problem but still a problem.

 

As @BackwardMac correctly states, you need whatevergreen.kext combined with lilu.kext. If you only have an Intel iGPU at the moment, you might try to boot without any additional shiki bootflag, but if metal won't work, you can add 'shikigva=1' as bootflag and test. At the moment I'm running with 'shikivga=12' and have metal acceleration for both NVIDIA dGPU and Intel iGPU for HEVC and h.264. (Yet, FCP X is still super slow in encoding).

 

14 hours ago, BackwardMac said:

Then in config.plist :

- no need for intelGFX fake id (replace with whatevergreen/Lilu)

- no addHdmi, no addIMEI, no FixDisplay, no disablefxfirmware (replace with new whatevergreen/Lilu)

- ig platform 0x3E9B0007 works good as Raduis said and should be use. (support by new whatevergreen/Lilu)

- Some people say that you don't need injectIntel checked anymore as Whatevergreen do the job, but for my Mobo, I'm unable to boot without it.

 

 

I'll try this new platform ID, thanks @BackwardMac. At the moment I'm using the ig-platform-id 0x59120003 combined with whatevergreen, lilu and a shikigva=12 flag. I've never had InjectIntel active, maybe my current FakeID is the reason - I'll delete this, try the new platform ID and see.

Edited by Gymnae

Share this post


Link to post
Share on other sites

Hello Everybody, 

 

I was able to make the patch for correct port type with UHD 630.

Be aware that I d'ont know if everyone need to use it.

But since all graphics relate are manage by whatevergreen/llilu, there is a new way to change port type.

You will find those patch in my uploaded config.plist, in device/properties.

 

More info to make your own at : 

 

CLOVER(v2Mojave).zip

Share this post


Link to post
Share on other sites
On 12/3/2018 at 7:36 AM, Gymnae said:

I'll try this new platform ID, thanks @BackwardMac. At the moment I'm using the ig-platform-id 0x59120003 combined with whatevergreen, lilu and a shikigva=12 flag. I've never had InjectIntel active, maybe my current FakeID is the reason - I'll delete this, try the new platform ID and see.

 

I tried ig-platform-id "0x3E9B0007" and "0x3E9B0003", both times the iGPU wasn't attached properly. I guess this be could because these two platform ids only work for a special build of 10.13.6 for new Apple hardware and official  10.14.x builds.

 

I'm back to "0x59120003", InjectIntel, IntelGFX fakeid, shikigva=12

This setup results in full metal/openCL acceleration for HEVC and h.264. FinalCutPro X is still super slow in encoding, thus I switch to Davinci Resolve. This makes full use of the CPU and GPUs.

 

When NVIDIA web drivers are available, I will revisit this.

Edited by Gymnae

Share this post


Link to post
Share on other sites
2 hours ago, Gymnae said:

I guess this be could because these two platform ids only work for a special build of 10.13.6 for new Apple hardware and official  10.14.x builds.

Yes it is probably that, I wasn't able to use the 0x3E9B0007 in 10.13.6.

I think support for coffeelake on 10.13 is only on the built for last macbookpro..

 

2 hours ago, Gymnae said:

This setup results in full metal/openCL acceleration for HEVC and h.264. FinalCutPro X is still super slow in encoding, thus I switch to Davinci Resolve. This makes full use of the CPU and GPUs.

Can you tell me how you check for metal/opencl HEVV H264..? I don't really know how to, I just check "about this Mac", check transparency, memory, glitch and Geekbench.

 

 

 

2 hours ago, Gymnae said:

When NVIDIA web drivers are available, I will revisit this.

I don't really need it ut I'm waiting too and it is a big subject actually, will those driver arrive one day?

For now I have a little GT 740 which work OOB but I think about buying a new one, and it's appear that AMD is now the good choice for direct support on Mac OS X.

Shame, I prefere Nvidia..

 

Share this post


Link to post
Share on other sites
On 12/1/2018 at 6:56 PM, radius said:

Hi,

 

First thanks to @Gymnae and @Panzerschiffe  for the detailed tutorial. I'm trying to install Mojave on my new build (Gigabyte H370 HD3 - Bios F4 / Intel i5 8400 / iGPU) but have a black screen when the installation start it's GUI. (verbose boot works fine).

I tried both HDMI and DVI ports. I've correctly (I hope, I attached a screenshot) configured clover to use the iGPU but I haven't try @BackwardMac suggestion yet because I don't know where to put these patch. Can someone give more details ?

I'm not new to hackintosh but my previous motherboard (Gigabyte Z87-UD3H) was working fine out of box without all the patching required here.

 

Thanks for your help

 

IMG_9733.jpg

 

It is out of topic but I recommend you updating your bios, F4 had some issues. Your CPU Led probably glowing red after boot.

Share this post


Link to post
Share on other sites
On 11/11/2018 at 11:13 AM, Panzerschiffe said:

 

  1. Set internal GPU to enable (Set internal GPU to disable. You don't need internal graphics with RX graphic cards and you will have lesser kext files)

 

 

I advise keeping this as enabled. Since Mojave Mac OS is doing JPEG decoding in hardware using the GPU but it seems to rely on the iGPU even when you have a dGPU (I have a RX580 - by the way it's a Sapphir Nitro rx580, work out of the box without any clover config, neither Lilu/Whatevergreen).

If you disable the iGPU you will likely have preview and quicklook not able to render JPEG. 

There is a kext that can fix that (https://github.com/vulgo/NoVPAJpeg) but keeping the iGPU enable is easier. 

Share this post


Link to post
Share on other sites

Hello. I have an H370 HD3 bios verison F2, i5 8400, 8Gb RAM, Nvidia GT1050Ti, 256gb SSD Kinston, and I'm trying to install High Sierra but I cant't even start. 

 

I,ve created my 8gb usb with the kext, config.plist with my macbook following the instructions , I've configured the bios as described in the first post, and load the setting in the hack2 file, but when I select in clover the usb, in a few second the installation stops and I have a message "THIS VERSION OF MAC OS X IS NOT SUPPORTED ON THIS PLATFORM!".

 

Anybody can help me?

 

 

20181213_202039.thumb.jpg.bd4354189b851475e2b5835d8b68530a.jpg

Edited by orchalino
error in bios version

Share this post


Link to post
Share on other sites
On 12/13/2018 at 1:20 PM, themacmeister said:

Thanks for the guide, it got my H370 HD3 running, I just did a clean install of Mojave 10.14.2, and LayoutID 7 does not seem to work?

Try LayoutID 1

If I remember correctly, with the newest method posted in the guide you don't have to set a LayoutID manually, the kext defines it automatically. Thus I'd try ID 1 and no ID injection

On 12/13/2018 at 7:39 PM, orchalino said:

I,ve created my 8gb usb with the kext, config.plist with my macbook following the instructions , I've configured the bios as described in the first post, and load the setting in the hack2 file, but when I select in clover the usb, in a few second the installation stops and I have a message "THIS VERSION OF MAC OS X IS NOT SUPPORTED ON THIS PLATFORM!".

 

 

 

 

Do you have FakeSMC.kext in /Other ?

It's best not to use the files attached - in fact I'll delete them - instead enter the BIOS settings manually. If this is your very first attempt, I'd recommend to also read a more thorough, beginner guide, because this build doesn't require exotics settings, a proper vanilla guide is a great point to start. Check out this one: https://hackintosh.gitbook.io/-r-hackintosh-vanilla-desktop-guide/

Share this post


Link to post
Share on other sites

Thanks for your reply. 

Yes, I've FakeSMC.kext in the /others directory, and I,ve tried to configure the bios manually and with your archive, without success. It isn't my first hackintosh, my first was a Snow Leopard with iAtkos, and have another High Sierra in a Gigabyte Z87X, but I don't know how to solve this problem with this motherboard. It could be due to the F2 bios version?

 

This is the /other files in my usb pen.

821379965_ScreenShot2018-12-17at15_19_54.png.47695320faa562d6031be85936717272.png

 

And the patched directory.

 

1049538764_ScreenShot2018-12-17at15_20_19.png.f1545673f1c89977ff7232b086653aea.png

 

Thanks again for your help. 

 

Edited by orchalino

Share this post


Link to post
Share on other sites
7 minutes ago, orchalino said:

Thanks for your reply. 

Yes, I've FakeSMC.kext in the /others directory, and I,ve tried to configure the bios manually and with your archive, without success. It isn't my first hackintosh, my first was a Snow Leopard with iAtkos, and have another High Sierra in a Gigabyte Z87X, but I don't know how to solve this problem with this motherboard and this graphic card.  

 

This is the /other files in my usb pen.

821379965_ScreenShot2018-12-17at15_19_54.png.47695320faa562d6031be85936717272.png

 

hanks again for your help. 

 

 

Are you sporting an nvme drive?

Delete IntelGraphicsFixup, NvidiaGraphicsFixup and VoodooHDA. VoodooHDA should never be needed and replace the GPU fixups with whatevergreen.kext.

Have you googled for your error? For me this was in past when FakeSMC wasn't read correctly. But resetting the BIOS to default and starting from there can also help.

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   1 member

  • Similar Content

    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?f=45&t=9172
       
      ---USB---
      https://pikeralpha.wordpress.com/2016/07/13/simple-skylake-usb-fix-no-kexts-required/
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By rtke333
      Hi!

      Could anyone help me installing High Sierra on this system?
      I succesfully installed Sierra before on this system with help of Jake Lo (thanks!!), I just wondering if could High sierra possible to installed on this system?
      Boot stopped at this. I'll attach my Clover folder and a picture from boot.
      UEFI enabled, and for skylake I used IntelGraphicsDVMTfixup and IntelGraphicsFixup kexts. My bios is very limited and does not have any option to change dvmt prealloc or anything else.
      Everything works fine on Sierra.
      Here is my system:
       
      THIS TOPIC IS OUTDATED AND WILL NO LONGER UPDATED.
      PLEASE GO TO THIS LINK FOR GUIDE & UPDATED FILES:
      https://www.insanelymac.com/forum/topic/338103-guide-acer-aspire-v-15-v5-591g-mojave-windows/
       


      Acer Aspire V15 V5-591G-55TU
       
      (Note: Bootpack works fine with another versions of 591G, for example: V5-591G-71K2, -764Z, -59PU, etc.)

      Mobo: Skylake USOPP_SLS
      Bios: Insyde corp latest version
      CPU: Intel Core i5-6300HQ 2.30 GHz (Skylake)
      GPU: Geforce GTX 950M 2 GB (optimus, disabled), Intel HD 530
      Ram: 8 GB DDR4 (4+4 GB)
      Wifi: Qualcomm Atheros QCNFA344A, Replaced to BCM94352Z
      Ethernet: Realtek 8168B/8111B
      Audio: ALC 255 (layout-3 fix)
      Card Reader: Realtek
      HDD: 1 TB
      Dual-boot with Windows 10

      Any help appreciated!

      UPDATE! (2017.10.30)
      UPDATE! (2017.11.09)
      UPDATE! (2018.02.01)

      Successfully installed High Sierra 10.13, 10.13.1, 10.13.3
      SEE THIS POST: #49 IF YOU THINK YOUR CPU IS HOT (60+°C) OR NOT GOING UNDER 1.3GHz FREQUENCY WHEN IDLE
      (Original OSXLatitude post link: http://forum.osxlatitude.com/index.php?/topic/10077-success-acer-aspire-v-15-v5-591g-55tu-high-sierra-dual-boot-windows/)
      Working:
      Wi-Fi and Bluetooth with BCM94352z: (enabled with BrcmFirmwareRepo.kext, BrcmPatchRAM2, FakePCIID.kext, FakePCIID_Broadcom_WiFi.kext, install them with Kext Utility or another kext installer) (Original WiFi is Qualcomm Atheros, unsupported but BT works) Hand-off with BCM94352z Full Graphics enabled on HD 530, HDMI, VGA. ALC 255 Audio: (Internal Speakers, Internal Microphone, Headphone jack (microphone not tested) with layout-3 fix (you can use AppleHDAPatcher) Ethernet Realtek 8168B/8111B App Store, Messages, FaceTime, Siri, iCloud (native) Integrated webcam (native) 3.0 USB (native) Touchpad and Keyboard: Fn keys are good, the weird thing is the Brightness key. On my keyboard it's Pause Break:Br-up, Fn+F12:Br-dwn. (VoodoPS2Controller.kext) Battery info: Install ACPIBatteryManager.kext with kext utility or other installer. Sleep Mode: In High Sierra sleep mode not worked for me natively. Inject custom EDID to fix the blank screen after wake from sleep
      See here for instruction (thanks black.dragon74 and Jake Lo !!) Please add these 2 patches to ACPI\DSDT\Patches in your config.plist in order to avoid not responding applications after sleep: (added in "v5_591g_55tu_updated_CLOVER.zip") HECI to IMEI 48454349 494d4549 EC0 to EC 4543305f 45435f5f Before updating to a new version of High Sierra please update kexts to new versions to avoid kernel panics Note: No need for "IntelGraphicsDVMTFixup.kext" so you should delete it. Not working:
      Original Wi-Fi: Qualcomm Atheros QCNFA344A unsupported, you need switch to BCM94352Z or just use a mini usb wifi dongle. NVIDIA GTX 950M: Optimus not supported. Card Reader: Unsupported For WiFi:
      You can choose an external USB wifi dongle (I used tp-link Archer T1U (5GHz support), Tp-link have official macOS drivers, you just need to install it (OR)Replace your M.2 Qualcomm Card with a compatible BCM94352Z card (you will have hand-off Bluetooth too), just install the kext I wrote above I'll attach my EFI folder for anyone who want to install High Sierra (acer_aspire_v5_591g_55tu_hs.zip).
      *REUPLOADED updated CLOVER folder, attached as "v5_591g_55tu_updated_CLOVER.zip" (uploaded to OSXLatitude forum, can't upload here).
       
      I'm using High Sierra in Dual-boot with Windows 8.1. To do this in a clean install or with Windows installed first try my little minimal guide:
       
      Dual-boot clean install (on one drive):
      1. Boot into your Mac installer, Create 2 partitions in GUID table (1 for Win (I used FAT32 but I think it's no matter what), 1 for Mac), 
      2. Install Mac, boot with your USB, *mount your EFI partition (use terminal or an EFI mounter app), create an EFI folder, copy the CLOVER folder I attached to the EFI folder, restart,
      3. Boot into your Win installer, Format the partition you created for Win, install. 
      4. Now, it's automatically booting into Windows. To use Clover open cmd in administrator, type:
      bcdedit /set {bootmgr} path \EFI\CLOVER\CLOVERX64.efi 5. You're done! It will booting into Clover when you start the system, and you can select Win or Mac (or another OS if installed on a 3rd partition).
       
      Dual-boot with Windows installed first (on one drive):
      If you already have Windows and you don't want to lose all your data there is a hope:
      You need bootable Mac Installer and a full system restore image (you can search for it).
      (You may see errors if your EFI partition is not 200 MB)
      1. Boot into your Windows, resize your partition or create one for Mac.
      2. Boot into your Mac installer and in Disk Utility format the partition you created.
      3. Restore from image: select your full system restore image.
      4. When it's finished restoring you just need to restart, then boot to the system with your usb.
      5. Do Step 2. from "*" from clean install dual-boot above. but KEEP "Microsoft" FOLDER IN IT!
      6. Do Step 4. from clean install dual-boot above.
      7. You're done! You can select your old Windows and your new macOS!
      (I only tried with Windows 8/8.1/10. I don't know Windows 7,etc.)
       
      IF YOU GETTING ERRORS DURING MAC RESTORE:
      Make sure you have partitions in GPT The best version for restore method is Windows 8.1. It's using 200 MB EFI. Windows 10 using 100 MB EFI and will annoy the Mac restore. You can use with Windows 10, just ignore the errors IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):
      Make sure you have GPT partitions, and GPT installer IF YOU USED RESTORE METHOD THEN CAN'T MOUNT YOUR EFI PARTITION (No EFI partition found)
      It's because your EFI is not 200 MB or not an "Apple" original EFI,  but do not worry, try another EFI mounter, or mount from terminal (I used EFI mounter v3: Getting errors, but you can mount and use without problem) You also could "mount" the EFI from windows, for that open cmd and type: diskpart list vol (Now select the "System" volume,(FAT 32) For example I select 4) sel vol 4 list part (Select System type partition, for example 2) sel part 2 assign letter=b (This will "mount" your EFI partition, to manage files download totalcmd or explorer++ (run as admin)) remove letter=b (This will "unmount" your EFI) Here is a video from dual-boot with Windows installed first (on one drive):
      https://www.youtube.com/watch?v=0_Q8uPkwcWQ
      Here some pictures:




    • By Mieze
      This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
       

       
      A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
       
      5 Series
      82578LM 82578LC 82578DM 82578DC 6 and 7 Series
      82579LM 82579V 8 and 9 Series
      I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
      I219LM I219V 200 Series (since V2.3.0d0)
      I219LM I219V 300 Series (since V2.4.0d0)
      I219LM I219V  
      Key Features of the Driver
      Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.  
      Current Status
      The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS.   Known Issues
      There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.  
      FAQ
      Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Installation
      Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      Troubleshooting
      Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000.  In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
      Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
      The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
      Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
      Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
    • By End3rPower50
      Hi, i've installed on my pc MacOS Mojave but after installation my pc, sometimes, crash giving kernel panic.
      I came to the conclusion that it is a random kernel panic because sometimes it starting up and other times it isn't starting up
       
      My PC:
      CPU: Intel i7 6500U
      LAN: RTL8100
      Wi-Fi & Bluetooth: Dell DW1820A
      USB 3.1
       
      CLOVER.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
×