Contribute
Register

HP Probook Installer Clover Edition

I posted it here: http://www.tonymacx86.com/hp-probook-yosemite/170903-hp-840-g1-not-seeing-bcm943224hms-wifi.html so I'm not double posting/attaching to the forums. Thanks again!

If PBI-CE gave you MacBookAir5,2 *and* a whitelist patch for BCM943224, it is clearly a bug in PBI-CE. No whitelist patch needed when using a board-id already in the whitelist (such as MacBookAir5,2).

If you changed the SMBIOS to MacBookAir5,2 after using PBI-CE, then it is your own error.
 
I have question about ProBook 650 G1 and its imitation of MacBook. 650 G1 is 15" laptop, but in About info, there is MacBook Pro (Retina, 13", Late 2013). Its ok?
I'm asking because my problems of getting custom HiDPI resolution to work.
 
I have question about ProBook 650 G1 and its imitation of MacBook. 650 G1 is 15" laptop, but in About info, there is MacBook Pro (Retina, 13", Late 2013). Its ok?
I'm asking because my problems of getting custom HiDPI resolution to work.

Not likely to be relevant. Mac model is chosen based on CPU/chipset/graphics device configuration, not screen size.
 
Why FakeSMC plugins are removed on latest version?
That makes HWMonitor unusable.
 
@nguyenmac,

Suggestion: Install both bluetooth kexts (BrcmPatchRAM.kext, IOath3kfrmwr.kext) automatically. Remove options from PBI-CE.

Reason: The latest BrcmPatchRAM.kext will not load unless the associated hardware is installed (this commit: https://github.com/RehabMan/OS-X-BrcmPatchRAM/commit/6f6ad88f5c0c68e58da9885237a386f29551928c). And this was always true of IOath3kfrmwrk.kext.

This will avoid a certain common "pilot error" where there are serious USB problems due to lack of BT firmware in present but unitialized BT device.


Thanks for watching out for us. You solved this very issue for me a little while back.
 
I upgraded my existing installation (it was on Clover@3192 I believe) with PBI 6.4.0.1 and now I have the same kexts in both /EFI/EFI/Clover/kexts/10.10 and /System/Library/Extensions. Is it safe to remove them from /EFI? Also, there's BrcmPatchRAM.kext even though I have an Atheros, not Broadcom card. Is this how it's supposed to be?(edit: RehabMan explained that already)
 
I upgraded my existing installation (it was on Clover@3192 I believe) with PBI 6.4.0.1 and now I have the same kexts in both /EFI/EFI/Clover/kexts/10.10 and /System/Library/Extensions. Is it safe to remove them from /EFI? Also, there's BrcmPatchRAM.kext even though I have an Atheros, not Broadcom card. Is this how it's supposed to be?(edit: RehabMan explained that already)

Yes, but you won't be able to boot from Recovery partition.
 
Yes, but you won't be able to boot from Recovery partition.

Which directory takes the precedence during boot? Aren't the kexts being loaded twice (first from /EFI, then from /S/L/E)? Boot.log shows that Clover injects them from /EFI:
Code:
3:422  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.10
3:423  0:001    Extra kext: EFI\CLOVER\kexts\10.10\ACPIBacklight.kext
3:452  0:028    Extra kext: EFI\CLOVER\kexts\10.10\ACPIBatteryManager.kext
3:454  0:002    Extra kext: EFI\CLOVER\kexts\10.10\ACPIPoller.kext
3:455  0:001    Extra kext: EFI\CLOVER\kexts\10.10\BrcmPatchRAM.kext
3:491  0:035    Extra kext: EFI\CLOVER\kexts\10.10\FakeSMC.kext
3:494  0:003    Extra kext: EFI\CLOVER\kexts\10.10\IOath3kfrmwr.kext
3:497  0:003    Extra kext: EFI\CLOVER\kexts\10.10\ProBookAtheros.kext
3:497  0:000    Extra kext: EFI\CLOVER\kexts\10.10\RealtekRTL8111.kext
3:505  0:008    Extra kext: EFI\CLOVER\kexts\10.10\VoodooPS2Controller.kext
3:507  0:001      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Keyboard.kext
3:510  0:003      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Mouse.kext
3:512  0:001      Extra PlugIn kext: EFI\CLOVER\kexts\10.10\VoodooPS2Controller.kext\Contents\PlugIns\VoodooPS2Trackpad.kext
does the system itself load them again from /S/L/E?
 
Back
Top