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

[Ranguvar]

Right. I've tried contacting Samsung to no avail (also tried an email to samsungsemi.com).
I will try Lenovo as well, but highly doubtful.
The X1 Carbon Gen 6 page from Lenovo has no firmware updates, only a Rapid Storage driver.

Attached is all the information I have on this drive.

https://www.anandtech.com/show/12082/the-samsung-pm981-ssd-review-512gb-1tb-phoenix-3d-nand

 

[RehabMan]

If I use the 13.x's NVMe kext will instant restart. I'm also waiting Samsung to update firmware. But PM981 is an OEM product. And seems can't get support from Samsung.

Right. I've tried contacting Samsung to no avail (also tried an email to samsungsemi.com).
I will try Lenovo as well, but highly doubtful.
The X1 Carbon Gen 6 page from Lenovo has no firmware updates, only a Rapid Storage driver.

Attached is all the information I have on this drive.

https://www.anandtech.com/show/12082/the-samsung-pm981-ssd-review-512gb-1tb-phoenix-3d-nand

Probably best to just replace the SSD with hardware that is compatible (SATA M.2 is best).

 

[Ranguvar]

Probably best to just replace the SSD with hardware that is compatible (SATA M.2 is best).

This is the best SSD on the market right now as far as I can tell, so personally I'm going to sit with Windows and Linux and wait until there is better support (perhaps when the consumer 970 or 980 drives based off this reach market)

 

[RehabMan]

This is the best SSD on the market right now as far as I can tell, so personally I'm going to sit with Windows and Linux and wait until there is better support (perhaps when the consumer 970 or 980 drives based off this reach market)

The big problems with non-Apple NVMe and macOS:
- no power management (so they tend to run hot and reduce battery life)
- problems with TRIM+APFS that cause boot delays (and the boot delays cause other problems, TRIM on NVMe cannot be disabled)
- NVMe compatibility is still not great with IONVMeFamily.kext (it is obviously only tested with NVMe devices Apple is using)

I think such problems are likely to stick around for quite some time.

 

[Ranguvar]

The big problems with non-Apple NVMe and macOS:
- no power management (so they tend to run hot and reduce battery life)
- problems with TRIM+APFS that cause boot delays (and the boot delays cause other problems, TRIM on NVMe cannot be disabled)
- NVMe compatibility is still not great with IONVMeFamily.kext (it is obviously only tested with NVMe devices Apple is using)

I think such problems are likely to stick around for quite some time.

Wow. I had no idea it was _that_ bad.
Thanks for the heads up.

 

[f23258]

The big problems with non-Apple NVMe and macOS:
- no power management (so they tend to run hot and reduce battery life)
- problems with TRIM+APFS that cause boot delays (and the boot delays cause other problems, TRIM on NVMe cannot be disabled)
- NVMe compatibility is still not great with IONVMeFamily.kext (it is obviously only tested with NVMe devices Apple is using)

I think such problems are likely to stick around for quite some time.

I try to install 10.13.3 by 10.12.6 HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml, it is sucessful at the first screen but failed at the second stage. And the report is as attachment. Tks

 

[RehabMan]

I try to install 10.13.3 by 10.12.6 HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml, it is sucessful at the first screen but failed at the second stage. And the report is as attachment. Tks

Using the class-code spoof and HackrNVMeFamilyInjector.kext is the *same* as using native IONVMeFamily.kext.
As per README, HackrNVMeFamilyInjector.kext is for dual-boot when using class-code spoof for 10.12.x/10.11.x along with 10.13.x.

 

[f23258]

Using patched kext from 12.6 and ssdt can drive pm981 in 13.x，but it isn't stable. I only can use it for a data disk, if install the macOS13.x in pm981 would fail. I install 13.3 in a SATA SSD.

I have used macOS 10.13.3 Supplemental Update successfully in PM981 by HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml,
and it can be usually used. It is rarely crashed now.
I install it as follow,
1. Install 10.13.3 to USB device by HFS+ format
2. Make a VD copy from the USB device by Paragon Hard Disk manager (Don't support APFS now)
3. Restore it to the PM981 HFS+ partition
4. EFI with HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml

 

[f23258]

Using the class-code spoof and HackrNVMeFamilyInjector.kext is the *same* as using native IONVMeFamily.kext.
As per README, HackrNVMeFamilyInjector.kext is for dual-boot when using class-code spoof for 10.12.x/10.11.x along with 10.13.x.

But there is a problem that it would crash in 10.13.x at pm981. But only can use the hackrnvmefamilyinjector.kext in the clover to run 10.13.x successfully. only run can't fresh install.

 

[RehabMan]

I have used macOS 10.13.3 Supplemental Update successfully in PM981 by HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml,
and it can be usually used. It is rarely crashed now.
I install it as follow,
1. Install 10.13.3 to USB device by HFS+ format
2. Make a VD copy from the USB device by Paragon Hard Disk manager (Don't support APFS now)
3. Restore it to the PM981 HFS+ partition
4. EFI with HackrNVMeFamilyInjector.kext nad ssdt-nvme.aml

Using HackrNVMeFamilyInjector.kext (class-code spoof injector kext) is the same as using native IONVMeFamily.kext (no class-code spoof).