HP Probook Installer Clover Edition

[wfewfe]

Yes, this point is not clear, you may explain it in the guide with more details.
Anyway, I did as you said, and it works and I moved the next step.
I have the 2 images attached displayed one by one continuously.

What should I do?

 

[nguyenmac]

Yes, this point is not clear, you may explain it in the guide with more details.
Anyway, I did as you said, and it works and I moved the next step.
I have the 2 images attached displayed one by one continuously.
View attachment 120298View attachment 120299
What should I do?

I wrote this:

Download Config.zip, extract then select right config.plist and copy to /EFI/Clover/

And you said that I'm not clear?

Did I tell you to copy config.zip to /EFI/CLOVER/? How could you do this?
Did I tell you to create Config folder and create a folder HD 4000 1366x768 in /EFI/CLOVER/? So How could you do this?

Now you blame me for not writing it clearly? Oh god, I wrote it as much detail as possible.

The problem you're asking is included in the guide already.

You're too much! I will never support a guy who can't follow such a simple guide like you (I doubt you can follow any guide in Hackintosh).

 

[wfewfe]

dear nguyenmac ,
Please be patient, this is the first time for me to install MAC os system, and I am sorry to bother you.
I don't blam you at all, on the contrary, I thank your efforts and I appreciate your help.
I am new in the MAC os world. Please accept my deep apologizes.

 

[nguyenmac]

dear nguyenmac ,
Please be patient, this is the first time for me to install MAC os system, and I am sorry to bother you.
I don't blam you at all, on the contrary, I thank your efforts and I appreciate your help.
I am new in the MAC os world. Please accept my deep apologizes.

The guide I gave you have no requirements of OS X world, I did everything for you.

If you want me to be patient to you, you should be patient to read the guide WORD BY WORD first.

Or wait until someone more patient than me reply you.

 

[RehabMan]

I'm a little confused. To get both QE/CI and OpenCL work on 10.10:

1/ For HD4600: 2 kexts + DSDT patches for ig-platform-id/hda-gfx

Just the normal config.plist settings + FakePCIID.kext + FakePCIID_HD4600_HD4400.kext will do the job.

If you're doing the injections via DSDT/SSDT edits, that works too (because of device-id=0412).

2/ For HD4400:
b/ 2 kexts + DSDT patches for ig-platform-id/hda-gfx
c/ 2 kexts + DSDT patches for Rm-device=12040000/ig-platform-id/hda-gfx

Again, it depends on how you're doing the "normal" injects. For HD4400, config.plist/Graphics/Inject/Intel=true, and ig-platform-id=mobile-value, enables it pretty well. But to use FakePCIID.kext and FakePCIID_HD4400_HD4600.kext you need to inject device-id=0412 or RM,device-id=0412 as well. You can treat it like HD4600 (device-id=0412) or can do something special with RM,device-id=0412.

If we use 10.9, do method 1/2b/2c still work? Or we have to remove them and just use original DSDT patches?

Since 10.9 supports both natively, FakePCIID.kext is not necessary. In a dual-boot system (both 10.9 and 10.10) here's how I would do it:
For both HD4400/HD4600
- FakePCIID.kext/FakePCIID_HD4600_HD4400 installed only to 10.10 /S/L/E
- Use FakeID=0412 (the FakeID will have no material effect on 10.9, but will help FakePCIID.kext do its job on 10.10). Not needed with HD4400 with latest commit.
- injection of hda-gfx/ig-platform-id is the same in either case (can be done via config.plist or _DSM)

EDIT: Will this work even for USB devices like Bluetooth?

This is for PCI devices only.

 

[RehabMan]

I just make a test for my Broadcom 4352 14e4:43b1, but it does not work. Here is what I did:

0/ Remove ProbookARPT.kext (wifi injector kext)
1/ Make FakePCIID_Broadcom4352.kext with info.plist:

        <key>Broadcom4352</key>
        <dict>
            <key>CFBundleIdentifier</key>
            <string>org.rehabman.driver.FakePCIID</string>
            <key>IOClass</key>
            <string>FakePCIID</string>
            <key>IOMatchCategory</key>
            <string>FakePCIID</string>
            <key>IOPCIPrimaryMatch</key>
            <string>0x43b114e4 0x43a014e4</string>
            <key>IOProviderClass</key>
            <string>IOPCIDevice</string>
            <key>RM,Build</key>
            <string>Release-RehabMan</string>
            <key>RM,Version</key>
            <string>Broadcom4352</string>
        </dict>

2/ Patch ARPT device in DSDT:

