Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It sounds like the only way to get it to boot would be to install Clover and have it inject the kext. Otherwise, the kext would have to go in to /S/L/E/ or /L/E/ which would require that macOS to have already started booting which isn't possible without the kext if the NVMe drive is the boot drive.

From https://github.com/RehabMan/patch-nvme:
Screen Shot 2016-10-25 at 8.03.13 PM.png
 
You don't need Clover for a Mac Pro. Install macOS on a spare SATA drive (non NVMe) and create the HackrNVMeFamily-10_12_0.kext on the spare drive installation in accordance to RehabMan's instructions. Put the HackrNVMeFamily-10_12_0.kext on the Desktop and install it with KextBeast. Then, remove the IONVMeFamily.kext from the spare drive's /System/Library/Extensions/ folder and reboot without caches to the spare drive. (I can't remember the way to clear caches; I use OnyX or a similar program before rebooting.)

You should now see the NVMe SSD. Install Sierra to the NVMe. Remove the IONVMeFamily.kext from the NVMe drive's /System/Library/Extensions/ folder. Install the HackrNVMeFamily-10_12_0.kext into the NVMe drive's /System/Library/Extensions/ folder using KextBeast which will let you select the NVMe drive while running from the spare drive. (KextBeast defaults to the current drive but will allow you to change the drive as the last option you can choose before installation of the kext).

Change the startup drive in the System Preference's Startup Disk to the NVMe.

Now restart.

Note: I have not tried the above procedure on either of my Mac Pros because I don't use a NVMe in them yet. But, I have a hackintosh that uses the Samsung 950 Pro M.2 NVMe. So, the above procedure should work. YMMV.

Edit:
As was pointed out below, the above procedure will probably not work since the Mac Pro BIOS only supports SATA drive recognition. Too bad for us.

Reference:
RehabMan's patch-nvme: https://github.com/RehabMan/patch-nvme
KextBeast: https://www.tonymacx86.com/resources/categories/tonymacx86-downloads.3/
 
Last edited:
  • Like
Reactions: LightBulbFun
You don't need Clover for a Mac Pro. Install macOS on a spare SATA drive (non NVMe) and create the HackrNVMeFamily-10_12_0.kext on the spare drive installation in accordance to RehabMan's instructions. Put the HackrNVMeFamily-10_12_0.kext on the Desktop and install it with KextBeast. Then, remove the IONVMeFamily.kext from the spare drive's /System/Library/Extensions/ folder and reboot without caches to the spare drive. (I can't remember the way to clear caches; I use OnyX or a similar program before rebooting.)

You should now see the NVMe SSD. Install Sierra to the NVMe. Remove the IONVMeFamily.kext from the NVMe drive's /System/Library/Extensions/ folder. Install the HackrNVMeFamily-10_12_0.kext into the NVMe drive's /System/Library/Extensions/ folder using KextBeast which will let you select the NVMe drive while running from the spare drive. (KextBeast defaults to the current drive but will allow you to change the drive as the last option you can choose before installation of the kext).

Change the startup drive in the System Preference's Startup Disk to the NVMe.

Now restart.

Note: I have not tried the above procedure on either of my Mac Pros because I don't use a NVMe in them yet. But, I have a hackintosh that uses the Samsung 950 Pro M.2 NVMe. So, the above procedure should work. YMMV.

Reference:
RehabMan's patch-nvme: https://github.com/RehabMan/patch-nvme
KextBeast: https://www.tonymacx86.com/resources/categories/tonymacx86-downloads.3/

Looks strange to me.

The driver stored inside the NVMe SSD.

The system can't see the NVMe SSD until driver loaded.

So, how can the system load the kext without seeing it at the beginning?

I can understand that the NVMe SSD is totally usable after boot from another SSD, but can't see how's possible to boot from itself.

It works on a Hackintosh most likely because that Hackintosh support NVMe SSD natively.
 
Looks strange to me.

The driver stored inside the NVMe SSD.

The system can't see the NVMe SSD until driver loaded.

So, how can the system load the kext without seeing it at the beginning?

I can understand that the NVMe SSD is totally usable after boot from another SSD, but can't see how's possible to boot from itself.

It works on a Hackintosh most likely because that Hackintosh support NVMe SSD natively.

Edit: You're probably right since the Mac Pro BIOS doesn't recognize non SATA drives. Oh, well, you can still use RehabMan's patch-nvme since NVMeGeneric.kext doesn't work with Sierra.
 
Last edited:
The Mac Pro doesn't have an NVMe EFI driver, so unless this guy finishes his work it's not possible to directly boot it. It should be possible though to store the boot.efi and kext cache (which can contain an NVMe driver) on a different volume. It's quite nasty though, wouldn't recommend that for everyday use.
 
I'm currently experimenting to see if Amfeltec card is stable to handle my graphics intensive work but it keeps crashing every time I quit or restart my MacPro5,1. I have four SM951 sticks fixed to it and created a RAID 0 disk using SoftRAID 5.5. Installing ElCap went without any problem but when I shutdown the machine a wheel keeps spinning on a black background and it goes on and on. Each time I have to force quit my Mac and this is giving me some concerns of possibly corrupting files. Has anyone experienced this?

I want to write a followup on the problem I was having with my Amfeltec Squid x4. I wrote about this on July 17 here in this thread but the problem had persisted ever since and it was frustrating to watch and wait for the spinning wheel to disappear each time I shutdown my MP5,1, which usually would go on endlessly.

