Kokil Thapa - Professional Web Developer in Nepal
Freelancer Web Developer in Nepal with 15+ Years of Experience

Kokil Thapa is an experienced full-stack web developer focused on building fast, secure, and scalable web applications. He helps businesses and individuals create SEO-friendly, user-focused digital platforms designed for long-term growth.

Fix Ubuntu Black Screen Issues

By Kokil Thapa | Last reviewed: September 2026

You need to fix Ubuntu black screen issues when the machine powers on but never reaches a usable desktop. The cursor may blink. The monitor may stay dark after the Plymouth splash. On production servers and developer workstations alike, this failure blocks work entirely. I've hit this on Ubuntu 22.04 and 24.04 LTS boxes while deploying Ubuntu server environments and maintaining client infrastructure. This guide walks through the causes, the fastest recovery paths, and the fixes that stick.

Why does Ubuntu show a black screen after boot or login?

A black screen is rarely random. Something in the boot chain or display stack fails silently. The kernel loads. systemd starts services. Then the graphics stack or desktop environment crashes before you see a login prompt.

Common triggers include:

  • Proprietary NVIDIA or AMD drivers that mismatch the running kernel
  • A failed gdm3 or lightdm display-manager session after an unattended upgrade
  • Wayland vs Xorg incompatibility on laptops with hybrid Intel+NVIDIA GPUs
  • Corrupted /etc/X11/xorg.conf left over from manual driver installs
  • Full disk or broken filesystem on /home, preventing session files from loading
  • Secure Boot blocking unsigned third-party kernel modules

Before you reinstall Ubuntu, spend ten minutes isolating the layer that failed. That saves hours and keeps your data intact. For broader install problems, see the Ubuntu installation troubleshooting guide.

Ubuntu Boot Chain — Black Screen Failure PointsBIOS / UEFISecure BootGRUBKernel paramsKernelinitramfssystemdServicesDisplay Managergdm3 / lightdm / sddmGPU Driver StackNVIDIA / AMD / IntelGNOME Desktop Session
Fix Ubuntu black screen issues by identifying which boot-chain layer fails before the desktop loads

How do you fix Ubuntu black screen issues from GRUB?

GRUB is your first rescue tool. You do not need a live USB if the bootloader still appears. Hold Shift during boot on BIOS systems, or tap Esc on UEFI machines, to open the GRUB menu.

Boot with nomodeset

Highlight your Ubuntu entry. Press e to edit boot parameters. Find the line starting with linux. Append these flags before the quiet splash tokens:

nomodeset acpi=off

Press F10 to boot once with those settings. If the desktop loads, your GPU driver or kernel mode-setting is the culprit. Do not stop here — make the fix permanent.

Enter recovery mode

From GRUB, choose Advanced options for Ubuntu. Pick the previous kernel if a recent update triggered the black screen. Select recovery mode, then root — drop to a root shell with network access if possible.

Run these commands in order:

  1. Remount the root filesystem read-write: mount -o remount,rw /
  2. Update package lists: apt update
  3. Reinstall the display manager: apt install --reinstall gdm3
  4. Rebuild initramfs for all kernels: update-initramfs -u -k all
  5. Reboot: reboot

On systems where GRUB itself is damaged, the Ubuntu boot repair guide covers Boot-Repair from a live session. That tool fixes broken EFI entries and missing kernels without wiping /home.

What display drivers cause Ubuntu black screen problems?

GPU drivers are the number-one cause I see on developer laptops and office workstations. Ubuntu 24.04 LTS ships with open-source nouveau for NVIDIA cards. Many users switch to proprietary drivers for CUDA or multi-monitor setups. A kernel update then leaves the old module behind.

