Fixing Garuda GNOME Live ISO Boot Failure on NVIDIA RTX 5060 Ti

The Problem

I was setting up a new desktop (Intel i5-9400F, NVIDIA RTX 5060 Ti, Gigabyte Z390 M) and booting the Garuda GNOME live ISO garuda-gnome-linux-zen-260309.iso gave me nothing — just a blinking underscore in the top-left corner and a dead display. GDM never came up.

Having run Garuda GNOME on my laptop for nearly three years I had no intention of switching to KDE, so I dug in.

What worked out of the box: KDE Gaming 260309 booted fine — which strongly pointed at a GNOME/GDM-specific display stack issue rather than a kernel or hardware problem.

Gathering Clues

I SSHed into the live media and pulled the GDM service status:

$ sudo systemctl status gdm.service

● gdm.service - GNOME Display Manager
     Active: active (running) since Sun 2026-04-26 19:45:02 UTC; 1s ago
   Main PID: 131472 (gdm)

Apr 26 19:45:03 garuda-gnome gnome-session-i[131674]: Failed to upload environment to systemd: \
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 26 19:45:03 garuda-gnome gnome-session-i[131674]: Failed to start unit gnome-session@gnome.target: \
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Apr 26 19:45:03 garuda-gnome gdm[131472]: Gdm: GdmDisplay: Session never registered, failing
Apr 26 19:45:03 garuda-gnome gdm[131472]: Gdm: GdmLocalDisplayFactory: maximum number of display \
  failures reached. Giving up.

GDM was starting, spawning a Wayland session, and immediately dying because gnome-session couldn't talk to systemd's D-Bus name. The process tree was fine — the real failure was upstream.

The decisive clue came from trying to switch virtual consoles:

$ chvt 1
Couldn't get a file descriptor referring to the console.

That's the kernel telling you it can't properly address the console device — which happens when the GPU hasn't been handed off correctly during boot. Insert surprised Pikachu face: the NVIDIA driver was blocking kernel DRM initialisation, so the entire display stack was broken before GDM even tried.

The Fix — Step by Step

Step 1 — Boot the live ISO with DRM modesetting disabled

At the GRUB boot menu, press e to edit the boot entry and append to the kernel line:

nomodeset nvidia_drm.modeset=0 nouveau.modeset=0

This forces the kernel to skip GPU modesetting entirely and fall back to a framebuffer console. GNOME comes up in a degraded but functional state — enough to run the installer.

Step 2 — Install Garuda normally

With the display now working, proceed through the Calamares installer as usual.

Step 3 — Fix the post-install initramfs stall

After installation, the first reboot stalled at "generating ramdisk / initramfs". Edit the GRUB boot entry again and add nomodeset after quiet loglevel=3:

quiet loglevel=3 nomodeset

The system will now boot into the installed environment.

Step 4 — Install NVIDIA drivers and verify

Once inside the installed system, run a full update and install the proprietary drivers:

garuda-update
# then install nvidia if not already pulled in:
sudo pacman -S nvidia-dkms nvidia-utils

Verify the driver loaded correctly:

nvidia-smi

You should see your GPU listed with the driver version and no errors.

Step 5 — Re-enable DRM modesetting permanently

Edit /etc/default/grub and set:

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nvidia_drm.modeset=1"

Regenerate the GRUB config:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Reboot.

Result

Display comes up at full 2560×1440, NVIDIA drivers are active, GDM and GNOME shell run without any issues.

Why This Happens

The RTX 5060 Ti (GB206, Lovelace architecture) requires the proprietary NVIDIA driver to manage modesetting. The live ISO boots with driver=nonfree but the kernel-level DRM handoff still races — especially on newer GPUs — leaving the console subsystem in a state where no process can open a VT file descriptor. GNOME's Wayland compositor depends on that console path during startup, so the entire session fails before rendering a single frame.

The nomodeset flag bypasses the DRM layer completely for the install, and nvidia_drm.modeset=1 hands it back cleanly once the full driver stack is in place post-install.

System Reference