Contribute
Register

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

Joined
Mar 5, 2021
Messages
40
Motherboard
GIGABYTE Z590 Vision-G
CPU
10700K
Graphics
RX580
I was able to fix the issue by changing:

XML:
<key>iMac20,2-XHCI</key>
and
XML:
<string>iMac20,2</string>

in Info.plist in the USBPorts.kext to

XML:
<key>iMacPro1,1-XHCI</key>
and
XML:
<string>iMacPro1,1</string>

to match my SMBios, and now everything is working just fine! Thanks!

Good, matching the SMBIOS has been always important ;)
 
Joined
Dec 12, 2011
Messages
87
Motherboard
GIGABYTE Z590 Vision G
CPU
i7-11700K
Graphics
RX 6700 XT & RX 560
Mobile Phone
  1. iOS
Thanks for all the help! :clap:

I found a tiny issue: In line 1010-1011 in OpenCore's conflig.plist should be changed from

XML:
<key>CustomDelays</key>
<string>Auto</string>

to

XML:
<key>CustomDelays</key>
<false/>

Source: https://dortania.github.io/docs/latest/Configuration.html#x1-700008
Screenshot 2021-05-12 at 11.42.05.png

Untitled.jpg
 
Joined
Nov 6, 2012
Messages
25
Motherboard
Asrock Deskmini 310
CPU
i5 9500
Graphics
630HD
Mac
  1. iMac
  2. Mac mini
  3. Mac Pro
Mobile Phone
  1. iOS
I’m trying a build with this motherboard. My problem is it absolutely will not recognize any NVMe drive in the BIOS. I first thought I had a defective board, returned it, and the replacement does the same thing. I’ve tried multiple NVMe drives no success. I finally installed Big Sur on a SATA SSD successfully, but can’t figure out why it won’t recognize NVMe.
 
Joined
Dec 12, 2011
Messages
87
Motherboard
GIGABYTE Z590 Vision G
CPU
i7-11700K
Graphics
RX 6700 XT & RX 560
Mobile Phone
  1. iOS
I had similiar issues. I was never able to get a drive up and running in M2A_CPU (red), eventhough I did use an Intel Core i7-11700K (11th Gen Intel CPU).

Possible Solutions:
1) Flash the latest BIOS (F4d)
2) Do not use the M2A_CPU NVMe port (red)
3) Check whether your drive is among the supported QVL
4) Try M2C_CPU and M2B_CPU first (green), in my experience M2P_SB (blue) is the most compatible one, however, it only supports PCIe Gen 3.
If it does not show up in the BIOS the issue is completely unrelated to macOS/Hackintosh.

Questions:
What NVMe drive do you have? Is it PCIe 4 or only 3?

Zwischenablage01.jpg


Zwischenablage02.jpg
 
Joined
Jul 18, 2016
Messages
93
Motherboard
Asus Z-170 Deluxe
CPU
i7-6700K
Graphics
RX 580
Mobile Phone
  1. iOS
Intel i225-V 2.5GBe controller works with fake device-id(F2150000) and FakePCIID.kext, FakePCIID_Intel_I225-V.kext.
View attachment 511205

@ohcang, have you tried removing fake PCI ID kext for the built-in Ethernet on macOS 11.4? Since it may have been supported natively now?

“…with macOS 11.4 Beta 1, Apple has opened up AppleIntelI210Ethernet to supporting a larger array of devices including the i225-V NIC found on most higher end boards.”

https://dortania.github.io/hackintosh/updates/2021/04/24/rocket-lake.html
 
Joined
Mar 5, 2021
Messages
40
Motherboard
GIGABYTE Z590 Vision-G
CPU
10700K
Graphics
RX580
Small Quick Fix 21.05.25

Issue

I added another GPU(Dual RX580) and switched the WiFi module type from PCI-e to NVME M.2.
However, Sleep does not work properly after that.

Screen Shot 2021-05-25 at 3.38.02 PM.png

NGFF M.2 M KEY type WiFi module ↑
I bought this one from the Aliexpress($42.71)
Broadcom BCM943602CS with WiFi Card to NGFF M.2 KEY M Adapter



The USB port from the M.2 WiFi module's Bluetooth prevents sleep.
I spent several hours trying to figure out what was wrong and finally came up with a solution.

Solution
Apply the ACPI Hot Patch as follows after adding SSDT-GPRW.aml to the ACPI folder.

Unfortunately, after applying this patch, you won't be able to wake up using USB/Bluetooth devices.
The power button works only.

Sleep/Wake, on the other hand, works wonderfully.


Code:
    <key>ACPI</key>
    <dict>
        <key>Patch</key>
        <array>
            <dict>
                <key>Comment</key>
                <string>change Method(GPRW,2,N) to XPRW, pair with SSDT-GPRW.aml</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>R1BSVwI=</data>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data></data>
                <key>OemTableId</key>
                <data></data>
                <key>Replace</key>
                <data>WFBSVwI=</data>
                <key>ReplaceMask</key>
                <data></data>
                <key>Skip</key>
                <integer>0</integer>
                <key>TableLength</key>
                <integer>0</integer>
                <key>TableSignature</key>
                <data></data>
            </dict>
        </array>
    </dict>


