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

[meltman]

The 840 G3 is supported (config_8x0_G3_Skylake.plist, install_8x0g3_skylake).

Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).

Thanks, Didn't realize it was supported (isn't shown on front page of this thread).

It was FakeSMC - I overlooked that.

What are your thoughts on a Zbook Studio G3 compatibility?
i7-6820HQ
CM236 Chipset
NVidia Quadro M1000M
intel i219-LM ethernet
Thunderbolt 3

I can gather the data from one of these if you're interested. I know the NVIDIA card will probably be a deal-breaker though.

 

[RehabMan]

Thanks, Didn't realize it was supported (isn't shown on front page of this thread).

Comes under category "100-series"...

What are your thoughts on a Zbook Studio G3 compatibility?
i7-6820HQ
CM236 Chipset
NVidia Quadro M1000M
intel i219-LM ethernet
Thunderbolt 3

I can gather the data from one of these if you're interested. I know the NVIDIA card will probably be a deal-breaker though.

Depends on details. We haven't seen a Zbook G3 here yet.

 

[freeweber]

So.. .according to ioreg, you have two USB3 ports (SSP7/SSP8). Do you know the location of these two ports? There appears to be a USB2 port (HP22) as well (location?).

No WWAN installed, so I might have to guess about that port...

Added prelim support in SSDT-USB-8x70.dsl. Some comments regarding locations might be off (they came from the SSDT-USB-6x70.dsl). Please test.

Sure, the two usb 3.0 ports are on the left side of the laptop and the usb 2.0 port is on the right port (always on for charging..). I tested the file and it worked .

Back to my problem with the slow booting time. I deleted the IntelBacklight.kext and the booting time is still very long. So I looked into the system.log and found this:

Spoiler

"Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.trustd.agent): The ServiceIPC key is no longer respected. Please remove it.
Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.TrustEvaluationAgent): This key does not do anything: OnDemand
Jun 22 22:05:44 Georgs-MacBook-Pro launchd[1]: BUG in libdispatch: 15F34 - 1718 - 0x0
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: timed out waiting for IOKit to quiesce
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: Busy services :
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2 [1, 62472 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert [1, 62384 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0 [1, 62269 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 62207 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2 [2, 58705 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelCapriController [!matched, 1, 28645 ms]
..."

So there is a 18 seconds gap between:
Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.TrustEvaluationAgent): This key does not do anything: OnDemand
and
Jun 22 22:05:44 Georgs-MacBook-Pro launchd[1]: BUG in libdispatch: 15F34 - 1718 - 0x0

Have anybody seen this error before?
Thanks!

 

[RehabMan]

Sure, the two usb 3.0 ports are on the left side of the laptop and the usb 2.0 port is on the right port (always on for charging..). I tested the file and it worked .

Back to my problem with the slow booting time. I deleted the IntelBacklight.kext and the booting time is still very long. So I looked into the system.log and found this:

Spoiler

"Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.trustd.agent): The ServiceIPC key is no longer respected. Please remove it.
Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.TrustEvaluationAgent): This key does not do anything: OnDemand
Jun 22 22:05:44 Georgs-MacBook-Pro launchd[1]: BUG in libdispatch: 15F34 - 1718 - 0x0
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: timed out waiting for IOKit to quiesce
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: Busy services :
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2 [1, 62472 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert [1, 62384 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0 [1, 62269 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 62207 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2 [2, 58705 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelCapriController [!matched, 1, 28645 ms]
..."

So there is a 18 seconds gap between:
Jun 22 22:05:26 Georgs-MacBook-Pro com.apple.xpc.launchd[1] (com.apple.TrustEvaluationAgent): This key does not do anything: OnDemand
and
Jun 22 22:05:44 Georgs-MacBook-Pro launchd[1]: BUG in libdispatch: 15F34 - 1718 - 0x0

Have anybody seen this error before?
Thanks!

The problem is shown here:

Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: timed out waiting for IOKit to quiesce
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]: Busy services :
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2 [1, 62472 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2/AppleACPIPlatformExpert [1, 62384 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0 [1, 62269 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1, 62207 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2 [2, 58705 ms]
Jun 22 22:05:46 Georgs-MacBook-Pro configd[50]:   MacBookPro9,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelCapriController [!matched, 1, 28645 ms]

The "timed out waiting for IOKit to quiesce" means a start/probe in a kext is hung up waiting, and the system only gives a approx 60 seconds for that to resolve. (hence the 62384, 62269, 62207ms...). After the timeout, it cancels...

You can see it is hanging up in the IGPU related matching/starting...

It is because your laptop has no IMEI on the PCI bus (8086:1e3a, I searched in ioreg) ... you can confirm in Linux with 'lspci -nn'.

OS X requires IMEI. It is a motherboard/firmware flash/defective hardware sort of thing. You can try reflashing BIOS or looking online for a way to reflash IMEI firmware (or install Windows including IMEI driver to see if it fixes), but often it means motherboard replacement.

 

[robertashraf]

I have a question, RehabMan, if I installed windows 10 through parallels Desktop on a Hackintosh with no wifi working for OSX (incompatible wifi), will it work on windows or not? Thank you very much in advance!

 

[RehabMan]

I have a question, RehabMan, if I installed windows 10 through parallels Desktop on a Hackintosh with no wifi working for OSX (incompatible wifi), will it work on windows or not? Thank you very much in advance!

I've never tried that specific scenario (WiFi is working on my hacks).

Plus, I don't really care for "what if" questions, as it calls for predicting the future, which is impossible.

 

[robertashraf]

I've never tried that specific scenario (WiFi is working on my hacks).
Plus, I don't really care for "what if" questions, as it calls for predicting the future, which is impossible.

Okaay, my question was to be exact, if anything not working on osx (for another example the internal sd card reader) will it work on windows with parallels desktop? Just asking from your experience

 

[Krazy-Killa]

Okaay, my question was to be exact, if anything not working on osx (for another example the internal sd card reader) will it work on windows with parallels desktop? Just asking from your experience

Just like with any OS (OSX, Windows, Linux, or even VMware vSphere [ESX(i)]), if the host OS is not able to recognize a specific piece of hardware (SD Card Reader, WiFi, Bluetooth, HDD, etc), then it will not be recognized inside a virtualized environment as that hardware HAS to be detected and recognized by the host OS before hand.

 

[RehabMan]

Okaay, my question was to be exact, if anything not working on osx (for another example the internal sd card reader) will it work on windows with parallels desktop? Just asking from your experience

I haven't tested that either... Problem is I don't think much of running systems in a VM.. it is just too slow for the desktop scenario (server is a different thing..)

 

[Titanius]

Hello RehabMan,

Problems with my 650 G1 Haswell

after Sleep the internal Display work but the external Display not working (no Picture) but it´s in Display Settings aktive
after deep Sleep the Displays (internal and external on DisplayPort) are Black (no Picture) that i must Power off and restart.

The ssdt´s, config, and kext are updated today but the Problem are the same