Contribute
Register

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

Status
Not open for further replies.
Did you forget HPFanReset.efi?
I guess so, when was that introduced?
I did a reinstall last week on the G2 and haven't seen that back then ... or my eyes are failing me o_O
 
I guess so, when was that introduced?

It has always been in the guide. I will make install_downloads.sh install it automatically (DONE).

Note: Prior to yesterday's updates, SSDT-FAN-MOD.aml was the default. I changed to SSDT-FAN-READ.aml. You can change your fan behavior as described in post #1 with the FANPREF option (also updated yesterday).

I did a reinstall last week on the G2 and haven't seen that back then ... or my eyes are failing me o_O

Keep in mind that as the repo changes, so does the instructions in post #1. What you know yesterday may not be adequate today.
 
It has always been in the guide. I will make install_downloads.sh install it automatically (DONE).

Note: Prior to yesterday's updates, SSDT-FAN-MOD.aml was the default. I changed to SSDT-FAN-READ.aml. You can change your fan behavior as described in post #1 with the FANPREF option (also updated yesterday).



Keep in mind that as the repo changes, so does the instructions in post #1. What you know yesterday may not be adequate today.


I start Cinebench R15 and can't hear fan, I have HPFanReset.efi? Using SSDT-FAN-READ.aml ?

When Fan should be start spinning?
 
I have HPFanReset.efi?
Using SSDT-FAN-READ.aml ?

Regarding whether you are using these files or not, I cannot answer. You did not provide the files requested in "Problem Reporting".

When Fan should be start spinning?

It depends on what fan control SSDT you are using and (with SSDT-FAN-READ) BIOS behavior.
 
Regarding whether you are using these files or not, I cannot answer. You did not provide the files requested in "Problem Reporting".



It depends on what fan control SSDT you are using and (with SSDT-FAN-READ) BIOS behavior.


Ok, I will now try SSDT-FAN-MOD If have again problems I post files.


And I want to install sensors, I put FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_LPCSensors.kext, FakeSMC_GPUSensors.kext in EFI/Clover/kexts/Other. But when I reboot still no sensors in HWMonitor app.


 
And I want to install sensors, I put FakeSMC_ACPISensors.kext, FakeSMC_CPUSensors.kext, FakeSMC_LPCSensors.kext, FakeSMC_GPUSensors.kext in EFI/Clover/kexts/Other. But when I reboot still no sensors in HWMonitor app.



Clover does not inject kexts from EFI when config.plist/SystemParameters/InjectKexts=Detect and FakeSMC is in kernel cache (due to being installed to the system volume).

This guide installs all kexts to the system volume (at /L/E). As a result, you should not expect kexts you add to EFI to have any effect when you boot your system partition.

If you want the FakeSMC sensors, you need to install them to /L/E.
 
It has always been in the guide. I will make install_downloads.sh install it automatically (DONE).

Note: Prior to yesterday's updates, SSDT-FAN-MOD.aml was the default. I changed to SSDT-FAN-READ.aml. You can change your fan behavior as described in post #1 with the FANPREF option (also updated yesterday).

Keep in mind that as the repo changes, so does the instructions in post #1. What you know yesterday may not be adequate today.
Thanks for including it ... I noticed stuff changing constantly ... good of course, but will check it more often now ;)

Still quite hot and haven't noticed the fan yet ... but it isn't as hot as before luckily!
 
The config.plist has the correct setting.

Devices/Audio/Inject=0 is the way you keep Clover from injecting anything for audio.

Also note: Because of this is not possible to inject layout-id=0 with Clover's Audio/Inject even though layout-id 0 is valid (it just means we generally use a different layout-id, and if can be injected with ACPI or /Devices/Arbitrary if really needed).

Another note: ACPI injections (via _DSM) always override any injections done via EFI properties.

If you remove Audio/Inject, clover will inject a "default" that is based on the codec id (which is usually wrong).

Here is the relevant code from Clover:
Code:
      Prop2 = GetProperty (DictPointer, "Audio");
      if (Prop2 != NULL) {
        // HDA
 //       Prop = GetProperty (Prop2, "ResetHDA");
 //       gSettings.ResetHDA = IsPropertyTrue (Prop);
        Prop = GetProperty (Prop2, "Inject");
        if (Prop != NULL) {
          // enabled by default
          // syntax:
          // [B]- HDAInjection=No or 0 - disables injection[/B]
          // - HDAInjection=887 - injects layout-id 887 decimal (0x00000377)
          // - HDAInjection=0x377 - injects layout-id 887 decimal (0x00000377)
          // - HDAInjection=Detect - reads codec device id (eg. 0x0887)
          //   converts it to decimal 887 and injects this as layout-id.
          //   if hex device is cannot be converted to decimal, injects legacy value 12 decimal
          // - all other values are equal to HDAInjection=Detect
[B]          if (Prop->type == kTagTypeInteger) {
            gSettings.HDALayoutId = (INT32)(UINTN)Prop->string; //must be signed
            gSettings.HDAInjection = (gSettings.HDALayoutId > 0);
          }[/B] else if (Prop->type == kTagTypeString){
            if ((Prop->string[0] == 'n') || (Prop->string[0] == 'N')) {
              // if starts with n or N, then no HDA injection
              gSettings.HDAInjection = FALSE;
            } else if ((Prop->string[0] == '0')  &&
                       (Prop->string[1] == 'x' || Prop->string[1] == 'X')) {
              // assume it's a hex layout id
              gSettings.HDALayoutId = (INT32)AsciiStrHexToUintn (Prop->string);
            } else {
              // assume it's a decimal layout id
              gSettings.HDALayoutId = (INT32)AsciiStrDecimalToUintn (Prop->string);
            }
          }
        }

In the Probook setup, all property injection is done with ACPI.

thank you for the explanation.
 
Still quite hot and haven't noticed the fan yet ... but it isn't as hot as before luckily!

If you think there is an issue with your config, read post #1, "Problem Reporting"...
 
Status
Not open for further replies.
Back
Top