X1 Carbon 2017 (5th) can't install High Sierra due to the SSD PM981

[f23258]

Maybe when the official version of pm981 comes out (970evo or 980evo), Samsung should solve these problems.

Is 10.3.3 solved this problem. Tks

 

[dsgvsn]

Is 10.3.3 solved this problem. Tks

patch like this , it's only for 13.2 . In 13.2 ,it works ,but after I update to 13.3 , it doesn't work.
Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha implemented by syscl adapted for 10.13.x by Ricky
Name: IONVMeFamily
find: <f6c1100f 85410100 00>
replace: <f6c1010f 85410100 00>

 

[f23258]

patch like this , it's only for 13.2 . In 13.2 ,it works ,but after I update to 13.3 , it doesn't work.
Comment: IONVMeFamily Preferred Block Size 0x10 -> 0x01 (c) Pike R. Alpha implemented by syscl adapted for 10.13.x by Ricky
Name: IONVMeFamily
find: <f6c1100f 85410100 00>
replace: <f6c1010f 85410100 00>

I try to install 10.13.2 by USB device using this patch but still failed. It reboots at first setup screen. It is really upset.

 

[RehabMan]

I try to install 10.13.2 by USB device using this patch but still failed. It reboots at first setup screen. It is really upset.

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/

 

[f23258]

I PATCH IT IN CONFIG.PLIST，NOW CAN USE IT IN 10.12.6

 

[Ranguvar]

Same issue on ThinkPadX1 Carbon 2018 (6th).
Same drive, Samsung PM981.

Tried with no specific NVMe tweaks, as well as with SSDT_NVMe-Pcc.aml plus HackrNVMeFamilyInjector.kext plus the _DSM to XDSM patch.

Attached CLOVER folder minus themes for both.

Symptoms: Random installer freezes or system reboots, if not during first install step, then during the second after booting from the internal storage.

Checking on Windows shows BIOS device name as \_SB.PCI0.RP05.PXSX
Location paths are PCIROOT(0)#PCI(1C04)#PCI(0000) and ACPI(_SB_)#ACPI(PCI0)#ACPI(RP05)#ACPI(PXSX)

 

[RehabMan]

Same issue on ThinkPadX1 Carbon 2018 (6th).
Same drive, Samsung PM981.

Tried with no specific NVMe tweaks, as well as with SSDT_NVMe-Pcc.aml plus HackrNVMeFamilyInjector.kext plus the _DSM to XDSM patch.

Attached CLOVER folder minus themes for both.

Symptoms: Random installer freezes or system reboots, if not during first install step, then during the second after booting from the internal storage.

Checking on Windows shows BIOS device name as \_SB.PCI0.RP05.PXSX
Location paths are PCIROOT(0)#PCI(1C04)#PCI(0000) and ACPI(_SB_)#ACPI(PCI0)#ACPI(RP05)#ACPI(PXSX)

Using HackrNVMeFamilyInjector.kext + SSDT_NVMe-Pcc.aml cannot be expected to do anything interesting.
It is equivalent to native IONVMeFamily.kext without SSDT_NVMe-Pcc.aml.

 

[Ranguvar]

Using HackrNVMeFamilyInjector.kext + SSDT_NVMe-Pcc.aml cannot be expected to do anything interesting.
It is equivalent to native IONVMeFamily.kext without SSDT_NVMe-Pcc.aml.

Should I just be using SSDT_NVMe-Pcc.aml and the rename?
I cannot generate a spoof kext for 10.13.3.

 

[RehabMan]

Should I just be using SSDT_NVMe-Pcc.aml and the rename?
I cannot generate a spoof kext for 10.13.3.

Spoof kext must be generated from 10.12.6 (or other version supported by patch_nvme.sh).

 

[Ranguvar]

Same issue with spoofed 10.12.6 kext, no visible difference.