[Sticky] [GUIDE] DSDT override eGPU error 12 fix  

Page 5 / 5 Prev
  RSS

(@chanathip_kittipatchara)
New Member
Joined: 7 months  ago
Posts: 1
April 22, 2018 8:00 am  

I use Rx560 and now I still stuck with DSDT Pls Help me.
Check My DSDT
My DSDT File. Original
https://drive.google.com/drive/folders/16lFvkA_9ZLHenpKXgaXy7-p71EYzoUoq?usp=sharing

I waiting to you.


ReplyQuote
(@felix920506)
Active Member
Joined: 6 months  ago
Posts: 5
May 27, 2018 3:30 pm  

I followed the guide on the forum and when I try to compile the code it just spits out:
Syntax error. Unexpected PARSEOP_NOTIFY. Expecting ',' or ')'
Plz Give me some help
EDIT:
original DSDT file  https://drive.google.com/file/d/1xwYexZoL73H55xbu63X9TJcyTQgHX2Qp/view?usp=sharing


ReplyQuote
DentalStone
(@dentalstone)
New Member
Joined: 5 months  ago
Posts: 1
June 15, 2018 10:10 am  

Hi there Nando! I have recently ventured into the world of eGPUs and I was wondering if you could compile a DSDT override for my PC, as I am no good with hex editing and whatever else this process entails.


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years  ago
Posts: 1804
June 15, 2018 11:07 am  

@dentalstone , sure, one-on-one assistance as you request can be provided on a professional level. My contact details can be found at https://egpu.io/Setup1x .

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years  ago
Posts: 1804
July 31, 2018 4:10 am  

2018 13" MBP's factory DSDT no longer has 'large memory' in Windows like a 2017 13" MBP has

Confirmed with an offline user who had error 12 in Windows. This was fixed by disabling secure boot followed by a 'load' of the following DSDT override:

http://www.mediafire.com/file/p2zb5g9hxhia5p4/Apple_2018_mid-13in-Macbook-Pro-TouchBar_zeren.zip/file

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


theitsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1485
July 31, 2018 6:16 am  

@nando4 Disappointing news. I'm guessing the most effective DSDT Override approach would be:

  • Trim/minimize Clover functionalities to only execute DSDT overrides
  • Possibly automate patched DSDT aml generation, at least for Macs
  • Use an external boot disk and never install on primary internal disk
  • Ensure Clover is not writing to the flashed EFI firmware (which should be left alone) on Mac

 

This is a similar approach to @goalque's work with automate-eGPU EFI. In my opinion, if the above conditions are met, bricking a Mac would never be a problem. Hopefully we see a factory "Large Memory" space on the new Macs with an update, but at the moment it seems DSDT in-memory overrides have use even on the latest hardware.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
(@yukinsnow)
New Member
Joined: 4 months  ago
Posts: 3
July 31, 2018 6:47 am  

Thanks to @nando4 !!Soloving my problem!!


- there is no 'large memory' area in a 2018 13" MBP and you had error 12 on your eGPU
- you applied this registry override DSDT override, got 'large memory' and fixed error 12 on your eGPU

Another improtant thing, If you wang to use this method or into rEFInd, you should turn 'secure boot' off first. iMac and 2018 later MBP need this step.
https://support.apple.com/en-us/HT208330


nando4 liked
ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years  ago
Posts: 1804
July 31, 2018 7:05 am  

@mac_editor, sure, loading the DSDT override via a Goalque modified Clover or using the stock Clover would eliminate test signing mode. If an external drive reduces bricking risk then it's good to use.

As for the Apple firmware, the code added to the 2017 13" MBP for large memory is present in the 2018 13". It's just that it's broken such that there is no large memory shown in View -> Resources -> By Type

Indeed, if Apple monitors these threads then please reinstate 'large memory' via a fixed DSDT in a future firmware update.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1485
July 31, 2018 7:16 am  
Posted by: nando4

As for the Apple firmware, the code added to the 2017 13" MBP for large memory is present in the 2018 13". It's just that it's broken such that there is no large memory shown in View -> Resources -> By Type

Eyebrow-raising comment. So the code is there, but not working as intended, or a bug? Then I'm guessing that the user fixed error 12 by fixing that code snippet (or just redid that section per the awesome DSDT guide). One thing you may add on there to it is to promote use of external drive for Clover on Macs. Should at least keep internal drive partitions clean. I read elsewhere on the forum that Mojave was also breaking "Large Memory" on Macs. Will be interesting to see how things pan out until release.

