Contribute
Register

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

Yes, running true 5K. I need both ports, and I need a Thunderbolt 4 compatible cable. Just does not work on mine without one.
Wonderful, thank you! My LG 5K works at true 5K (both DP ports) on my z390m board using GC-Titan Ridge. So I’ll try my existing TB cable first, but now I know where to turn if it doesn’t work on Maple Ridge.
 
Wonderful, thank you! My LG 5K works at true 5K (both DP ports) on my z390m board using GC-Titan Ridge. So I’ll try my existing TB cable first, but now I know where to turn if it doesn’t work on Maple Ridge.
Can you post a picture of how you set the cables at the back
 
Can you post a picture of how you set the cables at the back
On the z390?
It’s simple, really: the two short display port to mDP cables that come with the Titan Ridge card BOTH are used from the GPU to the Titan Ridge. Then it’s one USB-c/TB cable to the LG 5k.
In the case of the Asus z690, it would be two DP cables from the GPU to the two DP inputs on the motherboard DP ins, then one USB-c/TB from the motherboard to the monitor.
J
 
Last edited:
Question for you @dehjomz (or anyone who knows):

I just purchased this 690 board, BUT, I’m going to be purchasing a 13700k to go with it. So…..

Assuming the new board does NOT come with bios 2203/04, and I have to install the bios update via flashback just to get the board to work with 13th gen, how in the heck does one update the Intel ME first???
I would suggest to flashback to 2103. And avoid 2204 for now. The board will boot with raptor lake, but until the ME update is updated, there could be a missing m.2 slot or raptor lake may not run as intended under load.

If you have access to an existing windows installation You can then just use a windows to go installation (Use Rufus to install windows to a usb disk ) and boot windows install the ME update that corresponds to BIOS 2103.
Hello @biuti,

Some comments:
  • Auto Sleep is affected by many factors that are not obvious when looking at the sleep log. Even though sleep log may indicate coreaudiod, that does not mean the problem is with audio.
  • To check auto sleep, please try this:
    • Physically disconnect Ethernet cable from 10GbE port
    • If that alone does not help, try disabling System Preferences --> Energy Saver --> Wait for network access
  • When you say "front panel jacks are not detected" ...
    • What happens if you connect a headphone to front panel?
    • What happens if you connect a microphone to front panel?
  • Regarding Intel I225-V Ethernet:
    • Please check if VT-d is enabled in BIOS (we should enable it)
    • Also try setting device-id to F3158680 in Device Properties (see screenshot below)
  • Also perform a cold boot. If that does not help, try CMOS Reset and re-configure BIOS parameters
Aquantia AQ113C is not supported in Big Sur. It is only supported in Monterey and newer (Ventura).

Regarding fan connections -- we should connect AIO pump to CPU_OPT or AIO. But chassis and radiator fans should be connected to standard fan headers. On some boards the CPU_OPT and AIO headers are fixed at max speed, which is quite overkill for radiator and chassis fans.

View attachment 562423
The older venerable aquantia aqc107 is supported in Big Sur but the 113 needs at least Monterey
 
Nothing changes in audio interface, I cannot hear nor send through mike.
Actually the pictures were done with headphone plugged in both jacks.
  • Is the front panel audio header properly connected to motherboard?
  • Does your computer case have separate headphone and microphone jacks, or a single combo jack?
  • If you have Windows or Linux, do headphone and microphone work there?

I could have the old computer, I could try if I managed to make it run on iGPU (it should).
I deleted the file, now I have also two Thunderbolt bridges interfaces, but still only self assigned IP on the i225-V.
I will try the arg too, but I don't understand why it should work differently from any other here, it's weird.

Edit: tried, no apparent differences apart losing device name in system report
View attachment 562441
Are any third-party firewall or anti-virus applications installed?


I also have duplicated Bluetooth port, I guess after the file deletion. Should I just delete all the interfaces, delete the file again and reboot? Guess so.
View attachment 562442
I changed switch port, I will try with a different cable as well, just to be sure, but it worked since last week so I'm not really holding my breath on this.