During the past month, I did two things: One, I had a hunch that the problem was a cache related issue and, after sifting through them in System folder, I discovered that throwing away System/Library/Caches/com.apple.coresymbolicationd/data helped produce a smooth shutdown. Two, when I tried the Lycom DT-120 in place of Squid, this adapter worked fine and the shutdown sequence proceeded normally. Also at one point my MP5,1 produced intermittent I/O errors and I was sure there was something strange going on with the Squid card and I guessed that my Mac would try to record all errors in the cache file but was unable to write them, or something like that.

Recently I had a chance to buy another Squid adapter for another machine and this time I decided to get a x16 model and experimented it on my machine and voila! This card worked perfectly in the same slot #3. Obviously the difference was in the spec, x16 against my earlier x4, but this time Amfeltec sent me a card with a cooling fan attached to the inner end of the card. They also included four heat sinks in the box which adhered to four SSD blades (SM951 512GB AHCI).

They call their current Squid card Gen.3 and I must assume the people at Amfeltec have addressed the heat issue and upgraded their product accordingly. I don't know if these cooling devices are included with their current x4 card but if anyone is seeing similar symptoms, I would strongly recommend getting a Gen.3 adapter. Now that I want to move on to Sierra soon, I’m going to replace my card in the next few weeks.

Sorry, if this is an old news.
 
  • Like
Reactions: zoltm and m4v3r1ck
Now that I want to move on to Sierra soon, I’m going to replace my card in the next few weeks.

It turned out that I was allowed to keep the Squid x16 very fortunately and I went ahead with installing Sierra right away. Well, actually, Sierra handles the shutdown issue much better. I have encountered NO hangup so far. This must have been an OS related issue.
 
  • Like
Reactions: m4v3r1ck
I want to write a followup on the problem I was having with my Amfeltec Squid x4. I wrote about this on July 17 here in this thread but the problem had persisted ever since and it was frustrating to watch and wait for the spinning wheel to disappear each time I shutdown my MP5,1, which usually would go on endlessly.

During the past month, I did two things: One, I had a hunch that the problem was a cache related issue and, after sifting through them in System folder, I discovered that throwing away System/Library/Caches/com.apple.coresymbolicationd/data helped produce a smooth shutdown. Two, when I tried the Lycom DT-120 in place of Squid, this adapter worked fine and the shutdown sequence proceeded normally. Also at one point my MP5,1 produced intermittent I/O errors and I was sure there was something strange going on with the Squid card and I guessed that my Mac would try to record all errors in the cache file but was unable to write them, or something like that.

Recently I had a chance to buy another Squid adapter for another machine and this time I decided to get a x16 model and experimented it on my machine and voila! This card worked perfectly in the same slot #3. Obviously the difference was in the spec, x16 against my earlier x4, but this time Amfeltec sent me a card with a cooling fan attached to the inner end of the card. They also included four heat sinks in the box which adhered to four SSD blades (SM951 512GB AHCI).

They call their current Squid card Gen.3 and I must assume the people at Amfeltec have addressed the heat issue and upgraded their product accordingly. I don't know if these cooling devices are included with their current x4 card but if anyone is seeing similar symptoms, I would strongly recommend getting a Gen.3 adapter. Now that I want to move on to Sierra soon, I’m going to replace my card in the next few weeks.

Sorry, if this is an old news.

Thanks for your insights for this card! Great card, but with a great (to much for my budget) price tag! :eek:

[doublepost=1477922960][/doublepost]
It turned out that I was allowed to keep the Squid x16 very fortunately and I went ahead with installing Sierra right away. Well, actually, Sierra handles the shutdown issue much better. I have encountered NO hangup so far. This must have been an OS related issue.

That's great news then!

Enjoy your Squid x16 / cooling fan / heatsinks edition! Could you please post a screen-cap with the SSD's & heatsinks installed?

Cheers
 
i wonder those little cute SSD can work in cMP and wonder third party like sintech mind to create an PCIe adapter to work with...

i planning to extending old cMP little longer and planning upgrade using SSUBX but those little things tempt me, main problem those little SSD contain proprietary NVMe Apple controller which is cumbersome for cheese grater which doesn't have NVMe capability baked in logicboard
 
I can't find the AHCI version of the SM951 (MZHPV512HDGL) and don't feel like buying two 120 cards with two 256GB sticks (MZHPV256HDGL). Since I don't work with large files, no Photoshop, no video work, only DAM for my photos (200GB library) I would presume it'll be enough for me, speed wise, to simply stick a SATA2 SSD in one of the four HDD bays. Any suggestions? 500GB capacity covers me for macOS, sw, and my photos.

Oh yeah, MP5,1 plain stock model.

TIA!
 
I can't find the AHCI version of the SM951 (MZHPV512HDGL) and don't feel like buying two 120 cards with two 256GB sticks (MZHPV256HDGL). Since I don't work with large files, no Photoshop, no video work, only DAM for my photos (200GB library) I would presume it'll be enough for me, speed wise, to simply stick a SATA2 SSD in one of the four HDD bays. Any suggestions? 500GB capacity covers me for macOS, sw, and my photos.

Oh yeah, MP5,1 plain stock model.

TIA!

Have you tried looking for the Apple SSUBX in 512GB?
 
this might be a dumb question, but are there any adaptors to make a standard PCIe SSD work in a 2013 Mac Pro? That would be my ideal solution- adding a Samsung 960 Evo to my trashcan internally
 
this might be a dumb question, but are there any adaptors to make a standard PCIe SSD work in a 2013 Mac Pro? That would be my ideal solution- adding a Samsung 960 Evo to my trashcan internally

Isn't 960 Evo NVMe only? How can it work on any Mac Pro? (At least not bootable)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.