Scanning for conditional device declarations

[spakk]

1 hour ago, Cyberdevs said:

@spakk

Just a quick question does this work with all mainboard models or is it designed to Z890 series? 

The DSDT-Analysis-Tool is not only for the Z890 series. It can work with any mainboard if you can get the DSDT from your system. The tool looks at ACPI tables in general, so it should work with many different motherboards, no matter the chipset or model. This includes the Z890 series, but is not limited to it.

However, the DSDT quality and layout can be different depending on the manufacturer and BIOS version. This may change how well the tool works or the results you get. It is a good idea to try it with your own board’s DSDT and tell us if you find any problems.

[leesureone]

13 hours ago, spakk said:

 

 

I appreciate your efforts and generating those files for me to test. These Z890 MSI boards are tricky as @MaLd0n mentioned earlier in the thread. Previously the only way I could get macOS to finish loading is by using a DSDT.aml file created by another user (possibly @MaLd0n). The basic SSDTs that work with other Asus and Gigabyte 890 boards fail and macOS freezes before it finishes loading. 

 

I get a very similar result trying to load just SDDT-Force.aml, it freezes and verbose mode shows a series of ACPI errors. I'e attached the boot log file and a picture of where it freezes. I also attached the DDST file if anyone is curious, analyzing it and seeing what is significant and why it works is well beyond my reach. 😵‍💫

 

I have a feeling this method may work well with with Z890 boards that aren't made by MSI, I may try thatDSDT.amlDSDT.amlDSDT.am later and will post again if I do

opencore-2025-06-01-123916.txt DSDT.aml.zip

Edited June 1, 2025 by leesureone

[spakk]

42 minutes ago, leesureone said:

 

I appreciate your efforts and generating those files for me to test. These Z890 MSI boards are tricky as @MaLd0n mentioned earlier in the thread. Previously the only way I could get macOS to finish loading is by using a DSDT.aml file created by another user (possibly @MaLd0n). The basic SSDTs that work with other Asus and Gigabyte 890 boards fail and macOS freezes before it finishes loading. 

 

I get a very similar result trying to load just SDDT-Force.aml, it freezes and verbose mode shows a series of ACPI errors. I'e attached the boot log file and a picture of where it freezes. I also attached the DDST file if anyone is curious, analyzing it and seeing what is significant and why it works is well beyond my reach. 😵‍💫

 

I have a feeling this method may work well with with Z890 boards that aren't made by MSI, I may try thatDSDT.amlDSDT.amlDSDT.am later and will post again if I do

opencore-2025-06-01-123916.txt 256 kB · 1 download DSDT.aml.zip 51.51 kB · 2 downloads

You mentioned that you want to test this "DSDT.amlDSDT.amlDSDT.aml", but I can't find anything like that. The link you provided just leads to a page without a download:
https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=o_1islp5a308pe1spnmgofn11ojbl

[leesureone]

28 minutes ago, spakk said:

You mentioned that you want to test this "DSDT.amlDSDT.amlDSDT.aml", but I can't find anything like that. The link you provided just leads to a page without a download:
https://www.insanelymac.com/applications/core/interface/file/attachment.php?id=o_1islp5a308pe1spnmgofn11ojbl

Let me try again

DSDT.aml.zip

[MaLd0n]

2 hours ago, leesureone said:

using a DSDT.aml file created by another user (possibly @MaLd0n).

Yes it's me. Ana Carolina is my wife. She start like hackintosh in 2025.

[leesureone]

30 minutes ago, MaLd0n said:

Yes it's me. Ana Carolina is my wife. She start like hackintosh in 2025.

Is it possible to convert or transform the DSDT to SSDT's and or ACPI Patches? It's beyond me to know where to start. 

[Max.1974]

9 hours ago, spakk said:

I’m modifying the code to make it work on macOS and Linux as well. I’ll upload the updated version here later today.
 

Oh my Gosh!!! Thanks a lot my fried!!! Hope you have success   

 

Awesome!!! 

[MaLd0n]

On 6/1/2025 at 1:22 PM, leesureone said:

Is it possible to convert or transform the DSDT to SSDT's and or ACPI Patches? It's beyond me to know where to start. 

You only need the PCHA and PCHS patches if you want to use SSDT. Boot is fine with this. Try with etorix patches.

Here we go my SSDT with all chipset 800 need, create missing devices in two scopes, etc

 

If have LAN 2.5g u can remove RMNE device. CHIP800.aml.zip

 

[etorix]

On 5/31/2025 at 2:32 PM, leesureone said:

I used an EFI which will boot the Asus Z890 into Sequoia, I added the ACPI patches and kept Vit9696's patch and also enabled patch #2. Cleared the NVRAM and it didn't;t seem to make a difference as without patch #2. It starts to load macOS but then halts on a variety of ACPI errors. Please see attached, I wanted but could not upload the EFI file because apparently it is too large, even after removing the Resource folder.

Coming back to this: Is it the Asus Z890 ProArt with an EFI which was known to work except for the extra patch, or the MSI Z890 Tomahawk with an EFI which was validated on the Asus board?

