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

1
.gitignore vendored
View File

@@ -2,3 +2,4 @@ _book/
node_modules/ node_modules/
.vscode/ .vscode/
.DS_Store .DS_Store
yarn.lock

BIN
.vuepress/.config.js.swp Normal file
View File

Binary file not shown.

15
.vuepress/components/Foo/Bar.vue Executable file
View File

@@ -0,0 +1,15 @@
<template>
<p class="demo">
{{ msg }}
</p>
</template>
<script>
export default {
data () {
return {
msg: 'Hello this is <Foo-Bar>'
}
}
}
</script>

3
.vuepress/components/OtherComponent.vue Executable file
View File

@@ -0,0 +1,3 @@
<template>
<p class="demo">This is another component</p>
</template>

15
.vuepress/components/demo-component.vue Executable file
View File

@@ -0,0 +1,15 @@
<template>
<p class="demo">
{{ msg }}
</p>
</template>
<script>
export default {
data() {
return {
msg: 'Hello this is <demo-component>'
}
}
}
</script>

275
.vuepress/config.js Executable file
View File

@@ -0,0 +1,275 @@
const {
description
} = require('../package')
module.exports = {
/**
* Ref：https://v1.vuepress.vuejs.org/config/#title
*/
title: 'Getting Started With ACPI',
/**
* Ref：https://v1.vuepress.vuejs.org/config/#description
*/
description: description,
/**
* Extra tags to be injected to the page HTML `<head>`
*
* ref：https://v1.vuepress.vuejs.org/config/#head
*/
head: [
['meta', {
name: 'theme-color',
content: '#3eaf7c'
}],
['meta', {
name: 'apple-mobile-web-app-capable',
content: 'yes'
}],
['meta', {
name: 'apple-mobile-web-app-status-bar-style',
content: 'black'
}],
["link", {
rel: "'stylesheet",
href: "/styles/website.css"
},]
],
base: '/Getting-Started-With-ACPI/',
markdown: {
extendMarkdown: md => {
md.use(require('markdown-it-multimd-table'))
}
},
/**
* Theme configuration, here is the default theme configuration for VuePress.
*
* ref：https://v1.vuepress.vuejs.org/theme/default-theme-config.html
*/
theme: 'vuepress-theme-succinct',
globalUIComponents: [
'ThemeManager'
],
themeConfig: {
lastUpdated: true,
repo: 'https://github.com/dortania/Getting-Started-With-ACPI',
editLinks: false,
docsDir: '',
editLinkText: '',
logo: '/homepage.png',
nav: [{
text: 'Dortania Guides',
ariaLabel: 'Language Menu',
items: [{
text: 'Home Site',
link: 'https://dortania.github.io/'
},
{
text: 'OpenCore Install Guide',
link: 'https://dortania.github.io/OpenCore-Desktop-Guide/'
},
{
text: 'OpenCore Post-Install',
link: 'https://dortania.github.io/OpenCore-Post-Install/'
},
{
text: 'Wireless Buyers Guide',
link: 'https://dortania.github.io/Wireless-Buyers-Guide/'
},
{
text: 'GPU Buyers Guide',
link: 'https://dortania.github.io/GPU-Buyers-Guide/'
},
{
text: 'Anti Buyers Guide',
link: 'https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/'
},
]
},
/*
{
text: 'Github',
link: 'https://github.com/dortania/OpenCore-Desktop-Guide'
}
*/
],
sidebar: [{
title: 'Introduction',
collapsable: false,
sidebarDepth: 1,
children: [
['', 'Getting Started With ACPI'],
['ssdt-platform', 'Choosing the SSDTs'],
]
},
{
title: 'Methods',
collapsable: false,
sidebarDepth: 2,
children: [
'/ssdt-methods/ssdt-methods',
{
title: 'Methods',
collapsable: false,
sidebarDepth: 2,
children: [
'/ssdt-methods/ssdt-prebuilt',
'/ssdt-methods/ssdt-easy',
'/ssdt-methods/ssdt-long',
]
},
]
},
{
title: 'Manual',
collapsable: false,
sidebarDepth: 1,
children: [
'/Manual/dump',
'/Manual/compile',
]
},
{
title: 'Desktop',
collapsable: false,
sidebarDepth: 1,
children: [
['/Desktops/desktop-disable', 'Disabling desktop dGPUs'],
]
},
{
title: 'Laptop',
collapsable: false,
sidebarDepth: 0,
children: [
['/Laptops/backlight', 'Fixing Backlight'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Laptops/backlight-methods/prebuilt', 'Prebuilt'],
['/Laptops/backlight-methods/manual', 'Manual'],
]
},
['/Laptops/trackpad', 'Fixing Trackpad'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Laptops/trackpad-methods/prebuilt', 'Prebuilt'],
['/Laptops/trackpad-methods/manual', 'Manual'],
]
},
['/Laptops/laptop-disable', 'Disabling laptop dGPUs'],
]
},
{
title: 'Universal',
collapsable: false,
sidebarDepth: 0,
children: [
['/Universal/ec-fix', 'Embedded Controller'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/ec-methods/prebuilt', 'Prebuilt'],
['/Universal/ec-methods/ssdttime', 'SSDTTime'],
['/Universal/ec-methods/manual', 'Manual'],
]
},
['/Universal/plug', 'CPU Power Management'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/plug-methods/prebuilt', 'Prebuilt'],
['/Universal/plug-methods/ssdttime', 'SSDTTime'],
['/Universal/plug-methods/manual', 'Manual'],
]
},
['/Universal/awac', 'AWAC vs RTC'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/awac-methods/prebuilt', 'Prebuilt'],
['/Universal/awac-methods/manual', 'Manual'],
]
},
['/Universal/nvram', 'NVRAM PMC'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/nvram-methods/prebuilt', 'Prebuilt'],
['/Universal/nvram-methods/manual', 'Manual'],
]
},
['/Universal/rhub', 'USB RHUB'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/rhub-methods/prebuilt', 'Prebuilt'],
['/Universal/rhub-methods/manual', 'Manual'],
]
},
['/Universal/smbus', 'Fixing SMBus Support'],
{
title: 'Methods',
collapsable: true,
sidebarDepth: 2,
children: [
['/Universal/smbus-methods/manual', 'Manual'],
]
},
['/Universal/irq', 'IRQ Fix'],
['/Universal/spoof', 'GPU Spoof'],
]
},
{
title: 'Cleanup',
collapsable: false,
sidebarDepth: 1,
children: [
['cleanup', 'Cleanup'],
]
},
{
title: 'Misc',
collapsable: false,
sidebarDepth: 1,
children: [
['troubleshooting', 'Troubleshooting'],
['CONTRIBUTING', 'Contributing'],
]
},
],
},
/**
* Apply plugins，ref：https://v1.vuepress.vuejs.org/zh/plugin/
*/
plugins: [
'@vuepress/plugin-back-to-top',
'vuepress-plugin-smooth-scroll',
['vuepress-plugin-medium-zoom',
{
selector: "img",
options: {
background: 'var(--bodyBgColor)'
}
}],
]
}

