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

[RehabMan]

AppSore, but originally was installed with using Unibeast.

My guide does not use Unibeast.

It seems that new drivers in drivers64UEFI were added after updating Clover. But what is wrong with empty CLOVER/kexts ?)

Suggest you remove the extra files in drivers64UEFI.
Proper content in EFI/Clover/kexts/Other will be required to boot the recovery partition or the installer in update scenarios.

 

[Angoo]

Make sure BIOS is up-to-date.

Is updated

What do you mean by "logo glitch"? (that could mean one of two different things).

I posted image here

 

[RehabMan]

I posted image here

I answered your (off-topic) post at that thread.

 

[Angoo]

You might need to debug your _LID device in DSDT.
Look at your system log for clues as to why it is not sleeping (or is it instantly waking?)

Found algorithm: close LID, open LID (display with brightness 0 now), increase brightness level by keys, close LID the second time and now laptop will sleep after ~20 sec

 

[RehabMan]

Found algorithm: close LID, open LID (display with brightness 0 now), increase brightness level by keys, close LID the second time and now laptop will sleep after ~20 sec

You should probably debug your _LID method to see if it is returning the correct values per ACPI spec.
Does display sleep work correctly? (Apple->Sleep, followed by immediate press of any key).

 

[Angoo]

Does display sleep work correctly? (Apple->Sleep, followed by immediate press of any key).

Yes, all work correctly with Apple->Sleep. Where can I read about debugging?

Method is such now:

        Device (LID)
        {
            Name (_HID, EisaId ("PNP0C0D"))  // _HID: Hardware ID
            Method (_LID, 0, NotSerialized)  // _LID: Lid Status
            {
                Store (^^PCI0.LPCB.EC0.CLID, Local0)
                Return (Local0)
            }
        }

 

[RehabMan]

Yes, all work correctly with Apple->Sleep. Where can I read about debugging?

Method is such now:

        Device (LID)
        {
            Name (_HID, EisaId ("PNP0C0D"))  // _HID: Hardware ID
            Method (_LID, 0, NotSerialized)  // _LID: Lid Status
            {
                Store (^^PCI0.LPCB.EC0.CLID, Local0)
                Return (Local0)
            }
        }

You can use ACPIDebug.kext to debug it (it is on my github site, documented in README).
Hopefully you have some programming experience.

 

[Der-3]

Thank you for your guide and the awesome work !
I have a 99% working EliteBook 840 G3 on 10.12.2 for my daily use
(just waiting for my compatible Broadcom Wifi/Bluetooth chipset )

 

[VioletDragon]

Rumor has it that the internal display controller might not be capable of displaying 1920x1080, not sure how to determine this.

FWIW here is a 40pin to 30pin adapter and here is a couple of 1920x1080 displays (one LED and one IPS) if anyone wants to try it.

I cant see a controller to be the issue. LVDS connector supports Dual Link as some models comes with 1600x900. 1920x1080 should work but its just finding the screen.

 

[zul_akmar85]

Hi Rehabman. Need your help one more time. I've been using my machine for almost a week now. I notice that my laptop's feels a bit warmer while on osx + plus the battery will only last less than 3hours. Windows10 last a lot longer, approximately 6hours and feels less warm. My usage is almost the same between these OSes. I have QUITE fan kext installed. Is this behaviour is expected?