#82 · closed · 15 comments
  Placa mãe Tipo de processador OctalCore AMD Ryzen 7 5700G, 4641 MHz (46.5 x 100) Nome da Placa Mãe DUEX A520 Chipset da Placa Mãe AMD A520, AMD K19.5 FCH, AMD K19.5 IMC] Tipo de BIOS AMI (05/23/2023)
Can you send the DSDT.aml file here? Chances are it's not an issue with SSDTTime, but instead an issue with your mobo's firmware. I can see if it needs a patch or similar to disassemble and send both the patch and patched DSDT as needed. -CorpNewt
Send the DSDT.aml file directly please - not a screenshot. -CorpNewt
[DSDT.zip](https://github.com/user-attachments/files/20259004/DSDT.zip)
Thanks - I'll give it a look. -CorpNewt
``` Intel ACPI Component Architecture ASL+ Optimizing Compiler/Disassembler version 20200925 Copyright (c) 2000 - 2020 Intel Corporation File appears to be binary: found 8128 non-ASCII characters, disassembling Binary file appears to be a valid ACPI table, disassembling Input file /Users/corpnewt/Downloads/DSDT.aml, Length 0x5F1A (24346) bytes ACPI: DSDT 0x0000000000000000 005F1A (v02 ALASKA A M I 01072009 INTL 20120913) Pass 1 parse of [DSDT] Firmware Error (ACPI): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20200925/dswload-495) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20200925/psobject-372) Could not parse ACPI tables, AE_ALREADY_EXISTS ``` It indeed does appear to be botched - I'll create a patch to rename one of the instances of `\_GPE._L08`. -CorpNewt
thanks
It looks like `_L08` is defined in 2 places - the first sends wake notifications to `GPP3` and `PWRB`. The second sends wake notifications to `GPP3.PTXH` (a USB controller). I'll patch out the second one and see where we end up: First: ``` Scope (_GPE) { Method (_L19, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GP17, 0x02) // Device Wake Notify (\_SB.PCI0.GP17.XHC0, 0x02) // Device Wake Notify (\_SB.PCI0.GP17.XHC1, 0x02) // Device Wake Notify (\_SB.PWRB, 0x02) // Device Wake } Method (_L10, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GPP0, 0x02) // Device Wake } Method (_L08, 0, NotSerialized) { Notify (\_SB.PCI0.GPP3, 0x02) // Device Wake Notify (\_SB.PWRB, 0x02) // Device Wake } } ``` Second: ``` Scope (_GPE) { Method (_L0D, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GPP3.PT02.PT28.LAN, 0x02) // Device Wake } Method (_L02, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GPP3.PT02.PT26, 0x02) // Device Wake Notify (\_SB.PCI0.GPP3.PT02.PT27, 0x02) // Device Wake Notify (\_SB.PCI0.GPP3.PT02.PT29.WLAN, 0x02) // Device Wake } Method (_L14, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GPP3.PT02.PT20, 0x02) // Device Wake Notify (\_SB.PCI0.GPP3.PT02.PT24, 0x02) // Device Wake } Method (_L08, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF { Notify (\_SB.PCI0.GPP3.PTXH, 0x02) // Device Wake } } ``` -CorpNewt
Will you send me the corrected file?
Here is a config.plist -> ACPI -> Patch entry you can add to prevent your botched DSDT from affecting macOS: ```xml <dict> <key>Base</key> <string></string> <key>BaseSkip</key> <integer>0</integer> <key>Comment</key> <string>_L08 to XL08 Rename to Fix Decompilation Errors</string> <key>Count</key> <integer>0</integer> <key>Enabled</key> <true/> <key>Find</key> <data>FBxfTDA4AIZcLwRfU0JfUENJMEdQUDM=</data> <key>Limit</key> <integer>0</integer> <key>Mask</key> <data></data> <key>OemTableId</key> <data>AAAAAAAAAAA=</data> <key>Replace</key> <data>FBxYTDA4AIZcLwRfU0JfUENJMEdQUDM=</data> <key>ReplaceMask</key> <data></data> <key>Skip</key> <integer>0</integer> <key>TableLength</key> <integer>0</integer> <key>TableSignature</key> <data>AAAAAA==</data> </dict> ``` And here's the patched DSDT that you can give SSDTTime to generate other tables: [DSDT-Patched.aml.zip](https://github.com/user-attachments/files/20259159/DSDT-Patched.aml.zip) -CorpNewt
Did the patch and file work as intended?
This does not appear to be an issue iwth SSDTTime - but instead with your EFI. Not relevant to this GitHub repo. -CorpNewt
Thanks bro Em sex., 16 de mai. de 2025 18:44, CorpNewt ***@***.***> escreveu: > *corpnewt* left a comment (corpnewt/SSDTTime#82) > <https://github.com/corpnewt/SSDTTime/issues/82#issuecomment-2887726543> > > This does not appear to be an issue iwth SSDTTime - but instead with your > EFI. Not relevant to this GitHub repo. > > -CorpNewt > > — > Reply to this email directly, view it on GitHub > <https://github.com/corpnewt/SSDTTime/issues/82#issuecomment-2887726543>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BSRNFWV4JAFNYUGPBEMVASD26ZL3ZAVCNFSM6AAAAAB5I4LBX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBXG4ZDMNJUGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Np - best of luck with your troubleshooting. -CorpNewt