No Image on Laptop screen on wake but output on HDMI works

[NONITS]

@elmacci I know you dont have the blade stealth anymore but I recall you mentioned you used opencore at one point. Im considering using opencore on a new ice lake blade can you share your opencore efi?

 

[Scorch404]

Im considering using opencore on a new ice lake blade...

I've got the Icelake Stealth so would be interested too. Not been successful with OC yet and not even to the OSX installer but will share once I have success.

 

[chanwyatt]

i've no longer used the hackintosh anymore.but this is mine efi in opencore 0.57/macos15.4. works okay and hopes to be useful.

 

[nguyenburner]

Can you explain how you patched your DSDT for trackpad? Your DSDT file works for me but I am trying to create my own.

 

[tmbt]

Hi,
i know this is an old thread but the information i found here helped me to solve the same problem i had on my new laptop (Huawei Matebook X 2020).
I had black screen after sleep but using an external monitor i noticed the same Display0 behavior attaching to the next framebuffer available.
I coudn't use your config.plist because my laptop is 10th gen and differnt connectors BUT i spent some times (actually 2 days ) analyzing and reading all the data you've collected and finally noticed one thing :
Both the working Framebuffer's (0x3EA50004 and 0x3E9B0006) connectors @NONITS and @elmacci are using has the same flags on the internal monitor connector [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000498 - ConnectorLVDS

while the internal display connector associated with the Framebuffer's usually used and suggested for example on Dortania (0x3E9B0000 and 0x3E9B0007) has [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS.

As you can see flags is different. 498 vs 98. Well... i don't know what that 4 stand for BUT i injected in OC device property this framebuffer-con0-alldata -> 00000800 02000000 98040000 and magically now the internal display works after sleep. Works when an external TypeC to HDMI is connected on both my laptop port and works even if you hotplug it not just before waking from sleep.

I hope someone could land here and find this information usefull.

Mattia

 

[DottiestDuke47]

Hi,
i know this is an old thread but the information i found here helped me to solve the same problem i had on my new laptop (Huawei Matebook X 2020).
I had black screen after sleep but using an external monitor i noticed the same Display0 behavior attaching to the next framebuffer available.
I coudn't use your config.plist because my laptop is 10th gen and differnt connectors BUT i spent some times (actually 2 days ) analyzing and reading all the data you've collected and finally noticed one thing :
Both the working Framebuffer's (0x3EA50004 and 0x3E9B0006) connectors @NONITS and @elmacci are using has the same flags on the internal monitor connector [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000498 - ConnectorLVDS

while the internal display connector associated with the Framebuffer's usually used and suggested for example on Dortania (0x3E9B0000 and 0x3E9B0007) has [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS.

As you can see flags is different. 498 vs 98. Well... i don't know what that 4 stand for BUT i injected in OC device property this framebuffer-con0-alldata -> 00000800 02000000 98040000 and magically now the internal display works after sleep. Works when an external TypeC to HDMI is connected on both my laptop port and works even if you hotplug it not just before waking from sleep.

I hope someone could land here and find this information usefull.

Mattia

Hi, I have a XPS with a very similar issue. I tries to patch using the deatils you provided but it did not fix my issue. I was wondering whether you could provide a few more details on how you found what to patch, since I am very new to framebuffer patching.

Many thanks