Smallersen Posted January 2, 2016 Share Posted January 2, 2016 Of course. UEFI OS is the EFI partition of the 950 Pro N1-Samsung SSD 950 is the legacy entry UEFI OS (P7 Samsung 850... is my momentary system SSD Link to comment Share on other sites More sharing options...
magnifico Posted January 2, 2016 Share Posted January 2, 2016 Try uefi OS 950 pro. .. Link to comment Share on other sites More sharing options...
Smallersen Posted January 2, 2016 Share Posted January 2, 2016 There is no entry "uefi OS 950 pro", just "UEFI OS" or "N1-Samsung SSD 950". I tried both without success, also with the normal SSD 850 EVO disconnected. Link to comment Share on other sites More sharing options...
magnifico Posted January 2, 2016 Share Posted January 2, 2016 I mean uefi os Link to comment Share on other sites More sharing options...
Smallersen Posted January 2, 2016 Share Posted January 2, 2016 This was my main setting while trying of course, but it doesn´t work. I have the following "drivers64UEFI" in clover folder: DataHubDxe-64.efiEmuVariableUefi-64.efiFSInject-64.efiNvmExpressDxe-64.efiOsxAptioFixDrv-64.efiOsxFatBinaryDrv-64.efiHFSPlus.efi I use as boot flags only: -v npci=0x3000 kext-dev-mode=1 Is there something missing or too much? Link to comment Share on other sites More sharing options...
magnifico Posted January 2, 2016 Share Posted January 2, 2016 Wich gpu have You? Link to comment Share on other sites More sharing options...
Smallersen Posted January 2, 2016 Share Posted January 2, 2016 Nvidia GTX 660 Ti which work out of the box with Apple driver. Same as GTX 680. As I said, the same settings work seamlessly absolut perfect with my normal SSD. There must be a NVMe specific problem like volumes not recognized, volumes not mounted etc. Link to comment Share on other sites More sharing options...
magnifico Posted January 2, 2016 Share Posted January 2, 2016 So this Samsung 950 pro nvme is not bootable mhmm Link to comment Share on other sites More sharing options...
Smallersen Posted January 2, 2016 Share Posted January 2, 2016 Thanks anyway. Link to comment Share on other sites More sharing options...
gwincraft Posted January 6, 2016 Share Posted January 6, 2016 I'm currently trying to get Yosemite booting from an NVME drive.Hardware:Asus x99e-ws/USB3.15960xGTX 960Thunderbolt EXIISamsung sm951 nvme versionSoftware:Yosemite 10.10.5NVME driver is in S/L/E on my current boot ssd. NVME driver is also in /EFI/CLOVER/kexts/10.10 folder on the EFI partition on my boot drive.NVME drive is recognized, and usable as a non boot drive in OSX.I've done the following:1) CCC my boot drive to the NVME drive.2) Installed clover on the NVME drive.3) copied my EFI folder on my boot drive (efi partition) to the NVME drive (efi partition).4) Attempted to boot.Result:OsxAptioFixDrv: AllocateRelocBlock(): can not allocate relocation block (0x16687 pages below 0x100000000)I've also:1) CCC my boot drive to the NVME drive.2) Installed clover on the NVME drive.3) copied my EFI folder on my boot drive (efi partition) to the NVME drive (efi partition).4) Installed NvmExpressDXE-64.efi to /EFI/CLOVER/drivers64UEFI on both my boot drive and the nvme drive5) Attempted to boot.Result:OsxAptioFixDrv: AllocateRelocBlock(): can not allocate relocation block (0x16687 pages below 0x100000000) If I set "Above 4G Encoding" in my bios to "enable" then I end up hanging on whatever follows the following message: [ PCI configuration end, bridgets 16, devices 21 ] Any ideas? Link to comment Share on other sites More sharing options...
magnifico Posted January 6, 2016 Share Posted January 6, 2016 Link to comment Share on other sites More sharing options...
AppleIIGuy Posted January 6, 2016 Share Posted January 6, 2016 Why are you putting NVMExpressDxe in drivers64UEFI? My computer boots just fine without it. And NvmExpressDxe-64.efi is for LEGACY mode not UEFI mode. http://sourceforge.net/p/cloverefiboot/tickets/137/ Link to comment Share on other sites More sharing options...
gwincraft Posted January 7, 2016 Share Posted January 7, 2016 I was following the guidance from a thread on another hackintosh related forum. It was recommended there that the NvmExpressDXE-64.efi needed to be in the drivers64UEFI folder in order to work. My Clover is set up for UEFI boot only, so legacy boot (and therefore legacy drivers) don't help me here. Edit: Got it to boot from the NVME drive, but only with nv_disable=1. When I try to use my already-installed web drivers, I hang at PCI configuration begin. Link to comment Share on other sites More sharing options...
StephanCA Posted April 16, 2016 Share Posted April 16, 2016 Does anyone experience random restarts on startup/shutdown with this driver? Link to comment Share on other sites More sharing options...
Brabbelbla Posted April 24, 2016 Share Posted April 24, 2016 Yes. Link to comment Share on other sites More sharing options...
dudenesspa Posted May 6, 2016 Share Posted May 6, 2016 Any progress on getting this driver to work with 10.11.4 and beyond without kernel panics and other issues? Any other NVME solutions come about recently? Link to comment Share on other sites More sharing options...
magnifico Posted May 6, 2016 Share Posted May 6, 2016 from what I know, the developer has left the development Link to comment Share on other sites More sharing options...
AppleIIGuy Posted May 7, 2016 Share Posted May 7, 2016 What KP? My Uptime is 16+ days and no KP with NMVe driver... Link to comment Share on other sites More sharing options...
magnifico Posted May 7, 2016 Share Posted May 7, 2016 sure? on el capitain or yose? Link to comment Share on other sites More sharing options...
dudenesspa Posted May 7, 2016 Share Posted May 7, 2016 NVMeGeneric.kext kernel panic on El Cap 10.11.4. It "worked" on .1-.3 meaning I could at least get to login. Sometimes it will alternate with usbhostresources kp but I think that is more about my board and the kext I use made by someone else. My board is Gigabyte z170x gaming 7. Link to comment Share on other sites More sharing options...
AppleIIGuy Posted May 7, 2016 Share Posted May 7, 2016 El Cap 10.11.4 Link to comment Share on other sites More sharing options...
dudenesspa Posted May 7, 2016 Share Posted May 7, 2016 El Cap 10.11.4 I made it through upgrading to 10.11.4 but then I started getting the usbhostresources kp. Then I tried reinstalling from a 10.11.4 installer and then I got the NVMeGeneric.kext kernel panic. Hard to believe this has not been resolved. Link to comment Share on other sites More sharing options...
magnifico Posted May 7, 2016 Share Posted May 7, 2016 El Cap 10.11.4 you're lucky, the only person in the world who does not kp of 10.11.4 you have made some changes to your system? are you using a new revision of the kext? Here works only with Yosemite and el 10.11.3, but with only 11.4 kp Link to comment Share on other sites More sharing options...
joevt Posted May 8, 2016 Share Posted May 8, 2016 I'm using the NVMe driver in 10.11.4 to boot Mac OS X on a Gigabyte Z170X Gaming 7. I have sleep disabled so I don't know if that would cause a kernel panic. It does KP during shutdown (only 50% of the time), but I don't mind that too much since the system is mostly shutdown at that point. I have the built in serial port connected to another Mac to observe the kprintf and IOLog messages during shutdown. I've reported the contents of the output (with and without KP) at http://forums.macrumors.com/threads/nvme-for-mac-pro-5-1.1919972/page-9#post-22866241 which I believe is the thread containing the original announcement of the driver. Link to comment Share on other sites More sharing options...
AppleIIGuy Posted May 8, 2016 Share Posted May 8, 2016 I sleep my system every day with no KP. Rebooting / shutdown causes no KP. Link to comment Share on other sites More sharing options...
Recommended Posts