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

[RehabMan]

Note: Added NVMe_patches_10_12_5.plist for 10.12.5 support.
The patches are the same as for 10.12.4... just the md5 sums changed.

(added for latest security update in 10.11.6 too)

 

[bluegreytheory]

Gotcha. Problem reporting files are attached this time... Hopefully these will give some insight in this. Thanks for taking a look!

 

[RehabMan]

Gotcha. Problem reporting files are attached this time... Hopefully these will give some insight in this. Thanks for taking a look!

Your ioreg shows no other NVMe device other than the two that are recognized.
There is no device at BR2C.
Same in Clover bootlog... only these two seen:

0:100  0:000  === [ GetDevices ] ========================================
...
0:100  0:000  PCI (00|02:00.00) : 144D A802 class=010802
...
0:100  0:000  PCI (00|04:00.00) : 8086 0953 class=010802

That means it is a hardware/BIOS issue...

 

[bluegreytheory]

Interesting, I'll see if there's anything that jumps out at me in the BIOS. Weird that Windows can mount it yet Mac can't even locate it. Thanks for the feedback.

 

[RehabMan]

Interesting, I'll see if there's anything that jumps out at me in the BIOS. Weird that Windows can mount it yet Mac can't even locate it. Thanks for the feedback.

What is the output of 'lspci -nn' in Linux Terminal?

 

[bluegreytheory]

What is the output of 'lspci -nn' in Linux Terminal?

A whole bunch of Unknown Devices...

 

[RehabMan]

A whole bunch of Unknown Devices...

Notice that there are only two NVMe SSDs listed:

02:00.0 Mass storage controller [0108]: Samsung Electronics Co Ltd Unknown device [144d:a802] (rev 01)
04:00.0 Mass storage controller [0108]: Intel Corporation Unknown device [8086:0953] (rev 01)

 

[bluegreytheory]

I'm probably reading this wrong but in the boot log, there are 3 mentions of NVMe from the Scan Volumes section but one without a UUID?:

[06]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)
Result of bootcode detection: bootable unknown (legacy)
[07]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(1,GPT,CAB60138-6DE0-427C-BE26-D18D6F582807,0x22,0x40000)
[08]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,9C1C0E47-0250-4B96-9394-5C2631D4A0ED,0x40800,0x587AB000)

 

[RehabMan]

I'm probably reading this wrong but in the boot log, there are 3 mentions of NVMe from the Scan Volumes section but one without a UUID?:

[06]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)
Result of bootcode detection: bootable unknown (legacy)
[07]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(1,GPT,CAB60138-6DE0-427C-BE26-D18D6F582807,0x22,0x40000)
[08]: Volume: PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\NVMe(0x1,00-00-00-00-00-00-00-00)\HD(2,GPT,9C1C0E47-0250-4B96-9394-5C2631D4A0ED,0x40800,0x587AB000)

Three checks (one MBR check, 2 partition checks) on one NVMe device.

 

[Lensjocky]

I just updated to 10.12.5 and installed new Nvidia Drivers. No Problem.

Then proceeded to create new "HackrNVMeFamily-10_12_5.kext" to the best of my ability and used "Kext Wizard" to install into S/L/E after deleting "HackrNVMeFamily-10_12_4.kext". I then repaired permissions and rebuilt the cache.

My machine will not boot anymore. (Luckily I have a bootable 10.12.4 backup...)
I tried to revert to "HackrNVMeFamily-10_12_4.kext" but that will not allow it to boot either.
I suspect the trouble to be with my kext creation using "patch_nvme.sh".
Here is my suspicious looking terminal window when I try and create updated kext.


All was well on 10.12.4 using Samsung SSD 960 EVO 500GB using class-code spoof.

Any thoughts on how I can get my machine out of the weeds?