AskDavis/Getting-Started-With-ACPI
1
0
Fork 0
mirror of https://github.com/AskDavis/Getting-Started-With-ACPI.git synced 2026-01-01 05:05:57 -08:00
Code Issues Packages Projects Releases Wiki Activity

Inital import

Browse Source
This commit is contained in:
Mykola Grymalyuk
2020-07-17 14:46:53 -06:00
parent 5232db073b
commit 3586de127a
33 changed files with 11223 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Universal/awac-methods/manual.md
View File

@@ -13,7 +13,7 @@ Finding which SSDT you need is quite easy actually, first open your decompiled D
Next search for `ACPI000E`. You should get something similar:
![](/images/Universal/awac-md/ACPI000E.png)
![](../../images/Universal/awac-md/ACPI000E.png)
The above tells us a few things:
@@ -24,7 +24,7 @@ The above tells us a few things:
But to double check, next search for `PNP0B00`:
![](/images/Universal/awac-md/PNP0B00.png)
![](../../images/Universal/awac-md/PNP0B00.png)
And looks at that, we can in fact disable our AWAC and enable the RTC! If not skip to here: [RTC0 Method](#rtc0-method)
@@ -68,7 +68,7 @@ You should get something like the following show up:
LPC Pathing | PCI Pathing
:-------------------------:|:-------------------------:
![](/images/Universal/nvram-md/lpc.png) | ![](/images/Universal/nvram-md/pci0.png)
![](../../images/Universal/nvram-md/lpc.png) | ![](../../images/Universal/nvram-md/pci0.png)
From the above, we can see we have both `PCI0` and `LPC`. Now we can head to the next stage
@@ -90,7 +90,7 @@ External (_SB_.PCI0.LPCB, DeviceObj) <- Rename this
Scope (_SB.PCI0.LPCB) <- Rename this
```
![](/images/Universal/awac-md/ssdt-before.png)
![](../../images/Universal/awac-md/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this:
@@ -102,7 +102,7 @@ External (_SB_.PCI0.LPC, DeviceObj) <- Renamed
Scope (_SB.PCI0.LPC) <- Renamed
```
![](/images/Universal/awac-md/ssdt-after.png)
![](../../images/Universal/awac-md/ssdt-after.png)
### Compiling the SSDT

10
Universal/ec-methods/manual.md
View File

@@ -30,7 +30,7 @@ Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT
Next, search for `PNP0C09`. You should get something similar:
![](/images/Desktops/pnp.png)
![](../../images/Desktops/pnp.png)
From the above example we see 2 main things:
@@ -64,7 +64,7 @@ If you already have Windows installed on this machine, finding the EC pathing is
Start by opening up Device Manager in Windows and looking for a device named `Embedded Controller`. Once found, click on it and select the `BIOS device Name` entry. You should get something like this:
![](/images/Desktops/ec.png)
![](../../images/Desktops/ec.png)
From the above, we can see that our pathing is `SB.PC00.LPC0.EC0`
@@ -96,7 +96,7 @@ External (_SB_.PCI0.LPCB, DeviceObj) <- Rename this
Scope (_SB.PCI0.LPCB) <- Rename this
```
![](/images/Desktops/ssdt-before.png)
![](../../images/Desktops/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this:
@@ -108,7 +108,7 @@ External (_SB_.PC00.LPC0, DeviceObj) <- Renamed
Scope (_SB.PC00.LPC0) <- Renamed
```
![](/images/Desktops/ssdt-after.png)
![](../../images/Desktops/ssdt-after.png)
@@ -142,7 +142,7 @@ This is the equivalent of not having an EC as we can't control it with our SSDT-
Example of an EC with STA already:
![Credit to rottenpants466](/images/Desktops/sta.png)
![Credit to rottenpants466](../../images/Desktops/sta.png)
## Compiling the SSDT

6
Universal/nvram-methods/manual.md
View File

@@ -20,7 +20,7 @@ You should get something like the following show up:
LPC Pathing | PCI Pathing
:-------------------------:|:-------------------------:
![](/images/Universal/nvram-md/lpc.png) | ![](/images/Universal/nvram-md/pci0.png)
![](../../images/Universal/nvram-md/lpc.png) | ![](../../images/Universal/nvram-md/pci0.png)
Now with the pathing, you can head here: [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
@@ -42,7 +42,7 @@ External (_SB_.PCI0.LPCB, DeviceObj) <- Rename this
Scope (_SB.PCI0.LPCB) <- Rename this
```
![](/images/Universal/nvram-md/ssdt-before.png)
![](../../images/Universal/nvram-md/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this:
@@ -54,7 +54,7 @@ External (_SB_.PCI0.LPC, DeviceObj) <- Renamed
Scope (_SB.PCI0.LPC) <- Renamed
```
![](/images/Universal/nvram-md/ssdt-after.png)
![](../../images/Universal/nvram-md/ssdt-after.png)
## Compiling the SSDT

12
Universal/plug-methods/manual.md
View File

@@ -20,7 +20,7 @@ CPU naming is fairly easy to figure out, first open your decompiled DSDT you got
Next search for `Processor`. This should give you a result like this:
![](/images/Universal/plug-md/processor.png)
![](../../images/Universal/plug-md/processor.png)
As we can see, the first processor in our list is `SB.PR00`. This is what we'll be applying the `plugin-type=1` property too.
@@ -28,11 +28,11 @@ As we can see, the first processor in our list is `SB.PR00`. This is what we'll
Due to the different DSDT structure of these systems, you'll need to to actually check in multiple places as the pathing isn't as obvious:
![](/images/Universal/plug-md/processor-2.png)
![](../../images/Universal/plug-md/processor-2.png)
If we then search for instances of `CP00` we find that its full ACPI pathing is `SB.SCK0.CP00`:
![](/images/Universal/plug-md/cp00.png)
![](../../images/Universal/plug-md/cp00.png)
Now with the pathing, you can head here: [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
@@ -42,7 +42,7 @@ If you already have Windows installed on this machine, finding the CPU pathing i
Start by opening up Device Manager in Windows and looking for a device named `Processor`. Once found, click on it and select the `BIOS device Name` entry. You should get something like this:
![](/images/Universal/plug-md/plug-bios.png)
![](../../images/Universal/plug-md/plug-bios.png)
From the above, we can see that our pathing is `PR.CPU0`. Pay close attention to the start as `PR` is important for creating the SSDT
@@ -50,7 +50,7 @@ From the above, we can see that our pathing is `PR.CPU0`. Pay close attention to
Odd quirk of DeviceManager in Windows is that the Processor's order does not actually match the ACPI path, instead giving something like `SB.SCK0.CP10`:
![](/images/Universal/plug-md/plug-x299.png)
![](../../images/Universal/plug-md/plug-x299.png)
When this happens, you can either:
@@ -75,7 +75,7 @@ For the below example, we'll be using the X299 example(`SB.SCK0.CP00`)
Original | Cleaned Up
:-------------------------:|:-------------------------:
![](/images/Universal/plug-md/ssdt-mess.png) | ![](/images/Universal/plug-md/ssdt-clean.png)
![](../../images/Universal/plug-md/ssdt-mess.png) | ![](../../images/Universal/plug-md/ssdt-clean.png)
## Compiling the SSDT

6
Universal/rhub-methods/manual.md
View File

@@ -13,7 +13,7 @@ Next, search for the `Device (RHUB)`
You should get something like the following show up:
![](/images/Universal/rhub-md/rhub-path.png)
![](../../images/Universal/rhub-md/rhub-path.png)
From the above, we can see that the full ACPI pathing for RHUB is `PCI0.XHC.RHUB`. If it's not as clear you can search for what those device paths are for your system:
@@ -42,7 +42,7 @@ External (_SB_.PCI0.XHC_.RHUB, DeviceObj) <- Rename this
Scope (_SB.PCI0.XHC_.RHUB) <- Rename this
```
![](/images/Universal/rhub-md/ssdt-before.png)
![](../../images/Universal/rhub-md/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this:
@@ -54,7 +54,7 @@ External (_SB.PCI0.XHC1.RHUB, DeviceObj) <- Renamed
Scope (_SB.PCI0.XHC1.RHUB) <- Renamed
```
![](/images/Universal/rhub-md/ssdt-after.png)
![](../../images/Universal/rhub-md/ssdt-after.png)
## Compiling the SSDT

14
Universal/smbus-methods/manual.md
View File

@@ -18,7 +18,7 @@ So to find the ACPI pathing of our SMBus, we've got 2 methods:
To find the correct pathing for your devices, grab [Hackintool](https://www.tonymacx86.com/threads/release-hackintool-v3-x-x.254559/) ([Github link](https://github.com/headkaze/Hackintool)) and head to the PCI tab:
![](/images/Universal/smbus-md/pci.png)
![](../../images/Universal/smbus-md/pci.png)
Look for the SMBus device under Subclass, then look beside and you'll see the ACPI path(under IOReg Name). To convert , omit `@...`
@@ -32,7 +32,7 @@ If you already have Windows installed on this machine, finding the SMBus pathing
Start by opening up Device Manager in Windows and looking for a device named `SMBUS`. Once found, click on it and select the `BIOS device Name` entry. You should get something like this:
![](/images/Universal/smbus-md/smbus.png)
![](../../images/Universal/smbus-md/smbus.png)
From the above example, we can see the SMBus is located at:
@@ -52,7 +52,7 @@ So the important parts we care about are:
**Before**:
```text
```
External (_SB_.PCI0, DeviceObj) <- Rename this
External (_SB_.PCI0.SBUS.BUS0, DeviceObj) <- Rename this
@@ -67,13 +67,13 @@ Scope (_SB.PCI0) <- Rename this
Device (_SB.PCI0.SBUS.BUS0) <- Rename this
```
![](/images/Universal/smbus-md/before-rename.png)
![](../../images/Universal/smbus-md/before-rename.png)
Following the example SMBus pathing we found, the SSDT should look something like this:
**After**:
```text
```
External (_SB_.PC00, DeviceObj) <- Renamed
External (_SB_.PC00.SMBS.BUS0, DeviceObj) <- Renamed
@@ -88,7 +88,7 @@ Scope (_SB.PC00) <- Renamed
Device (_SB.PC00.SMBS.BUS0) <- Renamed
```
![](/images/Universal/smbus-md/after-rename.png)
![](../../images/Universal/smbus-md/after-rename.png)
# Compiling the SSDT
@@ -108,4 +108,4 @@ Once you've installed macOS, you can actually check whether your SSDT-SBUS-MCHC
kextstat | grep -E "AppleSMBusController|AppleSMBusPCI"
```
![](/images/Universal/smbus-md/verify.png)
![](../../images/Universal/smbus-md/verify.png)

4
Universal/spoof.md
View File

@@ -53,9 +53,9 @@ To find the PCI path of a GPU is fairly simple, best way to find it is running W
* Under the Details Tab, search for "Location Paths"
* Note some GPUs may be hiding under "BIOS device name"
![](/images/Desktops/amd.png)
![](../images/Desktops/amd.png)
![Credit to 1Revenger1 for the image](/images/Desktops/nvidia.png)
![Credit to 1Revenger1 for the image](../images/Desktops/nvidia.png)
The second "ACPI" is what we care about: