Contribute
Register

M.2 Samsung 950 PRO SSD NVMe

Status
Not open for further replies.
I am booting from the 950 PRO M.2 NVMe. The NVMeGeneric.kext cannot be installed in /Library/Extensions for me, or the system won't boot. The only way this worked for me, was by installing the NVMeGeneric.kext in the EFI partition ONLY.

After installing the CLOVER EFI package and the Post-Install packages, I had to switch to the UniBeast's CLOVER config.plist from the USB drive, or I could not boot. So, there is something in the post-install config.plist that keeps my system from booting from the M.2 NVMe drive. I haven't had the time yet to isolate what that is, though.

Word of caution: do not go on a 24-hour-straight bender trying to figure this out after a full workday.
 
hey,

thanks for sharing your progress with this. it helped me a great deal.
i managed to get a working, bootable install on the 950 NVMe by placing the driver in the EFI partition.



but now i'm stuck in the same situation.
whenever i use multibeast to update the kexts and boot config the system will hang at startup and give me the 'no entry' sign.
so i'm currently left with a system with no nvidia drivers and audio
and don't know how to proceed. :(
 
There is an AHCI version of this drive, does this work any better?
 
hey,

thanks for sharing your progress with this. it helped me a great deal.
i managed to get a working, bootable install on the 950 NVMe by placing the driver in the EFI partition.

You bet! Glad my suffering helped someone out. I've found out that you have to keep extensive written notes while trying this, because:

(a) it takes a __LOOOONG__ time to get everything working properly, and
(b) my mind can get loopy, and I sometimes wonder "have I tried the XYZ suggested from the thread IJK?"

Keeping detailed notes really helps. Plus I have them handy in case I'm re-installing ten months from now, by which time I will have forgotten everything I've tried to get the original setup working. I tend to keep my hardware setups for 5+ years, so having these notes comes in super-handy.

but now i'm stuck in the same situation.
whenever i use multibeast to update the kexts and boot config the system will hang at startup and give me the 'no entry' sign.
so i'm currently left with a system with no nvidia drivers and audio
and don't know how to proceed. :(

I'm not sure what you mean here. I don't use MultiBeast to update kexts -- I usually just drop the kexts where they need to go, and manually rebuild the caches.

Which kexts are you trying to update? Why?

What state *exactly* are you being left in (what hardware configuration do you have, what works, what doesn't, etc.)? More detail is always better than less, even if it seems like you're repeating yourself here.

I've also discovered JUST TODAY that I need the 'npci=0x2000' boot flag together with my 'nvda_drv=1' in the Clover's 'config.plist', or my system continually reboots just before I get the login screen. I'm using a PNY GeForce GTX 970 with dual dual-channel-mini-DVI outputs with my dual Apple CinemaDisplays -- if your setup is sufficiently different, it may not help you. But I hope it does. My boot flags in Clover's 'config.plist' are:

dart=0 npci=0x2000 nvda_drv=1 kext-dev-mode=1

and I'm running El Capitan 10.11.4.

I've read in another discussion thread that the 'kext-dev-mode' isn't needed with ElCap, but I don't see how FakeSMC and the IntelMausiEthernet kexts would get loaded without it. So I'm keeping it.

Are you trying to use the on-board audio?

I gave up on that a long time ago -- too messy. I've instead invested in 'AudioEngine D1' -- yes it's pricy, but I cannot imagine just how much time I've saved by *NOT* having to deal with various hacks to get the on-board audio working. To me, the cost of the AudioEngine unit was worth it. Plus the audio quality is a *LOT* better, IMO.
 
It's working great on my Hack in 10.11.5!
post-67982-0-91932200-1467258363.jpg post-67982-0-04242700-1467258475.pngAJATest.jpg
 
I am booting from the 950 PRO M.2 NVMe. The NVMeGeneric.kext cannot be installed in /Library/Extensions for me, or the system won't boot. The only way this worked for me, was by installing the NVMeGeneric.kext in the EFI partition ONLY.

After installing the CLOVER EFI package and the Post-Install packages, I had to switch to the UniBeast's CLOVER config.plist from the USB drive, or I could not boot. So, there is something in the post-install config.plist that keeps my system from booting from the M.2 NVMe drive. I haven't had the time yet to isolate what that is, though.

Word of caution: do not go on a 24-hour-straight bender trying to figure this out after a full workday.

I'm on a different hardware (Inte NUC6i5syh) but using a NVME 950 PRO as a boot device (El Capitan).
It works very well with NVMeGeneric driver, but it doesn't show up in any System Report listing: how can I check in your opinion if TRIM has been enabled? I've run trimforce enable on the cmdline ... but how to check it has been applied to my drive ?

How have you been able to let your system see it as internal?
Any help would be welcome :)
 
I'm on a different hardware (Inte NUC6i5syh) but using a NVME 950 PRO as a boot device (El Capitan).
It works very well with NVMeGeneric driver, but it doesn't show up in any System Report listing: how can I check in your opinion if TRIM has been enabled? I've run trimforce enable on the cmdline ... but how to check it has been applied to my drive ?

How have you been able to let your system see it as internal?
Any help would be welcome :)

You quoted a message from April, but the message that shows the system seeing the NVMe drive as internal was from this week. Reread #67 and follow the link. After removing NVMeGeneric.kext, applying the NVMeFamily patch settings to config.plist, and restarting, the NVMe drives should appear in System Profiler and will show that TRIM is enabled.
 
Status
Not open for further replies.
Back
Top