Mac OSX Sierra 10.12.X on ThinkPad T470s

[RehabMan]

Is it version depended? I need to search for one, as I dont have it on my current system. So I'm going to use the next version of IOReg I find. Whats wrong with IOJones? I have it from here https://www.tonymacx86.com/threads/alternative-to-ioregistryexplorer-iojones.95400/

Obtaining IORegistryExplorer v2.1 is covered in the FAQ, "Problem Reporting".
IOJones just doesn't have the features that I use from IORegistryExplorer.

Why do I see this using Reply but not in your original post?

No idea what you're referring to.

I'm afraid to do so,

Nothing ventured, nothing gained.
Your config.plist is no prize (full of unnecessary/wrong settings).

 

[Valko8877]

No idea what you're referring to.

Man your mind seems to work like a BIOS. Same input, same output. Please have a look at the IOReg attached. Are there reasons, the NVMe controller is listed under IOPP?

Nothing ventured, nothing gained.

I'll keep it in mind. R.I.P soon old config.plist.

 

[RehabMan]

Please have a look at the IOReg attached. Are there reasons, the NVMe controller is listed under IOPP?

Your NVMe is at _SB.PCI0.RP09.PXSX. Look at IOACPIPlane. The IOPP intermediary is expected and is essentially the driver for the PCI bridge at RP09.

Is this ioreg extracted when running the installer?

I think your config.plist is messing with you. But there is way too much garbage in there to sift through.

Also, you should update Clover to the latest. It has additional helpful logs...

Note: Strange ig-platform-id you're using. Typically, when we want to pick an invalid ig-platform-id, we just use 0x12345678.

 

[Valko8877]

Is this ioreg extracted when running the installer?

Yes.

I think your config.plist is messing with you. But there is way too much garbage in there to sift through.

Man I don't know. It's not like I try to avoid messing with it, but I have a feeling it's something else. I extracted a DSDT with Clover and saw that there is no device named "_SB_.PCI0.RP09.PXSX". I've attached the DSDT.aml to this post.

EDIT: There is. And it seems to contain nothing:

            Device (PXSX)
            {
                Name (_ADR, 0x00)  // _ADR: Address
            }

Furthermore I recognized that the NVM drive is connected to a SATA connector, when you open the laptop and look at the mainboard. I don't know what Lenovo is doing there. These are the only lines relating to PCI0.RP09 in the original DSDT:

    External (_SB_.PCI0.RP09.PWRG, UnknownObj)    // (from opcode)
    External (_SB_.PCI0.RP09.RSTG, UnknownObj)    // (from opcode)
    External (_SB_.PCI0.RP09.SCLK, UnknownObj)    // (from opcode)

So I tried to search for NVM and found this:

    External (_SB_.PCI0.SAT0.NVM1.VLPM, UnknownObj)    // (from opcode)
    External (_SB_.PCI0.SAT0.NVM2.VLPM, UnknownObj)    // (from opcode)
    External (_SB_.PCI0.SAT0.NVM3.VLPM, UnknownObj)    // (from opcode)

Without knowing what is meant by PWRG, RSTG, SCLK and SAT0 as also VLPM is hard to determine for me, what in particular these lines are meaning. Probably what is named NVM1, 2, 3 etc isn't even about NVMe. Could it be, that the drive is really connected to a SATA controller and just passed to windows as NVM? I'll try to get another DSDT from within the macOS installer.

Also, you should update Clover to the latest. It has additional helpful logs...

What makes you feel like I dont use the latest version? I downloaded Clover_v2.4k_r4318 on 8th December, isnt it the latest version?

 

[RehabMan]

Man I don't know. It's not like I try to avoid messing with it, but I have a feeling it's something else.

No further help until you switch to a cleaner config.plist.

I extracted a DSDT with Clover and saw that there is no device named "_SB_.PCI0.RP09.PXSX". I've attached the DSDT.aml to this post.

Plain as day:

    Scope (\_SB.PCI0)
    {
...
        Device (RP09)
        {
...
            Device (PXSX)
            {

 

[Valko8877]

No further help until you switch to a cleaner config.plist

Please see the files attached. I hope I dont need to make my config.plist even more minimalistic. Probably it is with 7KB the tiniest one, I've ever used.

 

[RehabMan]

Please see the files attached. I hope I dont need to make my config.plist even more minimalistic. Probably it is with 7KB the tiniest one, I've ever used.

Your options in config.plist/ACPI/SSDT/Generate are not correct for your hardware.
Your DropTables configuration is also wrong.
DropOem=true also wrong.
See correct options in my guide plists.

You don't need it yet, but AutoMerge should be true (much easier to patch ACPI with the AutoMerge feature).

 

[Valko8877]

Your options in config.plist/ACPI/SSDT/Generate are not correct for your hardware.
Your DropTables configuration is also wrong.
DropOem=true also wrong.
See correct options in my guide plists.

If I relate to your "correct" options from your guide and set them up in my own config I get directly a kernel panic relating to USB. This happens also, if I change the DropTables setting or the setting for DropOem. I would really appreciate it, if you would explain why something is wrong instead of just saying "Thats wrong and this is wrong, because it's not like that in my guides". That would give me a much better understanding of how this things work and to what pay special attention to.

 

[RehabMan]

If I relate to your "correct" options from your guide and set them up in my own config I get directly a kernel panic relating to USB.

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/

 

[Valko8877]

No "Problem Reporting" files attached.

I can provide you for a second time a copy of the Clover folder, but I didn't see the point for it, as I changed nothing except the option "Drop OEM SSDT" from "Yes" to "No" which directly brings me a USB kernel panic as on picture from post #1