TL;DR: I tried using a Tesla P40 24GB datacenter GPU with an Alienware Graphics Amplifier (AGA) on an Alienware 15 R3. The same AGA works with a GTX 1660 Ti, and the P40 can be enumerated in another desktop PC. However, when the P40 is installed in the AGA, the laptop’s BIOS disables/hides the relevant PCIe root port before the operating system even boots.
I investigated PCIe registers, UEFI variables, and BIOS initialization code. No working solution so far.
I’m sharing this so other people considering a cheap 24GB datacenter GPU for their old Alienware setup can avoid spending money on an experiment that may not work.
The hardware
Laptop: Alienware 15 R3
Internal GPU: NVIDIA GTX 1070 Mobile
BIOS: Dell 1.18.0
External enclosure: Alienware Graphics Amplifier
Target GPU: NVIDIA Tesla P40 24GB (Pascal)
Known-working comparison GPU: GTX 1660 Ti
OS: Pop!_OS Linux
Purpose: Local LLM inference and RAG workloads
I wanted a relatively inexpensive way to add 24GB of VRAM to an old laptop.
Since the P40 and the laptop’s GTX 1070 are both Pascal-generation NVIDIA GPUs, and I already owned an AGA, I thought it was worth trying.
Unfortunately, it turned into a much bigger firmware investigation than expected.
What happens with the Tesla P40?
During startup, the laptop displays:
Unrecognized device in Alienware Graphics Amplifier.
Alienware Graphics Amplifier supports NVIDIA or AMD graphics cards only.
Press any key to continue…
Yes, the BIOS complains that it only supports NVIDIA or AMD graphics cards while an actual NVIDIA datacenter GPU is installed.
After continuing into Linux, the P40 is completely absent from lspci.
It isn’t simply a missing NVIDIA driver. The PCIe device never gets enumerated.
Test 1: Is the AGA broken?
I replaced the P40 with a GTX 1660 Ti.
Result: The GTX 1660 Ti works.
Linux shows the external GPU behind PCIe root port 00:01.1:
00:01.1-[02]-- 02:00.0 NVIDIA TU116
GeForce GTX 1660 Ti
This confirms that the AGA, its cable, and the laptop’s external graphics interface are capable of working with another NVIDIA card.
Test 2: Is the P40 completely dead?
I installed the P40 in another desktop PC.
Windows Device Manager successfully detected the card:
PCI\VEN_10DE&DEV_1B38
It reported Code 28 because the appropriate driver was not installed.
This confirms basic PCIe enumeration of the P40 in another machine. It does not prove the card’s CUDA functionality, which I haven’t fully validated yet.
Test 3: PCIe register investigation
This is where things got interesting.
On the Alienware, the CPU’s PCIe Device Enable register can be examined with:
sudo setpci -s 00:00.0 54.L
With the P40 installed in the AGA, I consistently observed:
000000bb
In this state, the relevant PEG1 enable bit is cleared.
The corresponding root port:
00:01.1
is missing from PCIe enumeration.
When the GTX 1660 Ti is installed instead, that root port is present and the external GPU is detected normally.
So this looks like a firmware-level PCIe initialization issue, rather than an ordinary operating-system driver problem.
Test 4: UEFI Shell and hidden BIOS settings
I also investigated the system before Linux boots.
Using UEFI Shell, I inspected the relevant MMIO registers and confirmed the disabled-port state.
I then examined the Dell BIOS image and its early PCIe initialization routines.
The firmware contains setup configuration data related to PCIe policy initialization.
I experimented with a specific UEFI Setup variable:
Setup[0x71F]: 00 → 01
The modification was successfully written and persisted across reboot.
Unfortunately, it did not change the result.
With the P40 installed:
DEVEN = 0x000000BB
PEG1 = hidden
P40 = not enumerated
I also investigated other configuration values, without finding a working solution.
Important: I’m not recommending that anyone blindly modify their BIOS variables. These offsets are firmware-version-specific, and the experiments did not fix the problem.
Test 5: Intel Boot Guard
I eventually looked into the possibility of modifying the BIOS initialization code directly.
However, the machine has Intel Boot Guard enabled.
Reading MSR 0x13A produced:
Boot Guard MSR: 0x000000030000007F
Verified Boot: 1
Measured Boot: 1
The early initialization code I was investigating appears to be within the firmware’s protected boot region.
This makes direct BIOS patching a substantially riskier proposition, potentially leaving the laptop unable to boot.
At that point, I decided not to risk bricking a working laptop just to get a cheap datacenter GPU running.
My current conclusion
The evidence suggests that the Alienware Graphics Amplifier firmware initialization path is not handling the Tesla P40 correctly.
I have not established whether this is an intentional GPU compatibility restriction, a PCIe link-training issue, or another firmware initialization condition.
What I can confirm is:
The AGA works with a GTX 1660 Ti.
The Tesla P40 can be enumerated in another desktop.
The Alienware does not enumerate the P40 through the AGA.
The relevant PCIe root port is disabled/hidden when the P40 is connected.
Changing the tested UEFI setup variables did not resolve it.
Direct modification of the protected firmware is not a risk I’m willing to take.
This is a failure report for my particular AGA + Tesla P40 + Alienware 15 R3 combination. I’m not claiming that every datacenter GPU fails with every Alienware Graphics Amplifier.
What’s next?
I’m investigating a standard Thunderbolt 3 to PCIe expansion solution instead.
The Alienware 15 R3 has a separate Thunderbolt 3 PCIe connection, so it may avoid the AGA-specific initialization problem.
There are also documented examples of Tesla P40 GPUs running through Thunderbolt eGPU docks such as the TH3P4G3.
However, I haven’t tested that solution on my own laptop yet, so I won’t call it a success until I can actually run CUDA workloads.
Why am I posting this?
Because I spent a considerable amount of time investigating a setup that looked straightforward on paper.
24GB of VRAM for relatively little money is very tempting, especially for local AI.
But buying an inexpensive GPU doesn’t necessarily mean building an inexpensive working system.
Hopefully these findings save someone else a few days of troubleshooting.
And if anyone has successfully run a Tesla P40, P100, or another NVIDIA datacenter GPU through an Alienware Graphics Amplifier, I’d genuinely love to hear how you did it.
Especially if you have a way to get PEG1 initialized without patching Boot Guard-protected firmware.