Jump to content
Mork vom Ork

Patch for using NVMe under macOS Sierra is ready.

1,377 posts in this topic

Recommended Posts

Racer, this I mean, it takes both spoof that SSDT

I'm just saying my post #770 was very clear the way I originally wrote it.

No further clarification needed.

Share this post


Link to post
Share on other sites
Advertisement

It is because you still have IONVMeFamily.kext present.

As per patch-nvme README, you must delete IONVMeFamily.kext if you're not using the class-code spoof.

 

Suggest you read carefully.

Hello, I tried to delete IONVMeFamilty.kext but I can't because the filesystem is read-only. I tried to remount it as read-write but it won't remount or umount probably because it is the root filesystem. So how can I still delete it ?

Share this post


Link to post
Share on other sites

Hello, I tried to delete IONVMeFamilty.kext but I can't because the filesystem is read-only. I tried to remount it as read-write but it won't remount or umount probably because it is the root filesystem. So how can I still delete it ?

I assume you're tying to boot the installer... clearly you didn't read the README very carefully.

If you are trying to use HackrNVMeFamily for the 10.12 installer, forget about it. Use the correct patches in config.plist KextsToPatch.

You can only use HackrNVMeFamily for the installer if you implement the class-code spoof.

Share this post


Link to post
Share on other sites

Just a small update... I'm now minus 1 patch in KextsToPatch and ~15 patches in KernelToPatch and am still getting a recognized internal NVMe with full read/write access (my NVMe is my primary drive and no problems during boot)! :guitar:

 

~1500 write/~2500 read:

EI1xvQy.png

 

Thanks Rehabman! I greatly appreciate you taking the time to write up a shell script and for helping guide me through the spoof setup.

 

 

 

My only question would be: If I was to update the OS from 10.12 to 10.12.2, would I need to generate a new spoofed HackrNVMeFamily.kext?

Just read your readme on Github. It should survive upgrades!

Share this post


Link to post
Share on other sites

Just a small update... I'm now minus 1 patch in KextsToPatch and ~15 patches in KernelToPatch and am still getting a recognized internal NVMe with full read/write access (my NVMe is my primary drive and no problems during boot)! :guitar:

 

 

 

 

im just using 4 from 15 pike's patches and still getting recognized (samsung PM951)

 

find <0fb68c88 82000000 83f90c0f 85320100>

repl <0fb68c88 82000000 83f9090f 85320100>

 

find <00c783a4 00000000 10000048 8b480848>

repl <00c783a4 00000000 02000048 8b480848>

 

find <89c181e1 ff0f0000 4801d148 81f9ff0f 0000773b>

repl <89c181e1 ff010000 4801d148 81f9ff01 0000773b>

 

find <4981c5ff 0f000049 c1ed0c49 8b042448>

Real <4981c5ff 0f000049 c1ed0949 8b042448>

Share this post


Link to post
Share on other sites

im just using 4 from 15 pike's patches and still getting recognized (samsung PM951)

 

find <0fb68c88 82000000 83f90c0f 85320100>

repl <0fb68c88 82000000 83f9090f 85320100>

 

find <00c783a4 00000000 10000048 8b480848>

repl <00c783a4 00000000 02000048 8b480848>

 

find <89c181e1 ff0f0000 4801d148 81f9ff0f 0000773b>

repl <89c181e1 ff010000 4801d148 81f9ff01 0000773b>

 

find <4981c5ff 0f000049 c1ed0c49 8b042448>

Real <4981c5ff 0f000049 c1ed0949 8b042448>

Dangerous/foolish.

Share this post


Link to post
Share on other sites

Racer listen , do you remember about my problem restart slow?

 

Today I installed El capitain on a ssd AHCI hard, you know that I also have two disks ssd NVME, when I put in the config .plist the kext to patch NVME, I even on the slow restart EL capitain, but when I remove the kext to patch config from .plist, the reboot is fast

Share this post


Link to post
Share on other sites

Racer listen , do you remember about my problem restart slow?

 

Today I installed El capitain on a ssd AHCI hard, you know that I also have two disks ssd NVME, when I put in the config .plist the kext to patch NVME, I even on the slow restart EL capitain, but when I remove the kext to patch config from .plist, the reboot is fast

