Jump to content

197 posts in this topic

Recommended Posts

1 minute ago, Cyberdevs said:

Based on your hardware specs you should be able to use the methods provided in the first post. How is your config.plist configured?

Are you using any kexts for activating your GPUs or you just use clover's injections or DSDT/SSDTs for your hardware?

The only kexts I use that effect the GPU are Lilu and Whatevergreen as they allow me to use my DP on the RX580. I can upload my EFI if you want to have a look.

Share this post


Link to post
Share on other sites
Advertisement
Just now, RedHibby said:

The only kexts I use that effect the GPU are Lilu and Whatevergreen as they allow me to use my DP on the RX580. I can upload my EFI if you want to have a look.

Yeah upload your EFI folder I will take a look, please remove the following folders from the EFI folder and the following data from your config.plist before uploading it:

Folders:

Apple

Themes

 

Data from config.plist

1. Serial Number

2. MLB

3. UUID or SmUUID if you have them.

Share this post


Link to post
Share on other sites
Posted (edited)
20 hours ago, Cyberdevs said:

Yeah upload your EFI folder I will take a look, please remove the following folders from the EFI folder and the following data from your config.plist before uploading it:

Folders:

Apple

Themes

 

Data from config.plist

1. Serial Number

2. MLB

3. UUID or SmUUID if you have them.

My EFI.

 

Edited by RedHibby

Share this post


Link to post
Share on other sites
Posted (edited)
20 hours ago, RedHibby said:

My EFI.

 

Thanks for the help but I am pleased to say I have got it working. I had another look at my BIOS and found the IGPU in the advanced system agent. I enabled it and my preview is working perfectly.

Screenshot 2018-08-12 at 23.55.07.jpg

Edited by RedHibby

Share this post


Link to post
Share on other sites
5 hours ago, RedHibby said:

Thanks for the help but I am pleased to say I have got it working. I had another look at my BIOS and found the IGPU in the advanced system agent. I enabled it and my preview is working perfectly.

That's good news ;)

Share this post


Link to post
Share on other sites

As a followup to my earlier posting, I have been able to get this working on my Coffee Lake system I wrote about earlier. (Gigabyte Z370XP SLI, i5-8400, RX-580) The recent Public Beta (18A365a) added some more systems into the graphics support, Pavo wrote this somewhere in the main Mohave pre-release thread.

 

I used Clover Configurator to generate the smbios section for an iMac Pro, removed stuff like the firmware features, etc. -- letting Clover generate that information, and replaced this small smbios section in my main config.plist, took the machine offline and restarted. Preview and QuickLook worked as they should. I did not have to turn on the IGPU in the BIOS settings, nor use inject-intel = true or make any other changes.

 

So Pavo's idea about the smbios settings waaaaaay back when does look like it is on the mark. Hopefully Apple will keep adding more systems so that Preview and QuickLook work right, after all iTunes, Safari, pretty much all of the other apps use jpegs and display them correctly already.

 

Thank you all for your help.

Share this post


Link to post
Share on other sites
55 minutes ago, jerryy2 said:

As a followup to my earlier posting, I have been able to get this working on my Coffee Lake system I wrote about earlier. (Gigabyte Z370XP SLI, i5-8400, RX-580) The recent Public Beta (18A365a) added some more systems into the graphics support, Pavo wrote this somewhere in the main Mohave pre-release thread.

 

I used Clover Configurator to generate the smbios section for an iMac Pro, removed stuff like the firmware features, etc. -- letting Clover generate that information, and replaced this small smbios section in my main config.plist, took the machine offline and restarted. Preview and QuickLook worked as they should. I did not have to turn on the IGPU in the BIOS settings, nor use inject-intel = true or make any other changes.

 

So Pavo's idea about the smbios settings waaaaaay back when does look like it is on the mark. Hopefully Apple will keep adding more systems so that Preview and QuickLook work right, after all iTunes, Safari, pretty much all of the other apps use jpegs and display them correctly already.

 

Thank you all for your help.