ScenarioSymptomsFix
NVIDIA proprietary mismatchBlack screen after login, cursor visiblePurge and reinstall matching driver version
Hybrid Intel + NVIDIA laptopBlack screen on Wayland, works on XorgSwitch session or install nvidia-prime
AMD amdgpu regressionBlack screen after kernel 6.x upgradeBoot older kernel, hold package, file bug
Intel iGPU onlyBlack screen after suspendDisable Wayland in GDM custom.conf
VirtualBox / VMware guestBlack screen at loginReinstall guest additions, increase VRAM

Fix NVIDIA black screen from a TTY

If you see a blinking cursor but no login screen, switch to a text console. Press Ctrl+Alt+F3. Log in with your username and password.

Purge conflicting NVIDIA packages and reinstall the recommended driver:

sudo apt purge 'nvidia-*' -y
sudo apt autoremove -y
sudo ubuntu-drivers autoinstall
sudo reboot

Check which driver Ubuntu recommends before installing manually:

ubuntu-drivers devices

For headless servers running GPU passthrough or remote desktop, driver issues are less common. Still, I verify graphics packages after every Ubuntu security update cycle on mixed fleets.

Recovery Workflow — Fix Ubuntu Black ScreenBlack ScreenCtrl+Alt+F3Open TTYLogin ShellDiagnosedmesg | grep drmFix Driver / GDMpurge, reinstall, resetDesktop OK
Step-by-step recovery workflow to fix Ubuntu black screen issues without reinstalling the OS

Switch from Wayland to Xorg

GNOME on Ubuntu defaults to Wayland on 22.04 and 24.04 LTS. Some proprietary drivers still misbehave under Wayland. Edit the GDM configuration:

sudo nano /etc/gdm3/custom.conf

Uncomment or add this line under [daemon]:

WaylandEnable=false

Restart the display manager:

sudo systemctl restart gdm3

You can also pick Ubuntu on Xorg from the gear icon on the login screen. That tests Xorg without a permanent config change. The Ubuntu GNOME desktop guide explains session types in more detail.

How do you recover Ubuntu when the desktop will not load?

When GRUB recovery and TTY access both fail, escalate to a live USB. Download the current Ubuntu 24.04 LTS ISO. Boot into Try Ubuntu. Open a terminal and identify your root partition:

lsblk -f

Mount it — replace /dev/sda2 with your actual root partition:

sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt

Inside the chroot, you can reinstall critical packages, reset passwords, or remove broken configs. Common chroot fixes:

  • Remove stale Xorg config: rm /etc/X11/xorg.conf
  • Reinstall desktop metapackage: apt install --reinstall ubuntu-desktop
  • Fix broken packages: dpkg --configure -a && apt -f install
  • Regenerate GRUB: update-grub

Check disk space before blaming drivers. A full root partition causes silent session failures:

df -h /

If usage is above 95%, clear old kernels and journal logs:

sudo journalctl --vacuum-size=200M
sudo apt autoremove --purge

On production EC2 instances where I run Deployer 7 pipelines for client sites, disk exhaustion after log rotation misconfiguration has caused similar symptoms. The fix is operational, not graphical. See Ubuntu server monitoring for prevention.

Read logs while the screen is black

From any TTY or chroot session, pull the last boot messages:

journalctl -b -1 -p err
dmesg | tail -50
cat /var/log/Xorg.0.log | grep EE

Lines tagged (EE) in the Xorg log point to driver or config errors. Kernel DRM errors in dmesg confirm GPU module failures. Official Ubuntu desktop troubleshooting documentation lists additional log locations for GNOME Shell crashes.

GPU Driver Choice vs Black Screen RiskOpen Sourcenouveau (NVIDIA)Low break riskamdgpu (AMD)Kernel tiedi915 (Intel)Most stableWeaker 3D perfProprietarynvidia-driver-550Breaks on kernel bumpamdgpu-proMedium riskCUDA / gamingBest GPU perfPin kernel if neededMatch driver version to running kernel after every update
Open-source versus proprietary GPU drivers and their impact when you fix Ubuntu black screen issues

How do you prevent Ubuntu black screen issues after updates?

