Contribute
Register

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

@root2
I don't have any NVME M.2 SSD on my system.
I'll check this issue after purchasing an NVME SSD in a few days ;)
 
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.

View attachment 519678

View attachment 519680
View attachment 519681


When the machine freezes at login, does the clock, top right in the menu-bar still advance?
 
Fun fact, the specific model SN850 from WD is on Gigabyte's QVL for supported and tested NVMe SSDs. Still, the mainboard doesn't POST if you insert the drive into M2A_CPU. Or when you use two of them in M2B_CPU AND M2C_CPU. The issue is discussed in the Gigabyte forum, but there is not fix. Best advice stay away from PCIe 4.0 NVMe drives if you can, and you do not need/want their mind blowing speed.
 
When the machine freezes at login, does the clock, top right in the menu-bar still advance?
Nope, everything freezes completely. Do you think this is yet another issue unrelated to NVMe?
I tried to press cancel, but then the cursor froze. I waited a few minutes, but nothing changed.

image0.jpeg
 
Nope, everything freezes completely. Do you think this is yet another issue unrelated to NVMe?
I tried to press cancel, but then the cursor froze. I waited a few minutes, but nothing changed.

View attachment 519683

For sure later on in the crash there are negative NVME issues, but earlier it is centred on the USB sub-system, hence my question about the clock.

Hard to pinpoint.

I'm not familiar with your build. Have you disabled the RX6700?
 
For sure later on in the crash there are negative NVME issues, but earlier it is centred on the USB sub-system, hence my question about the clock.

Hard to pinpoint.

I'm not familiar with your build. Have you disabled the RX6700?
Yes, it's disabled (and I verified this in macOS 11.3) using SSDT.
 
Today I purchased an NVME drive (hynix p31).
However, I believe nvme has nothing to do with the freezing problem.
I just discovered that the i225 ethernet causes freezing problems.
For the time being, I believe it is best to turn it off in cmos and use it.
If I find a solution, I'll update this thread ASAP.
 
@root2

Here's the quick fix

Issue
Freezing and stuttering or boot failure after Big sur 11.4 update

Cause
Kernel patch for Intel i225 onboard NIC does NOT work anymore on 11.4

Solution

- Restore to the old version of fake id injection


1. Delete/Disable vit9696 kernel patch
Screen Shot 2021-05-31 at 1.11.51 AM.jpg


2. Add FakePCIID.kext, FakePCIID_Intel_I225-V.kext(Add Kernel also)

Code:
    <key>Kernel</key>
    <dict>
        <key>Add</key>
        <array>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>FakePCIID_Intel_I225-V.kext</string>
                <key>Comment</key>
                <string>Supports 2.5Gbit Ethernet (Intel I225-V)</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string></string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
            <dict>
                <key>Arch</key>
                <string>Any</string>
                <key>BundlePath</key>
                <string>FakePCIID.kext</string>
                <key>Comment</key>
                <string>Allows faked device-ids to attach to suitable drivers</string>
                <key>Enabled</key>
                <true/>
                <key>ExecutablePath</key>
                <string>Contents/MacOS/FakePCIID</string>
                <key>MaxKernel</key>
                <string></string>
                <key>MinKernel</key>
                <string></string>
                <key>PlistPath</key>
                <string>Contents/Info.plist</string>
            </dict>
        </dict>
    </dict>



3. Add DeviceProperties like as below

Code:
    <key>DeviceProperties</key>
    <dict>
        <key>Add</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1B,0x2)/Pci(0x0,0x0)</key>
            <dict>
                <key>device-id</key>
                <data>
                8hUAAA==
                </data>
                <key>device_type</key>
                <string>Ethernet controller</string>
                <key>model</key>
                <string>Intel(R) Ethernet Controller I225-V</string>
            </dict>
        </dict>
    </dict>


Reboot,
Done


This issue is unrelated to the NVME SSD Drive.
Cuz I purchased a new NVME drive and use it as well :)


If you need more in-depth research on this issue, please check this thread.



Thanks, CaseySJ
 

Attachments

  • FakePCIID_Intel_I225-V.kext.zip
    2.4 KB · Views: 128
  • FakePCIID.kext.zip
    13.6 KB · Views: 128
Last edited:
@ohcang, can you share more pictures for your hardware setup, particularly the case layout and the motherboard. Thanks.
There are no special components and settings.
Please check my components list(page 1) and look for the manual on the manufacturer's website.
 
Back
Top