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

[RehabMan]

So I have moved all my other Kexts for my particular build and needs to /L/E... except HackrNVMeFamily-10_12_3.kext because my machine crashes if I put it in /L/E instead of /S/L/E. Is there any reason why that is?

If class-code spoof is implemented correctly and SIP is disabled properly, HackrNVMeFamily will work from /L/E or /S/L/E equally.

 

[pingupop]

Hi,
First RehabMan, thanks for all the work. Let me know where I can donate.

Trying to get the code right for my location path.
My Location paths under Windows 10 for the Samsung 950 (PCI-Adapter):

PCIROOT(0)#PCI(0101)#OCI(0000)
ACPI(_SB_)#ACPI(PC0)#ACPI(PEG1)#ACPI(PEGP)

I guess I need to change 0x0008000 and PBR8, but to what?

// Inject bogus class-code for NVMe SSD to prevent IONVMeFamily.kext from loading
DefinitionBlock("", "SSDT", 2, "hack", "NVMe-Pcc", 0)
{
    External(_SB.PCI0.PEG1.PEGP, DeviceObj)
    // create identities for the bridge @8 and SSD0 @0
    Device(_SB.PCI0.PEG1.PEGP.PBR8)
    {
        Name(_ADR, 0x00080000)  // corresponds to #PCI(0800), MSW byte reversed
        Device(SSD0) { Name(_ADR, 0) } // corresponds to #PCI(0000)
    }
    // now we can inject the _DSM at the newly created ACPI path
    Method(_SB.PCI0.PEG1.PEGP.PBR8.SSD0._DSM, 4)
    {
        If (!Arg2) { Return (Buffer() { 0x03 } ) }
        Return(Package()
        {
            "class-code", Buffer() { 0xff, 0x08, 0x01, 0x00 },
            "built-in", Buffer() { 0 },
        })
    }
}
//EOF

 

[RehabMan]

ACPI(_SB_)#ACPI(PC0)#ACPI(PEG1)#ACPI(PEGP)

It appears you have a full ACPI path already (ignoring/fixing your obvious typo).

_SB.PCI0.PEG1.PEGP

 

[pingupop]

It appears you have a full ACPI path already (ignoring/fixing your obvious typo).

_SB.PCI0.PEG1.PEGP

Oops Shame on me.

 

[Bozmantate]

I followed the Post #1 guide but still not seeing either of my 2 x MVMe drives (1 x Toshiba and 1 x 960 EVO)


I used
_SB_.PCI0.RP09.SSD0
_SB_.PCI0.RP13.SSD0

to create the .aml

created --spoof .kext and copied to USB/ACPI/patched for installer and HDD/S/L/E using Kext Utility

I don't see either in USB/installer/system utility but both show up in BIOS

what am I missing?

my clover is attached here CLOVER.zip

 

[Bozmantate]

I used
_SB_.PCI0.RP09.SSD0
_SB_.PCI0.RP13.SSD0

to create the .aml

sorry typo revision i used
_SB.PC10.RP09.SSD0
_SB.PC10.RP13.SSD0

to create the .aml

 

[RehabMan]

I followed the Post #1 guide but still not seeing either of my 2 x MVMe drives (1 x Toshiba and 1 x 960 EVO)
View attachment 236634 View attachment 236635

I used
_SB_.PCI0.RP09.SSD0
_SB_.PCI0.RP13.SSD0

to create the .aml

created --spoof .kext and copied to USB/ACPI/patched for installer and HDD/S/L/E using Kext Utility

I don't see either in USB/installer/system utility but both show up in BIOS

what am I missing?

my clover is attached here CLOVER.zip

Your Windows Device Manager image shows no ACPI identity for the SSD (leaf node).
Read post #1 for how to add it.
You did not provide any Device Manager image for the NVMe device at RP13.

 

[Bozmantate]

Your Windows Device Manager image shows no ACPI identity for the SSD (leaf node).
Read post #1 for how to add it.

are you suggesting that i add SSD0 or PXSX as the leaf node?

or because i am using 960EVO (Special injections required for 10.11.x and Samsung 960 EVO (or other 144d:a804 NVMe device)? (I'm using 10.12.03)

You did not provide any Device Manager image for the NVMe device at RP13.

both of the ID's are displayed in the Device Manager image (RP09 and RP13)

 

[RehabMan]

are you suggesting that i add SSD0 or PXSX as the leaf node?

You have to add the leaf node for each as your path indicates no ACPI identity for the trailing #PCI(000)). The name does not matter. My examples use SSD0 when they are added.

 

[blitzthis77]

Hello Everyone Happy to make my first very confused post. Tried to follow the guide to a T, but obviously made a mistake somewhere. I have attached the requested files, and would love to get a hand if possible. I have tried both the with then _DSM Rename in Xcode and without (this version shows without) and it doesn't make any difference. I figure I made an error in entering the .aml data, but my eyes haven't found it yet. Thanks for this amazing forum and environment!