Jump to content
Welcome to InsanelyMac.com - No more ads! And some exciting news... Read more... ×
kushwavez

[GUIDE] ASUS Z170-DELUXE - i7-6700K - HD 530 & RX 5700 - [From macOS El Capitan 10.11.6 to Big Sur 11 - Windows 10]

35 posts in this topic

Recommended Posts

A really good motherboard with macOS compatible bult-in Wifi & Bluetooth

P_setting_fff_1_90_end_500.png

ASUS Z170-Deluxe (with Wifi)

BIOS: v3801

CPU: i7-6700K 4.0 to 4.2 GHz (w/o OC)

RAM: 1x 16 GB Corsair DDR4 2400 MHz

GPU: Intel HD 530 (Headless) & ASUS Radeon RX 5700 OC 8 GB

Audio: ALC 1150

Ethernet: I219V2, I211-AT

WiFi & Bluetooth: Broadcom BCM94360HMB Half-Mini-PCI-E

More Specs: https://www.asus.com/Motherboards/Z170-DELUXE/specifications/

 

El Capitan 10.11.6 -> Big Sur 11 - Windows 10

 

What is working:

  • BCM94360HMB Wifi and Bluetooth
  • AirDrop, Handoff, FaceTime, Messages, App Store, iCloud, etc.
  • Intel HD 530 (QE/CI tested, but now I'm using it in headless)
  • Sleep
  • RX 5700 (QE/CI with 2 1080p monitors connected)
  • Sound (all ports)
  • USB Ports
  • Two Ethernet ports
  • macOS with a light OC (4.12 GHz - 4.5 Ghz, XMP, ASUS optimal)
  • ASUS HyperKit and M.2 with a KINGSTON NVMe SSD - 250 GB
  • Hardware decoding/encoding on both HD 530 and RX 5700 (HD 530 up to HEVC, RX 5700 at the time of writing VP9)
    • iGPU only (with QuickSync) is used in the default config.plist
    • To use dGPU for hw decode/encode and also use Intel QuickSync you need to start with "config_headless.plist" This will use iMac17,2 SMBIOS and shikigva=80
    • To use dGPU only boot with "config_amd.plist" also disable iGPU completely in BIOS. This will use iMacPro1,1 SMBIOS without iGPU
  • System Integrity Protection is Enabled by default. If you need to boot with SIP disabled you may use "config_debug.plist" or disable it manually in Clover settings. If you want Enabled SIP but with allowing unsigned kexts you may boot with "CsrActiveConfig = 0x01"

 

What is not working:

  • -

 

 

Not tested:

  • Thunderbolt (no equipment)

 

Issues:

  • None

 

BIOS Settings:

  • Boot\CSM (Compatibility Support Module):
    • Launch CSM: Disabled
  • Boot\Secure Boot:
    • OS type: Other OS
    • Secure Boot State: Disabled
  • Advanced\System agent (sa) Configuration:
    • VT-d: Enabled
    • Graphics Configuration: (This is for HD 530 in headless)
      • Primary Display: Auto (to use dGPU only this must be PEG)
      • iGPU Multi-monitor: Enabled (to use dGPU only this must be Disabled)
      • RC6(Render Standby): Enabled (to use dGPU only this must be Disabled)
      • DVMT Pre-Allocated: 128M
  • Advanced\PCH Storage Configuration:
    • SATA Mode Selection: AHCI
    • HyperKit: Enable (if you have NVMe SSD with ASUS HyperKit)
  • Advanced\CPU Configuration:
    • Intel Virtualization Technology: Enabled
    • CPU- Power Management Control:
      • CPU- C-States: Enabled
      • Intel SpeedShift: Enabled

 

Getting ready for installation:

 

Installation:

  • Create an installer with any method you know (- Mac: createinstallmedia, gibMacOS - Windows: Transmac, Vmware, Win32diskimager, gibMacOS)
  • Copy my Clover folder to the USB's EFI folder
  • Boot with the Installer USB
    • If you have any problem (kp or freeze) boot with config_debug.plist to see what causes the issue

 

Post Installation:

  • Download Clover Configurator and generate a new Serial Number for yourself

 

Some pictures:

884262691_Screenshot2020-11-13at10_37_50.png.2416a6ff1b22dcaff541ef3f1f8a0bd4.png

 

 

110295672_Screenshot2020-01-11at14_41_45.png.85a031007620b31a9d0f60f038382260.png

Screenshot-2020-01-11-at-14-42-06.png

K-perny-fot-2020-01-11-14-07-59.png

 

El Capitan 10.11.6

Spoiler

Screen-Shot-2020-11-02-at-22-14-15.png

 

Sierra 10.12.6

Spoiler

Screen-Shot-2020-11-02-at-21-36-08.png

 

High Sierra 10.13.6

Spoiler

Screen-Shot-2020-11-02-at-16-50-18.png

 

Mojave 10.14.6

Spoiler

Screenshot-2020-11-02-at-7-07-36.png

 

Catalina 10.15.7

Spoiler

Screenshot-2020-11-02-at-18-14-07.png

 

Catalina & Windows 10 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 doesn't matter what you choose), 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 (if there is no 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).

 

IF YOU GETTING ERRORS DURING WINDOWS INSTALLATION (could not be formatted, etc):

  • Make sure you have GPT partitions, and GPT (UEFI) installer, also disconnect all external storage drives (except the installer USB)

 

Mounting EFI from Windows:

  • Open cmd in administrator mode and type:
    • mountvol b: /s (This will mount your EFI)
      • Open Total Commander or Explorer++ in administrator mode to manage EFI
    • mountvol b: /d (This will unmount your EFI)

 

Useful Applications for Mac:

 

Useful Applications for Windows:

 

Notes:

  • According to @albertoacj's comment Sidecar is only working in headless iGPU mode when using an AMD GPU, keep that in mind
  • No need to change anything inside Clover from El Capitan to Big Sur
  • For macOS Mojave and older you might need the full AirPortBrcmFixup.kext for full WiFi support 

 

Changelog:

2020.11.12: Noticed that the CPU is always at 4200 Mhz, created an SSDT for proper CPU stepping. Updated to Big Sur release version, updated bootpack

2020.11.03: Tested El Capitan, Sierra, High Sierra, Mojave, Catalina, Big Sur

2020.11.01: Updated bootpack to Clover v5126, ready for macOS 11 Big Sur final release

2020.04.23: Corrected layout-id to use all audio ports, updated bootpack

2020.04.22: Deleted unnecessary boot-args, can boot without any custom boot-args (except agdpmod=pikera for RX 5700), updated bootpack

2020.04.20: Deleted unnecessary lines from config.plist, updated bootpack

2020.04.17: Replaced FakeSMC with VirtualSMC because FakeSMC is outdated (to see your frequencies use Intel Power Gadget) -> Removed unnecessary kexts, Updated all necessary kexts, updated Clover to v5112, updated bootpack, enabled SIP, deleted bootcamp theme

2020.03.26: Updated to 10.15.4 -> Updated WhateverGreen, Lilu -> Updated Clover to v5107

2020.03.23: Removed "EmuVariableUefi.efi" -> deleted, caused false nvram map, now it's native, updated Clover to v5106

2020.02.11: Updated to 10.15.3 -> No problem when/after installing

2020.01.19: Added ASUS HyperKit NVMe SSD to the "What is working" list

2020.01.12: Tested system with OC, added more informations to BIOS settings

2020.01.11: Added SmallTreeIntel82576.kext for 2nd Ethernet, Tested Ethernet ports

2020.01.11: First upload

 

Edited by kushwavez
headless is needed for Sidecar with AMD GPU

Share this post


Link to post
Share on other sites
On 1/11/2020 at 5:29 PM, kushwavez said:
  • RX 5700 (QE/CI with 2 1080p monitors connected)

Which ports are used? 2 x DP or DP + HDMI?

HDMI sound works on both?

 

Share this post


Link to post
Share on other sites
3 minutes ago, verdazil said:

Which ports are used? 2 x DP or DP + HDMI?

HDMI sound works on both?

 

Now I'm using 1 HDMI and 1 DP.

Also yes, sound is working on both.

Share this post


Link to post
Share on other sites

hey @kushwavez, just found your post trying to get my Bluetooth updated after updating to Catalina... my build it extremely similar, dual boot and everything... LINK to my Build

 

I was comparing the Kext list we were both using, what are all of the FaksSMC_###Sensors.kext files used for? I have not seen those before?

 

I might also comb through and compare our config.plist to see the differences

Share this post


Link to post
Share on other sites
3 minutes ago, ABaller said:

hey @kushwavez, just found your post trying to get my Bluetooth updated after updating to Catalina... my build it extremely similar, dual boot and everything... LINK to my Build

 

I was comparing the Kext list we were both using, what are all of the FaksSMC_###Sensors.kext files used for? I have not seen those before?

 

I might also comb through and compare our config.plist to see the differences

You should try using BrcmBluetoothInjector.kext on Catalina. Without that my Bluetooth is not working. I tested out handoff, bt speakers, bluetooth internet sharing from iPhone, the only thing I can't test is Side Car as I have no iPad. FakeSMC sensor kexts is for iStat Menus to show my CPU, GPU, core temperatures and other values. Also I installed all of my kexts only to Clover/kexts/Other. Some people saying that you should not, but there is no problem with that. I have no custom kexts installed to L/E. 

Share this post


Link to post
Share on other sites

funny you should say that... I was reading about Catalina and the problems people were having with Kexts in L/E... so I just moved all of mine from L/E to EFI/CLOVER/Kexts/Other and then rebuilt the cache... Here is the comparison of the Kexts we're using

  1. AirportBrcmFixup.kext (2.0.5) | I'm using 2.0.6
  2. AppleALC.kext (1.4.5) | I'm using 1.4.7
  3. BrcmBluetoothInjector.kext (2.2.10) | I'm Not Using
  4. BrcmFirmwareData.kext (2.2.10) | I'm Not using, but I am using BrcmFirmwareRepo.kext (2.2.10)
  5. BrcmPatchRAM2.kext (2.2.10) | I'm using the Same
  6. CodecCommander.kext (2.6.3) | I'm Not Using
  7. FakeSMC_ACPISensors.kext | I'm Not Using
  8. FakeSMC_CPUSensors.kext | I'm Not Using
  9. FakeSMC_GPUSensors.kext | I'm Not Using
  10. FakeSMC_LPCSensors.kext | I'm Not Using
  11. FakeSMC_SMMSensors.kext | I'm Not Using
  12. FakeSMC.kext (6.26-357) | I'm using 6.26-322
  13. IntelMausiEthernet.kext (2.5.0d14) | I'm using the Same
  14. Lilu.kext (1.4.2) | I'm using the Same
  15. realtekALC.kext (2.0) | I'm Not Using
  16. SmallTreeIntel82576.kext (1.0) | I'm Not Using
  17. WhateverGreen.kext (1.3.7) | I'm using the Same

So I replaced my BrcmFirmwareRepo.kext with your BrcmFirmwareData.kext.... used your BrcmBluetoothInjector.kext.. and still no bluetooth?

 

What is CodecCommander?

 

Share this post


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

So I replaced my BrcmFirmwareRepo.kext with your BrcmFirmwareData.kext.... used your BrcmBluetoothInjector.kext.. and still no bluetooth?

try clearing nvram with a hard reset, and don't forget to rebuild kextcaches after moving your kexts from L/E

edit: ah I see you rebuilt kextcaches

12 hours ago, ABaller said:

What is CodecCommander?

CodecCommander is required to fix problems like sound crackling or freezing. probably not needed so I'll delete that in the next update.

Edited by kushwavez

Share this post


Link to post
Share on other sites

Just got my Bluetooth all working again... Thank you for the help!!

 

I ended up deleting BrcmPatchRAM2 and BrcmFirmwareRepo and replacing those two with BrcmPatchRAM3, BrcmBluetoothInjector, and BrcmFirmwareData from https://github.com/acidanthera/BrcmPatchRAM/releases

 

I also compared our two config.plist files... you have a ton more options checked than I do, it's worth looking at if you get a chance... When I built my hack I was very careful not to include anything that wasn't necesary.

config (export).plist

Share this post


Link to post
Share on other sites

I am using i5-6500 and B250 MB. The gpu history only shows Intel SKL Unknown and a low boot time.

How to fix it....guys ? I am directly using the config.plist above.

Share this post


Link to post
Share on other sites

@adsasf use the zip from the main #1 post. Also you have a different motherboard but anyways the iGPU must be the same. Try it. I suppose the slow boot is because you are using HDD or a low-speed ssd. Use the config_debug.plist for debug informations from hangs in verbose mode.

 

Unfortunately my motherboard is broken now and my iGPU outputs are not working anymore so I can't really update the bootpack, but I'm pretty sure it's working as I tested/configured it and used my iGPUs and the RX 5700 for a long time before it's became broken.

Share this post


Link to post
Share on other sites

Nice work, kushwavez

However, I read that Speed Shift overrides SpeedStep. If Speed Shift is enabled, having SpeedStep enabled or disabled makes no difference.

Share this post


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

I'm just waiting for the Big Sur release to test and do a clean install. 

This will be install with Clover or OpenCore?

Share this post


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

This will be install with Clover or OpenCore?

Clover. Since v5122 it has been integrated with OpenCore, so it can boot Big Sur just fine. I have a working OC EFI but I don't see any advantage by using it. They're almost equivalent in functions and performance, both good. My personal opinions that Clover is better because of it's GUI. You can edit so much things just from the GUI, easier to "automate" the whole select process, and best for multi-boot systems. 

Share this post


Link to post
Share on other sites

Thanks, I also prefer Clover. I hope that the integration with OpenCore will not lead to BIOS malfunction. Due to constant problems with BIOS, I do not want to use OpenCore. I don't have enough time now and I gladly use your work: Clover + 10.11.

Share this post


Link to post
Share on other sites

Thanks,kushwavez I'm waiting for the 11 final release now. 

P. S. I have successfully installed and boot the system using both Clover and OpenCore. Thanks for the help.

Edited by verdazil

Share this post


Link to post
Share on other sites

Hi I need help to understand this way to creat an installer after I downloaded  Big Sur i used  creatinstallmedia after I copy your files to EFI but something is wrong... I think I have to install clover first in this install pendrive am I wrong ?

Share this post


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

Hi I need help to understand this way to creat an installer after I downloaded  Big Sur i used  creatinstallmedia after I copy your files to EFI but something is wrong... I think I have to install clover first in this install pendrive am I wrong ?

It doesn't really matter what to do first - copy the EFI directory to the appropriate partition of the flash drive or transfer the installer to the flash drive.

Share this post


Link to post
Share on other sites
19 hours ago, kushwavez said:

@albertoacj

- Create the installer with createinstallmedia

- Mount your USB EFI

- Create an EFI folder, simply copy & paste the CLOVER and BOOT folder to it

- Boot from USB

I don't know what can be...  I have a 1080 ti, I bought a rx 580 to use with Hackintosh (not arrived yet) so I remove  the gtx 1080 ti and try only with Igpu HD530

the installer doesn't work, and qcode 4 shows in motherboard , z170 deluxe same yours. I plugged  gtx 1080 ti and the installer start to work and the first time I could see macOS Big Sur installer. And install complete but when I  try to boot give me a error and reboots. When I put the ssd in a usb case I start my MacBook holding alt and the system start o_O

Thanks all for help. 

Share this post


Link to post
Share on other sites

@albertoacj Code 04 is "PCH initialisation before microcode loading", that shouldn't be an error. If it's working after you put back the GTX, then please go into UEFI settings and verify that your iGPU is selected for the output.

Advanced\System agent (sa) Configuration:

  • Graphics Configuration: 
    • Primary Display: IGFX
    • iGPU Multi-monitor: Enabled 
    • RC6(Render Standby): Enabled
    • DVMT Pre-Allocated: 128M

Share this post


Link to post
Share on other sites
9 hours ago, kushwavez said:

@albertoacj Code 04 is "PCH initialisation before microcode loading", that shouldn't be an error. If it's working after you put back the GTX, then please go into UEFI settings and verify that your iGPU is selected for the output.

Advanced\System agent (sa) Configuration:

  • Graphics Configuration: 
    • Primary Display: IGFX
    • iGPU Multi-monitor: Enabled 
    • RC6(Render Standby): Enabled
    • DVMT Pre-Allocated: 128M

Thank so much kushwavez now is working, didn't boot with config.plist so I try config_debug.plist and it work perfect I edit config_debug put my serial, uid, removed verbose mode and now start fast and with no errors.

i set  -v in config.plist and show is sticking in disk1s2 accelerated crypto : 0 I don't know what  is this.

Everythink works fine except sleep the system sleep when come back code 30 in mono and no video is a common error I think, when my video card arrived I'll try to fix.

Thank you very much, one more time, for share...

Share this post


Link to post
Share on other sites

@albertoacj I'm glad it's working. You're welcome.

But I don't really understand why are you can boot with config_debug.plist and not with config.plist. They're actually same, only differences are that kernel and bootloader debug is enabled in config_debug.plist. 

 

And for sleep problem: try disabling Power Nap. If the computer still can't sleep then it's maybe because some of the USB ports. If that so, then I'll investigate this further and create a proper patch for the USBs (but as I can remember all of my ports are working, except the USB-C as I don't have any USB-C device to test atm)

 

