Jump to content

[GUIDE] Gigabyte Z690 AORUS ULTRA & i7-12700KF & AMD RX 6600 [Mojave] [Monterey] [Ventura] [Sonoma]

verdazil

By verdazil,
in Installation Guides

 Share
19 posts in this topic

Recommended Posts

verdazil
verdazil
Posted
Posted (edited)

[GUIDE] Gigabyte Z690 AORUS ULTRA & i7-12700KF & AMD RX 6600 [Monterey] [Ventura] [Sonoma]

 

•    Guide using OpenCore 0.8.6 for macOS Monterey & Ventura
•    BIOS basic settings
•    EFI folder available
•    macOS installation procedure is standard and is not covered here.

 

Hardware

•    Motherboard: Gigabyte Z690 AORUS ULTRA (rev. 1.0)
•    CPU: Intel® Core™ i7-12700KF
•    Memory: Kingston FURY, KF560C32RSK2-32, DDR5-6000 CL32-38-38 @1.35V
•    Video: SAPPHIRE PULSE AMD Radeon RX 6600
•    Monitor: BENQ-BL2711U + LG TV 42LF650V
•    Ethernet: Intel® 2.5GbE LAN chip I225-V (Built-in)
•    WiFi: Intel® Wi-Fi 6 AX200 (Built-in)
•    Bluetooth: Intel® BLUETOOTH 5.2 (Built-in)
•    NVMe: M.2, PCIe 4.0, Netac, 1 Tb + M.2, PCIe 3.0, Samsung 970 EVO 250 Gb
•    HDD: Western Digital, 2 Tb

 

macOS & OpenCore version

•    macOS Monterey, 12.6.1 (21G217), macOS Ventura, 13.0.1 (22A400)
•    OpenCore 0.8.6


Some important BIOS settings 
BIOS version F20 [03.11.2022]

•    CFG Lock: Disabled
•    CSM: Disabled
•    VT-d: Disabled
•    Fast Boot: Disable Link
•    Above 4G Decoding: Enabled
•    Windows 10 Features: Windows 10
•    XHCI Hand-Off: Enabled
•    IO APIC 24-119 Entries: Enabled
•    Legacy USB Support: Enabled
•    USB Mass Storage Support: Enabled
•    Intel Platform Trust Technology (PTT): Enabled
•    Security Device Support: Disabled
•    Network Stack: Disabled
•    Secure Boot: Disabled
•    Enable VMD controller: Disabled
•    Initial Display Output: PCIe 1 Slot

 

OpenСore settings and EFI files

You can use settings and files from my EFI for installation and daily work in macOS. During installation, use the following specific settings in config.plist:
•    SecureBootModel = Default
•    SIP enabled (csr-active-config=00000000)
After installation, you can change them depending on the third-party software you are using and other circumstances. Please read the Notes at the end of this post carefully.


What works?
All PC devices and Apple technologies work properly in Monterey. See below about Ventura.

 

What does not work?
Bluetooth works well in Monterey, but BlueToolFixup.kext needed for it to work, can sometimes lead to random stuck when the system is rebooted or the computer is turned off. You can disable Bluetooth (deactivate BlueToolFixup.kext, IntelBluetoothFirmware.kext and IntelBTPatcher.kext in config.plist) or tolerate this disadvantage. Bluetooth does not work in Ventura. I hope the developers will fix this in the upcoming BlueToolFixup.kext releases. 

 

Some tests

 

image.thumb.png.d4087245d64d30de1d4f0c38ecc420cb.pngimage.thumb.png.f7f52fb7d03d8c632ced44bb6a6f12cf.pngimage.thumb.png.ee83630063f58e167f30028567442899.pngimage.thumb.png.6a58d0b4146a3a936a9409a23288f008.png

Credits

 @Slice for personal assistance and support

Acidanthera: OpenCore and kexts
Dortania: OpenCore guides.
 

Notes:

•    About macOS Ventura. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600/?do=findComment&comment=2797479

