[Guide] HP ProBook/EliteBook/Zbook using Clover UEFI hotpatch (10.11)

[RehabMan]

Tried this didn't work for me

You may have some other mistake.
Read post #1, "Problem Reporting".
And... there are versions of Clover (on sourceforge) that do have boot without caches...

Don't forget to fill out your profile properly (as requested in the guide). Your current profile lacks several details...

 

[kecinzer]

Your config.plist is corrupt. Read post #1, "Final config.plist".

Can you please be more specific? What is corrupted? Only thing I did after finalize configuration is, that I added serial numbers to it and changed Theme and boot device to previusly selected one.

 

[RehabMan]

Can you please be more specific? What is corrupted?

You will notice if you try and open it with a plist editor (Xcode or PlistEdit Pro). Clearly, you edited it with a text editor and damaged the syntax.

I just checked and post #1 very specifically advises to use only a plist editor when making changes to your config.plist.

Note:

SPEEDY-NUC:~ rehabman$ plutil -lint /Users/rehabman/Downloads/keciPB/CLOVER/config.plist
/Users/rehabman/Downloads/keciPB/CLOVER/config.plist: Value missing for key inside <dict> at line 844

 

[kecinzer]

You will notice if you try and open it with a plist editor (Xcode or PlistEdit Pro). Clearly, you edited it with a text editor and damaged the syntax.

I just checked and post #1 very specifically advises to use only a plist editor when making changes to your config.plist.

Note:

SPEEDY-NUC:~ rehabman$ plutil -lint /Users/rehabman/Downloads/keciPB/CLOVER/config.plist
/Users/rehabman/Downloads/keciPB/CLOVER/config.plist: Value missing for key inside <dict> at line 844

Ah, thank you for explanation.
And you think that after I fix it, my DP port start working?

 

[RehabMan]

Ah, thank you for explanation.
And you think that after I fix it, my DP port start working?

Predicting the future is not a skill I have. I have some ideas for your DP port, but need a valid setup first. Also, your problem may be device specific.

 

[kecinzer]

Predicting the future is not a skill I have. I have some ideas for your DP port, but need a valid setup first. Also, your problem may be device specific.

Ok, I fixed my config.plist, now when I run command that you mentioned, its ok.

plutil -lint config.plist
config.plist: OK

 

[RehabMan]

Ok, I fixed my config.plist, now when I run command that you mentioned, its ok.

plutil -lint config.plist
config.plist: OK

If you still have an issue, must provide files as requested post #1, "Problem Reporting".

 

[kecinzer]

If you still have an issue, must provide files as requested post #1, "Problem Reporting".

Problem with DP is still here .
Attaching latest file.

 

[RehabMan]

Problem with DP is still here .
Attaching latest file.

Try these two patches (add to config.plist/KernelAndKextPatches/KextsToPatch).
Use a plist editor.

patch #1:
Comment: DP-delay port 0105(12), 0x0a260005 0x0a260006, 0x0d220003, 0x0a2e000a, 0x0a26000a
Find: <01050900 00040000 87000000>
Replace: <01051200 00040000 87000000>
Name: com.apple.driver.AppleIntelFramebufferAzul

patch #2:
Comment: DP-delay, port 0204(12), 0x0a260005 0x0a260006
Find: <02040900 00040000 87000000>
Replace: <02041200 00040000 87000000>
Name: com.apple.driver.AppleIntelFramebufferAzul

Reply with "Problem Reporting" files, as always.

If not working, test with a different monitor...

Note: I don't know why you stated previously that you patched the framebuffer kext for 16mb framebuffer size. Your kextcache output shows no evidence of that.

 

[kecinzer]

Try these two patches (add to config.plist/KernelAndKextPatches/KextsToPatch).
Use a plist editor.

patch #1:
Comment: DP-delay port 0105(12), 0x0a260005 0x0a260006, 0x0d220003, 0x0a2e000a, 0x0a26000a
Find: <01050900 00040000 87000000>
Replace: <01051200 00040000 87000000>

patch #2:
Comment: DP-delay, port 0204(12), 0x0a260005 0x0a260006
Find: <02040900 00040000 87000000>
Replace: <02041200 00040000 87000000>

Reply with "Problem Reporting" files, as always.

If not working, test with a different monitor...

Note: I don't know why you stated previously that you patched the framebuffer kext for 16mb framebuffer size. Your kextcache output shows no evidence of that.

Thank you a lot. Trying it right now.
I don't know what you mean about 16MB framebuffer kext?