[Guide] HP ProBook 430 G6 (Whiskey Lake)

[WhenMusicAttacks]

Hi, don't know if there are still Probook 430 G6 users visiting this thread but I just bought a used one and did install Big Sur with Opencore.
I just wanted to know if some of you managed to disable "CFG Lock" and "Overclocking Lock" (for voltageshift) on this computer? I gathered different bios versions, from R71 01.09.01 to R71 01.16.00 and couldn't find any CFG Lock references with UEFITool.
Second question, did you managed to get fan speed value with VirtualSMC and SMCSuperIO plugin? I can get rpm informations with FakeSMC, but then getting reliable battery charge status is more problematic.

To enable voltageshift you need to rollback to a bios older than november 2019, as that's when plundervolt mitigation was implemented in microcode. I was not able to unlock tdp on this machine, undervolting worked and was an incredible speed upgrade - and noise reduction aswell

 

[poulpor]

To enable voltageshift you need to rollback to a bios older than november 2019, as that's when plundervolt mitigation was implemented in microcode. I was not able to unlock tdp on this machine, undervolting worked and was an incredible speed upgrade - and noise reduction aswell

Thank you very, very much for your help, Bios 01.08.03 Rev.A, released in july 2019 was the solution, it is allowing voltageshift to operate, lowering the idle temp from 39°C to 34°C, that's great news for me! During my previous tests, I stopped at Bios 01.09.01, so near and yet so far

Regarding TDP, do you mean changing PL1 (which is TDP value) and PL2 (sort of short burst time period) with VoltageShift had no effect on throttling? Because thanks to this Bios version, I can change PL1 and PL2 values with Voltageshift 1.24, for example (see screenshots):
Before, with default PL1: 17W PL2:25W
After, changed voltages and PL1:20W PL2:35W

I saw a VoltageShift 1.25 version popped since the last time I visited sicreative/VoltageShift, with a mysterious changelog note:"Support kext remaining on System".
Personally, I'm using Keyboard Maestro on other rigs to automatically run the VoltageShift script at login and wake from sleep events, it works good, will give a try to this 1.25 version to see if it survives wake event.

 

[poulpor]

I think I can confirm PL1 and PL2 settings in VoltageShift are effective for the 430 G6, I did some Geekbench 5 tests and the difference is real.
Blue bar score is reached with PL1:55W PL2:65W (sort of no-limit for this low energy cpu), grey one was something like PL1:25W PL2:35W.
To achieve the bigger score, I also replaced my "MacbookPro like" CPUFriendDataProvider.kext by an "iMac" one, less aggressive regarding frequencies boost en electric consumption.

For those who may not be familiar with VoltageShift, it's very easy to use, just install the kext then, for example, create a Voltageshift folder in your applications folder and copy voltageshift app inside along with some useful shell scripts, like this one which sets CPU (-130mV), GPU (-120mV), CPUcache (-130mV) voltages and PL1 (45W) PL2 (65W).
You have to keep the "" for the password and can, of course, change the voltage offset values to your liking.
With VoltageShift 1.24, you had to use an app to schedule this voltage script launch at login (boot) and wake from sleep, because it was reset to default voltage after those events. I used Keyboard Maestro to achieve these and you'll find the corresponding macro in the zip, along with the 3 shell scripts detailed here:

#!/bin/bash
cd /Applications/VoltageShift
echo "yourmacuserpassword"|sudo -S ./voltageshift offset -130 -120 -130
sleep 0.5
echo "yourmacuserpassowrd"|sudo -S ./voltageshift power 45 65
osascript -e 'tell application "Terminal" to quit' &

This one is for reading the actual voltage and TDP values:

#!/bin/bash
cd /Applications/VoltageShift
echo "yourmacuserpassword"|sudo -S ./voltageshift info

And this one to continuously monitor those values:

#!/bin/bash
cd /Applications/VoltageShift
echo "yourmacuserpassword"|sudo -S ./voltageshift mon

 

[WhenMusicAttacks]

Thank you very, very much for your help, Bios 01.08.03 Rev.A, released in july 2019 was the solution, it is allowing voltageshift to operate, lowering the idle temp from 39°C to 34°C, that's great news for me! During my tests, I stopped at Bios 01.09.01, so near and yet so far

Regarding TDP, do you mean changing PL1 (which is TDP value) and PL2 (sort of short burst time period) with VoltageShift had no effect on throttling? Because thanks to this Bios version, I can change PL1 and PL2 values with Voltageshift 1.24, for example (see screenshots):
Before, with default PL1: 17W PL2:25W
After, changed voltages and PL1:20W PL2:35W

I saw a VoltageShift 1.25 version popped since the last time I visited sicreative/VoltageShift, with a mysterious changelog note:"Support kext remaining on System".
Personally, I'm using Keyboard Maestro on other rigs to automatically run the VoltageShift script at login and wake from sleep events, it works good, will give a try to this 1.25 version to see if it survives wake event.

TDP is integrated in the buildlaunchd script - 6 values are offset, 1 to enable boost, then the 2 PL values, and the last one is the timer to repeat the script

 

[antonio765]

I updated BIOS to 1.19. Boots fine with Clover 5115 so far. Battery status is great, no problems detected. I'm using this patch by @e285ne:
https://www.tonymacx86.com/threads/guide-hp-probook-430-g6-whiskey-lake.282302/page-6#post-2147595

BIOS update 1.19 includes Changelog:

- Addresses security vulnerabilities CVE-2021-39297, CVE-2021-39299, CVE-2021-39300, CVE-2021-39301.
- Includes the following firmware:
Embedded Controller (EC), version 51.30.00
Intel GOP, version 9.0.1080
Intel Management Engine (Consumer), version 12.0.85.1869 (Production)
Intel vBIOS, version 9.2.1015 Intel/Realtek PXE ROM RTL8111, version 2.66
Intel/Realtek PXE ROM RTL8153, version 2.019
Intel/Realtek UEFI PXE ROM RTL8111, version 2.043
USB Type-C Power Delivery (PD) Firmware (CCG5), version 7.11

Above mentioned vulnerabilities may allow escalation of privilege and arbitrary code execution.