Interactive Troubleshooter

Published: Oct 18, 2026

Ubuntu Black Screen After Nvidia Driver Install - Secure Boot Diagnostic

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Comprehensive diagnostic troubleshooting tree for resolving black screen hangs, login loops, or display manager lockups on Ubuntu systems following Nvidia proprietary driver installation, kernel module loading failures, and UEFI Secure Boot blocks.

Full Diagnostic Tree & Step-by-Step Overview

What is the exact visual state or error behavior observed after booting Ubuntu following the Nvidia driver installation?

System hangs on a pure black screen with a blinking underscore cursor or frozen desktop logo
System boots into a login loop, returning back to the login screen after entering valid credentials
Graphical user interface fails entirely, dropping directly into a basic TTY login prompt or emergency mode
System crashes or freezes during early initramfs boot sequence with kernel taint or module errors

What happens when you press Ctrl+Alt+F3 at the black screen to access a virtual terminal (TTY)?

TTY terminal opens successfully, allowing root login and command execution
Screen remains completely unresponsive or flashes black without rendering any text login prompt
Error message displays indicating 'NVRM: GPU at PCI... Board has a fatal error' or kernel panic
System reboots automatically or shuts down shortly after hitting the black screen hang

Resolving UEFI Secure Boot Module Blocking (MOK Key Enrollment)

Solution:

Root Cause: UEFI Secure Boot Rejection of Unsigned Proprietary Kernel Modules

When UEFI Secure Boot is enabled in motherboard firmware, the Linux kernel enforces strict cryptographic signature verification on all kernel modules (.ko). Proprietary Nvidia drivers compiled locally via DKMS are unsigned by default unless a Machine Owner Key (MOK) is created, enrolled, and verified during installation. When the system boots, the kernel refuses to load nvidia.ko and nvidia-modeset.ko, causing the display server to crash and hang on a black screen.

Diagnostic Verification:

Access TTY via Ctrl+Alt+F3, log in, and check kernel logs for signature rejections:

bash
dmesg | grep -iE "secure|lockdown|nvidia|sign"

Look for messages stating: Loading of tainted module failed: tainted module and 'EE' signature required or Modprobe nvidia failed.

Step-by-Step Fix:

1.Check Secure Boot Status:

Run the MokManager status query:

bash
mokutil --sb-state

If it reports SecureBoot enabled, proceed to enroll keys or sign modules.

2.Enroll Existing MOK Keys or Create New Ones:

If prompted during installation, you may have set a MOK password. If not, generate and sign modules manually:

bash
sudo update-secureboot-policy --enroll-key

Alternatively, disable Secure Boot temporarily in your motherboard BIOS/UEFI settings (Security > Secure Boot > Disabled) to restore immediate graphical boot.

3.Re-sign Nvidia DKMS Modules:

If keys exist, rebuild and sign the installed Nvidia kernel modules:

bash
sudo dpkg-reconfigure nvidia-dkms-<version>

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Always complete the MOK password prompt during sudo apt install nvidia-driver-<version> when Secure Boot is enabled in UEFI.

Fixing Display Manager and Wayland/X11 Compositor Conflicts

Solution:

Root Cause: Display Manager Service Crash due to Nvidia Modesetting Failure

Ubuntu's default display manager (gdm3 for GNOME, lightdm for XFCE/Unity) initializes the graphical display server. When the proprietary Nvidia driver fails to initialize KMS (Kernel Mode Setting) or conflicts with Wayland compositors, the display manager service crashes in an infinite restart loop, leaving the screen blank without rendering the login greeter.

Diagnostic Verification:

Access TTY via Ctrl+Alt+F3 and check the status of the display manager service:

bash
systemctl status gdm3

Check system journal logs for service crash loops:

bash
journalctl -u gdm3 -b 0 --no-pager

Step-by-Step Fix:

1.Switch from Wayland to X11 Display Server:

Edit the GDM custom configuration file to disable Wayland enforcement:

bash
sudo nano /etc/gdm3/custom.conf

Uncomment the line #WaylandEnable=false by removing the hash symbol (#).

Save (Ctrl+O, Enter) and exit (Ctrl+X).

2.Restart the Display Manager Service:

