Identify both executable and Unix process
A traditional 32-bit Wine rendering process needs a matching 32-bit Vulkan loader, ICD library and any injected layers. A 64-bit process needs their 64-bit counterparts. The Windows game can also start a launcher with a different architecture. Newer WoW64 arrangements complicate this: PE32 describes the Windows executable, but does not by itself prove that the underlying Unix graphics process is 32-bit. Establish the runner’s architecture and actual failed library load. The normal vulkaninfo command on an x86_64 desktop commonly probes only the 64-bit path.
Read architecture warnings in context
A fatal inability to load the required libvulkan.so.1 or the selected ICD deserves an architecture check. An ignored wrong ELF class warning for Steam’s gameoverlayrenderer.so is weaker evidence: Steam can try both overlay architectures so the unsuitable one is skipped. Do not turn every ELF warning into an instruction to install graphics packages. Confirm the library named by the failing process, whether another candidate was accepted, and whether device creation subsequently succeeded. Keep logs from one launch together; otherwise a successful 64-bit launcher may obscure a failing game process.
Fix the matching runtime, not a guessed package
Use the distribution’s documentation for the selected driver and required architecture. Arch multilib, Debian or Ubuntu multiarch and Fedora multilib have different package names and policies. Flatpak Steam’s graphics runtime also has to match its host driver. On NixOS, hardware.graphics.enable32Bit is declarative configuration; a nix-shell that temporarily provides vulkaninfo does not enable system-wide 32-bit graphics. Check the option against the machine’s pinned NixOS release and rebuild from a recorded configuration only after the missing architecture is established. Do not mix package managers or copy host libraries into a container.
Gather evidence before changing the system
Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.
Read-only observation
file "/path/to/game.exe"Requirements: Replace the placeholder with a real executable; file must be installed.
PE32 and PE32+ help identify the Windows program. Inspect the launcher too when the error belongs to it; this result is not the Unix loader’s architecture.
Read-only observation
file "$(command -v vulkaninfo)"Requirements: A POSIX-compatible shell, file and an installed vulkaninfo command.
Read the architecture of this probe. A 64-bit ELF binary’s successful result cannot validate a separate 32-bit process. A wrapper script needs further inspection of its invoked binary.
Temporary diagnostic environment
nix-shell -p vulkan-tools --run "vulkaninfo --summary"Requirements: Nix with a configured nixpkgs channel; this is not a declarative graphics change.
NixOS-only way to provide a temporary diagnostic tool. It can download store paths, and ordinarily still runs a native-architecture probe using the existing graphics configuration.
A controlled test with a way back
Use a distribution-supported Vulkan probe of the failing Unix architecture in the same runtime, if available. Compare it with the native probe and the game’s loader log before installing anything.
Rollback: Exit a temporary diagnostic shell. For a later NixOS configuration change, restore the previous configuration or known-working generation. Package changes on other distributions need their own recorded package transaction.
What this test cannot establish: There is no universal vulkaninfo32 executable or universal install command. Architecture depends on the runtime, not solely on the Windows executable or host CPU.
Sources and scope
This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.
- Khronos Vulkan loader: architecture-error handling
An incompatible ELF architecture can be skipped during driver discovery; the surrounding result matters.
- Valve Steam for Linux: mixed-architecture overlay warning
Valve’s explanation distinguishes ignored preload architecture warnings from a fatal missing graphics dependency.
- Official NixOS Wiki: Steam and graphics configuration
NixOS configures Steam and graphics libraries declaratively; a diagnostic shell does not enable system drivers.