2CPU

The 980M can run Occulus rift if you get the special modded USB drivers. Not sure if they are around anymore as notebook forum went down but it was legit.

Damn reminds me of my m15x which took me from XXX to 680M to 980M. Vivid memories of playing VR w my friends and even my boss during Xmas so long ago.

Except you can use AI to be better at work. No one has GB200 running which is 50x better than H100. We are using A100 garbage which is half the speed of H100. You don't see the future of exponential improvement. Who even uses google anymore.....

VBIOS update went well and I recommend making sure the 5080 is in a stable boot before doing any update. I think I did not need at first to use HackFlags since I had a few devices disabled in the BIOS. Flashing the BIOS and only disabling the EFI capsule update did then need 400. So if your install of 5080 shows Code 12 then might need 400 setting. But do not proactively add this until the Code shows up in Device Manager for the 5080 or your system might not boot.

Yeah the "HackFlags" of PCI can be some dark times. I messed around (again) and found out.....laptop dead for two days as I wanted to try 200 or 600 setting. Ended up having to recover my registry in Win USB boot recovery via command line. After launching regedit you click on HKEY_LOCAL_MACHINE and then you can "Load Hive" from the File menu. At that point you are actually editing the HDD/SSD registry if pointing at C:\Windows\System32\config System registry. Made a recovery edit away from 200 & 600 which ruined my PCIe SSD enumeration for boot (just sits forever with spinning circle). Currently having to use 400 of the HackFlags for reasons unknown to me and just "Unload Hive" after correction. As posted before I did not require any HackFlags registry entry. Perhaps the BIOS flash back to 1.3.2 is the new variable.... On BIOS 1.28.0 (of Area-51 R1) I could select Windows recovery from the ... of the Dell OS Recovery F12 boot (upper right) and get it to allow me to enter Windows Safeboot but not the case on 1.3.2 BIOS. (easy path to Windows Safeboot made it way easier to mess around with registry edits) Hence this venting post where maybe, just maybe it helps someone else in a weird spot like I was. I've also cooked my EFI boot partition like 5 times from the 5080 marginal training. Self-inflected since I was forced to power off deadlocked OS at improper times. Requiring me to again boot into command line Win USB recovery and then use diskpart to delete the corrupted EFI (which is often 100MB btw) partition and recreate it. Then use bcdedit to assign that newly created EFI system partition to the proper Windows directory. Yay......easy fix but not fun when you cannot figure out why sudden BSOD at boot. (or just use Hiren's Win11 boot DVD utilities, smart to do) Never needed any data recovery as just missing EFI/corrupted boot partition or a self inflicted PCIe config issues. Posted from the 1.3.2 BIOS Alienware Area-51M R1 w AGA running 5080 which is working awesome at the moment. I learn from "breaking" things and glad to be just learning and not totally SOL. Edit: Also Hiren's boot DVD is a lifesaver when you are going too fast and blast away your BCD or drive partitions. The utilities on there are great resources.

Going to order another AGA from eBay to see if somehow I have a bad cable or unit. I can observe PCIe errors on the AGA. When I get a "good boot" everything is great but annoying I have to play around with the boots to do so. Update: Both AGA show the same behavior and if anyone wants to buy a nice unit I have a spare now. Edit: I checked into these further with HWInfo. Reply/Recovery of the PCIe link but this is a "good boot" Here is what a "bad boot" looks like: without the workaround posted above your laptop will eventually freeze/reboot

@i.bakar thanks for replying to my PM and supplying the ICC file.

AGA keepin' is real though with ~5x improvement. 2080: 5080:

I swapped the CPU to a 9900K and the stability has improved and maybe better BIOS since I changed that too. Overall the OS does not lock up like it would with the 9900 and the AGA w 5080. I've downgraded the Gfx driver since I lost outline highlight in the Indiana Jones game and need that function.

Before the downgrade make sure to backup your data.

However you need to swap the CPU to one that does not have the Intel e-fuses burned by microcode (happens on the later BIOS for security fixes). Otherwise your R1 will not boot. I had planned an upgrade of the 9900 to 9900K, got one from eBay after confirming the user never updated their BIOS. A flash from 1.27.0 to 1.12.0 worked fine and then I used recovery method to downgrade to 1.3.2 which resulted in no boot. I then swapped to 9900K and system booted with 1.3.2 BIOS. I immediately changed BIOS settings to disable firmware capsule update.

Removing added 32GB sticks of RAM did not help with the misbehavior. It seems that the AGA/5080 comes up in good state sometimes and marginal state other times (more often lately in marginal). If attempting to run 3dmark and it will freeze on the marginal occasions. Could just be bad PCIe link training or something with enumeration on boot. Anyways, not my best runs but at least now in a working state. Steel Nomad at 80+ fps seems decent. Paying a 15-20% penalty with Gen3x4 so it will never be a benchmark box.

It was plug and play for about three days (Add Y splitter for power and display port cable from 5080 to Monitor). Not sure why but today the system is really unstable. UPDATE 2: The discussed work around seems to be fine for basic tasks, benchmarks and casual games but will eventually freeze when extreme gaming loads placed. Only waiting for a "good boot" works at extreme gaming load =/ (like 1 in 10 boots it seems) Update: Turns out the AGA/Win10/5080 can come up in less than perfect PCIe/BIOS handshake. I must of been fortunate with my initial boots but appears the issue is confusion that Win10 has dealing with the PCIe errors and then handing off the Gfx workloads back-n-forth with the onboard discrete and the AGA. This terrible passing of programs around trying to optimize just craters the performance/stability. Using @ssj92 post about dealing with different cards in his M18x system was a good workaround. I noticed an improvement when I had assigned a program to use the 5080 explicitly and had wondered if there was a global setting like no 2080 for GPU workloads. Even on "bad boots" the 3d mark is 2 or 3 fps less than perfect rather than completely freezing (later testing has exposed this to not be 100% workaround). All the display related programs only run on the 5080 with the "DirectXUserGlobalSettings" (only laptop display shown attached on 2080) I cannot disable the 2080 or the internal LCD remains on after the 5080 takes over on Windows boot and I don't want to burn the image into the screen. I've currently disabled the iGPU in device manager to try and further limit the "Gfx program shuffling", 2080 just sits idle and turns the LCD off while I use external monitor via Display Port from the 5080. FYI I recommend HWInfo64 default boot on startup with the 5080 sensors displayed. Thus I know immediately if I have best gaming fps ready to go or need to try again. However the workaround is perfect for 99% of everything else. Likely most will need the HackFlags at 400 and then above HighPerfAdapter adjustment. Not sure if it matters but I also removed the Gen1 idle transition by changing NVIDIA control panel to high performance. Old debug progress and rant posts: Just really strange since last night I was getting sudden drops in the IJ full circle to 5 fps then back to 50+ which did not happen Saturday (the day I added more RAM). Now the game refuses to launch properly and runs at 5 fps the entire time and me messing with the settings with a choppy mouse hasn't helped. I read that the best way to unlock the full potential of the AGA is to manually disable the internal/laptop gfx discrete (somehow in BIOS such that they do not show in OS) such that the system only looks to the AGA card. I haven't discovered those steps but perhaps I am getting unlucky BIOS enumeration which is giving the 5080 trouble w the OS? Sometimes if I have the other cards disabled in the device manager then strange things happen. One being the internal LCD does not cleanly hand-off during boot and stuck with logo when the 5080 monitor takes over. (not always though)

I've seen some really great scores from Reddit with the amplifier. I went to check the how-to and post was removed by a filter. Does anyone know the steps? Guessing I hook up the display to the back of my card in the alienware amplifier.