KP when attempting to upgrade to 10.15.4 from 10.15.3

[dalilama]

All updates since 10.15 were installed when fine up till this point. Updated Clover to 5107 and downloaded the 10.15.4 update. Kernel panic on 1st reboot for the update. Using -v I was able to identify the point of the panic with the message "IOConsoleUsers gIOScreenLockState 3". I know this points to a graphics issue. I have a 3 monitor setup that was working perfectly prior to this using the on-board HD4600 chip. DisplayPort, HDMI, DVI-D for each monitor. Boot messages appear on the DVI-D based monitor.

Lilu was updated to 1.4.2, WEG to 1.3.7 prior to the update.

Any ideas on how to address this?

 

[amaroq]

I had the same issue. Although I'm on a dual monitor setup.

Everything worked fine on 10.15.3, but the 10.15.4 installer kept giving a KP on launch.

I found a forum post that mentioned it's due to having a second monitor plugged in so I unplugged mine and voila! I was able to update to 10.15.4.

The downside is dual monitors didn't work after the update either, so I've been using a single monitor for a couple weeks now.

My monitor setup is my main monitor plugged into HD 4600 via DVI and my secondary monitor also plugged into HD 4600 via HDMI. I also have a GTX 980 Ti but since Apple hasn't approved drivers for that in recent updates I have it disabled via a DSDT inject in Clover.

When I boot with my second monitor plugged in I get a KP mentioning IntelFrameBufferAzul so I'm looking more into how to fix the port detection for my specific mobo.

There's more info here: https://www.tonymacx86.com/threads/...ching-guide-hdmi-black-screen-problem.269149/

I'll try to update this thread if I can get it working.

 

[amaroq]

Upon following the guide in my previous post I found while trialing that my other HDMI port works fine when hotplugged.

Here's my mobo output:
DVI: main monitor
HDMI 1: not working causes KP
HDMI 2: KP on boot, but working if hotplugged

 

[dalilama]

There are other people with different motherboard manufacturers but the common theme is multiple monitors using an HD 4600 on board chip for the displays, and at least one HDMI connection. Hoping someone can steer me in the right direction.

 

[amaroq]

Another odd finding:

If I boot with nothing else connected but my HDMI 1, which I said causes a KP in my last post, then it works fine. As soon as I plug in the DVI for my main monitor I get a KP.

The same thing happens if I reverse the roles and boot with DVI and then plug in HDMI 1.

I'm not sure why these two ports don't play nicely together, but at least HDMI 2 works with the DVI.

 

[mahoefer]

Any updates/news regarding this issue? I just updated to 10.15.4 and now have this issue as well.

 

[sar4ras]

I'm having the same issue. My setup is HD 4600 with dual monitor plugged to HDMI and DVI.
After the 10.15.4 upgrade the OS hangs at "IOConsoleUsers gIOScreenLockState 3" during the boot.
If I use only one monitor, it works fine and hot plugging works for the other monitor after the boot.

 

[mahoefer]

I'm having the same issue. My setup is HD 4600 with dual monitor plugged to HDMI and DVI.
After the 10.15.4 upgrade the OS hangs at "IOConsoleUsers gIOScreenLockState 3" during the boot.
If I use only one monitor, it works fine and hot plugging works for the other monitor after the boot.

Hot plugging doesn't work for me. I don't get any kernel panics since switching over to OpenCore, which solved other sleep/wake issues I was having as well. Which ig-platform-id are you using?

 

[sar4ras]

Hot plugging doesn't work for me. I don't get any kernel panics since switching over to OpenCore, which solved other sleep/wake issues I was having as well. Which ig-platform-id are you using?

0x0d220003
for me hot plugin works for any interface.

Did OpenCore fix the OS hanging at "IOConsoleUsers gIOScreenLockState 3" during the boot?

 

[mahoefer]

0x0d220003
for me hot plugin works for any interface.

Did OpenCore fix the OS hanging at "IOConsoleUsers gIOScreenLockState 3" during the boot?

No it didn't. It only fixed the random kernel panics I was getting during sleep/wake.

In the meantime, I've also tried unsuccessfully setting the correct type id's and various bus id combinations for the connectors and patching the Framebuffer info. None of which helped. When I hot plug either HDMI or DVI, when the other monitor is already on, I don't see any change in Hacktool or IOReg. So the second monitor is not being recognized at all.