Setup & Software Discussions
[GUIDE] DSDT override eGPU error 12 fix
 

[GUIDE] DSDT override eGPU error 12 fix  

Page 5 / 6
  RSS

(@chanathip_kittipatchara)
New Member
Joined: 1 year ago
Posts: 1
Apr 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.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@felix920506)
Active Member
Joined: 1 year 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

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
DentalStone
(@dentalstone)
New Member
Joined: 1 year ago
Posts: 1
Jun 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.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 3 years ago
Posts: 1891
Jun 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 + GTX 1080 Ti @ 32Gbps-M2 (ADT-Link R43SG) + Win10


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 3 years ago
Posts: 1891
Jul 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 + GTX 1080 Ti @ 32Gbps-M2 (ADT-Link R43SG) + Win10


theitsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Jul 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.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
(@yukinsnow)
New Member
Joined: 11 months ago
Posts: 3
Jul 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

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


nando4 liked
ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 3 years ago
Posts: 1891
Jul 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 + GTX 1080 Ti @ 32Gbps-M2 (ADT-Link R43SG) + Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Jul 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.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 3 years ago
Posts: 1891
Jul 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 + GTX 1080 Ti @ 32Gbps-M2 (ADT-Link R43SG) + Win10


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Jul 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.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


nando4 liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
Posts: 1418
Jul 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
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


nando4 liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
Posts: 4034
Jul 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

94 external GPU build guides


ReplyQuote
Ningauble77
(@ningauble77)
Estimable Member
Joined: 1 year ago
Posts: 134
Jul 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.

2018 13 Macbook Pro + Core v2 + Radeon VII Win10 1809/MacOS 10.14.5 Beta
ASUS X99 Deluxe+Core v2 + Radeon VII Win10 1809


theitsage liked
ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Jul 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.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
Posts: 1418
Jul 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
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 3 years ago
Posts: 4034
Aug 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

94 external GPU build guides


nando4 liked
ReplyQuote
RabMoghal
(@rabmoghal)
New Member
Joined: 10 months ago
Posts: 1
Aug 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.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
mstapha999
(@mstapha999)
New Member
Joined: 11 months ago
Posts: 3
Aug 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 :

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@iman_rahmat)
New Member
Joined: 10 months ago
Posts: 1
Sep 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 ?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@sen_pt_sen_boat)
New Member
Joined: 8 months ago
Posts: 1
Oct 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 !

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
marioscp
(@marioscp)
New Member
Joined: 7 months ago
Posts: 1
Nov 20, 2018 2:32 am  
hi
im trying upgrade my laptop with better gpu
im currently with an acer 5750g 
i7 2630qm
8 ram
bios 1.21 (still lookin for akbar modded 1.21 bios for 16 RAM)
dgpu 610M
egpu gtx 680 thanks to setup 1.35
 
but now i want more, and i just buyed an gtx 1070
 
im trying to make an dsdt override and i saw one already done, i downloaded and loaded and guess what BSOD on boot...
so o tryed to make my own but when it come to compile de dsdt-modified.dsl file into an .aml file it hapens this:
 
C:\Windows\system32>c: & cd \dsdt
 
C:\dsdt>iasl -ve dsdt-modified.dsl
 
Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20161222-32
Copyright (c) 2000 - 2016 Intel Corporation
 
dsdt-modified.dsl   7986:                 (Local0 + 0x02)
Error    6114 -                                  ^ Result is not used, operator
has no effect
 
ASL Input:     dsdt-modified.dsl - 10147 lines, 368379 bytes, 3860 keywords
 
Compilation complete. 1 Errors, 7 Warnings, 10 Remarks, 308 Optimizations
 

C:\dsdt>

 
and doesnt create the .aml file to load
 
what i should do?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
bruno
(@bruno)
New Member
Joined: 8 months ago
Posts: 3
Nov 26, 2018 12:44 am  

Hi guys, 

GTX 970 connetced, drivers installed - Error 12 appear

I started with DSDT override and no idea how to finnish. 

After I typed : asl /Fo=dsdt-modified.aml dsdt-modified.asl  

This showed up:
4759:                                        ATMC()

dsdt-modified.asl(4759): error: ATMC is not a method

In Notepad++ :

4759            Release(MCPU)

What should I do next ? 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
ha5dzs
(@ha5dzs)
New Member
Joined: 7 months ago
Posts: 2
Nov 28, 2018 2:51 pm  

Could someone tell me how the table of numbers (that are given so we can just paste it) are generated in the Microsoft method?
I can see that the length is defined in the Buffer(...) statement, and the array has to have the same number of entries.
Are these numbers memory addresses, or page lengths, or qword counts, or what? Why is it important to have 0x79, 0x00 at the end?

