What is in the HP Probook Installer/What does it do?

[Gordo74]

Hi All,

Long time desktop builder here foraying into OSX on laptops. It looks darn easy with the tools you guys have put together. I have a Probook 4530s with an Atheros 9280.

On my desktops I have everything injected through Clover with my own DSDT, kext patches on the fly, and minimal kexts injected (I believe just bluetooth, fakeSMC, and my network card) directly from Clover. This allows me to update through the App store with no issues while retaining 100% functionality.

My question is this: I'd like to keep that setup, as it is what I am most familiar with. Does the HP Probook installer work the same was as I setup my desktop? Or does it install kexts to /S/L/E and write in some crazy boot arguments that need the sacrificial blood of lambs to keep working? Can I set it up like I have done on my desktop?

Thanks,
Gordo

 

[RehabMan]

Hi All,

Long time desktop builder here foraying into OSX on laptops. It looks darn easy with the tools you guys have put together. I have a Probook 4530s with an Atheros 9280.

On my desktops I have everything injected through Clover with my own DSDT, kext patches on the fly, and minimal kexts injected (I believe just bluetooth, fakeSMC, and my network card) directly from Clover. This allows me to update through the App store with no issues while retaining 100% functionality.

My question is this: I'd like to keep that setup, as it is what I am most familiar with. Does the HP Probook installer work the same was as I setup my desktop? Or does it install kexts to /S/L/E and write in some crazy boot arguments that need the sacrificial blood of lambs to keep working? Can I set it up like I have done on my desktop?

Thanks,
Gordo

http://www.tonymacx86.com/hp-proboo...-install-yosemite-hp-laptops-clover-uefi.html

If you want to know what the Probook Installer does, the source code is available...

All patches to native kexts are done via injectors or Clover hotpatch.

Note: It is actually best to install all kexts you need to /S/L/E, although that is not the method the PBI-CE employs.

 

[Gordo74]

http://www.tonymacx86.com/hp-proboo...-install-yosemite-hp-laptops-clover-uefi.html

If you want to know what the Probook Installer does, the source code is available...

All patches to native kexts are done via injectors or Clover hotpatch.

Note: It is actually best to install all kexts you need to /S/L/E, although that is not the method the PBI-CE employs.

Hi RehabMan,

I read through that entire thread actually. I used to Mod here so I am not one for asking stupid questions (much, at least).

I know the source code is available, which I cannot read easily enough. I was just wondering if there was a layman's terms on how it installs/where, which you answered with the hot patching.

Good to know that all patches are done on the fly and kexts are injected from Clover. This should allow for native updating, am I correct?

 

[RehabMan]

...
Good to know that all patches are done on the fly and kexts are injected from Clover. This should allow for native updating, am I correct?

Correct.

 

[nguyenmac]

Hi RehabMan,

I read through that entire thread actually. I used to Mod here so I am not one for asking stupid questions (much, at least).

I know the source code is available, which I cannot read easily enough. I was just wondering if there was a layman's terms on how it installs/where, which you answered with the hot patching.

Good to know that all patches are done on the fly and kexts are injected from Clover. This should allow for native updating, am I correct?

Here is some brief introduction:

• Install Clover UEFI with suitable settings to EFI partition.
• Create suitable config.plist.
• Install approriate kexts to your /EFI/Clover/kexts (important kexts) and /System/Library/Extensions/ (DummyHDA kext).
• Take your ACPI files (DSDT, SSDT) from /EFI/Clover/ACPI/origin/ in your EFI partition or a "CLOVER" partition, patch it then copy to your EFI partition.

 

[Gordo74]

Here is some brief introduction:

• Install Clover UEFI with suitable settings to EFI partition.
• Create suitable config.plist.
• Install approriate kexts to your /EFI/Clover/kexts (important kexts) and /System/Library/Extensions/ (DummyHDA kext).
• Take your ACPI files (DSDT, SSDT) from /EFI/Clover/ACPI/origin/ in your EFI partition or a "CLOVER" partition, patch it then copy to your EFI partition.

Perfect! Exactly what I was looking for!

Only one additional follow up question. On my desktop, there is a dummy HDA text in the /EFI/Clover/kexts with on the fly patching done to the native AppleHDA. This has allowed for easy updating without losing audio. Does the PB Installer use the same method of using the native HDA kext?

 

[RehabMan]

Perfect! Exactly what I was looking for!

Only one additional follow up question. On my desktop, there is a dummy HDA text in the /EFI/Clover/kexts with on the fly patching done to the native AppleHDA. This has allowed for easy updating without losing audio. Does the PB Installer use the same method of using the native HDA kext?

HDA injectors must be installed to /S/L/E (as they must reside in kernel cache). But your point about easy updates is still true, because the audio patching is implemented with an injector and Clover hotpatches.

Actually, it is best to install all kexts to /S/L/E and use kext injection only when necessary (installer, recovery). Sadly, this is not what the ProBook Installer does.

 

[nguyenmac]

Perfect! Exactly what I was looking for!

Only one additional follow up question. On my desktop, there is a dummy HDA text in the /EFI/Clover/kexts with on the fly patching done to the native AppleHDA. This has allowed for easy updating without losing audio. Does the PB Installer use the same method of using the native HDA kext?

I believe yours method is old.

Yours:
- HDA injector
- zml.zlib files inside AppleHDA.kext
- patches for audio codec + xml.zlib -> zml.zlib in config.plist

New:
- DummyHDA (must be installed in /S/L/E)
- patches for audio codec in config.plist.

Both will work though I think the new one is more compact.

 

[RehabMan]

I believe yours method is old.

Yours:
- HDA injector
- zml.zlib files inside AppleHDA.kext
- patches for audio codec + xml.zlib -> zml.zlib in config.plist

New:
- DummyHDA (must be installed in /S/L/E)
- patches for audio codec in config.plist.

Both will work though I think the new one is more compact.

Note: So-called "DummyHDA" *is* an HDA injector.

Injector kext: A codeless kext... A kext with no code just data (Info.plist, Resources/*, etc). The only twist is the symlink used for the AppleHDA binary.

Also note that using an HDA injector is no guarantee that audio will always survive updates. It will only work as long the Clover config.plist patches work, and the whole method doesn't break down entirely (it does not conform to Apple guidelines for kexts). Bottom line: It is a hack and we're lucky it is working at the moment.

 

[Gordo74]

I believe yours method is old.

Yours:
- HDA injector
- zml.zlib files inside AppleHDA.kext
- patches for audio codec + xml.zlib -> zml.zlib in config.plist

New:
- DummyHDA (must be installed in /S/L/E)
- patches for audio codec in config.plist.

Both will work though I think the new one is more compact.

Hmm, I'm using Toledo's HDA Clover patch which runs out of terminal. I think you're right in the way mine does it, but to Rehabman's point, "my way" uses the native AppleHDA kext with no dummy kexts/non native kexts in /S/L/E which gives it a much better chance of surviving updates.

Maybe something to consider in the new version. You're right in that it is "more compact" putting a dummy HDA kext in /S/L/E, but it is less "native".