Contribute
Register

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

Status
Not open for further replies.
As described in post #1, "Known Problems", "Audio", it is possible (and somewhat common) for AppleHDA to "fall out of kernel cache". In this case a cache rebuild is needed (after booting without caches).

As a work around for this problem, I added the pre-patch_hda.sh script to the github project. The script reads your config.plist (on your EFI partition) and applies the patches directly to the AppleHDA binary on disk. That way it doesn't matter if Clover fails to patch the kext when it is not in cache.

The script must be run after you have your final config.plist copied to your EFI/Clover on your EFI partition.

Usage:
Code:
cd ~/Projects/probook.git
./pre-patch_hda.sh

You would need to run it after any update (that updated AppleHDA), just as you do for install_downloads.sh.

Note: The reason this is not done from install_downloads.sh at this point is because, in the guide, install_downloads.sh is run prior to having the correct config.plist in place. Also note that if you have the wrong config.plist, the script will patch AppleHDA with the wrong patches. No backup is made, so to restore, you would need to use the OS X/macOS installer.


I recently installed Mac OS Sierra on my HP Probook 4540s having some issues. For now the laptop is up, but I could not get the sound working following the guide until the end with the sound issues. I found this and I tried, but I get no sound yet. And after I run the commands I get errors/warnings that I do not know if it's normal part of the procedure.

Attached screen.

Thanks!
 

Attachments

  • Screen Shot 2017-09-03 at 12.25.27 PM.png
    Screen Shot 2017-09-03 at 12.25.27 PM.png
    258.1 KB · Views: 75
I recently installed Mac OS Sierra on my HP Probook 4540s having some issues. For now the laptop is up, but I could not get the sound working following the guide until the end with the sound issues. I found this and I tried, but I get no sound yet. And after I run the commands I get errors/warnings that I do not know if it's normal part of the procedure.

Attached screen.

Thanks!

Read post #1, "Problem Reporting".
 
Further isolate the problem by using a magnet to close the lid switch without actuality closing the lid.

ok found it . it is located near the power button (not on the lid). what next?
 
ok found it . it is located near the power button (not on the lid). what next?

Activate the lid switch with the magnet (it should attempt sleep in 15-20 seconds, just as Apple->Sleep).
Observe and report the results.
 
There should be a backup that would allow rollback.
You might check into it.



No comparison can be done without both sets.
Sadly, i cannot, tried while on 1.39 with official hp installer for 1.37 and also by creating usb recovery bios key.
Attached ACPI from 1.37. I hae to say i did not check wich state i left his bios DVMT setting. I hope i left it 64 or it does not matter...
 

Attachments

  • origin.zip
    64.9 KB · Views: 58
it does not go to sleep. it makes that sound just like i would have pressed and hold down a key (press F1 on your desktop and hold it that is the sound). and the sound it keeps on going for some time like 15 seconds and then stops, after a minute or so sound comes up again . - all this time the laptop does not sleep .

if i open the switch meanwhile that sound is playing display light's on with the sound keeping rolling and if i press a key on the keyboard the sound stops. (open switch=remove the magnet)
 
it does not go to sleep. it makes that sound just like i would have pressed and hold down a key (press F1 on your desktop and hold it that is the sound). and the sound it keeps on going for some time like 15 seconds and then stops, after a minute or so sound comes up again . - all this time the laptop does not sleep .

You didn't mention it, but I assume this happens after the 15-20 sec delay.
Correct?
(details matter in this game)
 
Sadly, i cannot, tried while on 1.39 with official hp installer for 1.37 and also by creating usb recovery bios key.
Attached ACPI from 1.37. I hae to say i did not check wich state i left his bios DVMT setting. I hope i left it 64 or it does not matter...

No real differences in the two BIOS as far as ACPI except for the additional SSDT in the 1.39 case (may be different options set in BIOS, or different hardware in the laptop).

So the change must be somewhere else. The way BIOS initializes the graphics hardware perhaps. Or just different BIOS settings between the two cases.
 
Status
Not open for further replies.
Back
Top