Yeah DP7 seems to be more forth coming on the Graphics and overall performance. I recently updated my SandyBridge rig with no IGPU and only the AMD R9 270X and there are almost no issues in regard to preview, quick look and Screen Capture (Video)

I'm confident that with the final release all the issues will be resolved.

Share this post


Link to post
Share on other sites

I turned of my IGPU and Preview fails to open JPG's. Perhaps the next update will sort out Preview for RX580's. Back to switching my IGPU back on. :)

Share this post


Link to post
Share on other sites
Posted (edited)
25 minutes ago, RedHibby said:

I turned of my IGPU and Preview fails to open JPG's. Perhaps the next update will sort out Preview for RX580's. Back to switching my IGPU back on. :)

I believe for iMac17,1 SMBIOS you need to leave the iGPU on because in a real iMac17,1 the intel hd 530 frambuffer is loading when macOS starts, even though there's no RX580 chipset for the dGPU in the iMac17,1 but it is how it's defined.

Edited by Cyberdevs

Share this post


Link to post
Share on other sites

up dated to:10.14 Beta (18A365a). only after Adding a Sapphire 280X . In the second PCI slot (as i couldnt be bothered to change the water cooled loop around.And. As no support for EVGA GTX 1070

All seems to work ok except previewing jpg screen shots

 

Share this post


Link to post
Share on other sites

My mobo has Intel HD Graphics 2500 chip. I have put my activated IGFX in BIOS and tried to configure it by adding IntelGraphicsFixup.kext in /EFI/Clover/kexts/other and removing DSDT. But mojave just completed boot (using -v) and the display just remained black with the text without showing the GUI. In Sierra it caused kernel panic and reboot.

 
  •  

Share this post


Link to post
Share on other sites
1 hour ago, Nila said:

My mobo has Intel HD Graphics 2500 chip. I have put my activated IGFX in BIOS and tried to configure it by adding IntelGraphicsFixup.kext in /EFI/Clover/kexts/other and removing DSDT. But mojave just completed boot (using -v) and the display just remained black with the text without showing the GUI. In Sierra it caused kernel panic and reboot.

What is the model of you main GPU?

as far as I know the intel HD 2500 is not supported in macOS you can use it to stop the dGPU from being initialized during boot which is not the case in macOS and resolving the black screen issue.

Share this post


Link to post
Share on other sites

Actually HD2500 is my inbuild GPU. If it is unsupported in Mac, I won't be able to enable it and have to use my GT 730 card instead.

Share this post


Link to post
Share on other sites

Yes you need to use your GT730 instead, even if you get the HD2500 to be recognized by macOS you won't have acceleration for the HD2500 GPU anyway so I doubt it would be helpful.

Which version of Mojave are you trying to install? because I guess the transparency issue is now fixed on DP8 and newer releases.

I have fully functional 7790 and R9 270X macOS Mojave since DP8 but I'm not sure about nVidia GPUs but I think your GT730 is supported natively. isn't it?

Share this post


Link to post
Share on other sites

Is there any other solution instead of changing SMBIOS? I don't have iGPU in my processor Xeon 1231v3 (Haswell). My PC is Asus Maximus VII Hero, Xeon 1231v3, Sapphire RX 480 8GB Nitro+

Share this post


Link to post
Share on other sites
1 minute ago, MrVanosh said:

Is there any other solution instead of changing SMBIOS? I don't have iGPU in my processor Xeon 1231v3 (Haswell). My PC is Asus Maximus VII Hero, Xeon 1231v3, Sapphire RX 480 8GB Nitro+

 

Did you not get to the alternative medicine part of the tutorial? :)

Share this post


Link to post
Share on other sites
On 9/7/2018 at 6:06 PM, Cyberdevs said:

Yes you need to use your GT730 instead, even if you get the HD2500 to be recognized by macOS you won't have acceleration for the HD2500 GPU anyway so I doubt it would be helpful.

Which version of Mojave are you trying to install? because I guess the transparency issue is now fixed on DP8 and newer releases.

I have fully functional 7790 and R9 270X macOS Mojave since DP8 but I'm not sure about nVidia GPUs but I think your GT730 is supported natively. isn't it?

