You plug the HDMI cable into your laptop and the external monitor stays black
You check the cable, swap the port, and GNOME Settings still shows only one display. Or worse, the second screen flickers, locks at 60Hz when it should do 144Hz, or disappears after a suspend cycle. The frustration is immediate. You need that extra screen space to finish the work, and the system is refusing to cooperate.
What's actually happening
The display stack in Fedora is a chain of handoffs. The kernel DRM subsystem detects the physical connection and negotiates the link parameters. The display server (Wayland or X11) reads that information and tells the compositor where to draw the pixels. If the monitor is dead, the break is usually in one of three places. The kernel never saw the cable. The display server saw the cable but decided not to use it. Or the driver is missing or misconfigured.
Fedora defaults to Wayland with open-source drivers. That combination works for 95% of hardware out of the box. When it fails, the fix is almost always a configuration tweak or a driver swap, not a kernel recompile.
Diagnose the connection state
Start by checking whether the kernel sees the monitor. This bypasses the desktop environment and talks directly to the hardware interface. Run this command to list every output port and its status.
# List all DRM connectors and their connection state
for d in /sys/class/drm/card*-*/status; do echo "$d: $(cat $d)"; done
If you see disconnected, the kernel does not detect the link. Check the cable, the port, and the monitor input source. If you see connected, the hardware link is good. The issue is in the display server configuration or the driver.
Trust the kernel status. If the kernel says disconnected, no amount of GUI clicking will bring the screen back.
Configure X11 outputs
Fedora uses Wayland by default, but some users run X11 sessions. The tools differ depending on your session type. Check your session first.
# Check the current display server protocol
echo $XDG_SESSION_TYPE
If the output is x11, use xrandr to manage displays. Query the outputs to find the name of the inactive port.
# Query X11 outputs to find the name of the disconnected or inactive port
xrandr --query
# Enable the output at its native resolution
xrandr --output HDMI-1 --auto
# Position the secondary screen to the right of the laptop display
xrandr --output HDMI-1 --auto --right-of eDP-1
The --auto flag tells X11 to select the highest resolution mode advertised by the monitor's EDID data. If the monitor reports multiple modes, --auto picks the largest. If you need a specific refresh rate, append --rate 144. For example, xrandr --output HDMI-1 --mode 2560x1440 --rate 144. This is useful when the default mode locks at 60Hz due to bandwidth limitations or cable quality.
Run journalctl -xeu gdm after a failed detection. The compositor logs usually explain why it rejected the output.
Configure Wayland outputs
On Wayland, xrandr commands often fail with xrandr: Failed to get size of gamma for output default. This error means you are running xrandr on a Wayland session. Wayland compositors handle output management internally.
Open GNOME Settings and navigate to Displays. If the monitor appears there, click it, select the resolution, and click Apply. If the monitor is missing in GNOME Settings but the kernel shows connected, the compositor might be ignoring it due to a driver quirk.
Wayland compositors like Mutter handle output management differently than X11. Mutter queries the DRM kernel interface and builds a scene graph. If a monitor is connected but not shown, Mutter might be treating it as a duplicate of an existing output or ignoring it due to a rotation mismatch. Check journalctl -u gdm for lines containing mutter and output. You may see warnings about failed to set mode or invalid connector. These logs often reveal that the kernel driver is rejecting the mode request.
Run journalctl -xeu gdm and grep for mutter. Read the actual error before guessing.
Install NVIDIA proprietary drivers
NVIDIA GPUs are the most common source of multi-monitor headaches on Fedora. The open-source nouveau driver lacks full support for modern multi-monitor features and variable refresh rates. You need the proprietary driver. Fedora does not ship proprietary drivers by default. You must enable RPM Fusion and install the driver package.
# Enable RPM Fusion free and non-free repositories
sudo dnf install -y \
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
# Install the NVIDIA driver with automatic kernel module building
sudo dnf install -y akmod-nvidia
# Reboot to load the new kernel modules
sudo reboot
After installing the driver, Wayland requires a kernel parameter to function correctly with NVIDIA hardware. Without this flag, you may see black screens or fallback to X11. Edit the GRUB configuration to add the parameter.
# /etc/default/grub
# Add nvidia-drm.modeset=1 to the end of the GRUB_CMDLINE_LINUX line
GRUB_CMDLINE_LINUX="... nvidia-drm.modeset=1"
Regenerate the GRUB configuration and reboot.
# Regenerate the GRUB configuration file
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Snapshot the system before the driver install. A botched NVIDIA install can leave you unable to boot. Run this from a backup VM first if you can.
Persist the configuration
xrandr commands are temporary. They reset on reboot. To persist the layout, use the desktop environment's profile system or a startup script. GNOME saves display profiles automatically when you apply changes in Settings. For X11 users who need a script, create an autostart entry.
# Create a desktop entry for the display script
mkdir -p ~/.config/autostart
cat > ~/.config/autostart/monitors.desktop << EOF
[Desktop Entry]
Type=Application
Name=Configure Monitors
Exec=/home/$USER/bin/setup-monitors.sh
X-GNOME-Autostart-enabled=true
EOF
Trust the package manager. Manual file edits drift, snapshots stay. Use GNOME's built-in profiles when possible.
Verify the fix
Confirm the fix by checking the active outputs and resolution.
# Verify active outputs and modes on X11
xrandr --query | grep -E 'connected|current'
# Check Wayland output state via kernel
cat /sys/class/drm/card*-*/status
Reboot before you debug. Half the time the symptom is gone after a clean module load.
Common pitfalls and errors
xrandr: Failed to get size of gamma for output default: You are runningxrandron a Wayland session. Switch to X11 or use GNOME Settings.NVRM: Xid (PCI:0000:01:00): 79: This is an NVIDIA GPU error. Checkdmesg | grep -i nvidia. AnXid 13usually indicates a GPU hang, often caused by a driver mismatch or power state issue. AnXid 31suggests a timeout in the command stream. These errors point to driver stability, not display configuration.- Editing
/usr/lib/configs: Config files in/etc/are user-modified. Files in/usr/lib/ship with the package. Edit/etc/. Never edit/usr/lib/. - Laptop lid close: GNOME power settings might turn off the external display when the lid closes. Check Settings > Power.
- SELinux denials: If a display helper is blocked, check
journalctl -t setroubleshoot. SELinux denials show up with a one-line summary. Read those before disabling SELinux.
Run journalctl -t setroubleshoot if SELinux is blocking a display helper. Read the denial before disabling SELinux.
When to use which tool
Use xrandr when you are on an X11 session and need to script display layouts.
Use GNOME Settings when you are on Wayland and want to configure resolution and position.
Use akmod-nvidia when you have an NVIDIA GPU and need full multi-monitor support on Wayland.
Use nvidia-drm.modeset=1 when the NVIDIA driver is installed but Wayland fails to start or shows black screens.
Use udevadm trigger --subsystem-match=drm when the kernel detects the cable but the display server has not updated its state.
Stay on the open-source driver when you have Intel or AMD hardware and the default configuration works.