You upgraded from Fedora 40 to 42 and the boot stops at the GRUB menu
You just downloaded the latest Fedora Workstation ISO, flashed it to a USB stick, and rebooted. The Fedora logo appears, the spinner turns for a moment, and then the screen goes black. Or maybe the installer loads but hangs on "Starting Anaconda" with no progress bar. You've tried three times. The hardware works fine with Windows or another Linux distro. Something is blocking the installer from reaching the desktop environment where the actual installation happens.
What's actually happening
The Fedora installer is called Anaconda. It runs inside a live environment loaded from the USB. When you boot, the kernel loads, initializes hardware, and starts the graphical installer. A crash or freeze usually means one of three things. The kernel cannot talk to your graphics hardware because of a driver mismatch. The ISO file is corrupted, so the installer tries to read garbage data and aborts. Or the system lacks the resources to run the graphical installer, though this is rare on modern hardware.
The installer doesn't have a full OS to fall back on. If the kernel panics or the display server fails, you get a black screen or a frozen cursor. You need to intervene at the boot stage or verify the media before the kernel even starts. The boot menu gives you control. You can change kernel parameters, switch to a text-based installer, or debug the failure before the system locks up.
Verify the ISO checksum
A corrupted download is the most common cause of installer crashes. Bit rot, network interruptions, or a browser caching error can leave the ISO incomplete. The installer will fail with obscure errors because it cannot find critical files. Verify the checksum before you burn the USB or blame the hardware.
Here's how to calculate the checksum and compare it to the official value.
sha256sum Fedora-Workstation-Live-x86_64-43-1.6.iso
# Compare this output against the SHA256 value on the Fedora download page
# A mismatch indicates corruption or an incomplete download
# Redownload the ISO if the hashes do not match exactly
The Fedora download page lists the SHA256 hash for every image. Copy the hash from the terminal and paste it next to the official value. They must match character for character. If they differ, delete the ISO and download it again.
A mismatched hash means the file is broken. Redownload the ISO before touching the boot parameters.
Bypass graphics drivers with nomodeset
Graphics drivers are the usual suspect when the installer freezes on the splash screen. The kernel attempts to load a driver for your GPU to enable high-resolution graphics. If the driver has a bug or conflicts with the hardware, the kernel panics or the display freezes. The nomodeset parameter tells the kernel to skip the GPU driver and use the basic BIOS or UEFI framebuffer instead. This reduces graphics performance but allows the installer to load.
Here's how to edit the boot parameters to add nomodeset.
- Boot from the USB and wait for the GRUB menu.
- Highlight the "Start Fedora Workstation" entry and press
eto edit. - Find the line starting with
linux. It usually ends withquiet. - Move the cursor to the end of that line and type a space followed by
nomodeset. - Press
F10orCtrl+Xto boot with the modified parameters.
# GRUB Edit Screen
linux /images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-43-1-6 nomodeset
# Append nomodeset to disable kernel mode setting for the GPU
# This forces the installer to use basic display drivers provided by firmware
# The installer will load with lower resolution but should avoid driver crashes
If the installer loads, proceed with the installation. The nomodeset parameter is temporary. It only applies to the installer session. The installed system will use the standard drivers unless you configure them differently.
Append nomodeset and boot. If the installer loads, the GPU driver was the blocker.
Switch to text mode installation
If the graphical interface fails to load entirely, you can use the text mode installer. Text mode runs a terminal user interface (TUI) that requires no graphics acceleration. It provides the same installation options as the GUI, including partitioning, user creation, and package selection. Text mode is also useful for headless servers or systems with minimal hardware.
Here's how to select text mode from the boot menu.
- Boot from the USB and wait for the GRUB menu.
- Select the "Troubleshooting" option and press Enter.
- Choose "Install Fedora Workstation in text mode" and press Enter.
- The installer will start in a terminal window. Follow the prompts to complete the installation.
# Troubleshooting Menu
Install Fedora Workstation in text mode
# Select this option to run the installer without a graphical display server
# The TUI installer uses ncurses and works on any terminal
# All installation features are available in text mode
Text mode installs the same system. The interface is different, the result is identical.
Recreate the boot media
Third-party flash tools sometimes corrupt the USB image. Some tools pad the image incorrectly, add boot sectors that conflict with the ISO, or fail to flush the write buffer. The result is a USB stick that appears to flash successfully but crashes during boot. Use dd to create a reliable image. dd writes the ISO bits exactly as they appear to the device.
Here's how to create a bootable USB using dd.
sudo dd if=Fedora-Workstation-Live-x86_64-43-1.6.iso of=/dev/sdX bs=4M status=progress oflag=sync
# bs=4M sets the block size for faster writes
# oflag=sync forces the OS to flush buffers to the USB device immediately
# status=progress shows the write speed so you know the operation is active
# Replace /dev/sdX with your actual USB device path
Identify the USB device path using lsblk before running the command. Do not use the wrong device path. dd will overwrite the target without confirmation. Wait for the command to finish. The progress indicator will stop and return to the prompt.
Trust dd. It writes bits exactly as they appear in the file.
Advanced debugging with rd.debug
If the installer crashes silently and you need to capture logs, enable debug mode. The rd.debug parameter tells the initramfs to output detailed logs to the console. The inst.debug parameter enables debug logging for Anaconda. These parameters help you identify the exact point of failure.
Here's how to enable debug mode and capture logs.
- Boot from the USB and edit the GRUB entry as described earlier.
- Append
rd.debug inst.debugto thelinuxline. - Boot the system. The console will show verbose output.
- If the installer crashes, switch to a virtual console by pressing
Ctrl+Alt+F2. - Check the logs in
/run/install/repo/logs/.
cat /run/install/repo/logs/anaconda.log
# View the Anaconda log for installation errors
# Look for lines marked ERROR or CRITICAL
# Copy the relevant lines for a bug report
The logs contain timestamps, component names, and error messages. Use this information to file a bug report or search for known issues. Debug mode slows down the installer. Use it only when you need to diagnose a failure.
Capture the logs. You cannot fix a silent crash without evidence.
Common pitfalls
Editing the wrong line in GRUB breaks the boot. The GRUB menu shows multiple lines. Only edit the line starting with linux. The initrd line loads the initial ramdisk. Modifying it can prevent the kernel from mounting the root filesystem.
Secure Boot can cause crashes on some hardware. Some UEFI implementations have bugs that reject signed modules or crash during the handoff. If the installer fails with a verification error, disable Secure Boot in the firmware settings. Fedora supports Secure Boot, but hardware bugs exist. Test with Secure Boot disabled to rule out firmware issues.
USB ports matter. USB 3 ports can sometimes cause compatibility issues with older kernels or specific controllers. Try a different USB port. USB 2 ports are more reliable for boot media. If the installer hangs on USB initialization, switch ports.
The nomodeset parameter is not a permanent fix for the installed system. It only affects the installer. If the installed system has graphics issues, you need to install proprietary drivers or configure the bootloader permanently. The installer fix does not carry over.
When to use this vs alternatives
Use nomodeset when the installer freezes on the graphical splash screen or shows a black screen after the logo.
Use inst.text when the graphical interface fails to load entirely or you are installing on a headless server.
Use sha256sum verification when the installer reports missing files or checksum errors during boot.
Use dd to create the boot media when third-party flash tools produce unbootable USB sticks.
Use rd.debug and inst.debug when the installer crashes silently and you need to capture logs for a bug report.
Use Secure Boot disable when the firmware rejects the boot loader or crashes during initialization.