Share:

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

Page 3 / 6
  RSS

nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
April 23, 2017 2:01 pm  
Posted by: JoGary

 

if I use intel method I get 18 errors like below.

dsdt-modified.dsl   9492:                                 PLD_Revision           = 0x1,
Error    6105 -               Invalid object type for reserved name ^  (_PLD: found Buffer, Package required)

had some others but they where easy to repair. any help resolving last 18 errors would be great.

   

Change the section from (example):

      Name (_PLD, ToPLD (
                        PLD_Revision           = 0x1,
                        ..
                        PLD_Order              = 0x0)

 

To include a Package() { } like this:

      Name (_PLD, Package() {ToPLD (
                        PLD_Revision           = 0x1,
                        ..
                        PLD_Order              = 0x0) }

 

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
Haydenator
(@haydenator)
New Member
Joined: 2 years ago
Posts: 3
April 28, 2017 2:30 am  

Hi, I just got a eGPU and I have been stuck with this problem for hours. I went through the first step, but then when I tried the "Microsoft Method" I was so confused on where you got the dsdt.dsl from as I did not get any file when I did the first step. Also, when I searched "Device(PCI0), I got "Name(BUF0, Buffer(0x1ee)" with a big hex under it. I couldn't find "Name(_CRS" with a big hex.

EDIT: found and fixed.

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


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 21, 2017 12:01 pm  

Has anyone tried forcing an eGPU into the Large Memory area?

I have been able to create the Large Memory thanks to this site's hard work. Now my problem is getting a second eGPU into the Large Memory area. I've tried combination of Pascal, Maxwell and Kepler- the 2nd eGPU is always ending up in error code 12 hell.

The exception is combination of Kepler + either Pascal or Maxwell, which just works even without the DSDT fix. So I am still thinking the problem might be solved if I could just force the eGPU (or both it doesn't really matter) having error code 12 problem into the Large Memory area.

I have tried many things,  including downgrading my MSI GT80S  from Windows 10 to Windows 7 (unfortunately, even one eGPU is automatically error code 12 with Windows 7), installing Windows Server 2008-2016 (yes, I know Thunderbolt is not supported, although I was hoping somebody found a hack by now). 

Thanks in advance.

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
May 22, 2017 2:34 am  

@mcarver316, you may want to look at this script and it's mm command to help with your problem.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 25, 2017 11:28 am  
Posted by: nando4

@mcarver316, you may want to look at this script and it's mm command to help with your problem.

Thanks nando4!

I will look into the thread this weekend as it seems very involved. Much of the instruction is for the Mac, so I'll try and see if I can get the instructions applicable to Windows to work.

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 5:42 am  

No DSDT fix needed!!! I asked an MSI BIOS genius to unlock the MSI BIOS, switched Thunderbolt security from unique ID to legacy, and boom!!! Both 1080 Ti are active without error code 12!!!

FINALLY!!! Thanks to EGPU member, SKY!!!

 

FINALLY ALL4GPUACTIVE

 

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


theitsage liked
ReplyQuote
jefniro
(@jefniro)
Estimable Member
Joined: 2 years ago
Posts: 148
May 28, 2017 7:16 am  
Posted by: mcarver316

No DSDT fix needed!!! I asked an MSI BIOS genius to unlock the MSI BIOS, switched Thunderbolt security from unique ID to legacy, and boom!!! Both 1080 Ti are active without error code 12!!!

FINALLY!!! Thanks to EGPU member, SKY!!!

 

FINALLY ALL4GPUACTIVE

 

What it's amazing is that you have two GTX 1070 and two GTX 108o TI!! Four Nvidia GTX!! 😁😁😁 

late-2016 13" MacBook Pro Touchbar + [email protected] (AKiTiO Node) + macOS & Win10


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
May 28, 2017 8:12 am  
Posted by: mcarver316

No DSDT fix needed!!! I asked an MSI BIOS genius to unlock the MSI BIOS, switched Thunderbolt security from unique ID to legacy, and boom!!! Both 1080 Ti are active without error code 12!!!

FINALLY!!! Thanks to EGPU member, SKY!!!

Consider if a modified BIOS is necessary. eg: I applied the procedure here and was able to extract a Dell E5470's IFR file containing UEFI variables from a BIOS dump.  Thunderbolt Security Legacy Mode could be NVRAM toggled on the E5470 with 'setup_var 0xFF5 0x1'.

0x39575                 Setting: Thunderbolt" Security level, Variable: 0xFF5 {05 91 E9 05 EA 05 24 04 01 00 F5 0F 10 10 01 04 00}
0x39586                     Default: 8 Bit, Value: 0x2 {5B 06 00 00 00 02}
0x3958C                     Option: Legacy Mode, Value: 0x1 {09 07 EB 05 00 00 01}
0x39593                     Option: Unique ID, Value: 0x2 (default MFG) {09 07 EC 05 20 00 02}
0x3959A                     Option: One time saved Key, Value: 0x3 {09 07 ED 05 00 00 03}
0x395A1                     Option: DP++ only, Value: 0x4 {09 07 EE 05 00 00 04}

This is just an example. That E5470 didn't have a Thunderbolt controller on it, but the BIOS had remnants of supporting Thunderbolt.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


goalque liked
ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1369
May 28, 2017 11:18 am  

Intel is working on this security setting for Linux:

http://www.phoronix.com/scan.php?page=news_item&px=Thunderbolt-Security-Levels

Explained in detail here:

https://lkml.org/lkml/2017/5/18/849

+  none
+    All devices are automatically connected by the firmware. No user
+    approval is needed. In BIOS settings this is typically called
+    *Legacy mode*.

http://www8.hp.com/h20195/v2/GetPDF.aspx/4AA6-5088EEW.pdf

Thus far, I've been only able to parse the memory as it has not been documented how to read the device/vendor name. This information can be extracted from the DROM:

https://lkml.org/lkml/2017/5/18/846

Linux is open source, the best source for understanding how things work at the lowest level.

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
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 12:18 pm  
Posted by: goalque

Intel is working on this security setting for Linux:

http://www.phoronix.com/scan.php?page=news_item&px=Thunderbolt-Security-Levels

Explained in detail here:

https://lkml.org/lkml/2017/5/18/849

+  none
+    All devices are automatically connected by the firmware. No user
+    approval is needed. In BIOS settings this is typically called
+    *Legacy mode*.

http://www8.hp.com/h20195/v2/GetPDF.aspx/4AA6-5088EEW.pdf

Thus far, I've been only able to parse the memory as it has not been documented how to read the device/vendor name. This information can be extracted from the DROM:

https://lkml.org/lkml/2017/5/18/846

Linux is open source, the best source for understanding how things work at the lowest level.

The MSI BIOS was/is rather restrictive. Unlocking the BIOS meant extensive custom patch to unhide about 90 percent of the 'fun' settings. The important one in this case was the ability to switch Thunderbolt from 'Unique' ID to 'Legacy'.

Unfortunately, I had the Linux install in another MSI laptop. I will test Linux compatibility with the GT73VR with the modded BIOS in a few days.

 

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1369
May 28, 2017 12:47 pm  

@mcarver316:

Keep in mind that these settings are not yet fully available for Linux, they are under development as far I know but help us understand how to call directly the Thunderbolt controller.

In the end, we are just interested in what the legacy mode actually does "automatically", right?

Seems to be a significant factor for resolving the eGPU error code 12.

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


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 1:24 pm  
Posted by: nando4
Posted by: mcarver316

No DSDT fix needed!!! I asked an MSI BIOS genius to unlock the MSI BIOS, switched Thunderbolt security from unique ID to legacy, and boom!!! Both 1080 Ti are active without error code 12!!!

FINALLY!!! Thanks to EGPU member, SKY!!!

Consider if a modified BIOS is necessary. eg: I applied the procedure here and was able to extract a Dell E5470's IFR file containing UEFI variables from a BIOS dump.  Thunderbolt Security Legacy Mode could be NVRAM toggled on the E5470 with 'setup_var 0xFF5 0x1'.

0x39575                 Setting: Thunderbolt" Security level, Variable: 0xFF5 {05 91 E9 05 EA 05 24 04 01 00 F5 0F 10 10 01 04 00}
0x39586                     Default: 8 Bit, Value: 0x2 {5B 06 00 00 00 02}
0x3958C                     Option: Legacy Mode, Value: 0x1 {09 07 EB 05 00 00 01}
0x39593                     Option: Unique ID, Value: 0x2 (default MFG) {09 07 EC 05 20 00 02}
0x3959A                     Option: One time saved Key, Value: 0x3 {09 07 ED 05 00 00 03}
0x395A1                     Option: DP++ only, Value: 0x4 {09 07 EE 05 00 00 04}

This is just an example. That E5470 didn't have a Thunderbolt controller on it, but the BIOS had remnants of supporting Thunderbolt.

I will try to give the information without violating my NDA to the modder.

Here are the steps:

1) Run AMI [redacted] tool to extract OEM MSI BIOS

2) Email OEM BIOS to modder

3) Modder emails back modded BIOS plus a patch

4) Per modder instruction, download and use [redacted] USB BIOS tool to a) perform special formatting of the USB b) compile modded BIOS with patch and OEM BIOS from live memory in Windows

