pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[scottkendall]

2. I get the same kernel panic - and @pastrychef also noted that he gets it, after upgrading to 10.15.4. He mentions it in the 10.15.4 upgrade thread, and I asked about it there (https://www.tonymacx86.com/threads/macos-10-15-4-update.292646/page-12#post-2091141)! He said that he just disabled WhateverGreen to fix (which I think just means removing the -wegbeta boot argument).

No it means they prevented WEG from loading, as far as I know they are using OC in which case they set WEG to disable in their config. If they are using Clover they removed the file from their Kext/other directory. Removing the beta boot argument just makes it now load on a beta OS. Maybe WEG considers 15.4 a beta OS.

 

[adenbeckitt]

To expand on this, I instead just removed AppleALC and that seems to prevent the KP.

I don't use the onboard audio outputs so this is fine for me until a better solution is found.

 

[pastrychef]

Just updated to the newest clover and macos last night. Will try that

Also, just woke my mac and it froze.

EDIT:

panic(cpu 0 caller 0xffffff8014416487): "AppleHDAHDMI_DPDriver::setPowerState(0xffffff8054ff7b00 : 0xffffff7f967fc6f8, 0 -> 1) timed out after 10178 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffffa3dfcb3b40 : 0xffffff8013d215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffffa3dfcb3b90 : 0xffffff8013e5a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffffa3dfcb3bd0 : 0xffffff8013e4bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffffa3dfcb3c20 : 0xffffff8013cc7a40 mach_kernel : _return_from_trap + 0xe0
0xffffffa3dfcb3c40 : 0xffffff8013d20c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffffa3dfcb3d40 : 0xffffff8013d21087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffffa3dfcb3d90 : 0xffffff80144c2c7c mach_kernel : _panic + 0x54
0xffffffa3dfcb3e00 : 0xffffff8014416487 mach_kernel : __ZN9IOService12ackTimerTickEv + 0x6f7
0xffffffa3dfcb3e50 : 0xffffff8014415d69 mach_kernel : __ZN9IOService21actionAckTimerExpiredEP8OSObjectPvS2_S2_S2_ + 0x9
0xffffffa3dfcb3e60 : 0xffffff801442d2fe mach_kernel : __ZN10IOWorkLoop9runActionEPFiP8OSObjectPvS2_S2_S2_ES1_S2_S2_S2_S2_ + 0x3e
0xffffffa3dfcb3ea0 : 0xffffff8014414b18 mach_kernel : __ZN9IOService17ack_timer_expiredEPvS0_ + 0x38
0xffffffa3dfcb3ec0 : 0xffffff8013d63545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffffa3dfcb3f40 : 0xffffff8013d63071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffffa3dfcb3fa0 : 0xffffff8013cc713e mach_kernel : _call_continuation + 0x2e

EDIT2: The panic seems to an AppleALC panic, which should be fixed with the KernelToPatch code already in your config. However, it seems not to work.

I got around this be removing WhateverGreen. The only reason I had WhateverGreen in the first place was to enable all the video out ports on my video card and to enable HDMI/DisplayPort audio. I only have one monitor so, having just two video out ports working is not an issue for me and something in 10.15.4 has HDMI audio working anyway.

 

[pastrychef]

1. @adenbeckitt I get the same on boot, but does not seem to cause any problems

View attachment 457253

2. I get the same kernel panic - and @pastrychef also noted that he gets it, after upgrading to 10.15.4. He mentions it in the 10.15.4 upgrade thread, and I asked about it there (https://www.tonymacx86.com/threads/macos-10-15-4-update.292646/page-12#post-2091141)! He said that he just disabled WhateverGreen to fix (which I think just means removing the -wegbeta boot argument).

panic(cpu 0 caller 0xffffff8000a16487): "AppleHDAHDMI_DPDriver::setPowerState(0xffffff8045873900 : 0xffffff7f82a996f8, 0 -> 1) timed out after 10147 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296
Backtrace (CPU 0), Frame : Return Address
0xffffffa3d65bbb40 : 0xffffff80003215cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffffa3d65bbb90 : 0xffffff800045a3c5 mach_kernel : _kdp_i386_trap + 0x155
0xffffffa3d65bbbd0 : 0xffffff800044bf7e mach_kernel : _kernel_trap + 0x4ee
0xffffffa3d65bbc20 : 0xffffff80002c7a40 mach_kernel : _return_from_trap + 0xe0
0xffffffa3d65bbc40 : 0xffffff8000320c97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffffa3d65bbd40 : 0xffffff8000321087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffffa3d65bbd90 : 0xffffff8000ac2c7c mach_kernel : _panic + 0x54
0xffffffa3d65bbe00 : 0xffffff8000a16487 mach_kernel : __ZN9IOService12ackTimerTickEv + 0x6f7
0xffffffa3d65bbe50 : 0xffffff8000a15d69 mach_kernel : __ZN9IOService21actionAckTimerExpiredEP8OSObjectPvS2_S2_S2_ + 0x9
0xffffffa3d65bbe60 : 0xffffff8000a2d2fe mach_kernel : __ZN10IOWorkLoop9runActionEPFiP8OSObjectPvS2_S2_S2_ES1_S2_S2_S2_S2_ + 0x3e
0xffffffa3d65bbea0 : 0xffffff8000a14b18 mach_kernel : __ZN9IOService17ack_timer_expiredEPvS0_ + 0x38
0xffffffa3d65bbec0 : 0xffffff8000363545 mach_kernel : _thread_call_delayed_timer + 0xec5
0xffffffa3d65bbf40 : 0xffffff8000363071 mach_kernel : _thread_call_delayed_timer + 0x9f1
0xffffffa3d65bbfa0 : 0xffffff80002c713e mach_kernel : _call_continuation + 0x2e

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0 debug=0x100 keepsyms=1 -lilubetaall -vsmcbeta -wegbeta -alcbeta -disablegfxfirmware -no_compat_check

Mac OS version:
19E266

Yes, scottkendall is correct.

If you are using Clover, delete WhateverGreen from /EFI/CLOVER/kexts/Other/.

If you are using OpenCore, disable WhateverGreen in your config.plist.

 

[scottkendall]

I got around this be removing WhateverGreen. The only reason I had WhateverGreen in the first place was to enable all the video out ports on my video card and to enable HDMI/DisplayPort audio. I only have one monitor so, having just two video out ports working is not an issue for me and something in 10.15.4 has HDMI audio working anyway.

I added the piker black screen patch from clover to OC I got all video ports.

 

[pastrychef]

I added the piker black screen patch from clover to OC I got all video ports.

Cool!

Please post the patch. Thanks in advance.

 

[scottkendall]

Cool!

Please post the patch. Thanks in advance.

On Clover it is under kextstopatch ---> dropdown list----> Black Screen Patch Vega 56/64, RX580 etc. (c)Pike R. Alpha

AppleGraphicsDevicePolicy Find:626F6172 642D6964 Replace:626F6172 642D6978 Comment: Black Screen Patch Vega 56/64, RX580 etc. (c)Pike R. Alpha

In OpenCore I just copied another patch and modified it with the info above and for Identifier I put com.apple.driver.AppleGraphicsDevicePolicy

I do not have HEVC though but that could likely be enabled by a dummy kext.

 

[malm123]

I think Acronis True Image works for macOS, but I've never tried. I use Carbon Copy Cloner.

I don't know about 144Hz displays... Mine just does 60Hz.

- The problem was occasional black screen on boot with 1080 TI (50% of the time)-
So at the suggestion of another forum post, I tried installing Nvidia pixel clock patch. It made the black screen on boot issue happen every time. Then, after trying again with a different version from recovery mode, I made the system fail to boot in recovery and safemode (lock up at about 80% loaded, verbose mode says "failed to initialize graphics firmware").

I tried restoring a Carbon Copy image that Imade at your suggestion @pastrychef, but still got the the same issue. Followed your instructions on page one of this post to make a new bootable disk, loaded those kexts, booted and replaced kexts with yours and I am back in but still have original issue of occasional black screen on boot.

- The Fix -
My version of Clover was outdated. had some trouble figuring out how to install kexts. Then I realized all I needed was another read of Pastrychef's post to figure out my clover needed to be updated and now has the option to install lilu and whatever green right in the configurator. Now with those updated I haven't had a black screen on boot yet. THANK YOU @pastrychef that's 3 times now you've saved me.

 

[pastrychef]

- problem was occasional black screen on boot with 1080 TI (50% of the time)-
So at the suggestion of another forum post, I tried installing nvidia pixel clock patch. it made the black screen on boot issue happen every time, then after trying again with a different version from recovery mode, made the system fail to boot in recovery and safemode (lock up at about 80% loaded, verbose mode says "failed to initialize graphics firmware").

I tried restoring a carbon copy image that i made at your suggestion @pastrychef, but still got the the same issue. Followed your instructions on page one of this post to make a new bootable disk, loaded those kexts, booted and replaced kexts with yours and I am back in but still have original issue of occasional black screen on boot.

- The Fix -
my version of clover was outdated. had some trouble figuring out how to install kexts then realized all i needed was another read of Pastrychef's post to figure out my clover needed to be updated. now with lilu and whatevergreen updated I havent had a black screen on boot yet. THANK YOU @pastrychef thats 3 times now you've saved me.

There are no special steps required for updating kexts. Just navigate to /EFI/CLOVER/kexts/Other/ and replace old versions with newer versions.

 

[kentval]

I think I've posted an EFI for you before in this thread. Just search for posts by you on this thread and you should be able to find it.

Yep, sorta: found post 8734 with an EFI for 5103. Could not find any others. Re-did mine to basically match yours with some exceptions:

Need
RTC fix enabled for my mobo
inject true for audio

In SIMBIOS, these are different in mine from yours:

EFIversion
FrimwareFeatues
FirmwareFeaturesMask

Next I'm going to change CsrActiveConfig to 0 (from 0x67) and see if that will allow my updates to show.

[EDIT: No change. I'm locked out of updates the easy way, it seems.)

Thanks again for your encouragement.