Ohchang's build: Gigabyte Z590 Vision G + i7-10700K + AMD RX580

UtterDisbelief · Mar 27, 2023

loopatic said:
Ok i found it..
Thanks..
It's better for me to use the last EFI attached folder for MacOS Monterey fresh installation???

I have these issues on OCC and when I chose boot from usb to begin the installation

Those errors show you that there is a mismatch between the version of OpenCore you are using the version your config.plist was originally written for.

Make sure the version of OpenCore Configurator app is the correct one for the version of OpenCore you are using. Load your new config.plist, make a small change, Save, then change it back and Save again. This will reformat the config.plist correctly.

root2 · Mar 29, 2023

Since the activation of AppleVTD I can no longer dualboot my Windows 10 using OpenCore. Instead, I need to press F12 and change the boot device. Is there any fix for that? For example, can I buy a USB-C network card (like the AX88179A) and just disable the Intel i225-V in the UEFI and be done with it (needing AppleVTD)?

Or can this be a solution? (inject AppleIntelI210Ethernet.kext from Monterey) - Tried this method, I get an IP, but cannot ping. So my current solution is a USB-C network card based on the AX88179A chipset.

ohchang · Apr 21, 2023

Mini guide - EFI for Z590 Vision G Ver 0.8 update for Ventura

I didn't test in Ventura 13.3.x or newer cuz there are critical problems in Unicode(like Korean) NFD/NFC related issue.
This guide works well under Ventura 13.2.1(22D68).

1. Freezing and stuttering after Ventura 13.x update

→ Force to use injected KEXT driver(from Monterey) for Intel i225-V, These settings are not affect to WiFi/BT at all

* If you already updated to Ventura then freeze after boot-up, just un-plug ethernet cable.

No custom firmware,
No VT-D related settings like SSDT-DMAR.aml,
No Ethernet hardware setting manually.

- Custom firmware
I don't prefer custom firmware. Just so, I didn't try this solution.

- SSDT-DMAR.aml injection and related settings
I tested various solutions multiple times, but it does not work with Z590 Vision G. Freezing, stuttering, and stuck still appear.

[Procedure - DO NOT skip any step]

- Use Device properties same as Ver 0.7(same as below, device-id: F31588680)
device-id F2150000/F3150000 does not work at all, even with the Kernel patch.

Code:

            <key>PciRoot(0x0)/Pci(0x1B,0x2)/Pci(0x0,0x0)</key>
            <dict>
                <key>device-id</key>
                <data>
                8xWGgA==
                </data>
                <key>device_type</key>
                <string>Ethernet Controller</string>
                <key>model</key>
                <string>Intel Ethernet Controller I225-V 2.5GbE</string>
            </dict>

- Add AppleIntelI210Ethernet.kext(ver 2.3.1 From Monterey or Bigsur) to the KEXT folder and config.plist also

- Add e1000=0 to boot-args in config.plist

- Set Ethernet hardware setting to Auto. There is no need to enable VT-d in BIOS (or disable DisableIoMapper in Kernel Quirks).

2. Not working FCPX/Compressor or H/W acceleration failure after the Ventura update

→ Edit IGPU Device properties(update later)

After the update to the Ventura, Apple/Adobe Pro apps do not work well. Even H/W acceleration failures occur frequently. Maybe something changed in the MacOS iGPU acceleration process.

[Procedure]
- Change Device properties like as below

Code:

            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Slot-0</string>
                <key>enable-metal</key>
                <data>
                AQAAAA==
                </data>
                <key>rps-control</key>
                <data>
                AQAAAA==
                </data>
            </dict>

- This setting is incomplete but works well. (Export speed 10~20% slower than v0.7)

DONE!

Please refer to my github or attached file v0.8
Thanks

root2 · Apr 24, 2023

Welcome back @ohchang. :headbang:

We were seriously worried about you. :wave:

ohchang · Apr 24, 2023

root2 said:
Welcome back @ohchang. We were seriously worried about you.

I recommend the above new way to set the Ethernet setting(without Apple VT-d); maybe it won't bother to boot with Windows.

root2 · Apr 26, 2023

I have seen it, thanks. I updated to OpenCore 0.9.1, macOS Ventura 13.3 (22E252), iMacPro1,1, BIOS F7b, AppleIntelI210Ethernet.kext 2.3.1 (downloaded from the Internet; Dated: Feb. 26, 2022; md5sum: 96e610a84ce38be006f4dde9109149b1).

The system is not crashing, I managed to get an IP from my router but I cannot browse the Web nor ping a host on the network. Similar to my previous attempts.

ping www.google.com - no response
ping 8.8.8.8 - no response
ping 192.168.0.1 (my router) - no response