As for uploading the EFI, config.plist and the ACPI folder should be enough (although a complete dump of the board ACPI may be useful if some errors come from parsing the native SSDTs).

[leesureone]

18 hours ago, spakk said:

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!

 

 

🛠️ What does the DSDT-Analysis-Tool.py do?

The DSDT-Analysis-Tool.py is a small but useful Python script that helps you analyze a DSDT.aml file and automatically generate matching SSDTs and OpenCore patches — perfect for Hackintosh users.

---

✅ What the tool can do automatically:

1. Select DSDT.aml
   With one click, you can load your DSDT.aml file. It gets copied to the working folder.

2. Decompile the DSDT (make it readable)
   The tool uses iasl.exe to convert the DSDT.aml into a DSDT.dsl file, which is readable and editable.

3. Find devices with "If" conditions
   It automatically searches for If conditions and the devices inside them, showing which devices are only active under certain conditions.

4. Create SSDT-Force
   The tool generates an SSDT file with dummy devices so that OpenCore or Clover can recognize them properly.

5. Create an OpenCore patch template
   A ready-to-use patch template is created automatically for use in OpenCore.

6. Check for important devices
   It checks if key devices like HDEF, GFX0, or XHC are present. If any are missing, you get a warning.

7. Create individual SSDTs for each device (optional)
   If you want, the tool can generate a separate SSDT for each found device.

---

💾 Where are the files saved?

All generated files are saved automatically in this folder:
C:\Users\Mein\Desktop\DSDT-Analysis-Tool\DSDT_xxx\

---

🌍 Language Support

The tool detects your system language (German, English, etc.). If your language isn’t supported, it defaults to English.

---

📦 What’s included in the ZIP file?

The DSDT-Analysis-Tool.zip contains:

• The tool itself

• The required iasl.exe

• A help file

• Example images in the “Bilder” (Images) folder

---

📌 Note

This is not a professional tool, but it automates many tasks to save time.
If you find a bug or want to improve something:
Feel free to change and share it freely with others!

---

Have fun using it! 😊

 

DSDT-Analysis-Tool.zip 2.28 MB · 11 downloads

I used the tool in Windows on the Asus Z890 system, compiled the SSDTForce.aml and enabled that and a bridge file needed for the 6650XT Video card and boom, booted right up. I'll need to do more testing but first results are excellent. Thank you for all the time you spent creating this and the commitment to the community! Well done!

30 minutes ago, MaLd0n said:

You only need the PCHA and PCHS patches if you want to use SSDT. Boot is fine with this. Try with etorix patches.

Here we go my SSDT with all chipset 800 need, create missing devices in two scopes, etc

SSDT-800.zip

If have LAN 2.5g u can remove RMNE device.

 

Thank you for that, its my next project!

[MaLd0n]

On 6/1/2025 at 2:11 PM, leesureone said:

I used the tool

I tested with @etorix patch and work fine here

Test this in MSI 

I fixed it via Scopes RP0x.PXSX. Work fine too.

on Bios/UEFI disable VT-d, Disable Secure boot, Set xmp and enable Extension memory mode. 

[etorix]

49 minutes ago, MaLd0n said:

Here we go my SSDT with all chipset 800 need, create missing devices in two scopes, etc

Very interesting reading, thank you!
I see you take the system bus under PC02, but give it two BUS_ devices; may I ask why? And what are the MAC_ devices under PC00 and PC02?

[MaLd0n]

MAC devices is a missing devices. i just create with correct _ADR but there is no difference. it's just for my delight in ioreg. 

 

About BUS0 and BUS1. It's apple patches from MacPro7,1 acpi. These patches have always been a mystery and no one has ever explained whether they are really necessary. It will work the same with or without this patch.

DSDT.MacPro7,1 Real.zip

 

 

 

[leesureone]

33 minutes ago, MaLd0n said:

I tested with @etorix patch and work fine here

Test this in MSI EFI leesureone.zip

I fixed it via Scopes RP0x.PXSX. Work fine too.

on Bios/UEFI disable VT-d, Disable Secure boot, Set xmp and enable Extension memory mode. 

Nicely done, I even have my own personalized .aml file!!🤣

[etorix]

Enjoy!

You might have to customise a bit further. If I understand correctly you have a RX6650XT and need to spoof it. @MaLd0n's all-in-one SSDT preemptively names the PCI bridge where the GPU will connect; this might conflict with your spoofing SSDT, so you may want to check, and possibly remove the bridge naming in the platform SSDT to leave it in the separate SSDT which will move with the card.

[surenmunoo]

1 hour ago, leesureone said:

Nicely done, I even have my own personalized .aml file!!🤣

For your Asus Z890 ProArt, I use this EFI created for me by @MaLd0n It boots perfectly and has good scores. @MaLd0ndid advise that the Z890 ProArt is not good so far for Hackintoshing. EFI.zipI use 2 x 32G GSkill Ram sticks and if I decide to update via settings, then I have to remove 1 stick of Ram, otherwise it works well in Ventura and Sequoia for now and very stable with no crash. Unfortunately, I could not post this in the other forum else I will get banned 😂