I need to move the memory addresses because I have more than 64 GB RAM. The Intel method didn't work for me, because the disassembler couldn't find all the symbols in my hardware.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
ha5dzs
(@ha5dzs)
New Member
Joined: 7 months ago
Posts: 2
Nov 29, 2018 1:00 pm  
Posted by: ha5dzs

Could someone tell me how the table of numbers (that are given so we can just paste it) are generated in the Microsoft method?
I can see that the length is defined in the Buffer(...) statement, and the array has to have the same number of entries.
Are these numbers memory addresses, or page lengths, or qword counts, or what? Why is it important to have 0x79, 0x00 at the end?

I need to move the memory addresses because I have more than 64 GB RAM. The Intel method didn't work for me, because the disassembler couldn't find all the symbols in my hardware.

Following on from this, I did find a few things out. The addresses are there, but they are shown in a little endian format. I still don't understand a few things:
0x8A, 0x2B, 0x00, 0x00, 0x0C, 0x03 Is this some sort of a preamble?
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Guess this is the 'granularity', which is set to 0x 0000 0000 0000 0000
0x00, 0x00, 0x00, 0x20, 0x0C, 0x00, 0x00, 0x00 This is the start address: 0x 0000 000C 2000 0000
0xFF, 0xFF, 0xFF, 0x0F, 0x0E, 0x00, 0x00, 0x00 This is the end address: 0x 0000 000E 0FFF FFFF
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 This is the offset: 0x 0000 0000 0000 0000
0x00, 0x00, 0x00, 0xF0, 0x01, 0x00, 0x00, 0x00 This is the length, which is 0x 0000 0001 F000 0000
0x79, 0x00 I guess these are some sort of a terminator bytes, the last one looks like EOS.

So, do I interpret this correctly, and if I were to change the addresses, I can keep the preamble the same?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Taylan
(@taylan)
Active Member
Joined: 7 months ago
Posts: 16
Nov 30, 2018 4:52 pm  

In Step 1, Option 1 (Intel method), point ii, the following command is listed:

    iasl -da -dl -fe refs.txt dsdt.dat

But the .dsl file generated by this command was giving me syntax errors, and the iasl command output indicated that it couldn't find 7 symbols despite the provided refs.txt file.
I googled and found the following thread:

https://www.tonymacx86.com/threads/compiling-errors-with-iasl.151443/

That gave me the idea to run the following command instead of the one in the guide:

    iasl -da -dl *.dat

The *.dat pattern matches not only the dsdt.dat file but also some accompanying ssdtX.dat files generated by acpidump which apparently contain the missing symbols. This resulted in a working .dsl file.

Might be worth adding this to the guide. My laptop is an HP EliteBook 8770w.

HP EliteBook 8770w, GTX 770, EXP GDC / ExpressCard, Corsair CX430


ReplyQuote
Taylan
(@taylan)
Active Member
Joined: 7 months ago
Posts: 16
Dec 1, 2018 12:03 pm  

Another thing that might be worth adding to the guide: after I rebooted, BitLocker requested the Recovery Key for the machine.

It said it's because the configuration for some file in C:\WINDOWS\System32\ changed, probably related to putting Windows in test-mode and/or overriding the DSDT table.

Can be pretty annoying if your machine is managed centrally by your company or so. I needed to contact my co-workers from our IT department to get the key.

HP EliteBook 8770w, GTX 770, EXP GDC / ExpressCard, Corsair CX430


ReplyQuote
Firecat
(@firecat)
New Member
Joined: 6 months ago
Posts: 2
Jan 3, 2019 1:34 am  

Useful info that should be added to the guide: if you get in a boot loop after loading the ACPI tables you may be able to boot by selecting the "Last Known Good Configuration" option from the safe mode menu (F8 on Windows 7).

Lenovo Thinkpad T430, EXP GDC v.8.4 Expresscard, GTX 1070 Ti


ReplyQuote
Firecat
(@firecat)
New Member
Joined: 6 months ago
Posts: 2
Jan 3, 2019 9:06 am  

I'm getting an Error 12 with my eGPU on my Lenovo Thinkpad T430 running Windows 7. I followed the instructions in this guide: https://egpu.io/forums/pc-setup/fix-dsdt-override-to-correct-error-12/

I tried both the intel and microsoft methods, and also tried the newest iasl. I could get them both compiled with both compilers with no errors, but when I tried to load I got a BSOD bootloop.

