Contribute
Register

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

Status
Not open for further replies.
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...

Logic that will take "modified hex" in Find and Replace and leave it as-is, then pass it to new HexSearchAndReplace().
The format could be used in both Find and Replace data:
Sample:
04000081.{107}04006601.{108}

04000081...04006601.{108} equal to 04000081.{3}04006601.{108}

New HexSearchAndReplace() would traverse the Source Hex-by-Hex and if it finds '.' it will accept any byte. if following is "{" then it will parse count out of the Source and skip "}" and skip "count-1" in check logic (already skipped one byte when it saw '.'). Same thing for "Replace" logic(so it could accommodate really crazy update scenarios).
 
If it is any help
Code:
[COLOR=#000000]04000081.{107}04006601.{108}[/COLOR]
=
Code:
04 00 00 81 00 00 00 00 00 00 00 00 02 00 11 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 00 66 01 01 03 01 01 00 00 00 02 00 00 00 01 00 00 00 40 10 07 00 00 10 07 00 00 00 00 00 00 70 36 05 00 00 00 00 00 00 00 00 00 00 00 00 00 05 03 00 00 02 00 00 00 30 02 00 00 00 00 00 00 01 00 00 00 40 00 00 00 00 00 00 00 01 00 00 00 40 00 00 00 00 00 00 00 01 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

For 10.9.0.

An Intel HD4000 user enabled graphics output by taking AppleIntelGraphicsFB from PBI. Any idea?
http://www.tonymacx86.com/hp-probook-mavericks/112925-hp-elitebook-2570p-success.html
If by AppleIntelGraphicsFB he means AppleIntelFramebufferCapri, then that is normal, since the kexts are probably still compatible. But don't count on the VGA out.
 
We have a second difference for the Ivy ProBooks (the first was the AppleRTC.kext patch). Is this patch the same as your previous for ML?

I have loaded attached kext and tested HDMI - works fine.

Not sure about AppleRTC patches you mentioned for 4x40s. I have noticed after PBI 6.1.9 my 4440s was a little agitated with going to sleep. I since restored Apple original AppleRTC.kext and rely on Clover to patch AppleRTC on the fly. It is going to sleep like swiss clockwork now. My 4440s was particularly stubborn with going to sleep on ML, so I relied on PleaseSleep to put it to sleep reliably. But on Maverick it is working without any help. My other 4540s sleep fine on ML though without any help, but I did not upgrade 4540s to Maverick yet.
 
I have loaded attached kext and tested HDMI - works fine.
Can you specify what resolution does the tested Probook use or specify with platform-ID you use, thx. I assume is the low-res 4440s you are talking about, so platform-id 03006601.
 
Can you specify what resolution does the tested Probook use or specify with platform-ID you use, thx. I assume is the low-res 4440s you are talking about, so platform-id 03006601.

I tried with and without mirroring + HDMI sound. All works.

<key>Graphics</key>
<dict>
<key>DualLink</key>
<integer>0</integer>
<key>ig-platform-id</key>
<string>0x01660003</string>
<key>Inject</key>
<dict>
<key>Intel</key>
<true/>
</dict>
</dict>
 
I have loaded attached kext and tested HDMI - works fine.

Not sure about AppleRTC patches you mentioned for 4x40s. I have noticed after PBI 6.1.9 my 4440s was a little agitated with going to sleep. I since restored Apple original AppleRTC.kext and rely on Clover to patch AppleRTC on the fly. It is going to sleep like swiss clockwork now. My 4440s was particularly stubborn with going to sleep on ML, so I relied on PleaseSleep to put it to sleep reliably. But on Maverick it is working without any help. My other 4540s sleep fine on ML though without any help, but I did not upgrade 4540s to Maverick yet.

It is probably not a good idea to patch both on disk and use also Clover's patching. Pick one (on disk or on-the-fly) and use only that method.
 
Two external monitors on Mavericks, anyone?

Has anyone managed to get working configuration with two external monitors on Mavericks?
Only one external monitor is working for me.


I have Clover + Mountain Lion installed with ig-platform-id 01660009 where all works fine. Two external monitors or LVDS and one external monitor at any given time.


But on Mavericks only one external monitor is working.
With laptop lid open I have LVDS + external monitor, with lid closed only one external monitor.


ML and Mavericks environment is as close as possible.
The same DSDT;
The same Clover version (2236);
Almost the same Clover configuration (no changes regarding Display and SMBios, actually just TRIM patch added).


I patched Mavericks AppleIntelFramebufferCapri with the same string as for Mountain Lion:
05 03 00 00 02 00 00 00 30 02 00 00 02 05 00 00 00 04 00 00 07 01 00 00 03 04 00 00 00 04 00 00 07 01 00 00

The last output, starting with 03 04 … is working, but the middle one, with 02 05 is not.
Of course if I switch 02 05 with 03 04 then the other monitor gets display. Tried also 04 06 …, no joy.
One thing I noticed with IOReg is that on Mavericks there are two ports with connector-type 02 (?).
Mountain Lion has two ports with connector-type value 04 which seems right.


Please share your thoughts.
IOReg info linked here.
 
Interesting stuff...
First thing I would try is change the code in 10.9 kext:
Code:
09 00 66 01 01 03 03 03 00 00 00 04 00 00 00 0100 00 00 40 10 07 00 00 10 07 00 00 00 00 00 00
00 00 00 00 00 00 00 00 [B]60 36 05[/B] 00 00 00 00 00

to match the one in 10.8:
Code:
09 00 66 01 01 03 03 03 00 00 00 04 00 00 00 0100 00 00 20 10 07 00 00 10 07 00 00 00 00 00 00
00 00 00 00 00 00 00 00 [B]F0 D9 05[/B] 00 00 00 00 00

Idk what it means but is worth a shot.
Or even before that, just try an old 10.8 kext?
 
Status
Not open for further replies.
Back
Top