This sudden lockup problem seems to be growing. It would be helpful to see what your systems have in common to determine whether there's any pattern. It's important that all of these questions be answered:
What SMBIOS name are you using? iMacPro1,1 or iMac19,1?
What is the make/model of your GPU?
What are your config.plist boot arguments?
What version of Lilu and WhateverGreen are you using?
What version of macOS are you running?
How much RAM is in your system and what is the configuration of the DIMM modules (e.g. 8GB modules x 4)?
I'm sad to say I experienced another one tonight, although it wasn't a complete lockup. Interestingly enough, the system became unresponsive, but the mouse still worked and started 'painting' blue lines across the screen wherever it went.
Here's the answer to your questions:
What SMBIOS name are you using? iMacPro1,1 or iMac19,1? iMac19,1
What is the make/model of your GPU? Sapphire Radeon Nitro+ Rx 5700 Xt
What are your config.plist boot arguments? keepsyms=1, dart=0, debug=0x100, slide=0, agdpmod=pikera
What version of Lilu and WhateverGreen are you using? Latest: L=1.4.1 WG=1.3.6
What version of macOS are you running? 10.15.2
How much RAM is in your system and what is the configuration of the DIMM modules (e.g. 8GB modules x 4)? 32gb (4x8gb DIMMs)
When did you first notice the lockups? Saturday (first day of new build)
I tried this with my Clover setup. Removed EmuVariableUefi.efi and nvram.plist, and installed the .aml file, rebooted, and nvram looks good on my end too.
I'll also note, that I haven't been able to see any of the BIOS splash screens connecting my monitor to the sapphire card, neither HDMI, nor any of the display ports. All of the working install has been the motherboard HDMI port. I do have "initial display output " set to "PCIe 1 slot" in the bios, and power going to the card. The sapphire logo lights up if that's worth anything.
You only have the one monitor plugged into the Sapphire card? Not one into the Sapphire and one into the iGPU?
If so, sounds like something is up with the graphics card. You should be seeing the POST screen on your display connected to your Sapphire. And you have BOTH power inputs on the Sapphire card connected right? Which slot is the Sapphire in?
Great! I’ll run some tests myself, then update the Catalina Mini-Guide and possibly the OpenCore Mini-Guide as well. The heavily modified DSDT in OpenCore mini-guide is exhibiting a number of ACPI parsing errors at boot, and I was unable to use the experimental SSDT-TbtOnPch_Designare-Draft<xx>.aml. So if the only tangible benefit of that DSDT is support for native NVRAM, it would be better to use the standard unmodified file and simply throw in SSDT-NVRAM.aml.
The properties you set though don't work, so it doesn't show in PCI.
Just finished testing the two new SSDTs. There is good news and bad news!
Good News:
Both SSDT-TbtOnPch-Designare_Draft05.aml (I renamed it to Draft05) and SSDT-TbtOnPch-Designare_Simplified_Draft01.aml cause the full set of Thunderbolt devices to appear in IOReg! This solves the problem of missing child nodes.
Bad news:
The system locks up (freezes completely) after about 2-3 minutes with both SSDTs if any Thunderbolt device is connected.
If no Thunderbolt device is connected, then the system works reliably with both SSDTs.
Hot plug does not work whether GPIO3 Force Power is enabled or disabled.
** OpenCore Mini-Guide Updated to Avoid Modified DSDT and Use SSDT-NVRAM **
The OpenCore Mini-Guide is now more forward-compatible because it no longer uses a specially modified Gigabyte DSDT, but instead uses the system's standard DSDT. When new firmware updates are installed or features in BIOS are enabled/disabled, it will no longer be necessary to modify the custom DSDT to keep up with those changes.
The primary reason for using the specially modified DSDT was to enable native NVRAM support. But this has now been achieved with a simple SSDT-NVRAM.aml. Thanks to @doradekell and @CODYQX4 for the inputs that led to this.
New ZIP files for both OpenCore 0.5.4 Standard and OpenCore 0.5.4 n-d-k fork have been uploaded.
This sudden lockup problem seems to be growing. It would be helpful to see what your systems have in common to determine whether there's any pattern. It's important that all of these questions be answered:
What SMBIOS name are you using? iMacPro1,1 or iMac19,1?
What is the make/model of your GPU?
What are your config.plist boot arguments?
What version of Lilu and WhateverGreen are you using?
What version of macOS are you running?
How much RAM is in your system and what is the configuration of the DIMM modules (e.g. 8GB modules x 4)?
When did you first notice the lockups?
Did you install Clover rc scripts? These files will be in your /etc/rc.boot.d and /etc/rc.shutdown.d folders.
If not, please try that by following the procedure here: Catalina Mini-Guide --> Step 3 --> Bullet #9.
What is the power rating of your PSU? 650W, 750W, 850W, ?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
