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

[RehabMan]

I tried to install a 960 Evo today, used the NVME script, put the NVMeHackr kext into S/L/E and got a Kernel Panic while booting. Interestingly Clover boots El Capitan just fine without the M.2 SSD installed. I'm on 10.11.6.

It means you made a mistake.
Read guide:
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

 

[reisenfs]

It means you made a mistake.
Read guide:
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

Thanks, it seems like I didn't read correctly. I don't really have access to Windows right now, so would renaming the original IONVME or moving it out of S/L/E work?

 

[RehabMan]

would renaming the original IONVME or moving it out of S/L/E work?

Yes, but it will come back first update and cause panic.
Assuming you already have a USB with the Windows installer, on fast hardware, you can install Win10 in about 15 minutes.

 

[joncas]

I tried to install a 960 Evo today, used the NVME script, put the NVMeHackr kext into S/L/E and got a Kernel Panic while booting. Interestingly Clover boots El Capitan just fine without the M.2 SSD installed. I'm on 10.11.6.

Be sure to remove the original IONVMeFamily.kext: both being present is what causes the kernel panic on my build.

 

[RehabMan]

Be sure to remove the original IONVMeFamily.kext: both being present is what causes the kernel panic on my build.

It is because you neglected to implement the class-code spoof.
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

 

[joncas]

It is because you neglected to implement the class-code spoof.
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

Yes, I know -- it's because I haven't yet been smart enough to get the SSDT correctly patched -- but your reply encourages me to try that again, so that the next OS-X update doesn't break things again ...
Many thanks!

 

[RehabMan]

Yes, I know -- it's because I haven't yet been smart enough to get the SSDT correctly patched -- but your reply encourages me to try that again, so that the next OS-X update doesn't break things again ...
Many thanks!

You can do it.

 

[x0xDJSx0x]

This is my experience so far with this driver, and I'm running Yosemite 10.10.5 on X99 Deluxe i7 5960X. I boot up to my desktop and I'm using my Samsung XP941(AHCI) m.2 on my PCI-e extension card, Then instal my Samsung 950Pro nvme to my m.2 slot bouts to my desktop and I wasn't recognize not where in OS X, but as soon as I crack open kext wizard and install the kext, a pop up message of TIME Machine asking me to use the new drive was available. So I have full access to my Samsung NVMe 950Pro M.e version of SSD. I haven't test if will be able to be bootable. I will use CCC to test and post later results.

what kext did you use and was it bootable

 

[RehabMan]

what kext did you use and was it bootable

For NVMe procedures, read here:
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

 

[iRichard]

Is there a tutorial anywhere for how to boot from NVME on High Sierra using the new drivers it comes with? thanks

edit couple weeks later: I found out that NVME works out of the box on Sierra using SSDs that support 4096 bytes block size (not Samsung those are fixed 512 bytes) so got a THNSN5512GPU7 a great MLC drive and used OZC SSD utility to format it to 4096 and all good on Sierra don't need to use High Sierra after all

Hello. i like to buy toshiba ssd (THNSN5512GPU7 ) next week. Mac pro 4.1 High sierra. You use with oem or hackintos?

Thanks!