Contribute
Register

Does macOS High Sierra support NVME SSD natively?

Status
Not open for further replies.
Joined
Jun 3, 2017
Messages
5
Motherboard
GIGABYTE Z270N GAMING 5
CPU
INTEL CORE 7700K
Graphics
HD 630 + AMD SAPPHIRE R9 380
Mobile Phone
  1. Android
  2. iOS
just look the title~
 
I'm actually having trouble with my Plextor M8PeG 256GB NVME drive in High Sierra. Unless I apply all the same patches as for Sierra, the drive is not seen in High Sierra. @RehabMan indicated that I still need the bit swap clover patch, but I tried removing the other stuff and it is still not seen.

So some drives seem natively supported while others seem not.

Detail of what fixes NVME for me in Sierra/High Sierra:
- EFI/CLOVER/ACP/patched/SSDT-NVMe-Pcc.aml: an ssdt built using the ACPI path discovered under Windows and compiled
- EFI/CLOVER/kexts/Other/HackrNVMeFamily-10_12_6.kext: the NVMe Hackr kext built with --spoof
- EFI/CLOVER/config.plist:
--- Rename _DSM to XDSM (e.g. find 5f44534d replace 5844534d )
--- Bit swap block size 0x10 (e.g. find f6c1100f 851c0100 00 replace f6c1010f 851c0100 00 in IONVMeFamily)
 
--- Bit swap block size 0x10 (e.g. find f6c1100f 851c0100 00 replace f6c1010f 851c0100 00 in IONVMeFamily)

It should work native, with that one patch.
You will need to be certain you have the correct patch for 10.13 (the code, and therefore also the patch, has likely changed).
 
It should work native, with that one patch.
You will need to be certain you have the correct patch for 10.13 (the code, and therefore also the patch, has likely changed).
Oh! Ok. That makes sense. I got the possible replace values from a post on a thread by Pike R Alpha I think? I'll have to hunt around and get the new values when they're posted. Thanks!
 
Oh! Ok. That makes sense. I got the possible replace values from a post on a thread by Pike R Alpha I think? I'll have to hunt around and get the new values when they're posted. Thanks!

Looking at the patch for 10.12 and the disassembly of 10.12 vs. 10.13, the patch for 10.13 is:

Find: f6 c1 10 0f 85 41 01 00 00
Replace: f6 c1 01 0f 85 41 01 00 00

Diff result:
Code:
SPEEDY-NUC-2:1013 rehabman$ diff IONVMeFamily.s IONVMeFamily_p.s
1c1
< IONVMeFamily:
---
> IONVMeFamily_p:
4352c4352
< 000000000000526e    f6 c1 10     testb    $0x10, %cl
---
> 000000000000526e    f6 c1 01     testb    $0x1, %cl
 
Looking at the patch for 10.12 and the disassembly of 10.12 vs. 10.13, the patch for 10.13 is:

Find: f6 c1 10 0f 85 41 01 00 00
Replace: f6 c1 01 0f 85 41 01 00 00

Diff result:
Code:
SPEEDY-NUC-2:1013 rehabman$ diff IONVMeFamily.s IONVMeFamily_p.s
1c1
< IONVMeFamily:
---
> IONVMeFamily_p:
4352c4352
< 000000000000526e    f6 c1 10     testb    $0x10, %cl
---
> 000000000000526e    f6 c1 01     testb    $0x1, %cl
Thank you!
 
It should work native, with that one patch.

Is this patch required for all NVMe drives in 10.13? I have a Samsung 960 EVO PCIe NVMe M.2 (MZ-V6E1T0BW) drive. Do I need this patch?
 
Is this patch required for all NVMe drives in 10.13? I have a Samsung 960 EVO PCIe NVMe M.2 (MZ-V6E1T0BW) drive. Do I need this patch?

Hardware dependent.
 
I'm actually having trouble with my Plextor M8PeG 256GB NVME drive in High Sierra. Unless I apply all the same patches as for Sierra, the drive is not seen in High Sierra. @RehabMan indicated that I still need the bit swap clover patch, but I tried removing the other stuff and it is still not seen.

So some drives seem natively supported while others seem not.

Detail of what fixes NVME for me in Sierra/High Sierra:
- EFI/CLOVER/ACP/patched/SSDT-NVMe-Pcc.aml: an ssdt built using the ACPI path discovered under Windows and compiled
- EFI/CLOVER/kexts/Other/HackrNVMeFamily-10_12_6.kext: the NVMe Hackr kext built with --spoof
- EFI/CLOVER/config.plist:
--- Rename _DSM to XDSM (e.g. find 5f44534d replace 5844534d )
--- Bit swap block size 0x10 (e.g. find f6c1100f 851c0100 00 replace f6c1010f 851c0100 00 in IONVMeFamily)

@aol have you solved for the Plextor M8PeG issue? I have a 512M being installed on 10.13.2, I still cannot see the drive.
 
Status
Not open for further replies.
Back
Top