You installed Fedora, fired up Steam, and clicked play. The game crashes immediately with a message about missing Vulkan layers, or the launcher hangs on a black screen. You checked the hardware specs. The GPU is fine. The issue is the driver stack. Fedora ships with a secure, minimal base. Gaming requires extra pieces that do not come pre-installed on a fresh system.
What's actually happening
The kernel talks to the hardware. User space applications talk to drivers. Drivers talk to the kernel. Fedora separates these concerns to maintain a clean, auditable system. For AMD and Intel GPUs, the drivers are part of the Mesa project, which is open source and included in the core repositories. For NVIDIA GPUs, the drivers are proprietary. They live in the RPM Fusion repository. You must enable RPM Fusion to install NVIDIA drivers. Fedora does not ship proprietary firmware or drivers by default. This keeps the distribution compliant with free software principles. It also means you have to take one extra step to get gaming working.
Think of the GPU as a high-performance engine. The kernel is the chassis. The drivers are the transmission. Fedora gives you the chassis and a basic transmission for standard driving. Gaming needs a sport transmission. For AMD and Intel, the sport transmission is open source and available in the main garage. For NVIDIA, it is a proprietary part you have to source from a third-party vendor. The akmod-nvidia package handles the installation and rebuilds the transmission whenever you update the chassis.
The Vulkan architecture adds another layer. Applications do not talk to the driver directly. They talk to the Vulkan loader. The loader reads configuration files called ICDs to find the driver. The vulkan-loader package provides the loader. The vulkan-nvidia or mesa-vulkan-drivers packages provide the ICDs. If the loader cannot find a valid ICD, Vulkan initialization fails. This is why vulkaninfo is the primary diagnostic tool. It uses the loader to query the system. If vulkaninfo fails, the game will fail.
Convention aside: dnf upgrade --refresh is the normal weekly maintenance command. Run this to keep the Mesa stack current. Mesa updates frequently with driver fixes and performance improvements. dnf system-upgrade is for crossing major Fedora releases. They are different commands. Do not conflate them.
The fix for NVIDIA GPUs
Enable the RPM Fusion repositories to access the proprietary driver packages. Fedora cannot distribute these packages due to licensing restrictions. RPM Fusion bridges that gap.
Enable the RPM Fusion free and non-free repositories to access proprietary drivers.
sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
# WHY: Downloads and installs the repository definition files for RPM Fusion.
# WHY: The $(rpm -E %fedora) expansion ensures the URL matches your current Fedora release version.
# WHY: The non-free repository contains the NVIDIA driver packages.
Install the kernel module package and the Vulkan driver layer. The akmod package contains the source for the kernel module. It triggers a build against the running kernel. This ensures the module matches your exact kernel version.
Install the kernel module package and the Vulkan driver layer.
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda vulkan-nvidia
# WHY: akmod-nvidia contains the source for the kernel module. The package triggers a build against the running kernel.
# WHY: xorg-x11-drv-nvidia-cuda provides the X11 display driver and CUDA runtime libraries required by many games.
# WHY: vulkan-nvidia installs the proprietary Vulkan ICD, which tells the Vulkan loader how to talk to NVIDIA hardware.
Ensure the kernel development headers are present. The akmod build process requires these headers to compile the module. If they are missing, the build fails silently, and the GPU falls back to the basic Nouveau driver.
Install the kernel development headers and force a module rebuild if necessary.
sudo dnf install kernel-devel kernel-headers
# WHY: The akmod build process requires the kernel development headers to compile the module.
# WHY: If these are missing, the module build fails silently, and the GPU falls back to the basic Nouveau driver.
sudo akmods --force
# WHY: Forces a rebuild of all akmod packages. Use this if the module failed to build during installation.
sudo systemctl restart display-manager
# WHY: Restarts the graphical session to load the new kernel module and display driver.
Reboot before you debug. Half the time the symptom is gone after the display manager restarts and the module loads cleanly.
The fix for AMD and Intel GPUs
AMD and Intel GPUs use the Mesa stack, which is part of the core Fedora repositories. You do not need RPM Fusion. You do need to ensure the packages are up to date. Mesa receives frequent updates with driver improvements and Vulkan support fixes.
Update the Mesa libraries to get the latest driver improvements and Vulkan support.
sudo dnf upgrade --refresh
# WHY: The --refresh flag forces dnf to download fresh metadata, ensuring you get the latest Mesa packages available.
# WHY: Fedora's release cadence is six months. Regular updates keep the Mesa stack current with upstream fixes.
# WHY: This command updates all packages, including mesa-libGL, mesa-vulkan-drivers, and the kernel.
Verify it worked by checking the Vulkan and OpenGL versions. The vulkan-tools package provides the diagnostic binaries. Install it if it is missing.
Verify the Vulkan loader detects your GPU and reports the correct driver version.
sudo dnf install vulkan-tools
# WHY: vulkan-tools provides the vulkaninfo binary, which queries the Vulkan ICDs installed on the system.
vulkaninfo | grep "deviceName"
# WHY: Filters the output to show the GPU name. If this returns nothing, the Vulkan loader cannot find a valid driver.
Check the OpenGL renderer string to confirm the driver is active.
Check the OpenGL renderer string to confirm the driver is active.
sudo dnf install mesa-dri-drivers
# WHY: mesa-dri-drivers contains the DRI drivers needed for glxinfo to query the OpenGL implementation.
glxinfo | grep "OpenGL renderer"
# WHY: Displays the renderer string. Look for "NVIDIA", "Radeon", or "Intel" followed by the model name.
Run vulkaninfo before you launch the game. If the tool can't see the GPU, the game won't either.
Common pitfalls and what the error looks like
SELinux denials are a common friction point for games running under Proton or Steam. The containerized environment may trigger denials when accessing GPU device nodes. Do not disable SELinux globally. Check the logs for the specific denial.
Convention aside: SELinux denials show up in journalctl -t setroubleshoot with a one-line summary. Read those before disabling SELinux. The output includes a link to the solution. Follow the link.
Check for SELinux denials that block game processes from accessing GPU resources.
journalctl -t setroubleshoot -n 20
# WHY: Queries the setroubleshoot service logs for recent SELinux denial summaries.
# WHY: The output includes a one-line explanation and a link to the solution, which is safer than raw audit logs.
# WHY: Use this instead of grep on audit.log. The summary is readable and actionable.
If you see denials related to steam or vulkan, the system may need a local policy module. Generate one only if the setroubleshoot log suggests it.
Generate a local policy module to fix persistent SELinux denials.
sudo grep -i "denied" /var/log/audit/audit.log | audit2allow -M mypolicy
# WHY: Parses the audit log for denials and generates a policy module named mypolicy.
# WHY: audit2allow creates the minimal policy required to allow the blocked actions.
sudo semodule -i mypolicy.pp
# WHY: Installs the generated policy module into the SELinux policy store.
Hybrid laptops require environment variables to force applications to use the discrete NVIDIA GPU. The default behavior routes rendering to the integrated Intel or AMD GPU to save power.
Set environment variables to force applications to use the discrete NVIDIA GPU on hybrid laptops.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia steam
# WHY: __NV_PRIME_RENDER_OFFLOAD=1 tells the NVIDIA driver to handle rendering for this process.
# WHY: __GLX_VENDOR_LIBRARY_NAME=nvidia forces the GLX vendor library to use the NVIDIA implementation instead of the Intel one.
# WHY: This command launches Steam with the discrete GPU active. Prefix other games with these variables if needed.
Firewall rules rarely affect local gaming. Some multi-GPU setups or games with specific networking features use ports 32768-32773. Open these only if you have a specific requirement.
Convention aside: firewall-cmd --reload after every rule change. Otherwise the runtime config and the persistent config diverge.
Open the Vulkan networking ports if your setup requires them.
sudo firewall-cmd --add-port=32768-32773/tcp --permanent
# WHY: Adds the port range to the persistent firewall configuration.
# WHY: Most local gaming does not require these ports. Only add them if a game or multi-GPU feature explicitly needs them.
sudo firewall-cmd --reload
# WHY: Reloads the firewall to apply the persistent configuration to the runtime.
Config files in /etc/ are user-modified. Files in /usr/lib/ ship with the package. Edit /etc/. Never edit /usr/lib/. Vulkan ICD configuration lives in /usr/share/vulkan/icd.d/. Do not edit files there. Create overrides in /etc/vulkan/icd.d/ if you need to change the configuration.
Trust the package manager. Manual file edits drift, snapshots stay.
When to use this vs alternatives
Use akmod-nvidia when you want the kernel module to rebuild automatically after a kernel update. Use kmod-nvidia when you are on a stable kernel and want to avoid the build delay at boot. Use mesa-vulkan-drivers when you have an AMD or Intel GPU and need the open-source Vulkan implementation. Use vulkan-nvidia when you have an NVIDIA GPU and require the proprietary Vulkan driver for performance or feature support. Use __NV_PRIME_RENDER_OFFLOAD=1 when you are running a hybrid laptop and need to force a specific application to the discrete GPU. Use journalctl -xe when a game fails to launch and you need to see the kernel and service logs together. Use vulkaninfo when you need to verify the Vulkan loader can find a valid driver before launching a game. Use firewall-cmd --add-port when a specific multi-GPU or networking feature requires open ports, not for standard gaming.