Also, @nando4, please forgive my ignorance on this one :), but your guide mentions that macOS and Linux ignore the root bridge 32-bit limitations, and Windows sticks by it. Have you ever investigated anything on Windows-end to ignore the limit instead of updating the limit? Just a thought.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years  ago
Posts: 1804
July 31, 2018 7:47 am  

@mac_editor, goalque was playing with Clover and so has a better grasp where UEFI writes on Macbooks.  Does an external drive help protect against Clover bricking the system? My Dell writes UEFI variables to NVRAM. If bork the system I just pull the battery and real time clock battery to reset the factory defaults.

As for Windows, it strictly honors the ACPI CRS definition set by the manufacturer for the system in defining PCIe allocation boundaries. Yes, Microsoft could help with error 12 by ignoring CRS for 64-bit PCIe BARs. Then we wouldn't need the DSDT override to extend CRS out into 64-bit space.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2015 15" Dell Precision 7510 M1000M + macOS 10.14 & Win10


mac_editor liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1485
July 31, 2018 8:07 am  

@nando4 My understanding of EFI is poor/limited at best. If Clover writes to NVRAM/SMC on Mac, both can be reset easily by the user. I, however, do not have evidence for myself as I have never bricked my system using just NVRAM writes and recovered it. What I do know is that Clover/automate-eGPU EFI can be installed on the internal, hidden EFI disk - I do not recommend this at all because why modify a perfectly fine partition for a bit of convenience at high risk? At least one can ensure integrity of the internal drives by not installing there.

Secondly, I suppose the definition of bricking needs some clarification - I assume bricking is when a Mac cannot boot into any system whatsoever - the only reason that may happen (according to me), besides some odd combo of NVRAM/SMC writes (which can be reset), would be if the flashed EFI software has been incorrectly modified (like for instance it may not compile properly as C code). If Clover is writing on that chip, then installing it anywhere = same risks. If not, then I would deem installing on external USB stick as better. @mikeal, I believe, uses this method for Clover.

Fact is, I just don't have that much insight on the matter. These are just some inferred logical conclusions that I came to. So the best bet is to vet Clover for the Mac, and until then, get as much theoretical safety by installing on external drive I suppose.

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


nando4 liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1298
July 31, 2018 8:46 am  

Bricking means the system doesn't react to any key combinations on startup and the screen stays black. This is possible by writing invalid/corrupted NVRAM/SMC/ACPI data to non-volatile memory areas that the firmware is unable to interpret, so users should be extra careful on what they are doing with Clover. I don't think that installing on the external USB would minimize these risks.

By default, automate-eGPU EFI doesn't call any SMC interfaces, doesn't create custom nvram values, doesn't try to access memory directly (leads to system freeze with newer TB3 Macs), and leaves SMBIOS tables untouched. Windows is not supported, yet.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


nando4 liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years  ago
Posts: 3081
July 31, 2018 1:13 pm  

@nando4 This may be due to a firmware change following system software update. The 2018 13" MacBook Pro I'm testing has the original firmware and I see Large Memory in Windows. Several members [whiskey_1130 & Ningauble77] have reported issues with error 12 when they upgraded to Mojave beta. Once exchanged for new units, all was well.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

82 external GPU build guides


ReplyQuote
Ningauble77
(@ningauble77)
Trusted Member
Joined: 10 months  ago
Posts: 83
July 31, 2018 1:42 pm  

In addition, after installing the Mojave boot rom, there were multiple "unknown devices" in the Device manager, one with an ACPI reference, so I am assuming the removal of the Large Memory entry is a bug, and not by design.  I would hope it returns, fully functional in a future Mojave beta, for the present for those who have updated the Boot Rom, this workaround should be a lifesend tho.


theitsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years  ago
Posts: 1485
July 31, 2018 2:17 pm  

@goalque Thank you so much for the clarifications - much appreciated :-). What are these "non-volatile" firmware areas that you are referring to specifically?

purge-wrangler.shpurge-nvda.shset-eGPU.sh
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
----
Multiple Build Guides


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years  ago
Posts: 1298
July 31, 2018 3:41 pm  
Posted by: mac_editor

@goalque Thank you so much for the clarifications - much appreciated :-). What are these "non-volatile" firmware areas that you are referring to specifically?

I explained about it here:

https://egpu.io/forums/mac-setup/help-apple-dev-kit-egpu-windows-10-1080ti-high-sierra/paged/2/#post-13601

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/2/#post-37896

Trammel Hudson, the creator of Thunderstrike, wrote:

