Contribute
Register

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

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,933
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Ok, done.

I'm trying to make a patch for battery status: according your guide I made DSDT patch: split all 16 (do not have 32 or more) bit variables into pairs of 8bit ones. But no luck. In system log I see errors about variables I change:
kernel: (AppleACPIPlatform) ACPI Error:
kernel: (AppleACPIPlatform) [BDC0]
kernel: (AppleACPIPlatform) Namespace lookup failure, AE_ALREADY_EXISTS
kernel: (AppleACPIPlatform) (20140828/dsfield-2d8)

What I'm doing wrong ?

Follow post #1 as written.
 
Joined
May 29, 2012
Messages
5
Motherboard
HP ProBook 450G5 2VP38EA-Clover
CPU
i5 8250U
Graphics
HD 620 1920x1080
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. iOS
Follow post #1 as written.
I did. After os x install it boots, then (after downloading and installing all patches) - kernel panic somewhere in USB init or later, I can't recognise where. My notebook is not in list - it is new model, hardware may differ (it have NGFF wifi instead of minipci-e) , I choose config_4x0_G5_Kabylake-R.plist and SSDT-450G1h.aml or SSDT-4x0G4k.aml. SMIBIOS is probook 14,1 .

BTW, your install stuff need some modifications: if I install 10.12 (I like HFS and so on), there is no HFS driver installed in bootloader, more than it is disabled in config:
Code:
        <key>DisableDrivers</key>
        <array>
                <string>VBoxHfs</string>
        </array>

Without any SSDT patches all works ok, but no battery status. I carefully follow instruction to get battery work: patched DSDT, but it does not help.
 
Joined
May 29, 2012
Messages
5
Motherboard
HP ProBook 450G5 2VP38EA-Clover
CPU
i5 8250U
Graphics
HD 620 1920x1080
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. iOS
The files you attached in post #509 prove you did not.
Sure, because I'd like to get my notebook work. I repeat: if I do all from post #1 - it won't boot at all: kernel panic and black screen, then reboot. In your files at github there is no SSDT exactly for this model. If I remove SSDT - it boots and works. If I use SSDT or config for another model, similar to mine - kernel panic. I got most of hardware to work: usb, camera, ethernet, sound, graphics. The only one thing to do is to make battery indicator work. This file https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/blob/master/hotpatch/SSDT-BATT-G4.asl is for G4, I have new version of G5. More details why it will not work later...

details:
my DSDT:
Code:
OperationRegion (ECRM, EmbeddedControl, Zero, 0xFF)

in https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/blob/master/hotpatch/SSDT-BATT-G4.asl:
Code:
OperationRegion (ECR2, EmbeddedControl, 0x00, 0xFF)

region name differ.
 
Last edited:
Joined
May 29, 2012
Messages
5
Motherboard
HP ProBook 450G5 2VP38EA-Clover
CPU
i5 8250U
Graphics
HD 620 1920x1080
Mac
  1. MacBook
  2. Mac mini
Mobile Phone
  1. iOS
I fix battery status: it needs to carefully modify DSDT to get it work.

One more note to RehabMan's patch set: you suppose that notebook has dual graphics card set. It is wrong: in mine only one graphics card. If I leave patches that disable secondary graphics card something will go wrong...
 
Last edited:

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,933
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Sure, because I'd like to get my notebook work. I repeat: if I do all from post #1 - it won't boot at all: kernel panic and black screen, then reboot.

You must provide problem reporting files as per FAQ.

In your files at github there is no SSDT exactly for this model.

Wrong.
Note:
Code:
NUC6i7KYK:probook.git rehabman$ ./install_acpi.sh help|grep -y kabylake-r
install_1050g1_kabylake-r
install_4x0g5_kabylake-r

details:
my DSDT:
Code:
OperationRegion (ECRM, EmbeddedControl, Zero, 0xFF)

in https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/blob/master/hotpatch/SSDT-BATT-G4.asl:
Code:
OperationRegion (ECR2, EmbeddedControl, 0x00, 0xFF)

region name differ.

By design.
You clearly don't understand how ACPI hotpatch is accomplished.
 
Joined
Jun 9, 2011
Messages
186
Motherboard
Gigabyte H107N-WiFi
CPU
i5-6500
Graphics
HD530
Mobile Phone
  1. Android
(Edit: Please ignore my earlier fault report. It was a false alarm. I made a careless mistake (sorry) I did ./install.acpi.sh config_4x40 instead of install_4x40)


Now that I have updated Clover and the kext, SSDT, etc, I would like to upgrade from El Capitan to Mojave. I checked my EFI/CLOVER/drivers64UEFI/ and it contains:

ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi
DataHubDxe-64.efi
FSInject-64.efi
HFSPlus.efi
HPFanReset.efi
SMCHelper-64.efi

Do I need to download and copy the latest apfs.efi into drivers64UEFI? Anything missing in drivers64UEFI?

Anything else to take note when upgrading to Mojave directly?

Thank you.
 
Last edited:

RehabMan

Moderator
Joined
May 2, 2012
Messages
183,933
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
(Edit: Please ignore my earlier fault report. It was a false alarm. I made a careless mistake (sorry) I did ./install.acpi.sh config_4x40 instead of install_4x40)


Now that I have updated Clover and the kext, SSDT, etc, I would like to upgrade from El Capitan to Mojave. I checked my EFI/CLOVER/drivers64UEFI/ and it contains:

ApfsDriverLoader-64.efi
AptioMemoryFix-64.efi
DataHubDxe-64.efi
FSInject-64.efi
HFSPlus.efi
HPFanReset.efi
SMCHelper-64.efi

Do I need to download and copy the latest apfs.efi into drivers64UEFI? Anything missing in drivers64UEFI?

Anything else to take note when upgrading to Mojave directly?

Thank you.

ApfsDriverLoader-64.efi takes care of apfs.efi.

Make sure you read post #1, "System updates".
 
Joined
Jun 9, 2011
Messages
186
Motherboard
Gigabyte H107N-WiFi
CPU
i5-6500
Graphics
HD530
Mobile Phone
  1. Android
ApfsDriverLoader-64.efi takes care of apfs.efi.

Make sure you read post #1, "System updates".
I read it several times but it doesn't say explicitly apfs.efi is needed, or not, or apfsdriverloader-64.efi takes care of it. That's why I asked.

Reference:

Updating to High Sierra

As you probably already know, High Sierra (and later) has a new file system called APFS. Boot drives on SSDs will automatically be converted to APFS if you start the High Sierra installer in the default way (eg. running /Applications/Install macOS High Sierra.app).
 
Top