How to Fix Ubuntu 24.04 Black Screen After Installing NVIDIA Driver 550

Installing a new graphics driver should make your screen sharper and your games smoother. On Ubuntu 24.04, the NVIDIA 550 driver sometimes does the opposite. You reboot, see the Ubuntu logo for a second, and then the screen goes completely black.

There is no login screen and no clear error. This is common after a driver upgrade, a kernel update, or a switch from Nouveau.

The good news is that your files are almost always safe. The system is usually running underneath the black screen. You just cannot see it because the graphics driver failed to load correctly. This guide walks you through safe recovery steps, from a simple terminal fix to a full clean reinstall of the driver.

Quick Answer

Boot into recovery mode or press Ctrl + Alt + F3 to open a terminal, log in, and run sudo apt purge nvidia-* && sudo ubuntu-drivers autoinstall to remove the broken 550 driver and install a working one. If Secure Boot is enabled, also enroll the MOK key or disable Secure Boot, because unsigned NVIDIA modules will be blocked and cause a black screen. Reboot after the install finishes.

Why Ubuntu 24.04 Shows a Black Screen After the NVIDIA 550 Install

Secure Boot Blocks the Driver Module

Ubuntu uses Secure Boot to stop unsigned code from loading during startup. The NVIDIA driver builds a kernel module on your machine. If that module is not signed, or if you skipped the Machine Owner Key enrollment screen during installation, the kernel will refuse to load it. Without the module, the display server has no driver to use.

Kernel and Driver Mismatch

Driver 550 needs matching kernel headers to build correctly. If you installed the driver right after a kernel update but before a reboot, the headers and the running kernel may not match. The build then fails quietly, and the next boot has no working graphics module.

Conflicts With Nouveau and Old Config Files

The open-source Nouveau driver and the NVIDIA driver cannot control the same card at the same time. Old files in /etc/X11/xorg.conf or leftover packages from driver 535 or 545 can also point the system to the wrong device. Wayland sessions on Ubuntu 24.04 add another layer, because NVIDIA support for Wayland is still sensitive to mode-setting settings.

Before You Start: Try These Quick Checks

Do these simple checks first. They take two minutes and sometimes save you a full reinstall.

1. Wait a full two minutes after the black screen appears. The first boot after a driver build can be slow.
2. Press Ctrl + Alt + F3. If a text login appears, your system is alive and you can fix it from the terminal.
3. Try a different cable or port. Use a direct HDMI or DisplayPort connection, not a dock, for testing.
4. Unplug extra monitors. Boot with only one display connected.
5. If you have both integrated and dedicated graphics, check your BIOS and set the primary display to the correct device for your setup.

Method 1: Fix the Driver From a Virtual Terminal

Step-by-Step Terminal Fix

1. At the black screen, press Ctrl + Alt + F3 and log in with your username and password. You will not see characters as you type your password. That is normal.
2. Check what driver is installed by running ubuntu-drivers devices and nvidia-smi. If nvidia-smi fails, the module did not load.
3. Remove the broken driver completely with sudo apt purge nvidia-driver-550 nvidia-* libnvidia-*.
4. Clean up leftover packages with sudo apt autoremove && sudo apt autoclean.
5. Update your package lists with sudo apt update.
6. Reinstall a recommended driver with sudo ubuntu-drivers autoinstall. This command picks the tested driver for your card instead of guessing a version.
7. Rebuild the early boot image with sudo update-initramfs -u.
8. Reboot with sudo reboot.

During the reinstall, watch for a blue Secure Boot screen that asks you to set a password for MOK enrollment. Write that password down. On the next boot, you must enter it once to enroll the key. Many black screen cases come only from skipping this step.

Enable NVIDIA Mode Setting

If the desktop returns but Wayland is unstable or the screen flickers, enable kernel mode setting, which Ubuntu 24.04 prefers for NVIDIA on Wayland.

1. Open the GRUB config with sudo nano /etc/default/grub.
2. Find the line that starts with GRUB_CMDLINE_LINUX_DEFAULT.
3. Add nvidia-drm.modeset=1 inside the quotes, keeping your other options.
4. Save the file, then run sudo update-grub and reboot.

You can also check the official guidance in the Ubuntu documentation for installing proprietary drivers to confirm the recommended process for your release.

Method 2: Use Recovery Mode When There Is No Terminal

If Ctrl + Alt + F3 does nothing, use the built-in recovery environment.

1. Restart the computer and hold Shift or tap Esc during boot to show the GRUB menu.
2. Select Advanced options for Ubuntu.
3. Choose the entry that ends with (recovery mode).
4. In the recovery menu, select network first to enable internet access.
5. Then select root to open a root shell.
6. Remount the system as writable with mount -o remount,rw /.
7. Run the same purge and reinstall commands from Method 1.
8. Type exit and choose resume, or simply run reboot.

Method 3: Boot With Nomodeset for One Session

The nomodeset option tells the kernel not to load graphics drivers during boot. It gives you a low-resolution desktop for one session, which is enough to fix the driver with the graphical tool.

1. Show the GRUB menu during boot.
2. Highlight the normal Ubuntu entry and press e to edit it.
3. Find the line that starts with linux and add nomodeset after quiet splash.
4. Press Ctrl + X or F10 to boot with this temporary change.
5. Once on the desktop, open Software & Updates and go to the Additional Drivers tab.
6. Select a tested NVIDIA driver, click Apply Changes, and reboot normally.

Do not make nomodeset permanent. It disables proper acceleration and hides the real problem.

For wider background on hybrid graphics and driver switching, our guide on how to keep Ubuntu updated safely from the terminal explains how kernel and driver updates should be timed together to avoid this mismatch.

Method 4: Fix Secure Boot and MOK Enrollment

If the driver installs without errors but nvidia-smi still says no devices were found, Secure Boot is the likely cause.

• Check Secure Boot status with mokutil --sb-state.
• Check if the module exists with lsmod | grep nvidia. An empty result means it did not load.
• Reinstall the driver and carefully complete the MOK enrollment on reboot, choosing Enroll MOK and entering the password you set during installation.
• As a test only, you can temporarily disable Secure Boot in BIOS to confirm the diagnosis. If the desktop appears, re-enable Secure Boot properly with signed modules instead of leaving it off long term.

The NVIDIA CUDA and driver installation guide for Linux also explains signing requirements in detail if you use drivers from NVIDIA directly instead of the Ubuntu packages.

Common Mistakes and Useful Tips

• Installing the .run file from the NVIDIA website on Ubuntu: This method fights with the package manager and often breaks on kernel updates. Prefer Ubuntu packages.
• Skipping the MOK password screen: If you set a Secure Boot password during install and then ignore the enrollment boot screen, the key is lost and the module stays unsigned.
• Mixing driver versions: Installing 550 over a half-removed 535 leaves conflicting libraries. Always purge before a clean install.
• Tip: Keep a recent backup and note your working driver version. After a good boot, run nvidia-smi and save the output so you know what to return to.
• Tip: If you use a laptop with Optimus, check prime-select query and set it to nvidia or on-demand as needed for your workload.

Conclusion

A black screen after installing NVIDIA driver 550 on Ubuntu 24.04 looks serious, but it is usually just a driver that failed to load, a Secure Boot key that was never enrolled, or a leftover config file pointing to the wrong place. Your personal files and installed programs are not damaged by this fault.

Start with a virtual terminal or recovery mode, purge the broken driver cleanly, let Ubuntu install the recommended driver for your hardware, and complete the MOK enrollment on the next boot. Add mode setting if Wayland is unstable, and avoid mixing manual and packaged drivers in the future. With those steps, most systems return to a normal desktop in under twenty minutes.

Frequently Asked Questions

Can I fix the black screen without losing my files?

Yes. The driver fix only removes graphics packages. Your documents, settings, and other programs stay untouched. You do not need to reinstall Ubuntu for this problem.

Why does the black screen return after a kernel update?

The NVIDIA module must be rebuilt for each new kernel. If the build fails because headers are missing, the next boot has no module. Installing linux-headers-$(uname -r) and reinstalling the driver usually stops it from repeating.

Should I use driver 550 or a newer driver instead?

Use the driver marked as tested or recommended in the Additional Drivers tool for your card. A newer number is not always better for older hardware, and stability matters more than chasing the latest release.

What if Ctrl + Alt + F3 does not show a login?

Use recovery mode from the GRUB menu instead. It loads a basic driver and gives you a root shell where you can purge and reinstall the NVIDIA packages safely.

Is it safe to disable Secure Boot permanently?

It will often make the driver load, but it lowers your boot security. The better fix is to keep Secure Boot on and enroll the MOK key correctly so the signed module is trusted.