Contribute
Register

OS X Driver for NVMe M.2 Solid State Drives Released

Status
Not open for further replies.
seyedhossein said:
if edit config.plist and paste to usb bootable, carash on boot

I did this:
-install 10.12.1 on ssd sata
-boot and login to Sierra from efi ssd sata partition (not usb)
-edit conf.plist (follow this):https://pikeralpha.wordpress.com/2016/06/27/nvmefamily-kext-bin-patch-data/
-paste new config.plist to efi clover folder
-restart and login to sierra
-now can see M2 NVMe partition
-clone from ssd to M2 NVMe
-everything works fine
-enjoy

Regards
Click to expand...

Keep in mind the patch data there is only for 10.12.0. Incomplete for 10.12.1.

See here for complete patch data for 10.12.1: https://github.com/RehabMan/patch-nvme
 
Ok do the patch worked for me to see the drive. Going to proceed with the 10.12.1 pach now before swicth completly.

Question... What did you use to clone? Disk Utility?
 
Got it, going to give it a try. The CCC doesn't seem to see the "Drive" but only the volume. That worries me since it needs the EFI partition to Boot. Have you been to boot from it using this method?

This is truly exciting it's further along than before.
 
Wow I really glad I backed up my system because it did not work well. I lost video with the 530 iGPU and reverted to my ssd boot. Sadfly I get blinky video that I didn't have before. Very odd.
 
Removing th Intel 530 patch and will try again. Non-blinky video vs glitchy is better. At this point I'm probably going to try moving to Linux as the GTX-1080 will be in shortly. Time to start working on the project and I'll try again with hackintoshing later. I've gotten this pretty stable(ish) to be used for iOS development so far but not for my daily use with the 1080.

I also don't like that power management is broken, plus I get a occasional blip from the trackpad that seems to mis a finger touch or two.

Overall, this is helpful on moving me away from MacOS to Linux I think where everything works 100%, including overclocking.

BTW, when I benched the Samsung NVMe drive under MacOS I got 1568MBs Writes and 2000+ (over the UI limit) in Reads. Amazing!
 
RehabMan said:
Keep in mind the patch data there is only for 10.12.0. Incomplete for 10.12.1.

See here for complete patch data for 10.12.1: https://github.com/RehabMan/patch-nvme
Click to expand...

special thanks (RehabMan)
use nvme m2 patch on sierra usb boot 10.12.1 (efi/clover/kexts/other) but crash on boot

I need help (step by step)

Thanks
 
Build 1
GA-Z170X-UD5 |  i7 6700 |  Radeon Nitro+ RX 5700 XT 8GB
seyedhossein said:
special thanks (RehabMan)
use nvme m2 patch on sierra usb boot 10.12.1 (efi/clover/kexts/other) but crash on boot

I need help (step by step)

Thanks
Click to expand...

You will need to describe exactly what you're doing.
Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).
 
RehabMan said:
You will need to describe exactly what you're doing.
Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).
Click to expand...

@RehabMan,

Apologies for jumping in but I think I'm seeing something similar.

I've just added Samsung's NVMe 960 EVO - (the 960 is right, they've just released a new one).

I was able to patch the original unmodified driver using your script from GitHub.

The output:
Code: 
Creating patched HackrNVMeFamily-10_12_1.kext
Vanilla MD5 matches expected MD5 entry (78d587a16e5736b563a175fbf8707372)
Patched MD5 matches expected MD5 entry (291b7e63764598ac8052c8a363964cb8)

When I copy that to my clover kexts folder for 10.12, I end up with the following seemingly unrelated kernel panic, which goes away as soon as the kext is removed.

View media item 187931
I was able to install directly to the NVMe drive by patching the IONVMeFamily.kext using clover. I did have to comment out the first patch which changes the info.plist - from <string>pci144d,a804</string> to <string>pci144d,a802</string>.

I'm also able to boot and use macOS on the NVMe using the same tweaked patch (I'm using it now - it's working great).

I noticed that the patching script has an option for device id matching or class matching? - I've left this set to the default: use_class_match=1

I've also left rename_class=1.....In short I'm using your script stock.

Any ideas?

Thanks,

Phil
 
b11001011 said:
@RehabMan,

Apologies for jumping in but I think I'm seeing something similar.

I've just added Samsung's NVMe 960 EVO - (the 960 is right, they've just released a new one).

I was able to patch the original unmodified driver using your script from GitHub.

The output:
Code: 
Creating patched HackrNVMeFamily-10_12_1.kext
Vanilla MD5 matches expected MD5 entry (78d587a16e5736b563a175fbf8707372)
Patched MD5 matches expected MD5 entry (291b7e63764598ac8052c8a363964cb8)

When I copy that to my clover kexts folder for 10.12, I end up with the following seemingly unrelated kernel panic, which goes away as soon as the kext is removed.

View media item 187931
I was able to install directly to the NVMe drive by patching the IONVMeFamily.kext using clover. I did have to comment out the first patch which changes the info.plist - from <string>pci144d,a804</string> to <string>pci144d,a802</string>.

I'm also able to boot and use macOS on the NVMe using the same tweaked patch (I'm using it now - it's working great).

I noticed that the patching script has an option for device id matching or class matching? - I've left this set to the default: use_class_match=1

I've also left rename_class=1.....In short I'm using your script stock.

Any ideas?

Thanks,

Phil
Click to expand...

As per README, you must use KextsToPatch when trying to patch for the installer.
Using HackrNVMeFamily is a post-install task (so you can delete conflicting IONVMeFamily.kext).

You can use HackrNVMeFamily for the installer, but you must use the "class-code" spoof as linked by the README.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top