EDIT: Oh my bad. Yes, waking up to a black screen is a common problem with HD 530. I didn't even realise because I never tried to put that PC to sleep with HD 530. Is working with RX 580 and RX 5700 tho as I tried that. I'll try to investigate that too.

Edited by kushwavez

Share this post


Link to post
Share on other sites

Hey there, I've pretty much the same build as yours (Z170 deluxe + 6700K).

The only difference is the graphics card: I have a GTX 1080. Since it is not supported I've decided to try to install Big Sur with your configuration using the HD530. The bios is set to igfx.

The hard drive is a Samsung NVME PM961 mounted on the hyperkit. 

 

  1. I've set up the BIOS as you recommended.
  2. I've created the USB pen with Big Sur and your configuration.
  3. I've formatted my partition with APFS through the Big Sur installer (which runs correctly)
  4. Right about halfway through the install procedure it stops and the system reboots (even though the progress bar has not finished). I tried to continue by booting from the USB dive and the new partition
  5. Right about halfway through the install procedure it stops and the system reboots. I tried to continue by booting from the USB drive and the new partition
  6. The system fails to run. An error on the logd service is shown repeatedly. 

I've tried to use the config_debug.plist to no avail.

What am I doing wrong? Why during thhe steps 4 and 5 the system reboots before finishing?

 