* Do NOT use this quick fix if you have a PCI-e WiFi module.

Screen Shot 2021-05-25 at 3.40.31 PM.png

PCI-e type WiFi module ↑


Thanks.


Ref.
 

Attachments

  • SSDT-GPRW.aml
    101 bytes · Views: 59
Last edited:
Joined
Mar 5, 2021
Messages
40
Motherboard
GIGABYTE Z590 Vision-G
CPU
10700K
Graphics
RX580
@ohcang, have you tried removing fake PCI ID kext for the built-in Ethernet on macOS 11.4? Since it may have been supported natively now?
I still haven't updated to Big Sur 11.4.

I already use Kernel Patch For Built-in Ethernet (Intel i225-V).
So, no longer use FakePCIID.kext and related patches.

Quick FIX
1. Delete FakePCIID.kext, FakePCIID_Intel_I225-V.kext files.
2. No need device-id injection also.
3. Then apply Kernel Patch as below.

Code:
    <key>Kernel</key>
    <dict>
        <key>Patch</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>Base</key>
                <string>__Z18e1000_set_mac_typeP8e1000_hw</string>
                <key>Comment</key>
                <string>AppleIntelI210Ethernet for i225-V NIC</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>
                8hUAAA==
                </data>
                <key>Identifier</key>
                <string>com.apple.driver.AppleIntelI210Ethernet</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data>
                </data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>
                8xUAAA==
                </data>
                <key>ReplaceMask</key>
                <data>
                </data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>
        </array>
    </dict>

Done

Ref.
 
Joined
Jul 18, 2016
Messages
93
Motherboard
Asus Z-170 Deluxe
CPU
i7-6700K
Graphics
RX 580
Mobile Phone
  1. iOS
I still haven't updated to Bigsur 11.4.

I already use Kernel Patch For Built-in Ethernet (Intel i225-V).
So, no longer use FakePCIID.kext and related patches.

Quick FIX
1. Delete FakePCIID.kext, FakePCIID_Intel_I225-V.kext files.
2. No need device-id injection also.
3. Then apply Kernel Patch as below.

Code:
    <key>Kernel</key>
    <dict>
        <key>Patch</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>Base</key>
                <string>__Z18e1000_set_mac_typeP8e1000_hw</string>
                <key>Comment</key>
                <string>AppleIntelI210Ethernet for i225-V NIC</string>
                <key>Count</key>
                <integer>0</integer>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>
                8hUAAA==
                </data>
                <key>Identifier</key>
                <string>com.apple.driver.AppleIntelI210Ethernet</string>
                <key>Limit</key>
                <integer>0</integer>
                <key>Mask</key>
                <data>
                </data>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>Replace</key>
                <data>
                8xUAAA==
                </data>
                <key>ReplaceMask</key>
                <data>
                </data>
                <key>Skip</key>
                <integer>0</integer>
            </dict>
        </array>
    </dict>

Done

Ref.
Thanks for letting us know. Do you think this can be applied to Asus Z590-e or other Z590 boards in general with the same Ethernet controller?

Do you use USBMap or USBToolbox to map your USB ports?

Thanks.
 
Joined
Mar 5, 2021
Messages
40
Motherboard
GIGABYTE Z590 Vision-G
CPU
10700K
Graphics
RX580
Thanks for letting us know. Do you think this can be applied to Asus Z590-e or other Z590 boards in general with the same ethernet controller?

Do you use USBMap or USBToolbox to map your USB ports?

Thanks.
This fix, I guess, can be apply to same Ethernet controller on similar boards. Please read the networking section of the dortania’s Z590 compatibility thread.

And I use the Hackintool to map USB ports. I recommend check the attachment for my latest EFI.
 
Joined
Dec 12, 2011
Messages
87
Motherboard
GIGABYTE Z590 Vision G
CPU
i7-11700K
Graphics
RX 6700 XT & RX 560
Mobile Phone
  1. iOS
I'm still on the latest BIOS F4d.

macOS 11.4 doesn't boot for me (which is strange because a beta version of 11.4 did boot in the past).

I encountered a NVMe-related kernel panic that I was able to solve by inserting the drive into another slot (I moved it from M2P_SB to M2B_CPU). Now the machine boots fine. But after the login screen, (and waiting approx 10 seconds) the entire system freezes.

The same issue is discussed here (that's where I got the idea about changing the NVMe ports).

I do use a WD_BLACK SN850 with the latest firmware 613000WD (which I already upgraded using Windows coming from 611100WD). Unfortunately, this didn't fix the issue.

A potential path towards a solution. I do use NVMeFix 1.0.7.

drive.jpg


IMG_3794.jpg

IMG_3759.JPG


Edit: Issue resolved see this solution.
 
Last edited:
Top