NVIDIA GT 730 Is natively supported. Only problem was Preview and Quick Look. As suggested in this forum, enabling HD 2500 was required to solve this problem. But I couldnot make it to work on Mojave and read somewhere that it is not supported since Mavericks. So I changed my SMBIOS to MacPro 6.1 and Preview and Quck Look works perfectly.

Share this post


Link to post
Share on other sites

Its worth mentioning that the 'alternative medicine' will most likely disable the encode/decode capabilities of the external GPU. You can bypass it with the -shikigva=4 bootflag on Skylake/KabyLake rigs...

Share this post


Link to post
Share on other sites
4 hours ago, Coke said:

Its worth mentioning that the 'alternative medicine' will most likely disable the encode/decode capabilities of the external GPU. You can bypass it with the -shikigva=4 bootflag on Skylake/KabyLake rigs...

 

That is indeed good info. Thank you. I haven't tried this method on any Skylake builds yet. At least none with a supported dedicated GPU. So yeah, I could not confirm it working in this particular case. Good to know. Thanks. :)

Share this post


Link to post
Share on other sites

I switched to SMBIOS 6,1 switched off my IGPU and removed Lilu and Whatevergreen. Everything is now working perfectly no issues with preview.

Edited by RedHibby

Share this post


Link to post
Share on other sites
7 hours ago, RedHibby said:

I switched to SMBIOS 6,1 switched off my IGPU and removed Lilu and Whatevergreen. Everything is now working perfectly no issues with preview.

 

That's how you do it. Good job. Glad you managed to fix it. :)

Share this post


Link to post
Share on other sites

Hello...

 

I have the same issue with Mojave Public Beta on Desktop, Quick Look and Preview app glitch for JPG files. But In my case i have no Graphics card, only integrated graphics (intel HD 4400). My Display is connect to Display Port (DP). I have VGA and DP option for Display connection no HDMI. 

 

My config is attached. 

 

Please Help 

 

Bhaggu

EFI.zip

Share this post


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

Hello...

 

I have the same issue with Mojave Public Beta on Desktop, Quick Look and Preview app glitch for JPG files. But In my case i have no Graphics card, only integrated graphics (intel HD 4400). My Display is connect to Display Port (DP). I have VGA and DP option for Display connection no HDMI. 

 

My config is attached. 

  

Please Help 

 

Bhaggu

 

Strange. This issue should not occur with the iGPU (and it didn't in my case). I know this is your first post, and I welcome you to this forum, but I'm gonna ask you to add your hardware information to your signature to see what we're dealing with. I can see you're using a Haswell system. But still, it would be nice to know a little more than that. :)

 

If your WhateverGreen kext is up to date (as it should be), you shouldn't need IntelGraphicsFixup kext anymore since it's already included into WEG. Could you try to remove it (or move it to Desktop, so you can put it back in case of anything) and try again?

 

About the config, I would strongly recommend you to always remove serial numbers from SMBIOS and RT Variables before uploading your config (or the entire EFI) for analysis.

 

Also, could you try iMac14,2 for once and see if it makes any difference? You can simply make a copy of your current config.plist, edit it, and rename the old one for iMac13,3 to configiMac13,3.plist or something, so you can access it from Clover GUI in case you need it (you can name it whatever you want, but it needs to contain the "config" part).

 

And could you please, check the option to Inject System ID in your config's System Parameters section?

879216540_ScreenShot2018-09-21at14_33_28.png.181605ccc7d899f35d6eb4ea185ec040.png

 

Otherwise, config looks ok.

