My build is for music production, video editing, some 3D content creation for filmmaking. After being up and running, using the build for daily use under heavy video editing workloads, I can say it is super stable, and can recommend this build to anyone, even regardless of the Intel 13/14 gen fears (most important thing one can do is update BIOS and use modified settings which I show below).

Also, I am with the Puget Sound mentality on this Intel question: https://www.pugetsystems.com/blog/2024/08/02/puget-systems-perspective-on-intel-cpu-instability-issues/

They are some pretty rigorous people, and even before reading their report, just from doing extensive research it was clear that setting up your BIOS is the number one thing one can do to help improve stability/longevity of their CPU. So until we have 13/14 gen CPUs recalled, removed from shelves at retailers, then I see no reason to dissuade anyone from buying 13/14 gen Intel on basis of fear over what could/might/may/perhaps happen.

With next gen Intel CPUs coming out, it sure will be interesting to see what is around the corner, and I will build a next gen system once it is proven out. But for now, late August 2024 this build represents just about as high end hackintosh as you can get.

*****

Some Benchmarks (note: SMBIOS iMacPro1,1):

GPU:

GeekBench 6.3 OpenCL 137000-139000. Metal 265000-268000. These scores are higher than on any Mac currently in existence.

CPU:

GeekBench 6.3 ~ 3000/20000

CineBench R23 ~ 2000/32500

CineBench R24 ~ 128/2005

*****

What Works? Pretty Much Everything hence asterisk SUCCESS*.

Sleep/Wake: No issues at all. No crash on wake from 2nd sleep that some report with Z790 boards.

No random crashing. No internet dropping out. Bluetooth seems to work just fine. All fine with GPU, Audio.

Not sure about Thunderbolt as I have no devices to test, but About Mac shows TB as two ports 40 Gb/s, so that is good sign I suppose.

iCloud, iStore work fine, and updates are working.

*****

What Not Working? FaceTime and Messenger work if using Itlwm kext, not with Airportitlwm. AirDrop not working, but community already has shown how to get AirDrop working using OCLP and, for instance, Fenvi T919 card.

Certain Apple Silicon only features won’t work. Nothing particularly interesting.

In Logic Pro, there is new AI hardware emulation plugin called ChromaGlow. Oh no – what is one to do without AI hardware emulation? Oh right., there is no shortage of pro hardware emulation plugins out there from UAD, Slate, etc. Also there is AI Stem Splitter, and since there is no shortage of third party stem splitters, this feature isn’t a deal breaker (serious remix producers tend to acquire real stems anyway).

In Final Cut Pro latest version, there is AI color correction which isn’t of much use if you have experience with color correction/grading, as well as an AI slow motion function, which doesn’t have demonstrated improvement over best optical flow methods especially in conjunction with modern cameras outputting insane slow motion.

Bottom line on Apple AI: If you are a talented creator, you won’t miss Apple Intelligence features and if you are resourceful you have access to any imaginable AI feature via other avenues…. Heck, in FCP they still can’t even offer auto roto brush, and the object tracking features are way behind their competition, so no matter what Apple brings to the game, they are just not catching up to Adobe and DaVinci on the video front, and on audio front Logic is still an awesome DAW without these added AI features.

*****

The Build

I have insanely detailed info on this build on the TM site here: https://www.tonymacx86.com/threads/success-asus-z790-proart-creator-14700k-6950-xt.330009/ I don’t really care about the whiney politics between these various Hackiontosh forums. They are all good. In any case I cover all the steps below so that this post is self contained.

📺

Also I have video series on the entire process of putting together a Windows/Mac system: https://www.youtube.com/playlist?list=PLgg8TepcCQdM8jB8LjdMa396mcjjAmvDL Parts 6-8 cover this Sonoma build.

One of my critiques of this reddit forum – even though it is great forum – is there is too much laziness when it comes to builds. Too much “read the guide” cliches. Good luck making this sort of build with “the guide”…

So my goal here is to provide a master class on a hackintosh setup, so people can see every needed step and benefit from that valuable educational process.

Here goes…

The Recipe

View post on imgur.com

Asus Z790 ProArt Creator WiFi – great board with Aquantia (AQC 113CS) 10 Gb and Intel (I 216-V) 2.5 Gb ethernet, as well as Intel (AX 210) Wifi 6. 4 NVMe slots. Thunderbolt 4. Good dual GPU support, as 2 GPUs will be treated as x8/x8 which has negligible impact on performance

