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

[RehabMan]

The Pc still not recognize the disk for disk utility formatting in the installer.. Can u help me ?
PCIROOT(0)#PCI(1D00)#PCI(0000)
ACPI(_SB_)#ACPI(PCI0)#ACPI(RP09)#ACPI(PXSX)
----
\_SB.PCI0.RP09.PXSX

Your SSDT is wrong.
No need for this code:

    Device (_SB.PCI0.RP09.PXSX)
    {
        Name (_ADR, Zero)  // _ADR: Address
    }

Also, next time, please read post #1, "Problem Reporting".

 

[axel9546]

Your SSDT is wrong.
No need for this code:

    Device (_SB.PCI0.RP09.PXSX)
    {
        Name (_ADR, Zero)  // _ADR: Address
    }

Also, next time, please read post #1, "Problem Reporting".

Okay sorry but i cant login into my pc
Anyway i changed this and i tryed to create Hackrnvmefamily kext for 10.12.3 (the osx v i would like to install) and i placed it into kext on the efi folder, but i still cannot recognize my ssd to install the osx into
This is the Efi folder so u can give it a check! Thanks

 

[RehabMan]

Okay sorry but i cant login into my pc
Anyway i changed this and i tryed to create Hackrnvmefamily kext for 10.12.3 (the osx v i would like to install) and i placed it into kext on the efi folder, but i still cannot recognize my ssd to install the osx into
This is the Efi folder so u can give it a check! Thanks

Your SSDT-NVMe-Pcc.aml is still wrong, in the same way I wrote in post #501.
Also, your HackrNVMeFamily-10_12_3.kext is not correct (it is actually 10.12.4 vanilla kext).

 

[axel9546]

Your SSDT-NVMe-Pcc.aml is still wrong, in the same way I wrote in post #501.
Also, your HackrNVMeFamily-10_12_3.kext is not correct (it is actually 10.12.4 vanilla kext).

I need to fix that so.
How i can fix that? I read the guide carefully but i cant login into my pc so im with a friend pc .. And im so bad at this sorry
Anyway what i still missing on ?

 

[RehabMan]

I need to fix that so.
How i can fix that? I read the guide carefully but i cant login into my pc so im with a friend pc .. And im so bad at this sorry
Anyway what i still missing on ?

Post #1 has everything you need.
And I already pointed out your mistake with the SSDT code.

 

[RehabMan]

why exactly the above numbers (5f44534d / 5844534d)? what do they mean?

u430:~ Admin$ echo -n 5f44534d|xxd -r -p|xxd
0000000: 5f44 534d                                _DSM
u430:~ Admin$ echo -n 5844534d|xxd -r -p|xxd
0000000: 5844 534d                                XDSM

Further details in the ACPI hotpatch guide:
http://www.tonymacx86.com/threads/guide-using-clover-to-hotpatch-acpi.200137/

 

[bluegreytheory]

I am a little stuck on this one and was hoping somebody (RehabMan!?) might have an idea of what the problem may be.

I have 3 NVMe SSDs: a Samsung 950 and 2x Intel 750s. I've got the Samsung and one of the Intels working, no problem! However, I can't get Sierra to recognize one of the Intels for reasons unknown.

I used these addresses (from Win10) in SSDT-NVMe-Pcc.aml:
\_SB.PCI0.BR1B.H000 (Intel 750 #1)
\_SB.PCI0.BR2C.H000 (Intel 750 #2) (* This one not recognized)
\_SB.PCI0.BR3A.H000 (Samsung 950) (Currently the Win10 boot & not even really needed to be visible on the mac side)

Very grateful for any suggestions. Attaching SSDT-NVMe-Pcc.aml just in case.

 

[RehabMan]

I am a little stuck on this one and was hoping somebody (RehabMan!?) might have an idea of what the problem may be.

I have 3 NVMe SSDs: a Samsung 950 and 2x Intel 750s. I've got the Samsung and one of the Intels working, no problem! However, I can't get Sierra to recognize one of the Intels for reasons unknown.

I used these addresses (from Win10) in SSDT-NVMe-Pcc.aml:
\_SB.PCI0.BR1B.H000 (Intel 750 #1)
\_SB.PCI0.BR2C.H000 (Intel 750 #2) (* This one not recognized)
\_SB.PCI0.BR3A.H000 (Samsung 950) (Currently the Win10 boot & not even really needed to be visible on the mac side)

Very grateful for any suggestions. Attaching SSDT-NVMe-Pcc.aml just in case.

Read FAQ, "Problem Reporting"
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[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!