bash
sudo systemctl restart gdm3

3.Force Nvidia Modesetting Activation:

Open GRUB configuration:

bash
sudo nano /etc/default/grub

Add nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT:

text
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

Save and update GRUB:

bash
sudo update-grub

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Keep GNOME Shell extensions updated, as outdated extensions frequently trigger GDM compositor crashes upon Nvidia context switches.

Resolving Hardware Faults, Power State Corruptions, and ACPI Conflicts

Solution:

Root Cause: ACPI Power Management and Hybrid GPU (Optimus) Switching Faults

Laptops featuring hybrid graphics (Intel/AMD integrated GPU paired with Nvidia discrete GPU) often encounter black screen hangs because Advanced Configuration and Power Interface (ACPI) power states fail to initialize the Nvidia card properly during kernel module loading. This leaves the PCIe bus in an unresponsive state.

Diagnostic Verification:

Inspect kernel error logs for ACPI or PCIe link training failures:

bash
dmesg | grep -iE "acpi|pcieport|nvidia|refused"

Check hybrid graphics status using prime-select:

bash
prime-select query

Step-by-Step Fix:

1.Switch to Intel/AMD Integrated Graphics Mode (For Laptops):

Force integrated profile to bypass discrete GPU initialization during boot:

bash
sudo prime-select on-demand

*(Or switch entirely to intel: sudo prime-select intel).*

2.Add ACPI Kernel Parameters to GRUB:

Open GRUB configuration:

bash
sudo nano /etc/default/grub

Add acpi_osi= ! acpi_osi="Windows 2009" or acpi_backlight=vendor to GRUB_CMDLINE_LINUX_DEFAULT.

Update GRUB:

bash
sudo update-grub

3.Purge and Clean Hybrid Switching Daemons:

Reinstall nvidia-prime packages to restore correct switch scripts:

bash
sudo apt install --reinstall nvidia-prime

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Ensure your laptop BIOS is updated to the latest vendor release to fix buggy ACPI DSDT tables.

Purging and Clean Reinstalling Nvidia Drivers via Recovery Root Shell

Solution:

Root Cause: Corrupted Driver Package Dependencies or Partial Installation State

Interrupted package installations, failed DKMS builds, or conflicting residual files from previous open-source nouveau drivers leave the system in a broken package dependency state, corrupting the initialization sequence and causing immediate boot hangs.

Diagnostic Verification:

Access GRUB recovery menu, select root (Drop to root shell prompt), and check package states:

bash
dpkg -l | grep -iE "nvidia|nouveau"

Check for unconfigured packages:

bash
sudo dpkg --configure -a

Step-by-Step Fix:

1.Mount Root Filesystem as Read-Write (If in recovery mode):

bash
mount -o remount,rw /

2.Purge All Existing Nvidia Driver Packages Completely:

bash
sudo apt-get purge "*nvidia*"
sudo apt-get autoremove --purge

3.Blacklist Nouveau Open-Source Driver:

Create a blacklist configuration file:

bash
echo -e "blacklist nouveau\noptions nouveau modeset=0" | sudo tee /etc/modprobe.d/blacklist-nouveau.conf
sudo update-initramfs -u

4.Install Stable Recommended Nvidia Driver Cleanly:

Install the recommended stable proprietary driver package for your GPU:

bash
sudo ubuntu-drivers install
sudo apt-get install nvidia-driver-535