5) Shut down system, reboot in UEFI mode (secure boot disabled) and let the USB flash tool run a batch job in EFI Shell

6) Boot normally to allow Windows to execute 'New Devices Getting Ready', then shut down again

7) Set the BIOS to boot in legacy mode and boot from USB

8) Run custom Memtest (performs memory test within seconds to ensure compatibility), ignore warning about bricking laptop

9) Exit Memtest, reboot into custom DOS, do short prayer then ignore second warning about bricking laptop, then finally flash the modded, recompiled BIOS

10) Type an obscure (this is now proprietary information) command to run yet another batch job in custom DOS mode

11) Shut down laptop, unplug and remove battery for five minutes (waited 10 minutes to make sure the EC controller registers the new BIOS and wipe remaining information in nvram).

12) Boot into BIOS, searched for anything resembling Thunderbolt security (the legacy mode was the closest, so I selected it)

13) Reset BIOS into UEFI, secure boot disabled

14) Boot into Windows

15) Plug the Cubix with modded Aki Node+Aki T3 Thunderbolt controller, cross fingers

16) Allow NVIDIA drivers to install

17) Reboot

18) Pickup jaw from ground, stare at screen  to ensure no more error code 12 in Device Manager

19) Run Hash Suite Pro - pickup jaw from ground again - marvel at 192 billion NTLM passwords processed per second. (219B p/s with 5 GPus)

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


