Jump to content

Patch for using NVMe under macOS Sierra is ready.


1,382 posts in this topic

Recommended Posts

I just made an installation X99 + Samsung 950pro + 6900K

One kext in 10.12

And one in S / L / E

Works impeccably

Thanks again Micky

Its supose to be installed in EFI/CLOVER/kexts/10.12 OR in S/L/E. Not in both. But as i write before, because Micky ask for testing it, when its only in EFI/CLOVER/kexts/10.12 it won't work. So i have installed it in S/L/E now.

Are you using kext creating by NVMeP 2.6?

Link to comment
Share on other sites

Its supose to be installed in EFI/CLOVER/kexts/10.12 OR in S/L/E. Not in both. But as i write before, because Micky ask for testing it, when its only in EFI/CLOVER/kexts/10.12 it won't work. So i have installed it in S/L/E now.

Are you using kext creating by NVMeP 2.6?

on 10.12.1

I used NVMep 2.6

I installed in 10.12 and in S / L / E

I have not injected anything into the config.plist

It works very well

NVMeP.zip

Link to comment
Share on other sites

friend, you told me days ago, you had the 16b2555, now what are you testing me is confusing ideas

it's very clear

I installed the 6900K and 10.12.1For a friend at home on his hardware it is a new installation

Nothing to do with the other facility

Link to comment
Share on other sites

Racer , what you mean ? Which patch are wrong ?? you can highlight them?  :angel_not:

For example, post #420: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-21?do=findComment&comment=2307585

 

configSample.plist has:

Find: <89b3f802 0000c1e0 0c050010 00008983>

Replace: <89b3f002 0000c1e0 09050010 00008983>

 

Should be...

Find: <89b3f802 0000c1e0 0c050010 00008983>

Replace: <89b3f802 0000c1e0 09050010 00008983>

 

I didn't read every post after that to see if it was ever corrected. But the same wrong patch also appears in other posts...

  • Like 2
Link to comment
Share on other sites

which version of clover?strange, you have used the Borg in 10.12 and also in SLE ???

clover 3922

YES!!!! in 10.12 and S/L/E

For example, post #420: http://www.insanelymac.com/forum/topic/312803-patch-for-using-nvme-under-macos-sierra-is-ready/page-21?do=findComment&comment=2307585

 

configSample.plist has:

Find: <89b3f802 0000c1e0 0c050010 00008983>

Replace: <89b3f002 0000c1e0 09050010 00008983>

 

Should be...

Find: <89b3f802 0000c1e0 0c050010 00008983>

Replace: <89b3f802 0000c1e0 09050010 00008983>

 

I didn't read every post after that to see if it was ever corrected. But the same wrong patch also appears in other posts...

Yes this post is no longer valid

Link to comment
Share on other sites

clover 3922

YES!!!! in 10.12 and S/L/E

 

Yes this post is no longer valid

Other posts also have the same wrong code.

Problem with this thread is that post #1 is not being updated...

From my understanding, I have the correct patches in my repo...

  • Like 1
Link to comment
Share on other sites

Other posts also have the same wrong code.

Problem with this thread is that post #1 is not being updated...

From my understanding, I have the correct patches in my repo...

I agree with you

The 2 points that must be followed is your repo and that of Micky

There its the right patches

Moreover, thank you both for your work

Link to comment
Share on other sites

RehabMan, is there way how to use HackrNVMeFamily kext and leave vanilla IONVMeFamily.kext in S/L/E? Thanks.

It works that way on 10.11.x. Not on 10.12.0.

 

Maybe eventually there will be a solution (idea: a kext that makes sure IONVMeFamily stays loaded + a patch that disables it).

 

It is possible also that a future IONVMeFamily.kext may fix the "memory corruption on failure" issue...

  • Like 1
Link to comment
Share on other sites

It works that way on 10.11.x. Not on 10.12.0.

 

Maybe eventually there will be a solution (idea: a kext that makes sure IONVMeFamily stays loaded + a patch that disables it).

 

It is possible also that a future IONVMeFamily.kext may fix the "memory corruption on failure" issue...

Im using kext generated by Mickys NVMeP together with vanilla IONVMeFamily and it works. Do you know how he is doing it?

Link to comment
Share on other sites

Im using kext generated by Mickys NVMeP together with vanilla IONVMeFamily and it works. Do you know how he is doing it?

I've not seen the result of the NVMeP patching.

There is some evidence that the bug in IONVMeFamily that causes the problem is fixed in 10.12.1 (or maybe 10.12.2 betas). But I cannot verify as I'm not running NMVe drives on 10.12 at the moment. Life is much simpler with SM951/AHCI...

Link to comment
Share on other sites

Please note that my github patch-nvme updated for 10.12.1.

 

https://github.com/RehabMan/patch-nvme.git

 

Also: Please note also that some of the patches presented in this thread for 10.12.1 are wrong...

generating kext for 10.12.1 is not working

$ ./patch_nvme.sh 10_12_1

Creating patched HackrNVMeFamily-10_12_1.kext

WARNING: Vanilla MD5 (46932bdf9fa5aa48803369fa87c5050a) does not match expected MD5 (78d587a16e5736b563a175fbf8707372)

WARNING: Patched MD5 (314f150f01867103769ddcd60203d966) does not match expected MD5 (291b7e63764598ac8052c8a363964cb8)

can this be fixed?

Link to comment
Share on other sites

generating kext for 10.12.1 is not working

$ ./patch_nvme.sh 10_12_1

Creating patched HackrNVMeFamily-10_12_1.kext

WARNING: Vanilla MD5 (46932bdf9fa5aa48803369fa87c5050a) does not match expected MD5 (78d587a16e5736b563a175fbf8707372)

WARNING: Patched MD5 (314f150f01867103769ddcd60203d966) does not match expected MD5 (291b7e63764598ac8052c8a363964cb8)

can this be fixed?

Current 10.12.1 is 16B2657 and the plist has the md5 for this build only.

 

You must be running latest 10.12.1 to use the 10.12.1 patches.

If you're running the older 10.12.1 (16B2555), you can upload your IONVMeFamily.kext and I'll check that the patches are compatible.

Link to comment
Share on other sites

Does a new patch needs to be generated on each build or can the 10.12.1 patch be used for any upcoming releases at least temporary until the new patch is applied? Is it better to stay on 10.11.6 for a while to avoid these patches?

 

Would the process be... create new patch > put on folder > reboot and test > update osx?

Link to comment
Share on other sites

 Share

×
×
  • Create New...