Yes, you are right on this. I was using a depreciated config.plist from a person who owns a T470 (without P).
I did and was able to get to the installer. Now it doesn't detect the harddrive. Assuming some issue with NVMe. Will also have a look on this.
Not sure what I did wrong, but I decided to go with HackrNVMeFamily and get now kernel panics relating to IOSCSIArchitectureModelFamily. I need to investigate what went wrong while using the kext. I followed the instructions and copied the HackrNVMeFamilyInjector.kext and the generated HackrNVMeFamily-10_12_6.kext to Clover kext folder.
True. After using the --spoof option, it can boot the installer again without kernel panics. But still no luck with having the SSD detected. May I ask you for having a look at the Clover folder attached to this post? I'm pretty sure I did something wrong in the config.plist.
Thank you. It can get pretty difficult, to pay attention, at all this stuff, without completly understanding, how it works and what it does. But I love to learn, I appreciate your time you take to help.
I removed all those stuff mentioned.
Is there a way to pass the APCI path over rather than having it automatically determined? I saw this option only for usage as SSDT, but not for patch_nvme.sh. I ask, because I'm using another System for the script, and you guess it, I didn't pay attention for the mismatching ACPI paths... Instead of _SB.PCI0.RP11.PXSX I need _SB.PCI0.RP09.PXSX so I wonder, if that can be changed somethere, as you where able to determine this.
I was suggesting you would get me wrong, as it took me longer, to understand what the patch does and I should have think more before I posted. I already got the right the ACPI path but I don't understand how I can use it. I've generated an SSDT using your example, saved it at the particular place, but I've got still no SSD. I'm pretty sure I did something wrong, but I need a hint