Any ideas on how this can be? Is my bios somehow preventing a DSDT override?

This post was modified 6 months ago

Lenovo Thinkpad T430, EXP GDC v.8.4 Expresscard, GTX 1070 Ti


ReplyQuote
azbest_hu
(@azbest_hu)
New Member
Joined: 6 months ago
Posts: 3
Jan 23, 2019 10:14 pm  

Firecat, What is your bios version on your t430 machine? Is your windows installed in uefi mode?

This post was modified 5 months ago

T430 (bios v2.78) + Exp gdc 8.4 EC + gtx 1050 + atx psu


ReplyQuote
(@warren_binder)
Active Member
Joined: 5 months ago
Posts: 7
Jan 24, 2019 3:18 am  

I am doing the Microsoft Method on my MBP 15" 2017 and I have ran into this error:

dsdt-modified.asl:

1844: Return(AR00())
^***
dsdt-modified.asl(1844): error: AR00 is not a method

Thoughts?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Noble Member Moderator
Joined: 2 years ago
Posts: 2093
Jan 24, 2019 3:24 am  

@warren_binder that Mac doesn’t need the DSDT override, since it already has Large Memory.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
----
Troubleshooting eGPUs on macOS
Command Line Swiss Knife
eGPU Hardware Chart
Multiple Build Guides
----
Current: MacBook Pro RP560X + 480/R9 Fury/Vega 64 | GTX 780/1070
Previous: 2014 MacBook Pro 750M + 480/R9 Fury | GTX 780/980 Ti/1070


theitsage liked
ReplyQuote
(@warren_binder)
Active Member
Joined: 5 months ago
Posts: 7
Jan 24, 2019 5:01 am  

Ok, thanks! I have disabled my left two ports, I have DDUed and installed the required drivers. I am still getting error 12.... any suggestions?

This post was modified 5 months ago

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@warren_binder)
Active Member
Joined: 5 months ago
Posts: 7
Jan 24, 2019 4:59 pm  

How do I boot with Clover? I am using an external boot drive...

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@viren_chocha)
New Member
Joined: 5 months ago
Posts: 2
Jan 27, 2019 5:00 am  

I am able to get my display card AMD R7 240 inside device manage listing and getting error 12. I have gone through your post for resolving the same and I am ok with Microsoft method.

My system detai
System : Lenovo Ideapad z570;  Processor : Core i5 2430M; Egpu dock : Exp GDC V8.5; Egpu card : msi AMD R7 240 

But on compilation I am getting error:Arg0 unexpected ASL term type. Typical entry where error is occuring is as below. Can you help please ? Error is occuring in below line no 23.

1. Method(GNOT, 0x2, NotSerialized)
2. {
3. If(PDRD())
4. {
5. Return(One)
6. }
7. Store(Arg0, CEVT)
8. Store(0x3, CSTS)
9. If(LAnd(LEqual(CHPD, Zero), LEqual(Arg1, Zero)))
10. {
11. If(LOr(LGreater(OSYS, 0x7d0), LLess(OSYS, 0x7d6)))
12. {
13. Notify(PCI0, Arg1)
14. }
15. Else
16. {
17. Notify(GFX0, Arg1)
18. }
19. }
20. If(CondRefOf(HNOT, ))
21. {
22. HNOT
23. Arg0     <---- this is the line which is thrown out as error
24.}
Else
{
Notify(GFX0, 0x80)
}
Return(Zero)
}

Laptop:Lenovo Ideapad Z570; 8 GB RAM, Exp GDC V8.5; Present : R7 240; Future : RX 570


ReplyQuote
pasiamoon
(@pasiamoon)
Active Member
Joined: 6 months ago
Posts: 6
Jan 31, 2019 6:28 pm  

Thank you nando4 for this guide! I fixed my error 12 with the DSDT override and the Intel method. Everything was fine but now Im getting the message from diferent games that I need to turn off the testsigning mode. So I was going to install clover to fix it but Im stuck at this point:

"Download the Clover ISO file and install it by extracting with 7-zip (64-bit only) the clover.tar.lzma->clover.tar->clover.pkg->\EFI folder to s:\EFI. Be sure to use the the 7-zip interface to extract to s: drive as Windows explorer refuses to allow viewing of the s: EFI volume."

Im not pretty sure with the s:\EFI drive. I can't find that folder in 7-zip and don't know how to continue. 

 

This post was modified 5 months ago

Macbook pro 2015 15" - Razer core X + ASUS GeForce GTX 1070 ROG Strix 8GB


ReplyQuote
Page 5 / 6