Contribute
Register

Thinkpad p50 Sierra 10.12.6

Status
Not open for further replies.

Attachments

  • Files_needed-new.zip
    4.2 MB · Views: 118
Your kextcache output indicates kexts are not installed correctly.
All kexts you need must be installed to the system volume.
Read post #2 of the guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

Ok here:
Code:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext NvidiaGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelMausiEthernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HDMI_Audio.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HD_Graphics.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext PinConfigs.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 5F98021F399A3A308B6D83B5F33B20D1
 
Ok here:
Code:
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Trackpad.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Mouse.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Keyboard.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext VoodooPS2Controller.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext USBInjectAll.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext NvidiaGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext Lilu.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelMausiEthernet.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext IntelGraphicsFixup.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_LPCSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_ACPISensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HDMI_Audio.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID_Intel_HD_Graphics.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext PinConfigs.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleALC.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 5F98021F399A3A308B6D83B5F33B20D1

Any change requires completely new "problem reporting" files.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
 
Ok made a new one.

Problems/comments:
- MacBookPro11,1 or MacBookPro13,1 would be better choice for SMBIOS. Try both.
- SystemMemory addresses are out-of-sync (you need to re-extract/re-patch ACPI):
Code:
NUC6i7KYK:patched rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (MNVS, SystemMemory, 0x4FFAD018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x7FFAD018, 0x1000)
<     OperationRegion (GNVS, SystemMemory, 0x4FF9B000, 0x0600)
>     OperationRegion (GNVS, SystemMemory, 0x7FF9B000, 0x0600)
<                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
>                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)
(that's a big mistake, so I stopped looking)
 
Problems/comments:
- MacBookPro11,1 or MacBookPro13,1 would be better choice for SMBIOS. Try both.
- SystemMemory addresses are out-of-sync (you need to re-extract/re-patch ACPI):
Code:
NUC6i7KYK:patched rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (MNVS, SystemMemory, 0x4FFAD018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x7FFAD018, 0x1000)
<     OperationRegion (GNVS, SystemMemory, 0x4FF9B000, 0x0600)
>     OperationRegion (GNVS, SystemMemory, 0x7FF9B000, 0x0600)
<                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
>                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)
(that's a big mistake, so I stopped looking)

Ok so apparently I forgot "FixRegions" enabled on config.plist (sorry), I removed it and now I get this list:
Code:
<                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
>                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
<                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
<             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
<         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)

I guess I have to make a new extraction again.

(Also, should I drop the OEM's CPU ssdt, since I get ALREADY_EXISTS on CPU _DSM?)
 

Attachments

  • midi_p50.zip
    4.2 MB · Views: 89
Last edited:
Ok so apparently I forgot "FixRegions" on config.plist (sorry), I removed it and now I get this list:
Code:
<                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
>                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
<                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
<             OperationRegion (PCI0, SystemMemory, Local7, One)
>             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
<         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)

I guess I have to make a new extraction again.

Extract, then repatch.
Because you still have bad diffs:
Code:
NUC6i7KYK:origin rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (MNVS, SystemMemory, 0x4FFAD018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x7FFAD018, 0x1000)
<     OperationRegion (GNVS, SystemMemory, 0x4FF9B000, 0x0600)
>     OperationRegion (GNVS, SystemMemory, 0x7FF9B000, 0x0600)
<                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
>                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)

(Also, should I drop the OEM's CPU ssdt, since I get ALREADY_EXISTS on CPU _DSM?)

No need to drop any SSDTs.
Your duplicate is due to incorrect CPU PM setup.
You have both SSDT-PluginType1.aml and config.plist/ACPI/SSDT/Generate/PluginType=true.
Two solutions that solve the same problem (mutually exclusive). Use only one of them.
Read here for details:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

Remove:
config.plist/ACPI/DSDT/Fixes/FixLAN_2000
 
Extract, then repatch.
Because you still have bad diffs:
Code:
NUC6i7KYK:origin rehabman$ diff ../origin/ ../patched/ |grep SystemMemory
<     OperationRegion (MNVS, SystemMemory, 0x4FFAD018, 0x1000)
>     OperationRegion (MNVS, SystemMemory, 0x7FFAD018, 0x1000)
<     OperationRegion (GNVS, SystemMemory, 0x4FF9B000, 0x0600)
>     OperationRegion (GNVS, SystemMemory, 0x7FF9B000, 0x0600)
<                 OperationRegion (XHCP, SystemMemory, Add (0xF8000000, 0x000A0000), 0x0100)
>                 OperationRegion (XHCP, SystemMemory, 0xF80A0000, 0x0100)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<                     OperationRegion (MCA1, SystemMemory, \XWMB, 0x9000)
>                     OperationRegion (MCA1, SystemMemory, XWMB, 0x9000)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<             OperationRegion (PCI0, SystemMemory, Local7, 0x01)
>             OperationRegion (PCI0, SystemMemory, Local7, One)
<         OperationRegion (PWMR, SystemMemory, \PWRM (), 0x0800)
>         OperationRegion (PWMR, SystemMemory, PWRM (), 0x0800)



No need to drop any SSDTs.
Your duplicate is due to incorrect CPU PM setup.
You have both SSDT-PluginType1.aml and config.plist/ACPI/SSDT/Generate/PluginType=true.
Two solutions that solve the same problem (mutually exclusive). Use only one of them.
Read here for details:
https://www.tonymacx86.com/threads/guide-native-power-management-for-laptops.175801/

Remove:
config.plist/ACPI/DSDT/Fixes/FixLAN_2000

Ok I removed FixLAN and PluginType=true but still get the "ALREADY_EXISTS" error and now it's 26 SSDT instead of 25 (I'll try with config's edit and remove the PluginType SSDT).

And I manually fixed those values in the DSDT and saved it.

(BTW, can I use the tool that generates all these files instead of doing it manually? I read that you said "almost".)
 

Attachments

  • remake.zip
    4.2 MB · Views: 118
Ok I removed FixLAN and PluginType=true but still get the "ALREADY_EXISTS" error and now it's 26 SSDT instead of 25 (I'll try with config's edit and remove the PluginType SSDT).

Now you enabled Clover full CPU PM generation (config.plist/ACPI/SSDT/Generate is default true).
Set config.plist/ACPI/SSDT/Generate=false, if you plan to use SSDT-PluginType1.aml.
(or you can set config.plist/ACPI/SSDT/Generate/PluginType=false, as originally suggested).

(BTW, can I use the tool that generates all these files instead of doing it manually? I read that you said "almost".)

The tool does everything but press F4 and F2 in Clover (before you run it).
 
Status
Not open for further replies.
Back
Top