Monitor doesn't wake after suspend - Driver 550.163.01 on Debian 13 with X11

Graphics / Linux Linux
1

System Information:

  • OS: Debian 13 “Trixie” (fresh upgrade from Debian 12)
  • Driver Version: 550.163.01
  • Display Server: X11
  • Kernel: 6.12.48+deb13-amd64

Problem Description:
After upgrading from Debian 12 to Debian 13, monitors do not wake up after suspend. The system appears to resume (fans spin up, lights come on) but displays remain black and unresponsive.

Reproducible Steps:

  1. Fresh Debian 13 installation with NVIDIA 550.163.01 drivers
  2. Run sudo systemctl suspend
  3. Wake system (keyboard/mouse/power button)
  4. Result: Black screens, system appears hung

Key Finding:
Uninstalling NVIDIA drivers completely resolves the issue - suspend/resume works perfectly with nouveau drivers.

Attempted Solutions (all failed):

  • Added nvidia.NVreg_PreserveVideoMemoryAllocations=1
  • Added nvidia.NVreg_EnableS0ixPowerManagement=1
  • Added nvidia.NVreg_EnableGpuFirmware=0
  • Enabled nvidia-suspend.service, nvidia-hibernate.service, nvidia-resume.service
  • Installed nvidia-suspend-common package

Expected Behavior:
Monitors should wake up properly after suspend, as they do with nouveau drivers.

Additional Notes:
This appears to be a regression - suspend/resume worked fine on Debian 12 with earlier NVIDIA drivers. Issue persists with X11 (not Wayland-specific).

I will attach nvidia-bug-report.sh output if this helps with diagnosis.

2

First of all, this is my 1st post here. I am not a developer, I am a retired mechanical engineer, who runs Debian.

Debian 13.2 Xfce

Kernel 6.12.57+deb13-amd64

NVIDIA 550.163.01

Two desktop machines here with Asus motherboards, AMD CPUs, GeForce GT 1030 cards.

My main machine shows the exact same behavior as described by mika9.

Black screen with mouse courser after resume. Purging Nvidia and using nouveau - no problem.

The 2nd machine (my back up) - NO PROBLEM waking up.

I could provide inxi reports of both computers and journalctl files for the suspend and resume time.

Karl

3

Hello,

First, as the power management is closely linked to BIOS quality, ensure that you have an up to date BIOS. For example, Ryzen need AGESA 1.9.0.0 to operate in mode S0ix. So, check for BIOS updates, and apply them if required.

Edit /etc/modprobe.d/nvidia-options.conf

#options nvidia-current NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660

# To grant performance counter access to unprivileged users, uncomment the following line:
#options nvidia-current NVreg_RestrictProfilingToAdminUsers=0
options nvidia-current NVreg_RestrictProfilingToAdminUsers=0

# Uncomment to enable this power management feature:
#options nvidia-current NVreg_PreserveVideoMemoryAllocations=1
options nvidia-current NVreg_PreserveVideoMemoryAllocations=1

# Uncomment to enable this power management feature:
#options nvidia-current NVreg_EnableS0ixPowerManagement=1
options nvidia-current NVreg_EnableS0ixPowerManagement=1

and uncomment the two last options (NVreg_PreserveVideoMemoryAllocations=1 and NVreg_EnableS0ixPowerManagement=1) as above.

I also uncommented NVreg_RestrictProfilingToAdminUsers=0, but it’s not needed by suspend, hibernate…

Reboot is mandatory.

Greetings

4

Hi @mika9 , thanks for reporting this issue.
Could you please help to attach a bug report once you see this issue? If the system stays unresponsive, please take a bug report after a reboot. If you are able to ssh into the repro system from another system, please take a bug report when it is in the hung state with the safe mode option.