DSDT patch
- Thread starter Deleted member 22707
- Start date
Bug fix for AM5 new firmware motherboards (DSDT-FIX)
DISCLAIMER - Pay attention! (Familiarity with ACPI is required) Patching a DSDT is risky. Do only if you know risks and how to recover it if something goes wrong! Hi everyone, with the release of new bios for am5 platforms which allow pre-support for 8000 series CPUs we came across a bug that no ...
But asking for help on the Discord from corpghost as @fabiosun suggested is a much cleaner approach.
As we are seeing more and more conditional device declarations, both on AMD and Intel motherboards, and large conditional blocks may be difficult to identify in MaciASL, I have written a little script to find these declarations.
Feed 'condevscan' with a decompiled dsdt.dsl file to get a list of conditional device declarations with conditions and line numbers.
Feed 'condevscan' with a decompiled dsdt.dsl file to get a list of conditional device declarations with conditions and line numbers.
Hey @ll,
were you able to patch the DSDT for Z880 motherboard?
If yes – great! If not, let me know.
I think we've now developed a very practical tool that can automatically generate DSDTs along with the corresponding OpenCore patches for direct integration into OC.
The last two DSDTs I tested were from a Z880 and an X670 motherboard.
However, I need someone who actually owns such a board for further testing.
Let me know if you're still interested.
spakk from insanelymac.com
were you able to patch the DSDT for Z880 motherboard?
If yes – great! If not, let me know.
I think we've now developed a very practical tool that can automatically generate DSDTs along with the corresponding OpenCore patches for direct integration into OC.
The last two DSDTs I tested were from a Z880 and an X670 motherboard.
However, I need someone who actually owns such a board for further testing.
Let me know if you're still interested.
spakk from insanelymac.com
Please generate a raw DSDT from your system using the latest iasl or MaciASL tool and upload it here as a compressed file.
Once I get home later, I will generate the final files, upload them here, and make them available to you.
Please contribute constructively if something doesn't work, as I don't have access to a comparable system. The more information, the better!
Feel free to upload DSDTs from other boards as well for testing purposes.
Edit:
I'll be home later to generate the DSDTs. In the meantime, feel free to upload your raw DSDTs to insanelymac.com:
Once I get home later, I will generate the final files, upload them here, and make them available to you.
Please contribute constructively if something doesn't work, as I don't have access to a comparable system. The more information, the better!
Feel free to upload DSDTs from other boards as well for testing purposes.
Edit:
I'll be home later to generate the DSDTs. In the meantime, feel free to upload your raw DSDTs to insanelymac.com:
Scanning for conditional device declarations
Recent motherboards now have "Device ()" declarations in their ACPI tables which are conditional on certain variables. For instance: If ((PCHA != Zero)): If ((PCHS != 0x04)): MacOS does not read these variables and may not create devices as required. If the device is used elsewhere in ACPI code b...
www.insanelymac.com
Last edited:
I used SSDT from within windows, hope that worksPlease generate a raw DSDT from your system using the latest iasl or MaciASL tool and upload it here as a compressed file.
Once I get home later, I will generate the final files, upload them here, and make them available to you.
Please contribute constructively if something doesn't work, as I don't have access to a comparable system. The more information, the better!
Feel free to upload DSDTs from other boards as well for testing purposes.
Edit:
I'll be home later to generate the DSDTs. In the meantime, feel free to upload your raw DSDTs to insanelymac.com:
Scanning for conditional device declarations
Recent motherboards now have "Device ()" declarations in their ACPI tables which are conditional on certain variables. For instance: If ((PCHA != Zero)): If ((PCHS != 0x04)): MacOS does not read these variables and may not create devices as required. If the device is used elsewhere in ACPI code b...www.insanelymac.com
I used the DSDT you uploaded on InsanelyMac.
That aside, it’d be great if you could drop a comment on InsanelyMac as well.
Any kind of feedback helps improve the tool and get it closer to a proper release!
@leesurone
A small mistake was pointed out to me by Anto65: the files in the SSDT-Force-Individual folder are currently in .dsl format and need to be converted to .aml. I need to update my tool accordingly.
And yes, that is correct: all required files must be compiled into .aml. The files in the SSDT-Force-Individual folder are currently in DSL format and need to be compiled into AML files using a tool like iasl or MaciASL. The compiled .aml files then have to be placed in the OpenCore folder EFI/OC/ACPI/ and added to the config.plist under ACPI -> Add so OpenCore loads them at boot.
A small mistake was pointed out to me by Anto65: the files in the SSDT-Force-Individual folder are currently in .dsl format and need to be converted to .aml. I need to update my tool accordingly.
And yes, that is correct: all required files must be compiled into .aml. The files in the SSDT-Force-Individual folder are currently in DSL format and need to be compiled into AML files using a tool like iasl or MaciASL. The compiled .aml files then have to be placed in the OpenCore folder EFI/OC/ACPI/ and added to the config.plist under ACPI -> Add so OpenCore loads them at boot.
No other SSDTs should be needed? I used MaciASL and after compiling it saves the file without an extension (no .aml) and I didn't feel like adding that to the almost 50 files. There is a nice pause now before the boot loser screen displays and then another one after selecting the drive to boot. Unfortunately it didn't complete loading macOS, I'm going to mess around with it a little more tomorrow and will take a picture of where it stops and upload it.
We’ve found a few errors that definitely need to be fixed. Unfortunately, there are duplicate declarations being added in the SSDT-Force.dsl file (see below for how to fix this).
The tool was actually supposed to convert the .dsl file into a SSDT-Force.aml file and generate it automatically, so that it could be used directly by OpenCore (OC).
Unfortunately, I missed that part when writing the code.
I’ll make a few corrections to fix this.
I’m going to convert the entire content of the “SSDT-Force-Individual” folder into .aml files so they can be read directly by OC.
For now, don’t put too much work into it , I need to correct it first anyway.
I’ll get back to you once it’s ready.
Hey@ll
here is the tool – it took a bit of time. I had to fix some errors in the tool, and I hope now everyone can use this simple Python tool.
I included everything you need in the zipped file DSDT-Analysis-Tool.zip, including a help file and some images in the "Picture" folder.
It’s not a professional tool, but it should automatically generate everything you need.
If you find any bugs in the code, feel free to fix and improve it — and share it freely with everyone.
With that said, enjoy!
Here is the tool for Windows, macOS, and Linux
Have fun using it!
here is the tool – it took a bit of time. I had to fix some errors in the tool, and I hope now everyone can use this simple Python tool.
I included everything you need in the zipped file DSDT-Analysis-Tool.zip, including a help file and some images in the "Picture" folder.
It’s not a professional tool, but it should automatically generate everything you need.
If you find any bugs in the code, feel free to fix and improve it — and share it freely with everyone.
With that said, enjoy!
Here is the tool for Windows, macOS, and Linux
Have fun using it!
Last edited:
I’ve revised both versions and added the missing elements, such as the language setting and the functions from the Etorix code. It should work now.
Please check whether the final result meets your expectations.
I wasn’t able to test the Mac version because I don’t have a Mac with me at the moment.
But it should work, the difference from the Windows version is only minor.
Please check whether the final result meets your expectations.
I wasn’t able to test the Mac version because I don’t have a Mac with me at the moment.
But it should work, the difference from the Windows version is only minor.
Scanning for conditional device declarations
www.insanelymac.com
In my Mac the tool does not work, when I press the button decompile - nothingHey@ll
here is the tool – it took a bit of time. I had to fix some errors in the tool, and I hope now everyone can use this simple Python tool.
I included everything you need in the zipped file DSDT-Analysis-Tool.zip, including a help file and some images in the "Picture" folder.
It’s not a professional tool, but it should automatically generate everything you need.
If you find any bugs in the code, feel free to fix and improve it — and share it freely with everyone.
With that said, enjoy!
Here is the tool for Windows, macOS, and Linux
Have fun using it!