Contribute
Register

ASUS PRIME Z690-P D4 LGA I9 12900K AMD 6900XT install and support thread

Status
Not open for further replies.
Could I get your input on my BIOS settings (for my ASUS TUF GAMING Z690-PLUS WIFI D4 mentioned above)? I'm still trying to get my installer to boot despite spend the last couple of evenings trying to figure out the source of the ACPI errors I'm getting, and I'd like to at least ensure there's one less potential source of problems. I've attached a fairly complete copy of my current BIOS settings in a text file with a few notes at the top. The current settings are largely based on what was posted on page 1 of this thread (by Middleman) with only a few notable differences such as VT-d being enabled and having my Primary Display set to Auto.

As noted in the file, I'm particularly concerned about the ASPM related Platform Misc. Config settings (and the few other settings that I can't find an equivalent for in my BIOS).

Thanks for your help!
 

Attachments

  • ASUS Tuf Gaming Z690-Plus WIFI D4 BIOS settings.pdf
    66.3 KB · Views: 131
Could I get your input on my BIOS settings (for my ASUS TUF GAMING Z690-PLUS WIFI D4 mentioned above)? I'm still trying to get my installer to boot despite spend the last couple of evenings trying to figure out the source of the ACPI errors I'm getting, and I'd like to at least ensure there's one less potential source of problems. I've attached a fairly complete copy of my current BIOS settings in a text file with a few notes at the top. The current settings are largely based on what was posted on page 1 of this thread (by Middleman) with only a few notable differences such as VT-d being enabled and having my Primary Display set to Auto.

As noted in the file, I'm particularly concerned about the ASPM related Platform Misc. Config settings (and the few other settings that I can't find an equivalent for in my BIOS).

Thanks for your help!
Have you had a look at CaseySJ's Asus Z690ProArt build here? Perhaps you can refer to it for guidance. He also has most the BIOS settings listed (you have to click Firmware BIOS settings screenshots link).
> https://www.tonymacx86.com/threads/...hunderbolt-4-i7-12700k-amd-rx-6800-xt.318311/

I would advise also the use of CPUFriend & CPUFriendData for Z690. For Monterey 12.3 also disable XHCIPortLimit, enable AdviseWindows under PlatformInfo, try to use SSDT-UIAC plus USBInjectall OR SSDT-UIAC plus custom USBMap.
 
Have you had a look at CaseySJ's Asus Z690ProArt build here? Perhaps you can refer to it for guidance. He also has most the BIOS settings listed (you have to click Firmware BIOS settings screenshots link).
> https://www.tonymacx86.com/threads/...hunderbolt-4-i7-12700k-amd-rx-6800-xt.318311/

I would advise also the use of CPUFriend & CPUFriendData for Z690. For Monterey 12.3 also disable XHCIPortLimit, enable AdviseWindows under PlatformInfo, try to use SSDT-UIAC plus USBInjectall OR SSDT-UIAC plus custom USBMap.
Thanks, I took a look at the post and tried to both minimize my initial SSDT and kext selection and was able to get my system to finally boot to the installer and install Monterey. I think a big part of the issue I was having is that my board does not have the option to disable CFG-Lock in the bios and I did not have both of the CfgLock Quicks selected in Kernel->Quirks.

So now I just need to go through the list and work to get all of the post-install stuff up and running.
 
Thanks, I took a look at the post and tried to both minimize my initial SSDT and kext selection and was able to get my system to finally boot to the installer and install Monterey. I think a big part of the issue I was having is that my board does not have the option to disable CFG-Lock in the bios and I did not have both of the CfgLock Quicks selected in Kernel->Quirks.

So now I just need to go through the list and work to get all of the post-install stuff up and running.
That's great! At least you finally nailed what the issue was. It's always good to know. :thumbup:

Have fun with your machine too! It's going to be one of the fastest around.
 
yes no option for cfg-lock on the Asus tuf z690 but
Screenshot 2022-05-01 at 12.55.18.png
I think its unlocked because I don't need any kernel quirks
 
Huh. Well my board definity had it locked. I checked by running ControlMsrE2.efi from the EFI shell and it said as much. (Incidentally, this held true for the original 0707 Bios I was running and the 1404 Bios I updated to as I was trying to get things working.) After following the instructions on Dortania's Open Core post install for turning off CFG-Lock manually in the Bios, I was able to uncheck the two CfgLock Quicks and boot without them. But I had to perform the unlock operation first.

I can only assume that despite being nearly the same that my Plus Wifi D4 board is just different enough from your Plus D4.

Of course, I now have other things to figure out. So far I've determined that sleep isn't working correctly, nor are all of my USB ports. I also have some weird problem (possibly USB related) with my Logitech mouse where the user assigned buttons stop working (and sometimes the scroll wheel), which I haven't been able to fix without rebooting.

Regarding my USB ports, I'm having trouble figuring out how to map them. One thing in particular that confused me is that several ports were showing as USB2 HSXX when populated with a USB3 flash drive. Furthermore, the Dortania guide seems to be out of date, and the current instructions for USBMap are a little too sparse, since when I tried following them I ended up with a NO working USB ports. If anyone can suggest a better documented/more thorough guide that will work with Monterey please let me know.
 
As a quick followup, to see if any one knows, when using the USBmap.kext, you can/should disable the SSDT-UIAC, USBInjectAll, and XhciPortLimit, is that correct?
 
Last edited:
As a quick followup, to see if any one knows, when using the USBmap.kext, you can/should disable the SSDT-UIAC, USBInjectAll, and , is that correct?
"Should" According to USBmap developer, USBmap works on its own.

USBInjectAll is a form of SSDT-UIAC—it includes a version of SSDT-UIAC to enable as many ports as possible: 26 max per root controller (root means appears as PCIe).

From what I've gleaned, SSDT-UIAC is an early approach that used to come in two forms, an inject-all form and a user edited custom form. As approaches advanced, the all form got packaged into USBInjectAll to make other approaches work, like Hackintool.

XhciPortLimit quirk is an odd bit of config I don't understand and haven't yet come across its history. Anyway it should be FALSE, which means "do not unlimit" (a double negative) to whatever effect and for whatever purpose OpenCore has about this quirk. Here's what the OC documentation says about it:

22. XhciPortLimit
Type: plist boolean
Failsafe: false
Requirement: 10.11 (not required for older)
Description: Patch various kexts (AppleUSBXHCI.kext, AppleUSBXHCIPCI.kext, IOUSBHostFamily.kext) to
remove USB port count limit of 15 ports.
Note: This option should be avoided whenever possible. USB port limit is imposed by the amount of used bits in
locationID format and there is no possible way to workaround this without heavy OS modification. The only valid
solution is to limit the amount of used ports to 15 (discarding some). More details can be found on AppleLife.r

USBmap includes an inject-all function: your setup run makes an inject-all form, called a dummy USBmap.kext
A. You boot with the dummy
B. Verify you can detect all the port instances you are going to want
C. Edit dummy to eliminate unneeded with another helper program if you can find everything and boot again
D. Discover all for final map and set types
E. Create and install the final map.

'B' is done only if needed (most won't) to get all the ports you care about visible under the Mac ACPI ceiling of 26.

So there's two levels of editing: Edit dummy (inject-all form) to show you care about limited to 26 per root, then another edit to get to the final working map which which is limited to 15 instances per root. If you don't get to 15 or fewer your config will be unstable.

A port instance is a speed personality such as HS vs SS. or one of the two orientations of a non-switched Type-C connector. A pair of instances that belong to the same physical port are termed companions. You don't need to enable both companions, you can choose as you like. A port's type is determined by the connector module. For example, a port that is served by a board header should be typed according to whatever module you connect to the header. "Internal" is for onboard components like sound and LED controllers, or onboard fan-out controllers.

USB tunneled by Thunderbolt doesn't pertain to mapping, that's it's own world.

I'm not sure about this last part:

I think boards with TB have their Type-C ports served by a root USB controller when a USB device is connected.

Ports for USB controllers that hang from a root aren't limited and don't figure for mapping.

Root is a term I made up that expresses where the controller appears in the ACPI tree under the obseration that the config in question appears as a PCI entity. This is a subject with important factors I don't understand.

USBmap calls them "IOKitPersonalities" but in essennce they are controllers. The devil is in the circuit designs which I have never studied.

hth
 
confirmed cfglock is locked on tuf z690.success unlocked with modGRUBShell. setup_var_cv CpuSetup 0x44 0x01 0x00 Bios 1404
 
Last edited:
Would anyone know if the Z690 chipset and/or the intel processor i9-12900k is being used on the latest iMac or MacPro?
 
Status
Not open for further replies.
Back
Top