Contribute
Register

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

cost difference :) , especially because I would use my already owned, fast timing, DDR4 32gb kit
Maybe look at M-ATX boards then as well although not a lot of those out there either. Just an FYI, Asrock lists K class processors as supported.


 
HI m4rk0, could you explain this a little more? How do I implement it? Thanks

Hi

Sure.

Here you can download the required kext.
Once you have downloaded it and added+enabled in your EFI folder, you can add the boot-arg I wrote; if you need some guidance on how to add boot-arg, please refer to @CaseySJ ’s screenshot to find the exact location of boot args.
If you need further assistance, you may have to check the first page of this thread, where he explains in detail everything, step by step.

35D7696D-0381-44DD-926D-C5FEEF7B4106.png
 
Hi! So here is the update from my side:

I have followed the steps exactly as it is described in the first post, also have taken some notes from CatBus here. My setup is pretty much the same:

MOBO: Asus ProArt Creator Z690
CPU: Intel i7 13700k
Ram: Kingston FURY Beast (2 x 16GB, 6000 MHz, DDR5 RAM)
GPU: Asus RX 580 first, then installed ASUS Radeon TUF RX 6800 XT O16G GAMING
Chassis: Lian Li O11 Dynamic EVO
Bluetooth & Wifi: Fenvi T919
Audio Interface: Motu M4

BIOS version 2103
Used 7.1 MacPro in SMBIOS
Boot SSD is connected to second slot
Dual boot with Windows 11

Once again, I have used 0.8.0 version to start with, then upgraded to 0.8.3 and then upgraded to 0.8.7 manually (had to replace drivers as well). After all, installed Ventura 13.0.1. Went just very smooth almost no problems at all. I just had one problem when using RX 580, that I had to enable CSM in the BIOS for it to work.

Otherwise pretty much everything is working. Sleep was not working first, but after Venture installation even that started to work. However for some reason it is not working properly right now, a bit inconsistent. Might be the audio interface or 10 GbE Lan, or even suspecting if Asus Armoury on Win 11 side has installed something to effect it? I am not sure, however I do not mind sleep a lot anyway. Bluetooth, Wifi, Airdrop works. USB-C hot plug works.

Haven't tested Sidecar and Thunderbolt since I don't have a thunderbolt device yet.

Only problem right now is that I don't get incremental updates. I have tried the boot args CaseySJ provided, but doesn't seem to trigger anything. Probably I will just install 13.1 manually later.

Some notes
- when RX 580 was plugged in, I did not even remove agdpmod=pikera boot arg for it, just worked.
- screens were identified wrongly, so my main screen was recognized as second screen, changing cables fixed it
- XMP is off, as CatBus had a difficulty there, I experienced the same. Didn't bother just disabled it, however I don't se any big difference on boot time.
- Network devices were named strangely, but just renamed those manually.
- I first didn't like the Lian Li chassis, seemed too complex to me and so many options. Also I thought it would be loud since it is mesh on the top and back, but surprisingly it is quite silent anyway. And installation was pretty easy so yeah now I really like it especially after adding a couple of RGB fans :)

About Motu M4
- It gave me a nightmare at first. I installed the driver/extension, which caused a green & black screen and it wasn't booting anymore. It simply broke something, even USB boot or backup device didn't help. I am suspecting if it tried to install an incompatible system extension or anything similar. Or if it collided with 6800 XT somehow, because even if I removed Motu M4, it didn't boot. It was coming ok until the bootloader, then looked like booting, but right before the login screen, it was blacking out, same behaviour both on MacOS and Windows. So yeah, after many trials it finally booted, I have immediately removed Motu extension, it seems to be stable right now.

All in all I am very happy with it. Thank you again @CaseySJ for this great build and all the support!

Also a question, I am not sure if I should enable SIP now? It is same as it is in the first config I have downloaded I think.
 
Last edited:
CaseySJ one last doubt! I thought SSDTs were universal, not board specific, apart for the USB mapping one, am I wrong?
SSDTs are patches to the ACPI tables. Some are generic, but many are board specific. Some, like bridging SSDTs (SSDT-BRG0) or Thunderbolt SSDTs, are even slot-specific: Move the add-in card to another slot and you have to recompile the SSDT!
 
SSDTs are patches to the ACPI tables. Some are generic, but many are board specific. Some, like bridging SSDTs (SSDT-BRG0) or Thunderbolt SSDTs, are even slot-specific: Move the add-in card to another slot and you have to recompile the SSDT!
So, ITX mobos abandoned, can't find what I'd like. I was considering ASUS TUF Gaming Z690-PLUS D, good price point and I don't need thunderbolt, nor wifi. Starting from this thread build EFI it looks like I only need generic SSDTs, right? Can you confirm those are all not board specific:

SSDT-PLUG-ALT-Z690.aml
SSDT-AWAC.aml
SSDT-XH_ADLS3.aml
SSDT-EC-USBX-Z690.aml
SSDT-SBUS.aml
SSDT-USBW.aml
SSDT-DTPG.aml
SSDT-DMAC.aml
 
Maybe look at M-ATX boards
If it was to be different I wanted it "tiny"... at this point better to opt for an ATX and keep my modded case you see in my profile pic
 
CaseySJ one last doubt! I thought SSDTs were universal, not board specific, apart for the USB mapping one, am I wrong? Why did you say Device Paths in SSDTs as well? I have a certain experience with hackintoshes, but you never stop learning! Thanks!
A few SSDTs are universal, but most are not.
 
...

Only problem right now is that I don't get incremental updates. I have tried the boot args CaseySJ provided, but doesn't seem to trigger anything. Probably I will just install 13.1 manually later.

...

Also a question, I am not sure if I should enable SIP now? It is same as it is in the first config I have downloaded I think.
Glad to hear the build went well!

Regarding macOS updates, there are two separate factors:
  1. Getting notification that a macOS update is available
  2. Applying an "incremental" update versus "full size" update
    • Incremental update has a smaller file size
    • For macOS 13.2 the incremental file is about 910MB
    • Full update is about 12GB
If you are not receiving notification for macOS updates, then:
  • Set SecureBootModel to Default (not disabled)
  • Set csr-active-config to 00000000
If incremental macOS update is not occurring, and instead the full 12GB file is being downloaded, then:
  • Add boot-arg revpatch=auto,sbvmm,asset
  • Reboot and try again
 
Can you confirm those are all not board specific:

SSDT-PLUG-ALT-Z690.aml generic
SSDT-AWAC.aml only if the board needs it (probably all Z690)
SSDT-XH_ADLS3.aml only if the board needs it
SSDT-EC-USBX-Z690.aml Dortania's SSDT is generic… by using lots of conditional code; depends what's in this -Z690 version
SSDT-SBUS.aml probably generic for all Z690
SSDT-USBW.aml only if the board needs it
SSDT-DTPG.aml generic; NOT NEEDED if there's no Thunderbolt SSDT, or no other SSDT which relies on it
SSDT-DMAC.aml definitely board-specific… and possibly BIOS-specific!
If you do not want to investigate what your board precisely needs, go for a published User Build or Golden Build and pick the very same motherboard (CPU model is irrelevant).
 
Back
Top