The black screen often arrives the morning after unattended-upgrades installs a new kernel. The old NVIDIA module no longer matches. Prevention beats recovery every time.

Hold kernel packages during driver transitions

While testing a new proprietary driver, hold the kernel metapackage:

sudo apt-mark hold linux-image-generic linux-headers-generic

Release the hold once drivers are confirmed working:

sudo apt-mark unhold linux-image-generic linux-headers-generic

Understanding the full apt update workflow on Ubuntu helps you spot pending kernel changes before rebooting.

Keep one known-good kernel

Never delete all previous kernels immediately. GRUB keeps them under Advanced options. If a new kernel black-screens, boot the prior one from TTY or GRUB. Then remove the bad kernel or fix the driver against it.

Disable Secure Boot for unsigned modules

Proprietary NVIDIA modules require Secure Boot signing or MOK enrollment. If you skip enrollment during install, the module silently fails. Either enroll the MOK key when prompted, or disable Secure Boot in UEFI firmware. The NVIDIA Unix driver documentation covers signing steps for enterprise deployments.

Automate post-update checks on servers

For headless Ubuntu servers running PHP-FPM, MySQL, and Nginx, graphics rarely matter. Still, I run a simple post-reboot health check in cron after maintenance windows. It confirms SSH, web stack, and queue workers respond. Details live in our Linux system administration service and the Nginx on Ubuntu install guide.

Developers should also verify toolchain versions after recovery. A broken desktop often means missed Docker installs on Ubuntu or pending PHP version upgrades that were scheduled alongside the kernel bump.

Decision Tree — Fix Ubuntu Black Screen IssuesCan you reach GRUB?NoLive USB + Boot-RepairYesRecovery / nomodesetTTY works (F3)?NoChroot from live USBYesPurge GPU driverReinstall gdm3Reboot and verify
Decision tree to choose the fastest path when you fix Ubuntu black screen issues on 22.04 or 24.04 LTS

What tools and commands help diagnose a black screen fast?

Keep a short command checklist saved offline. When the screen is black, you cannot browse for answers. These commands work from any TTY session on Ubuntu 22.04 and 24.04 LTS.

systemctl status gdm3
systemctl status display-manager
lsmod | grep nvidia
ubuntu-drivers list
journalctl -u gdm3 --since today
systemd-analyze blame

If gdm3 shows failed, read the full unit log with journalctl -u gdm3 -b. A common fix is resetting the GDM state directory for your user:

sudo rm -rf /var/lib/gdm3/.config
sudo systemctl restart gdm3

For permission problems that block session startup after a manual chown, see Ubuntu file permissions explained. Wrong ownership on ~/.Xauthority or ~/.config produces a black screen that looks like a driver bug.

Remote teams can paste log output into a JSON formatter tool or share via SSH from a second machine. If SSH works but the local display does not, the problem is strictly graphical. Focus on drivers and GDM, not networking. The Ubuntu network troubleshooting guide covers the opposite case — no network, working display.

After recovery, run a full system tune-up. Clearing swap, trimming SSDs, and disabling unnecessary startup apps reduce the chance of session timeouts on low-RAM machines. The Ubuntu performance tuning guide covers those steps. For developer workstations, the Ubuntu for developers guide sets up a stable baseline before you install GPU-heavy tooling.

I maintain several sister sites on shared EC2 infrastructure — legal-tech portals like Notary Kathmandu and translation platforms — where uptime depends on predictable server reboots. Desktop black screens are a different beast, but the discipline is the same: know your rollback path before you apply updates. Our Adventure Third Pole Trek booking platform runs on a similar Deployer 7 pipeline where post-deploy smoke tests catch failures early.

