If you unplug a ThunderBolt connected NVMe device crashes may occur. Q: Does this driver support hot-plug for ThunderBolt configurations?Ī: yes, however it does not support hot “un-plug”. Q: Can I use this to support an NVMe device in an external ThunderBolt enclosure like the Akitio? Why they use the NVMe name for a non-compliant device and driver is a mystery.

Q: Doesn’t Apple supply NVMe drivers and EFI boot ROMs for their new machines?Ī: Apple chose to make their NVMe devices and drivers non-compliant with the NVMe standard. Q: What devices have you tested this with?Ī: Intel P3700 series, Samsung SM1715 and SM951 seriesĪ: No, not until someone writes a standards compliant EFI driver for the Macintosh. Q: What version of OS X does this driver support?Ī: /Library/Extensions – Note that the owner and group for the entire kext MUST be set to root:wheel Just downloaded and tested the brilliant new driver for NVME m.2 x 4 PCIe from Checkit it out! And yes, you really need to remove the drivers from your fw because otherwise they will connect rather than the one you added with bcfg. If it works for a few tries/hours/days, you can convert to ffs and flash.

Now the NVMe driver will load automatically on every boot and it will be pretty much like you flashed it, just that it's on a disconnectable storage. I trust TianoCore more than the AMI or OEM junk anyway.Īnd of course there is always a chance of bricking, but if you want to be sure and have a 'feeling' of how it will be with the driver flashed, remove the NVMe drivers from your fw, move Clover's to the root of the ESP of a NON-NVMe drive (USB, HDD or whatever), run 'ls fsX:' - replacing X with a number starting at 0 - till you found the correct volume and finally enter: bcfg driver add 1 NvmExpress.efi 'NvmExpress' I'm also not sure why a device driver that should only be used at boot time needs a SMM driver as well. The Clover driver should be the one shipping with EDK2, but I'm not sure.

UEFITool A67 instal the new for windows