There's only the USB key with EFI.
Should I have USBWakeFixup.kext enabled?
View attachment 562439
I have enabled both USBWakeFixup.kext and its companion SSDT-USBW.aml. But this is optional. Either way is okay.
 
  • Is the front panel audio header properly connected to motherboard?
  • Does your computer case have separate headphone and microphone jacks, or a single combo jack?
  • If you have Windows or Linux, do headphone and microphone work there?
well, I tried connecting the front audio panel of my old PC case and it wasn't working. That means I should also have been able to fail plugging it correctly twice, that I cannot exclude tho :) I will check again.
Yes, mic and headset, separated with icons.
I tried in win10 to go I used for the Intel ME FW, and plugging the headset did not change anything, but I really don't know Windows a lot, I just saw AudioHD in device manager but did not investigate too much.

I found something interesting:
Currently using line out for the speakers. If I connect the headphones to the mic in (pink, bottom left) the name of the first output interface changes to Headphones. That is the one I'm using (so related to line out) and obviously I cannot hear anything from the headphones.
If I connect the mic to the mic in port there's no signal in input. Neither in Line in.
Plugging the mic in c/sub, an input port changes name to microphone port.
So there has to be some mess in EFI.
I deleted the alcid arg (wasn't working anyway) and added 0d000000 as layout-id in device. I'll try alcid=13 and 14.

Are any third-party firewall or anti-virus applications installed?

I have LuLu. tried to quit it and exclude from running at login, also rebooting.
The problem is that disconnecting and reconnecting the cable from the network port, I'm able to get an IP, router IP and DNS, still internet is not working. Even ping does fail. I can see the connection on the router interface, everything seems ok.
I have enabled both USBWakeFixup.kext and its companion SSDT-USBW.aml. But this is optional. Either way is okay.
I will try enabling and disabling both.

I will check AudioHD port (again), and also power connection to the MB, even if I doubt anything would work if I did some mistake there.

As a last resort, tomorrow I'll try to CMOS reset and install Monterey from scratch on another disc. At least I will be able to use one of you EFI without any editing so to exclude that from the equation.
 
...

As a last resort, tomorrow I'll try to CMOS reset and install Monterey from scratch on another disc. At least I will be able to use one of you EFI without any editing so to exclude that from the equation.
I was just going to suggest this!
 
Hi @CaseySJ ! I completed the macOS installation on my new Z790 hackintosh based on your EFI smoothly. But it get stuck on this error message "ACMTRM: _startEnrollment: set TRM_EnrollmentPending = True." when I boot into macOS with Verbose mode. I also attached the Opencore log and my EFI plist. Any helps would be appreciated!

Update:
now it stuck on this error:
"ACMTRM-S: setData: saving *policy* (dataLen=49) in 3 seconds (fullSync: No -> No)."

macOS: Ventura 13.2
OpenCore: 0.8.3
Motherboard: Z790 ProArt
CPU: i9-13900K
GPU: AMD W5700
SSD: WN850 2TB
 

Attachments

  • opencore-2023-01-25-041356.txt
    256 KB · Views: 25
  • config.plist
    37.7 KB · Views: 20
Last edited:
Hi @CaseySJ ! I completed the macOS installation on my new Z790 hackintosh based on your EFI smoothly. But it get stuck on this error message "ACMTRM: _startEnrollment: set TRM_EnrollmentPending = True." when I boot into macOS with Verbose mode. I also attached the Opencore log and my EFI plist. Any helps would be appreciated!

macOS: Ventura 13.2
OpenCore: 0.8.3
Motherboard: Z790 ProArt
CPU: i9-13900K
GPU: AMD W5700
SSD: WN850 2TB
I have same hardwares as you except the graphic. My graphic card is AMD RADEON RX 6800XT. I have successfully installed。Everything seems OK。I'm out, I will attach EFI Later.
 
I have same hardwares as you except the graphic. My graphic card is AMD RADEON RX 6800XT. I have successfully installed。Everything seems OK。I'm out, I will attach EFI Later.

Thanks for your reply. Which macOS did you installed?
Hoping to test your EFI soon.
 
Back
Top