You unboxed the laptop and Fedora won't boot
You just unboxed a new laptop. You burned the Fedora Workstation ISO to a USB stick, booted from it, and the installer loaded. You reached the live desktop, but the screen flickers, the Wi-Fi icon shows a red cross, and the touchpad only moves when you press the left button. You didn't buy a Linux machine, but you want to run Fedora. Now you are staring at a live session that feels like a broken prototype.
This happens when the kernel doesn't have the right driver or firmware for your specific hardware. Fedora ships a curated set of open-source drivers. Proprietary blobs and newer hardware support often require extra steps. The good news is that Fedora can run on almost any modern laptop. You just need to match the hardware to the right packages and firmware.
What's actually happening
Fedora separates the core distribution from proprietary software. The kernel includes drivers for Intel, AMD, and standard peripherals. These drivers are open-source and maintained by the community. When you boot, the kernel probes your hardware. If it finds a chip it recognizes, it loads a module. If the chip needs a binary blob that isn't in the base image, the device stays silent until you provide that blob.
Think of the kernel as a translator. Hardware speaks in binary dialects. The kernel has dictionaries for common dialects. If your laptop uses a rare dialect, the kernel can't translate the commands. You need to install the missing dictionary. For NVIDIA GPUs, the open-source nouveau driver often lacks performance or power management. The proprietary driver fixes this but lives outside Fedora's main repositories. For Wi-Fi and Bluetooth, the kernel might have the driver, but the firmware file might be missing.
Fedora also offers a Hardware Enablement (HWE) kernel. This kernel is newer than the standard one and includes support for recent hardware. If your laptop is newer than the current Fedora release, the HWE kernel might be the difference between a working system and a black screen.
Run dnf upgrade --refresh weekly to keep your packages current. This command forces dnf to check for updates even if the metadata is fresh. It ensures you get the latest driver fixes. Don't confuse this with dnf system-upgrade, which is for crossing major Fedora releases. They are different commands.
How to verify and configure hardware
Test with the live ISO
Never install Fedora without testing the live ISO first. Boot the USB stick and check if the screen works, Wi-Fi connects, and audio plays. If the live session works, the installed system will work. If the live session fails, you need to enable extra repositories or install firmware before proceeding.
The live environment gives you a safe space to run commands. You can install RPM Fusion and test drivers without touching the disk. If the system becomes unstable, you can just reboot and start over.
Test the live ISO before you install. A broken live session means a broken installation.
Identify your chips
You need to know exactly which GPU and Wi-Fi chip are in your laptop. Generic names like "VGA compatible controller" don't help. You need the vendor and device IDs.
Here's how to identify the exact chip models before you guess which driver you need.
# Check GPU and Wi-Fi to see what the kernel sees
# -nn prints vendor IDs which help match hardware against driver lists
lspci -nn | grep -E 'VGA|Network'
The output will show lines like 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics]. Copy the vendor and device IDs. Search for these IDs on the Fedora Hardware Enablement list or the Linux hardware database. This tells you if the hardware is supported out of the box.
Check the vendor IDs. Generic names hide the details you need to find the right driver.
Enable RPM Fusion
Fedora excludes packages that violate licensing or patent restrictions. Proprietary drivers, multimedia codecs, and some firmware live in RPM Fusion. You need to enable this repository to get full hardware support.
Here's how to add RPM Fusion to your system so you can install proprietary drivers and codecs.
# Enable RPM Fusion free and non-free repositories
# RPM Fusion provides packages Fedora cannot ship due to licensing restrictions
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
This command downloads and installs the repository configuration files. The free repo contains open-source packages that Fedora excludes for policy reasons. The non-free repo contains proprietary drivers and codecs. Both are safe and widely used by the Fedora community.
Enable RPM Fusion early. Many hardware fixes depend on packages that aren't in the default repositories.
Install NVIDIA drivers
If you have an NVIDIA GPU, the open-source nouveau driver might work, but it often lacks performance and power management. The proprietary nvidia-driver package fixes this. Fedora provides this driver via RPM Fusion using the akmod package.
Here's how to install the proprietary NVIDIA driver and its dependencies.
# Install the proprietary NVIDIA driver and its dependencies
# akmod-nvidia builds the kernel module for your current kernel version automatically
sudo dnf install akmod-nvidia xorg-x11-drv-nvidia-cuda
The akmod-nvidia package contains the source code for the driver. When you install it, the system compiles the kernel module for your running kernel. This ensures the driver works even after kernel updates. The xorg-x11-drv-nvidia-cuda package provides the user-space libraries and CUDA support.
If you see Error: Transaction test error: package nvidia-driver conflicts with nouveau-dkms, the system is detecting a conflict. Remove the conflicting package first. Run sudo dnf remove nouveau-dkms before installing the NVIDIA driver.
Reboot after installing the NVIDIA driver. The kernel module needs to load on the next boot.
Update firmware
Modern laptops rely on firmware updates for hardware bugs. Wi-Fi drops, Bluetooth disconnects, and battery drain often come from outdated firmware. Fedora uses fwupd to manage these updates safely.
Here's how to check for and install firmware updates using fwupd.
# Update firmware for Wi-Fi, Bluetooth, and BIOS using fwupd
# fwupd provides vendor-signed firmware updates safely without flashing BIOS manually
fwupdmgr get-updates
If updates are available, run fwupdmgr update. This command downloads and installs the updates. Some updates require a reboot. Follow the prompts to complete the process. Firmware updates can fix hardware issues that no driver can solve.
Run fwupdmgr get-updates after every major system update. Firmware bugs often get patched months after the hardware ships.
Verify the configuration
After you install drivers and update firmware, you need to confirm everything is working. Don't assume the fix worked. Check the actual state of the hardware.
Run glxinfo | grep "OpenGL renderer" to verify the GPU driver is active. The output should show the NVIDIA or AMD renderer, not the software renderer. Run nmcli device wifi list to ensure Wi-Fi is scanning for networks. Run pactl list short sinks to check audio devices.
If the GPU driver failed to build, you might see llvmpipe in the OpenGL output. This means the system is using software rendering. Check the logs with journalctl -xeu akmods. The x flag adds explanatory text and the e flag jumps to the end. Most sysadmins type journalctl -xeu <unit> muscle-memory style.
Check the logs before you reboot. If the driver failed to build, the system might drop to a TTY on restart.
Common pitfalls
Secure Boot blocks unsigned modules
Secure Boot prevents unsigned kernel modules from loading. Fedora signs its own modules. Third-party modules like akmod-nvidia need a Machine Owner Key (MOK) to be trusted.
If you see modprobe: ERROR: could not insert 'nvidia': Required key not available, Secure Boot is blocking the driver. You must enroll the MOK key during the first boot after installing akmod-nvidia. The system will show a blue screen asking for a password. Enter the password you set during the MOK enrollment process. If you skip this step, the driver won't load.
Secure Boot is a security feature, not an enemy. Enroll the MOK key to keep Secure Boot enabled while using proprietary drivers.
Config files drift
Config files in /etc/ are user-modified. Files in /usr/lib/ ship with the package. Edit /etc/. Never edit /usr/lib/. If you edit a file in /usr/lib/, the next package update will overwrite your changes. Use /etc/ for customizations. The package manager manages /usr/lib/.
Trust the package manager. Manual file edits drift, snapshots stay.
Touchpad and trackpoint conflicts
Some laptops have both a touchpad and a trackpoint. The kernel might enable both, causing cursor jumps. Check libinput settings. You can disable the trackpoint in the BIOS or via xinput.
Run xinput list to find the device IDs. Run xinput disable <id> to test disabling a device. If the cursor stabilizes, make the change permanent in /etc/X11/xorg.conf.d/.
Test input devices in the live session. A broken touchpad makes installation painful.
Decision matrix
Use Intel integrated graphics when you want plug-and-play stability and the best battery life. Use AMD Radeon when you need open-source GPU acceleration without proprietary drivers. Use NVIDIA with RPM Fusion when you require CUDA support or specific game performance. Use the HWE kernel when your laptop is newer than the current Fedora release cycle. Stick to the standard kernel when your hardware is older than two years.
Check the hardware list before you buy. A laptop with a brand-new Wi-Fi chip might work, but it might also require a kernel update you don't want to manage.