Intel i7-14700K – with latest BIOS 2504 with 0x129 plus additional settings, this is excellent stability/performance compared to default Intel baseline

Red Devil 6950 XT – requires some extra work but I show the details

G.Skill Trident Z5 2×32 GB DDR5 6400 – on Asus QVL, XMP working fine in Windows/Sonoma

WD SN850X (x3) – these are for Sonoma, Video Editing, Audio, etc

Samsung 990 – this is for Windows 11

Samsung T9 – this is for fast external USB storage

WD EasyStore 5TB, 8 TB – these are for medium term backup needs for Windows and Mac

Fractal Torrent Case – great for air cooling

Thermalright Phantom Spirit Evo 120 Cooler – yes, air cooler; don’t listen to AIO mafia. With this build you will get very good air cooling results, especially when this cooler paired with case like Fractal Torrent

Corsair RM1000X – I could get away with 850W, but the extra headroom is because I plan on adding 2nd GPU to have Nvidia in Windows

Thermal Grizzly Kryonaut – this is just to maybe get improved cooling

Thermalright LG1770 Contact Frame – this is just to maybe get improved cooling

RME BabyFace Pro USB Audio – just a regular USB 2 device, nothing crazy, but works

Installation Notes: Preparation

There are existing guides, such as the Z690 ProArt Golden Build from Casey, but because there are so many nuances of a given build, and because Golden Builds often contain important nuances found hundreds of pages later, I prefer to start from scratch, research for a couple weeks, ask around in forums, and determine every detail.

I decided to do as much as possible up front on Windows, as I believe the hackintosh community needs to do a better job showing people how to do full prep work in Windows, since many would-be hackintosh adventurers won’t have Mac access. That said, all my below steps can be done on Mac of course.

BIOS

Get latest version from ASUS website.

Go into BIOS.

Here are my settings, including specific things for stability/performance on Intel 13/14 Gen CPUs:

1. In EZ Mode main screen set XMP to Enabled.
2. Switch to Advanced Mode. Under AI Tweaker set AI Overclock Tuner~ to XMP I or XMP II.
3. Under AI Tweaker-> Choose Intel Default Settings under Performance Preferences, which is the so-called Intel Baseline Profile which will apply conservative settings Intel suggests for stability (253W for Long Term Package Power and Short Term Package Power, 307A for ICCMax). Also here on top set ~Intel Adaptive Boost Technology to Disabled. And last thing here, set SVID Behavior to Auto.
4. Under AI Tweaker->Internal CPU Power Management, based on this thread: https://www.\*\*\*\*\*\*.com/r/intel/comments/1eebdid/1314th\_gen\_intel\_baseline\_can\_still\_degrade\_cpu/,

• Set AC Loadline to some value lower than 0.5. If you lower in .1 decrements you will end up with stress test failures in, for instance, Intel XTU. In my case I set to 0.1 because my failures happen at 0.06, so I went above that to ensure stability.
• Set IA VR Voltage Limit to 1400 (1.4 volts). This prevents the CPU from having 1.5V spikes.
• Set IA CEP to Disabled (only if lowering AC Loadline).

1. Under Advanced->CPU Configuration, note that Active Performance Cores and Active Efficient Cores are set to All, and Hyper Threading is Enabled by default. You will see this mentioned in various build notes as being required settings in order for Sonoma to make use of all cores in some fashion.
2. Under Advanced->System Agent Configuration note Vt-d is Enabled by default. Also note the entry Control Iommu Rre-boot Behavior. Mine was set to Enabled by default, as that apparently was the case from whatever the system analyzed (details of DMAR table or something). There is no information in the community about this.
3. Under Advanced->System Agent Configuration->Memory, notice that Memory ReMap is Enabled by default. This is what makes Encode Above 4G work.
4. Go to Advanced->System Agent Configuration->Graphics Configuration, chose PEG Slot as Primary Display, and if you are using K version of the CPU for use in Windows, set iGPU Multi Monitor to Enabled.
5. Go to Advanced->Thunderbolt Configuration. Ok, this is a topic… Some say disable during install, some say keep it all enabled. I use defaults.
6. Go to Advanced->Trusted Computing and set Security Device Support to Disabled.
7. Go to Advanced->UEFI Variables Protection and set Password Protection of Runtime Variables to Disabled. I set this because I figure given how much access OpenCore requires to UEFI, we probably want it disabled. Also, the ModGrubShell command to unlock CfG will fail if this is set to default Enabled.
8. Go to Advanced->PCI Subsystem and note that Resize BAR Support is Enabled by default.
9. Go to Advanced->USB Configuration and set Legacy USB Support to Disabled, and XHCI Handoff should be Enabled by default.
10. Go to Advanced->Onboard Devices Configuration and make sure all devices are Enabled (HD Audio, Intel LAN, Marvel 10G LAN, USB Power Delivery in Soft Off State, WiFi Controller, Bluetooth Controller).
11. Go to Advanced->Onboard Devices Configuration->Serial Port Configuration and set Serial Port to Disabled.
12. Go to Monitor and make sure CPU Fan Q Fan Control is set to PWM Mode. Do the same for a second CPU fan and all your chassis fans. Default setting of Auto is probably fine, but since we know all these fans from the cooler and case are PWM Mode, may as well just set them.
13. Go to Boot->Compatibility Support Module (CSM) and set Launch CSM to Disabled.
14. Go to Boot->Secure Boot and set OS Type to Other OS.
15. Go to Boot->Boot Configuration and set Fast Boot to Disabled.