Edited by arsradu

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 headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Beta Warning
      Please note that it is currently in a "beta" state so use it at your own risk. I am just documenting this here for those of you who want to get framebuffer patching now.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically (see caveat below)
      - Be aware that WhateverGreen does not rename all instances of GFX0 -> IGPU but should be okay in most cases
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can wait for the official binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - Desktop: 0x00030010 (default)
      - Laptop: 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - Support started with OS X 10.8.x
      - Desktop: 0x0166000A (default), 0x01620005
      - Laptop: 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - Support started with OS X 10.9.x
      - Desktop: 0x0D220003 (default)
      - Laptop: 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - Support started with OS X 10.10.2
      - Desktop: 0x16220007 (default)
      - Laptop: 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - Support started with OS X 10.11.4
      - Desktop: 0x19120000 (default)
      - Laptop: 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - Support started with macOS 10.12.6
      - Desktop: 0x59160000 (default)
      - Laptop: 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - Desktop: 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - Laptop: 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-cursormem (Haswell only) framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Framebuffer Dumps
      There are two ways to dump your framebuffer data (both require WhateverGreen + Lilu debug versions):
       
      1. Using -igfxdump boot flag to dump IGPU framebuffer kext to /AppleIntelFramebuffer_X_Y (root of your boot drive)
       
      There are several ways of reading this dump:
      - Using 010 Editor along with the IntelFramebuffer.bt template
      - Using Intel FB-Patcher File->Open menu
       
      2. Using -igfxfbdump boot flag to dump native and patched framebuffer table to ioreg at IOService:/IOResources/WhateverGreen
       
      There are several ways of reading this dump:
      - Using dump_platformlist.sh shell script
      - Using Intel FB-Patcher File->Import->IOReg Dump menu
       
      Debug Output
      To get debug output from Lilu use the -liludbgall flag and for WhateverGreen use the -wegdbg boot flag. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt
      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for all data patching method, ioreg framebuffer dump and other contributions
       


    • By Luan Eduardo
      Installing macOS Mojave 10.14 on Gigabyte Z370N WIFI + i7 8700K + UHD 630



      Changelog:
       
      10/17/2018 08:12h GMT-0
      - Fix Kexts permissions commands adjusted.
      - Removed FrameBuffer patch that is not needed.
      - Added audio solution and HDMI.
      - Unfortunately DisplayPort does not work.
      - Replaced Wifi/BT with DW1560 (BCM94352Z)
       
      10/11/2018 04:15h GMT-0
      - Added USB 3.0 patch.
      - Adjusted some steps.
      - Changed text formatting.
       
      10/11/2018 03:42h GMT-0
      - Added missing UEFI configuration.
       
      10/07/2018 00:36h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor ->  Work. All SpeedStep stages.
      - Video Card ->  Work. QE/CI and Metal.
      - Chipset ->  Work.
      - HDMI (1st) ->  Work.
      - HDMI (2nd) ->  Work.
      - DP ->  Not work.
      - Audio ->  Work.
      - HDMI Audio ->  Work.
      - WiFi/Bluetooth ->  Work. Replaced.
      - Ethernet (1st) ->  Work.
      - Ethernet (2nd) ->  Not work.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
       
       
      Todo
       
      - Make audio work.
      - Make HDMI audio work.
      - Test DisplayPort.
      - Make second ethernet work.
      - Replace Wifi/Bluetooth.
       
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover EFI
      - Clover Configurator
      - Some KEXTs


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ .app/Contents/Resources/createinstallmedia --volume /Volumes/Install--nointeraction This will take about 30 minutes.
       


      Install bootloader

      Download the CloverEFI (used 4674) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix64


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop. Edit the /Volumes/EFI/CLOVER/config.plist inside this new partition, open with Clover Configurator (used 5.2.1.0)
       
      Full UHD630 Acceleration
       
      config.plist (Clover Configurator): 
       
      - Uncheck: Acpi - Fixes - FixDisplay
      - Uncheck: Acpi - Fixes - AddHDMI
       
      - Change value: Gui - Screen Resolution to 3840x2160 (Your screen resolution, mine is 4k)
      - Change value: Rt Variables - CsrActiveConfig to 0x3
      - Select value: SMBIOS - Up/Down arrows - iMac18,1 - Intel Core i5-7360U @ 2.30Ghz (I know, it's not our processor, but is that option)
       
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the Lilu.kext from here. I used the version 1.2.7.
      - Download the WhateverGreen.kext. I used the version 1.2.3.RELEASE.
       
       
      All USBs (2.0, 3.0, Type-C, internal)
       
      config.plist (Clover Configurator): 
       
      - Add value: Kernel and Kext Patches - KextsToPatch:
                       Name*: com.apple.driver.usb.AppleUSBXHCI
                       Find* [HEX]: 83FB0F0F 83030500 00
                       Replace* [HEX]: 83FB0F90 90909090 90
                       Comment: disable port limit in XHCI kext (credit PMHeart)
                       MathOS: 10.14.x

       
       
      Sleep/Wake
       
      config.plist (Clover Configurator): 
       
      - Check: Boot - Arguments - dart=0
       
       
      Audio onboard and HDMI
       
      config.plist (Clover Configurator): 
       
      - Change: Device - Audio Injection - layout-id to 7
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the Lilu.kext from here. I used the version 1.2.7. (already installed above)
      - Download the AppleALC.kext from here. I used the version 1.3.2.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the FakePCIID.kext and FakePCIID_Broadcom_WiFi.kext from here. I used the version 2018-1014.
      - Download the BrcmFirmwareRepo.kext, BrcmPatchRAM.kext and BrcmNonPatchRAM.kext from here. I used the version 2018-0505.
       
       
      Mandatory Kexts
       
      Download those Kexts and put in /EFI/CLOVER/kexts/10.14/
       
      - Download the FakeSMC.kext from here. I used the version 2018-0915.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-0424.
       
       
      Put the Clover installer on the flash drive too.
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      - Shutdown and insert the flash.
      - Power on with DEL pressed to enter BIOS setup.
      - Change value: Periphelrals - Initial Display to IGP
      - Change value: Periphelrals - USB Configuration - XHCI Hand-off to ENABLE
      - Change value: Chipset - VT-d to DISABLE
      - Change value: Chipset - Internal Graphics to ENABLE
      - Change value: Chipset - DVMT Pre-Allocated to 128M
      - Change value: Chipset - Wake On Lan to DISABLE
      - Save & Exit Setup
       
      - Now, hold the F12
      - In the list, select your flash drive.
      - It will show twice. One with UEFI prefix and another without.
      - Select with UEFI prefix. Ie.: "UEFI: Sandisk Cruzer"
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "HD".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the config.plist inside your destination disk EFI parittion with config.plist inside flash card EFI partition.

      The flash drive EFI partition is unmounted. Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 1.
       
      Last step
       
      Copy all Kexts from flash drive to /Library/Extensions, with those commands in Terminal:
      sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -system-prelinked-kernel sudo kextcache -system-caches Restart the system.
       
       
      It's done!

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
       
    • By am_yvr
      Asus Prime B360M-A or Asus Prime H310M-E :

      Which of these two motherboards would give less hassle in a Hackintosh build - requiring fewer after install fixes/updates to get everything working in Mojave or High Sierra?
       
      These are the only two Asus models that I can afford, fit the form factor in my build, and already have had a BIOS upgrade by Asus to 9th-generation - if I want to replace the CPU with an i9 in the future (for now I'll be using i7-8700 or even i3-8350k but I want to future proof a bit)
       
      Thanks guys!
    • By thomazella
      Hi guys. Just wanted to say this is my new favorite forum for mac hacks

      I'm trying to get mojave to work, and using the guide's (moderator made, on the front page) clover folder I ALMOST got it! T.T

      There's something still wrong tho. lol.

      - Install to a HDD formated as case-sensitive APFS goes black at 2 minutes remaining. Is it supposed to fill the progress bar 100%? If so then I have a problem.
      - Assuming the install went well, I tried to boot to "MacOS Prebooter" from clover screen and got that error.

      I have a Z170m ASUS, awesome board. I'm sure it can be done. With Intel 6700k.
      Latest clover. Guide's clover config!!

      What do you guys think?
      - mobo config problem
      - other hardware thing (I have many harddrives connected?)
      - clover config
      - need some driver/kext
      - something else

      THANK YOU!

      PS: I've tried upgrading with the App store download on a Sierra system to arrive in the same screen, with the same error.
      I'll also spend some time today searching the forums. Just busy atm, and thanks for any help or tips!!

×