*(Replace 535 with your hardware's recommended driver branch).*

5.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Avoid mixing graphics drivers from personal PPA repositories; stick to Ubuntu's official graphics drivers PPA or standard apt repositories.

What occurs specifically when you enter your password on the login screen?

Screen flickers black for two seconds and instantly loops back to the exact same login prompt
Screen goes permanently black with mouse cursor visible and movable
Desktop environment loads partially (top bar missing, icons distorted, or background grey)
Error: 'The system is running in low-graphics mode' warning dialog appears

Fixing User Profile Permissions and .Xauthority Ownership Login Loops

Solution:

Root Cause: Broken User Session File Permissions or .Xauthority Ownership

A login loop is often caused when user session files (such as ~/.Xauthority, ~/.ICEauthority, or /tmp directory mounts) lose correct ownership permissions (root instead of the user UID). When GDM attempts to write session auth tokens, permission denial causes session termination and an immediate return to the login greeter.

Diagnostic Verification:

Log into TTY (Ctrl+Alt+F3), inspect ownership of user home authority files:

bash
ls -la ~ | grep -i authority

Check if ownership belongs to root:root instead of username:username.

Step-by-Step Fix:

1.Correct Ownership Permissions on Authority Files:

Fix ownership of hidden session files in your home directory:

bash
sudo chown $USER:$USER ~/.Xauthority ~/.ICEauthority
sudo chmod 600 ~/.Xauthority

2.Check Disk Space on Root Partition:

Full root partitions (/) prevent display managers from writing session logs:

bash
df -h /

Clean package cache if disk is 100% full:

bash
sudo apt clean

3.Reset GNOME Desktop Settings and Extensions:

If user configuration is corrupt, reset GNOME state:

bash
dconf reset -f /org/gnome/

4.Restart Display Manager:

bash
sudo systemctl restart gdm3

Prevention & Long-Term Monitoring:

Never run GUI applications using sudo directly from a user login session, as this alters ownership of files inside ~/.config/ and ~/.cache/.

Resolving Black Screen with Movable Mouse Cursor After Login

Solution:

Root Cause: X11 / Wayland Session Initialization Failure or Missing Display Configuration

When a black screen appears immediately after login with a responsive mouse cursor, the display manager successfully authenticated the user, but the X server or Wayland compositor failed to launch the desktop shell window manager (gnome-shell, mutter, or kwin). This is typically caused by corrupted display configuration profiles (monitors.xml) or incompatible Nvidia OpenGL libraries.

Diagnostic Verification:

Access TTY (Ctrl+Alt+F3), check user session logs for window manager crashes:

bash
journalctl -b 0 -u gdm3 --grep="gnome-shell"

Check Xorg log files for fatal errors:

bash
cat ~/.local/share/xorg/Xorg.0.log | grep -iE "error|fatal"

Step-by-Step Fix:

1.Delete Corrupted Monitor Configuration Profiles:

Remove stale multi-monitor XML layout files:

bash
rm -f ~/.config/monitors.xml

2.Re-link Nvidia OpenGL Library Alternatives:

Ensure Ubuntu's alternative linker points correctly to Nvidia libraries rather than Mesa fallback:

bash
sudo update-alternatives --set glx /usr/lib/nvidia

3.Reinstall Ubuntu Desktop Meta-Package:

Restore missing desktop environment dependencies:

bash
sudo apt install --reinstall ubuntu-desktop gnome-shell

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Avoid modifying raw Xorg configuration files (xorg.conf) manually unless configuring advanced multi-GPU rendering pipelines.

Fixing Broken GNOME Shell and Missing Top Panel After Nvidia Install

Solution:

Root Cause: Incompatible GNOME Shell Extensions or Broken Mutter Compositor

Proprietary Nvidia driver updates frequently alter OpenGL and Vulkan rendering pipelines. If installed GNOME Shell extensions (such as Dash to Dock, User Themes, or AppIndicator) are incompatible with the active Mutter compositor version under the new Nvidia driver, the shell crashes upon startup, leaving a broken desktop with no top panel or launcher.

Diagnostic Verification:

Check system journal for GNOME Shell segmentation faults:

bash
journalctl /usr/bin/gnome-shell -b 0 --no-pager

Step-by-Step Fix:

1.Disable All GNOME Shell Extensions via TTY:

Temporarily disable all user extensions to isolate rendering conflicts:

bash
gsettings set org.gnome.shell disable-user-extensions true

2.Purge Incompatible Extension Packages:

Remove problematic extensions from local directories:

bash
rm -rf ~/.local/share/gnome-shell/extensions/*

3.Restart GNOME Shell Compositor:

Press Alt+F2, type r, and hit Enter (in graphical session), or restart GDM3 service from TTY:

bash
sudo systemctl restart gdm3

4.Update System Extension Manager:

Once logged in successfully, update all desktop extensions to versions compatible with your current Ubuntu release.

Prevention & Long-Term Monitoring:

Verify extension compatibility against Ubuntu LTS and GNOME version matrices before performing major driver upgrades.

Fixing 'Low-Graphics Mode' and Fallback Xorg Configuration Errors

Solution:

Root Cause: Invalid or Outdated xorg.conf File Conflicts

When Ubuntu boots and detects an invalid or manually generated /etc/X11/xorg.conf configuration file that references non-existent device paths or deprecated driver strings (such as Driver "nv" or Driver "vesa"), the X server refuses to start and triggers the low-graphics mode fallback dialog.

Diagnostic Verification:

Check for the existence of legacy Xorg config files:

bash
ls -la /etc/X11/xorg.conf

Read Xorg error logs for unrecognized device directives:

bash
cat /var/log/Xorg.0.log | grep -iE "error|failed|driver"

Step-by-Step Fix:

1.Remove or Rename Deprecated xorg.conf Files:

Move legacy configuration files out of the active X11 directory:

bash
sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

2.Generate Clean Nvidia Xorg Configuration:

Let Nvidia auto-detect and generate a valid configuration profile:

bash
sudo nvidia-xconfig

3.Verify Permissions and Owner of X11 Directory:

bash
sudo chown -R root:root /etc/X11/xorg.conf.d/

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Modern Ubuntu releases and Nvidia drivers handle displays dynamically via KMS; avoid creating manual xorg.conf files unless required for specific multi-monitor rotation setups.

What specific diagnostic indicator or service state is shown when entering the emergency TTY terminal?

Command 'nvidia-smi' returns 'NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver'
Command 'modprobe nvidia' fails with error: 'finit_module: Operation not permitted' or 'Required key not available'
Kernel panics or freezing occurs during boot due to Plymouth splash screen rendering bugs
APT package manager reports broken dependencies between kernel headers and nvidia-dkms modules

Fixing 'NVIDIA-SMI Failed' Driver Communication Errors

Solution:

Root Cause: Kernel Version Mismatch with Compiled DKMS Nvidia Modules

The nvidia-smi utility cannot communicate with the driver because the currently running Linux kernel version does not match the kernel version for which the Nvidia DKMS modules were built. This occurs when an automated background apt upgrade updates the Linux kernel (linux-image) but fails to compile the matching Nvidia DKMS module before rebooting.

Diagnostic Verification:

Run uname -r to check the active running kernel version:

bash
uname -r

Check installed DKMS module status:

bash
dkms status

Look for mismatched kernel versions or added/built status failures.

Step-by-Step Fix:

1.Rebuild DKMS Modules for Active Kernel:

Trigger manual compilation for all registered DKMS modules:

bash
sudo dkms autoinstall

Alternatively, force rebuild specific nvidia version:

bash
sudo dkms install nvidia/535.183.01 -k $(uname -r)

2.Update Initial RAM Disk (initramfs):

bash
sudo update-initramfs -u -k all

3.Reboot the System:

bash
sudo reboot

4.Verify Driver Communication:

Open terminal and confirm successful communication:

bash
nvidia-smi

Prevention & Long-Term Monitoring:

Ensure unattended-upgrades is configured correctly or verify dkms hooks execute successfully during kernel upgrades.

Resolving 'Required Key Not Available' Module Insertion Failures

Solution:

Root Cause: UEFI Secure Boot Module Loading Restriction (Key Not Available)

When modprobe nvidia fails with Required key not available (Error code -126), the Linux kernel security keyring has rejected the proprietary module because it lacks a valid signature recognized by the system's UEFI Secure Boot certificate database.

Diagnostic Verification:

Inspect kernel error logs during manual module insertion:

bash
sudo modprobe nvidia
dmesg | tail -n 15

Look for: Loading of module failed: Required key not available.

Step-by-Step Fix:

1.Enroll MOK Certificate into Kernel Keyring:

If you have generated a MOK certificate previously (MOK.priv and MOK.der), enroll it into the system:

bash
sudo mokutil --import /var/lib/shim-signed/mok/MOK.der

Provide a temporary password when prompted.

2.Complete MOK Enrollment at System Reboot:

Reboot the computer (sudo reboot).

The BlueMOK Management utility will appear on screen before Ubuntu boots.

Select Enroll MOK, view key, continue, and enter the password you created.

3.Alternatively, Disable Secure Boot in UEFI:

Enter motherboard BIOS/UEFI settings during boot and disable Secure Boot to bypass cryptographic module checks entirely.

4.Verify Module Loading:

After reboot, verify module presence:

bash
   lsmod | grep nvidia

Prevention & Long-Term Monitoring:

Maintain automated MOK signing scripts (such as shim-signed hooks) to sign DKMS modules on every kernel update automatically.

Fixing Plymouth Splash Screen and Early KMS Render Hangs

Solution:

Root Cause: Plymouth Graphical Boot Splash Render Freeze

Plymouth is Ubuntu's graphical boot splash screen manager. When proprietary Nvidia drivers are installed, Plymouth often conflicts with early Kernel Mode Setting (KMS), causing the boot sequence to freeze right before the login manager initializes.

Diagnostic Verification:

Edit GRUB during boot (e key) and remove quiet splash parameters to view verbose kernel boot messages. Observe if the boot hangs specifically at Started Nvidia Persistence Daemon or during framebuffer initialization.

Step-by-Step Fix:

1.Disable Plymouth Splash Screen Permanently:

Open GRUB configuration:

bash
sudo nano /etc/default/grub

Remove quiet splash from GRUB_CMDLINE_LINUX_DEFAULT, leaving only parameter flags like nvidia-drm.modeset=1.

Save and update GRUB:

bash
sudo update-grub

2.Disable Plymouth Service via Systemd:

bash
sudo systemctl disable plymouth-quit-wait.service

3.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Running headless or high-performance workstations benefit from verbose boot logging (quiet splash removed) for rapid diagnostics.

Resolving Broken Kernel Headers and DKMS Build Dependencies

Solution:

Root Cause: Missing or Mismatched Linux Kernel Headers

DKMS requires matching kernel header packages (linux-headers-$(uname -r)) to compile proprietary C/C++ driver source code against the running kernel ABI. If kernel headers are missing or out of sync, DKMS builds fail silently during driver installation, resulting in missing module binaries and a subsequent black screen.

Diagnostic Verification:

Check if matching kernel headers are installed:

bash
dpkg -l | grep linux-headers

Test manual DKMS build compilation:

bash
sudo dkms build nvidia/535.183.01

Step-by-Step Fix:

1.Install Matching Kernel Headers and Build Essentials:

bash
sudo apt update
sudo apt install --reinstall build-essential linux-headers-$(uname -r)

2.Purge Broken Nvidia DKMS Entries:

bash
sudo dkms remove nvidia/535.183.01 --all

3.Reinstall Nvidia Driver Package Cleanly:

bash
sudo apt install --reinstall nvidia-driver-535

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Ensure linux-generic meta-packages are installed so kernel updates pull corresponding header dependencies automatically.

What early boot error or panic signature is outputted during the initramfs phase?

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Initramfs unpacking failed: Decoding failed or compressed data stream error
System drops to (initramfs) busybox prompt due to UUID mismatch or storage controller driver drop
ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP._DSM]

Rebuilding Corrupted Initramfs Images After Nvidia Driver Installation

Solution:

Root Cause: Corrupted or Incomplete Initial RAM Disk (initramfs)

During driver installation, post-installation scripts execute update-initramfs to bundle necessary kernel modules into the initial boot image. If power is interrupted or disk space exhausts during this phase, an incomplete initramfs image is written, causing early boot kernel panics and failure to mount root filesystems.

Diagnostic Verification:

Boot via Ubuntu Live USB, mount your root partition, chroot into the system, and check initramfs file integrity:

bash
sudo ls -lh /boot/initrd.img-*

Verify if file sizes appear abnormally small (e.g., under 10MB).

Step-by-Step Fix:

1.Boot into Live USB and Enter Chroot Environment:

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

2.Regenerate Initramfs for All Installed Kernels:

bash
sudo update-initramfs -u -k all

3.Update GRUB Bootloader Configuration:

bash
sudo update-grub

4.Exit Chroot and Reboot:

bash
exit
sudo reboot

Prevention & Long-Term Monitoring:

Maintain at least 1GB of free space on the /boot partition to accommodate large kernel and initramfs images during updates.

Fixing Compressed Data Stream and CPIO Unpacking Errors

Solution:

Root Cause: Corrupted Compression Tool Binaries or Full Disk Storage

Initramfs generation relies on compression tools like lz4, gzip, or zstd. If these binary utilities are corrupted or if temporary build directories run out of inodes during apt install, compressed archives fail to unpack during early boot, triggering a hard freeze.

Diagnostic Verification:

Check available inode count on root partition:

bash
df -i /

Test initramfs extraction manually in a live environment:

bash
unmkinitramfs /boot/initrd.img-$(uname -r) /tmp/initrd_test

Step-by-Step Fix:

1.Reinstall Essential Compression and Initramfs Tools:

Boot via Live USB/Chroot and reinstall core compression utilities:

bash
sudo apt install --reinstall initramfs-tools gzip lz4 zstd coreutils

2.Clean Stale Temporary Build Files:

bash
sudo rm -rf /var/tmp/* /tmp/*

3.Force Clean Re-creation of Initramfs:

bash
sudo update-initramfs -c -k $(uname -r)

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Regularly clean old unused kernel packages using sudo apt autoremove --purge to reclaim /boot partition inodes.

Repairing Busybox Initramfs Prompt and UUID Mount Failures

Solution:

Root Cause: Partition UUID Mismatch in GRUB Root Parameter

If driver installation scripts or manual edits accidentally alter partition tables, UUIDs inside /etc/fstab or GRUB configuration mismatch the actual partition identifiers on disk, dropping the boot sequence into a (initramfs) busybox debug shell.

Diagnostic Verification:

At the (initramfs) prompt, list storage devices:

bash
blkid

Compare UUIDs listed with those defined in /boot/grub/grub.cfg and /etc/fstab.

Step-by-Step Fix:

1.Boot into Live USB to Edit Configuration Files:

Mount your root partition and inspect /etc/fstab:

bash
cat /mnt/etc/fstab

2.Update Partition UUIDs:

Replace incorrect UUID strings with valid values returned by blkid.

3.Update GRUB UUID Pointers:

Chroot into the system and regenerate grub config:

bash
sudo update-grub

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Avoid editing block device identifiers or cloning partitions without updating dependent UUID references in fstab and grub.

Bypassing ACPI PEG0/PEGP DSDT Faults on Optimus Laptops

Solution:

Root Cause: Motherboard ACPI DSDT Bug in PCIe Root Port Power States

Some laptop motherboard firmware contain buggy ACPI Digital Definition Source Tables (DSDT) that fail when the Linux kernel attempts to power on discrete Nvidia PCIe graphics (PEG0/PEGP) during boot, triggering unhandled ACPI exceptions and system freezes.

Diagnostic Verification:

Check dmesg for ACPI exceptions related to PCI Express graphics:

bash
dmesg | grep -iE "acpi.*error|dsm|pep"

Step-by-Step Fix:

1.Disable Discrete GPU Power Management in GRUB:

Open GRUB configuration:

bash
sudo nano /etc/default/grub

Add acpi_rev_override=1 or pcie_aspm=off to GRUB_CMDLINE_LINUX_DEFAULT.

Save and update GRUB:

bash
sudo update-grub

2.Blacklist Nouveau and Enable Nvidia Persistence Daemon:

bash
sudo systemctl enable nvidia-persistenced

3.Update Motherboard BIOS:

Flash your laptop's BIOS/UEFI to the latest vendor version to resolve ACPI table bugs.

4.Reboot the System:

bash
sudo reboot

Prevention & Long-Term Monitoring:

Keep laptop firmware updated, as hardware vendors frequently issue ACPI bugfixes specifically for Linux kernel compatibility.

Related Diagnostic Guides

SSH Connection Refused on Port 22 But Service Running - Firewall Tree

Linux Boot Stuck at GRUB Rescue After Windows Update - Dual Boot Fix

SmartScreen Can't Be Reached Right Now Error Fix - Windows Diagnostic Guide

Account Locked After Too Many Attempts in Microsoft 365 - Admin Unlock Tree

Windows 11 Wi-Fi Connected but No Internet? How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website