- Mar 17, 2016
- Classic Mac
- Mobile Phone
So are you booting from the m2 drive?
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.
does anyone know if i can use 950 Pro SSD With NVMe on Z170 mainboard with El Capitan and boot normaly. I have searched on diferent forums and didn't get any answer.
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