M.2 Samsung 950 PRO SSD NVMe

[GuitarGuy77]

Thanks gabrieljsmith1,
I got the SM951 NVMe working a while ago with the NVMeGeneric.kext but since then RehabMans and Pike's fix seem like the best solution. I no longer use NVMe version for my macOS drive, I opted for a SM951 AHCI version.

Ah glad to hear you got it working! Yes mine is the AHCI version of the SM951. Its so dang neat to be able to run OS X on these

 

[wdk23411]

You can make it show internal by adding an ACPI identity for the device. For example, on my desktop, the raw PCIe device appears under PCI0->P0P1, so I created a small SSDT to add an ACPI identity:

DefinitionBlock ("", "SSDT", 2, "hack", "nvme", 0)
{
    External (_SB_.PCI0.P0P1, DeviceObj)
    Scope (_SB.PCI0.P0P1)
    {
        Device (SSD0)
        {
            Name (_ADR, Zero)
        }
    }
}

Hi RehabMan, here is my IOreg zip file. Would you mind help me to find how could I get my Intel 750 ssd show as "internal". Thanks a lot.

 

[RehabMan]

Hi RehabMan, here is my IOreg zip file. Would you mind help me to find how could I get my Intel 750 ssd show as "internal". Thanks a lot.

There is a PCI bridge along the path to your SSD. No experience with them...
So... This is just a guess:

// Add ACPI identity for device under PCI bridge port 0x10 (address 0x00100000) under BR2A.H000
DefinitionBlock("", "SSDT", 2, "hack", "nvme", 0)
{
    External(_SB.PCI0.BR2A.H000, DeviceObj)
    Scope(_SB.PCI0.BR2A.H000)
    {
        Device(BR10)
        {
            Name(_ADR, 0x00100000)
            Device(SSD0) { Name(_ADR, 0) }
        }
    }
}
//EOF

 

[wdk23411]

There is a PCI bridge along the path to your SSD. No experience with them...
So... This is just a guess:

// Add ACPI identity for device under PCI bridge port 0x10 under BR2A.H000
DefinitionBlock("", "SSDT", 2, "hack", "nvme", 0)
{
    External(_SB.PCI0.BR2A.H000, DeviceObj)
    Scope(_SB.PCI0.BR2A.H000)
    {
        Device(BR10)
        {
            Name(_ADR, 0x10)
            Device(SSD0) { Name(_ADR, 0) }
        }
    }
}
//EOF

Thanks for reply. It seems that the code doesn't work for me. And all the usb3.0 port doesn't work after follow you suggestion except the USB3.1 port. Perhaps I should choose another motherboard.

Edit: The patch worked by change the "0x10" to "0x00100000". Thank you very much.

 

[RehabMan]

Edit: The patch worked by change the "0x10" to "0x00100000". Thank you very much.

OK. Good... I edited my original proposal to avoid confusion.

Can you attach an image of what you see for the NVMe in Windows Device Manager for "Location paths"?

See here: https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

 

[wdk23411]

Can you attach an image of what you see for the NVMe in Windows Device Manager for "Location paths"?

Sorry , I have only one OS installed. I will make a test once I receive my new SSD.

 

[5star]

Where can I get a copy of the vanilla IONVMeFamily.kext to repatch?

I am having problems and would like to do a patch, but I can't because I deleted it when I patched before.

 

[RehabMan]

Where can I get a copy of the vanilla IONVMeFamily.kext to repatch?

Vanilla IONVMeFamily.kext is installed by the OS X/macOS installer.

 

[5star]

Vanilla IONVMeFamily.kext is installed by the OS X/macOS installer.

So the only way to get the kext back is to re-install the OS?

 

[joevt]

So the only way to get the kext back is to re-install the OS?

Use Pacifist.app at https://www.charlessoft.com to open the installer package that contains the IONVMEFamily.kext and use that to install it. It should have version 2.1.0 for macOS 10.12.3 and version 1.2.0 for Mac OS X 10.11.6.