Once I switch over to Wi-Fi all of that works. Ideas?

Edit: Okay, I found a solution. I enforced a speed (1Gbps), aka disabled auto-negotiation. It did not work on the first attempt, but I switch back and forth multiple times, and then it eventually started to work, for whatever reason. I also booted into Windows, there, everything works out-of-the-box, even auto-negotiation, then back to macOS, ping works now

Thank you.

root2 · Oct 17, 2023

Updated to BIOS F8 (because I'm an idiot) now encountering random crashes. The error messages are hinting toward NVMe again.

Code:

panic(cpu 0 caller 0xffffff8007c1c81e): nvme: "3rd party NVMe controller. Loss of MMIO space. Write. fBuiltIn=1 MODEL=WDS100T1X0E-00AFY0 FW=613200WD CSTS=0xffffffff US[1]=0x0 US[0]=0x169 VID=0x15b7 DID=0x5011 CRITICAL_WARNING=0x0.\n" @IONVMeController.cpp:6147
Panicked task 0xffffff9539dc7bf8: 177 threads: pid 0: kernel_task
Backtrace (CPU 0), panicked thread: 0xffffff95392aa598, Frame : Return Address

      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[D6B20D06-8D30-36EF-930A-378AFC969811]@0xffffff8007c14000->0xffffff8007c40fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[113550EC-8AB4-3E71-A39B-4C9E4FD16720]@0xffffff80069fd000->0xffffff8006a30fff
            dependency: com.apple.iokit.IOPCIFamily(2.9)[F11A1D9C-398D-3933-94D6-9539D3B7B1FD]@0xffffff8007eac000->0xffffff8007eddfff
            dependency: com.apple.iokit.IOReportFamily(47)[491DDA55-D371-3A28-9A77-C28DB013D8AE]@0xffffff8007eee000->0xffffff8007ef0fff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[70B6B0B8-8059-3529-A544-D33C65534409]@0xffffff8007fe1000->0xffffff8007ff8fff

Process name corresponding to current thread (0xffffff95392aa598): kernel_task
Boot args: agdpmod=pikera e1000=0

Mac OS version:
22G120

Kernel version:
Darwin Kernel Version 22.6.0: Fri Sep 15 13:39:52 PDT 2023; root:xnu-8796.141.3.700.8~1/RELEASE_X86_64

Edit: Downgraded to BIOS F7, crashes still occur.

Edit2: Downgraded to BIOS F6, looks like everything is working fine.

rjlian · Oct 28, 2023

root2 said:
I have seen it, thanks. I updated to OpenCore 0.9.1, macOS Ventura 13.3 (22E252), iMacPro1,1, BIOS F7b, AppleIntelI210Ethernet.kext 2.3.1 (downloaded from the Internet; Dated: Feb. 26, 2022; md5sum: 96e610a84ce38be006f4dde9109149b1).

The system is not crashing, I managed to get an IP from my router but I cannot browse the Web nor ping a host on the network. Similar to my previous attempts.

Once I switch over to Wi-Fi all of that works. Ideas?

Edit: Okay, I found a solution. I enforced a speed (1Gbps), aka disabled auto-negotiation. It did not work on the first attempt, but I switch back and forth multiple times, and then it eventually started to work, for whatever reason. I also booted into Windows, there, everything works out-of-the-box, even auto-negotiation, then back to macOS, ping works now Thank you.

After restarting, the monitor has no signal. I used the AMD RX6600 instead of AMD RX 580. Is there any way to solve this problem? Note: in 'boot-arts', I have added parameters: agdpmod=pikera. My CPU is i9 10900K rather than i7 10700K. BIOS is F8.

rjlian · Oct 29, 2023

ohchang said:
I recommend the above new way to set the Ethernet setting(without Apple VT-d); maybe it won't bother to boot with Windows.

In OpenCore 0.9.1, Ventura 13.6.1. F8 BIOS. After replacing RX580 with RX6600, no signal appears on the monitor. Is there any solution?

CaseySJ · Oct 29, 2023

rjlian said:
In OpenCore 0.9.1, Ventura 13.6.1. F8 BIOS. After replacing RX580 with RX6600, no signal appears on the monitor. Is there any solution?

Does this mean no BIOS splash screen either? No OpenCore boot menu?

Have you tried CMOS Reset?

Search

Ohchang's build: Gigabyte Z590 Vision G + i7-10700K + AMD RX580

UtterDisbelief

Moderator

root2

ohchang

root2

ohchang

root2

Attachments

root2

rjlian

rjlian

CaseySJ

Moderator

Forum

Guides

Downloads