Cheers

D3566EC8-4999-4A18-AA95-4FE773990D03_1_105_c.jpeg

2395BFF6-2719-4F77-A318-3EE9CE9E8C97_1_105_c.jpeg

05086B1A-7243-4F5E-AE33-0F0ECCE8251C_1_105_c.jpeg

Edited by Alesss

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Enckyridion
      Hello. Is any Qualcomm Atheros AR8152 PCI-E Fast Ethernet Controller (NDIS 6.30) kext working on this new version of Big Sur? If so, could you help me? I've been looking for days and everyone I test doesn't work. Thank you.
    • By blazinsmokey
      I've written some detailed guide in my time but I'm going to keep this one shorter. I want to accomplish 2 things with this write up.
      1. Address the native nvram problem, this is huge for people with similar hardware moving forward with Big Sur.
      2. Help others get installed and booted with a very clean setup.

      Hardware and Overview
      ASUS Maximus VII Hero Z97, 4790K, Sapphire Nitro+ RX 580 8GB, HDMI to 43" 4K screen.
       
      Modifying the BIOS to get native nvram fix for Big Sur is also confirmed working for these boards
      ASUS Z97 ROG Maximus VII Hero ASUS Z97-A, requires manual modifying of BIOS file ASUS Z97-P ASUS Z97 ROG Maximus VII Gene ASUS Z97 ROG Maximus VII Ranger ASUS Z97 ROG Maximus VII Impact ASUS Z97 ROG Maximus VII Formula ASUS H97M-E ASUS Z97-PRO(Wi-Fi ac)  
      This included setup was used to upgrade directly to from Catalina to Big Sur but installation should be fine as well.

      Using OpenCore 0.6.3 and latest kexts. Using SMBIOS iMacPro1,1 even tho it may be frowned upon but it worked for DRM at least in Catalina, not willing to change it now. You can however do as you please.

      Everything pretty much works. FaceTime, Messages, AppStore etc. Waking the computer from sleep though requires pressing the PWR button.

      There is no options in OpenCore or Clover, drivers or magic to get native nvram working. You have to modify the BIOS or flash an old one that doesn't have the white list as discussed below. So if you can't go through with fixing the NVRAM, you will have to use the transplant method.

      NVRAM Problem
      Big Sur installer fails after about 20% progress in the Apple logo, fails shortly after disk#: device is write locked ending with apfs_vfsop_unmount. Verbose output below just before restart. I imagine a new install the same problem occurs because after the first state information on the drive and whatever is stored in the native nvram and the installer can't access something that is not there because it wasn't saved in the first place.


      Background
      Reddit post here starts to question it as Haswell in general but seemed more an issue with ASUS Z97 boards. A comment in that thread led me to Vit9696 saying fix your NVRAM. All other paths led to devs are aware and it's an macOS bug or giving up and transplanting the installation by using another machine. Well I ain't having none of that, Vit9696 said fix nvram, so I fixed it.

      Why
      Vit9696 actually solved this for us years ago here. The key take away is the whitelist part and replacing NvramSmi driver.
      Fix
      As stated above we can extract the NvramSmi driver from an older BIOS and the replace it in the latest one. I believe most our boards from this era are no longer being supported but the latest firmwares do have microcode to patch vulnerabilities like Spectre, meltdown, etc. It would be ideal to go this route and it's not that hard and working nvram is great!

      I'm guessing another way would be to flash back to old BIOS where native nvram is working and upgrade/install Big Sur and then flash the latest after. You could save your BIOS profile if available that way you won't have to set everything back up. If this is also the case for incremental updates, sounds like a nightmare.

      How (I chose to fix)

      Replacing the NvramSmi driver made the most sense and it was relatively easy. I am no expert and you know the responsibility I take in anyone trying this **** and failing, ZERO.

      To find a BIOS version before the whitelist was added to the NvramSmi driver I used the dates from the link in Vit9696's quotes. User 314TeR said his ASUS Maximus VII Impact nvram broke after 0412 which was released 2014/10/17 and worked with 0217 released 2017/07/28. To me anything after 2014/10/17 will have added the whitelist.

      So with my board I downloaded version 1104.

      Download UEFITool 0.26.0 as the latest versions won't let you rebuild/replace.

      Download latest BIOS and one without whitelist.

      Load older BIOS in UEFI tool, my case 1104. Search with text nvramsmi and extract as is, the file section. Like below. Save the ffs, name it whatever and close out we are done here.



      Load the latest BIOS now, 3503 in my case and search nvramsmi again. This time replace as is and select the ffs you just named and saved.


       
      You can't flash the modified BIOS as usual, they are contained in a way with write security. I just used my board's USB Flashback Utility. Named the modified BIOS to M7H.CAP, each board will have it's own naming method. Copied to a fat32 usb, stuck it in the correct USB port in the back and pressed the button for 3 seconds. 2 minutes later and I was booting my modified BIOS and restarted the upgrade process again from within macOS.
       
      That last bit is IMPORTANT, if you were trying to upgrade from Catalina and have the bootable option to install MacOS it still won't work after you fixed your nvram. You MUST restart the process again from within Catalina. 
      If you don't have USB Flashback Utility, take a look here for alternative ways.

      After BIOS modified flash test your nvram, mine worked right away. Then I tried the upgrade and that worked fine. I believe it was 4 phases total and 3 reboots. Took about 25 minutes on SSD.

      My modified BIOS 3503 is attached, don't be stupid with it and try to install on a different board. Rename it accordingly if you want to use it.

      Some BIOS Settings
      AHCI - Enabled
      VTD - Disabled
      Primary Display - Auto
      CPU Graphics Multi Monitor - Disabled
      Legacy USB - Enabled
      xHCI - Enabled
      EHCI handoff - Enabled
      Fast Boot - Disabled
      Secure Boot - Other OS
      CSM - Disabled

      OpenCore Configuration Basic Understanding
      ACPI SSDT-EC.aml - fix for EC on Catalina and above SSDT-GPRW.aml - fixes immediate wake from sleep, paired with rename patch in plist SSDT-LPCB.aml - allows AppleLPC to be loaded, helps with power management SSDT-PLUG.aml - necessary for CPU identification and power management SSDT-SBUS-MCHC.aml - allows AppleSMBusPCI/Family/Controller SSDT-USBX.aml - USB power config Drivers AudioDxe.efi - boot chime HfsPlus.efi - reading Hfs partitions OpenCanopy.efi - GUI boot picker OpenRuntime.efi - NVRAM, memory management, etc Kexts AppleALC.kext - audio IntelMausiEthernet.kext - nic Lilu - various fixes and system enhancements USBPorts.kext - USB Mapping (you can edit this details in USB section) VirtuaSMC.kext - Apple SMC emulator WhateverGreen.kext - various fixes for graphics and system devices Resources download from binary resources, removed all audio except boot chime Tools OpenShell.efi - shell cli config.plist Highly suggest looking at the Dortania Guide Haswell section if you are want to know why x is set the way it is, I don't have time for that and that information is readily available USB Ports
      If all accessible ports are enabled in our system it is going to break the 15 port limit so a single sacrifice needs to be made. Instead of wiping out a whole port, I personally removed USB 2.0 ability on one of the USB 3 ports.

      The included USBPorts.kext includes all 16 ports, so the last USB 3.0 port SSP6 port(furthest from ethernet) will not function at 3.0 speeds if you use this kext as is. Customizing is simple with the kext. Open the plist inside the kext and you can remove the one port/functionality you don't need. Included are pictures labeling what is what HSXX and SSPX. There's also a SSDT included to help identify.

      Shout out to @YoshiMac for posting images of the USB ports mapped out. I included some of his work so you have quick access when deciding but his post is great as well. Hopefully I can return the favor a bit with this guide.

      OpenCore Config Customize
      While I added a SMBIOS just to get you going, you need to get your own SMBIOS - > https://dortania.github.io/OpenCore-Install-Guide/config.plist/haswell.html#platforminfo I'm using UIScale 2 for HiDPI, where as you may need to change to 1 Boot args currently uses verbose, you can remove that if all is well after I'm sure I'm forgetting to mention stuff, just let me know if I should warn about some other stuff here. Files Attached
      The included EFI is OpenCore 0.6.3 with updated kexts as of 11/18/2020

      USB Folder includes pics of the mapping and original USBPorts.kext with 16 ports for back up. There is also .dsl file which maps the ports if you need some clarification textually, do not use it.

      Modified 3503 bios for Maximus VII Hero with replaced NvramSmi from 1104.

      Well that wraps it up I think. If you need any extra advice or questions shoot away.
       
      Asus Maximus VII Hero OC 0.6.3 Share.zip
       
      BIOS in next post due to size limit
       
      Modified 3503 bios for Maximus VII Hero with replaced NvramSmi from 1104.
      3503modifiedM7H.CAP
    • By ltooz_audis
      I've installed Big Sur on HP Envy 13 i7-7500u HD620 KabyLake with DW1560 using OpenCore 0.6.4. Everything is working.
       
      Cheers,
      Louis
    • By ltooz_audis
      Everyone knows the DW1560 WIFI doesn't work in Big Sur and the Bluetooth only works without handoff support due to missing wifi. This is how I fixed mine.
      Cheers,
      Louis
    • By SolidaSlOl
      Hello, 

      I stuck on getting "root" as the last message after clicking install macOS:
      My build:
      Gigabyte Z370P D3 (BIOS version: F13)
      9400-F
      Gigabyte Radeon RX 5600 XT Gaming OC
      Samsung 970 Evo Plus 500GB
       
      I went through the whole OpenCore guide and tried the following (always got the same error):
      Both prebuild ACPI and "SSDTs: The easy way" (these are in the attached EFI folder) All types of HPET (as 4th file in ACPI) Without USBInjectAll.kext Changing USB after clicking "Install" (saw that recommendation somewhere) Both USB 2.0 and 3.0  
      I would really appreciate any help, thanks.
       
      EFI.zip
      Also, attached bios configuration.
       
       
       
×