•    About macOS Sonoma. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600-monterey-ventura/?do=findComment&comment=2812278

•    About macOS Mojave. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600-monterey-ventura-sonoma/?do=findComment&comment=2827087

 

•   About macOS Monterey:

 

•    USBMap.kext in my EFI is individual. I used F_USB1 and F_U32 Motherboard Internal Connectors. You may need to edit or replace it if you are using a different connector on your motherboard or want to use another Mac-model in Platforminfo --> Generic. If you edit mine or create a new one USBMap.kext, don't forget that the Audio device, ITE device and Bluetooth device works over the USB and require separate ports to work (ports HS04, HS13, HS14). Unfortunately, this reduces the number of USB ports available (15-3=12).
•    CPUFriendDataProvider.kext in my EFI is CPU i7-12700K(KF) specific. Do not use it for other CPU models.
•    You must insert your own SeralNumber & MLB & ROM & SystemUUID in the config.plist file.
•    I225-V Ethernet controller works without additional kext in Monterey, only need device-id replacement in the config.plist section DeviceProperties --> Add. Note that the settings in this section are individual. Leave only those that match your hardware.
•    If you do not have a 4k monitor, you must replace (for the corresponding screen resolution) or just delete the file /EFI/OC/Resources/Image/Acidanthera/GoldenGate/Background.icns
•    Don't forget to reset NVRAM after changing OpenCore settings.
•    My CPU and memory are both overclocked and stable, but this guide does not discuss this due to the variation in the physical characteristics of each individual piece of hardware.
•    I haven't noticed any significant benefits when using MacPro7,1 Mac-model instead of iMacPro1,1

My EFI folder for Monterey:

https://drive.google.com/file/d/1kILvTfn-cA6s4FFTZL_1lUhHwPIN2R53/view?usp=sharing

 

 

Edited by verdazil
  • Like 8
  • Thanks 3
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted (edited)

Now macOS Ventura too!

 

1. To work Intel I225-V controller in Ventura you need to add the .kext version of the AppleIntel210Ethernet driver.

 

2.  itlwm Wi-Fi driver for Ventura is currently in alpha version. However, it works correctly on my hardware.

 

3. Motherboard native Bluetooth does not yet work in Ventura. I hope the developers keep working.


Everything is in the new version of my EFI for Ventura, which you can download from the link below.

 

https://drive.google.com/file/d/1rEb9b4OOhmH1cvNS4zpfuDUW-krP3LKU/view?usp=sharing

Edited by verdazil
  • Like 2
Link to comment
Share on other sites
tony955
tony955
Posted
Posted
On 11/18/2022 at 7:17 PM, verdazil said:

[GUIDE] Gigabyte Z690 AORUS ULTRA & i7-12700KF & AMD RX 6600 [Monterey] [Ventura]

 

•    Guide using OpenCore 0.8.6 for macOS Monterey & Ventura
•    BIOS basic settings
•    EFI folder available
•    macOS installation procedure is standard and is not covered here.

 

Hardware

•    Motherboard: Gigabyte Z690 AORUS ULTRA (rev. 1.0)
•    CPU: Intel® Core™ i7-12700KF
•    Memory: Kingston FURY, KF560C32RSK2-32, DDR5-6000 CL32-38-38 @1.35V
•    Video: SAPPHIRE PULSE AMD Radeon RX 6600
•    Monitor: BENQ-BL2711U + LG TV 42LF650V
•    Ethernet: Intel® 2.5GbE LAN chip I225-V (Built-in)
•    WiFi: Intel® Wi-Fi 6 AX200 (Built-in)
•    Bluetooth: Intel® BLUETOOTH 5.2 (Built-in)
•    NVMe: M.2, PCIe 4.0, Netac, 1 Tb + M.2, PCIe 3.0, Samsung 970 EVO 250 Gb
•    HDD: Western Digital, 2 Tb

 

macOS & OpenCore version

