[GUIDE] DSDT override eGPU error 12 fix
 
Notifications
Clear all

[GUIDE] DSDT override eGPU error 12 fix  

 of  26
  RSS

mcarver316
(@mcarver316)
Estimable Member
Joined: 4 years ago
 

In case anyone is wondering what the fuss is about:

04FullSizeRender 28 05 17 10 38
2015 17" MSI GT73VR 6RF Titan (GTX1070-SLI) [6th,4C,H] + GTX 1080 Ti x4 @ 32Gbps-TB3 (AKiTiO Node) + Win10 [build link]  

goalque liked
ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 4 years ago
 
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 Titan (GTX1070-SLI) [6th,4C,H] + GTX 1080 Ti x4 @ 32Gbps-TB3 (AKiTiO Node) + Win10 [build link]  

ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 4 years ago
 
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 Titan (GTX1070-SLI) [6th,4C,H] + GTX 1080 Ti x4 @ 32Gbps-TB3 (AKiTiO Node) + Win10 [build link]  

ReplyQuote
mcarver316
(@mcarver316)
Estimable Member
Joined: 4 years ago
 

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 Titan (GTX1070-SLI) [6th,4C,H] + GTX 1080 Ti x4 @ 32Gbps-TB3 (AKiTiO Node) + Win10 [build link]  

ReplyQuote
barneyinthesky
(@barneyinthesky)
New Member
Joined: 3 years ago
 

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.

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
Edward09
(@edward09)
Active Member
Joined: 3 years ago
 

Hello everyone

plz help me. I have an HP Elitebook 8570p with an EC slot and an EXP GDC 8.4 with an EVGA gtx 780. it was still ok until today when I am playing Rise of the tomb raider and suddenly I was out of the game with something related to Nvidia driver as i remember.

And now I cannot start my eGPU. It ran for a few seconds and then it shut down . I wonder if it has problem with my ATX psu. besides, i am using Hunkey LW6500HG

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
rushvora
(@rushvora)
Trusted Member
Joined: 4 years ago
 

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?

2016 15" MacBook Pro (RP455) [6th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + Win10 [build link]  

ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 4 years ago
 
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

 
2015 15" Dell Precision 7510 (Q M1000M) [6th,4C,H] + GTX 1080 Ti @32Gbps-M2 (ADT-Link R43SG) + Win10 1803 [build link]  


ReplyQuote
rushvora
(@rushvora)
Trusted Member
Joined: 4 years ago
 
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?

2016 15" MacBook Pro (RP455) [6th,4C,H] + GTX 1080 Ti @ 32Gbps-TB3 (Mantiz Venus) + Win10 [build link]  

ReplyQuote
nando4
(@nando4)
Noble Member Admin
Joined: 4 years ago
 

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

eGPU Setup 1.35    •    eGPU Port Bandwidth Reference Table

 
2015 15" Dell Precision 7510 (Q M1000M) [6th,4C,H] + GTX 1080 Ti @32Gbps-M2 (ADT-Link R43SG) + Win10 1803 [build link]  


rushvora liked
ReplyQuote
 of  26