14
.vuepress/enhanceApp.js Executable file
View File

@@ -0,0 +1,14 @@
/**
* Client app enhancement file.
*
* https://v1.vuepress.vuejs.org/guide/basic-config.html#app-level-enhancements
*/
export default ({
Vue, // the version of Vue being used in the VuePress app
options, // the options for the root Vue instance
router, // the router instance for the app
siteData // site metadata
}) => {
// ...apply enhancements for the site.
}

BIN
.vuepress/public/acpi-logo.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 118 KiB

BIN
.vuepress/public/apple-touch-icon-precomposed-152.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 118 KiB

BIN
.vuepress/public/dortania-logo-clear.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 54 KiB

BIN
.vuepress/public/favicon.ico Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 118 KiB

BIN
.vuepress/public/homepage.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 118 KiB

70
.vuepress/styles/index.styl Executable file
View File

@@ -0,0 +1,70 @@
/**
* Custom Styles here.
*
* ref：https://v1.vuepress.vuejs.org/config/#index-styl
*/
[data-theme='light']
--sideBgColor $sideBgColor
[data-theme='dark']
--sideBgColor $sideBgColorDark
--bgColor $bgColor
.home .hero img
max-width 450px!important
// [data-theme='light']
// display none
// .home .hero img
// max-width 450px!important
/**
html
body
background-color var(--bgColor)
.theme-default-content:not(.custom)
max-width 1000px
.navbar
.links
background-color var(--navBgColorDark)!important
.navbar
filter: drop-shadow(0px 1px 1px var(--bgColor));
*/
.navbar
filter: drop-shadow(0px 1px 1px var(--bgColor));
.sidebar
background-color var(--sideBgColor)
div[class*="language-"]
pre, pre[class*="language-"]
margin-top 0
html {
overflow: scroll;
}
::-webkit-scrollbar {
width: 0px;
background: transparent; /* make scrollbar transparent */
}
tr
&:nth-child(1n)
background-color var(--bodyBgColor)
&:nth-child(2n)
background-color var(--sideBgColor)
.dropdown-wrapper .nav-dropdown
border: 1px solid var(--sideBgColor)!important
background-color var(--sideBgColor)!important
box-shadow: 0px 0px 2px var(--bodyBgColor)
right: -12%!important

