RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,016
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
RehabMan, So now I have this for the SSDT-NVMe-Pcc.aml, which is my drive's ACPI path and the extra injections for the 960 EVO, does that look right?
Code:DefinitionBlock ("", "SSDT", 2, "hack", "NVMe-Pcc", 0x00000000) { External (_SB_.PCI0.EXP5.PXSX, DeviceObj) // (from opcode) Method (_SB.PCI0.EXP5.PXSX._DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LNot (Arg2)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x0A) { "class-code", Buffer (0x04) { 0xFF, 0x08, 0x01, 0x00 }, "built-in", Buffer (One) { 0x00 }, "compatible", Buffer (0x0D) { "pci144d,a801" }, "IOName", "pci144d,a801", "name", Buffer (0x0D) { "pci144d,a801" } }) } }
I still have an issue though. I had reinstalled the OS and updated while using the NVMeGeneric.kext, and now Apple's latest security update is newer than the "Security Update 003" that you support; it is "Supplemental Security Update 003" which reports as: OS X 10.11.6 (15G1217)
Your script builds a kext but with these warnings, so I'm guessing it won't work:
$ ./patch_nvme.sh --spoof 10_11_6_sec2016-003
Code:Creating patched HackrNVMeFamily-10_11_6_sec2016-003.kext WARNING: Vanilla MD5 (0aed9374ab41e40976bd191cba126423) does not match expected MD5 (b3b4dd50b2bbd9cc4dc901fad12643ac) WARNING: Patched MD5 (477dadd3231cbe4327813fa1832871fc) does not match expected MD5 (6ea6fd529ee962f6308b95a854897556)
Might you be adding support for the supplemental version of 003? If not, then should I be able to apply the non-supplemental update version now that this one is already in place?
Attach your IONVMeFamily.kext.