nando4 liked
ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 1:27 pm  
Posted by: goalque

@mcarver316:

Keep in mind that these settings are not yet fully available for Linux, they are under development as far I know but help us understand how to call directly the Thunderbolt controller.

In the end, we are just interested in what the legacy mode actually does "automatically", right?

Seems to be a significant factor for resolving the eGPU error code 12.

Yeah I know what you're saying. I'm still a tadpole (not even a baby yet) when it comes to using the tools Nando4 suggested. As soon as I figure out how to use and extract the information, I will post it here.

Also, keep in mind, this BIOS mod is very specific to MSI laptops. It took someone with extensive coding experience 6-24 hours (each mod is specific to the laptop model and BIOS) to perform the hack. Even just flashing the BIOS was overly complicated and constant warning of bricking the laptop.

I'm afraid I may be back in the same error code 12 hell with the Clevo 870DM3, which should arrive in 2-3 weeks. I wish I had known Thunderbolt security was/is the problem, before forking the money on another laptop. But such is life I guess. 

The good news is for EGPU IO members interested in deep learning, video, audio, hash security audits and other non-bandwidth intensive (so sorry my gaming friends)projects, it is possible to use a Multi-GPU expansion chassis or daisy chain eGPU boxes for multi-GPU applications.

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1369
May 28, 2017 1:59 pm  

