[Guide] HackrNVMeFamily co-existence with IONVMeFamily using class-code spoof

onigoetz said:

I did use that path, I first generated my DSDT using ssdtGen.sh. I modified it to follow the description in post #1 but now I also get the ` AppleNVMe Assert failed:` errors when using the SSDT + spoofed Kext.

Am I missing something or is the 960 Pro not compatible with Sierra ?

Click to expand...

onigoetz said:

I did use that path, I first generated my DSDT using ssdtGen.sh. I modified it to follow the description in post #1 but now I also get the ` AppleNVMe Assert failed:` errors when using the SSDT + spoofed Kext.

Am I missing something or is the 960 Pro not compatible with Sierra ?

Click to expand...

RehabMan said:

Problems:
- No SSDT-NVMe-Pcc.aml in ACPI/patched.
- No _DSM->XDSM patch in config.plist/ACPI/patches (use a plist editor and copy/paste)
- No HackrNVMeFamily_10_12_4.kext in EFI/Clover/kexts/Other (in fact you don't even have FakeSMC.kext)

In other words, you have zero of the three components needed to implement this solution...

If you've already installed, you must have FakeSMC.kext on the system volume (or you would fail to boot), so don't forget to install HackrNVMeFamily_10_12_4.kext to the system volume as well. Make sure you use --spoof.

Click to expand...

Nynko said:

Hi, I'm sorry to ask again, but I can't find the path I need to replace from the example (With no Acpi behind a PCI-Bridge). Here is my path: PCI0@0/AppleACPIPCI/pci-bridge@1D/IOPP/pci144d,a802@0

Does someone could help me ?

I know that I certainly need to put: 0x001d0000 after _ADR (in order to generate the ACPI path) but it is not enough, I need to change others things but what ?

Click to expand...

// Inject bogus class-code for NVMe SSD to prevent IONVMeFamily.kext from loading
DefinitionBlock("", "SSDT", 2, "hack", "NVMe-Pcc", 0)
{
    External(_SB.PCI0, DeviceObj)
    // create identities for the bridge @1d and SSD0 @0
    Device(_SB.PCI0.PB1D)
    {
        Name(_ADR, 0x001d0000)  // corresponds to pci-bridge@1D
        Device(SSD0) { Name(_ADR, 0) } // corresponds to pci144d,a802@0
    }
    // now we can inject the _DSM at the newly created ACPI path
    Method(_SB.PCI0.PB1D.SSD0._DSM, 4)
    {
        If (!Arg2) { Return (Buffer() { 0x03 } ) }
        Return(Package()
        {
            "class-code", Buffer() { 0xff, 0x08, 0x01, 0x00 },
            "built-in", Buffer() { 0 },
        })
    }
}
//EOF

Nynko said:

(of course I couldn't save with PBR1D)

Click to expand...