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

[UNOE]

Ok, thank you for replying. Samsung SM951 is available both NVMe and AHCI type, 128 and 256Gb (and greater) so I could try the AHCI model through the PCIe adapter......

If it works it would be a great way to keep that x58 in the same league as x79. With 6 core already your not lacking much.

 

[ppcnostalgic]

I googled for infos and someone says it works as bootable disk in a real Mac Pro 4.1 and 5.1... These machines have a X58 chipset on mobo just like my Gigabyte, so I think it should work but I'm not sure about real speed-wise benefits. As you said in previous post PCIe 2.0 could really be a bottleneck and the difference, if any, probably would not be as big as expected compared to my Vertex4 SSD Sata3 that I'm running now to boot the system. Anyway thank you for your hints, so kind helping me about my old stuff...

 

[UNOE]

I googled for infos and someone says it works as bootable disk in a real Mac Pro 4.1 and 5.1... These machines have a X58 chipset on mobo just like my Gigabyte, so I think it should work but I'm not sure about real speed-wise benefits. As you said in previous post PCIe 2.0 could really be a bottleneck and the difference, if any, probably would not be as big as expected compared to my Vertex4 SSD Sata3 that I'm running now to boot the system. Anyway thank you for your hints, so kind helping me about my old stuff...

Well for one the Intel Sata 2.0 ports are faster than Sata 3.0 ports on that board for 4K benchmarks and access times. So you should benfit greatly even if limited to PCIe 2.0. I would expect it to be much faster. In every aspect file size type. When I owned that board I used Intel Sata ports because it was snappier.

 

[zixonx]

I used the NVME driver from this thread and successfully installed 10.11.3 and got it bootable, using an asus z170i-pro gaming with sm951 nvme 256GB, but it appears that the driver has some potential problems that it occasionally crashes when the system shutdown, and turn the shutdown into a reboot with a panic notice... I don't know what to do to fix it but changing my start-up drive to a regular sata drive.....
Is there anyone had encountered the same and could solve it? thank you guys all, and sorry for my English...

 

[zixonx]

I've been using this driver for a week now with system 10.11.2 and a Samsung SM951 (nvme), installing it via the Clover kext injection.
Everything works fine except that at shutdown it often crashes leading to the system message that a problem occurred at the next boot.

Has anyone else seen this problem ?

The only other place I found this mentioned is here :
http://www.apple-art.com/NVMe-for-Mac-Pro-5-1_10916299-10.html

Enclosed is my crash log showing that the NVMe kext is at the origin of the problem, in case anyone has an idea ...

View attachment 171848

hi joncas，I got the same problem here, with my asus z170i-pro gaming with sm951 nvme 256GB... I don't know what to do to fix it but changing my start-up drive to a regular sata drive.....
have you came up with something could solve this? thank you!

 

[UNOE]

I used the NVME driver from this thread and successfully installed 10.11.3 and got it bootable, using an asus z170i-pro gaming with sm951 nvme 256GB, but it appears that the driver has some potential problems that it occasionally crashes when the system shutdown, and turn the shutdown into a reboot with a panic notice... I don't know what to do to fix it but changing my start-up drive to a regular sata drive.....
Is there anyone had encountered the same and could solve it? thank you guys all, and sorry for my English...

try disabling CSM and fast boot.

 

[zixonx]

try disabling CSM and fast boot.

Thank you UNOE!
I did what you say and it does reduced the frequence of the panic notice, it used to shows up every time the system shuts or reboots, now it is much less than before, but it still could show every now and then, and I can't figure out its rule... So do you have any further suggestions for fixing it for good?
Thank you again and please forgive my English....

 

[mantes]

In my opinion, do not put the kext into S/L/E or L/E, just let clover inject it. I doubted the system would load the kext on an unknown device before the kext be loaded.
BTW: the clover option "Inject Kexts" will cause some issues. Clover would not inject the kext when it detected the system has a same kext which would not be loaded when the system was booting.

Sorry for my English.

Thanks for the info. So far the system has been booting perfectly after removing the NVMe kext from S/L/E & L/E and letting Clover inject from the 10.10 folder and I'm no longer using the usekernelcache=no flag. Also repaired permissions and rebuilt kext cache as a precaution.

I will say that the system seemed to boot faster with the NVMe kext in the folders with the usekernelcache=no flag which seems to work with no issue, except when I was messing with a raid controller card and I'll sum that up to user error because I wasn't able to duplicate when things were done correctly.

 

[UNOE]

Thank you UNOE!
I did what you say and it does reduced the frequence of the panic notice, it used to shows up every time the system shuts or reboots, now it is much less than before, but it still could show every now and then, and I can't figure out its rule... So do you have any further suggestions for fixing it for good?
Thank you again and please forgive my English....

Try a enabling one disabling another, combination of the two. Also try different UEFI option like UEFI first for storage and video card or legacy first for video card depending on your hardware of course.

 

[jclusso]

UPDATE:

After looking further I've confirmed it is definitely related to the NVMe drive. I get a bunch of errors like this when resuming from sleep. Does anyone else have this issue?

Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: nvme_timeoutJan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:58 nsid:1 lba:68305480 len:8
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:58 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:53 nsid:1 lba:68313072 len:8
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:53 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:52 nsid:1 lba:68317280 len:8
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:52 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:51 nsid:1 lba:68317296 len:16
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:51 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:92 nsid:1 lba:68317416 len:8
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:92 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:78 nsid:1 lba:68317432 len:32
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:78 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:55 nsid:1 lba:68317472 len:16
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:55 cdw0:0
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: aborting outstanding i/o
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: WRITE sqid:1 cid:110 nsid:1 lba:68317496 len:8
Jan 24 20:03:35 iMac kernel[0]: NVMeGeneric: ABORTED - BY REQUEST (00/07) sqid:1 cid:110 cdw0:0

Two questions...

- Does anybody have a weird freeze for like 5-10 seconds when coming out of sleep?
- Does anybody have a kernel panic only when rebooting but than it starts up fine.

Running this on a PCIe card in a Gigabyte z97 Gaming 7.