"There is a different region in the flashrom (around offset 0x670000) that OSX uses to store the nvram data in an EFI firmware volume and is also rewritten on most boots."

https://www.mail-archive.com/[email protected]/msg09248.html

If this memory area cannot be rewritten/read in SEC/Pre-EFI/DXE stages, due to corrupted non-volatile data, the Mac doesn't show any sign of life when you press the power button.

Some Macs have a replaceable battery for CMOS chip (such as a 2014 Mac mini) but some have a capacitor to retain data across power cycles. In the worst case, you have to replace the logic board.

automate-eGPU EFIapple_set_os.efi
--
late-2016 13" Macbook Pro nTB + [email protected] (Netstor HL23T) + macOS & Win10
late-2016 13" Macbook Pro nTB + GTX980/[email protected] (Netstor HL23T) + macOS10.13 & Win10


mac_editor and theitsage liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years  ago
Posts: 3081
August 1, 2018 8:26 pm  

Here are screen captures from Device Manger of a 2018 13" MacBook Pro. With its original firmware, Windows in Boot Camp has Large Memory.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

82 external GPU build guides


nando4 liked
ReplyQuote
RabMoghal
(@rabmoghal)
New Member
Joined: 3 months  ago
Posts: 1
August 27, 2018 7:37 am  

Laptop: HP ProBook 6550b
OS: Windows 10, Intel I5, 4gb Ram
Egpu: Gigabyte AMD Radeon HD HD 7870
Method: Dock & Express Card

Hello there, this is my first time doing just about every instruction listed here, first time I tried the intel method, and after  turning test signing on, I restarted to find the ACPI BIOS ERROR on start up. I entered the CMD mode on start up and turned test signing off, but alas, I still had to do a re-install of windows to get back up and running.

This is attempt 2 now, deleted everything and did a fresh install of all the files, to try the windows method of compiling the dsdt-modified.asl file. I'm now getting the following error, which I can't find any advice on in the forum. 

1784:                   })
                            ^***
dsdt-modfied.asl(1794): error: Buffer has too many initializers

Can anyone give me an idea of what to do next?

Many Thanks.
Rab.


ReplyQuote
mstapha999
(@mstapha999)
New Member
Joined: 4 months  ago
Posts: 3
August 29, 2018 11:56 am  

Hello, 

i have an egpu with code 12 error, and now i'm doing some DSDT overriding, but i faced 2 errors in my way ( see the picture ) i've tried everything, but seems i'm just destroying the whole file. bytheway this is my dsdt content :
http://www.mediafire.com/file/3nkhgv91we81vdx/dsdt.rar/file
the file that i'm trying to patch is named : dsdt-modified.dsl
please help me guys, i'd really appreciate your help. Thanks 

This is the error am getting :


ReplyQuote
(@iman_rahmat)
New Member
Joined: 2 months  ago
Posts: 1
September 11, 2018 5:02 am  

Dear all,

i build my EGPU with this spesification :

Laptop HP Elitebook 2570P i7-3520M

Bios version : 68ISB Ver. F.72 release 30 july 2018
Adapter : EXP GDC V.8.5C
Power : PSU ATX Simbadda 500W
GPU : ATI Radeon HD6570
RAM 8GB
i Use HDD Docking to expand my storage in CDROOM slot.

at the first hardware not found in device manager, and i have done DSDT Override, large memory found in my device manager and then my hardware was found as AMD Radeon HD 6570 , but error 12 found.. any suggestion to solve my problem ?


ReplyQuote
(@sen_pt_sen_boat)
New Member
Joined: 3 weeks  ago
Posts: 1
October 23, 2018 4:12 pm  

Hi guys,
I am new on this forum, so I wish  to seize the opportunity to salute all members, and also to give my thanks to nando !
After a long war with my HP 8470, I manage to create he DSDT registry override (took me some 4-5 tentative !)  and I got the "large memory";
Next, I manage to install the driver for my 960 GTX, and ONLY with the hot-plug the machine accepts the eGPU.
My problem now its with the system stability;
I get the eGPU usable even on laptop screen, not just on external monitor, however after 2-3 min I get "nvidia driver stop....etc" , driver error message ;
On NVidia driver page, even looking for old drivers, one can just scroll back to oct . 2017;

Problem is, for me, the new drivers crashes, and the oldest I found its no better.

Anybody can help me to point me out what driver I should try - I mean a stable one ?
Or, in other order, its my problem related only to the driver - or should I change something else ?

Any help will be very much appreciated !


ReplyQuote
Page 5 / 5 Prev