Sonoma Prep In Windows

1. Download OpenCore 1.0.0 (or newer). See here for releases: https://github.com/acidanthera/OpenCorePkg/releases. Copy the included EFI folder to your USB drive, desktop or somewhere.

2. Create the Sonoma Install USB. Steps: https://dortania.github.io/OpenCore…-guide/windows-install.html#downloading-macos. To perform this setup you need the macrecovery tool found in your downloaded OpenCore EFI/Utilities folder.

Run the download utility by right clicking the EFI/Utilities/macrecovery folder, choosing “Open Terminal”, then using the command to download latest version of Sonoma:

Code:

python3 macrecovery.py -b Mac-937A206F2EE63C01 -m 00000000000000000 download

You may get a result similar to what I got:

https://preview.redd.it/unaj5964n5ld1.png?width=1705&format=png&auto=webp&s=8e91be74758c79380c3fc18da9b6b69f882c19c3

I had to use the command python and not python3. Follow rest of the Dortania instructions at above link to create your Sonoma Install USB.

** Note: If you make a full Sonoma offline USB installer on Mac it won’t fit on a 16 GB USB! Use 32 GB.

3. Gather the myriad of tools we will need to get things set up.

Tools that work on Windows or Mac:

SSDTTime: Get dump of the DSDT table and perform various SSDT actions.

MountEFI: Help mount EFI partitions.

ProperTree: Editing our config.plist file

GenSMBIOS: Generating information such as Serial Number for chosen SMBIOS.

USBToolBox: Create custom USB Map.

Intel Power Gadget: Mac version at the link

UEFITool: For CFG unlock – Be sure to press Show All Assets!

Universal IFR Extractor: Another tool for CFG unlock… **Note that this is not the link from Dortania, but link to new version. I use Windows version in my guide.

Mac-only Tools:

Hackintool: View various bits of system information

IORegistryExplorer: View incredibly detailed information about system devices.

VDADecoderCheck: Test if hardware decode/encode working on GPU

HeliPort: If using Itlwm.kext

RadeonGadget: Comes with RadeonSensor kext

Place all these tools in some convenient location.

EFI Tools:

Modified GRUB Shell: Unlock CFG. Place ModGRUBShell.efi in your EFI/OC/Tools folder.

ControlMsrE2.efi: For CFG unlock, already under stock EFI/X64/OC/Tools folder so you need to copy it to your EFI/OC/Tools folder.

ResetNVRAM.efi: Already in the OpenCore distribution under EFI/X64/OC/Tools so you need these in USB EFI/OC/Tools folder.

Sonoma Preparation in Windows Continued – Create SSDTs

Here is the guide on SSDTs: https://dortania.github.io/OpenCore-Install-Guide/ktext.html#ssdts

I prefer to build SSDTs manually or with SSDTTime. SSDTTime is great way to build needed SSDTs and we already downloaded it.

1. Dump your system DSDT. Launch SSDTTime and you will see

https://preview.redd.it/bs99aetvo5ld1.png?width=1102&format=png&auto=webp&s=33c73863d526934d5e79c4e90b1e40b97852bd7a

** Note: If you don’t see the P option it might be because you are in a location that Intel blocks. So connect via a VPN if needed. I am in Moscow and needed VPN.