40
.vuepress/styles/palette.styl Executable file
View File

@@ -0,0 +1,40 @@
/**
* Custom palette here.
*
* ref：https://v1.vuepress.vuejs.org/zh/config/#palette-styl
*/
$bodyFontSize = 16px
$fallbackTheme = 'dark'
// Light Theme
$accentColor = #00bfff
$textColor = #2c3e50
$bodyBgColor = #fff
$sideBgColor = #fff
$badgeTipColor = #e3f8ff
// Dark Theme
$accentColorDark = #30BCD5
$textColorDark = #ccc
$bodyBgColorDark = #2d3033
$sideBgColorDark = #363b40
$badgeTipColorDark = #023e52
/**
//$textColor = #2c3e50
$borderColor = #363b40
//$borderColor = #eaecef
$codeBgColor = #282c34
$bgColor = #2d3033
$navBgColor = #363b40
$bgColorDark = #2d3033
$navBgColorDark = #363b40
$sideBgColorDark = #363b40
*/
$bgColor = #111112

4
Desktops/desktop-disable.md
View File

@@ -25,9 +25,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" * Under the Details Tab, search for "Location Paths"
* Note some GPUs may be hiding under "BIOS device name" * 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: The second "ACPI" is what we care about:

8
Laptops/backlight-methods/manual.md
View File

