100% Success with the Acer Aspire E5-575G-53VG and Sierra 10.12.5

[RehabMan]

What?? Impossible! xD . (see attached)

It is RTF, not text:

{\rtf1\ansi\ansicpg1252\cocoartf1504\cocoasubrtf830
{\fonttbl\f0\fmodern\fcharset0 CourierNewPSMT;}
{\colortbl;\red255\green255\blue255;\red16\green16\blue16;\red255\green255\blue255;}
{\*\expandedcolortbl;;\cssrgb\c7451\c7451\c7451;\cssrgb\c100000\c100000\c100000;}
\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\deftab720
\pard\pardeftab720\sl300\partightenfactor0

\f0\fs26\fsmilli13333 \cf2 \cb3 \expnd0\expndtw0\kerning0
\outl0\strokewidth0 \strokec2 External(MDBG, MethodObj, 1)\cb1 \
\cb3 External(_GPE.MMTB, MethodObj, 0)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECWT, MethodObj, 2)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECRD, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECMD, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.PEG0.PEGP.SGPO, MethodObj, 2)\cb1 \
\cb3 External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.SAT0.SDSM, MethodObj, 4)\cb1 \
\cb3 External(_GPE.VHOV, MethodObj, 3)\cb1 \
\cb3 External(_SB.PCI0.XHC.RHUB.TPLD, MethodObj, 2)}

Correct procedures for creating refs.txt are in the guide.
https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/

You clearly didn't use correct procedures...

 

[Feartech]

It's.... the same as the guide. >_>

View attachment 258132

this is yours:

{\rtf1\ansi\ansicpg1252\cocoartf1504\cocoasubrtf830
{\fonttbl\f0\fmodern\fcharset0 CourierNewPSMT;}
{\colortbl;\red255\green255\blue255;\red16\green16\blue16;\red255\green255\blue255;}
{\*\expandedcolortbl;;\cssrgb\c7451\c7451\c7451;\cssrgb\c100000\c100000\c100000;}
\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\deftab720
\pard\pardeftab720\sl300\partightenfactor0

\f0\fs26\fsmilli13333 \cf2 \cb3 \expnd0\expndtw0\kerning0
\outl0\strokewidth0 \strokec2 External(MDBG, MethodObj, 1)\cb1 \
\cb3 External(_GPE.MMTB, MethodObj, 0)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECWT, MethodObj, 2)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECRD, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.LPCB.H_EC.ECMD, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.PEG0.PEGP.SGPO, MethodObj, 2)\cb1 \
\cb3 External(_SB.PCI0.GFX0.DD02._BCM, MethodObj, 1)\cb1 \
\cb3 External(_SB.PCI0.SAT0.SDSM, MethodObj, 4)\cb1 \
\cb3 External(_GPE.VHOV, MethodObj, 3)\cb1 \
\cb3 External(_SB.PCI0.XHC.RHUB.TPLD, MethodObj, 2)}

 

[jackharvest]

The guide says its a handy way to create it, not the only way! Haha - I will use the handy way. . Thanks for the help! Every question I've had has been the same reason I missed math problems 20 years ago: Frack'n read the whole thing dangit.

 

[Feartech]

The guide says its a handy way to create it, not the only way! Haha - I will use the handy way. . Thanks for the help! Every question I've had has been the same reason I missed math problems 20 years ago: Frack'n read the whole thing dangit.

that is why it is called a guide, to guide you the way

 

[RehabMan]

The guide says its a handy way to create it, not the only way!

There are other ways...
But the way you chose (a rich text editor) is one of the wrong ways...

 

[jackharvest]

I love you guys! Ok, so, now I have NO errors, and 83 warnings, 93 remarks, and 175 optimizations. But who cares right! No errors! Now to apply appropriate patchwork...

There are other ways...
But the way you chose (a rich text editor) is one of the wrong ways...

PS: Textedit is crap. What should I be using instead? Textwrangler? Sublime 3?

 

[RehabMan]

PS: Textedit is crap. What should I be using instead? Textwrangler? Sublime 3?

TextEdit works fine if you set Preferences correctly.
And yes... there are lots of other text editors available. I use Xcode.

 

[jackharvest]

After disassembly we can proceed to patch the various files. In this example, we'll patch almost all the files.

For DSDT.dsl:
"Fix PARSEOP_ZERO Error" (be sure to uncommment the "more agressive" patches)
"Fix ADBG Error"
"Rename _DSM methods to XDSM"
"IRQ Fix"
"SMBUS Fix"
"OS Check Fix (Windows 8)"
"Add IMEI"
"RTC Fix"
"Fix _WAK Arg0 v2"
"Fix _WAK IAOE" (new patch)
"Rename GFX0 to IGPU"
"Rename B0D3 to HDAU" (new patch)
"ASUS N55SL/VivoBook"
"USB3 _PRW(0x6D) and Rename XHC to XHC1" (new patch)
"Audio Layout 12"

Are any of these specific to your Asus laptop you based the guide on (besides the Asus N55SL/VivoBook one)?

EDIT #1:

- the battery patch is specific to the target machine, in this case an Asus laptop

Never mind, this probably means its the only one. . Patch time!

EDIT #2:
Ok, all done! When I ran 'iasl *.dsl' to ensure there were no errors, everything passed except SSDT-4x.dsl had 32 errors. I didn't touch that file because

SSDT-2x, SSDT-3x, SSDT-4x are not included as they are dynamically loaded.

-- so I figured it wasn't necessary. Is this correct? Am I only copying the ones I patched into the EFI, or all of them?

EDIT #3:
Ok, I now have performed all patches across all DSDT and SSDT files (with the exception of "Asus N55SL/VivoBook", "USB3_~", and "Audio Layout 12", as they seemed device specific (plus my audio and usb's are all working). Running grep to find GFX0 references now gives me the following!:

grep -I GFX0 *.dsl

SSDT-4x.dsl: External (_SB_.PCI0.GFX0.DD02._BCM, MethodObj) // Imported: 1 Arguments

Yay! It only finds it in SSDT-4x.dsl, and this piece of crap doesn't compile anyway! I'm presuming I just omit this one due to my quote in "EDIT #2". Time to keep going in the guide with _OFF etc.

 

[jackharvest]

Well, I've modified the .dsl files until all instances of GFX0 were gone, as well as the other items in the guide. Here's my final .aml files, as well as the .dsl versions of the same thing (in case its easier to parse through that instead of the .aml files):

 

[RehabMan]

View attachment 258172

Well, I've modified the .dsl files until all instances of GFX0 were gone, as well as the other items in the guide. Here's my final .aml files, as well as the .dsl versions of the same thing (in case its easier to parse through that instead of the .aml files):

What are you trying to do?
What is the issue?
If you have an issue, you must describe it clearly and provide "Problem Reporting" files.