Key Takeaways

  • Boot GRUB with nomodeset to confirm a GPU driver or mode-setting failure before making permanent changes.
  • Use Ctrl+Alt+F3 to reach a TTY, then purge and reinstall NVIDIA packages with ubuntu-drivers autoinstall.
  • Switch GDM from Wayland to Xorg when hybrid laptops black-screen after login on Ubuntu 24.04 LTS.
  • Keep at least one previous kernel in GRUB Advanced options as an instant rollback after bad updates.
  • Check disk space and read /var/log/Xorg.0.log for (EE) errors before assuming hardware failure.
  • Document your working driver version and hold kernel packages during driver transitions on production machines.

People Also Ask

Why does Ubuntu go black after login but the mouse cursor still works?

A visible cursor with a black background usually means GDM started but the GNOME shell or GPU compositor crashed. The display server is partially alive. Switch to TTY with Ctrl+Alt+F3, check journalctl -u gdm3, and try switching from Wayland to Xorg. Proprietary NVIDIA drivers cause this most often after kernel updates.

How do I fix a black screen after updating Ubuntu?

Reboot and select the previous kernel from GRUB Advanced options. Once booted, reinstall your GPU driver to match the new kernel, run update-initramfs -u -k all, and reboot again. If no previous kernel works, boot a live USB and chroot into the root partition to purge and reinstall graphics packages.

Can a full disk cause an Ubuntu black screen?

Yes. When the root partition reaches 100% capacity, GDM and GNOME cannot write session files or cache data. The screen stays black or loops back to login. Boot into recovery mode or TTY, run df -h, and free space with apt autoremove, journal vacuum, and old log cleanup.

Does reinstalling Ubuntu fix black screen problems?

Reinstallation works but destroys your setup time. Driver purges, GDM resets, and kernel rollbacks fix most black screens in under thirty minutes without touching /home. Reinstall only when filesystem corruption or repeated failed upgrades leave the system unrecoverable even from a live USB chroot.

Get your Ubuntu workstation back online

Most Ubuntu black screen issues resolve with GRUB recovery, a TTY session, and a clean driver reinstall. You rarely need to wipe the disk. Start with nomodeset, read the Xorg log, and keep one known-good kernel as insurance. If your team runs Ubuntu servers or developer fleets in Nepal and needs hands-on help after a bad upgrade cycle, contact us for support and maintenance. For a full desktop baseline before you customise, start with the Ubuntu desktop complete guide and the essential Ubuntu terminal commands reference.

Frequently Asked Questions

Something in the boot chain or display stack fails silently after the kernel loads. Common triggers include proprietary NVIDIA or AMD drivers mismatching the running kernel, a failed gdm3 session after unattended upgrades, Wayland versus Xorg incompatibility on hybrid Intel plus NVIDIA laptops, corrupted /etc/X11/xorg.conf from manual driver installs, a full root disk blocking session files, or Secure Boot blocking unsigned third-party kernel modules.

Hold Shift on BIOS systems or tap Esc on UEFI machines to open GRUB. Press e on your Ubuntu entry, find the linux line, append nomodeset acpi=off before quiet splash, then press F10 to boot once. If the desktop loads, your GPU driver is likely the culprit. For a permanent fix, choose Advanced options, enter recovery mode, remount root read-write, run apt update, reinstall gdm3, rebuild initramfs with update-initramfs -u -k all, and reboot.

nomodeset tells the kernel not to load GPU mode-setting drivers early in boot. Append it to GRUB boot parameters when you suspect a graphics driver or kernel mode-setting failure is causing the black screen.

Press Ctrl+Alt+F3 to switch to a text console TTY. Log in with your username and password, then run driver fixes, reinstall packages, or read logs without needing a graphical desktop.

From a TTY with Ctrl+Alt+F3, purge conflicting NVIDIA packages with sudo apt purge nvidia-* -y, run sudo apt autoremove -y, then sudo ubuntu-drivers autoinstall to install the recommended driver. Check recommendations first with ubuntu-drivers devices. A kernel update often leaves the old proprietary module behind while a mismatched nvidia module loads, producing a black screen after login with a visible cursor. Reboot after reinstalling.

Yes, when proprietary drivers misbehave under Wayland on Ubuntu 22.04 or 24.04 LTS, especially hybrid Intel plus NVIDIA laptops. Edit /etc/gdm3/custom.conf and set WaylandEnable=false under the daemon section, then restart gdm3 with sudo systemctl restart gdm3. You can also pick Ubuntu on Xorg from the gear icon on the login screen to test without a permanent change. NVIDIA proprietary mismatches often black-screen on Wayland but work on Xorg.

Yes. When root reaches capacity, GDM and GNOME cannot write session or cache files, so the screen stays black or loops at login. Check with df -h / and free space via apt autoremove --purge, sudo journalctl --vacuum-size=200M, and log cleanup from recovery mode or TTY.

Reboot and select the previous kernel from GRUB Advanced options. Once booted via TTY or recovery mode, reinstall your GPU driver to match the new kernel, run update-initramfs -u -k all, and reboot again. Unattended-upgrades often installs a new kernel overnight while the old NVIDIA module no longer matches. If no previous kernel works, boot a live Ubuntu 24.04 LTS USB, chroot into the root partition, and purge plus reinstall graphics packages.

A visible cursor with a black background usually means GDM started but the GNOME shell or GPU compositor crashed. The display server is partially alive. Switch to TTY with Ctrl+Alt+F3, check journalctl -u gdm3, and try switching from Wayland to Xorg. Proprietary NVIDIA drivers cause this most often after kernel updates leave a module mismatch.

Reinstallation works but wastes setup time and is rarely necessary. Driver purges, GDM resets, and kernel rollbacks fix most black screens in under thirty minutes without touching /home. Reinstall only when filesystem corruption or repeated failed upgrades leave the system unrecoverable even from a live USB chroot session.

Download the Ubuntu 24.04 LTS ISO, boot Try Ubuntu, identify the root partition with lsblk -f, mount it at /mnt along with /boot/efi if needed, bind-mount dev, proc, sys, and run, then chroot into /mnt. Inside chroot, remove stale Xorg config with rm /etc/X11/xorg.conf, reinstall ubuntu-desktop, run dpkg --configure -a and apt -f install for broken packages, and regenerate GRUB with update-grub.

Hold kernel packages during driver transitions with sudo apt-mark hold linux-image-generic linux-headers-generic until drivers are confirmed working, then unhold. Keep at least one previous kernel in GRUB Advanced options for instant rollback. For proprietary NVIDIA modules, enroll the MOK key when prompted during install or disable Secure Boot in UEFI firmware, since unsigned modules fail silently otherwise.

From any TTY, run systemctl status gdm3, lsmod | grep nvidia, ubuntu-drivers list, and journalctl -u gdm3 --since today. Pull boot errors with journalctl -b -1 -p err, dmesg | tail -50, and cat /var/log/Xorg.0.log | grep EE for driver config failures. If gdm3 failed, reset its state with sudo rm -rf /var/lib/gdm3/.config and restart gdm3. Wrong ownership on ~/.Xauthority or ~/.config can mimic a driver bug.

From GRUB recovery mode or a TTY, remount root read-write with mount -o remount,rw /, run apt update, then apt install --reinstall gdm3. Rebuild initramfs with update-initramfs -u -k all and reboot. If gdm3 shows failed in systemctl status, read the full log with journalctl -u gdm3 -b, remove /var/lib/gdm3/.config if state is corrupted, and restart with sudo systemctl restart gdm3.

Proprietary NVIDIA kernel modules require Secure Boot signing or MOK enrollment during installation. If you skip enrollment, the module silently fails and can produce a black screen after boot. Either complete MOK key enrollment when the installer prompts, or disable Secure Boot in UEFI firmware settings. This is a common oversight on developer laptops switched from open-source nouveau to proprietary drivers for CUDA or multi-monitor setups.

Share this article

0 Comments

Leave a comment

Your email is not published. Comments appear once they have been read. Sign in to have your details filled in.

Quick Contact Options
Choose how you want to connect me: