Contribute
Register

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

Status
Not open for further replies.
The github project has been updated with the changes needed to SSDT-USB-8x70.dsl.

Please test (now all ports should work without -uia_ignore_rmcf).

Perfect all usb Port run without problem without -uia_ignore_rmcf

Many thanks
 
Hi, I have a problem on Windows that makes me think OS X is the source of this problem, let me explain :

When I installed OS X for the first time, I also installed Windows 10 and Linux Mint. From this moment, I started to have touchpad issues on Windows. When I scroll, sometimes it will works properly, sometimes it will zoom/unzoom, and most of the time it will do nothing. To partially solve it, I have to put Windows in sleep mode and wake it and then it will works properly.

After a few months, I had a problem with Linux that forced me to reinstall all my operating systems, and as I had a problem with the installation of OS X, I skipped it and only reinstalled Windows and Linux.

From this moment, the problem was gone. But yesterday, I took the time to reinstall OS X, then I reinstalled Windows and the problem was back.

So I guess the problem is related to OS X, I don't see how and why but that's my only explanation... And I still haven't been able to really solve it so if you have any idea...
 
Hi, I have a problem on Windows that makes me think OS X is the source of this problem, let me explain :

When I installed OS X for the first time, I also installed Windows 10 and Linux Mint. From this moment, I started to have touchpad issues on Windows. When I scroll, sometimes it will works properly, sometimes it will zoom/unzoom, and most of the time it will do nothing. To partially solve it, I have to put Windows in sleep mode and wake it and then it will works properly.

After a few months, I had a problem with Linux that forced me to reinstall all my operating systems, and as I had a problem with the installation of OS X, I skipped it and only reinstalled Windows and Linux.

From this moment, the problem was gone. But yesterday, I took the time to reinstall OS X, then I reinstalled Windows and the problem was back.

So I guess the problem is related to OS X, I don't see how and why but that's my only explanation... And I still haven't been able to really solve it so if you have any idea...

Compare cold boot into Windows to warm boot into Windows after running OS X (eg. restart from OS X into Windows).
Also compare EC reset cold boot to above...

Also, read post #1, "Problem Reporting".

--

Your profile is not filled out as requested in the guide. Please fix.

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

Mobo: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
Mobo: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.

Note: When specifying your bootloader, if using Clover legacy, please be sure to specify "Clover legacy"). Specifying "Clover" will be assumed as "Clover UEFI"
 
Rehabman I did load the kext using kext wizard and now I have kernel panic and boot loop... any ideas
 
Rehabman I did load the kext using kext wizard and now I have kernel panic and boot loop... any ideas

No idea what you mean by "the kext".
And I don't see where you attached the photo of the KP.

If you're referring to the FakeSMC sensor kexts (plural), probably FakeSMC_CPUSensors.kext does not support your CPU.

Remove it.

Had you filled out your profile prior to asking the question (as requested in the guide), I probably would have mentioned the fact that CPUSensors may not support your CPU...
 
I don't see where you attached the photo of the KP.
Probably FakeSMC_CPUSensors.kext does not support your CPU. Remove it.
I don't know how I've tried save mode boot without kext everything..
 

Attachments

  • 1472745865444.jpg
    1472745865444.jpg
    42.2 KB · Views: 111
I don't know how I've tried save mode boot without kext everything..

No panic shown there.
You will need to remove the kexts via Terminal in the OS X installer (or recovery), then rebuild cache...
Or you can fresh install.
 
No panic shown there.
You will need to remove the kexts via Terminal in the OS X installer (or recovery), then rebuild cache...
Or you can fresh install.
I can boot in recovery yes could you tell me the command to use it terminal pleaee
 
Status
Not open for further replies.
Back
Top