@@ -11,13 +11,13 @@ For this guide, we're gonna assume Windows is already on this laptop, as otherwi
Now open DeviceManager, and head to the following: Now open DeviceManager, and head to the following:
```text ```
Device Manager -> Display Adapters -> Properties -> Details > BIOS device name Device Manager -> Display Adapters -> Properties -> Details > BIOS device name
``` ```
* Note some GPU ACPI pathing may be hiding under "BIOS device name" * Note some GPU ACPI pathing may be hiding under "BIOS device name"
![Credit to 1Revenger1 for the image](/images/Laptops/backlight-md/devicemanager.png) ![Credit to 1Revenger1 for the image](../../images/Laptops/backlight-md/devicemanager.png)
From the above example, we can see our display is hooked up to `PCI0.GFX0` From the above example, we can see our display is hooked up to `PCI0.GFX0`
@@ -41,7 +41,7 @@ Scope (_SB.PCI0.GFX0) <- Rename this
Device(_SB.PCI0.GFX0.PNLF) <- Rename this Device(_SB.PCI0.GFX0.PNLF) <- Rename this
``` ```
![](/images/Laptops/backlight-md/ssdt-before.png) ![](../../images/Laptops/backlight-md/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this: Following the example pathing we found, the SSDT should look something like this:
@@ -55,7 +55,7 @@ Scope (_SB.PCI0.GPU0) <- Renamed
Device(_SB.PCI0.GPU0.PNLF) <- Renamed Device(_SB.PCI0.GPU0.PNLF) <- Renamed
``` ```
![](/images/Laptops/backlight-md/ssdt-after.png) ![](../../images/Laptops/backlight-md/ssdt-after.png)
## Compiling the SSDT ## Compiling the SSDT

16
Laptops/laptop-disable.md
View File

@@ -24,7 +24,7 @@ To start, grab [SSDT-dGPU-Off.dsl](https://github.com/dortania/Getting-Started-W
Next we need to get on Windows, and head to the following: Next we need to get on Windows, and head to the following:
```text ```
Device Manager -> Display Adapters -> dGPU -> Properties -> Details > BIOS device name Device Manager -> Display Adapters -> dGPU -> Properties -> Details > BIOS device name
``` ```
@@ -35,15 +35,15 @@ This should provided you with an ACPI path for your dGPU, most commonly:
* Nvidia dGPU: `\_SB.PCI0.PEG0.PEGP` * Nvidia dGPU: `\_SB.PCI0.PEG0.PEGP`
* AMD dGPU: `\_SB.PCI0.PEGP.DGFX` * AMD dGPU: `\_SB.PCI0.PEGP.DGFX`
![Credit to 1Revenger1 for the image](/images/Desktops/nvidia.png) ![Credit to 1Revenger1 for the image](../images/Desktops/nvidia.png)
Now with that, we'll need to change the ACPI path in the SSDT. Main sections: Now with that, we'll need to change the ACPI path in the SSDT. Main sections:
```text ```
External(_SB.PCI0.PEG0.PEGP._OFF, MethodObj) External(_SB.PCI0.PEG0.PEGP._OFF, MethodObj)
``` ```
```text ```
If (CondRefOf(\_SB.PCI0.PEG0.PEGP._OFF)) { \_SB.PCI0.PEG0.PEGP._OFF() } If (CondRefOf(\_SB.PCI0.PEG0.PEGP._OFF)) { \_SB.PCI0.PEG0.PEGP._OFF() }
``` ```
@@ -59,7 +59,7 @@ To start, grab [SSDT-NoHybGfx.dsl](https://github.com/dortania/Getting-Started-W
Next we need to get on Windows, and head to the following: Next we need to get on Windows, and head to the following:
```text ```
Device Manager -> Display Adapters -> dGPU -> Properties -> Details > BIOS device name Device Manager -> Display Adapters -> dGPU -> Properties -> Details > BIOS device name
``` ```
@@ -70,12 +70,12 @@ This should provided you with an ACPI path for your dGPU, most commonly:
Now with that, we'll need to change the ACPI path in the SSDT. Main sections: Now with that, we'll need to change the ACPI path in the SSDT. Main sections:
```text ```
External (_SB_.PCI0.PEG0.PEGP._DSM, MethodObj) // dGPU ACPI Path External (_SB_.PCI0.PEG0.PEGP._DSM, MethodObj) // dGPU ACPI Path
External (_SB_.PCI0.PEG0.PEGP._PS3, MethodObj) // dGPU ACPI Path External (_SB_.PCI0.PEG0.PEGP._PS3, MethodObj) // dGPU ACPI Path
``` ```
```text ```
If ((CondRefOf (\_SB.PCI0.PEG0.PEGP._DSM) && CondRefOf (\_SB.PCI0.PEG0.PEGP._PS3))) If ((CondRefOf (\_SB.PCI0.PEG0.PEGP._DSM) && CondRefOf (\_SB.PCI0.PEG0.PEGP._PS3)))
``` ```
@@ -84,7 +84,7 @@ If ((CondRefOf (\_SB.PCI0.PEG0.PEGP._DSM) && CondRefOf (\_SB.PCI0.PEG0.PEGP._PS3
\_SB.PCI0.PEG0.PEGP._DSM (ToUUID ("a486d8f8-0bda-471b-a72b-6042a6b5bee0"), 0x0100, 0x1A, Buffer (0x04) \_SB.PCI0.PEG0.PEGP._DSM (ToUUID ("a486d8f8-0bda-471b-a72b-6042a6b5bee0"), 0x0100, 0x1A, Buffer (0x04)
``` ```
```text ```
// Card Off // Card Off
\_SB.PCI0.PEG0.PEGP._PS3 () \_SB.PCI0.PEG0.PEGP._PS3 ()
``` ```

8
Laptops/trackpad-methods/manual.md
View File

@@ -12,7 +12,7 @@ Finding the ACPI pathing is quite easy actually, first open your decompiled DSDT
Next search for `Device (GPI0)`. Should give you a result similar to this: Next search for `Device (GPI0)`. Should give you a result similar to this:
![](/images/Laptops/trackpad-md/gpi0.png) ![](../../images/Laptops/trackpad-md/gpi0.png)
What we care about from this is the `_STA` method: What we care about from this is the `_STA` method:
@@ -34,7 +34,7 @@ What we want is for this to always return `0x0F` when booting macOS, so we want
Here's some more examples: Here's some more examples:
![](/images/Laptops/trackpad-md/gpi0-2.png) ![](../../images/Laptops/trackpad-md/gpi0-2.png)
With this example, we can see that we need both `SBRG` and `GPEN` to return `One`. If only one is present, it'll create some issues so in our SSDT we'll want to have both of them return `One`: With this example, we can see that we need both `SBRG` and `GPEN` to return `One`. If only one is present, it'll create some issues so in our SSDT we'll want to have both of them return `One`:
@@ -57,7 +57,7 @@ If (_OSI ("Darwin"))
} }
``` ```
![](/images/Laptops/trackpad-md/ssdt-before.png) ![](../../images/Laptops/trackpad-md/ssdt-before.png)
Following the example pathing we found, the SSDT should look something like this: Following the example pathing we found, the SSDT should look something like this:
@@ -70,7 +70,7 @@ If (_OSI ("Darwin"))
} }
``` ```
![](/images/Laptops/trackpad-md/ssdt-after.png) ![](../../images/Laptops/trackpad-md/ssdt-after.png)
## Compiling the SSDT ## Compiling the SSDT

10
Manual/compile.md
View File

@@ -12,23 +12,23 @@ So compiling DSDTs and SSDTs are quite easy with macOS, all you need is [MaciASL
For those who prefer the command line, grab [iasl-stable](https://github.com/acidanthera/MaciASL/blob/master/Dist/iasl-stable) and run the following: For those who prefer the command line, grab [iasl-stable](https://github.com/acidanthera/MaciASL/blob/master/Dist/iasl-stable) and run the following:
```text ```
path/to/iasl.exe path/to/DSDT.aml path/to/iasl.exe path/to/DSDT.aml
``` ```
* If compiled .aml file is provided, a decompiled .dsl file will be given and vice versa. * If compiled .aml file is provided, a decompiled .dsl file will be given and vice versa.
![](/images/Manual/compile-md/macos-compile.png) ![](../images/Manual/compile-md/macos-compile.png)
## Windows ## Windows
Compiling and decompiling on windows is fairly simple though, you will need [iasl.exe](https://acpica.org/downloads/binary-tools) and Command Prompt: Compiling and decompiling on windows is fairly simple though, you will need [iasl.exe](https://acpica.org/downloads/binary-tools) and Command Prompt:
```text ```
path/to/iasl.exe path/to/DSDT.aml path/to/iasl.exe path/to/DSDT.aml
``` ```
![](/images/Manual/compile-md/windows-compile.png) ![](../images/Manual/compile-md/windows-compile.png)
* If compiled .aml file is provided, a decompiled .dsl file will be given and vice versa. * If compiled .aml file is provided, a decompiled .dsl file will be given and vice versa.
@@ -36,7 +36,7 @@ path/to/iasl.exe path/to/DSDT.aml
Compiling and decompiling with Linux is just as simple, you will need a copy of iasl. You can get it here ([iasl](http://amdosx.kellynet.nl/iasl.zip)) or through the `iasl` package in your package manager. iasl can be used as such: Compiling and decompiling with Linux is just as simple, you will need a copy of iasl. You can get it here ([iasl](http://amdosx.kellynet.nl/iasl.zip)) or through the `iasl` package in your package manager. iasl can be used as such:
```text ```
path/to/iasl path/to/DSDT.aml path/to/iasl path/to/DSDT.aml
``` ```

6
Manual/dump.md
View File

@@ -54,9 +54,9 @@ For the latter, you just need to replace the following files with [DEBUG version
* EFI/OC/ * EFI/OC/
* `OpenCore.efi` * `OpenCore.efi`
For the former, you can actually skip the ACPI section, return to the OpenCore guide([Desktop](https://dortania.github.io/OpenCore-Desktop-Guide/), [Laptop](https://dortania.github.io/vanilla-laptop-guide/)) and finish making the USB. Once booted to the picker, you can shut off the PC and check your USB: For the former, you can actually skip the ACPI section, return to the [OpenCore guide](https://dortania.github.io/OpenCore-Desktop-Guide/) and finish making the USB. Once booted to the picker, you can shut off the PC and check your USB:
![](/images/Manual/dump-md/sysreport.png) ![](../images/Manual/dump-md/sysreport.png)
And voila! You have a DSDT! Now you can continue on with making SSDTs And voila! You have a DSDT! Now you can continue on with making SSDTs
@@ -66,7 +66,7 @@ For this, we'll want ti grab [`acpidump.efi`](https://github.com/dortania/OpenCo
If OpenCore is having issues running acpidump.efi from the boot picker, you can call it from the shell with [OpenShell](https://github.com/acidanthera/OpenCorePkg/releases)(reminder to add to both `EFI/OC/Tools` and in your config under `Misc -> Tools` ): If OpenCore is having issues running acpidump.efi from the boot picker, you can call it from the shell with [OpenShell](https://github.com/acidanthera/OpenCorePkg/releases)(reminder to add to both `EFI/OC/Tools` and in your config under `Misc -> Tools` ):
```text ```
shell> fs0: // replace with proper drive shell> fs0: // replace with proper drive
fs0:\> dir // to verify this is the right directory fs0:\> dir // to verify this is the right directory
Directory of fs0:\ Directory of fs0:\

2
README.md
View File

@@ -1,6 +1,6 @@
# Getting started with ACPI # Getting started with ACPI
<img src="images/README-md/acpi-logo.png" width="512"> <img src="acpi-logo.png" width="512">
## A quick explainer on ACPI ## A quick explainer on ACPI

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: 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: 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`: 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) 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 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 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 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: 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 Scope (_SB.PCI0.LPC) <- Renamed
``` ```
![](/images/Universal/awac-md/ssdt-after.png) ![](../../images/Universal/awac-md/ssdt-after.png)
### Compiling the SSDT ### 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: 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: 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: 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` 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 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: 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 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: Example of an EC with STA already:
![Credit to rottenpants466](/images/Desktops/sta.png) ![Credit to rottenpants466](../../images/Desktops/sta.png)
## Compiling the SSDT ## 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 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) 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 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: 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 Scope (_SB.PCI0.LPC) <- Renamed
``` ```
![](/images/Universal/nvram-md/ssdt-after.png) ![](../../images/Universal/nvram-md/ssdt-after.png)
## Compiling the SSDT ## 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: 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. 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: 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`: 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) 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: 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 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`: 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: 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 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 ## 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: 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: 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 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: 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 Scope (_SB.PCI0.XHC1.RHUB) <- Renamed
``` ```
![](/images/Universal/rhub-md/ssdt-after.png) ![](../../images/Universal/rhub-md/ssdt-after.png)
## Compiling the SSDT ## 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: 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 `@...` 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: 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: 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**: **Before**:
```text ```
External (_SB_.PCI0, DeviceObj) <- Rename this External (_SB_.PCI0, DeviceObj) <- Rename this
External (_SB_.PCI0.SBUS.BUS0, 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 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: Following the example SMBus pathing we found, the SSDT should look something like this:
**After**: **After**:
```text ```
External (_SB_.PC00, DeviceObj) <- Renamed External (_SB_.PC00, DeviceObj) <- Renamed
External (_SB_.PC00.SMBS.BUS0, DeviceObj) <- Renamed External (_SB_.PC00.SMBS.BUS0, DeviceObj) <- Renamed
@@ -88,7 +88,7 @@ Scope (_SB.PC00) <- Renamed
Device (_SB.PC00.SMBS.BUS0) <- Renamed Device (_SB.PC00.SMBS.BUS0) <- Renamed
``` ```
![](/images/Universal/smbus-md/after-rename.png) ![](../../images/Universal/smbus-md/after-rename.png)
# Compiling the SSDT # 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" 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" * Under the Details Tab, search for "Location Paths"
* Note some GPUs may be hiding under "BIOS device name" * 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: The second "ACPI" is what we care about:

3
cleanup.md
View File

@@ -11,8 +11,7 @@ You can save yourself some work with the config.plist by running Cmd/Ctrl+R in P
For those who do not yet have a config.plist, you'll want to next head back to your respective OpenCore guides and create the config.plist: For those who do not yet have a config.plist, you'll want to next head back to your respective OpenCore guides and create the config.plist:
* [OpenCore Desktop guide](https://dortania.github.io/OpenCore-Desktop-Guide/) * [OpenCore Install guide](https://dortania.github.io/OpenCore-Desktop-Guide/)
* [OpenCore Laptop Guide](https://dortania.github.io/vanilla-laptop-guide/)
Users of `FixHPET` will also need to merge oc_patches.plist into their config.plist Users of `FixHPET` will also need to merge oc_patches.plist into their config.plist

10693
package-lock.json generated Normal file
View File

File diff suppressed because it is too large Load Diff

29
package.json Normal file
View File

@@ -0,0 +1,29 @@
{
"name": "OpenCore-Desktop-Guide",
"version": "0.0.1",
"description": "",
"main": "index.js",
"authors": {
"name": "",
"email": ""
},
"repository": "/OpenCore-Desktop-Guide",
"scripts": {
"dev": "vuepress dev",
"build": "vuepress build"
},
"license": "MIT",
"devDependencies": {
"@vuepress/plugin-back-to-top": "^1.5.2",
"vuepress": "^1.5.2",
"vuepress-plugin-medium-zoom": "^1.1.8",
"vuepress-plugin-zooming": "^1.1.7",
"vuepress-theme-book": "0.0.3",
"vuepress-theme-dark-new": "^0.1.2",
"vuepress-theme-succinct": "^1.5.2"
},
"dependencies": {
"markdown-it-multimd-table": "^4.0.3",
"vuepress-theme-yuu": "^2.3.0"
}
}

5
ssdt-methods/ssdt-easy.md
View File

@@ -33,7 +33,7 @@ For users who don't have all the options available to them in SSDTTime, you can
Run the `SSDTTime.bat` file as Admin on the target machine and you should see something like this: Run the `SSDTTime.bat` file as Admin on the target machine and you should see something like this:
![](/images/ssdt-easy-md/ssdttime.png) ![](../images/ssdt-easy-md/ssdttime.png)
What are all these options?: What are all these options?:
@@ -65,8 +65,7 @@ Reminder that Cmd/Crtl+R with ProperTree pointed at your OC folder will add all
For those who do not yet have a config.plist, you'll want to next head back to your respective OpenCore guides and create the config.plist: For those who do not yet have a config.plist, you'll want to next head back to your respective OpenCore guides and create the config.plist:
* [OpenCore Desktop guide](https://dortania.github.io/OpenCore-Desktop-Guide/) * [OpenCore Install guide](https://dortania.github.io/OpenCore-Desktop-Guide/)
* [OpenCore Laptop Guide](https://dortania.github.io/vanilla-laptop-guide/)
Users of `FixHPET` will also need to merge oc_patches.plist into their config.plist Users of `FixHPET` will also need to merge oc_patches.plist into their config.plist

14
troubleshooting.md
View File

@@ -21,7 +21,7 @@ Grab [OpenShell](https://github.com/acidanthera/OpenCorePkg/releases) and add it
Next, call upon OpenCore shell and enter the following: Next, call upon OpenCore shell and enter the following:
```text ```
shell> fs0: //replace with proper drive shell> fs0: //replace with proper drive
fs0:\> dir //to verify this is the right directory fs0:\> dir //to verify this is the right directory
@@ -39,21 +39,21 @@ fs0:\EFI\OC\Tools> acpidump.efi -b -n DSDT -z
If you try to decompile your DSDT and get an error similar to this: If you try to decompile your DSDT and get an error similar to this:
```text ```
iASL Warning: There were 19 external control methods found during disassembly, but only 0 were resolved (19 unresolved) iASL Warning: There were 19 external control methods found during disassembly, but only 0 were resolved (19 unresolved)
``` ```
This happens when one ACPI table requires the rest for proper referencing, it does not accept the creation of DSDTs as we're only using it for creating a select few SSDTs. For those who are worried, you can run the following: This happens when one ACPI table requires the rest for proper referencing, it does not accept the creation of DSDTs as we're only using it for creating a select few SSDTs. For those who are worried, you can run the following:
```text ```
iasl * [insert all ACPI files here] iasl * [insert all ACPI files here]
``` ```
## Decompiling Error ## Decompiling Error
![](/images/troubleshooting-md/decompile-error.png) ![](../images/troubleshooting-md/decompile-error.png)
```text ```
Loading Acpi table from file iASLAwjHrs.aml Loading Acpi table from file iASLAwjHrs.aml
Acpi table [DSDT] successfully installed and loaded Acpi table [DSDT] successfully installed and loaded
Pass 1 parse of [DSDT] Pass 1 parse of [DSDT]
@@ -63,12 +63,12 @@ This is a common error on DSDTs that have methods that aren't supported by maciA
## Invalid character (0x3D), expecting ASL keyword or name ## Invalid character (0x3D), expecting ASL keyword or name
![](/images/troubleshooting-md/invalid-parse.png) ![](../images/troubleshooting-md/invalid-parse.png)
Similar to the above error, you're running an outdated copy of maciASL. Make sure you're using the latest from Acidanthera's repo: [maciASL](https://github.com/acidanthera/MaciASL/releases) Similar to the above error, you're running an outdated copy of maciASL. Make sure you're using the latest from Acidanthera's repo: [maciASL](https://github.com/acidanthera/MaciASL/releases)
## Syntax error, unexpected PARSEOP_ONE, expecting '(' ## Syntax error, unexpected PARSEOP_ONE, expecting '('
![](/images/troubleshooting-md/invalid-parse.png) ![](../images/troubleshooting-md/invalid-parse.png)
Similar to the above 2 errors, you're running an outdated copy of maciASL. Make sure you're using the latest from Acidanthera's repo: [maciASL](https://github.com/acidanthera/MaciASL/releases) Similar to the above 2 errors, you're running an outdated copy of maciASL. Make sure you're using the latest from Acidanthera's repo: [maciASL](https://github.com/acidanthera/MaciASL/releases)