Are you saying that reconfigured BIOS/ACPI tables was the key rather than the Thunderbolt legacy mode? Sounded too easy with just one setting.

If the BIOS mods were only a prerequisite for enabling the TB legacy mode and the legacy mode is the key, this is very good news!

I respect privacy and NDA is a very important thing. I’ve observed that some members have been on the edges 🙂

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


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 2:13 pm  
Posted by: goalque

Are you saying that reconfigured BIOS/ACPI tables was the key rather than the Thunderbolt legacy mode? Sounded too easy with just one setting.

If the BIOS mods were only a prerequisite for enabling the TB legacy mode and the legacy mode is the key, this is very good news!

I respect privacy and NDA is a very important thing. I’ve observed that some members have been on the edges 🙂

I think if the eGPU vendors and Laptop OEMs get together, it can be done- flash/software to enable Legacy Mode at boot.

Imagine something like DIY eGPU setup, with the ability to enable Legacy Mode.

---

When I asked the modder to solve the error code 12 problem, he said not possible, no can do.

When Sky mentioned Thunderbolt security, a bulb went off and thought maybe, just maybe unlocking the BIOS will also unhide the settings for Thunderbolt security.

I asked the modder again, this time to just unlock the BIOS. He did mention menus for Thunderbolt security settings are included in the unlocked BIOS.

So I'm not sure if DSDT/UEFITool/Universal IFR Extractor/EFI Shell like hacking needed to happen, or it was simply part of unlocking the BIOS.

Here are the pics after with the modded BIOS (default setting is Unique ID):

03FullSizeRender 28 05 17 10 38
02FullSizeRender 28 05 17 10 38 1
01IMG 2699 28 05 17 10 38

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
May 28, 2017 2:13 pm  

@mcarver316 , can you see if you can save a BIOS dump with the Universal BIOS Backup Tool here at and upload it (or email it to me)? I'll see if the process to extract IFR variables will apply to it and if so, whether Thunderbolt variables appear.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 2:27 pm  
Posted by: nando4

@mcarver316 , can you see if you can save a BIOS dump with the Universal BIOS Backup Tool here at and upload it (or email it to me)? I'll see if the process to extract IFR variables will apply to it and if so, whether Thunderbolt variables appear.

Windows won't allow me to extract with Universal BIOS Backup Tool even with 'run as administrator'. I emailed will email you the modded BIOS extracted by the AMI AFU tool.

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 2 years ago
Posts: 1369
May 28, 2017 2:40 pm  
Posted by: mcarver316

Yes, I think if the eGPU vendors and Laptop OEMs get together, it can be done- flash/software to enable Legacy Mode at boot.

Imagine something like DIY eGPU setup, with the ability to enable Legacy Mode.

There's a chance that we can develop an UEFI tool without a need to flash the firmware. For NDA reasons regarding the MSI BIOS modder, I recommend private messaging.

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


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133

goalque liked
ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 2:59 pm  
Posted by: goalque
Posted by: mcarver316

Yes, I think if the eGPU vendors and Laptop OEMs get together, it can be done- flash/software to enable Legacy Mode at boot.

Imagine something like DIY eGPU setup, with the ability to enable Legacy Mode.

There's a chance that we can develop an UEFI tool without a need to flash the firmware. For NDA reasons regarding the MSI BIOS modder, I recommend private messaging.

Okay. Shoot me a PM. I'm not sure I'm much help though.

I've divulged enough information here for proof of concept without crossing the NDA restriction.

I'm willing to fork a prize for anyone who can develop a UEFI tool without violating somebody's IP.

Do we need a kickstarter campaign?

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
wimpzilla
(@wimpzilla)
Reputable Member
Joined: 2 years ago
Posts: 463
May 28, 2017 5:57 pm  

Okay. Shoot me a PM. I'm not sure I'm much help though.

I've divulged enough information here for proof of concept without crossing the NDA restriction.

I'm willing to fork a prize for anyone who can develop a UEFI tool without violating somebody's IP.

Do we need a kickstarter campaign?

These kind of trick, either mod the bios to unlock menus or mod the NVRAM through EFI shell was done before.

Until you not release proprietary code or information that goes beyond the fact that the option is present in the bios and allowed into desktop mb bios do not warn you.

Obviously making public tools that easily do that, is worst than share a public modded bios or a "how to" about the trick. If you want to keep the nice trick you found available.

Nice found by the way. 🙂

 

2012 13-inch Dell Latitude E6320 + R9 [email protected] (EXP GDC 8.4) + Win10
E=Mc²


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 6:09 pm  
Posted by: wimpzilla

Okay. Shoot me a PM. I'm not sure I'm much help though.

I've divulged enough information here for proof of concept without crossing the NDA restriction.

I'm willing to fork a prize for anyone who can develop a UEFI tool without violating somebody's IP.

Do we need a kickstarter campaign?

These kind of trick, either mod the bios to unlock menus or mod the NVRAM through EFI shell was done before.

Until you not release proprietary code or information that goes beyond the fact that the option is present in the bios and allowed into desktop mb bios do not warn you.

Obviously making public tools that easily do that, is worst than share a public modded bios or a "how to" about the trick. If you want to keep the nice trick you found available.

Nice found by the way. 🙂

 

I work in security audit, so I am legally bound by the NDA- I'm only sharing non-proprietary information here to encourage further development of the eGPU movement.

The thunderbolt limitation is artificial- we are stuck with Intel holding back due to real security reasons- all Thunderbolt enabled computers allows bypassing host security regardless of platform due to direct memory access (first discovered in firewire).

 

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 2 years ago
Posts: 133
May 28, 2017 10:12 pm  

Also let me be clear: I'm not selling the idea that Legacy Mode is all that is needed to get rid of error code 12 for good. It may well be that unlocking the BIOS in this very specific case meant making extensive modifications to the Thunderbolt settings to allow for multiple eGPUs by default.

One thing is certain: leaving the Thunderbolt security setting to 'Unique ID' limits the Thunderbolt resource allocation to one eGPU (or two eGPUs in a very specific configuration, as I have  already covered in my other posts). Switching back to Unique ID also screws up Thunderbolt worse than before (error code 12, 34 and 43 on the eGPUs), so I'd rather not do that until the Clevo 870DM3 arrives and I have a backup.

Until Intel figures out a way to roll Thunderbolt security automatically in the controller without additional BIOS voodoo, we will be stuck in these error code hell for quite some time. Thunderbolt 4, maybe?

2015 17" MSI GT73VR-6RF 2xGTX1070 + [email protected] (AKiTiO Node driving Cubix Chassis) + Win10 > 365Gigahashes per second


ReplyQuote
barneyinthesky
(@barneyinthesky)
New Member
Joined: 2 years ago
Posts: 1
June 10, 2017 1:03 pm  

macOS ignores the root bridge constraints as too does Linux when booted with the 'pci=noCRS' parameter. Neither of those OS require a DSDT override and can allocate freely in the huge 64-bit PCIe address space.

First of all, Hello everybody! First time posting here, sorry if this is wrong thread:

Where to write this command? I'm with ubuntu 16.04 and can't get it going. I worte pci=noCRS in etc/default/grub and did sudo update-grub but if I do lspci -v I can see that my eGPU didn't assign memory. Is that right file for that command?

05:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1) (prog-if 00 [VGA controller])
    Subsystem: Palit Microsystems Inc. GK104 [GeForce GTX 760]     Physical Slot: 1
    Flags: fast devsel, IRQ 19
    Memory at <unassigned> (64-bit, prefetchable) [disabled]     Memory at <unassigned> (64-bit, prefetchable) [disabled]     I/O ports at 4000 [size=128]     [virtual] Expansion ROM at e1c00000 [disabled] [size=512K]     Capabilities: <access denied>
    Kernel modules: nvidiafb, nouveau, nvidia_340

My system: Lenovo ThinkPad T420, only igpu, eGPU: GTX760

NVM: I'm an idiot, didn't plug in power as it should be done so lot of issues were cause of that.

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


ReplyQuote
rushvora
(@rushvora)
Trusted Member
Joined: 2 years ago
Posts: 76
June 29, 2017 3:42 pm  

I have some questions - I've successfully done a DSDT override using TESTSIGNING MODE method. However, with this method I cannot play PUBG or other games utilising BattleEye anticheat. 

Does the Clover method brick MBPs with a wrong DSDT? Since I've successfully implemented a DSDT file, and the Clover method requires the same file, it should work, right? (I know, risks are always involved, etc)

Also, since Windows is on an external SSD and not Bootcamp, is the risk minimized? Since the EFI volume will be on a different disk altogether?

late-2016 15" MacBook Pro RP455 + [email protected] (Mantiz Venus) + Win10 // external SSD


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
June 29, 2017 3:48 pm  
Posted by: rushvora

I have some questions - I've successfully done a DSDT override using TESTSIGNING MODE method. However, with this method I cannot play PUBG or other games utilising BattleEye anticheat. 

Does the Clover method brick MBPs with a wrong DSDT? Since I've successfully implemented a DSDT file, and the Clover method requires the same file, it should work, right? (I know, risks are always involved, etc)

Also, since Windows is on an external SSD and not Bootcamp, is the risk minimized? Since the EFI volume will be on a different disk altogether?

Yes, Clover uses the same DSDT file you've used as a registry override.

Warnings as best as we know about Clover use have been issued at:
https://egpu.io/forums/builds/2016-macbook-pro-154-tb3-gtx980tirazer-core-os-x-win10-clover-dsdt-in-memory-override/#cloverdsdt

In that same thread,  a Clover DSDT override was used on a late-2016 15" MBP without incident.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
rushvora
(@rushvora)
Trusted Member
Joined: 2 years ago
Posts: 76
June 29, 2017 4:06 pm  
Posted by: nando4
Posted by: rushvora

I have some questions - I've successfully done a DSDT override using TESTSIGNING MODE method. However, with this method I cannot play PUBG or other games utilising BattleEye anticheat. 

Does the Clover method brick MBPs with a wrong DSDT? Since I've successfully implemented a DSDT file, and the Clover method requires the same file, it should work, right? (I know, risks are always involved, etc)

Also, since Windows is on an external SSD and not Bootcamp, is the risk minimized? Since the EFI volume will be on a different disk altogether?

Yes, Clover uses the same DSDT file you've used as a registry override.

Warnings as best as we know about Clover use have been issued at:
https://egpu.io/forums/builds/2016-macbook-pro-154-tb3-gtx980tirazer-core-os-x-win10-clover-dsdt-in-memory-override/#cloverdsdt

In that same thread,  a Clover DSDT override was used on a late-2016 15" MBP without incident.

Does the same risk of MBP being bricked apply when Clover is loaded on an external SSD/external USB?

late-2016 15" MacBook Pro RP455 + [email protected] (Mantiz Venus) + Win10 // external SSD


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
June 29, 2017 4:12 pm  

Same risk applies regardless of whichever media is being used to load Clover.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


rushvora liked
ReplyQuote
clarencechen
(@clarencechen)
New Member
Joined: 2 years ago
Posts: 1
July 3, 2017 6:06 pm  

Thanks for the post, but I need help getting it to finally work!