•    macOS Monterey, 12.6.1 (21G217), macOS Ventura, 13.0.1 (22A400)
•    OpenCore 0.8.6


Some important BIOS settings 
BIOS version F20 [03.11.2022]

•    CFG Lock: Disabled
•    CSM: Disabled
•    VT-d: Disabled
•    Fast Boot: Disable Link
•    Above 4G Decoding: Enabled
•    Windows 10 Features: Windows 10
•    XHCI Hand-Off: Enabled
•    IO APIC 24-119 Entries: Enabled
•    Legacy USB Support: Enabled
•    USB Mass Storage Support: Enabled
•    Intel Platform Trust Technology (PTT): Enabled
•    Security Device Support: Disabled
•    Network Stack: Disabled
•    Secure Boot: Disabled
•    Enable VMD controller: Disabled
•    Initial Display Output: PCIe 1 Slot

 

OpenСore settings and EFI files

You can use settings and files from my EFI for installation and daily work in macOS. During installation, use the following specific settings in config.plist:
•    SecureBootModel = Default
•    SIP enabled (csr-active-config=00000000)
After installation, you can change them depending on the third-party software you are using and other circumstances. Please read the Notes at the end of this post carefully.


What works?
All PC devices and Apple technologies work properly in Monterey. See below about Ventura.

 

What does not work?
Bluetooth works well in Monterey, but BlueToolFixup.kext needed for it to work, can sometimes lead to random stuck when the system is rebooted or the computer is turned off. You can disable Bluetooth (deactivate BlueToolFixup.kext, IntelBluetoothFirmware.kext and IntelBTPatcher.kext in config.plist) or tolerate this disadvantage. Bluetooth does not work in Ventura. I hope the developers will fix this in the upcoming BlueToolFixup.kext releases. 

 

Some tests

 

image.thumb.png.d4087245d64d30de1d4f0c38ecc420cb.pngimage.thumb.png.f7f52fb7d03d8c632ced44bb6a6f12cf.pngimage.thumb.png.ee83630063f58e167f30028567442899.pngimage.thumb.png.6a58d0b4146a3a936a9409a23288f008.png

Credits

 @Slice for personal assistance and support

Acidanthera: OpenCore and kexts
Dortania: OpenCore guides.
 

Notes:

•    About macOS Ventura. See: https://www.insanelymac.com/forum/topic/354826-guide-gigabyte-z690-aorus-ultra-i7-12700kf-amd-rx-6600/?do=findComment&comment=2797479
•    USBMap.kext in my EFI is individual. I used F_USB1 and F_U32 Motherboard Internal Connectors. You may need to edit or replace it if you are using a different connector on your motherboard or want to use another Mac-model in Platforminfo --> Generic. If you edit mine or create a new one USBMap.kext, don't forget that the Audio device, ITE device and Bluetooth device works over the USB and require separate ports to work (ports HS04, HS13, HS14). Unfortunately, this reduces the number of USB ports available (15-3=12).
•    CPUFriendDataProvider.kext in my EFI is CPU i7-12700K(KF) specific. Do not use it for other CPU models.
•    You must insert your own SeralNumber & MLB & ROM & SystemUUID in the config.plist file.
•    I225-V Ethernet controller works without additional kext in Monterey, only need device-id replacement in the config.plist section DeviceProperties --> Add. Note that the settings in this section are individual. Leave only those that match your hardware.
•    If you do not have a 4k monitor, you must replace (for the corresponding screen resolution) or just delete the file /EFI/OC/Resources/Image/Acidanthera/GoldenGate/Background.icns
•    Don't forget to reset NVRAM after changing OpenCore settings.
•    My CPU and memory are both overclocked and stable, but this guide does not discuss this due to the variation in the physical characteristics of each individual piece of hardware.
•    I haven't noticed any significant benefits when using MacPro7,1 Mac-model instead of iMacPro1,1

 

My EFI folder for Monterey:

