I did this several months ago and I did not document it. I have a feeling that every MB is going to be different. It was not easy for the ProArt Creator, as it has the cover that has to be removed just to get access to the module itself. The toughest part for me was re-attaching the antennas on the new chip. I am very much near sited so I had no problems seeing it, but I have big fingers so having a plastic tool with a straight edge was very useful. I searched high and low for a guide or video on how to do it, but at the time I couldn't find anything and just muddled through it on my own.
BTW, I don't think the Z390 Designare module can be changed, unless you're talking about a different board.
Thank you, yep i’m preparing to upgrade to the z690 (already bought the proart that’s why I’m asking. I could not find any where any reference on how to do the modification…and came across with your build..
Anyway thanks a lot….
I thought it interesting to note that highend PC brand XMG is launching a new high performance PC tower system aimed at the audio and video markets called the XMG Studio. And it’s using my motherboard as their main build - the Asus Z690 Prime P D4. Good board choice I guess?
> https://www.tweaktown.com/news/8581...th-core-i9-12900k-geforce-rtx-3090/index.html
It will depend on which chipset the add-on card uses. But if you are saying a known Mojave compatible PCIe USB3 card from a Mac Pro does not work in your 600-series build, then you would have to check the PCI addresses being used.
It was just an error on my side. Using a standard clean injectall config with SSDT uiac and XHCI port limit the add in USB 3 work as USB 3, this is solving the issue for now...
I thought it interesting to note that highend PC brand XMG is launching a new high performance PC tower system aimed at the audio and video markets called the XMG Studio. And it’s using my motherboard as their main build - the Asus Z690 Prime P D4. Good board choice I guess?
> https://www.tweaktown.com/news/8581...th-core-i9-12900k-geforce-rtx-3090/index.html
In my testing (I made a video on my Italian channel) the Asus board, M version, had the best VRM in the 200 euros tier, which is basically all I care about OTHER THAN Thunderbolt. (weird enough also the b660 gigabyte board was better than the z690 gaming x with the testing cpu, i5 12600)
I completely agree with you about Mojave with its 32-bit compatibility (and it seems to be the last macOS to allow booting macOS from an external USB drive).
I worked on my ASUS Z690 Maximus Extreme and have Mojave working. The required CPU emulation is below (due to differing emulation sections, there must be discrete EFIs, one for Mojave and another for Big Sur/Monterey):
Neither Ethernet port works (because neither Aquantia AQC113 nor Intel I225V existed during Mojave's lifetime; AQN107 did, but it's not on the Z690 mobos, sigh), but the Fenvi T919 Wifi/BT AIC in slot 2 works for a WiFi-based Ethernet connection. Since there are only 3 PCIe slots on the mobo, there isn't room for both the Fenvi T919 AIC and another Ethernet card. (No room unless one makes herculean efforts to add a PCIe splitter for slot 2 to have 2 AIC hanging outside the rear of the chassis; I've bought the parts, but not used. A usable PCIe Ethernet card is this one; which requires the Mieze's kext, LucyRTL8125Ethernet, downloadable with the Kext Updater app or here.)
Contrary to comments about the USB ports, I have good functionality of USB-C and USB-3 on the front and rear panels of the build. I see no difference with USB ports when booting between Mojave and Big Sur/Monterey.
I'll attach the EFI (OC v081) for Mojave below. There are some settings that will need adjusting, such as SN input and USB port kext for any other mobo, shown in Spoiler below.
USB kext unique to this mobo; create for other mobos. If not using Fevi AIC, disable associated kexts. View attachment 546613
One significant issue is with the GPUs. Mojave requires pre-Navi GPUs and most of us are using Navi GPUs with Big Sur and Monterey. So I chose to use dual GPUs, with an ASUS Strix 6900 Big Sur/Monterey (or Windows 11) in slot 1 and a Nano Vega 56 in slot 3 for Mojave. To make this work, there are customized SSDT files and DevPro injections as shown in Spoiler below.
An important point. Due to the nature of the Z690 mobo, if you place an NVMe drive in the slot closest to the CPU, the 3rd PCIe slot is inactivated (booooo....). So I used the two NVMe slots farthest from the CPU, leaving the 1st NVMe slot empty. (The ASUS Z690 Max Extr does have an additional slot next to the DDR5 slots for a special AIC that can hold 2 additional NVMe drives; I have these both populated too.)
So if you want to use 2 different GPUs as discussed in this post, you will probably need to leave the 1st NVMe slot empty, but check your mobo manual to see if your mobo is different.
ACPI section. Note that there is a parallel SSDT (named SSDT-PEG1-BRG0-HDAU.aml) to use when booting into Big Sur or Monterey, which inactivates the Vega 56. This other SSDT also requires (not shown) a flipped version of the DevProp section where the "disable-gpu" is disabled for the 6900 and enabled for the Vega 56. View attachment 546615
Dev Prop section. Obviously, if you're using different GPUs, you'll need to adjust the details within the DevProp section for each GPU. If you don't adjust and have different GPUs, you'll likely have a boot failure. View attachment 546616
Additionally, there are some Memory settings that could be customized as shown in Spoiler below. If you don't want to bother with this section, simply disable CustomMemory and ignore the details below.
One thing to note about this dual boot setup: booting is usually begun using the monitor connected via DP to the 6900 GPU. When the BIOS screen appears, press F8 to allow EFI selection from BIOS: selecting the EFI associated with the Mojave drive. Once selected, the boot process continues into OC, and from the OC menu, the Mojave drive is next chosen.
Once the Apple logo progress bar reaches about half-way, it appears frozen. The boot is not frozen, just the DP input. At that point (or a bit earlier), switch the same monitor from the DP to the HDMI input (which is connected to the Vega 56), and the progress bar continues. From this point, the HDMI input is controlled by the Mojave OS.
BTW, all attached images are inside the Docs folder of the posted EFI.
Finally, do exam all ACPI, DevProp injections and kext settings beyond what I've described above, to see if the settings are agreeable with your mobo. And please only test this EFI by placing it on a removable drive, not your main EFI.
Catalina, Big sur, and Monterey still can boot from an external USB but they need to support SCSI over USB (UASP) to work properly.
Some Samsung drives like the T7, unfortunately, have a TRIM incompatibility with Monterey, which causes a very slow default boot up time on Monterey. But you can set OpenCore’s SetAPFSTrimTimeout to 0 to mitigate the issue.
@easy31 use this EFI, made for you. In PlatformInfo put your network MAC and serial number, system UUID..... for iMacPro1,1. Inside is the latest OpenCore 8.1.
Hello @StefanAM,
I am progressing on the installation of the hackintosh. I just need to solve the problem of network with AQUANTIA AQC 113C, can you help me?
I added in ACPI the SSDT AQUANTIA.aml file attached but it still does not work...
Hello @StefanAM,
I am progressing on the installation of the hackintosh. I just need to solve the problem of network with AQUANTIA AQC 113C, can you help me?
I added in ACPI the SSDT AQUANTIA.aml file attached but it still does not work...
first of all thank you very much for your help.
I followed Miliuco's tutorial, but unfortunately it still doesn't work...
Below is what I have:
- Extract via Opencore debug from DMAR.aml
- delete DMAR.aml ACPI/systeme with config.plist
- Insert DMAR.aml modifier in OC/ACPI
- config.plist Delete DMAR.aml in ACPI/Delete
first of all thank you very much for your help.
I followed Miliuco's tutorial, but unfortunately it still doesn't work...
Below is what I have:
- Extract via Opencore debug from DMAR.aml
- delete DMAR.aml ACPI/systeme with config.plist
- Insert DMAR.aml modifier in OC/ACPI
- config.plist Delete DMAR.aml in ACPI/Delete
Okay. For the SSDT-AQUANTIA yes you should remove it otherwise it will conflict.
You should try to have ForceaquantiaEthernet disabled also using the new DMAR setup.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
(weird enough also the b660 gigabyte board was better than the z690 gaming x with the testing cpu, i5 12600)