I have a 2016 MacBook pro 15" with i7-6920hq and radeon pro 460 graphics. I am using akitio node and gtx 1070. I used to freeze at booting windows logo if connected to the eGPU so I decided to do an override. I have now followed your instructions to the point when I booted via clover and am getting the "large memory" section. However, I am getting "code 12" if I boot with egpu connected and "there is no driver installed for this device" if I hot plug it after bootup. I tried your four methods for this problem and none worked. Now there's another problem, when I deleted devices using large memory from device manager I lost my built in sound driver and graphic card. I spent some effort to get gpu back and some virtual sound driver back but now cannot solve "no speaker or headphones are plugged in" problem and lost all sound from this computer. Tried all methods there are online, reinstalled all bootcamp drivers, no luck. Help please

 

(two of the three attachment pictures encountered "unknown error" when uploading)

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: 2 years ago
Posts: 1871
July 3, 2017 10:19 pm  
Posted by: clarencechen

Thanks for the post, but I need help getting it to finally work!

I have a 2016 MacBook pro 15" with i7-6920hq and radeon pro 460 graphics.

They key appears to be using apple_set_os.efi AND the DSDT override to solve error 12 as outlined in several implementation guides for your system:  

https://egpu.io/external-gpu-implementations-table/?table_filter ="15-in Macbook Pro -TB3 Win10"

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
panchitous
(@panchitous)
Active Member
Joined: 2 years ago
Posts: 16
July 4, 2017 3:28 am  
Posted by: clarencechen

Thanks for the post, but I need help getting it to finally work!

I have a 2016 MacBook pro 15" with i7-6920hq and radeon pro 460 graphics. I am using akitio node and gtx 1070. I used to freeze at booting windows logo if connected to the eGPU so I decided to do an override. I have now followed your instructions to the point when I booted via clover and am getting the "large memory" section. However, I am getting "code 12" if I boot with egpu connected and "there is no driver installed for this device" if I hot plug it after bootup. I tried your four methods for this problem and none worked. Now there's another problem, when I deleted devices using large memory from device manager I lost my built in sound driver and graphic card. I spent some effort to get gpu back and some virtual sound driver back but now cannot solve "no speaker or headphones are plugged in" problem and lost all sound from this computer. Tried all methods there are online, reinstalled all bootcamp drivers, no luck. Help please

 

(two of the three attachment pictures encountered "unknown error" when uploading)

The best guide so far for your setup.  https://egpu.io/forums/builds/late-2016-15-macbook-pro-rp455-gtx-1080ti32gbps-tb3-mantiz-venus-windows-10-external-ssd/#post-14523

I must remark that with akitio node you need to install thunderbolt drivers after bootcamp drivers, then follow above guide. 

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


ReplyQuote
bwerkman17
(@bwerkman17)
New Member
Joined: 2 years ago
Posts: 2
July 11, 2017 8:53 pm  

hi nando,

First of all, thanks for the great guide.

I'm on a Lenovo X230 and instead of creating my own DSDT file, I just went to the pre-compiled overrides to get mine. I loaded it up just fine (at least I think), but no large memory. I've tried doing this step over again, but still nothing. 

Thanks

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: 2 years ago
Posts: 1871
July 11, 2017 9:35 pm  

bwekman17, the same precaution given at https://egpu.io/public-repository-egpu-dsdt-overrides/ applies to your situation as well:

* following these instructions to load the dsdt-modified.aml file may BSOD your Windows not function as intended due to same-model BIOS-firmware differences.  Proceed then to use Winmerge to compare and merge this file’s dsdt-modified.dsl content into your dsdt-modified.dsl file when creating your own dsdt-modified.aml file.

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 2 years ago
Posts: 1871
August 16, 2017 7:09 pm  

INFO: 2017 Macbook Pros adds a 'large memory' factory DSDT

 

@jzfgs has identified here that this Macbook adds a 16GB-32GB (0x400000000-0x7FFFFFFFF) large memory item to the factory DSDT as the Device Manager->View->Resources by connection screenshot below shows.  A DSDT override to accomplish this is no longer necessary.

