mirror of
https://github.com/AskDavis/Getting-Started-With-ACPI.git
synced 2026-01-01 05:05:57 -08:00
Switch to submodule
This commit is contained in:
Dhinak G
@@ -1,6 +1,5 @@
|
||||
# Fixing System Clocks on HEDT: Manual
|
||||
|
||||
|
||||
* [Finding the ACPI path](#finding-the-acpi-path)
|
||||
* [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
|
||||
* [Compiling the SSDT](#compiling-the-ssdt)
|
||||
@@ -8,7 +7,7 @@
|
||||
|
||||
## Seeing if you need SSDT-RTC0-RANGE
|
||||
|
||||
To start, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
To start, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Now search for `PNP0B00` and look at the `_CRS` entry within it:
|
||||
|
||||
@@ -23,10 +22,9 @@ Now the problem is that the OEM forgot to mat sections 0x72 and 0x73. Because of
|
||||
|
||||
And finally, verify if it has an _STA method as well. This will be used shortly
|
||||
|
||||
|
||||
## Finding the ACPI path
|
||||
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
To start, search for the following:
|
||||
|
||||
@@ -79,8 +77,8 @@ Scope (_SB.PCI0.LPC0.RTC) <- Renamed
|
||||
Scope (_SB.PCI0.LPC0) <- Renamed
|
||||
|
||||
|
||||
/* <- Remove if your RTC device didn't have an _STA
|
||||
Scope (RTC)
|
||||
/* <- Remove if your RTC device didn't have an _STA
|
||||
Scope (RTC)
|
||||
{
|
||||
Method (_STA, 0, NotSerialized) // _STA: Status
|
||||
{
|
||||
@@ -94,7 +92,7 @@ Scope (_SB.PCI0.LPC0) <- Renamed
|
||||
}
|
||||
}
|
||||
}
|
||||
*/ <- Remove if your RTC device didn't have an _STA
|
||||
*/ <- Remove if your RTC device didn't have an _STA
|
||||
```
|
||||
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@
|
||||
|
||||
* **Note**: X99 and X299 see [here](../awac-methods/manual-hedt.md)
|
||||
|
||||
Finding which SSDT you need is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding which SSDT you need is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next search for `ACPI000E`. You should get something similar:
|
||||
|
||||
|
||||
@@ -31,5 +31,5 @@ For the RTC fix, there are 3 methods you can choose from:
|
||||
* **Does not support HEDT**
|
||||
* [Manual](/Universal/awac-methods/manual.md)
|
||||
* For most users
|
||||
* [Manual-HEDT](/Universal/awac-methods/manual-hedt.md)
|
||||
* [Manual HEDT](/Universal/awac-methods/manual-hedt.md)
|
||||
* For X99 and X299 users
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# Fixing Embedded Controller (SSDT-EC/USBX)
|
||||
|
||||
- [Fixing Embedded Controller (SSDT-EC/USBX)](#fixing-embedded-controller-ssdt-ecusbx)
|
||||
- [What this SSDT does](#what-this-ssdt-does)
|
||||
- [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
* [Fixing Embedded Controller (SSDT-EC/USBX)](#fixing-embedded-controller-ssdt-ecusbx)
|
||||
* [What this SSDT does](#what-this-ssdt-does)
|
||||
* [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
|
||||
## What this SSDT does
|
||||
|
||||
|
||||
@@ -1,17 +1,17 @@
|
||||
# Fixing Embedded Controllers: Manual
|
||||
|
||||
- [Fixing Embedded Controllers: Manual](#fixing-embedded-controllers-manual)
|
||||
- [Finding the ACPI path](#finding-the-acpi-path)
|
||||
- [DSDT](#dsdt)
|
||||
- [DeviceManager](#devicemanager)
|
||||
- [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
|
||||
- [Edge Cases](#edge-cases)
|
||||
- [Multiple PNP0C09's show up](#multiple-pnp0c09s-show-up)
|
||||
- [No PNP0C09 show up](#no-pnp0c09-show-up)
|
||||
- [PNP0C09 already named `EC`](#pnp0c09-already-named-ec)
|
||||
- [PNP0C09 already has an `_STA` method](#pnp0c09-already-has-an-_sta-method)
|
||||
- [Compiling the SSDT](#compiling-the-ssdt)
|
||||
- [Wrapping up](#wrapping-up)
|
||||
* [Fixing Embedded Controllers: Manual](#fixing-embedded-controllers-manual)
|
||||
* [Finding the ACPI path](#finding-the-acpi-path)
|
||||
* [DSDT](#dsdt)
|
||||
* [DeviceManager](#devicemanager)
|
||||
* [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
|
||||
* [Edge Cases](#edge-cases)
|
||||
* [Multiple PNP0C09's show up](#multiple-pnp0c09s-show-up)
|
||||
* [No PNP0C09 show up](#no-pnp0c09-show-up)
|
||||
* [PNP0C09 already named `EC`](#pnp0c09-already-named-ec)
|
||||
* [PNP0C09 already has an `_STA` method](#pnp0c09-already-has-an-_sta-method)
|
||||
* [Compiling the SSDT](#compiling-the-ssdt)
|
||||
* [Wrapping up](#wrapping-up)
|
||||
|
||||
TO-DO:
|
||||
|
||||
@@ -26,7 +26,7 @@ To find the ACPI pathing, you have 2 methods:
|
||||
|
||||
### DSDT
|
||||
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next, search for `PNP0C09`. You should get something similar:
|
||||
|
||||
@@ -43,18 +43,18 @@ But now we get into edge case territory, what fun!
|
||||
|
||||
The main ones to check for are:
|
||||
|
||||
- [Fixing Embedded Controllers: Manual](#fixing-embedded-controllers-manual)
|
||||
- [Finding the ACPI path](#finding-the-acpi-path)
|
||||
- [DSDT](#dsdt)
|
||||
- [DeviceManager](#devicemanager)
|
||||
- [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
|
||||
- [Edge Cases](#edge-cases)
|
||||
- [Multiple PNP0C09's show up](#multiple-pnp0c09s-show-up)
|
||||
- [No PNP0C09 show up](#no-pnp0c09-show-up)
|
||||
- [PNP0C09 already named `EC`](#pnp0c09-already-named-ec)
|
||||
- [PNP0C09 already has an `_STA` method](#pnp0c09-already-has-an-_sta-method)
|
||||
- [Compiling the SSDT](#compiling-the-ssdt)
|
||||
- [Wrapping up](#wrapping-up)
|
||||
* [Fixing Embedded Controllers: Manual](#fixing-embedded-controllers-manual)
|
||||
* [Finding the ACPI path](#finding-the-acpi-path)
|
||||
* [DSDT](#dsdt)
|
||||
* [DeviceManager](#devicemanager)
|
||||
* [Edits to the sample SSDT](#edits-to-the-sample-ssdt)
|
||||
* [Edge Cases](#edge-cases)
|
||||
* [Multiple PNP0C09's show up](#multiple-pnp0c09s-show-up)
|
||||
* [No PNP0C09 show up](#no-pnp0c09-show-up)
|
||||
* [PNP0C09 already named `EC`](#pnp0c09-already-named-ec)
|
||||
* [PNP0C09 already has an `_STA` method](#pnp0c09-already-has-an-_sta-method)
|
||||
* [Compiling the SSDT](#compiling-the-ssdt)
|
||||
* [Wrapping up](#wrapping-up)
|
||||
|
||||
If none of the above apply to you, you're ready for the next section:
|
||||
|
||||
@@ -79,7 +79,6 @@ Now that we have our ACPI path, lets grab our SSDT and get to work:
|
||||
* [SSDT-EC](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-EC.dsl)
|
||||
* For Broadwell and older
|
||||
|
||||
|
||||
Now when opening this SSDT, you'll notice a few things. Mainly:
|
||||
|
||||
* Some code is commented out
|
||||
@@ -110,8 +109,6 @@ Scope (_SB.PC00.LPC0) <- Renamed
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Edge Cases
|
||||
|
||||
### Multiple PNP0C09's show up
|
||||
@@ -132,17 +129,17 @@ When this happens, you'll only need to create a "dummy" EC for macOS.
|
||||
|
||||
Try searching for any devices named: "LPCB", "LPC0", "LPC", "SBRG", "PX40". If you have any of these, try using the LPC pathing of each of those device in place of the Embedded Controller's pathing.
|
||||
|
||||
Note that **DO NOT** uncomment the EC disaling code as there are no devices that are considered "EC" in your machine.
|
||||
Note that **DO NOT** uncomment the EC disabling code as there are no devices that are considered "EC" in your machine.
|
||||
|
||||
### PNP0C09 already named `EC`
|
||||
|
||||
Congrats! No need to create an SSDT-EC! However you will still want USBX if you're skylake or newer.
|
||||
Congrats! No need to create an SSDT-EC! However you will still want USBX if you're Skylake or newer.
|
||||
|
||||
Prebuilt can be grabbed here: [SSDT-USBX.aml](https://github.com/dortania/OpenCore-Post-Install/blob/master/extra-files/SSDT-USBX.aml)
|
||||
|
||||
### PNP0C09 already has an `_STA` method
|
||||
|
||||
This is the equivalent of not having an EC as we can't control it with our SSDT-EC, instead we'll need to create a "dummy" EC for macOS. You'll still want to find the PCI and LPC pathing for this device. So follow the guide as if you were creating a laptop SSDT-EC/USBX.
|
||||
This is the equivalent of not having an EC as we can't control it with our SSDT-EC, instead we'll need to create a "dummy" EC for macOS. You'll still want to find the PCI and LPC pathing for this device. So follow the guide as if you were creating a laptop SSDT-EC/USBX.
|
||||
|
||||
Example of an EC with STA already:
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
## Finding the ACPI device
|
||||
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next, search for the following devices:
|
||||
|
||||
@@ -21,7 +21,6 @@ If none of the 3 show up, you'll need to create an SSDT-IMEI.
|
||||
|
||||
The rest of this page will however assume none of those 3 devices showed up.
|
||||
|
||||
|
||||
## Compiling the SSDT
|
||||
|
||||
So there's actually no edits required to SSDT-IMEI, you can either grab the source code and compile yourself or use the prebuilt
|
||||
@@ -30,7 +29,6 @@ So there's actually no edits required to SSDT-IMEI, you can either grab the sour
|
||||
|
||||
* [SSDT-IMEI's source code](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-IMEI.dsl)
|
||||
|
||||
|
||||
With the SSDT done, you're now [ready to compile the SSDT!](/Manual/compile.md)
|
||||
|
||||
## Wrapping up
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# Fixing IMEI (SSDT-IMEI)
|
||||
|
||||
- [Fixing IMEI (SSDT-IMEI)](#fixing-imei-ssdt-imei)
|
||||
- [What this SSDT does](#what-this-ssdt-does)
|
||||
- [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
* [Fixing IMEI (SSDT-IMEI)](#fixing-imei-ssdt-imei)
|
||||
* [What this SSDT does](#what-this-ssdt-does)
|
||||
* [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
|
||||
## What this SSDT does
|
||||
|
||||
@@ -12,11 +12,10 @@ The purpose of SSDT-IMEI is:
|
||||
* The same applies when mixing Sandy Bridge motherboards with 7 series motherboards
|
||||
* An extra issue that may pop up is that the IMEI won't appear in ACPI, which can lead to more issues as macOS expects there to be an ACPI device to apply device-id's. So to resolve, we'll want to verify if we have an IMEI device, and if not create a new device.
|
||||
|
||||
|
||||
## Methods to make this SSDT
|
||||
|
||||
For the IMEI fix, there are 2 methods you can choose from:
|
||||
|
||||
* [Prebuilt](/Universal/imei-methods/prebuilt.md)
|
||||
* The prebuilt are a bit bloated. It's recommended to use the method below.
|
||||
* [Manual](/Universal/imei-methods/manual.md)
|
||||
* [Manual](/Universal/imei-methods/manual.md)
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
## Finding the ACPI path
|
||||
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next, search for the following:
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
* [What this SSDT does](#what-this-ssdt-does)
|
||||
* [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
|
||||
|
||||
## What this SSDT does
|
||||
|
||||
This SSDT is required for all "true" 300 series motherboards(Z370 is excluded), it specifically brings back NVRAM support and requires very little configuration for the end user.
|
||||
@@ -10,7 +10,7 @@ This SSDT is required for all "true" 300 series motherboards(Z370 is excluded),
|
||||
* B360
|
||||
* B365
|
||||
* H310
|
||||
* H370(HM370shouldn't require this)
|
||||
* H370 (HM370 shouldn't require this)
|
||||
* Z390
|
||||
|
||||
10th gen motherboards **do not** need this SSDT, NVRAM's native on these platforms.
|
||||
@@ -21,4 +21,4 @@ The main ways to make this SSDT:
|
||||
|
||||
* [Prebuilt](/Universal/nvram-methods/prebuilt.md)
|
||||
* [SSDTTime](/Universal/nvram-methods/ssdttime.md)
|
||||
* [Manual](/Universal/nvram-methods/manual.md)
|
||||
* [Manual](/Universal/nvram-methods/manual.md)
|
||||
|
||||
@@ -16,7 +16,7 @@ To find the ACPI pathing, you have 2 methods:
|
||||
|
||||
### DSDT
|
||||
|
||||
CPU naming is fairly easy to figure out, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
CPU naming is fairly easy to figure out, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next search for `Processor`. This should give you a result like this:
|
||||
|
||||
@@ -26,7 +26,7 @@ As we can see, the first processor in our list is `SB.PR00`. This is what we'll
|
||||
|
||||
**X99 and X299 note**:
|
||||
|
||||
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:
|
||||
Due to the different DSDT structure of these systems, you'll need to actually check in multiple places as the pathing isn't as obvious:
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# Fixing Power Management (SSDT-PLUG)
|
||||
|
||||
- [Fixing Power Management (SSDT-PLUG)](#fixing-power-management-ssdt-plug)
|
||||
- [What this SSDT does](#what-this-ssdt-does)
|
||||
- [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
* [Fixing Power Management (SSDT-PLUG)](#fixing-power-management-ssdt-plug)
|
||||
* [What this SSDT does](#what-this-ssdt-does)
|
||||
* [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
|
||||
## What this SSDT does
|
||||
|
||||
@@ -10,7 +10,7 @@ The purpose of SSDT-PLUG is to allow the kernel's XCPM(XNU's CPU Power Managemen
|
||||
|
||||
**Note**: SSDT-PLUG is only compatible with Intel's Haswell and newer CPUs, Sandy Bridge and Ivy Bridge will need to follow the [ssdtPRgen method](https://dortania.github.io/OpenCore-Post-Install/universal/pm.html#sandy-and-ivy-bridge-power-management)(in post-install) while AMD users should not use this(unless attempting to attach AGPM which is outside the scope of Dortania's guides)
|
||||
|
||||
* Ivy Bridge-E(HEDT/server) however is supported by XCPM
|
||||
* Ivy Bridge-E(HEDT/server) however is supported by XCPM
|
||||
|
||||
## Methods to make this SSDT
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
## Finding the ACPI path
|
||||
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either maciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT you got from [Dumping the DSDT](/Manual/dump.md) and [Decompiling and Compiling](/Manual/compile.md) with either MaciASL(if in macOS) or any other text editor if in Windows or Linux(VSCode has an [ACPI extension](https://marketplace.visualstudio.com/items?itemName=Thog.vscode-asl) that can also help).
|
||||
|
||||
Next, search for the `Device (RHUB)`
|
||||
|
||||
|
||||
@@ -49,22 +49,24 @@ The specifics are due to [Endianness](https://en.wikipedia.org/wiki/Endianness)
|
||||
### Linux
|
||||
|
||||
If you can run Linux, use command `lspci -vmmnnD -d 1002::0300`
|
||||
|
||||
```
|
||||
$ lspci -vmmnnD -d 1002::0300
|
||||
Slot: 0000:01:00.0
|
||||
Class: VGA compatible controller [0300]
|
||||
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
|
||||
Device: Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [6611]
|
||||
SVendor: Micro-Star International Co., Ltd. [MSI] [1462]
|
||||
SDevice: Device [3740]
|
||||
Rev: 87
|
||||
Slot: 0000:01:00.0
|
||||
Class: VGA compatible controller [0300]
|
||||
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
|
||||
Device: Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [6611]
|
||||
SVendor: Micro-Star International Co., Ltd. [MSI] [1462]
|
||||
SDevice: Device [3740]
|
||||
Rev: 87
|
||||
```
|
||||
|
||||
You can easily get
|
||||
- Slot ID `0000:01:00.0`, we need it later
|
||||
- Vendor ID `1002`, all AMD devices have this ID
|
||||
- Device ID `6611`, this is what we care about
|
||||
- Device name `Radeon HD 8570 / R7 240/340 / Radeon 520 OEM`, mainly cosmetic
|
||||
|
||||
* Slot ID `0000:01:00.0`, we need it later
|
||||
* Vendor ID `1002`, all AMD devices have this ID
|
||||
* Device ID `6611`, this is what we care about
|
||||
* Device name `Radeon HD 8570 / R7 240/340 / Radeon 520 OEM`, mainly cosmetic
|
||||
|
||||
## Finding the ACPI Path of the GPU
|
||||
|
||||
|
||||
@@ -11,7 +11,6 @@ Super simple, just grab the SSDT and compile:
|
||||
|
||||
* [SSDT-UNC.dsl](https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/AcpiSamples/SSDT-UNC.dsl)
|
||||
|
||||
|
||||
See here how to compile: [Compiling ACPI](/Manual/compile.md)
|
||||
|
||||
## Wrapping up
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
* [What this SSDT does](#what-this-ssdt-does)
|
||||
* [Methods to make this SSDT](#methods-to-make-this-ssdt)
|
||||
|
||||
|
||||
## What this SSDT does
|
||||
|
||||
This SSDT is required for all X99 and many X79 boards, it specifically disables unused devices in ACPI ensuing IOPCIFamily doesn't kernel panic. This requires very little configuration for the end user.
|
||||
@@ -17,4 +17,4 @@ This SSDT is required for all X99 and many X79 boards, it specifically disables
|
||||
The main ways to make this SSDT:
|
||||
|
||||
* [Prebuilt](/Universal/unc0-methods/prebuilt.md)
|
||||
* [Manual](/Universal/unc0-methods/manual.md)
|
||||
* [Manual](/Universal/unc0-methods/manual.md)
|
||||
|
||||
Reference in New Issue
Block a user