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

[gabriox]

https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

I don't know how to use MaciASL. Is there a guide somewhere?

 

[RehabMan]

I don't know how to use MaciASL. Is there a guide somewhere?

It is simple/obvious (hardly requires more skill than using a word processor such as Microsoft Word).

Copy code to clipboard.
File->New.
Paste.
Edit ACPI path in code to match your own path.
File->Save As, format: ACPI Machine Language Binary, name: SSDT-NVMe-Pcc.aml, path: somewhere you can find (eg. desktop).
Then copy the resulting SSDT-NMVe-Pcc.aml to EFI/ClOVER/ACPI/patched.

 

[donrchoi]

Hello, Rehabman,

I currently have a MacBook Pro 15" 2015, and am trying to install 960 EVO NVMe 1tb. I found out that I cannot boot Sierra from the NVMe drives, so I want to know what other possibilities I can think of at the moment.

I already have an adapter to overcome the physical incompatibility (http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1139.html) - all MBP cannot do is, from my knowledge, EFI recognition.

One thing that this laptop is incapable is that this one only has one PCIe slot unlike to the Mac Pro, so booting has to be done through NVMe drive. Is my understanding correct? If this (NVMe in MBP) setup is even remotely possible, I want to know where to start and how to install. Can I use a third party bootloader to boot in real mac systems? I want to know if either Clover or REFIt would work in real mac systems.

How do I prepare the nvme drive for the installation, how do I format it, how would this drive be recognized, or .. etc.

Thanks!

 

[gabriox]

It is simple/obvious (hardly requires more skill than using a word processor such as Microsoft Word).

Copy code to clipboard.
File->New.
Paste.
Edit ACPI path in code to match your own path.
File->Save As, format: ACPI Machine Language Binary, name: SSDT-NVMe-Pcc.aml, path: somewhere you can find (eg. desktop).
Then copy the resulting SSDT-NMVe-Pcc.aml to EFI/ClOVER/ACPI/patched.

My problem is the language. I spend more time in google translate than on tonymacx forum I had understand the use, but I did not understand that i have to do "file-new" (and I had an error). Now it's ok.

I don't understand if follow the part about "Special injections required for 10.11.x and Samsung 960 EVO" 'cause i have not samsung but i have 10.12... (is only for both?)

 

[RehabMan]

Hello, Rehabman,

I currently have a MacBook Pro 15" 2015, and am trying to install 960 EVO NVMe 1tb. I found out that I cannot boot Sierra from the NVMe drives, so I want to know what other possibilities I can think of at the moment.

I already have an adapter to overcome the physical incompatibility (http://eshop.sintech.cn/ngff-m2-pcie-ssd-card-as-2013-2014-2015-macbook-ssd-p-1139.html) - all MBP cannot do is, from my knowledge, EFI recognition.

One thing that this laptop is incapable is that this one only has one PCIe slot unlike to the Mac Pro, so booting has to be done through NVMe drive. Is my understanding correct? If this (NVMe in MBP) setup is even remotely possible, I want to know where to start and how to install. Can I use a third party bootloader to boot in real mac systems? I want to know if either Clover or REFIt would work in real mac systems.

How do I prepare the nvme drive for the installation, how do I format it, how would this drive be recognized, or .. etc.

Thanks!

You can use Clover to boot your Mac... it is just a matter of disabling all the hack related Clover features since most of them would not be needed on a real Mac.

Suggest you start by booting Clover from USB and experiment from there.

 

[RehabMan]

I don't understand if follow the part about "Special injections required for 10.11.x and Samsung 960 EVO" 'cause i have not samsung but i have 10.12... (is only for both?)

The extra property injects are only necessary with Samsung 960 EVO *and* 10.11.x.
They are not needed with the 10.12.x/960 EVO combo.
It is the definition of the word "AND". That said, doing the extra injections will not cause any problems if done for 10.12.x.

 

[gabriox]

The extra property injects are only necessary with Samsung 960 EVO *and* 10.11.x.
They are not needed with the 10.12.x/960 EVO combo.
It is the definition of the word "AND". That said, doing the extra injections will not cause any problems if done for 10.12.x.

In this phrase, in italian translation, term "and" is ambiguous and it could also mean that "special injection required for 10... and required for Samsung..."
But anyway, thank you
Now I had create the SSDT with MaciASL and the Kext with zip archive.
Based on what I understand by reading the guide, I should not do anything else. I should just copy the files Aml and install the kext, but I do not understand where. I have to do a clean install and locate the M.2. I must to enter Kext and Aml in folders on the EFI partition of the USB created with UniBeast?
I ask you Sorry if I Disorder but try to understand my difficulties with the language plz.
TU

 

[RehabMan]

In this phrase, in italian translation, term "and" is ambiguous and it could also mean that "special injection required for 10... and required for Samsung..."
But anyway, thank you
Now I had create the SSDT with MaciASL and the Kext with zip archive.
Based on what I understand by reading the guide, I should not do anything else. I should just copy the files Aml and install the kext, but I do not understand where. I have to do a clean install and locate the M.2. I must to enter Kext and Aml in folders on the EFI partition of the USB created with UniBeast?
I ask you Sorry if I Disorder but try to understand my difficulties with the language plz.
TU

Two requirements:
- class-code injection
- HackrNVMeFamily*.kext generated with --spoof loading/installed

class-code injection:
- done via correct SSDT-NVMe-Pcc.aml in ACPI/patched (it is where Clover loads AML files)
- must also insure no existing _DSM at that path (use _DSM->XDSM patch in config.plist/ACPI/DSDT/Patches)

HackrNVMeFamily*.kext generated with --spoof loading/installed
- generate on Mac running same version you're trying to generate
- copy to EFI/Clover/kexts/Other (for Clover injection)
- install to system volume (for case of FakeSMC.kext installed, booting from kernel cache). /Library/Extensions or /System/Library/Extensions... your choice.

Complete details: https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

 

[gabriox]

- class-code injection √ done (10.12.2)
- HackrNVMeFamily*.kext generated with --spoof loading/installed √ done
class-code injection: √ ok
- done via correct SSDT-NVMe-Pcc.aml in ACPI/patched (it is where Clover loads AML files) The others, they have gone √ ok
- must also insure no existing _DSM at that path (use _DSM->XDSM patch in config.plist/ACPI/DSDT/Patches) √ ok
HackrNVMeFamily*.kext generated with --spoof loading/installed √ done
- generate on Mac running same version you're trying to generate The others, they have gone √ done (in another ssd obviously)
- copy to EFI/Clover/kexts/Other (for Clover injection) √ ok
- install to system volume (for case of FakeSMC.kext installed, booting from kernel cache ? ). /Library/Extensions or /System/Library/Extensions... your choice. √ ok

Therefore, after this operations, I just normally have to install the system with my usb bootable and i will find M.2 HD in disk utility?

 

[RehabMan]

- class-code injection √ done (10.12.2)
- HackrNVMeFamily*.kext generated with --spoof loading/installed √ done
class-code injection: √ ok
- done via correct SSDT-NVMe-Pcc.aml in ACPI/patched (it is where Clover loads AML files) The others, they have gone √ ok
- must also insure no existing _DSM at that path (use _DSM->XDSM patch in config.plist/ACPI/DSDT/Patches) √ ok
HackrNVMeFamily*.kext generated with --spoof loading/installed √ done
- generate on Mac running same version you're trying to generate The others, they have gone √ done (in another ssd obviously)
- copy to EFI/Clover/kexts/Other (for Clover injection) √ ok
- install to system volume (for case of FakeSMC.kext installed, booting from kernel cache ? ). /Library/Extensions or /System/Library/Extensions... your choice. √ ok

Therefore, after this operations, I just normally have to install the system with my usb bootable and i will find M.2 HD in disk utility?

Yes, but...

If you haven't yet installed to the NVMe SSD, then it impossible for you to have a "check" on "install to system volume". That step is a post-install task.