https://drive.google.com/file/d/1kILvTfn-cA6s4FFTZL_1lUhHwPIN2R53/view?usp=sharing

 

 

hi, can you tell me if  CPUFriendDataProvider.kext is ok from my cpu i7-12700 thanks and congratulations.

Link to comment
Share on other sites
tony955
tony955
Posted
Posted
51 minutes ago, miliuco said:

@tony955

 

Please add a signature to your user profile. Thanks.

Ok Thanks, sorry but I'm impractical

Thanks, you are very kind

2 hours ago, verdazil said:

No, mine CPUFriendDataProvider.kext doesn't suit you. Try the kext from the attachment.

CPUFriendDataProvider.kext.zip 4.68 kB · 1 download

Thanks, you are very kind

  • Like 1
Link to comment
Share on other sites
  • 6 months later...
verdazil
verdazil
Posted
  • Author
Posted

Bluetooth work now in Ventura!

 

- Intel® Bluetooth AX200 (Gigabyte Z690 AORUS ULTRA, rev. 1.0 motherboard)

- Ventura 13.4 (22F66)

- OpenCore 0.9.2

 

Kexts BlueToolFixup.kext, IntelBluetoothFirmware.kext,  IntelBTPatcher.kext and additional NVRAM settings are used.

See settings in attached file.

bluetooth-config.plist.zip

  • Like 1
Link to comment
Share on other sites
  • 4 months later...
verdazil
verdazil
Posted
  • Author
Posted (edited)

About macOS Sonoma 14.0

 

- BIOS updated to F27 version

- OpenCore version 0.9.5

- I225-V Ethernet controller works with AppleIGC.kext and e1000=0 bootarg

- AppleALC.kext has been slimmed (86 kb vs 4 Mb original) to work only with the ALC897 audio codec, alcid=77 bootarg

- For SAPPHIRE PULSE AMD Radeon RX 6600 used SoftPowerPlayTable (slight performance limitation and Zero RPM keeps fans stopped until 60º)

- Everything else works stably the same as in previous macOS versions Monterey and Ventura. Of course, all kexts are updated to the latest release versions.

- Kexts for bluetooth operation are disabled in the config. Bluetooth can work, but I don’t need it.

- My EFI folder for macOS Sonoma 14.0: https://drive.google.com/file/d/1Er5cHHPYEvt3EKySOQkS8oeGo-nEars8/view?usp=sharing

Edited by verdazil
  • Like 2
Link to comment
Share on other sites
  • 5 months later...
verdazil
verdazil
Posted
  • Author
Posted

About macOS Sonoma 14.4

 

- BIOS updated to F28 version

- OpenCore version 0.9.9

- All kexts latest release versions (but Sonoma 14.4 needs latest alfa-version of AirportItlwm.kext)

 

After updating the system to version 14.4, an unpleasant problem appeared. When booting the system (cold or hot), a kernel panic sometimes occurs. Panic occurs within 1-3 seconds after the apple logo appears. At the same time, there is no information left in the system log about the causes of the panic. Rarely does the system boot immediately. Most often, 1-2-3... panics occur in a row, before the system boots normally. The system never provides any warning messages after booting.

A non-obvious solution to this problem has been found: you need to add latest release version CpuTscSync.kext

Now the system works perfectly.

  • Like 2
Link to comment
Share on other sites
  • 1 month later...
verdazil
verdazil
Posted
  • Author
Posted

A little more about Sonoma macOS 14.4

 

1. Starting from version Sonoma macOS 14.4 (including all 14.5 betas), if I restart the computer, the power to the HDD hard drives is turns off. Then, during the BIOS POST, power is turned on to the disks and they spin up one by one. This means longer reboot time, increased disk wear, and simply incorrect behavior. I couldn't solve this problem, so I'm staying with the version Sonoma macOS 14.3.1. To be fair, it must be said that all the machines (with different motherboards and CPUs of different generations) on which I updated the MacOS version to 14.4 or later behave this way. Apparently it's not a Hackintosh problem, it's a MacOS problem.

 

2. I slightly changed the hardware configuration of my machine (replaced one of the hard drives) and ran into others problems with reboot and shutdown. 
- When rebooting, it sometimes freezes, forcing me to shut down the computer completely. Sometimes it is enough to wait 30-40 seconds and the reboot occurs. When turning off the computer, sometimes I need to wait 30-40 seconds or hold down (4 sec) the Power button. 
- When the system boots, sometimes a kernel panic occurs.
These problems are related to incorrect memory allocation. The solution can be obtained by carefully following this manual:
https://dortania.github.io/OpenCore-Install-Guide/extras/kaslr-fix.html#so-what-is-kaslr
The important feature here is that there is no universal solution and everyone must individually carry out this work for their own hardware.

I would supplement this guide (kaslr-fix) with the following clarification. After you receive our own MmioWhitelist, do not use it mechanically, i. e. entirely. From this list you need to remove those items that prevent normal booting. Unfortunately, this can only be done manually, carefully selecting suitable positions and deleting unsuitable ones.

  • Like 2
Link to comment
Share on other sites
  • 3 months later...
verdazil
verdazil
Posted
  • Author
Posted (edited)

USB settings for Gygabyte Z690 AORUS ULTRA

 

1. I used F_USB1 and F_U32 Motherboard Internal Connectors.

2. To avoid exceeding the port limit (15), ports SS03 and HS14 are not defined in USBMap.kext. You can add any of them at the expense of some other port.

3. Please note that the USB controller device name in the USBMap.kext is ХHС. If yours is different, you need to apply the binary ACPI DSDT patch - renaming XHCI to XHC.

4. Please note that in other used SSDT tables you may also need to rename XHCI  to XHC

image.thumb.png.ef16bc836dda0fc0cafbafbea2c7cbc9.pngUSBMap.kext.zip USB-Map.plist.zip

HXCI-to-XHC.plist.zip

Edited by verdazil
  • Like 2
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted

I recommend using BIOS F29e firmware. This is the first firmware in which I do not have the problem with the computer freezing when turning off or rebooting.

  • Like 3
Link to comment
Share on other sites
  • 2 months later...
verdazil
verdazil
Posted
  • Author
Posted

Gigabyte has removed from its website BIOS F29e firmware.

In my opinion, the final version of BIOS for this motherboard is F29 firmware, Sep 27. 2024.

After flashing this version, all problems were completely solved. All devices and technologies work correctly, including sleep/wake.

  • Like 1
Link to comment
Share on other sites
verdazil
verdazil
Posted
  • Author
Posted (edited)

Successfully installed macOS Mojave 10.14.6

 

What does not work?

- LAN (There is no support for I225-V LAN in Mojave without reflashing the controller)

- Graphic acceleration (The AMD RX 6600 video card is supported starting from macOS Monterey 12.2)

 

EFI folder (OpenCore V. 1.0.2): https://drive.google.com/file/d/1gC6EQBLaP5fb0TUbIbqjHI1Kgas84QFp/view?usp=sharing

Edited by verdazil
Link to comment
Share on other sites
  • 3 weeks later...
Majonéz
Majonéz
Posted
Posted
On 4/29/2024 at 7:34 AM, verdazil said:

A little more about Sonoma macOS 14.4

 

1. Starting from version Sonoma macOS 14.4 (including all 14.5 betas), if I restart the computer, the power to the HDD hard drives is turns off. Then, during the BIOS POST, power is turned on to the disks and they spin up one by one. This means longer reboot time, increased disk wear, and simply incorrect behavior. I couldn't solve this problem, so I'm staying with the version Sonoma macOS 14.3.1. To be fair, it must be said that all the machines (with different motherboards and CPUs of different generations) on which I updated the MacOS version to 14.4 or later behave this way. Apparently it's not a Hackintosh problem, it's a MacOS problem.

 

Hi,
Have you found a solution to this since then?
The 15.2 still has the same behavior.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...