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

[willpower101]

Read post #1, "Problem Reporting".

Edit: Ignore everything I just said. It's not an upgraded resolution monitor.
Is there a way to check the model and supported resolution in mac? I just tore it apart and looked by hand at the serial.

I think I did it right?

http://www.tonymacx86.com/el-capitan-laptop-guides/189416-guide-hp-probook-elitebook-zbook-using-clover-uefi-hotpatch-10-11-a-62.html#post1240971

Tried with the regular res version just for fun, I get 1366x768 just fine, but that's maximum.
Changing the config.plist graphics resolution to 1600x900 or 1080x1920 has no effect.

Changing to SSDT-IGPU-HIRES.aml blanks out the internal display no matter what I set config.plist Graphics setting at.

Edit: partially fixed.
Rehabman, for some reason this change for jbamforb needs to be reverted on my system.

-                    "AAPL,DualLink", Buffer() { 0x01, 0x00, 0x00, 0x00 },         //900p/1080p
 +                    "AAPL00,DualLink", Buffer() { 0x01, 0x00, 0x00, 0x00 },       //900p/1080p/CODE]


[/COLOR][URL="https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/commit/fce0bca63863723f81f96a2453f52bf43e3ce5a3"][COLOR=#a9a9a9]https://github.com/RehabMan/HP-ProBook-4x30s-DSDT-Patch/commit/fce0bca63863723f81f96a2453f52bf43e3ce5a3[/COLOR][/URL][COLOR=#a9a9a9]

I tried with alternate droptables and generate p/c states in config. Going to go turn those off, rebuild caches and confirm that it still works.

[B]Edit 2: [/B]

The internal monitor won't go above 1366x768, despite being on HIRES.aml with AAPL00->AAPL[/COLOR][/STRIKETHRU]

 

[RehabMan]

Delete this in your config.plist:
Device / Audio / Inject = 0
this is not necessary if you are injecting
your LayoutID by SSDT and DSDT.

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:

      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.

 

[RehabMan]

Edit: Ignore everything I just said. It's not an upgraded resolution monitor.
Is there a way to check the model and supported resolution in mac? I just tore it apart and looked by hand at the serial.

Your computer has a 1366x768 display (because you have not replaced the stock screen). It will be shown as the top resolution in SysPrefs->Displays if you click on Scaled. Also shown in System Information->Graphics/Displays.

 

[Theetjuh]

I reverted to the original so you can test again with the new setup. See if you can reproduce the original result (it will help determine that there isn't something wrong with my procedures).

So I need to switch to master branch again and try again?

[edit]

I think I misunderstood, I stayed at 'alc280test' branch and updated git.
I have audio back again, headphone doesn't work and microphone does, I think how it was with alc280combo at the start right?

 

[Andrevvvvv]

Hello friends.
I have latest PBI-CE on my 4530s and 10.11.3 OS X. I read 1-st post and got no info about updating to 10.11.4. Is it safe with latest available PBI-CE or I should do this hotpatch?
And is there any chance that PBI-CE will return with comfy installer?

 

[VioletDragon]

Hello friends.
I have latest PBI-CE on my 4530s and 10.11.3 OS X. I read 1-st post and got no info about updating to 10.11.4. Is it safe with latest available PBI-CE or I should do this hotpatch?
And is there any chance that PBI-CE will return with comfy installer?

PBI is no longer supported. Recommend following this guide and using Clover Hotpatch also update kexts.

 

[RehabMan]

So I need to switch to master branch again and try again?

I made the revert in the alc280test branch.

I have audio back again, headphone doesn't work and microphone does, I think how it was with alc280combo at the start right?

Good. I just wanted to be sure that the problem of no audio is caused in the updated xml from mirone and not something else.

 

[RehabMan]

Hello friends.
I have latest PBI-CE on my 4530s and 10.11.3 OS X. I read 1-st post and got no info about updating to 10.11.4. Is it safe with latest available PBI-CE or I should do this hotpatch?
And is there any chance that PBI-CE will return with comfy installer?

There is a section in post #1 on how to transition from PBI-CE. You should read the entire post.

 

[Theetjuh]

Good. I just wanted to be sure that the problem of no audio is caused in the updated xml from mirone and not something else.

What I am noticing that my laptop is running really hot ... it didn't do that before!
I just looked but am using 'SSDT-FAN-READ.aml' like before, should I change to something else or is there something wrong in the ssdt?

 

[RehabMan]

What I am noticing that my laptop is running really hot ... it didn't do that before!
I just looked but am using 'SSDT-FAN-READ.aml' like before, should I change to something else or is there something wrong in the ssdt?

Did you forget HPFanReset.efi?