Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Gaming & Steam

This page is explicit about what InterGenOS provides for gaming today, what you install yourself, and what is not bundled. Where a detail is gaming-specific and not yet confirmed against the shipping system, it is flagged rather than invented.

InterGenOS is a built-from-source Linux distribution with a security-only posture: security is not first, it is only. The goal is a machine you understand, can modify, and can trust. Gaming on InterGenOS works the same way it works on any modern Wayland desktop: the graphics and input foundations are already in place, and the game platforms themselves are installed at your discretion.

The Graphics Foundation

Gaming starts with the GPU stack, and that stack ships and is enabled by default.

InterGenOS runs GNOME 49 on Wayland, with the Mesa graphics stack for AMD (Radeon) and Intel (Arc, Iris, UHD) GPUs. This covers the APIs games rely on:

  • Vulkan through radv (AMD) and anv (Intel)
  • OpenGL / OpenGL ES through radeonsi (AMD) and iris / crocus (Intel)
  • VA-API hardware video decode through radeonsi and intel-media-driver
  • OpenCL compute through rusticl

All Mesa drivers are installed and enabled out of the box. GNOME Shell uses OpenGL or Vulkan automatically. X11-only games run through Xwayland, the automatic translation layer for applications not yet ported to native Wayland.

NVIDIA GPUs

NVIDIA’s proprietary driver is not shipped by default. It is available as an explicit, user-initiated opt-in through pkm, and is offered only on hardware with an NVIDIA GPU present:

pkm install nvidia

You accept the NVIDIA license when prompted, then follow the post-install instructions for enrolling the NVIDIA kernel module with your Machine Owner Key. This matters for gaming because the module must be signed and enrolled to load under the signed Secure Boot chain that InterGenOS ships. See CUDA & NVIDIA for the driver path and Encryption & Keys for the Secure Boot and Machine Owner Key details.

Installing Steam

Steam is not part of the default desktop install. The desktop tier (derive the live count from the manifest; it is in the low hundreds of packages as of this writing) is a general workstation set, not a gaming bundle.

InterGenOS provides proprietary and license-restricted applications through download-helper packages. These do not bundle the vendor binary; they fetch it from the vendor on first install after you accept the license. Brave, Google Chrome, the Claude Code CLI, and Microsoft VS Code already ship under this pattern. If you intend to install Steam, check the repository for a helper package first:

pkm search steam

If a helper package is present, install it with pkm install <name> and accept the vendor license when prompted. If no native or helper package is available, Steam can also be run as a sandboxed Flatpak (see below). Confirm what your installed system actually offers with pkm search rather than assuming a package name.

Flatpak for Game Platforms

Flatpak is not pre-installed, but it is available as an optional install when you want sandboxed third-party applications:

sudo pkm install flatpak

Flatpak is a common delivery path for game platforms and launchers; several publish Flatpak builds upstream. It is not pre-installed because the binary mirror’s signed-index trust chain already provides equivalent integrity guarantees for packages built and signed in-tree. For third-party game platforms that InterGenOS does not build itself, the Flatpak sandbox is a reasonable trade.

What Is Not Bundled

InterGenOS makes deliberate omissions, and several of them touch gaming:

  • No Snap. The Snap daemon is not installed and not in the repository. Some games and launchers are distributed as Snaps upstream; that is not an installation path here.
  • No Flatpak by default. It is one command away, but it is opt-in, not pre-staged.
  • No auto-update. No background service downloads or applies updates without your explicit action. Game platforms with their own self-updaters operate within their own sandbox or install scope; the system itself updates only when you run sudo pkm sync && sudo pkm upgrade.
  • No telemetry from the OS. No component of the desktop phones home. Game platforms you install have their own privacy behavior, governed by the vendor and, where applicable, the Flatpak sandbox, not by InterGenOS.

Performance Notes

A few system characteristics are relevant to gaming and are confirmed by the shipping design:

  • Wayland compositing eliminates screen tearing. Every frame is composited through the display server. Variable refresh rate and mixed-DPI multi-monitor setups are handled by GNOME 49 without manual configuration.
  • Per-window isolation. Each application sees only its own input and pixel buffer, so one application cannot key-log another or scrape another window’s pixels. This is a security property that also applies while a game has focus.
  • VA-API hardware decode is available for video playback (for example, streaming or recorded gameplay in a player) through radeonsi and intel-media-driver.

Anti-Cheat and Online Play

Online and competitive games that rely on kernel-level anti-cheat have varying Linux support that depends on the title and the anti-cheat vendor. Because InterGenOS ships a signed Secure Boot chain, dm-verity integrity, and UKI signing, any component that needs to load a kernel module (including some anti-cheat solutions, and the NVIDIA driver above) must be signed and enrolled to load. Check the specific game’s Linux support before relying on it for competitive play.

AI Assistance for Setup

If you get stuck configuring a game platform or a GPU driver, InterGen, the offline-first local assistant (Qwen models, hardware-detected, zero telemetry), can help walk through pkm commands and driver setup without leaving your machine. For questions beyond the local model’s reach, Phone-A-Friend (Frontier/Cloud Escalation) can route to a frontier provider, but only when you choose to invoke it. Nothing leaves the machine by default.

Cross-References