Fix Audio Windows on MAC

 [GUIDE] DSDT override eGPU error 12 fix (Windows only)

 

here ◄ Mac owners please work through this thread to solve error 12 before doing a DSDT override
here ◄ pre-compiled DSDT overrides  - load or use as reference when making your own

 

Introduction

 

A Windows system's DSDT table root bridge definition (ACPI PNP0A08 or PNP0A03) is usually confined to a reserved 32-bit space (under 4GB) budgetted to be large enough to host the notebook's PCIe devices. A watermark TOLUD value is then set and locked in the system firmware. Windows OS honors the root bridge definition and will allocate PCIe devices within it. 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.

 

When retrofitting a eGPU, an error 12 (This device cannot find enough free resources that it can use) can occur against an eGPU in Windows' device manager making it inoperable. This can indicate there is insufficient 32-bit addressing space available to host the eGPU. An eGPU requires a relatively large PCIe config space to allocate into. Decreasing TOLUD by reducing RAM to 2GB offers a somewhat impractical workaround. Rather, the definitive solution is below.

 

This three step solution removes Window's 32-bit PCIe allocation constraint in order to resolve the eGPU error 12:

 

Step 1. Create a dsdt-modified.aml DSDT file with a 36-bit root bridge

 

Step 2. Load your dsdt-modified.aml as registry override or in-memory substitution



Step 3. Confirm success with a 'Large Memory' area in Device Manager

 

 

macOS users: refer instead to Mikeal's post that covers these steps titled Windows 10 - Clover DSDT memory override [UEFI Windows on Macbooks only].

 

 

Step 1. Create a dsdt-modified.aml DSDT file with a 36-bit root bridge

 

 

OPTION 1: Use the Intel method

 

 

OPTION 2: Use the Microsoft method

 

 

 

Step 2. Load your dsdt-modified.aml as a registry override or in-memory substitution

 

OPTION 1: Load your dsdt-modified.aml as a registry override with Windows test signing mode enabled

 

 

OPTION 2: Avoid test signing mode - load your dsdt-modified.aml as an in memory DSDT substitution

 

 

Step 3. Confirm success with a 'large memory' area in Device Manager

 

 

Success stories

 

 

FAQ

 

1. I still have an error 12 with the 'large memory' area present. How can I fix it?

 

2. How do I disable the registry DSDT override?

Comentarios

Publicar un comentario

Entradas más populares de este blog

Tkinter tkFileDialog module

Imagen
Tkinter tkFileDialog module tkFileDialog  is a module with open and save dialog functions. Instead of implementing those in  Tkinter GUI  on your own. Related courses Tkinter GUI Application Development Projects Overview An overview of file dialogs: Function Parameters Purpose .askopenfilename Directory, Title, Extension To  open  file: Dialog that requests selection of an existing file. .asksaveasfilename Directory, Title, Extension) To  save  file: Dialog that requests creation or replacement of a file. .askdirectory None To  open directory Tkinter Open File The  askopenfilename  function to creates an file dialog object. The extensions are shown in the bottom of the form (Files of type). The code below will simply show the dialog and return the filename.  If a user presses cancel the filename is empty. On a Windows machine change the initialdir to “C:\”. Python 2.7 version: from Tkinter import * from Tkinter import * import Tkinter , Tkconstants ,
Leer más

Using real data types in VHDL

Imagen
Using real data types in VHDL    Apart from the standard types like integer and std_logic_vector's VHDL also offer  real  data types. But a real data type has a big disadvantage. It is not synthesis-able. It can be used only for simulation purposes. This disadvantage limits its use to a large extend, but there are plenty of projects where we look only for simulation results.   Before starting the coding part of a VHDL project,one has to decide whether the project to be implemented on a real FPGA or just a computer simulation is required. If it has to be ran on FPGA, then forget about the real package and use only synthesis-able data types like std_logic,integer etc... Otherwise you can reduce the time and complexity of your project by using real data types. The real data type is defined in the library called  MATH_REAL . So you have to include the following line before the entity declaration in the code: use ieee.math_real.all; The math_real package also offers some elemen
Leer más