Contribute
Register

[Guide] Patching LAPTOP DSDT/SSDTs

here I done clover like in ur guide and same not booting I try your clover r4061 and its same not booting properly can look now maybe? now I booted only from usb and same with drop oem

No verbose boot photo attached.
What is the difference between this EFI/Clover and the one you booted with when you collected the ioreg provided in post #2223?

Because your Clover bootlog (extracted from ioreg) shows SSDTs loading as expected, and clearly that setup worked just fine...
Code:
18:162  0:000  Start: Processing Patched AML(s): Sorted
18:162  0:000  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
18:163  0:001  Inserting table[1]:SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
18:164  0:001  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
18:165  0:001  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
18:165  0:000  Inserting table[4]:SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[5]:SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[6]:SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[7]:SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success

You should start with unmodified native DSDT + SSDTs in ACPI/patched.
Verify you can boot that way...
Then apply patches one at a time until you determine the cause of the problem.

For you to investigate.

Note: Your FakeSMC.kext is not per guide. Also, config.plist/SMBIOS/Trust should be true. Also, use MacBookPro11,1, since you don't have the correct patches for HWP.
 
No verbose boot photo attached.
What is the difference between this EFI/Clover and the one you booted with when you collected the ioreg provided in post #2223?

Because your Clover bootlog (extracted from ioreg) shows SSDTs loading as expected, and clearly that setup worked just fine...
Code:
18:162  0:000  Start: Processing Patched AML(s): Sorted
18:162  0:000  Inserting table[0]:SSDT.aml from EFI\CLOVER\ACPI\patched ... Success
18:163  0:001  Inserting table[1]:SSDT-0.aml from EFI\CLOVER\ACPI\patched ... Success
18:164  0:001  Inserting table[2]:SSDT-1.aml from EFI\CLOVER\ACPI\patched ... Success
18:165  0:001  Inserting table[3]:SSDT-2.aml from EFI\CLOVER\ACPI\patched ... Success
18:165  0:000  Inserting table[4]:SSDT-3.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[5]:SSDT-4.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[6]:SSDT-12.aml from EFI\CLOVER\ACPI\patched ... Success
18:166  0:000  Inserting table[7]:SSDT-13.aml from EFI\CLOVER\ACPI\patched ... Success

You should start with unmodified native DSDT + SSDTs in ACPI/patched.
Verify you can boot that way...
Then apply patches one at a time until you determine the cause of the problem.

For you to investigate.

Note: Your FakeSMC.kext is not per guide. Also, config.plist/SMBIOS/Trust should be true. Also, use MacBookPro11,1, since you don't have the correct patches for HWP.
I just update to latest clover and changed SMBIOS MAcBookPro13.1 or 13,3 and thats it okay I little bit understand I just need try disassembly use for patched flies first? I changed MacBook Pro11,1 and config.plist/smbios/trust done were i can get HWP patch or guide? and about fakesmc.kext in what guide I can find about it? but same like before nothing happen
 

Attachments

  • RehabMan.zip
    2.3 MB · Views: 82
I just update to latest clover and changed SMBIOS MAcBookPro13.1 or 13,3 and thats it okay I little bit understand I just need try disassembly use for patched flies first? I changed MacBook Pro11,1 and config.plist/smbios/trust done were i can get HWP patch or guide? and about fakesmc.kext in what guide I can find about it? but same like before nothing happen

Off-topic.
Please open a separate thread.
 

Attachments

  • dsdt.dsl
    770.1 KB · Views: 111
I'm using 6.1 and I've one error. Can you help me? I've upload My dsl ...

This file is already patched... and one of the patches you applied caused an error.
You probably applied "Remove _DSM methods" when you should have used "Rename _DSM methods to XDSM"...

If you need help...
Attach native DSDT+SSDT files as ZIP (extracted via Clover F4... ACPI/origin).
 
This file is already patched... and one of the patches you applied caused an error.
You probably applied "Remove _DSM methods" when you should have used "Rename _DSM methods to XDSM"...

If you need help...
Attach native DSDT+SSDT files as ZIP (extracted via Clover F4... ACPI/origin).
I've yet. But I don't understand where is issues. It's my origin and it's the same from windows (e.g.. Aida) and linux (e.g.. ubuntu)
 

Attachments

  • origin.zip
    105.6 KB · Views: 65
I've yet. But I don't understand where is issues. It's my origin and it's the same from windows (e.g.. Aida) and linux (e.g.. ubuntu)

Use this refs.txt:
Code:
External(MDBG, MethodObj, 1)
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)

iasl -da -dl -fe refs.txt DSDT.aml SSDT*.aml

Result: no errors in DSDT.dsl
 
Use this refs.txt:
Code:
External(MDBG, MethodObj, 1)
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)

iasl -da -dl -fe refs.txt DSDT.aml SSDT*.aml

Result: no errors in DSDT.dsl
I've one error the same with parse_arg1
 

Attachments

  • DSDT.dsl
    1.1 MB · Views: 118
Last edited:
Back
Top