Contribute
Register

SSDT Dump Change from El Capitan to Sierra

Status
Not open for further replies.
CoBrA2168

CoBrA2168

Joined
Sep 4, 2011
Messages
526
Motherboard
Lenovo T440s
CPU
i5-4200u
Graphics
HD4400
I decided to redump my DSDT/SSDTs (by using F4 on Clover boot menu) and realized that they have changed somewhat from when I did it over a year ago when I installed El Capitan. I'm also using the latest version of Clover boot loader.

Is there any explanation for this? I thought the DSDT/SSDT files were dependent on the BIOS, not the OS (I haven't changed the BIOS since last year).

I've attached both Clover dumps (the new one is marked Sierra, the old one is El Capitan) to this post.

Code: 
   13    2 0xffffff7f82f2c000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>
josh-lenovo:~ joshuaseltzer$ kextstat|grep -y appleintelcpu
josh-lenovo:~ joshuaseltzer$ kextstat|grep -y applelpc
   97    0 0xffffff7f829e7000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <96 12 5 4 3>

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 Shiki.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.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_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext ALC292.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 617887D228D1EC855A458D7C148023B2
 

Attachments

  • CLOVER_SIERRA.zip
    2.5 MB · Views: 140
  • CLOVER_ELCAP.zip
    2.5 MB · Views: 118
  • Josh-Lenovo.ioreg.zip
    659.7 KB · Views: 117
CoBrA2168 said:
I decided to redump my DSDT/SSDTs (by using F4 on Clover boot menu) and realized that they have changed somewhat from when I did it over a year ago when I installed El Capitan. I'm also using the latest version of Clover boot loader.

Is there any explanation for this? I thought the DSDT/SSDT files were dependent on the BIOS, not the OS (I haven't changed the BIOS since last year).

I've attached both Clover dumps (the new one is marked Sierra, the old one is El Capitan) to this post.

Code: 
   13    2 0xffffff7f82f2c000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (5.0) 65E05472-6AE7-3308-8CC8-FA6CB0DB2AEE <12 11 7 6 5 4 3 1>
josh-lenovo:~ joshuaseltzer$ kextstat|grep -y appleintelcpu
josh-lenovo:~ joshuaseltzer$ kextstat|grep -y applelpc
   97    0 0xffffff7f829e7000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <96 12 5 4 3>

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 Shiki.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.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_Broadcom_WiFi.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakePCIID.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CPUSensors.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext CodecCommander.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmPatchRAM2.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext BrcmFirmwareRepo.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext AppleBacklightInjector.kext
kext-dev-mode allowing invalid signature -67030 0xFFFFFFFFFFFEFA2A for kext ALC292.kext
kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext ACPIBatteryManager.kext
KernelCache ID: 617887D228D1EC855A458D7C148023B2
Click to expand...

ACPI can change:
- any BIOS option change
- any BIOS upgrade
- any hardware change
 
RehabMan said:
ACPI can change:
- any BIOS option change
- any BIOS upgrade
- any hardware change
Click to expand...
So would you recommend just recompiling all of those files by using your guide?

I suppose I need to remember what patches I made in my DSDT as well so they don't conflict...
 
CoBrA2168 said:
So would you recommend just recompiling all of those files by using your guide?
Click to expand...

Re-extract/re-patch always needed after any change as listed.

I suppose I need to remember what patches I made in my DSDT as well so they don't conflict...
Click to expand...

Not sure what you mean, but yes, it is a good idea to make notes regarding which patches you need, as you will need to re-extract/re-patch in the future.
 
RehabMan said:
Re-extract/re-patch always needed after any change as listed.



Not sure what you mean, but yes, it is a good idea to make notes regarding which patches you need, as you will need to re-extract/re-patch in the future.
Click to expand...
I mean, if I manually changed something in my DSDT (like device EC0 to EC), I need to make sure they are reflected in the SSDT files right?
 
CoBrA2168 said:
I mean, if I manually changed something in my DSDT (like device EC0 to EC), I need to make sure they are reflected in the SSDT files right?
Click to expand...

As per ACPI patching guide, renames must be applied equally across all DSDT+SSDTs that reference the renamed symbol.
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top