At irregular intervals, my screen goes dark for half a second

… then everything returns to normal. This happens several times a day, even in the middle of writing or surfing. There is nothing unusual in the log file. What could it be?

btw: I had been using the same HDMI cable for years with a different distro until recently: this effect never occurred. So I don’t think the HDMI cable is the problem.

inxi -Fnzy                                                                                  ✔
System:
  Kernel: 6.18.8-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.5.5 Distro: Manjaro Linux
Machine:
  Type: Desktop System: LENOVO product: 12X9001AGE v: ThinkCentre M75t Gen 5
    serial: <superuser required>
  Mobo: LENOVO model: 3317 v: NOK serial: <superuser required> Firmware: UEFI
    vendor: LENOVO v: M4RKT31A date: 07/22/2025
CPU:
  Info: 8-core model: AMD Ryzen 7 8700G w/ Radeon 780M Graphics bits: 64
    type: MT MCP cache: L2: 8 MiB
  Speed (MHz): avg: 2404 min/max: 423/5177 cores: 1: 2404 2: 2404 3: 2404
    4: 2404 5: 2404 6: 2404 7: 2404 8: 2404 9: 2404 10: 2404 11: 2404 12: 2404
    13: 2404 14: 2404 15: 2404 16: 2404
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 driver: amdgpu v: kernel
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    dri: radeonsi gpu: amdgpu resolution: 3840x2160~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.4-arch1.1
    renderer: AMD Radeon 780M Graphics (radeonsi phoenix LLVM 21.1.6 DRM 3.64
    6.18.8-1-MANJARO)
  API: Vulkan v: 1.4.335 drivers: radv surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor driver: snd_pci_ps
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio driver: snd_hda_intel
  API: ALSA v: k6.18.8-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.4.10 status: active
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
  IF: wlp7s0 state: down mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: enp11s0f1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb type: USB
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 3.66 TiB used: 724.1 GiB (19.3%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL81T0HFLB-00BLL
    size: 953.87 GiB
  ID-2: /dev/sda vendor: HGST (Hitachi) model: HTS541010A9E680
    size: 931.51 GiB
  ID-3: /dev/sdb vendor: SanDisk model: SDSSDH3 2T00 size: 1.82 TiB
Partition:
  ID-1: / size: 937.53 GiB used: 222.17 GiB (23.7%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 328 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 512 MiB used: 3.2 MiB (0.6%) file: /swapfile
Sensors:
  System Temperatures: cpu: 35.8 C mobo: 32.2 C gpu: amdgpu temp: 29.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.5 GiB used: 6.45 GiB (21.1%)
  Processes: 431 Uptime: 3h 44m Shell: Zsh inxi: 3.3.40
    ~ 

Have you tried a different HDMI cable just to be certain?

1 Like

It could be caused by power dips or spikes, or perhaps RF interference being picked up by the HDMI cable; my display sometimes does this when the timer for the uplighter clicks on (inductive load, as it’s mercury vapour running via a magnetic ballast).

Just my 2p worth. :wink:

1 Like

Not yet. But i will.

If that’s the cause, I think it should have happened earlier.
But I’ll try a different HDMI cable.

1 Like

Not necessarily.

Regardless, trying a different HDMI cable will tell you something about the issue, even if it merely confirms the old cable is not the problem. It is a tried and true method of Fault finding. The first rule is don’t assume, confirm.

2 Likes

I do have the same issue with both of my monitors but with display port cables and I have a UPS so that should regulate any kind of power issue.
It would be extremely unlikely for both cables to suddenly have issues at basically the same time.

It doesn’t happen too frequently to me, only once or maybe twice a day(rarely) and some days are completely fine.

Some info on my setup from another post, but I do switch to the proprietary driver as well fairly regularly, haven’t noticed if it happens on both driver or one specific one:

I’ve only used manjaro for a couple of months daily and I have other more important issues that need fixing so I haven’t had time to look into this at all since it is a fairly minor annoyance.

Thanks for the info. Good to know that i am not alone with this annoyance.
Btw I have changed the HDMI-cable, so i will see if it happens again.

2 Likes

I changed the HDMI-cable (another hi-class-product), but the problem is still here.

1 Like

Hi @gloewa
Since you’ve already ruled out cables, it might be worth looking at the software side. AMD’s integrated graphics have a power saving feature called PSR (Panel Self Refresh) that’s known to cause exactly this - brief blackouts at random intervals.
:man_shrugging:

3 Likes

Good, now we can completely ignore the cable, and press on, breaking the problem into small bits… See above. :backhand_index_pointing_up:

1 Like

I must admit that I have also recently been experiencing this issue, although it hasn’t been enough to bother me, so I haven’t done any chasing up (apart from looking in my system log, which revealed nothing).

Anyway, hopefully @musdus may have found the cause of the issue:

The issue was resolved on an EndeavourOS system by disabling PSR, although it was more than a year ago:

I’m a little surprised that it has suddenly appeared in linux618 - maybe an amdgpu regression?

So, maybe try switching to linux66 to see if that resolves the issue. Don’t switch to anything earlier though, as that may cause another issue - this time with polkit.

If you don’t want to switch to an earlier kernel, then see if disabling PSD via the boot parameters will work.

This can be done by opening the /etc/default/grub file in a text editor such as kate:

kate /etc/default/grub

and adding amdgpu.dcdebugmask=0x10 to the GRUB_CMDLINE_LINUX= line. As it is a system file, kate will prompt you for your password when you save the file.

Then, run the following command:

sudo update-grub

Reboot, and wait & see if the issue still occurs.

3 Likes

I am not deeply familiar with the internals here, but based on similar reports this might be related to AMD PSR (Panel Self Refresh). PSR has a history of causing brief, random black screen flickers on AMD iGPUs, often during power-state changes.

If you want to rule this out, you can temporarily disable PSR (no reboot required):

sudo sh -c 'echo 0x200 > /sys/module/amdgpu/parameters/dcdebugmask'

If the issue stops occurring after a few days, it likely points to PSR. In that case you can make it permanent by adding
amdgpu.dcdebugmask=0x200 to your kernel parameters.

4 Likes

Thanks! :grinning_face: I will try the temporarary method first.

3 Likes

Would AMD PSR also be active for an Nvidia GPU or is there an Nvidia equivalent?

The file dcdebugmask has read-only permission, even for the root user.
Since this event occurs very rarely, I will make a note of this suggested solution and leave the system unchanged.

Thanks for your info!

Some packagers do that because they don’t understand UNIX. :grin:

The root account has write access to everything, regardless of its permissions, as long as the filesystem itself is mounted writable. :wink:

1 Like

I found a-dummys-guide-to-amd-gpu-issues-on-linux

:penguin:

2 Likes
 sudo sh -c 'echo 0x200 > /sys/module/amdgpu/parameters/dcdebugmask'                         ✔ 
[sudo] password for gloewa: 
sh: line 1: /sys/module/amdgpu/parameters/dcdebugmask: Permission denied
    ~                                                                                     1 ✘  5s  



![Screenshot_20260214_090225|454x500](upload://uWCsUvj8kBh7ivXwQISHIbVsF4C.png)