Method (_DSM, 4, NotSerialized)
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                0x03
                            })
                        }

                        Return (Package (0x0E)
                        {
                            "RM,vendor-id", 
                            Buffer (0x04)
                            {
                                0xE4, 0x14, 0x00, 0x00
                            }, 

                            "RM,device-id", 
                            Buffer (0x04)
                            {
                                0xA0, 0x43, 0x00, 0x00
                            }, 

                            "RM,subsystem-id", 
                            Buffer (0x04)
                            {
                                0x17, 0x01, 0x00, 0x00
                            }, 

                            "RM,subsystem-vendor-id", 
                            Buffer (0x04)
                            {
                                0x6B, 0x10, 0x00, 0x00
                            }, 

                            "model", 
                            Buffer (0x3A)
                            {
                                "Broadcom BCM4352 802.11 b/g/n/ac Wireless Network Adapter"
                            }
                        })
                    }

3/ Install both FakePCIID.kext and FakePCIID_Broadcom4352.kext to /S/L/E, rebuild cache.
4/ Restart, wifi does not work. Go to System Pref > Network > Add, Wifi is not in the list.

Without device-id injection (you have only "RM,"), you will need the injector (ProbookARPT.kext) to provide a reason for IOKit to load the kext.

Your choice:
- inject device-id=0xA0, 0x43, 0x00, 0x00 (assuming this is the device the native kext recognizes)
- keep using the injector (with the DSDT patch you have)

Basically, there are two things you must satisfy:
- provide IOKit a matching device to load the native kext (injector kext like ProbookARPT.kext or device-id inject)
- provide the necessary config for FakePCIID so the correct (fake) values can be returned from IOPCIDevice

Let me know if your injector works out. If you're still having trouble, post your "patchmatic -extract" output and ioreg.

 

[nguyenmac]

Without device-id injection (you have only "RM,"), you will need the injector (ProbookARPT.kext) to provide a reason for IOKit to load the kext.

Your choice:
- inject device-id=0xA0, 0x43, 0x00, 0x00 (assuming this is the device the native kext recognizes)
- keep using the injector (with the DSDT patch you have)

Basically, there are two things you must satisfy:
- provide IOKit a matching device to load the native kext (injector kext like ProbookARPT.kext or device-id inject)
- provide the necessary config for FakePCIID so the correct (fake) values can be returned from IOPCIDevice

Let me know if your injector works out. If you're still having trouble, post your "patchmatic -extract" output and ioreg.

If I include injector + your FakePCI, the only change I see is that OS X reports it to be AirPort Extreme instead of Third party card. That's thanks to subsystem id I think.

So I thought it works now.

 

[RehabMan]

If I include injector + your FakePCI, the only change I see is that OS X reports it to be AirPort Extreme instead of Third party card. That's thanks to subsystem id I think.

So I thought it works now.

You also can remove all related patches that are for PCI ID matching in config.plist.

Also, an FakePCIID injector is already provided in the build... (perhaps I should rename it).

 

[nguyenmac]

Just the normal config.plist settings + FakePCIID.kext + FakePCIID_HD4600_HD4400.kext will do the job.

If you're doing the injections via DSDT/SSDT edits, that works too (because of device-id=0412).

Again, it depends on how you're doing the "normal" injects. For HD4400, config.plist/Graphics/Inject/Intel=true, and ig-platform-id=mobile-value, enables it pretty well. But to use FakePCIID.kext and FakePCIID_HD4400_HD4600.kext you need to inject device-id=0412 or RM,device-id=0412 as well. You can treat it like HD4600 (device-id=0412) or can do something special with RM,device-id=0412.

So for both HD4400/HD4600 on 10.10, the universal solution is DSDT _DSM device-id=0412 (I prefer this to config.plist) + 2 kexts.

On 10.10: It works as expected with 2 kexts in /S/L/E.
On 10.9: Without 2 kexts, although device-id is for desktop, both HD4400/HD4600 still works fine.

Am I right?

Another thing, can I use Clover injection instead of installing in S/L/E?

 

[RehabMan]

So for both HD4400/HD4600 on 10.10, the universal solution is DSDT _DSM device-id=0412 (I prefer this to config.plist) + 2 kexts.

On 10.10: It works as expected with 2 kexts in /S/L/E.
On 10.9: Without 2 kexts, although device-id is for desktop, both HD4400/HD4600 still works fine.

Am I right?

I believe so.

Another thing, can I use Clover injection instead of installing in S/L/E?

I have not tested it that way (as you know, I don't use Clover/kexts for my main partition), but it will probably work. You'll need to install it only to kexts/10.10, since you don't want/need it for 10.9.

You can test and report back.