- Joined
- Aug 14, 2020
- Messages
- 4
- Motherboard
- Z390 Designare
- CPU
- i5-9600k
- Graphics
- GTX 1080
Does this work on Opencore. Transferred the premade file in atom to open in proper tree. Can I copy these properties on my hackintosh and make it work
I saw this intel gpu manual before I posted a message in this thread, and it confused me that I can not use the native device-id. I use 10.15.6 (19G73).which according to this is natively supported
<key>framebuffer-con1-flags</key>
<data>zwMAAA==</data>
<key>framebuffer-con2-flags</key>
<data>zwMAAA==</data>
Looks like I've solved the problem by selecting CNConnectorAlwaysConnected flag on both ports. Now I can boot with both 1080p 60Hz without issues. So the only things I need to add to my config.plist are
Thanks for your help! I will post if it is stable in next week.Code:<key>framebuffer-con1-flags</key> <data>zwMAAA==</data> <key>framebuffer-con2-flags</key> <data>zwMAAA==</data>
Sounds good, maybe default device-id 0x9BC8 will work good on iMac20,1. I will try it in a few daysiMac20,1 may be a better MacModel for you, since that model uses 10th Gen Intel.
Sounds good, maybe default device-id 0x9BC8 will work good on iMac20,1. I will try it in a few days
Looks like I've solved the problem by selecting CNConnectorAlwaysConnected flag on both ports. Now I can boot with both 1080p 60Hz without issues. So the only things I need to add to my config.plist are
Code:<key>framebuffer-con1-flags</key> <data>zwMAAA==</data> <key>framebuffer-con2-flags</key> <data>zwMAAA==</data>
The very first idea was "this is related with framebuffer memory size", since this is graphical artefact, happens when two monitors are connected (I thought 2*1080p consumed more vram so it need to enable fixes for 4k monitors) but nothing has changed after applying fixes for 4k.how you arrived
This is very strange that I have to use this flag, it looks like mac os somehow fails to communicate with the monitor during startup or some patches failed to apply at startup when monitor disconnects without this flag.https://www.insanelymac.com/forum/topic/334899-intel-framebuffer-patching-using-whatevergreen/?do=findComment&comment=2627325 said:One way you might get around it is to turn off the CNConnectorAlwaysConnected flag. Then it will treat your screen as an external
General Framebuffer Patching Guide using Hackintool...
General Framebuffer Patching Guide using Hackintool...
Excellent work!!! Really really good. Thank you so much for it...