The screen is dim after the monitor goes to sleep and does not return to full brightness

English Applications
1

After the latest update…
The screen is dim after the monitor goes to sleep and does not return to full brightness.
When I log out and log back in the screen is at full brightness.
What could be the cause?

Operating System: openSUSE Tumbleweed 20260324
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.19.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i5-10400F CPU @ 2.90GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor: NVIDIA GeForce GTX 1650
Manufacturer: ASUS
2

Your Nvidia GForce GTX 1650. I had a similar issue with a 1060 version & never did manage to get to the bottom of it. So I had to give up on letting my machine sleeping to resolve it - as lots of searching & tweaking didn’t help. My machine now sleeps happily now I no longer use the Nvidia card!

From a quick search AI suggests: A grey screen when resuming from sleep on an NVIDIA graphics card may be caused by issues with the NVIDIA drivers or settings related to power management. You can try adjusting the driver settings or updating to the latest version to see if that resolves the problem.

Good luck.

3

@rektal Can you post the output from cat /proc/driver/nvidia/params | sort and inxi -GSaz.

4

Just wanted to chime in and say that I too have the same problem. Nvidia RTX 3050 6gb. On Tumbleweed.

5

Post the same output, I see no issues here on GNOME with three screens and a Quadro RTX4000, I do use the run file and open driver (595.58.03). On Leap 16.0 I have a Quadro T400 that uses the rpms and open driver, no issues either.

6

Yes.

inxi -GSaz
System:
  Kernel: 6.19.9-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.19.9-1-default
    root=UUID=2f1c4e3c-38b9-45e3-9fde-4e808e939077 splash=silent
    systemd.show_status=yes quiet security=selinux selinux=1
    rd.driver.blacklist=nouveau mitigations=auto
  Desktop: KDE Plasma v: 6.6.3 tk: Qt v: N/A info: frameworks v: 6.24.0
    wm: kwin_wayland tools: avail: xscreensaver vt: 3 dm: SDDM Distro: openSUSE
    Tumbleweed 20260324
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1650] vendor: Gigabyte driver: nvidia
    v: 580.142 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-11; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
    lanes: 16 ports: active: DVI-D-1 empty: DP-1,HDMI-A-1 bus-ID: 01:00.0
    chip-ID: 10de:2188 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: nvidia
    unloaded: modesetting,nouveau,vesa failed: nv alternate: fbdev
    gpu: nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DVI-D-1 model: Idek Iiyama PLX2483H serial: <filter>
    built: 2014 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 92 gamma: 1.2
    size: 531x299mm (20.91x11.77") diag: 609mm (24") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.142
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
    memory: 3.91 GiB display-ID: :1.0
  API: Vulkan v: 1.4.341 layers: 3 device: 0 type: discrete-gpu
    name: NVIDIA GeForce GTX 1650 driver: nvidia v: 580.142 device-ID: 10de:2188
    surfaces: N/A device: 1 type: cpu name: llvmpipe (LLVM 21.1.8 256 bits)
    driver: mesa llvmpipe v: 26.0.2 (LLVM 21.1.8) device-ID: 10005:0000
    surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr


cat /proc/driver/nvidia/params | sort
CoherentGPUMemoryMode: ""
CreateImexChannel0: 0
DeviceFileGID: 481
DeviceFileMode: 432
DeviceFileUID: 0
DmaRemapPeerMmio: 1
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
EnableDbgBreakpoint: 0
EnableGpuFirmware: 18
EnableGpuFirmwareLogs: 2
EnableMSI: 1
EnablePCIeGen3: 0
EnablePCIERelaxedOrderingMode: 0
EnableResizableBar: 0
EnableS0ixPowerManagement: 1
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
ExcludedGpus: ""
GpuBlacklist: ""
GrdmaPciTopoCheckOverride: 0
IgnoreMMIOCheck: 0
ImexChannelCount: 2048
InitializeSystemMemoryAllocations: 1
KMallocHeapMaxSize: 0
MemoryPoolSize: 0
ModifyDeviceFiles: 1
NvLinkDisable: 0
OpenRmEnableUnsupportedGpus: 1
PreserveVideoMemoryAllocations: 1
RegisterPCIDriver: 1
RegistryDwords: ""
RegistryDwordsPerDevice: ""
ResmanDebugLevel: 4294967295
RmLogonRC: 1
RmMsg: ""
RmNvlinkBandwidthLinkCount: 0
RmProfilingAdminOnly: 1
S0ixPowerManagementVideoMemoryThreshold: 256
TemporaryFilePath: "/var/tmp"
UsePageAttributeTable: 4294967295
VMallocHeapMaxSize: 0

This also happens when I have the default option in my settings to dim the screen after 5 minutes. The screen remains dim after I move the mouse. This happens sometimes.

7

@rektal Hi the only two things that pop out to me are the age of the monitor and S0ix;

  • Idek Iiyama PLX2483H ← 2014
  • EnableS0ixPowerManagement: 1 ← Is this enabled in the BIOS?

Does the GPU support S0ix? See here for how to check https://download.nvidia.com/XFree86/Linux-x86_64/595.58.03/README/powermanagement.html

8

Will do, if I can access this pc again (I’m on my laptop right now). But for what its worth: my monitor is also a very old samsung. Maybe you are on to something. It doesn’t seem to happen on my Hisense TV when I think about it…

9

Everything works fine before the latest update including sleep mode.
I do not have this function in BIOS.

The IIyama monitor is old but it works flawlessly. I have Windows 11 on a different SSD and it doesn’t have this problem. I primarily use Linux. Maybe I should use an earlier snapshot or kernel to see if the problem persists.

10

I checked previous kernel 6.19.8-1-default and the is no problem.
I’ll check it out for a while and if everything is fine, I’ll stick with it.

11

Then it’s likely a upower or DE issue. I suggest check the logs and also versions installed of the various power tools.