The video stutters and the CPU spikes
You just installed Fedora on a new laptop. The desktop looks sharp, the terminal feels fast, and the Wi-Fi connects immediately. Then you open a 4K YouTube video or launch a modern game. The playback stutters. Your fan spins up. The system monitor shows a single CPU core pinned at 100 percent. The GPU usage sits at zero. You are decoding video in software. The hardware accelerator is idle.
What is actually happening under the hood
Fedora ships with a complete set of open-source graphics drivers out of the box. The i915 kernel module handles display output, power management, and basic 2D compositing. It also includes the libva library, which provides the Video Acceleration API framework. The framework is there. The actual hardware acceleration plugins are not.
Think of libva like a universal remote control. It knows how to talk to video players and browsers. It needs a specific driver module to translate those commands into electrical signals your GPU understands. Intel split their driver stack years ago. The older i965 driver covers legacy hardware. The modern intel-media-driver covers Gen 11 and newer GPUs. Fedora keeps the base framework in the main repositories. The modern media driver and the Vulkan implementation live in RPM Fusion. The separation exists because of packaging boundaries and third-party testing cycles, not because of missing functionality.
When you play a video without the media driver, the browser or player falls back to software decoding. Your CPU does the math that the GPU was designed to handle. The result is high power draw, thermal throttling, and dropped frames. The display server still works perfectly. The window manager still composites smoothly. Only the heavy media workloads suffer.
Run journalctl -xeu display-manager.service first. Read the actual error before guessing.
Enable RPM Fusion and install the drivers
You need to add the RPM Fusion repositories first. They provide the missing acceleration packages. Run these commands in order.
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
# The free repo contains open-source drivers and codecs.
# The nonfree repo contains firmware and proprietary blobs.
# Both are required for a complete graphics stack.
# dnf will prompt you to import the GPG keys. Type y and press Enter.
Once the repositories are registered, install the Intel media driver and the Vulkan implementation.
sudo dnf install intel-media-driver vulkan-intel
# intel-media-driver provides VA-API hardware decoding for modern Intel GPUs.
# vulkan-intel enables 3D rendering and compute workloads via the Vulkan API.
# dnf will pull in libva-utils and Mesa dependencies automatically.
# The transaction replaces the legacy i965 VA driver with the iHD driver.
Reboot before you debug. Half the time the symptom is gone.
Verify the installation
You need to confirm the system is actually routing video workloads to the GPU. The vainfo command queries the VA-API stack and prints the supported profiles.
vainfo
# This command lists all hardware-accelerated video profiles.
# Look for lines starting with profile that mention H.264, HEVC, or VP9.
# If you see VA-API version and Driver name: iHD, the media driver is active.
# The output confirms the GPU is handling decode, not the CPU.
If vainfo is not on your path, install the utility package first.
sudo dnf install libva-utils
# libva-utils provides vainfo and vaextract for debugging VA-API.
# It is a lightweight diagnostic tool, not a runtime dependency.
# Install it once and keep it for future hardware checks.
# The package does not modify system configuration files.
For Vulkan verification, run vulkaninfo or vkcube. The output will show Intel(R) Graphics as the device name and list the supported Vulkan version. If you are on Wayland, the vulkaninfo tool may complain about missing X11 display variables. Run it with WAYLAND_DISPLAY= wayland-info or simply check glxinfo | grep "OpenGL renderer" in an X11 session.
Run vainfo first. Read the actual driver name before guessing.
Common pitfalls and what the error looks like
The most common failure is a silent fallback to software decoding. vainfo will print Driver name: i965 or Driver name: null. That means the system is using the legacy driver or falling back to CPU decoding. Check your GPU generation. The i965 driver only supports up to Gen 10 (Coffee Lake). Gen 11 and newer require intel-media-driver.
Another frequent issue is missing Vulkan layers. If a game crashes with VK_ERROR_INCOMPATIBLE_DRIVER or Failed to create Vulkan instance, the vulkan-intel package is either missing or conflicting with a manual Mesa installation. Fedora manages Mesa through dnf. Manual tarball installations break the package manager dependency graph. Remove any /opt/vulkan or ~/.local/share/vulkan overrides before reinstalling.
Secure Boot can also block third-party kernel modules, though Intel drivers are fully open-source and usually load fine. If you see modprobe: FATAL: Module i915 not found or signature verification errors, check your Secure Boot configuration. Fedora ships with signed kernel modules by default. RPM Fusion packages are also signed. Import the keys when prompted.
Configuration drift is a quiet problem. Mesa reads settings from /etc/vulkan/icd.d/ and /etc/va/. Never edit files in /usr/lib/. Those ship with the package and get overwritten on every dnf upgrade --refresh. Edit /etc/ instead. The package manager respects user modifications in /etc/ and ignores /usr/lib/.
Trust the package manager. Manual file edits drift, snapshots stay.
When to use this vs alternatives
Use RPM Fusion Intel drivers when you need hardware video decoding, HEVC playback, or Vulkan 3D rendering. Use the default Fedora packages when you only need basic display output and window compositing. Use proprietary NVIDIA drivers when your hardware requires the nvidia-driver stack instead of Mesa. Stay on the stock Fedora installation if you are running a headless server or a virtual machine without a physical GPU.