Linux Gaming on Pop!_OS 24.04 LTS: The Full Picture in 2026

Linux gaming used to require patience, a thick skin, and a willingness to accept that some titles simply would not work. That era is not fully over, but it is retreating fast. Pop!_OS, developed by System76 out of Colorado, has positioned itself as one of the cleaner entry points into Linux gaming -- not because it reinvents the wheel, but because it carefully assembles the right pieces and gets them talking to each other before you even open a terminal.

The release of Pop!_OS 24.04 LTS on December 11, 2025 marked a significant shift. It shipped with the first stable release of COSMIC -- a Rust-based desktop environment built entirely in-house by System76 -- along with Linux kernel 6.17 (specifically 6.17.9 at launch), Mesa 25.1.5, and NVIDIA driver 580. (Source: Phoronix, December 11, 2025.) That combination is not cosmetic. Each component feeds directly into how games load, how frames get rendered, and how the system negotiates between your CPU, iGPU, and discrete GPU. This article covers what is happening under the hood, what the toolchain looks like in practice, and where the rough edges remain.

Why Pop!_OS for Gaming Specifically?

Pop!_OS is Ubuntu-based, which gives it access to the same vast package ecosystem, the same community documentation, and the same driver compatibility that Ubuntu users rely on. But System76 has made choices that Ubuntu has not. The single biggest quality-of-life win for gamers is the fact that Pop!_OS ships a dedicated NVIDIA ISO -- a separate download image where proprietary NVIDIA drivers come preinstalled. You do not spend the first hour of ownership chasing down the right driver branch or watching an X server fail to start.

For AMD hardware, the situation is even cleaner. AMD's open-source drivers are compiled directly into the Linux kernel itself, so you get full GPU support with nothing to install. Pop!_OS also includes Vulkan drivers and libraries by default, which matters because Proton -- Valve's Windows-to-Linux compatibility layer -- leans heavily on Vulkan to translate DirectX 11 and DirectX 12 calls. Having that foundation preloaded removes a friction point that trips up newcomers on other distributions.

The It's FOSS review called the release a "polished desktop experience" with expanded hardware support built on Ubuntu 24.04 LTS and Linux kernel 6.17. -- Sourav Rudra, It's FOSS (December 2025 review of Pop!_OS 24.04 LTS)

The power profile system is another underappreciated detail. Pop!_OS lets you toggle between battery saver, balanced, and high-performance modes directly from a panel applet. On laptops with hybrid graphics -- an integrated CPU GPU alongside a discrete card -- the 24.04 release introduced automatic per-application GPU assignment. If Steam requests the discrete GPU, the system routes it there without you touching a configuration file. That is the kind of quality-of-life work that used to require prime-run$ man prime-runA command-line wrapper that forces an application to run on the discrete NVIDIA GPU instead of the integrated one. You would type prime-run steam before every launch. Pop!_OS 24.04 makes this unnecessary -- the compositor handles GPU routing automatically per application. invocations from the terminal and careful manual setup.

COSMIC and What It Means for Gamers

COSMIC is System76's answer to years of accumulating frustration with GNOME's upstream development direction. It is written in Rust, runs natively on Wayland, and ships its own compositor. For gamers, Rust and Wayland are not just buzzwords -- they carry specific performance implications.

Wayland's architecture separates input handling at the compositor level, which eliminates the keylogging attack surface that exists in X11. More relevant to day-to-day gaming: Wayland handles variable refresh rate (VRR) support more gracefully than X11 in many configurations. COSMIC's compositor has refined VRR handling to account for a display's minimum refresh rate, meaning the cursor tracks smoothly even when a game is running below that floor -- something that was visibly jarring in earlier implementations.

System76 CEO Carl Richell described the release as a foundation for the company's next two decades, calling it "the first of what will be many rapid innovations." He also confirmed that COSMIC is funded entirely by System76 hardware sales -- customers buying Linux laptops and desktops are directly financing the desktop environment's development. (Source: System76 Blog, December 11, 2025.) That funding model has direct implications for the roadmap -- the team is incentivized to make COSMIC competitive on gaming hardware because that hardware is their product.

