Contribute
Register

Samsung 960 Evo NVMe drive question

Status
Not open for further replies.
Joined
Sep 7, 2014
Messages
48
Motherboard
Asus ROG 390-F
CPU
Coffee Lake i7
Graphics
RTX 2070 Super
In installed Sierra 10.12.2 on my Alienware 13 R3 as per http://beyondspec.org/ on an external HDD to see if I could get it to work. After a lot of tinkering about I got everything to work, including sound, network etc.

I then ordered a Samsung 960 Evo and installed the drive to my laptop. Made a backup of my Sierra installation for later use.
I assumed the USB installer was ready to detect my new NVMe drive (it does show up in Windows) but unfortunately it is not listed, ergo I can't install Sierra to it.

1) Am I right to asssume that I should put HackrNVMeFamily-10_12_2.kext on my USB drive into EFI/Clover/Kexts/Other, add the contents of NVMe_patches_10_12_2.plist to config.plist under EFI/Clover under "KernelToKextPatch" and then boot into the installer? Would I have to use the terminal to list the NVMe?

2) After I boot Sierra through my USB disk, would I then simply put HackrNVMeFamily-10_12_2.kext to S/L/E and L/E?

I know there are a lot of instructions out there, but they are all very confusing to me and I don't bring a lot of experience to the table.

Cheers!

EDIT: OK, so according to https://github.com/RehabMan/patch-nvme I simply add "NVMe_patches_10_12_2.plist" contents to config.plist on my USB stick, right?
 
Last edited:
In installed Sierra 10.12.2 on my Alienware 13 R3 as per http://beyondspec.org/ on an external HDD to see if I could get it to work. After a lot of tinkering about I got everything to work, including sound, network etc.

I then ordered a Samsung 960 Evo and installed the drive to my laptop. Made a backup of my Sierra installation for later use.
I assumed the USB installer was ready to detect my new NVMe drive (it does show up in Windows) but unfortunately it is not listed, ergo I can't install Sierra to it.

1) Am I right to asssume that I should put HackrNVMeFamily-10_12_2.kext on my USB drive into EFI/Clover/Kexts/Other, add the contents of NVMe_patches_10_12_2.plist to config.plist under EFI/Clover under "KernelToKextPatch" and then boot into the installer? Would I have to use the terminal to list the NVMe?

2) After I boot Sierra through my USB disk, would I then simply put HackrNVMeFamily-10_12_2.kext to S/L/E and L/E?

I know there are a lot of instructions out there, but they are all very confusing to me and I don't bring a lot of experience to the table.

Cheers!

EDIT: OK, so according to https://github.com/RehabMan/patch-nvme I simply add "NVMe_patches_10_12_2.plist" contents to config.plist on my USB stick, right?

Best to use class-code spoof. The guide is linked from the patch-nvme README.
 
OK i have been trying for a few days now. I just - can't - get this to work. I must be too damn thick to understand the concept. I've spent the last week or so reading up and trying to grasp the concept and I must say I am pretty bummed at this stage...

Bottomline: everything works on my laptop but NVMe, feels like I am so close yet can't solve this final piece of the puzzle. I am gonna attach my lspci, anything weird about it? I just don't know where to look anymore... drive works like a charm in Windows, so it's not HW.
 

Attachments

  • lspci.txt
    1.9 KB · Views: 126
OK i have been trying for a few days now. I just - can't - get this to work. I must be too damn thick to understand the concept. I've spent the last week or so reading up and trying to grasp the concept and I must say I am pretty bummed at this stage...

Read spoof guide (this link is provided in the patch-nvme README):
https://www.tonymacx86.com/threads/...h-ionvmefamily-using-class-code-spoof.210316/

If you have a problem, read post #1, "Problem Reporting".
 
I've read it, multiple times even. The problem is that I can't even see the ACPI namespace path in Windows, so I can't even provide the first step of those instructions... I am not even kidding.
 
I've read it, multiple times even. The problem is that I can't even see the ACPI namespace path in Windows, so I can't even provide the first step of those instructions... I am not even kidding.

What do you see in Windows?
Did you forget to set SATA mode to AHCI? (note that it requires tweaks to Windows if you're in RAID mode, using IRST).
Attach 'lspci -nn' from Linux Terminal.
 
I think I was just too late with editing one of my previous posts, but here it is again. I also just posted my clover.zip in the thread you provided. Should I also attach the lspci.txt file in there?
 
Status
Not open for further replies.
Back
Top