Scanning for conditional device declarations

[MaLd0n]

On 6/1/2025 at 8:37 PM, leesureone said:

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.

use SSDT Chip-800 with NootRX.kext. Remove whatevergreen.

 NootRX.kext.zip

 

SSDT with no video device 

 

If u want stay with whatevergreen just use this patch device properties.

Default video device on chipset serie 800 is RP01.PXSX... _ADR @6 into PC00.

Quote

RX6650

            <key>PciRoot(0x0)/Pci(0x6,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>compatible</key>
                <string>pci1002,73FF</string>
                <key>device-id</key>
                <data>/3MAAA==</data>
                <key>model</key>
                <string>AMD Radeon RX 6650</string>
            </dict>
            
            
            
RX6950

            <key>PciRoot(0x0)/Pci(0x6,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key>
            <dict>
                <key>compatible</key>
                <string>pci1002,73BF</string>
                <key>device-id</key>
                <data>v3MAAA==</data>
                <key>model</key>
                <string>AMD Radeon RX 6950</string>
            </dict>

[leesureone]

2 hours ago, MaLd0n said:

use SSDT Chip-800 with NootRX.kext. Remove whatevergreen.

 NootRX.kext.zip

 

SSDT with no video device Chip-800 no BRG0.zip

 

If u want stay with whatevergreen just use this patch device properties.

Default video device on chipset serie 800 is RP01.PXSX... _ADR @6 into PC00.

Awesome, thanks for all the excellent support 

[etorix]

You're doing nothing wrong. We use the deprecated Processor() declaration because we have to for macOS and get warnings (yellow sign) about lines 80-103, but not errors (red sign).

ls1-800.aml ls1-800.dsl

[leesureone]

5 hours ago, etorix said:

You're doing nothing wrong. We use the deprecated Processor() declaration because we have to for macOS and get warnings (yellow sign) about lines 80-103, but not errors (red sign).

ls1-800.aml 1.3 kB · 1 download ls1-800.dsl 9.9 kB · 0 downloads

Dang, I didn't realize it should have compiled with those warnings. I wish there was an Editing SSDTs (r whatever) for Dummies Guide. 

[spakk]

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.

 

 

 

DSDT-Analysis-Tool-Win_Lang.zipDSDT-Analysis-Tool_macOS-Linux_Lang.zip

 

 

I have integrated the following languages:

• Arabic
• German
• English
• Spanish
• French
• Italian
• Japanese
• Polish
• Russian
• Thai
• Turkish
• Chinese

 

 

Edit:

 

I’m aware that Python can cause some issues on Windows and is often blocked by antivirus or firewall software.
I use Comodo Antivirus and Firewall, and the file DSDT-Analysis-Tool-Win.py is frequently blocked by Comodo.

To ensure the program runs correctly, you need to manually set the file as “Trusted” in the File Rating section.

After that, you can start the tool via the command line using the following command:

 

```
python DSDT-Analysis-Tool-Win.py
```
Then press Enter to run the command.

The tool works!
I’m currently working on further development. The goal is to enable the tool to insert various patches in the future to allow targeted modification of the DSDT.

 

[MaLd0n]

SSDT for all mobos with Chipset 800 with _STA 

 

SSDT for all mobos with Chipset 800 with no _STA for Opencore MOD 

 

[surenmunoo]

On 6/3/2025 at 8:24 AM, spakk said:

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.

 

 

 

DSDT-Analysis-Tool-Win_Lang.zip 1.35 MB · 7 downloads DSDT-Analysis-Tool_macOS-Linux_Lang.zip 52.72 kB · 8 downloads

 

 

I have integrated the following languages:

• Arabic
• German
• English
• Spanish
• French
• Italian
• Japanese
• Polish
• Russian
• Thai
• Turkish
• Chinese

It works in English now, thanks 

6 hours ago, MaLd0n said:

SSDT for all mobos with Chipset 800 with _STA SSDT-800.OC.zip

 

SSDT for all mobos with Chipset 800 with no _STA for Opencore MOD SSDT-800.OC-MOD.zip

 

I would not need these right? Mine is still fine with the SSDT you setup for me. @leesureone These might help with your MSI issues 

[leesureone]

19 hours ago, surenmunoo said:

It works in English now, thanks 

I would not need these right? Mine is still fine with the SSDT you setup for me. @leesureone These might help with your MSI issues 

The Proart board is the more problematic of the two, the MSI board with the updates from @MaLd0nis now working better than it ever has. I honestly don't know what _STA is or used for.

[spakk]

2 hours ago, leesureone said:

The Proart board is the more problematic of the two, the MSI board with the updates from @MaLd0nis now working better than it ever has. I honestly don't know what _STA is or used for.

Here is a simple and complete explanation of _STA that I found , which explains it very clearly:

What is `_STA`?

_STA is an ACPI method that tells the operating system the status of a device.

What does `_STA` return?

It returns a bitmask value (a number between `0x00` and `0x1F`, or 0 to 31). Each bit has a meaning:

| Bit | Hex Value | Meaning                                   |
| --- | --------- | ------------------------------  |
| 0   | 0x01      | Device is present (powered on) |
| 1   | 0x02      | Device is enabled/working         |
| 2   | 0x04      | Device can wake the system    |
| 3   | 0x08      | Device is visible to the OS        |
| 4   | 0x10      | Device is a boot device             |

 

 

Common values

* `0x0F` (15) → Most common → device is present, enabled, visible, can wake
* `0x00` (0) →  Device is hidden (not present)
* `0x0D` (13) → Present, visible, cannot wake
* `0x0B` (11) → Present, visible, not enabled
* `0x10` (16) → Boot device only (rare)

Why is `_STA` important?

* Controls whether a device appears to the operating system
* Can be used to disable or hide devices (e.g. in SSDT patches)
* Helps avoid hardware conflicts
* Used in Hackintosh setups to hide things like embedded controllers (EC)

What if `_STA` is missing?

If a device has no `_STA` method, the system assumes:

* The device is fully available
* Value is assumed to be `0x0F` (present, working, visible, etc.)

So, if you want to hide or disable a device, you must define `_STA`.

Can `_STA` be dynamic?

Example:

Method (_STA, 0, NotSerialized)
{
    If (SomeCondition)
    {
        Return (0x00) // Device hidden
    }
    Else
    {
        Return (0x0F) // Device active
    }
}

This lets you enable or disable a device depending on a condition.

Summary

* `_STA` tells the system if a device is available, active, or hidden
* `0x0F` = fully active
* `0x00` = hidden
* Without `_STA`, it's assumed to be active
* Often used in **SSDT patches** to control device visibility
 

[spakk]

I’ll upload the revised tool here tomorrow. It’s time to go to  🛏️ now.

[spakk]

Here are the updated tools:

 

for Windows: DSDT-Analysis-Tool-Win.zip

for macOS / Linux:  DSDT-Analysis-Tool-macOS-Linux.zip

 

language:

 

Spoiler

ar = Arabic
de = German
en = English
es = Spanish
fr = French
it = Italian
ja = Japanese
po = Polish (the correct code is actually "pl")
pt-BR = Portuguese (Brazil)
pt-PT = Portuguese (Portugal)
ru = Russian
th = Thai
tr = Turkish
zh = Chinese (Mandarin)

 

I just realized now that I entered the country code for Polish incorrectly, it should be pl instead of po. But it doesn’t really matter; anyone can easily change it themselves.

 

 

Edit:

Windows – Installation and Launch Guide DSDT-Analysis-Tool.pdf file

 

Windows – Installation and Launch Guide DSDT-Analysis-Tool.pdf

[XanthraX]

Hi Spakk

When I enter "brew install python gettext iasl", I get this error in return:

Warning: No available formula with the name "iasl". Did you mean isl?
==> Searching for similarly named formulae and casks...
==> Formulae
isl

To install isl, run:
  brew install isl

==> Casks
maciasl

To install maciasl, run:
  brew install --cask maciasl"

[spakk]

34 minutes ago, XanthraX said:

Hi Spakk

When I enter "brew install python gettext iasl", I get this error in return:

Warning: No available formula with the name "iasl". Did you mean isl?
==> Searching for similarly named formulae and casks...
==> Formulae
isl

To install isl, run:
  brew install isl

==> Casks
maciasl

To install maciasl, run:
  brew install --cask maciasl"

Spoiler

Here's the information:

Clarification:

You probably meant`iasl`, which is the **Intel ACPI Compiler/Decompiler** used for working with DSDT/SSDT files.
* `isl` is something completely different – it stands for Integer Set Library and is unrelated to ACPI or DSDT analysis.

If you're analyzing DSDTs/SSDTs, you need `iasl`, not `isl`.

On macOS, you can correctly install `iasl` via the Terminal as follows:

How to install iasl on macOS:

1. If you already have Homebrew:

bash
brew install iasl

2. If you don’t have Homebrew yet:

Install it with:

bash
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then run again:

bash
brew install iasl

Verify the installation:

bash
iasl -v

If you see something like `iasl version 20240322`, the installation was successful.

Summary:

| Term     | Meaning             | Relevant for DSDT tools? |
| -------- | ------------------- | ------------------------ |
| iasl     | Intel ACPI Compiler | Yes, essential           |
| isl      | Integer Set Library | No, not relevant         |

 

 

15 minutes ago, eSaF said:

I am also having a problem opening on Windows via Python.

Unless I am doing something wrong, before the update all was ok.

I’m aware that Python can cause some issues on Windows and is often blocked by antivirus or firewall software.
I use Comodo Antivirus and Firewall, and the file DSDT-Analysis-Tool-Win.py is frequently blocked by Comodo.
To ensure the program runs correctly, you need to manually set the file as “Trusted” in the File Rating section.

After that, you can start the tool via the command line using the following command:

 

Spoiler

python DSDT-Analysis-Tool-Win.pyc 

 

[etorix]

43 minutes ago, XanthraX said:

When I enter "brew install python gettext iasl", I get this error in return

brew actually seeks to install the graphical application MaciASL. If you already have MaciASL installed, you have iasl… hidden somewhere.

Type either:

ln /Applications/MaciASL.app/Contents/MacOS/iasl-stable /usr/local/sbin/iasl

or

ln -s /Applications/MaciASL.app/Contents/MacOS/iasl-stable /usr/local/sbin/iasl

(first option will survive deinstalling MaciASL, but won't update; second option will update with MaciASL, but won't survive removal)

and then you can use DSDT-Analysis-Tool.

[spakk]

Does it make sense, and is there any interest, if I create a patches.xml from the OpenCore-Patch.txt that can be directly inserted into the config.plist when needed?

Below is a sample template from my DSDT-generated OpenCore-Patch.txt, which I have automatically converted into a patches.xml.

Is there a need for this? Or are there other features you would like to see integrated into this small tool? Feel free to share your suggestions!

OpenCore-Patch txt to patches xml.zip

[etorix]

For direct insertion, the file would best be a proper .plist, which could be opened directly in a plist editor.

But I do not understand the proposed patches and what you want to achieve. To take just the first one, broadly replacing PCI0 by XPCI0 violates the ACPI specification 😱 , has no obvious purpose for me (\_SB.PCI0 unconditionally exists) and even a legal rename is most likely to break a lot of things downwards.

Edited June 6, 2025 by etorix

[STLVNUB]

I Have A Problem with my USB Powering Down Then Powering up

Get The Dreaded message

The Disk Was Not Ejected  Properly or Words To That Effect

 

Any Idea n How To Fix That

Here Is My DSDT

System DSDT.aml

[Cyberdevs]

@STLVNUB

I don't think your issue is in the scope of this topic, for now as the OP stated previously this topic is dedicated to the 800 series mainboards, but If you use Hackintool to correctly map your USB ports and generate the SSDTs and the USBPorts.kext your issue will be resolved.

[Max.1974]

4 horas atrás, STLVNUB disse:

Eu tenho um problema com o desligamento do meu USB e depois com a alimentação

Receba a mensagem temida

O disco não foi ejetado corretamente ou palavras para esse efeito

 

Alguma ideia de como consertar isso

Aqui está o meu DSDT

Sistema DSDT.aml 264,57 kB·2 downloads

 

Hi @STLVNUB how are you going?  I'm not sure about your hardware, but it seems to be a laptop like my Lenovo T14 with some PCie hardware, including Thunderbolt. I managed to map it with two kexts, one USBToolbox + USBMap and the other USBports. Both are separate because I created the USB-C and Thunderbolt ports in Windows, with some SSDT patches needed for the Thunderbolt hardware. I also use battery patches to override sleep and the start of Thunderbolt. Another important thing, I managed to formalize (create) an SSDT with EC properties that dispense with the ECEnabler kext (with all due respect to the creator's help). But Sleep works very well with them. And I also created two more SSDTS of my own to fix deep Sleep and wakeup, everything works. I saw that you added some patches to your DSDT as well. Your DSDT is very similar to mine. You may still need the IOElectrify.kext, VoltageShift.kext and some trackpad kexts, if it is I2C, you may need the VoodoI2C, VoodooI2CHID set, in addition to the basic VoodooPS2, VoodooRMI and VoodooSMBUS.

 

My EFIs maybe help you. 

 

Lenovo Thinkpad T14 1th Gen intel i5-10310-U Commet Lake-U (Nvme / Thunderbolt 3)

 

Clover 

EFI CLOVER T14 RehabMan Kexts FULL Thunderbolt 3.zip

 

Opencore 

 

EFI T14 OC 105 FULL Thunderbolt 3.zip

 

[STLVNUB]

5 hours ago, Cyberdevs said:

@STLVNUB

I don't think your issue is in the scope of this topic, for now as the OP stated previously this topic is dedicated to the 800 series mainboards, but If you use Hackintool to correctly map your USB ports and generate the SSDTs and the USBPorts.kext your issue will be resolved.

ok thanks

 

3 hours ago, Max.1974 said:

 

Hi @STLVNUB how are you going?  I'm not sure about your hardware, but it seems to be a laptop like my Lenovo T14 with some PCie hardware, including Thunderbolt. I managed to map it with two kexts, one USBToolbox + USBMap and the other USBports. Both are separate because I created the USB-C and Thunderbolt ports in Windows, with some SSDT patches needed for the Thunderbolt hardware. I also use battery patches to override sleep and the start of Thunderbolt. Another important thing, I managed to formalize (create) an SSDT with EC properties that dispense with the ECEnabler kext (with all due respect to the creator's help). But Sleep works very well with them. And I also created two more SSDTS of my own to fix deep Sleep and wakeup, everything works. I saw that you added some patches to your DSDT as well. Your DSDT is very similar to mine. You may still need the IOElectrify.kext, VoltageShift.kext and some trackpad kexts, if it is I2C, you may need the VoodoI2C, VoodooI2CHID set, in addition to the basic VoodooPS2, VoodooRMI and VoodooSMBUS.

 