[Cyberdevs]

@spakk

Here is the DSDT for my Z690 Auros Master board. I also attached the files generated with the app. I used Clover to dump the ACPI tables.

GA-Z690 Aorus Master DSDT.aml.zip OpenCore-Patch.txt full_device_check.txt conditional_devices.txt

[leesureone]

59 minutes ago, etorix said:

Enjoy!

You might have to customise a bit further. If I understand correctly you have a RX6650XT and need to spoof it. @MaLd0n's all-in-one SSDT preemptively names the PCI bridge where the GPU will connect; this might conflict with your spoofing SSDT, so you may want to check, and possibly remove the bridge naming in the platform SSDT to leave it in the separate SSDT which will move with the card.

The 6650XT is in the Proart system so no issue, I saw the declaration in his SSDT and wondered what its purpose was exactly.  Are you saying there should be no need to spoof a GPU that would normally require that? If so bonus!

[leesureone]

30 minutes ago, surenmunoo said:

For your Asus Z890 ProArt, I use this EFI created for me by @MaLd0n It boots perfectly and has good scores. @MaLd0ndid advise that the Z890 ProArt is not good so far for Hackintoshing. EFI.zipI use 2 x 32G GSkill Ram sticks and if I decide to update via settings, then I have to remove 1 stick of Ram, otherwise it works well in Ventura and Sequoia for now and very stable with no crash. Unfortunately, I could not post this in the other forum else I will get banned 😂

Thanks for posting that, I know what he means...the bios can be finicky and mapping USB ports has proven to be difficult if not impossible meaning sleep will not work properly. Eventually the system freezes and causes the bios to reset to default settings, it ends up being a cycle of testing the new port map, resetting the computer when it freezes, then changing the bios settings back and resetting NVRAM.

Maybe you have had better luck

[surenmunoo]

38 minutes ago, leesureone said:

Thanks for posting that, I know what he means...the bios can be finicky and mapping USB ports has proven to be difficult if not impossible meaning sleep will not work properly. Eventually the system freezes and causes the bios to reset to default settings, it ends up being a cycle of testing the new port map, resetting the computer when it freezes, then changing the bios settings back and resetting NVRAM.

Maybe you have had better luck

SO far that EFI is very reliable except for what I posted about. No crash at all in any oS and USB works as it should. I have not experimented with sleep properly and just glad it all works for now. As the hacks become more prominent for Z890 then maybe it will get better. 

[etorix]

1 hour ago, Cyberdevs said:

Here is the DSDT for my Z690 Auros Master board. I also attached the files generated with the app.

At this point, it may be helpful to point that this discussion is primarily about 800-series and AM5 board, which cannot boot at all without some DSDT patching.

Not all conditional declarations are problematic, and USB ports being conditional on their parent being actually present should NOT be an issue. But if we find possible improvements for 600-series it will be a nice bonus.

[etorix]

1 hour ago, leesureone said:

The 6650XT is in the Proart system so no issue, I saw the declaration in his SSDT and wondered what its purpose was exactly.  Are you saying there should be no need to spoof a GPU that would normally require that? If so bonus!

No, no miracle of the sort!

I meant to say that if your were using a RX 6650XT (or anything which requires a spoof) with the all-in-one SSDT, you might want to remove the bridge declaration in the all-in-one, and name the bridge in the spoofing SSDT.

All-in-one SSDT make simple EFI folders and simpler config.plist, but if you have some special hardware and special SSDT for it, a modular approach is better.

[surenmunoo]

@spakk It does not give me in English. Language, region etc is New Zealand but the app does not show English

 

[leesureone]

1 hour ago, etorix said:

No, no miracle of the sort!

I meant to say that if your were using a RX 6650XT (or anything which requires a spoof) with the all-in-one SSDT, you might want to remove the bridge declaration in the all-in-one, and name the bridge in the spoofing SSDT.

All-in-one SSDT make simple EFI folders and simpler config.plist, but if you have some special hardware and special SSDT for it, a modular approach is better.

Thanks for clarifying

[leesureone]

2 hours ago, etorix said:

No, no miracle of the sort!

I meant to say that if your were using a RX 6650XT (or anything which requires a spoof) with the all-in-one SSDT, you might want to remove the bridge declaration in the all-in-one, and name the bridge in the spoofing SSDT.

All-in-one SSDT make simple EFI folders and simpler config.plist, but if you have some special hardware and special SSDT for it, a modular approach is better.

Well, I'm back working on the Proart system and as you mentioned the BRG0 section of the all in one SSDT is conflicting with the GPU bridge file. I tried editing the all in one but get a bunch of compile errors back to where it defines the processor counts (or whatever that area is) and I can't successfully edit the file. What am I doing wrong? Can you please point me in the right direction?

 

Edit: I tried deleting that section and that is what creates the compile errors back to lines 80 to 103

Chip-800.aml

Edited June 1, 2025 by leesureone