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

[tatosamp]

Perhaps you should provide more information about what you're actually doing...

I'm trying to get this intel SSD to be my only drive in my Hack Build.

 

[RehabMan]

I'm trying to get this intel SSD to be my only drive in my Hack Build.

You will need to provide more info.

such as:
- On what computer did you create the HackrIONVMe kext?
- What version of OS X was it running?
- What script command line did you use?
- What is the output of the script?
- Are you booting the installer or doing something else?
- What is the content of your EFI/Clover?
- What kexts are installed to the system volume?
- What is the output of 'sudo kextcache -i /'?
- Is the kext loading? (check 'kextcache | grep NVMe')
- etc.

 

[tatosamp]

You will need to provide more info.

such as:
- On what computer did you create the HackrIONVMe kext?
- What version of OS X was it running?
- What script command line did you use?
- What is the output of the script?
- Are you booting the installer or doing something else?
- What is the content of your EFI/Clover?
- What kexts are installed to the system volume?
- What is the output of 'sudo kextcache -i /'?
- Is the kext loading? (check 'kextcache | grep NVMe')
- etc.

- On what computer did you create the HackrIONVMe kext?
Using a Hackintosh installed to a Local SATA SSD OSX Yosemite 10.11.6 using UniBeast and MultiiBeast (Thanks TonyMac) tried creating patch NVMe on the same OS version on my MacBook Pro still cant see the Intel Drive

- What version of OS X was it running?
OS X 10.11.6

- What script command line did you use?
./patch_nvme.sh 10_11_6

- What is the output of the script?
Creating patched HackrNVMeFamily-10_11_6.kext
Vanilla MD5 matches expected MD5 entry (c236c91f4f20c1f2fb9f828f3ffc0a6c)
Patched MD5 matches expected MD5 entry (040b01cd4bfb18b8df793b96998810b7)

- Are you booting the installer or doing something else?
Not doing anything else, Booting from a Built on the same computer to a SATA SSD, I thought will be easier to debug the Intel drive by using it as second drive for the mean time while debugging the Driver, at least till the patched driver can recognize the drive before trying to boot from it as the only drive.

hat is the content of your EFI/Clover?
Attached on EFI_Clover.zip

- What kexts are installed to the system volume?
List Attached on SLE_LE_Content.txt

- What is the output of 'sudo kextcache -i /'?
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext

- Is the kext loading? (check 'kextcache | grep NVMe')
Seems that it wasn't loaded

 

[RehabMan]

- On what computer did you create the HackrIONVMe kext?
Using a Hackintosh installed to a Local SATA SSD OSX Yosemite 10.11.6 using UniBeast and MultiBeast (Thanks TonyMac) tried creating patch NVMe on the same OS version on my MacBook Pro still cant see the Intel Drive

- What version of OS X was it running?
OS X 10.11.6

- What script command line did you use?
./patch_nvme.sh 10_11_6

- What is the output of the script?
Creating patched HackrNVMeFamily-10_11_6.kext
Vanilla MD5 matches expected MD5 entry (c236c91f4f20c1f2fb9f828f3ffc0a6c)
Patched MD5 matches expected MD5 entry (040b01cd4bfb18b8df793b96998810b7)

- Are you booting the installer or doing something else?
Not doing anything else, Booting from a Built on the same computer to a SATA SSD, I thought will be easier to debug the Intel drive by using it as second drive for the mean time while debugging the Driver, at least till the patched driver can recognize the drive before trying to boot from it as the only drive.

hat is the content of your EFI/Clover?
Attached on EFI_Clover.zip

- What kexts are installed to the system volume?
List Attached on SLE_LE_Content.txt

- What is the output of 'sudo kextcache -i /'?
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext

- Is the kext loading? (check 'kextcache | grep NVMe')
Seems that it wasn't loaded

Install HackrNVMeFamily to the system volume.

Note that the 'kextcache |grep NVMe' must be done early after booting otherwise the kernel may have unloaded it already.

Also attach ioreg.

 

[tatosamp]

Install HackrNVMeFamily to the system volume.

Note that the 'kextcache |grep NVMe' must be done early after booting otherwise the kernel may have unloaded it already.

Also attach ioreg.

Trying to run 'kextcache |grep NVMe' from terminal is that the right syntax cause all i got is lots of option to run the kextcache, sorry Noob on this.

after installing the kext on system i got feed back from 'sudo kextcache -i /'
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext RealtekRTL8111.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext realtekALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_XHCIMux.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext HackrNVMeFamily-10_11_6.kext
kext-dev-mode allowing invalid signature -67054 0xFFFFFFFFFFFEFA12 for kext AppleHDA.kext

attached are the ioreg

 

[RehabMan]

Trying to run 'kextcache |grep NVMe' from terminal is that the right syntax cause all i got is lots of option to run the kextcache, sorry Noob on this.

kextstat|grep NVMe

 

[tatosamp]

kextstat|grep NVMe

46 0 0xffffff7f818fb000 0x23000 0x23000 com.apple.hack.HackrNVMeFamily (1.2.0) 9468CCDF-AD0E-301C-8225-CDB081651AB8 <34 20 17 16 12 7 6 5 4 3 1>

 

[RehabMan]

46 0 0xffffff7f818fb000 0x23000 0x23000 com.apple.hack.HackrNVMeFamily (1.2.0) 9468CCDF-AD0E-301C-8225-CDB081651AB8 <34 20 17 16 12 7 6 5 4 3 1>

It means it is matching and loading, but then failing probe or start. Which can only mean that Pike's patches do not work with your device. You can verify the theory and your setup by trying with a device that is known to work with the patches (Samsung 950 Pro NVMe).

 

[oRISHi]

Hi all, I'm about to purchase a new build, and I'm thinking about this M.2 drive to boot the system: https://www.amazon.com/dp/B00TGIVZTW/?tag=tonymacx86com-20. Will I need the NVMeFamily patch, or will it work the same as a SATA drive, OOB?
Thanks!

 

[TpwUK]

Hi all, I'm about to purchase a new build, and I'm thinking about this M.2 drive to boot the system: https://www.amazon.com/dp/B00TGIVZTW/?tag=tonymacx86com-20. Will I need the NVMeFamily patch, or will it work the same as a SATA drive, OOB?
Thanks!

Refer to the first post of this thread, it will show you your answer - Check the speeds and it tells you the variety pretty much and if you need the NVMe mods to suit.

Martin