Enter “P” and you will end up with a bunch of .aml and .dsl files under your SSDTTime/Results/ACPI folder. That ACPI folder won’t exist at first, but will be there after the first time you choose that “P” option. The .dsl files are decompiled .aml files, just text files so we can see what is in a SSDT. One of these files is called dsdt.dsl. We will need that to do some searches.

On Mac, when you use MacIASL and open a .asl file, it decompiles so that you see the text result. On Windows we will have all these decompiled text files available, so just use whatever text viewer you want.

2. Build the essential SSDTs. See here: https://dortania.github.io/Getting-Started-With-ACPI/ssdt-platform.html. For 14th Gen Intel we use essential SSDTs needed for Comet Lake. Those are SSDT-PLUG-ALT, SSDT-EC-USBX, SSDT-RHUB, SSDT-AWAC. We can build all these from SSDTTime.

SSDT-EC: Fix Embedded Controller

From the SSDTTime main window, choose 2 (FakeEC). It will then instruct you “Please drag and drop an ACPI table or folder of tables here:” So just click on your SSDTTime/Results/ACPI folder and drag it right there on to the terminal, then hit enter. You will end up with SSDT-EC.asl and SSDT-EC.dsl in your SSDTTime/Results folder.

SSDT-USBX: Provide proper USB Power

From the SSDTTime main window, choose 4 (USBX) then the default option presented. You will end up with SSDT-USBX.asl and SSDT-USBX.dsl in your SSDTTime/Results folder.

SSDT-PLUG-ALT: Enable Proper CPU Power Management

From the SSDTTime main window, choose 5 (PluginType). You will end up with SSDT-PLUG-ALT.asl and SSDT-PLUG-ALT.dsl in your SSDTTime/Results folder.

SSDT-AWAC: Fix Real Time Clock

From the SSDTTime main window, choose 7 (RTCAWAC). You will end up with SSDT-RTCAWAC.asl and SSDT-AWAC.dsl in your SSDTTime/Results folder.

SSDT-USB-Reset: Force Rebuild USB Ports

This is mainly needed to help USB Mapping on Mac. As I did USB Map in Windows I did not enable this SSDT. On USBToolBox page it says “Removes the need for controller renames in ACPI patches”. That is another way of saying SSDT-USB-Reset not needed.

But if you feel it will help you, from the SSDTTime main window, choose 8 (USB Reset). You will end up with SSDT-USB-Reset.asl and SSDT-USB-Reset.dsl in your SSDTTime/Results folder. These are same as what is commonly called SSDT-RHUB.

** Note: I notice that if SSDT-RHUB/SDT-USB-Reset is enabled, I have to hit a key twice to wake from sleep. With disabled, I only need to hit key once.

SSDT-Bridge: Correct Unnamed PCI Bridges

This is to build a PCI Bridge SSDT. This is needed if you have to spoof a GPU, and you have unnamed PCI bridges. See here https://www.tonymacx86.com/threads/radeon-rx-6950-xt.320302/ if you want to learn more about this process from the incredibly helpful contributors on that thread. There are often nuances, especially if you are using different hardware, so in case things for you don’t appear as they do for me, be sure to ask for help there.

We need to determine GPU device address and build SSDT-Bridge. Go to Device Manager, click on your GPU, then under Details tab choose Location Paths. In my case result was

https://preview.redd.it/kl9uoyv1p5ld1.png?width=660&format=png&auto=webp&s=8c0e94e280a7f7013668a753495a9a8e0c28da62

PCIROOT(0)#PCI(0100)#PCI(0000)#PCI(0000)#PCI(0000) PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)

ACPI(_SB_)#ACPI(PC00)#ACPI(PEG1)#ACPI(PEGP)#PCI(0000)#PCI(0000)

The path starts out with named bridges PC00, PEG1, PEGP, but then at the end we have 2 unnamed bridges #PCI(0000)#PCI(0000). This is why we need bridge SSDT.

Go back to SSDTTime main windows. Choose 9 (PCI bridge). You should see

https://preview.redd.it/4ohll8w4p5ld1.jpg?width=868&format=pjpg&auto=webp&s=f2be6d239c320adb3f43299f06d31d0f587365bf

Here you just copy and paste PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) to the SSDTTime terminal and hit enter. You will end up with SSDT-Bridge.asl and SSDT-Bridge.dsl in your SSDTTime/Results folder. Here is what my SSDT-Bridge.dsl looked like:

DefinitionBlock ("", "SSDT", 2, "CORP", "PCIBRG", 0x00000000) { /* * Start copying here if you're adding this info to an existing SSDT-Bridge! */ External (\_SB.PC00.PEG1.PEGP, DeviceObj) Scope (\_SB.PC00.PEG1.PEGP) { Device (BRG0) { Name (_ADR, Zero) // Customize this device name if needed, eg. GFX0 Device (PXSX) { // Target Device Path: // PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0) Name (_ADR, Zero) } } } /* * End copying here if you're adding this info to an existing SSDT-Bridge! */ } 

Seems Macs expect that last named bridge to be GFX0 or GFX1 or something. So I just edited the file, replacing PXSX with GFX0. Then I compiled so that I ended up with an edited SSDT-Bridge.asl. You can do this with the iasl.exe file that is under your SSDTTime/Scripts folder. Open a terminal and make sure you are in that Scripts folder, and enter the command how I show below:

https://preview.redd.it/vub502i9p5ld1.png?width=1360&format=png&auto=webp&s=0cbf6ea5b4fa890fba54364c46a31b2ec5719ca0

3. Square away Thunderbolt 4 SSDTs. Wow, a lot of work by a lot of contributors to get Thunderbolt Maple Ridge working as well as possible! Read here if interested: https://www.tonymacx86.com/threads/thunderbolt-4-modified-firmware-full-thunderbolt-bus-tree.329459/, https://www.tonymacx86.com/threads/thunderbolt-4-gc-maple-ridge.319857/

To get needed SSDTs for this motherboard, go to https://www.tonymacx86.com/threads/…-i7-12700k-amd-rx-6800-xt.318311/post-2405034 and download the two SSDTs that provided me: SSDT-THB4-RP05.asl, SSDT-DTPG.asl Or just get them from my EFI. Save those to SSDTTime/Results. We aren’t using SSDTTime here, but easier to just have our SSDTs in that folder. You will need these SSDTs for your EFI folder later. Note, the SSDT-DTPG isn’t thunderbolt specific. It just adds a function call that allows some other SSDTs to be cleaner/shorter.

4. Remove Reserved Memory from DMAR Table. Edit your DMAR table so it has no Reserved Memory Regions. Trust me, Asus Z790 ProArt BIOS (versions 2202 through 2504 anyway) has Reserved Memory Regions. Apparently various functions related to Vt-d, and networking (and GPU?) can be made to function better when following the Dortania steps on DMAR: https://dortania.github.io/Getting-Started-With-ACPI/Universal/dmar-methods/manual.html#preparation

We are still going to use SSDTTime, so don’t think we are done with it! Back at SSDTTime main window hit B to Fix DMAR. You should see this:

https://preview.redd.it/4kwipsjjp5ld1.png?width=1099&format=png&auto=webp&s=d44fe9a36756cde126f447bd9744ca56dcca119c

You will end up with DMAR.asl and DMAR.dsl in your SSDTTime/Results folder.

5. Some SSDTs that in theory can help and not hurt.

SSDT-HPET – Fix IRQ conflicts

See here: https://dortania.github.io/Getting-Started-With-ACPI/Universal/irq.html. Little info, but the idea is IRQ conflicts can arise and we may as well prevent them. Back to SSDTTime, enter 1 (Fix HPET). You will be told about potential conflicts. Hit default option (C). You will end up with SSDT-HPET.asl and SSDT-HPET.dsl in your SSDTTime/Results folder.

SSDT-SBUS-MCHC – Enable Proper Diagnostics

This has to do with helping make sure things like temperature, fan readings and other diagnostics are correctly produced in Mac. Go here: https://dortania.github.io/Getting-Started-With-ACPI/Universal/smbus.html where we will create SSDT-SBUS. It says “For install purposes, this SSDT isn’t needed but for post-install it’s recommended to put the final touches on your hack.” Since I prefer doing as much up front work as possible, let’s just make this SSDT now. Following the guide, get the BIOS Device Name under Details tab for your SBUS in Device Manager under System Devices. Here is what I see

https://preview.redd.it/r4ux2chlq5ld1.png?width=1156&format=png&auto=webp&s=1116882f7a676685f4edea058814d2da10e9f415

Download the sample SSDT-SBUS-MCHC.dsl file from above link. You will see the template contains “PCI0” in various places. Just open the .dsl file you just downloaded – it is just a text file.

** Note: The Dortania guide is outdated… The template has some stuff we don’t need, since our SSDT-DTGP enables simplified SSDTs in certain cases. So make some changes to the template first:

Delete the entry that says External (_SB_.PCI0, DeviceObj). Also delete the whole section that starts with Scope (_SB.PCI0){.

Uncomment out the section starting with Device (DVL0) {.

Now, everywhere you see “PCI0” change it to whatever you saw in Device Manager a couple minutes ago. In my case it is “PC00”.

Make sure your edited SSDT-SBUS-MCHC.dsl is in your SSDTTime/Results folder. Go back to a terminal and make sure you are at this SSDTTime/Results folder. Enter the iasl.exe command as shown below to compile this .dsl file and end up with SSDT-SBUS-MCHC.aml.

https://preview.redd.it/f7hjoobsq5ld1.png?width=1413&format=png&auto=webp&s=466406521588fe67690f2825e3c383e7023eba41

*****

As a result of these SSDTTime special operations and other SSDT actions, as well as ignoring some SSDTs that are certainly not needed, you should have these files under your SSDTTime/Results folder:

SSDT-RTCAWAC.aml
SSDT-PLUG-ALT.aml
SSDT-USBX.aml
SSDT-EC.aml
SSDT-HPET.aml
SSDT-DTPG.aml
SSDT-THB4-RP05.aml
SSDT-SBUS-MCHC.aml
SSDT-Bridge.aml
DMAR.aml

SSDT-USB-Reset.aml ***

** Note: SSDT-USB-Reset.aml you probably don’t need if using USBToolBox.

Now that you have all these SSDTs, copy the ones ending in .aml to your USB EFI/OC/ACPI folder.

Sonoma Preparation in Windows Continued – USB Mapping

The dreaded topic… Elephant in the room… People, it really isn’t that bad.

I can’t write everything out because of the annoying reddit error about too many characters. So just see my TM guide or youtube video, where I show you the USBToolBox mapping process.

Here is what I mapped, where anything with something after equal sign means I included it in my map.

https://preview.redd.it/xzmep9ius5ld1.png?width=1627&format=png&auto=webp&s=6f08470d7e22385bbb0e75cbeeb72e4838667698

https://preview.redd.it/c4sg8s97t5ld1.png?width=1374&format=png&auto=webp&s=a23ffcda090695f45ed61b172bec571b25b172c7

https://preview.redd.it/jfowsw19t5ld1.png?width=1216&format=png&auto=webp&s=9488a38cda161438b4f4e6f2a59420f8934857d3

Sonoma Preparation in Windows Continued – Gathering Kexts

Figure out needed kexts, in addition to UTBMap and USBToolBox kext that we already have from USB mapping. One really needs to read the Dortania guide very closely. My choice of kexts is based on the hardware that the ASUS Z790 ProArt Creator contains. That is, the built in WiFi (AX211), Bluetooth, Intel ethernet (i226-V) and Marvel ethernet (AQC113), Thunderbolt 4. I did not add any other hardware, apart from USB devices that don’t require anything. I named this build “Out of the Box” because it is meant to be used for all the existing hardware. You may need different kexts if you are not replicating my build, but instead adding additional hardware.

Look through here to confirm what you need: https://dortania.github.io/OpenCore-Install-Guide/ktext.html

So here is what I needed:

– Lilu
– VirtualSMC
– Whatevergreen
– SMCProcessor (kext contained in VirtualSMC download)
– SMCSuperIO (kext contained in VirtualSMC download)
– RadeonSensor
– SMCRadeonGPU (kext contained in RadeonSensor download)
– AppleALC
– NVMeFix
– USBToolBox (I am currently not using as I am using USBToolBox Native Classes option)
– USBMap (my custom USB map – maybe not right for you; if you use USBToolBox Native Classes option this will be named USBMap; if Native Classes disabled, then this will be named UTBMap)
– IntelBlueToothFirmware
– IntelBTPatcher (kext contained in IntelBlueToothFirmware download)
– BlueToolFixup
– Airportitlwm
– Itlwm (kext contained in Airportitlwm download)
– RestrictEvents
– CPUTopologyRebuild
– Z790-XHCI-Unsupported (this seems to be needed when using USBToolBox and Native Classes option)

** Note: I am not using CPUFriend and CPUDataProvider. You may need them if you choose 7,1 SMBIOS.

** Note: I am using the Sonoma 14.4 release of Airportltlwm. All other kexts are just standard latest releases.

** Note: Don’t enable both Airportitlwm and Itlwm. If you want to have iMessage, FaceTime working, then use Itwlm. But during install you need to use Airportitlwm to get WiFi internet or use ethernet. Definitely read the notes on the Airportitlwm page to see the pros and cons of Airportitlwm vs Itlwm. If using Itlwm, you will need HeliPort app to connect to WiFi.

Sonoma Preparation in Windows Continued – Gathering Drivers

See here about Drivers: https://dortania.github.io/OpenCore-Install-Guide/installer-guide/opencore-efi.html and here https://dortania.github.io/OpenCore-Install-Guide/ktext.html#firmware-drivers. Notice the first link doesn’t mention HFsPlus.efi, but second does. Yeah, that is why the guide is frustrating. So make sure HFsPlus.efi is in your USB EFI/OC/Drivers folder.

Sonoma Preparation in Windows Continued – Editing Config.plist

**Note: See my TM guide, as there is too much to write here and I keep getting “you exceeded character limit” error when trying to post this…

Ok, finally almost ready! This was my explanation of anything that I did that might be different from default sample.plist and different from the settings shown in the Comet Lake guide, and different from other documented builds out there. Remember, my settings are very specific to the hardware I want to use on the motherboard and my BIOS settings.

Sonoma Preparation in Windows Continued – Disabling CFG Lock

If I write it all out I will exceed post character limit – so just see my TM guide.

Finally you can install Sonoma!

Installation Notes: Installing Sonoma

1. First, unlock CfG using results we just obtained:

Boot OpenCore. Be sure to hit space bar right away to see the tools.

So you choose Modified GRUB Shell from the menu (be sure to hit space bar right away to get to the tools list!).

Once you are in the GRUB shell, issue the command

This command is as shown in the guide, but we changed it to use 0x44, because that is what we found. You will see some verbose output, saying it was a success.

setup_var_cv CpuSetup 0x44 0x01 0x00 

2. Confirm CfG unlocked

Run ControlMsrE2 tool again and this time you will get result:

This firmware has UNLOCKED MSR 0xE2 register! 

3. Launch Sonoma Installer. Choose the Sonoma base image dmg that OpenCore will display as a boot option. This runs the installer. You will see verbose output, maybe some errors, don’t panic. Maybe you will see some “RT.GV wake-failure” error.

I never got to the bottom of this but it doesn’t seem to have an impact on anything.

OpenCore should produce a lot of verbose output and after a while you will arrive at the Sonoma install screen. However, if prior to that you get a reboot, then just run the installer again and you should arrive at Sonoma install screen.

4. Choose Install Drive. At this point there will be delay as Sonoma thinks about your drive. This is the stage where you might get error about needing a firmware update to install to the volume. If so, set CustomSMBIOSGuid False and be sure to set UpdateSMBIOSMode to Create.

5. Install Sonoma. After Sonoma confirms all is well with your install drive, install will begin. You should have WiFi already working, so select your network and connect, or use Ethernet. Sonoma will download all the other components apart from the 700 MB Base Image file that we downloaded as part of making the USB installer. You will see the installer telling you there is around 2 hours and 30 minutes left or something. Then a reboot in much shorter than the advertised time. Make sure to select the USB drive again, and this time choose “Install Sonoma” as the boot option in OpenCore. This resumes the Sonoma install that we just set in motion. If after choosing the installer you get kicked back to computer restart, don’t panic. Just boot again, and again choose the “Install Sonoma” option from OpenCore. These issues will likely not be boot loops, so nothing insurmountable. Patience required. However, if you do get insurmountable problem, then time to go on the forums and ask for help!

When the installer resumes it might say 20 minutes remaining or something, plus another couple reboots, and at some point you should be taken to the setup procedure – choosing keyboard language, etc, etc.

** Note: Just be sure upon any reboot, that you select the correct OpenCore boot option. At several reboots, you will see “Install Sonoma”. But when install and setup are complete, you will see “Sonoma” as a boot option, as well as a “Sonoma Recovery” option. Like I said, patience is key. You may see reboots you weren’t expecting (though most are expected), so during any reboot just choose appropriate entry and you should be up and running, especially if you follow this guide very carefully.

You have now installed Sonoma! Time to test everything works.

** Note: At this point Windows 11 will be available in OpenCore. You can also just boot directly to Windows via BIOS. For now I am booting via BIOS.

***************************************************************************

Post Installation: Adjustments, etc

If you want to use Itlwm in order to have iMessage and FaceTime working, you need to put Itlwm kext in your EFI/Kexts folder, disable Airportitlwm. Then reboot, launch Heliport to connect to your WiFi.

Here is Dortania guide on some post install actions: https://dortania.github.io/OpenCore-Post-Install/#how-to-follow-this-guide

The only action here I took post install, was this:

Fixing Sleep | OpenCore Post-Install

I noticed at times my computer would freeze upon waking from sleep, so I issued these commands:

Code:

sudo pmset autopoweroff 0 sudo pmset powernap 0 sudo pmset standby 0 sudo pmset proximitywake 0 sudo pmset tcpkeepalive 0 

After this, I have not had a single crash/freeze on this system since I made the change three weeks ago.

Post Installation: Verifying Proper Functioning

**Note: It is always a good idea to reset NVRAM twice after making changes to BIOS or to your EFI. Anytime you get an unexpected reboot when launching Sonoma, reset NVRAM. Keeping this in mind can help avoid headaches.

1. Custom CPU Name

Look under About My Mac and you will see the custom CPU name we gave it:

Intel(R) Core(TM) i7-14700K 

2. Ethernet, WiFi

Now look under System Report. You will see under ethernet your Aquantia AQC113 and Intel i226-V entries. You will also see your WiFi entry. Run an internet speed test, which of course will have results dependent on your internet provider. In my case on WiFi I get around 310 Mbps Download, 185 Mbps Upload. With both Aquantia and Intel Ethernet I get around 540 Mbps Download and Upload. If you test in local network you would get closer to theoretical maximums speeds for ethernet controllers.

3. Bluetooth

I don’t have BT devices like mouse, etc, but tested file transfer from my MacBook as well as to my MacBook. All is well. For this you have to enable BlueTooth sharing on both computers.

4. iServices

AirDrop won’t work with this setup, but if you use a Fenvi T919 card and OCLP you can get AirDrop working.

Messenger and FaceTime work if I use Itlwm kext and Heliport.

5. Audio

I get HDMI or DP audio from GPU, as well as all the audio inputs/outputs on the Asus Z790 ProArt Creator via AplleALC layout id 13 (which TM user Casey made for Asus 690 ProArt Creator, which has same audio layout as the Z790 ProArt). Also my audio interface RME BabyFace Pro works fine.

6. NVMe/SSD

I ran Blackmagic Disk Test and get around 5800 MB/s Read and Write speeds.

7. Thunderbolt

I don’t have Thunderbolt devices, but under System Report->Thunderbolt I see two 40 Gb/s ports, so that suggests all could be well.

8. USB

All is well, thanks to our very thorough USB mapping! Just use Hackintool, plug a USB 2 and 3 device in all ports, and you will see that all your mapped ports are working.

9. Power Management

All is well. I followed here: https://dortania.github.io/OpenCore-Post-Install/universal/pm.html and see in IORegistryExplorer that XCPM is present.

10. Confirm SSDT-SMBUS-MCHC is working

As shown here https://dortania.github.io/Getting-Started-With-ACPI/Universal/smbus-methods/manual.html#verify-it-s-working enter this command in a terminal:

kextstat | grep -E "AppleSMBusController|AppleSMBusPCI" 

You should see two results. If you see only one, something isn’t right.

11. GPU

Run the tool we added earlier: VDADecoderCheck. It shows output

Hardware acceleration is fully supported 

Also I ran GeekBench 6.3 GPU OpenCL and Metal tests. OpenCL is around 137000-139000. Metal is around 265000-268000. Both of these scores are higher than on any Mac currently in existence.

12. CPU

About Intel 13/14 gen – one just needs cool head. Update to latest BIOS, make adjusted settings. You will end up with greatly reduced temperatures (I get no thermal throttling), reduced power, reduced Vcore. And your performance will take almost no hit.

My GeekBench 6.3 scores average around 3000/20000

CineBench R23 scores average 2000/32500

CineBench R24 scores average 128/2005

13. Temp, Power, etc

Using the modified BIOS settings shown above in BIOS section, I see excellent results.

Under stress tests:

Temperature max around 82, average around 80

Power max and average around 200W

Vcore max 1.35 and average 1.185.

These are all far lower than compared to Intel Baseline Profile with 0x129 microcode fix. This is why it is important to use modified settings.

Conclusion:​

I would say this is a superb build. Been using everyday for several months, performing very heavy video editing tasks daily, and everything is smooth, stable.

Again, thanks to dozens of you who helped! And again, all details are shown in the YouTube video as well. So if this guide is a bit tough to follow and you want to see more visuals, then just watch the videos or see my TM guide.

thanks