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

[RehabMan]

I swear that's what I am using this time.

The config.plist in the files you uploaded (post #118) is config.plist for pre-install.

 

[Mezmaron]

The config.plist in the files you uploaded (post #118) is config.plist for pre-install.

If you are referring to what is in the problem report, of course it is the pre-install one, because that is the only one that allows me to fully boot. I cannot generate a problem report from the one that doesn't allow me to fully boot.

I attached the one that I use that does not allow me to fully boot, the one that resets the computer shortly after the Apple log first appears.

 

[RehabMan]

If you are referring to what is in the problem report, of course it is the pre-install one,

I will not repeat this one more time... (because this is getting old, frustrating, and exceedingly silly).

Setup EFI/Clover on HDD (or SSD) as per guide.
Attempt to boot. Don't forget to press F2 and F4 prior to that attempt.
If it KPs, grab photo.

Then, BOOT WITH YOUR USB! Do not modify your EFI/Clover on HDD (or SSD)!!!
Use that boot session to collect PR files with gen_debug.sh.

Attach resulting debug zip, along with verbose boot photo.

 

[Mezmaron]

I will not repeat this one more time... (because this is getting old, frustrating, and exceedingly silly).

Setup EFI/Clover on HDD (or SSD) as per guide.
Attempt to boot. Don't forget to press F2 and F4 prior to that attempt.
If it KPs, grab photo.

Then, BOOT WITH YOUR USB! Do not modify your EFI/Clover on HDD (or SSD)!!!
Use that boot session to collect PR files with gen_debug.sh.

Attach resulting debug zip, along with verbose boot photo.

Done.

 

[RehabMan]

Done.
View attachment 356151 View attachment 356152

I see you're using the I2C branch (something you should mention, as it is not typical).
Try with current i2c github content (config_master changed, affecting all config/config_*.plist).

Also, try eliminating the framebuffer-cursormem property. It is typically used with ig-platform-id 0x0a260006, but you're using 0x04260000.

And try setting config.plist/ACPI/FixHeaders=true (previously we didn't have any issue that I can remember with ACPI headers in ProBook/EliteBook, but maybe I remember wrong).

If still failing after...
You should use master branch... as I2C should be considered very experimental.

Also try the Clover attached.

 

[Unnamed X]

Hi @RehabMan,

My Zbook 15 G2 runs almost perfectly, except 1 issue:
If I put my built-in display to sleep it will not wake up (black screen, no backlight) until the first computer sleep. After that, the display sleep will work, everything else works perfect. External display doesn't have this issue.

Here's my files, thank you.

Bump up. Still need help.

 

[RehabMan]

Hi @RehabMan,

My Zbook 15 G2 runs almost perfectly, except 1 issue:
If I put my built-in display to sleep it will not wake up (black screen, no backlight) until the first computer sleep. After that, the display sleep will work, everything else works perfect. External display doesn't have this issue.

Here's my files, thank you.

Your Clover bootlog shows no Intel graphics device:

0:100  0:000  === [ GetDevices ] ========================================
0:100  0:000  PCI (00|00:00.00) : 8086 0C04 class=060000
0:100  0:000  PCI (00|00:01.00) : 8086 0C01 class=060400
0:100  0:000  PCI (00|01:00.00) : 1002 6821 class=030000
0:100  0:000   - GFX: Model=AMD Radeon HD 7700 Series (ATI/AMD)
0:100  0:000  PCI (00|01:00.01) : 1002 AAB0 class=040300
0:100  0:000   - HDMI Audio:
0:100  0:000  PCI (00|00:14.00) : 8086 8C31 class=0C0330
0:100  0:000  PCI (00|00:16.00) : 8086 8C3A class=078000
0:100  0:000  PCI (00|00:16.01) : FFFF FFFF class=FFFFFF
0:100  0:000  PCI (00|00:19.00) : 8086 153A class=020000
0:100  0:000   - LAN: 0 Vendor=Intel
0:100  0:000  PCI (00|00:1A.00) : 8086 8C2D class=0C0320
0:100  0:000  PCI (00|00:1B.00) : 8086 8C20 class=040300
0:100  0:000  PCI (00|00:1C.00) : 8086 8C10 class=060400
0:100  0:000  PCI (00|00:1C.06) : 8086 8C1C class=060400
0:100  0:000  PCI (00|3B:00.00) : 12D8 2404 class=060400
0:100  0:000  PCI (00|3C:01.00) : 12D8 2404 class=060400
0:100  0:000  PCI (00|3D:00.00) : 14E4 43B1 class=028000
0:100  0:000   - WIFI: Vendor=Broadcom
0:100  0:000  PCI (00|3C:02.00) : 12D8 2404 class=060400
0:100  0:000  PCI (00|3C:03.00) : 12D8 2404 class=060400
0:100  0:000  PCI (00|5F:00.00) : 10EC 5249 class=FF0000
0:100  0:000  PCI (00|00:1D.00) : 8086 8C26 class=0C0320
0:100  0:000  PCI (00|00:1F.00) : 8086 8C4F class=060100
0:100  0:000  PCI (00|00:1F.02) : 8086 8C03 class=010601
0:100  0:000  PCI (00|00:1F.03) : 8086 8C22 class=0C0500

As written in the first sentence of the guide, this guide applies to only those laptops with Intel IGPU.

I have highlighted the specific text you seemed to have skipped reading:

The purpose of this guide is to provide a step-by-step guide to installing Mojave, High Sierra, Sierra, El Capitan, or Yosemite on the ProBook/EliteBook/Zbook equipped with Intel graphics.

 

[Mezmaron]

I see you're using the I2C branch (something you should mention, as it is not typical).
Try with current i2c github content (config_master changed, affecting all config/config_*.plist).

Also, try eliminating the framebuffer-cursormem property. It is typically used with ig-platform-id 0x0a260006, but you're using 0x04260000.

And try setting config.plist/ACPI/FixHeaders=true (previously we didn't have any issue that I can remember with ACPI headers in ProBook/EliteBook, but maybe I remember wrong).

If still failing after...
You should use master branch... as I2C should be considered very experimental.

Also try the Clover attached.

Wow... thank you so much. It was the i2c thing. I wiped out my Projects folder and started anew, this time omitting i2c and using the master branch, and it is now booting. It worked both before and after trying the newer Clover you posted.

I apologize for overlooking the fact that I used the i2c branch, and causing so much frustration. When I was first going through the guide and came across that, I could not find what kind of trackpad I had, and incorrectly thought that it would do no harm if I ran that command and didn't actually have that kind of trackpad. Afterwards, I overlooked the fact that I had made that choice.

The only things not working now, is that I have no brightness control. And when I unplug the AC adaptor, everything stays bright.

Not a huge issue, but if you would like to take a stab at it, I attached my latest PR. It should reflect the current status, including the newer Clover you posted.

 

[RehabMan]

Wow... thank you so much. It was the i2c thing. I wiped out my Projects folder and started anew, this time omitting i2c and using the master branch, and it is now booting. It worked both before and after trying the newer Clover you posted.

I apologize for overlooking the fact that I used the i2c branch, and causing so much frustration. When I was first going through the guide and came across that, I could not find what kind of trackpad I had, and incorrectly thought that it would do no harm if I ran that command and didn't actually have that kind of trackpad. Afterwards, I overlooked the fact that I had made that choice.

The only things not working now, is that I have no brightness control. And when I unplug the AC adaptor, everything stays bright.

Not a huge issue, but if you would like to take a stab at it, I attached my latest PR. It should reflect the current status, including the newer Clover you posted.

Brightness control should be working once you rebuild cache and reboot (it uses a Clover patch that can operate only on kexts in kernel cache, and initially AppleBacklight is not in cache).

Note: You should remove the VoodooI2C*, VoodooGPIO* kexts:

Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a048a5e50 [0x7fff8b8798e0]> { URL = "VoodooI2C.kext/ -- file:///Library/Extensions/", ID = "com.alexandred.VoodooI2C" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a048a4090 [0x7fff8b8798e0]> { URL = "VoodooGPIO.kext/ -- file:///Library/Extensions/VoodooI2C.kext/Contents/PlugIns/", ID = "org.coolstar.VoodooGPIO" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a048b6d00 [0x7fff8b8798e0]> { URL = "VoodooI2CServices.kext/ -- file:///Library/Extensions/VoodooI2C.kext/Contents/PlugIns/", ID = "com.alexandred.VoodooI2CServices" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a04857890 [0x7fff8b8798e0]> { URL = "VoodooI2CHID.kext/ -- file:///Library/Extensions/", ID = "com.alexandred.VoodooI2CHID" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a047678c0 [0x7fff8b8798e0]> { URL = "VoodooI2CUPDDEngine.kext/ -- file:///Library/Extensions/", ID = "com.blankmac.VoodooI2CUPDDEngine" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a0486b100 [0x7fff8b8798e0]> { URL = "VoodooI2CFTE.kext/ -- file:///Library/Extensions/", ID = "me.kishorprins.VoodooI2CFTE" }
Kext with invalid signatured (-67050) allowed: <OSKext 0x7f8a0486e500 [0x7fff8b8798e0]> { URL = "VoodooI2CELAN.kext/ -- file:///Library/Extensions/", ID = "me.kishorprins.VoodooI2CELAN" }

Note to those with I2C laptops: You need to figure out which I2C kexts your laptops actually need. Seems like there are many in that package and probably not all of them are supposed to be installed. For you with the I2C hardware to provide feedback...

 

[Mezmaron]

Brightness control should be working once you rebuild cache and reboot (it uses a Clover patch that can operate only on kexts in kernel cache, and initially AppleBacklight is not in cache).

Note: You should remove the VoodooI2C*, VoodooGPIO* kexts:

The brightness control is back. However, since I can't leave sh*t alone, I was tinkering around and tried something else before I saw your reply.

Since my 850 G1 has a 1920x1080 screen, I got the idea of using the IGPUH.aml instead of the IGPU.aml. I rebooted, and I then had brightness control. Sorry if this poisons the well for the results a bit, although I understand this may just be a coincidence and it's not related at all, and the kext cache may have just refreshed itself after a few reboots. But, speaking of IGPU vs IGPUH, shouldn't my system be using the IGPUH.aml anyway? Just curious- Was it thought that these models only came with lower-res screens, hence why there is no "install_8x0g1_haswell_hires" option for the install_acpi.sh script? Other than the unproven possibility that this enabled my backlight, there's really no difference that I can discern, not even on the Clover boot screen. Is it only relevant to the early boot process, for hardware that may have that resolution available for UEFI screens?

Also, FYI, I was tinkering around with another setting, and tried enabling the "Enable TRIM for non-Apple SSDs" to see if I got the negative side-effects. I definitely experienced the slower boot. The battery status looked normal. But, I lost the brightness control. Disabling that and rebooting brought it back. Just figured I'd mention this in case that side-effect was unknown before, since it wasn't mentioned in the guide.

Thanks again!