Contribute
Register

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

Status
Not open for further replies.
Hey guys,

I am unable to get the system to boot. Here are my specs:

6900K i7
MSI Z170A Gaming M5
Samsung 950 PRO NVMe 512GB
Angelbird PX1 PCIe x4 adapter for PCIe M.2 SSDs

I first installed everything on my SSD (to make sure everything works, and it does its perfect!) then I carbon copied everything to my NVME. After booting I get the no entry icon.

Do I need to include anything in my config other than what I already have? (see attachment)

I have NvmExpressDxe-64.efi in drivers64 and NVMeGeneric.kext in kext/10.11 (and installed on drive in /system/extensions, is that bad?)

Screen Shot 2016-05-26 at 6.05.23 AM.png
 

Attachments

  • config.plist
    6.2 KB · Views: 238
Did anyone work out how to increase the slow speeds? My Samsung 950 PRO 256gb is benchmarking at 600mb/s read and write. It is in the M2 10GBs slot on the Z97x-Gaming 5 mobo.

Can't see any related bios settings, what should i be looking out for?

Thanks, if anyone has any ideas would be much appreciated!
 
For anyone wondering, this is working with my Intel 750 1TB PCiE SSD on a skylark OSX 10.11.5 build. I'm getting 1250/770 MB/S read/write

Note: I'm not using this as a boot drive, but as a scratch disk for video rendering
 
Late but not least!! :thumbup: As promised, I have provided my fix to enable sleep while using MacVidCards's NVMeGeneric.kext. I have update my guide located on this link: http://www.tonymacx86.com/threads/o...-v-extreme-x99-haswell-e.188171/#post-1218158 but for NVMe only you can directly head to Step 6 . Don't forget to like and share if this has helped you!! Cheers! :headbang:
Thanks Hans88! Could you please explain how you came up with "slot-6" for your motherboard, so I can adapt for mine?
 
Does this also fix the restart after shutdown bug that some of us are experiencing?

To be honest, I don't know. I have never met with that bug even with my previous builds' which were an x79 and an AMD very long ago. That's why I can't say much about it. But what I can suggest; Have you tried using the Clover's "fix shutdown" DSDT mask?
 
Last edited:
Thanks Hans88! Could you please explain how you came up with "slot-6" for your motherboard, so I can adapt for mine?

NVMe makes use of PCIe lanes to operate. Due to limitations, in some cases, it may have to share bandwidth with a PCIe slot. In my case, as it was mentioned in the user's manual, it shares bandwidth with PCIe Slot-6. So, I assumed that it was through that slot it was being routed through. Try to find in your manual to see with which slot it is sharing bandwidth. However, if you are using an NVMe PCIe adapter, just figure in which slot you are using that and write the same value accordingly.
 
Last edited:
To be honest, I don't know. I have never met with that bug even with my previous builds' which were an x79 and an AMD very long ago. That's why I can't say much about it. But what I can suggest; Have you tried using the Clover's "fix shutdown" DSDT mask?
Yes, the shutdown fix doesn't help. I think it only affects Gigabyte boards and it only became a problem after the OS X 10.11.4 update. I wish I had looked into it more before I bought the Samsung NVMe drive. I'm thinking about returning it to Amazon.
 
Yes, the shutdown fix doesn't help. I think it only affects Gigabyte boards and it only became a problem after the OS X 10.11.4 update. I wish I had looked into it more before I bought the Samsung NVMe drive. I'm thinking about returning it to Amazon.

Its not just limited to Gigabyte, i'm using 2 x Samsung 950 Pro NVME SSD's both as boot drives for OSX & Windows on AsRock X97 Extreme 6/3.1 and suffer the shutdown/reboot problem with OSX but apart from that it seems to work very well and blows away all my other SATA SSD's in terms of speed .. i'm still running 10.11.4.

Was hoping that more work was going to done on developing the nvme kext but that looks like not the case now.

The only real issue i see from the improper shutdown is that sometimes not all osx caches are written or closed so sometimes it looks like OSX is rebuilding/reindexing on the next boot ....

Cheers
Jay
 
Status
Not open for further replies.
Back
Top