I don't recommend using KextsToPatch for NVMe.

Share this post


Link to post
Share on other sites

Racer hello ..I also used the kext hack in SLE El Capitan ... and always makes the some problem ... I am doing tests to figure out what is causing this slow reboot ... how come only happens with the kext hack?

Share this post


Link to post
Share on other sites

Racer hello ..I also used the kext hack in SLE El Capitan ... and always makes the some problem ... I am doing tests to figure out what is causing this slow reboot ... how come only happens with the kext hack?

No details... no idea.

Share this post


Link to post
Share on other sites

which details you want?

Specific details on the problem. EFI/Clover, ioreg, kextcache output, etc (eg. the usual).

Share this post


Link to post
Share on other sites

Racer hello ..I also used the kext hack in SLE El Capitan ... and always makes the some problem ... I am doing tests to figure out what is causing this slow reboot ... how come only happens with the kext hack?

I found that Spotlight may have a memory leak and was using up to 500mb+ RAM ( and continued to increase by the second -- you can see it in action in "Activity Monitor" under Process Name "mds_stores"). Try using this command to turn it off:

sudo mdutil -a -i off

and then reboot your computer.

 

 

 

If you want to turn it back on:

sudo mdutil -a -i on

Share this post


Link to post
Share on other sites

I found that Spotlight may have a memory leak and was using up to 500mb+ RAM ( and continued to increase by the second -- you can see it in action in "Activity Monitor" under Process Name "mds_stores"). Try using this command to turn it off:

sudo mdutil -a -i off
and then reboot your computer.

 

;)  no positive resulte

Share this post


Link to post
Share on other sites

Ok 

 

 

Last login: Tue Jan 10 18:46:35 on console

iMacdimagnifico:~ magnifico$ sudo touch /System/Library/Extensions && sudo kextcache -u / 

Password:

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext HackrNVMeFamily-10_12_1.kext

kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleGraphicsDevicePolicy.kext

KernelCache ID: F2B9E2A0E65199D2822A3769FF103BD2

symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>

iMacdimagnifico:~ magnifico$

 

 

iMac di magnifico for Racer .zip

Share this post


Link to post
Share on other sites

Try now:

sudo rm -f /System/Library/Caches/com.apple.kext.caches/Startup/kernelcache && sudo touch /System/Library/Extensions && sudo kextcache -u / 

;)

Share this post


Link to post
Share on other sites

Ok 

 

 

Last login: Tue Jan 10 18:46:35 on console[/size]

iMacdimagnifico:~ magnifico$ sudo touch /System/Library/Extensions && sudo kextcache -u / 

Password:

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext HackrNVMeFamily-10_12_1.kext

kext-dev-mode allowing invalid signature -67013 0xFFFFFFFFFFFEFA3B for kext AppleMobileDevice.kext

kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext AppleGraphicsDevicePolicy.kext

KernelCache ID: F2B9E2A0E65199D2822A3769FF103BD2

symlink("/System/Library/PrelinkedKernels/prelinkedkernel", "/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache") failed 17 (File exists) <createPrelinkedKernel 2795>

iMacdimagnifico:~ magnifico$

 

No EFI/Clover attached.

You should install all kexts you need to the system volume.

You are using the class-code spoof successfully.

It is strange that you have HackrNVMeFamily-10_12_1.kext, but are running 10.12.2 (it works, but should be considered only a short term situation).

This computer seems like a desktop, so not sure why you have PNLF.

Share this post


Link to post
Share on other sites

No EFI/Clover attached.

You should install all kexts you need to the system volume.

You are using the class-code spoof successfully.

It is strange that you have HackrNVMeFamily-10_12_1.kext, but are running 10.12.2 (it works, but should be considered only a short term situation).

This computer seems like a desktop, so not sure why you have PNLF.

you said that the kext 10.12.1 10.12.2 also works with, and I just did update to osx without changing the kext, I know that I use the bogus class code

Share this post


Link to post
Share on other sites

you said that the kext 10.12.1 10.12.2 also works with,

Yes... it does. But obviously it should be a short term situation.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×