Contribute
Register

[Guide] Patching LAPTOP DSDT/SSDTs

(sorry if this may sound like a stupid question, I just want to make sure I don't mess anything up.)
okay say at this point of having disassembled the files and now having .dsl files should I open them in MaciASL now?
so now I can just right click- open with MaciASL?
(specifically the dsdt one because I am using one of your laptop config.plist files for my laptop and you said we might not need to change those unless doing something specific )

You can open .dsl files in MaciASL by double clicking, just like any other document that has an app associated.
 
Hi can smbd to build ssdt for my laptop and will be good if combine it with dsdt. I spent about one day to combine all my 12ssdt files together following this guide and other but in vain. Thx. P.S. Thanks Rehab for Wi-fi and bt BCRM patch and methods following it I could repatch original apple kext to work out from box without using those ones. My laptop Dell Xps 13 9343 (100% all working except original speedstep (nullcpu instead)).
 
Hi can smbd to build ssdt for my laptop and will be good if combine it with dsdt. I spent about one day to combine all my 12ssdt files together following this guide and other but in vain.

Silly endeavor.
No need to combine SSDTs into one file.
 
Maybe y
Silly endeavor.
No need to combine SSDTs into one file.
I want to get only CPU section for proper cpu power management
 
Your ACPI files are still wrong.
For some reason, SSDT-7.aml in ACPI/patched is a completely different file than SSDT-7.aml in ACPI/origin.
I didn't check anything else.
See ACPI patching guide.
i quote in topic USB power property injection for Sierra
I do the following.
1. Extracting F4 clover
2. Disassembly with refs.txt
3. picture 1, error ssdt 7
4. i remove ssdt 7, disassembly ok
That is why I lost ssdt-7
i upload folder origin, If I do something wrong, please help me fix it. thanks you so much!!!
 

Attachments

  • have ssdt 7.png
    have ssdt 7.png
    73.6 KB · Views: 120
  • delete ssdt7.png
    delete ssdt7.png
    77.5 KB · Views: 133
  • origin.zip
    434.5 KB · Views: 80
i still don't understand.
first, i extract my DSDT or whatever it's using clover F4, and it's done. And now i copy extract file from "CLover/acpi/origin" into my desktop. And then i dissemble these file using this command "iasl -da -dl DSDT.aml SSDT*.aml". I have MaciASL on Application, should i open "DSDT.dsl" from dissemble progress and open it with MaciASL, patch my intel hd 3000 and compile it ?
 
i quote in topic USB power property injection for Sierra
I do the following.
1. Extracting F4 clover
2. Disassembly with refs.txt
3. picture 1, error ssdt 7
4. i remove ssdt 7, disassembly ok
That is why I lost ssdt-7
i upload folder origin, If I do something wrong, please help me fix it. thanks you so much!!!

You should not drop, eliminate, SSDT-7.aml (it is CPU related).
Based on ACPI/origin, you should have the following SSDTs in ACPI/patched (appropriately patched):
SSDT-0.aml
SSDT-1.aml
SSDT-2.aml
SSDT-3.aml
SSDT-4.aml
SSDT-5.aml
SSDT-6.aml
SSDT-7.aml

Correct disassembly is: iasl -da -dl -fe refs.txt DSDT.aml SSDT*.aml

Must omit/delete SSDT-8x.aml as it is the duplicate, not SSDT-7.
 
First create refs.txt in the directory where your DSDT/SSDT files are:
Code (Text):

External(MDBG, MethodObj, 1)
External(_GPE.MMTB, MethodObj, 0)
External(_SB.PCI0.LPCB.H_EC.ECWT, MethodObj, 2)
External(_SB.PCI0.LPCB.H_EC.ECRD, MethodObj, 1)
External(_SB.PCI0.LPCB.H_EC.ECMD, MethodObj, 1)
External(_SB.PCI0.PEG0.PEGP.SGPO, MethodObj, 2)
External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1)
External(_SB.PCI0.SAT0.SDSM, MethodObj, 4)
External(_GPE.VHOV, MethodObj, 3)
External(_SB.PCI0.XHC.RHUB.TPLD, MethodObj, 2)

External("MethodObj, 1 MethodObj 3, MethodObj ,4" or drive ....)Is there a rule requirement to add these to refs. TXT? Do these Numbers have any specific meaning
 
First create refs.txt in the directory where your DSDT/SSDT files are:
Code (Text):

External(MDBG, MethodObj, 1)
External(_GPE.MMTB, MethodObj, 0)
External(_SB.PCI0.LPCB.H_EC.ECWT, MethodObj, 2)
External(_SB.PCI0.LPCB.H_EC.ECRD, MethodObj, 1)
External(_SB.PCI0.LPCB.H_EC.ECMD, MethodObj, 1)
External(_SB.PCI0.PEG0.PEGP.SGPO, MethodObj, 2)
External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1)
External(_SB.PCI0.SAT0.SDSM, MethodObj, 4)
External(_GPE.VHOV, MethodObj, 3)
External(_SB.PCI0.XHC.RHUB.TPLD, MethodObj, 2)

External("MethodObj, 1 MethodObj 3, MethodObj ,4" or drive ....)Is there a rule requirement to add these to refs. TXT? Do these Numbers have any specific meaning

The numbers indicate the number of arguments for the method that the iasl disassembler should expect.

You should read the ACPI spec for further info.
 
Back
Top