Strange Whatevergreen bug on boot (dual monitor black screen)

[supongo]

I wanted to post this in the WEG support group as I think it is related, but im not sure.

 

When I boot my hack with 2 monitors plugged in, after Apple logo and progressbar both screens go to black, one (the HDMI one) flickering sometimes.

 

I have a Radeon VII, plugged in DP 1440p@144Hz and HDMI 1080p@60Hz.

 

I obtained the logs of a working boot (with DP only) and a nonworking one (both DP and HDMI).

 

logDPworking https://pastebin.com/KCMZJaNh

logDP&HDMInonworking-looping https://pastebin.com/sw2s8Ssv

 

In the nonworking one something loops, and I think depending on what position of the loop I remove a cable, the system can recover or not (and stay with a black screen).

 

I tried giving HDMI and DP different priorities with WEG (making an ASL with "connector-priority"), didnt get any better.

 

I cant grasp where to go from here. Anyone has any idea of what could be happening?

 

RadeonPriority.asl https://pastebin.com/L5K491Xn

logDPworking.txt logDP&HDMInonworking-looping.txt

Edited October 30, 2022 by supongo

[Slice]

And what if you exclude WhateverGreen?

[supongo]

It does the exact same, but with more glitches during boot log.

[supongo]

It does the exact same, but with more glitches during boot log.

 

Also I forgot to add: if I boot with one screen and login, after login I can plug whatever and works flawlessly.

[Slice]

35 minutes ago, supongo said:

It does the exact same, but with more glitches during boot log.

You means pink stripes? It is not a bug. This is a normal procedure to test video memory. It's a pity Apple decided to make it visible.

WhateverGreen cancels the test. And what? The system will work without testing video memory.

There is a way to increase a pause in EDID and in this case you will not see the pink stripes. May be as in real Mac.

 

But WhateverGreen has many functions not only visual effects and I am not sure they are innoxious.

[miliuco]

@supongo

 

What is macOS version?

Upload your config.plist.

[supongo]

1 hour ago, miliuco said:

@supongo

 

What is macOS version?

Upload your config.plist.

Sure, here you have it!

 

I'm using macOS Ventura but happened the same on Monterey.

config.plist

Edited October 30, 2022 by supongo

[miliuco]

@supongo

 

Do you need ResetLogoStatus?

And FuzzyMatch?

And -raddvi?

Try without them. I'm pretty sure you don't need them.

 

I see a lot of Tools, do you need all of them? I have only OpenShell.efi.

 

agdpmod=pikera in boot args makes any difference?

 

Give a try to these settings and comment.

[aniuks27]

14 hours ago, supongo said:

Sure, here you have it!

 

I'm using macOS Ventura but happened the same on Monterey.

config.plist 62.96 kB · 1 download

Your config is really messy. I would question a lot of kexts you use like SMCLightSensor ( pretty sure you don't need on desktop system) . Also CPUFriend kext have to go with accompanied kext like DataProvider.kext  or alternatively you can use SSDT method generated by CPUFriendFriend. Another question would be what bluetooth card/module you got , as you got lots of kexts for bluetooth. Another question would be: why MacPro7,1 with 8600K CPU? You kinda missing out iGPU encoding/decoding functionality.

 

[supongo]

2 hours ago, aniuks27 said:

Your config is really messy. I would question a lot of kexts you use like SMCLightSensor ( pretty sure you don't need on desktop system) . Also CPUFriend kext have to go with accompanied kext like DataProvider.kext  or alternatively you can use SSDT method generated by CPUFriendFriend. Another question would be what bluetooth card/module you got , as you got lots of kexts for bluetooth. Another question would be: why MacPro7,1 with 8600K CPU? You kinda missing out iGPU encoding/decoding functionality.

 

 

- True, SMCLightSensor should not be there!

- The receiver kext is not there because this is the plist of my recovery dongle, which is based just a version before I did the PMing.  I do have CPUFriendDataProvider.kext (and enabled!).

- My BT is a l219-V Intel combo, tbh I have no idea what kext i need for it, this part of the guide I followed in late hours.

- I have an 8600K with the iGPU off because DRM is not working 100% with iGPU & dGPU combos, and my dGPU encoder/decoder is awesome too. I have an ITX and I also would prefer to not heat my CPU too much because the heatsink is not so big, while the GPU can work at its normal speed.

 

3 hours ago, miliuco said:

@supongo

 

Do you need ResetLogoStatus?

And FuzzyMatch?

And -raddvi?

Try without them. I'm pretty sure you don't need them.

 

I see a lot of Tools, do you need all of them? I have only OpenShell.efi.

 

agdpmod=pikera in boot args makes any difference?

 

Give a try to these settings and comment.

 

- Dunno why ResetLogoStatus is there tbh.

- Dunno why FuzzyMatch is there tbh.

- True, I've actually never used any of these tools, theyve been with me since I first made the system boot.

- I thied back in the day and would not make much difference. Also tried vit6969 and that one would give problems.

 

Thank you so much with the reccomendations! I'll message back when I'm done with the testing.