My EFIs maybe help you. 

 

Lenovo Thinkpad T14 1th Gen intel i5-10310-U Commet Lake-U (Nvme / Thunderbolt 3)

 

Clover 

EFI CLOVER T14 RehabMan Kexts FULL Thunderbolt 3.zip 31.07 MB · 1 download

 

Opencore 

 

EFI T14 OC 105 FULL Thunderbolt 3.zip 22.49 MB · 3 downloads

 

Thanks So Much

[Avery B]

I would take another look at your patches @spakk:
- PCI0 -> XPCI0 isn't a valid patch - ACPI names are limited up to four characters (and are always padded out to four characters using underscores).
- I think the original script from @etorix checked for brackets (and depth) - it may be worth copying that logic over as some of these results look a little suspect. Any references to Argx/Localx is likely to be within a method which I don't think you want to patch. I saw a couple of those in the output from @surenmunoo.

[STLVNUB]

56 minutes ago, STLVNUB said:

ok thanks

 

Thanks So Much

I Try Your EFI As Is, And See How It Goes

 

[Max.1974]

2 hours ago, STLVNUB said:

I Try Your EFI As Is, And See How It Goes

 

Hi my friend, need use your SSDTs (maybe test som mines) and manage your DSDT if you want continue using it.  

My EFI and patches is for you compare and try use, good lucky!

 

Edited June 9, 2025 by Max.1974

[STLVNUB]

41 minutes ago, Max.1974 said:

Hi my friend, need use your SSDTs (maybe test som mines) and manage your DSDT if you want continue using it.  

My EFI and patches is for you compare and try use, good lucky!

 

not working, i tried virgin efi, none of my files

 

44 minutes ago, Max.1974 said:

Hi my friend, need use your SSDTs (maybe test som mines) and manage your DSDT if you want continue using it.  

My EFI and patches is for you compare and try use, good lucky!

 

ok

[Max.1974]

Opcore Simplify is awesome to create from scratch