Contribute
Register

<< Solved >> Display 7MB!!

Status
Not open for further replies.
According to Intel your Device ID is 0x3E92.

A quick look at Hackintool suggests that your patch should be something like this :

Code:
<key>Devices</key>
    <dict>
        <key>Properties</key>
        <dict>
            <key>PciRoot(0x0)/Pci(0x1B,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Internal@0,27,0</string>
                <key>device_type</key>
                <string>Audio device</string>
                <key>hda-gfx</key>
                <string>onboard-2</string>
                <key>layout-id</key>
                <data>
                AAAAAA==
                </data>
                <key>model</key>
                <string>8 Series/C220 Series Chipset High Definition Audio Controller</string>
            </dict>
            <key>PciRoot(0x0)/Pci(0x2,0x0)</key>
            <dict>
                <key>AAPL,ig-platform-id</key>
                <data>
                AACSPg==
                </data>
                <key>AAPL,slot-name</key>
                <string>Internal@0,2,0</string>
                <key>device-id</key>
                <data>
                mz4AAA==
                </data>
                <key>device_type</key>
                <string>VGA compatible controller</string>
                <key>framebuffer-con0-busid</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-con0-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con0-flags</key>
                <data>
                mAAAAA==
                </data>
                <key>framebuffer-con0-index</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-con0-pipe</key>
                <data>
                CAAAAA==
                </data>
                <key>framebuffer-con0-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con1-busid</key>
                <data>
                BQAAAA==
                </data>
                <key>framebuffer-con1-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con1-flags</key>
                <data>
                hwEAAA==
                </data>
                <key>framebuffer-con1-index</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con1-pipe</key>
                <data>
                CQAAAA==
                </data>
                <key>framebuffer-con1-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con2-busid</key>
                <data>
                BAAAAA==
                </data>
                <key>framebuffer-con2-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con2-flags</key>
                <data>
                hwEAAA==
                </data>
                <key>framebuffer-con2-index</key>
                <data>
                AgAAAA==
                </data>
                <key>framebuffer-con2-pipe</key>
                <data>
                CgAAAA==
                </data>
                <key>framebuffer-con2-type</key>
                <data>
                AAgAAA==
                </data>
                <key>framebuffer-con3-busid</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-con3-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-con3-flags</key>
                <data>
                IAAAAA==
                </data>
                <key>framebuffer-con3-index</key>
                <data>
                /////w==
                </data>
                <key>framebuffer-con3-pipe</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-con3-type</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-fbmem</key>
                <data>
                AAAAAA==
                </data>
                <key>framebuffer-patch-enable</key>
                <data>
                AQAAAA==
                </data>
                <key>framebuffer-stolenmem</key>
                <data>
                AACQAw==
                </data>
                <key>framebuffer-unifiedmem</key>
                <data>
                AAAAYA==
                </data>
                <key>hda-gfx</key>
                <string>onboard-1</string>
                <key>model</key>
                <string>Intel Crystal Well Integrated Graphics Controller</string>
            </dict>
        </dict>
    </dict>

"Intel Crystal Well Integrated Graphics Controller"?

The OP is listing UHD 630.

The whole point of the framebuffer guide is figuring out connector config, but Hackintool can just dump it with no thought?

With base64 binary data, you can't read the parameters to verify, so too many ways for this to go wrong in context and not be noticed.

I appreciate the effort that goes into making and using a tool like Hackintool, but it's not helpful to those struggling to grok essential config. You have to have the ability to do everything on your own that tool helps with in order to make sense of how to use it. There are so many ways to go wrong with it that it feels like black magic. If a spell works, you are lucky. If not you will never figure it out because you can't understand the tool without understanding the entire problem it is designed to solve. So the cut and paste is no help for anyone.

@mamPHP just because you have an outboard GPU that works means nothing for the integrated graphics, so don't gripe about how unbelievable it is that it doesn't just work zomg

Hackintool output may help, or it may not. Hackintool can as easily be the source of a problem as a solution. By reading Dortania and WEG you will get closer to the mystical wisdom. And Hackintool will make a bit more sense, although it's still incomprehensible to be. It needs a guide.

The biggest challenge of hackintosh is that it's all based on hacks not engineering. So you have to think like a wizard and not be surprised / afraid to get burned by spells you don't understand. It's a dark art. Hackintool is canned spells which can lead you astray from the light of the true path.

Suggest getting away from Clover and heading towards OC.

Go read the Dortania guide then consult the Whatevergreen FAQ for the device id for your hardware. Use the minimal config as described at Dortania and WEG. Then proceed to connector patching, if necessary, per the Framebuffer guide.

A lot of Hackintool lore and Clover is about older PC hardware and MacOS, but users today including you are at end of the line with last generations that will work, so watch out for lore and relics. Reading Dortania will help make this more clear.

You can prolly find working OC configuration for your rig elsewhere here, I think the topic of z390 and your chip is well convered.
 
Hi, COPR, I have almost the same issue or worse with OC and opencore stuff. Youtube is full with this "FIX" and most of them doesn't work or the publisher is already switched back to windows or linux. Hackitool is great but it doesn't fix this graphic loading issue for me. Finally i'm not bothering you any more. I'll keep using my nv 710, which works perfectly.

Regards
 
click on general tab and choose the options in there as well....
An empty KEY nothing else. The patch doesn't work on this motherboard model.
 
An empty KEY nothing else. The patch doesn't work on this motherboard model.
you have to tick the properties in the general tab as to what you want....
 
you have to tick the properties in the general tab as to what you want....
Screenshot 2021-10-12 at 22.00.39.png
 

Attachments

  • Screenshot 2021-10-13 at 19.14.52.png
    Screenshot 2021-10-13 at 19.14.52.png
    100 KB · Views: 26
  • Screenshot 2021-10-13 at 19.15.09.png
    Screenshot 2021-10-13 at 19.15.09.png
    120.8 KB · Views: 28
Connectors all show 'DP' but you previously stated that you are using HDMI.
 
Snip20211013_1.png

choose your options and click generate patch as already mentioned
 
Connectors all show 'DP' but you previously stated that you are using HDMI.
Maybe is a bug in hackintool. I'm using HDMI
 
Status
Not open for further replies.
Back
Top