XiaoMi-Pro-Hackintosh icon indicating copy to clipboard operation
XiaoMi-Pro-Hackintosh copied to clipboard

FBEnableDynamicCDCLK causes black screen when wake up from hibernate mode 25

Open stevezhengshiqi opened this issue 4 years ago • 8 comments

Bootloader: OpenCore v0.5.9 macOS Version: 10.15.5

Start from Release v1.3.8, we add framebuffer-flag property to support certain features on ig-platform-id: 0x591C0005, for example, support hidpi resolution higher than 1440x810.

However, after some tests, I noticed that the FBEnableDynamicCDCLK flag will break wake up from hibernate mode 25. Workarounds are to close the lid and reopen it, or set hibernate mode to 3 or 0.

A better solution is to disable the FBEnableDynamicCDCLK flag by setting framebuffer-flag to CwfDAA==. But after doing this, the device won't support hidpi resolution larger than 1440x810. It's a trade-off, and for now I find no better solution for this. macOS is known unfriendly to the low-resolution screens like the 1080p screen on XiaoMi-Pro.

stevezhengshiqi avatar Jun 16 '20 22:06 stevezhengshiqi

Hello mate, i just read your post and i would like to have more info about this... I'm not able to help you solving this problem but i follow your great work because my huawei Matebook is very similar to the Xiaomi Pro and i get a lot of tips from your setup .. So for example i'm able to use the 1440x810 HiDPI resolution without any issue after sleep thanks to your framebuffer-flag setup. But then i've read this post and i would like to better understand your tweak to be able to use HiDPI resolution bigger than 1440x810. I don't use hibernation at all so for me this is not an issue at all. What should i do to achieve this ? Setting platform-id to 0x591C0005 (right now i've the default 0x00001659) and be sure that FBEnableDynamicCDCLK is enable ? What about the other flags i see in Hackintool ? Should i have to leave them as default ?

Thanks and keep up the great work !

Mattia

tmbt78 avatar Jun 18 '20 22:06 tmbt78

@tmbt78 platform-id to 0x591C0005 in default enables FBEnableDynamicCDCLK. You can use https://github.com/xzhih/one-key-hidpi to enable custom HiDPI resolution. Seems like 1600x900 is the maximum HiDPI resolution for 1080p screen on 10.15+.

stevezhengshiqi avatar Jun 18 '20 23:06 stevezhengshiqi

@stevezhengshiqi .. Hi, i've tried to inject the platform id as suggested but i don't have hardware acceleration at all : Screenshot 2020-06-19 at 10 59 02

Could you please suggest me what i'm doing wrong ? I've tried to inject also differents device-id but with the same result.

Thanks Mattia

tmbt78 avatar Jun 19 '20 09:06 tmbt78

@tmbt78 How do you know you don't have hardware acceleration? Did you check with VDADecoderChecker? Also, 591C0005 is only for Kabylake GPUs or 8th Gen IGPUs, make sure it matches your platform.

BTW, you might need to open another issue since it's off-topic.

stevezhengshiqi avatar Jun 19 '20 09:06 stevezhengshiqi

I know because Metal doens't work, no more transparency, the mouse is laggy and i go back to 1920x1080 default resolution. Also About this Mac shows that my videocard has 7MB of RAM. I have an i5 7200U (it's a 7th generation CPU so it's a KabyLake). Right now i'm working on HiDPI 1440 x 810 using your framebuffer tweaks and 0x00001659 as platform ID. But if i switch to 591C0005 i lost hardware accelaration and HiDPI

tmbt78 avatar Jun 19 '20 09:06 tmbt78

@tmbt78 591c0005 is a Amber Lake Y platform id, which requires 8th Gen CPU. In your case, use 5916 is fine. You can check FBEnableDynamicCDCLK in Hackintool framebuffer section. The framebuffer-flag in this repository has already enabled FBEnableDynamicCDCLK.

stevezhengshiqi avatar Jun 19 '20 10:06 stevezhengshiqi

@stevezhengshiqi Thank you for the support ! I haven't noticed that the flag in your repository already has the FBEnableDynamicCDCLK enable .. i could have tried to increase the HiDPI resolution and try :) ... Anyway now i'm using a 1536*864 HiDPI resolution without screen garbage after sleep and i'm very happy!

Thanks !

Mattia

tmbt78 avatar Jun 19 '20 20:06 tmbt78

Only hibernatemode 25 will cause the screen problem. Normal sleep like hibernatemode 0 or 3 is not affected.

stevezhengshiqi avatar Jul 05 '20 03:07 stevezhengshiqi