2017 15" MBP 2017 13" MBP
Device Manager

mid 2017 13 in macbook pro device manager large memory

 

 

Looks like Apple have been watching us and are getting serious about eGPU support under Bootcamp.

All that is needed to fix error 12 in the 2017 15" MBP  is to disable then re-enable the eGPU hosting TB PCIe bridges either manually using Device Manager->View->Devices by connection or using a devcon.exe script as done by @jzfgs here.

 


The additions to the 2017 15" MBP can be seen by comparing it's dsdt.dsl to the 2016 15" MBP contained in these files:

 

The new additions that faciliate the 'large memory' (16GB-32GB) area being the QWordMemory & CreateQwordField entries shown below:

 

Field (GNVS, AnyAcc, Lock, Preserve)
{
  M64B,   64, 
  M64L,   64, 
}

Name (BUF0, ResourceTemplate ()
{
 QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed, NonCacheable, ReadWrite,
                    0x0000000000000000, // Granularity
                    0x0000000000010000, // Range Minimum
                    0x000000000001FFFF, // Range Maximum
                    0x0000000000000000, // Translation Offset
                    0x0000000000010000, // Length
                    ,, _Y0E, AddressRangeMemory, TypeStatic)
}

Method (_CRS, 0, Serialized)  // _CRS: Current Resource Settings
{
   If ((M64L == Zero))
                {
                    CreateQWordField (BUF0, \_SB.PCI0._Y0E._LEN, MSLN)  // _LEN: Length
                    MSLN = Zero
                }
                Else
                {
                    CreateQWordField (BUF0, \_SB.PCI0._Y0E._LEN, M2LN)  // _LEN: Length
                    CreateQWordField (BUF0, \_SB.PCI0._Y0E._MIN, M2MN)  // _MIN: Minimum Base Address
                    CreateQWordField (BUF0, \_SB.PCI0._Y0E._MAX, M2MX)  // _MAX: Maximum Base Address
                    M2LN = M64L /* \M64L */
                    M2MN = M64B /* \M64B */
                    M2MX = ((M2MN + M2LN) - One)
                }
}

 

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table    •    Several builds
2018 14" HP Elitebook 840 G5 i5-8350U 16GB 512GB + GTX 1080Ti @ 32Gbps-M2 (ADT R43SG) + Win10


mac_editor, jzfgs, goalque and 1 people liked
ReplyQuote
theitsage
(@itsage)
Famed Member Admin
Joined: 2 years ago
Posts: 3822
August 16, 2017 7:20 pm  

Awesome news! Somebody at Apple and/or partners is really rooting for eGPU community.

In my mid 2017 13" non-Touch Bar MacBook Pro, I did not have to disable anything. The 2016 version requires disabling of the iSight camera root. It's possible this change is across the board.

Best ultrabooks for eGPU use

eGPU enclosure buying guide

94 external GPU build guides


nando4 liked
ReplyQuote
jzfgs
(@jzfgs)
Active Member
Joined: 2 years ago
Posts: 12
August 16, 2017 7:30 pm  

Here's a screenshot from my 2017 15" MBP w/ i7 3.1GHz and a Radeon Pro 560!

Still working on how to create the script to disable/enable the PCIE bridges, but there is a Large Memory pool here:

Device Manager

 

EDIT:

If it helps, I uploaded my dsdt folder to Google Drive; dsdt.dsl is untouched–it doesn’t have the QWordMemory modifications specified in the OP or the syntax fix you referred me to.

Link:  https://drive.google.com/open?id=0B4fpRY5-IMA5cGdNWnlTUl83Tzg

2017 MacBook Pro 15" RP560 + [email protected] (AKiTiO Node) + Win10 [jzfgs]^ // error 12 fix by reallocation to 'large memory' script


theitsage and nando4 liked
ReplyQuote
Page 3 / 6