Intel HD Graphics Framebuffer Edits - Desktop

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

Interesting, Azul/0x0d220003 and AppleHDA/0x80860c0c do not support HDMI audio natively.

FakePCIID fixes HDAU 8086:0c0c, so no surprise there.

But stock DP connector data for HDMI port with working HDMI audio is a bit of a mystery.

 

[toleda]

HD4600+/HD4000/HD3000 Framebuffer Edits

But stock DP connector data for HDMI port with working HDMI audio is a bit of a mystery.

Attach IOReg.

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Post ioreg: http://www.tonymacx86.com/audio/58368-guide-how-make-copy-ioreg.html. Please, use the IORegistryExplorer v2.1 attached to the post! DO NOT reply with an ioreg from any other version of IORegistryExplorer.app.

I find information easier to find in ioreg with v2.1 IORegistryExplorer vs. any other version and vs. IOJones. The RHS properties are alpha sorted.

Specify vanila with patch vs. vanilla.

Vanilla framebuffer data 0x0d220003:

00048360: 0300 220d 0003 0303 0000 0002 0000 3001 (32 MB BIOS-allocated memory, 19 MB frame buffer memory)
00048370: 0000 0000 0000 0060 9914 0000 9914 0000 (0 MB cursor bytes, 1536 MB VRAM, BCL freq. 5273 Hz, max. BCL PWM 5273 Hz)
00048380: 0000 0000 0000 0000 0105 0900 0004 0000 (port 5, DisplayPort connector)
00048390: 8700 0000 0204 0a00 0004 0000 8700 0000 (port 6, DisplayPort connector)
000483a0: [B]0306[/B] 0800 0004 0000 1100 0000 ff00 0000 ([B]port 7[/B], DisplayPort connector / port unused ...
000483b0: 0100 0000 4000 0000 0204 0000 0101 0000  VGA connector)
000483c0: 0400 0000 0000 0000 0e00 0000 0000 0000

Before working via Clover KextsToPatch method, verify md5 of kext.

This is for 10.10.4:

Speedy-OSX:~ RehabMan$ md5 /System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/MacOS/AppleIntelFramebufferAzul 
MD5 (/System/Library/Extensions/AppleIntelFramebufferAzul.kext/Contents/MacOS/AppleIntelFramebufferAzul) = 7c646f5dd6013d22acd7946329bd23e2

Also, you may want to apply patches with the scripts (didn't you mention using toleda's .command scripts -- don't remember the details), then examine the changes with AppleIntelFramebufferAzul.sh. Compare with AppleIntelFramebufferAzu.sh output with vanilla kext. Then you'll understand what the scripts change (I have to admit I've never used them, as I prefer the transparency of Clover config.plist patches).

I attached IORegistryExplorer copy with clean and patched kext.

These are the md5:

• Clean: 7c646f5dd6013d22acd7946329bd23e2
• Patched: c6d65932efa4a716d9b4b1c540205ef3

I used the patch named: graphics_intel_hd5k-azul-g-90_patch.

I'm sorry, where do I find AppleIntelFramebufferAzul.sh?

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

See Clover/Azul patches, config-hdmi_hd4600-100.plist.zip
Use config-hdmi_hd4600-100.plist/KernelAndKextPatches/KextsToPatch/Item 4 (10.10-Azul-Port_0x7-DP2HDMI)
Xcode or PlistEdit Pro/Copy Item 4, Paste to EFI/CLOVER/config.plist
HDMI/DVI connectors are the same
View attachment 142967

I tried this patch over clean kext. Nothing seems to have changed.

The IOReg shows 3 displays connected. Attach an IOReg with only DVI connected.

How? DVI doesn't work.

 

[toleda]

HD4600+/HD4000/HD3000 Framebuffer Edits

I attached IORegistryExplorer

Last request, attach an IOReg with only DVI display connected.

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

I attached IORegistryExplorer copy with clean and patched kext.

These are the md5:

• Clean: 7c646f5dd6013d22acd7946329bd23e2
• Patched: c6d65932efa4a716d9b4b1c540205ef3

I used the patch named: graphics_intel_hd5k-azul-g-90_patch.

Previously mentioned... You can do what you want, but I recommend using only config.plist based patches and leave the files on disk vanilla.

Otherwise you'll confuse yourself. Clover patches are designed to be applied to vanilla kext on disk. If you start changing the kext on disk, the patches in config.plist will not work.

The ioreg seems to show 3 displays connected.

In both files:
connector-type:
framebuffer@0: <00 04 00 00>
framebuffer@1: <00 04 00 00>
framebuffer@2: <00 08 00 00>

In vanilla kext, 0x0d220003, all connectors are DP, so your 'clean' file not so clean at all...

I'm sorry, where do I find AppleIntelFramebufferAzul.sh?

Google can help you find things.

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

..
How? DVI doesn't work.

Think...

Possibilities:
- boot without the DVI display connected (use a different connector)
- unplug other display
- plug DVI display

Or:
- boot without any displays connected
- after booting, plug DVI display

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Previously mentioned... You can do what you want, but I recommend using only config.plist based patches and leave the files on disk vanilla.

I agree. I'm using vanilla kext now. The patch command didn't solve my problem so there is no point in applying it anyway.

In vanilla kext, 0x0d220003, all connectors are DP, so your 'clean' file not so clean at all...

The md5 is correct. I don't know...

@toleda:

The IOReg shows 3 displays connected. Attach an IOReg with only DVI connected.

How? DVI doesn't work.

Last request, attach an IOReg with only DVI display connected.

 

[papagno]

HD4600+/HD4000/HD3000 Framebuffer Edits

Think...

Possibilities:
- boot without the DVI display connected (use a different connector)
- unplug other display
- plug DVI display

Or:
- boot without any displays connected
- after booting, plug DVI display

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

 

[RehabMan]

HD4600+/HD4000/HD3000 Framebuffer Edits

The md5 is correct. I don't know...

You're probably patching via config.plist. Data/results cannot be interpreted without config.plist that corresponds.