Contribute
Register

OS X Driver for NVMe M.2 Solid State Drives Released

Status
Not open for further replies.
No need to switch to NVMeGeneric.kext at any point during the transition. Just install the HackrNVMeFamily-10.11.5.kext and at the same time, remove the patches for IONVMeFamily from your config.plist.


Hello,
If I am doing a new install can I use the HackrNVMeFamily instead of the NVMeGeneric.kext?
 
Hello,
If I am doing a new install can I use the HackrNVMeFamily instead of the NVMeGeneric.kext?
HackrNVMeFamily works if you put it in the EFI/Clover/Kexts/10.11 folder of the USB drive when I'm running 10.11.5. If the OS X installer is also 10.11.5, then there shouldn't be a problem. I don't know if it would be compatible with earlier or later versions of OS X or the OS X installer without trying it.

You can try HackrNVMeFamily first, but have NVMeGeneric available on the flash drive in case you need to switch them using the EFI Shell or a working Mac.
 
According to RehabMan's Readme, the patch_nvme.sh needs to be executed with the OS x system version as an argument. So, for El Capitan 10.11.5, you'll need to do the following commands in the Terminal:
Code:
cd ~/Downloads/patch-nvme-master
./patch_nvme.sh 10_11_5

Therefore, when you upgrade to 10.11.6, you need to recreate the kext using the argument "10_11_6". Note that you'll have to create the 10.11.6 version before you update to 10.11.6 and place it in the Config.plist's EFI/.../kexts/10.11.6 folder, then update to 10.11.6.

However, before each update, check RehabMan's site (at the above link) to see if the patch_nvme.sh has been updated. :thumbup:
 
The easiest way to go is the AHCI M.2 SSD blade. The NVMe versions are still not natively supported by Apple in El Capitan. I used the Samsung 950 Pro in my Gene build, but, when I recently built MyHero, I use the Samsung 951 ACHI to avoid the hassle. YMMV.
 
The patch by Pike R is working for me as well. Installed using RehabMans script and put in Kexts/10.11 .

Mighty thanks for all the work you are doing.
 
Does anyone have benchmarks from the 1.2TB Intel 750 series? I am getting close write speeds, but the read speeds are way off. Anyone have any solutions?

I have the generic kext, no nvme driver because mobo has native support. Anyone know why my reads are so low?

Most of the USB 3.0 ports also don't work, and bluetooth also doesn't work, but I'm still working on this build.
 

Attachments

  • Screen Shot 2016-07-10 at 11.07.40 PM.png
    Screen Shot 2016-07-10 at 11.07.40 PM.png
    12.1 MB · Views: 368
FYI for any other Intel 750 owners:

* According to this blog post from Pike, it seemed to imply that some of the patches in Sierra's stock IONVMeFamily.kext was to workaround a non-4096B LBA size.

So I tried erasing the 750 and formatting it with LBAFormat=3 as instructed here (note: the latest 3.0 version of the DCT has a slightly different syntax for passing in the NVMeFormat command, use -h to see the correct syntax), and it seems to work!

Note you still need the rest of RehabMan's patches on Info.plist and the binary patching of AppleNVMeController -> HackrNVMeController.

* I needed to put HackrNVMeFamily.kext on the EFI partition in Clover to boot from it. When I tried putting it in /L/E, or tried using Clover's kext patching mechanism, it wouldn't boot (waiting for root device error.)
 
So I'm assuming you mean these files (see attachment). What do I do with them? Maybe that's where I went wrong? I didn't do anything with those two files, I just put NVMeGeneric.kext in the EFI folder for Clover boot and installed 10.11.5. Can you elaborate or point me in the right direction?

and it seems to work!

When you say it works does that mean you successfully format it or that after formatting, installing OS and testing benchmarks you got the advertised speeds?

So what I am getting here is, reformat and make the 750 LBAFormat=3, then do something with those two files, and then the 750 should be getting the right speeds? I benchmarked on windows 10 and the 750 performs as advertised.
 

Attachments

  • Screen Shot 2016-07-11 at 6.26.13 PM.png
    Screen Shot 2016-07-11 at 6.26.13 PM.png
    181.4 KB · Views: 298
Does SIP need to be set to 0x03 (unsigned kexts) for the patched kext to work?

I always set CsrActiveConfig=0x67. Less problems that way.
 
Status
Not open for further replies.
Back
Top