Contribute
Register

ProBook Intel HD 4000 script, for external display...

Status
Not open for further replies.
before my 4540s i7 ml Intel HD Graphics 4000 512 MB now Mavericks Intel HD Graphics 4000 1024 MB is normal ?
Yup, completely normal. Apple changed their approach, now they don't assign a fixed amount of ram to the iGPU, but assign it dynamically according to needs. So that 1GB that you see is only the upper limit and not the actual amount of ram that is assigned to the graphic chip.
 
BTW riyadku, would you mind sharing with us what kext are you using and if hdmi/audio works.
 
BTW riyadku, would you mind sharing with us what kext are you using and if hdmi/audio works.
i checked last night hdmi/audio works 100 ok :headbang:ProBook Installer 6.1.9
 

Attachments

  • AppleIntelFramebufferCapri.kext.zip
    186.2 KB · Views: 143
i checked last night hdmi/audio works 100 ok :headbang:ProBook Installer 6.1.9
Ok, thx.
Note to self:
So you are using a low-res, therefore platform 01660003... there are no changes for the 01660003 in the newer version of the script.

There will be one noticeable difference when using the old script on 01660004, the VRAM will be 512MB.
 
KpKp Can You Give good Kext for AppleIntelFramebufferCapri.kext
 
KpKp Can You Give good Kext for AppleIntelFramebufferCapri.kext
What you mean, you just said it works fine for you?

You can try the one form the first post, that is the 10.9 patched version.
 
It has been working fine with full sleep and etc but this masage will come what i need du now ?
 

Attachments

  • Screen Shot 2013-10-24 at 8.57.48 PM.png
    Screen Shot 2013-10-24 at 8.57.48 PM.png
    35 KB · Views: 198
Not that simple...Find:
x04\x00\x00\x81.{107}\x04\x00\x66\x01.{108} (where .{107} & .{108} mean 107/108 bits of any value) and replace with
0x08000006000000000000000002001100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004006601010204020000000400000001000000401007000010070000000000000000000000000000000000000000000005030000020000003002000002050000000400000704000003040000000400008100000004060000000800000600000000000000000200110000000000000000

You can see in IORegistryExplorer if search for appleintelframebuffer, if the patch worked you should see 4 of them otherwise just 1.

Looks like another kernel patch type is in order to implement this search pattern.
Another UINTN SearchAndReplace(UINT8 *Source, UINT32 SourceSize, UINT8 *Search, UINTN SearchSize, UINT8 *Replace, INTN MaxReplaces) implementation is needed in Clover source code to handle this type of logic.

I think there are multiple occurrences with different content in between known bits, so "brutal force" approaches would not work.

It may take a while...
 
Looks like another kernel patch type is in order to implement this search pattern.
Another UINTN SearchAndReplace(UINT8 *Source, UINT32 SourceSize, UINT8 *Search, UINTN SearchSize, UINT8 *Replace, INTN MaxReplaces) implementation is needed in Clover source code to handle this type of logic.

I think there are multiple occurrences with different content in between known bits, so "brutal force" approaches would not work.

It may take a while...
I can create a "hardcoded" version if you want, with no "abstract" bytes, the only downside will be that it will work only on 10.9 (in this case) and is more likely to not work with the future Apple updates (&and is gonna be one long patch).

"bits" or "bytes"??
Definitely bytes :silent:.
 
Status
Not open for further replies.
Back
Top