The current state of COSMIC is best described as a solid Epoch 1. The window tiling works well across multiple workspaces and displays. The COSMIC Store pulls from both System76's repositories and Flathub. The major GNOME apps have been replaced with COSMIC-native equivalents -- COSMIC Files, COSMIC Terminal, COSMIC Text Editor -- all written in Rust and noticeably responsive. What is not yet there: touch device optimization, display toggle hotkeys with an on-screen display, and some audio routing quirks on certain laptop hardware. These are known issues tracked publicly on the pop-os GitHub project board. (Source: Pop!_OS 24.04 LTS release notes.)

Controller and Gamepad Support

Xbox controllers work over USB immediately on Pop!_OS -- the xpad kernel driver handles them without any additional installation. PlayStation DualSense and DualShock 4 controllers are both recognized by the kernel's hid-playstation module (DualShock 4 support moved from hid-sony to hid-playstation in Linux 6.2), and Steam Input maps them correctly in the vast majority of titles. For Bluetooth connections, pair the controller through the COSMIC Bluetooth panel applet and it will be available to Steam and any SDL2-based game.

There is one known rough edge in COSMIC Epoch 1: some users have reported that Bluetooth-connected controllers are recognized by Steam Input but fail to pass input through to the game itself under the COSMIC compositor, while the same controllers work correctly in GNOME. This is tracked as a known issue on the COSMIC Epoch GitHub project board. (Source: pop-os/cosmic-epoch, Issue #2711.) USB-connected controllers are not affected. If you encounter this with Bluetooth, the current workaround is to use a USB connection or a wireless USB adapter rather than Bluetooth until the compositor fix ships.

The Proton Stack: How Windows Games Run

The technical mechanism behind Linux gaming's resurgence is Proton, developed by Valve from a fork of WINE. Proton works by translating Windows API calls -- DirectX, Win32 system calls, and so on -- into Linux equivalents in real time. It bundles its own implementations of DirectX via DXVK (which translates DX8/9/10/11 to Vulkan) and VKD3D-Proton (which handles DX12). This is why the Vulkan stack being preinstalled on Pop!_OS is not incidental; it is load-bearing infrastructure.

System76's own gaming guide highlights a compelling benchmark: roughly "88% of the top 1000 popular games are rated Platinum, Gold, or Silver" on ProtonDB -- the community database where gamers log their compatibility results. (Source: blog.system76.com, Guide to Gaming on Pop!_OS.) Platinum means a game runs out of the box without any tweaks. Gold means minor tweaks are needed. Silver means it runs with some issues. That figure covers a library that would have been unthinkable five years ago. A note of context: this number is drawn from user-submitted reports and can shift as games receive updates, anti-cheat changes, or new Proton versions ship. It is also weighted toward the top 1,000 by popularity, which skews toward titles Valve has prioritized. Niche multiplayer titles and games with kernel-level anti-cheat pull that number down when you look beyond the top tier. ProtonDB is the best tool available, but it is a snapshot from community testers, not a guarantee.

Installing Steam on Pop!_OS is straightforward: search "Steam" in the COSMIC Store and install the native .deb package. The Flatpak version is available but has known complications with Proton compatibility, so the .deb is the recommended path for gamers. There is some disagreement about this online -- some users report the Flatpak working fine after adjusting sandbox permissions, and on immutable distributions where .deb packages are not an option, the Flatpak is the only choice. On Pop!_OS specifically, however, the .deb package avoids the Flatpak sandbox's permission friction with controller input, Proton's pressure-vessel runtime, and filesystem access to game libraries on secondary drives. Valve's own support documentation distributes Steam as a .deb, and System76's gaming guide installs it via apt. That is why this guide recommends the .deb path. Once installed, enabling Proton is a three-step process in Steam's settings.

# Install Steam via apt (preferred over Flatpak for Proton compatibility)
$ sudo apt install steam

# Then in Steam UI:
# Steam > Settings > Compatibility
# Toggle: Enable Steam Play for supported titles
# Toggle: Enable Steam Play for all other titles
# Dropdown: Select "Proton Experimental" for cutting-edge compatibility

Proton Experimental is Valve's bleeding-edge branch and typically has the broadest compatibility with newly released titles. For games that still fail to launch under official Proton, ProtonGE (maintained by community contributor GloriousEggroll) is the next stop. ProtonGE incorporates patches and fixes that have not yet been merged upstream, and it often resolves compatibility issues weeks before the official Proton release catches up.

# Install ProtonUp-Qt from COSMIC Store or via Flatpak
$ flatpak install flathub net.davidotek.pupgui2

# Launch ProtonUp-Qt, click "Add Version"
# Select GE-Proton (latest) and install

# Then in Steam: right-click game > Properties > Compatibility
# Check: Force the use of a specific Steam Play compatibility tool
# Select the GE-Proton version you installed

Per-game Proton version selection is an important capability. A game that crashes on Proton Experimental might run flawlessly on Proton 9.0 or a specific GE-Proton build. ProtonDB's game-specific pages aggregate exactly this information from real user reports, including which Proton version worked, what launch flags were used, and what hardware they were on. It is the first place to check before concluding a title is broken.

Non-Steam Games: Lutris, Heroic, and Bottles

Steam is not the only distribution channel, and Proton is not the only compatibility layer. Pop!_OS handles the broader non-Steam landscape through a set of tools that have matured considerably.

Lutris is the longest-standing game manager for Linux, with install scripts that automate the setup of games from GOG, Battle.net, Epic, and other sources. It manages its own Wine and Proton runner installations through a preferences panel, and it supports Wine-GE -- the Lutris-specific variant of GloriousEggroll's patches. Lutris works particularly well for older titles where the installation process requires specific Windows runtime librariescommon runtime dependenciesVisual C++ Redistributables (2005 through 2022), .NET Framework 3.5/4.x, DirectX 9/10/11 June 2010 redistributable, XNA Framework, Windows Media Foundation codecs, MSXML, and PhysX. Lutris install scripts bundle the correct versions automatically -- installing them by hand under Wine is one of the most error-prone steps in Linux gaming..

Heroic Games Launcher is the cleaner, more modern option for Epic Games Store and GOG libraries specifically. It integrates directly with those storefronts, handles authentication, and lets you configure Proton or Wine on a per-game basis without going through Steam. For anyone who built a library during Epic's free games period, Heroic is how you access it on Linux.

Bottles takes a different architectural approach: rather than managing individual game installations, it creates isolated "bottle" environments -- self-contained Windows sandboxes -- each with their own runner version, DXVK installation, and dependency set. For complex setups like games with their own launchers that need specific DLL overrides, Bottles gives you fine-grained control without one game's configuration bleeding into another's.

The Anti-Cheat Problem

The single largest compatibility barrier remaining for Linux gaming is kernel-level anti-cheat software. Games using Easy Anti-Cheat (EAC) and BattlEye have had native Linux support since 2021, when both vendors enabled it at Valve's request. However, support must be explicitly activated by each game's developer -- it is opt-in, not automatic.

The practical result is that some games using these anti-cheat systems work perfectly on Linux (because the developer enabled the native module), and others refuse to run or silently kick players from multiplayer sessions. The site Are We Anti-Cheat Yet? (areweanticheatyet.com) tracks the compatibility status of specific games by anti-cheat type. Before installing a multiplayer game, it is worth a two-second lookup on that site.

The clearest example of an absolute incompatibility is Valorant. Riot Games' Vanguard anti-cheat requires deep Windows kernel access at boot and does not function through any Linux compatibility layer. Riot has explicitly confirmed there are no plans for Linux support -- Vanguard's own documentation states that Linux cannot sufficiently attest boot state or kernel modules, and allowing emulation would be a security risk. (Source: Riot Games, Vanguard x LoL Retrospective.) This is not a solvable problem at the distribution level -- it is a policy decision by Riot Games, and attempting to circumvent Vanguard through virtualization or kernel patches risks permanent account bans. The same applies to any title using a kernel-level anti-cheat that lacks a native Linux module.

Performance Tuning: What Moves the Needle

Pop!_OS's power profile system is the first lever worth pulling. Switching from the default balanced profile to the high-performance profile disables CPU frequency scaling, keeps the discrete GPU active, and removes power governors that cap clock speeds. The difference in frame rates on GPU-limited games can be measurable, particularly on laptops with aggressive thermal throttling policies. For users who want to push further, overclocking on Linux is another avenue worth exploring.

The second significant variable is the game launch flags passed through Steam. Several environment variables have become standard practice in the Linux gaming community for squeezing out performance.

# Gamemode: CPU governor + scheduler optimizations while game is running
# Mangohud: in-game performance overlay (FPS, GPU/CPU usage, temps)

gamemoderun mangohud %command%

# For NVIDIA cards with persistent shader pre-caching:
__GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 gamemoderun mangohud %command%

# For AMD GPUs — enable GraphicsPipelineLibrary for reduced shader compile stutter
# (needed only on Mesa versions before 23.1; Mesa 23.1+ enables GPL by default):
RADV_PERFTEST=gpl gamemoderun mangohud %command%

# Install gamemode:
$ sudo apt install gamemode

# Install MangoHud:
$ sudo apt install mangohud

Gamemode (developed by Feral Interactive) temporarily applies a set of optimizations when a game is running: it switches the CPU governor to performance mode, applies process scheduling tweaks, and disables screen savers. It is a small but consistent win on most hardware. MangoHud is the standard Linux gaming overlay, showing frame rates, frametimes, GPU load, VRAM usage, and temperatures in a configurable HUD. Together they give you both performance and visibility.

A note on flags you may still find recommended on older guides: DXVK_ASYNC=1 is no longer valid advice. The dxvk-async patch was removed from GE-Proton after DXVK 2.0 introduced native GraphicsPipelineLibrary (GPL) support via the VK_EXT_graphics_pipeline_library Vulkan extension, which compiles shaders when a game loads its D3D shaders rather than at draw time -- eliminating the stutter dxvk-async was patching around. The dxvk-async repository was archived by its author on November 23, 2025. (Source: github.com/Sporif/dxvk-async.) Similarly, RADV_PERFTEST=aco has been a no-op since Mesa 20.2 (released in 2020), when ACO became the default RADV shader compiler. (Source: Phoronix, June 2020.) If you see either variable in a guide, treat it as a sign the guide is outdated. This is worth emphasizing because a significant number of Linux gaming guides, forum posts, and wiki pages written between 2020 and 2024 still list these flags without noting they are obsolete. The confusion persists because these variables do not cause errors when set -- they are silently ignored by current software, which makes it difficult for users to tell whether they are doing anything. They are not.

For NVIDIA hardware specifically, the hybrid graphics improvements in Pop!_OS 24.04 deserve attention. The old workflow required either running everything on the discrete GPU (destroying battery life) or manually invoking `prime-run` before the game executable. The new approach uses automatic GPU assignment: apps that request high-performance rendering are routed to the dGPU, everything else stays on the iGPU. You can also right-click an application icon to force it onto a specific GPU -- a UI-level shortcut that removes a real daily friction point for laptop gamers. (Source: It's FOSS review, December 2025.)

ProtonDB Ratings in Practice: Reading Between the Lines

ProtonDB's rating system -- Platinum, Gold, Silver, Bronze, Borked -- is useful but requires some interpretation. A Platinum rating means the game ran without any tweaks for the reviewer who submitted the report, on their hardware, with their Proton version, at the time they tested it. It does not mean it will run identically for you. GPU vendor, driver version, kernel version, and game patch version all affect compatibility.

The more useful information is often in the individual reports linked below each rating. These tell you which Proton version was used, what launch flags were applied, and what hardware the tester was running. When a game has a Gold or Silver rating, the reports frequently contain the exact fix that moves it from "crashes" to "playable" -- a specific launch flag, a particular Proton version, or a one-time workaround during the initial shader compilation pass.

Shader compilation deserves specific mention because it is a source of real frustration for new Linux gamers. Many Proton games compile their shader cache on first launch, which can take several minutes and causes severe stuttering during initial play sessions. This is not a bug and it is not permanent -- subsequent play sessions run from cache. It is a known limitation of the translation layer architecture, and it is worth knowing about in advance rather than concluding the game is broken. On AMD hardware with Mesa versions before 23.1, the RADV_PERFTEST=gpl launch flag enables GraphicsPipelineLibrary support, which compiles shaders at load time rather than at draw time and significantly reduces initial-session stutter. On Mesa 23.1 and later (released May 2023), GPL is enabled by default, so this flag is unnecessary on any reasonably current distribution -- including Pop!_OS 24.04, which ships Mesa 25.1.5.

System76's gaming guide reports that 88% of the top 1,000 Steam titles are rated Platinum, Gold, or Silver on ProtonDB -- and notes the trend is still improving. -- System76, The System76 Guide to Gaming on Pop!_OS (blog.system76.com)

NVIDIA vs. AMD on Pop!_OS: An Honest Assessment

The conventional wisdom in Linux gaming circles is that AMD hardware offers a smoother experience due to its fully open-source driver stack (Mesa/RADV), which receives frequent upstream updates and integrates tightly with Vulkan. That assessment remains broadly accurate in 2026, and it became even more definitive during the past year: AMD officially discontinued AMDVLK, its separately maintained open-source Vulkan driver, in September 2025. The announcement on the AMDVLK GitHub stated AMD was "throwing our full support behind the RADV driver as the officially supported open-source Vulkan driver for Radeon graphics adapters." (Source: AMD AMDVLK GitHub, Discussion #416, September 2025.) The consolidation means AMD is now fully invested in a single driver codebase that benefits from Valve, Red Hat, Google, and community contributions. For Linux gamers, this removes the old ambiguity about which Vulkan driver to use on AMD hardware -- RADV via Mesa is definitively the answer.

Pop!_OS's dedicated NVIDIA ISO and System76's packaging of NVIDIA drivers have done meaningful work to reduce the rough edges. The NVIDIA 580 driver series supports the RTX 50 Series (Blackwell) cards and includes improved Wayland support through GBM (Generic Buffer Management), which COSMIC's Wayland compositor relies on. NVIDIA has also been publishing more of its driver internals, enabling better integration between the proprietary driver and open-source tooling.

Where NVIDIA still trails on Linux: Vulkan driver update cadence (Mesa/RADV updates ship far more frequently than NVIDIA's proprietary releases), occasional Wayland compositing glitches under specific workloads, and the ongoing dependency on a proprietary driver that sits outside the kernel's upstream maintenance model. The Nova driver project represents NVIDIA's potential long-term path to open-source parity, but it is years away from production readiness. In the meantime, the advice "AMD if you have the choice, NVIDIA if you already own it" is still the most accurate summary of the Linux gaming GPU landscape in 2026. This is a statement you will find debated in every Linux gaming forum. NVIDIA users will correctly point out that the proprietary driver performs well, that many games run without issues, and that NVIDIA cards often offer better ray tracing performance. Those points are fair. The reason this guide still leans AMD is not about raw frame rates in any single game -- it is about the structural advantages of an open-source driver stack that receives updates through the distribution's normal package manager, integrates with the kernel's release cycle, and does not require a separate ISO or manual driver installation. For someone buying new hardware specifically for Linux gaming, those structural factors reduce long-term friction. For someone who already owns an NVIDIA card, Pop!_OS is among the best distributions for minimizing that friction through its NVIDIA ISO and System76's driver packaging.

What Comes Next

System76 has a public project board tracking planned COSMIC features, including frosted glass effects, desktop animations, printer settings, and touch/on-screen keyboard support. These are quality-of-life improvements rather than gaming-critical features. The gaming roadmap is more directly tied to Valve's Proton development, which shows no sign of slowing, and to NVIDIA's continuing work on the open-source Nova kernel driver.

The Nova driver is worth watching carefully. It is a Rust-written, open-source kernel driver for NVIDIA GPUs being developed upstream in the Linux kernel tree -- its initial core code was submitted for Linux 6.15 in March 2025 and merged when 6.15 released in May 2025. (Source: Phoronix, March 10, 2025.) Nova is designed specifically for NVIDIA GPUs that use the GSP (GPU System Processor) firmware -- meaning Turing (RTX 20 series) and newer. It is developed primarily by Danilo Krummrich of Red Hat and is intended as the long-term successor to Nouveau. The initial submission totaled approximately 1,200 lines -- around 700 lines of Rust code plus project documentation and a TODO list; practical end-user functionality is still being built piece-by-piece across subsequent kernel cycles. If Nova matures to feature parity with NVIDIA's proprietary driver, it would give NVIDIA users on Pop!_OS the same open-source driver advantages that AMD users currently have -- faster integration with new kernel features and tighter Vulkan coordination through Mesa. (Source: rust-for-linux.com/nova-gpu-driver.)

Pop!_OS upgrade notifications for 22.04 LTS users began appearing on March 3, 2026. (Source: System76 Blog, March 3, 2026.) If you are on 22.04, the path to 24.04 is documented and available via the Settings app or terminal command. The jump brings the full COSMIC stack, the newer kernel, and the improved hybrid graphics support -- all of which have direct gaming implications.

A question that comes up often is how Pop!_OS relates to the Steam Deck and SteamOS. They share the same underlying Proton technology, but they are different products with different goals. The Steam Deck runs SteamOS (an Arch-based, immutable system optimized for handheld hardware and controller-first interaction), while Pop!_OS is a general-purpose desktop distribution. Skills and configurations transfer between them -- Proton versions, launch flags, ProtonDB reports, and game saves via Steam Cloud all work the same way -- but Pop!_OS is not designed for handheld hardware and SteamOS is not designed for desktop use. The relationship is complementary, not competitive.

The Honest Summary

Pop!_OS in 2026 is a strong gaming operating system. It is not a replacement for Windows in every scenario -- kernel-level anti-cheat is a hard wall for specific titles (Valorant being the clearest example), and the COSMIC desktop is still Epoch 1 with known rough edges. But the fundamental stack is sound. Proton translates the vast majority of the Steam catalog with acceptable fidelity. The NVIDIA driver situation, while not as clean as AMD, is manageable in a way it was not two years ago. The hybrid graphics improvements in 24.04 are a real step forward for laptop gamers specifically.

The strongest case for Pop!_OS over other Linux gaming options is not any single feature -- it is the integration. The NVIDIA ISO removes driver setup friction. Vulkan is preinstalled. Power profiles are accessible. The kernel is recent enough to support current hardware. System76 maintains these components as a coherent stack rather than leaving users to assemble them from upstream pieces. For someone coming from Windows who wants Linux gaming without becoming a Linux expert first, that integration is the core value proposition.

The work that remains is largely upstream work: Valve expanding Proton compatibility, NVIDIA maturing the Nova driver, game developers enabling the native Linux anti-cheat modules they have technically had available since 2021. Pop!_OS's role is to stay current with that work and keep the surface between the user and the game as thin as possible.

Dual-Booting Pop!_OS with Windows

For gamers who need specific titles that will not run on Linux at all -- Valorant, League of Legends, Destiny 2 -- dual-booting is the practical answer. Pop!_OS uses systemd-boot rather than GRUB, which means the boot manager lives inside the EFI System Partition and presents a clean menu at startup. Installing Pop!_OS alongside Windows is supported, but there are specifics worth knowing before you begin.

The recommended approach is to install Windows first, then install Pop!_OS to a separate drive or a separate partition on the same drive. The installer will detect the existing Windows installation and configure systemd-boot to offer both options at boot. If you install to a second physical drive, you avoid the risk of partition table conflicts entirely -- this is the safest path for users who are not comfortable with manual partition management.

Steam game library sharing between the two operating systems is possible if your Steam library lives on a separate NTFS or ext4 partition. However, Proton prefix data is Linux-specific and will not carry over from a Windows Steam installation, so each game effectively maintains two separate save and configuration paths unless the game uses Steam Cloud for saves. For competitive multiplayer titles blocked by anti-cheat, boot into Windows. For everything else, stay in Pop!_OS.

How to Enable Proton for All Steam Games on Pop!_OS

Enabling Valve's Proton compatibility layer on Pop!_OS is a short process that unlocks the Windows game catalog through Steam.

1. Install Steam. Use apt for the best Proton compatibility: sudo apt install steam. The .deb package is preferred over the Flatpak version.
2. Open Steam Compatibility Settings. In Steam, navigate to Steam > Settings > Compatibility.
3. Enable Steam Play. Toggle "Enable Steam Play for supported titles" and "Enable Steam Play for all other titles." Select "Proton Experimental" from the dropdown for the broadest compatibility with recent releases.
4. Optionally install ProtonGE. Install ProtonUp-Qt via Flatpak (flatpak install flathub net.davidotek.pupgui2), then use it to install GE-Proton builds for games that need patches not yet merged upstream. In Steam, right-click a game, open Properties > Compatibility, and select the GE-Proton version you installed.

Frequently Asked Questions

What kernel does Pop!_OS 24.04 LTS ship with?

Pop!_OS 24.04 LTS launched on December 11, 2025 with Linux kernel 6.17.9, Mesa 25.1.5, and NVIDIA driver 580. The kernel receives ongoing updates through the normal LTS maintenance cycle.

Does Pop!_OS work well for gaming?

Yes. Pop!_OS 24.04 LTS includes a dedicated NVIDIA ISO with proprietary drivers preinstalled, Vulkan libraries by default, and is built on Ubuntu 24.04 LTS. Combined with Valve's Proton compatibility layer, it can run the vast majority of the Steam catalog on Linux. According to System76's gaming guide, roughly 88% of the top 1,000 Steam games are rated Platinum, Gold, or Silver on ProtonDB.

Can you play Valorant on Pop!_OS or Linux?

No. Valorant uses Riot's Vanguard kernel-level anti-cheat, which requires deep Windows kernel integration and does not function on Linux through any compatibility layer. Riot Games has explicitly stated they have no plans to support Linux. As of 2026 this remains an absolute compatibility barrier with no workaround that avoids account ban risk.

Is AMD or NVIDIA better for Linux gaming on Pop!_OS?

AMD hardware generally has a smoother Linux experience because its driver stack (Mesa/RADV) is fully open-source, receives frequent upstream updates, and AMD officially discontinued AMDVLK in September 2025 to consolidate fully behind RADV. NVIDIA on Pop!_OS has improved significantly with the 580 driver series and improved Wayland/GBM support, but still trails AMD in driver update cadence and Wayland compositing stability.

What is the NOVA driver for NVIDIA on Linux?

Nova is a Rust-written open-source kernel driver for NVIDIA GPUs, developed primarily by Danilo Krummrich of Red Hat as a successor to Nouveau. Its initial core code was submitted for Linux 6.15 in March 2025 and merged when 6.15 released in May 2025. It targets NVIDIA Turing (RTX 20 series) and newer GPUs that use NVIDIA's GSP firmware. It is not yet suitable for production use but is the open-source NVIDIA driver path being actively developed in the upstream Linux kernel.

What is COSMIC and why does it matter for gaming?

COSMIC is a Wayland-native desktop environment written in Rust, developed entirely by System76. Its first stable release (Epoch 1) shipped with Pop!_OS 24.04 LTS on December 11, 2025. For gamers, it matters because it provides native Wayland compositing with refined variable refresh rate handling, automatic per-application GPU assignment for hybrid graphics, and a compositor that games can request the discrete GPU through without manual terminal invocations.

Is DXVK_ASYNC still needed for Linux gaming in 2026?

No. The DXVK_ASYNC=1 environment variable is no longer valid. DXVK 2.0 introduced native GraphicsPipelineLibrary (GPL) support via the VK_EXT_graphics_pipeline_library Vulkan extension, which compiles shaders at load time rather than at draw time, eliminating the stutter dxvk-async was designed to patch. The dxvk-async repository was archived by its author on November 23, 2025. Similarly, RADV_PERFTEST=aco has been a no-op since Mesa 20.2 (2020) when ACO became the default RADV shader compiler.

How do I play non-Steam games on Pop!_OS Linux?

Three tools handle non-Steam games on Pop!_OS: Lutris manages games from GOG, Battle.net, Epic, and other sources with automated install scripts. Heroic Games Launcher integrates directly with Epic Games Store and GOG for authentication and per-game Proton/Wine configuration. Bottles creates isolated Windows sandbox environments for complex setups requiring specific DLL overrides. All three are available through the COSMIC Store or Flatpak.

Do controllers and gamepads work on Pop!_OS?

Yes. Xbox controllers work over USB immediately via the kernel's xpad driver, and PlayStation DualSense and DualShock 4 controllers are both recognized by the hid-playstation kernel module. Steam Input handles mapping for the vast majority of titles. One known COSMIC Epoch 1 issue affects Bluetooth-connected controllers in some games -- the controller is recognized by Steam Input but fails to pass input to the game. USB connections and wireless USB adapters are unaffected. The issue is tracked on the COSMIC GitHub project board.

Can I dual-boot Pop!_OS with Windows for gaming?

Yes. Install Windows first, then install Pop!_OS to a separate drive or partition. Pop!_OS uses systemd-boot, which will detect the Windows installation and present both options at startup. The main consideration is the EFI System Partition: Pop!_OS stores its kernel inside the ESP, so the default 100 MB ESP that some Windows installers create may be too small. Resize to at least 512 MB or install to a second physical drive to avoid the issue entirely.

Is Pop!_OS the same as SteamOS or the Steam Deck?

No. Pop!_OS is a general-purpose Ubuntu-based desktop distribution, while SteamOS is an Arch-based immutable system designed specifically for handheld hardware and controller-first interaction. They share the same underlying Proton technology, so Proton versions, launch flags, ProtonDB reports, and Steam Cloud saves all work the same way on both. The relationship is complementary: Pop!_OS is built for desktops and laptops, SteamOS is built for the Steam Deck.

Sources and References

Technical details in this article are drawn from official documentation and verified sources.

• Phoronix, December 11, 2025 -- Pop!_OS 24.04 LTS release announcement and component versions
• System76 Blog, December 11, 2025 -- COSMIC funding model and roadmap context
• Pop!_OS 24.04 LTS release notes -- Component stack and known issues
• System76 Guide to Gaming on Pop!_OS -- ProtonDB compatibility statistics
• It's FOSS, December 2025 -- Hybrid graphics and upgrade path details
• System76 Blog, March 3, 2026 -- 22.04 to 24.04 upgrade notification timeline
• AMD AMDVLK GitHub, September 2025 -- AMD consolidation behind RADV
• Phoronix, March 10, 2025 -- Nova open-source NVIDIA driver initial submission
• rust-for-linux.com -- Nova driver project documentation
• github.com/Sporif/dxvk-async -- DXVK async patch archival
• areweanticheatyet.com -- Anti-cheat compatibility tracker
• Riot Games, Vanguard x LoL Retrospective -- Vanguard Linux incompatibility and kernel-level anti-cheat architecture
• pop-os/cosmic-epoch, Issue #2711 -- Bluetooth controller input issue in COSMIC Epoch 1