Intel HD Graphics Framebuffer Edits - Desktop

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

Doesn't matter the order, the display attached to the DVI port remains black.

Previous problem description was booting with DVI caused reboot/crash. First time you mentioned DVI display black.

Use remote desktop to connect from another computer. Connect and capture ioreg.

If you practice, you can also do it 'blind'.

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

First time you mentioned DVI display black.

Here is my initial problem report:
http://www.tonymacx86.com/graphics/125239-hd4600-hd4000-hd3000-framebuffer-edits-17.html#post1060411

Use remote desktop to connect from another computer.

Great idea. I'll do that.

You're probably patching via config.plist.

I don't have any patch other than the following, which was in the initial config.plist:

<dict>
    <key>Comment</key>
    <string>External icons patch</string>
    <key>Find</key>
    <data>
    RXh0ZXJuYWw=
    </data>
    <key>Name</key>
    <string>AppleAHCIPort</string>
    <key>Replace</key>
    <data>
    SW50ZXJuYWw=
    </data>
</dict>

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

I don't have any patch other than the following, which was in the initial config.plist:

<dict>
    <key>Comment</key>
    <string>External icons patch</string>
    <key>Find</key>
    <data>
    RXh0ZXJuYWw=
    </data>
    <key>Name</key>
    <string>AppleAHCIPort</string>
    <key>Replace</key>
    <data>
    SW50ZXJuYWw=
    </data>
</dict>

Not possible to have HDMI connector type (00 08 00 00) at framebuffer@3 with no patches.

This is connector for @3 in 0x0d220003:

0306 0800 [B]0004 0000 [/B]1100 0000

Before continuing, make sure kext is vanilla and kernel cache is up-to-date.

Note: This is why I recommend to never patch the kext on disk. It will confuse you as you'll forget which patches you applied, and Clover config.plist patches you intend to use will be effective due to Find pattern not being found in the patched binary.

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Before continuing, make sure kext is vanilla...

md5 is right so I think the problem is not in the kext.

...and kernel cache is up-to-date.

Kext Utility says:

Syncing disk cache ... Done.

Is this cache what you were talking about?

I managed to export ioreg with DVI only. File is attached.

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

md5 is right so I think the problem is not in the kext.

...

I managed to export ioreg with DVI only. File is attached.

Now connector type is as expected for vanilla kext (<00 04 00 00>).

So probably before you neglected to rebuild cache...

From here on out, do all patches via config.plist and things will be less confusing.

We'll see what toleda thinks about best course of action (I have no Haswell machines with DVI).

I assume you tried this same monitor on one of the DP ports (via DP->DVI cable/adapter) and it works?

 

[toleda]

HD4600+/HD4000/HD3000 Framebuffer Edits

I managed to export ioreg with DVI only.

Post #162
Is this the DVI Monitor? Monitors & Projectors | VB172D | ASUS Global
No mention of a DVI input

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Is this the DVI Monitor? Monitors & Projectors | VB172D | ASUS Global

No, this one: https://www.asus.com/Monitors_Projectors/VB172T/specifications/

 

[toleda]

HD4600+/HD4000/HD3000 Framebuffer Edits

No, this one:

Link broken.

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Link broken.

Works for me.

[B]PC Input:[/B][COLOR=#333333][FONT=Segoe UI]DVI-D & D-Sub
[/FONT][/COLOR]

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

Attach IOReg.

I sent in PM.