[Guide] HackrNVMeFamily co-existence with IONVMeFamily using class-code spoof

[Lsucorey]

I think for private transfer of files it is fine. But of course, I prefer the thread itself. If you boot with a generic SMBIOS (eg. no serial# specified), there isn't that much in ioreg to be concerned about.

Thanks! That makes perfect sense; i'll be sure to do that next time. I'll also go ahead and reimplement my ideal 2017 iMac setup w/ Canadian Squid 960 Pro x 4 RAID 0 Array (feels better booting off of Canadian hardware than eating Canadian bacon.. just saying) w/ 850 EVO serving Clover BootLoader duty!

 

[RehabMan]

Thanks! That makes perfect sense; i'll be sure to do that next time. I'll also go ahead and reimplement my ideal 2017 iMac setup w/ Canadian Squid 960 Pro x 4 RAID 0 Array (feels better booting off of Canadian hardware than eating Canadian bacon.. just saying) w/ 850 EVO serving Clover BootLoader duty!

So??? Problem solved?

 

[RolandSCH]

I can't seem to get my Samsung 960 EVO to show up.
Motherboard is a Gigabyte Z170X and SSD is plugged into its M.2 port.

I followed your guide precisely, both on El Capitan (using the alternative .aml) and on Sierra.

Thanks for your amazing work!

 

[RehabMan]

I can't seem to get my Samsung 960 EVO to show up.
Motherboard is a Gigabyte Z170X and SSD is plugged into its M.2 port.

I followed your guide precisely, both on El Capitan (using the alternative .aml) and on Sierra.

Thanks for your amazing work!

You have an existing _DSM method at _SB.PCI0.RP17.PXSX in your DSDT. You forgot the _DSM->XDSM patch.
Read post #1.

 

[Lsucorey]

So??? Problem solved?

No, no additional progress was attempted since sleep was calling.. Then work. Now am back, so I'll proceed to reinstall Sierra implementing the setup mentioned in my prior post, and will reedit this post in an hour or two with ioreg if I see you have been active. Thanks again for your time & help, RehabMan.

 

[RehabMan]

No, no additional progress was attempted since sleep was calling.. Then work. Now am back, so I'll proceed to reinstall Sierra implementing the setup mentioned in my prior post, and will reedit this post in an hour or two with ioreg if I see you have been active. Thanks again for your time & help, RehabMan.

OK...

 

[Lsucorey]

OK...

This is the 960x1 OS X setup via the Carrier Board; once I get this setup working, then I will revert back to the 960x4 OS X setup.

Question: Your HackrNVMeFamily spoof is supposed to make it unnecessary to inject Pike's IONVMeFamily patches manually into config.plist, correct? Or do I have that wrong? I ask because I got it to boot w/out the UniBeast USB by injecting Pike's patches.

 

[RehabMan]

This is the 960x1 OS X setup via the Carrier Board; once I get this setup working, then I will revert back to the 960x4 OS X setup. I also noticed I am unable to restart; I must completely power off or else I get no display (although I know that is off topic so you can ignore - just letting you know).

Attach EFI/Clover in use.

 

[Lsucorey]

Attach EFI/Clover in use.

I got it working. Just booted from 850 EVO into Squid OS X RAID 10 Array (the mirror adds stability to the setup, and my write speed is still plenty fast for me). I'm somewhat disappointed my 16x PCIe socket seems to max out just a hair over 4 GB/sec though .. or it could be the max bandwidth of the Squid M.2 Carrier Board.

BACK ON TOPIC: I still do not understand why I needed the IONVMeFamily patches if I had your HackrNVMeFamily spoof installed properly; that was the whole point of your spoof, right? To avoid having to patch IONVMeFamily and streamline future updates? Do you think it is probable or possible that it is due to my SSDT-NVMe-Pcc.aml file being coded improperly?

 

[RehabMan]

I got it working. Just booted from 850 EVO into Squid OS X RAID 10 Array (the mirror adds stability to the setup, and my write speed is still plenty fast for me). I'm somewhat disappointed my 16x PCIe socket seems to max out just a hair over 4 GB/sec though .. or it could be the max bandwidth of the Squid M.2 Carrier Board.

BACK ON TOPIC: I still do not understand why I needed the IONVMeFamily patches if I had your HackrNVMeFamily spoof installed properly; that was the whole point of your spoof, right? To avoid having to patch IONVMeFamily and streamline future updates? Do you think it is probable or possible that it is due to my SSDT-NVMe-Pcc.aml file being coded improperly?

No need for IONVMeFamily patches if you have spoof implemented correctly.
Your previous ioreg shows class-code/ACPI identity not working. Hence request for EFI/Clover.