Black outs! - Display drops outs for 2-3 seconds

Was hoping to not be here asking for a push in the right direction so soon , but, here I am !

I’m seeing display drop out for 2-3 seconds at a time … (i3) refreshing all my workspaces , and then reloading them to their configured spots … for example if I don’t have something locked to workspace 7 in the i3 config then it will come hang out at 1 again .

I’m running a dual display setup … so all workspaces are getting compressed to display one when things come back , and THEN shot over to display 2 again … I unplugged display 2 but things still happen :frowning:

This happens with the dGPU off (AMDGPU running the show) and on (NVIDIA) …

There is a xorg config 90-nvidia-primary . Compisitor is compton … but I didn’t seem to have this issue with i3 on Ubuntu (same compositor) …

I also didn’t have this problem when testing the xfce and GNOME DE with endeavour …

hmmm .

also , somewhat randomly , entering my password with sometimes fail . For example sudo nano xxx I will fail to enter the correct password (even though I am … ) a reboot is needed to fix this :sweat_smile:

Anyone got any inklings ? :crazy_face:

i3 is not that easy to setup for multidisplay setups.
what are you using to do so ? xrandr?

i3-gnome-flashback …

So essentially GNOME … seem (s) (ed) to work out of the box … Only real strange thing I’m seeing is that GNOME settings thinks that the laptop display is the external monitor and vice versa.

I used the xrandr outputs to assign workspaces and classes to different monitors and that seemed to work fine …

EDIT: It’s pretty intermittent … This evening I was on the computer for an hour or so and it didn’t happen …but the time before that it was every five minutes or so… :crazy_face:

I have the same problem on XFCE.
my external monitor would occasionally go black for a few seconds. I thought it was something to do with the monitor, but i noticed this happens when I do some action. for example the latest occurrence happened when i launched Firefox. This happens very rare, so I didn’t give it much thought.
My nvidia card is disabled in bios, but this happened when i was using the nVidia card also.

$ inxi -G
Graphics:  Device-1: Intel driver: i915 v: kernel  
           Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: nvidia resolution: 1: 1920x1080~60Hz 
           2: 1920x1080~60Hz 
           OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.1.8

Same. Just noticed today. Have not found a cause yet. It appears to happen randomly.

I am also running i3, but on a laptop with (obviously) a single monitor. Also have a dual card setup (Intel/NVIDIA).

Okay…so I’m not going completely crazy … good news …

I noticed I have both AMD and ATI Xorg drivers loaded today so I purged ATI (and TLP) …no doubt it won’t fix anything ( havn’t seen it again yet though …but it is very…random) …

Will purge whatever else takes my fancy and report

[ 7865.164022] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.
[ 7865.164024] [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
[ 7865.816284] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.

dmesg tells me…

How are the monitors connected?

Just wondering how your monitors are connected?

HDMI … but that issue arises seems to get logged with or without an external monitor … The display dropouts seem to aswell …

Next time it happens I will scour journalctl

I have seen this issue with some using converters from usb-c to hdmi or docks etc that’s why i asked.

Indeed, this is a usb-c hub with a HDMI port

That may be the issue! Try it with quality full HDMI 2.0 cable.

Edit: The newest version of Hdmi is 2.1 Mostly for 4k -8k High Frame Rate

the dock knows only HDMI 1.4, the monitor is 1080p anyway. I’ve connected the cable directly to the HDMI port on the laptop now. Will see if it changes anything. It’s a long wait anyway, the issue occurred a few times a month maybe. I rather liked the fact that I connected everything to the hub, but it’s not such a big deal. The cable is also a cheap one. Maybe I’ll invest in a better one if the issue reoccurs. But enough about this, don’t want to hijack OP’s thread completely. Was thinking just to chime in, in case we can see something common.

See if it works first. Is it 1.4, 1.4a, or 1.4b?

no idea, it only says “HDMI (supports 4K @ 30Hz)”

1440P @ 30 Hz

Journalctl isn’t giving me much more than the obvious ? where else should I be looking? … also perhaps unrelated … I am randomly getting whole system locks … fixed only with a hard reboot … :laughing:

Oct 09 17:55:07 fruitbowl kernel: [drm:mod_hdcp_add_display_to_topology [amdgpu]] ERROR Failed to add display topology, DTM TA is not initialized.
Oct 09 17:55:07 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:55:07 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:55:08 fruitbowl kernel: [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
Oct 09 17:55:08 fruitbowl kernel: [drm:mod_hdcp_add_display_to_topology [amdgpu]] ERROR Failed to add display topology, DTM TA is not initialized.
Oct 09 17:55:08 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:55:08 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:56:42 fruitbowl kernel: [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0
Oct 09 17:56:42 fruitbowl kernel: [drm:mod_hdcp_add_display_to_topology [amdgpu]] ERROR Failed to add display topology, DTM TA is not initialized.
Oct 09 17:56:43 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:56:43 fruitbowl gsd-color[866]: no xrandr-eDP device found: Failed to find output xrandr-eDP
Oct 09 17:56:43 fruitbowl kernel: [drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0

I don’t even know what you hardware is? inxi -Fxxxa --no-host

Anyway i found this on another site.

[drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.

[drm] [Link 0] WARNING MOD_HDCP_STATUS_FAILURE IN STATE HDCP_UNINITIALIZED STAY COUNT 0

You can fix the flickering by doing xrandr --output eDP --off && xrandr --auto until it stops.

Not sure if this is the same issue or whether this will help? I assume this command turns off eDP and sets xrandr to default settings?

I would be looking at:

journalctl -p err

dmesg

inxi

System:
Kernel: 5.8.12-arch1-1-g14 x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-g14
root=UUID=53c618af-1c87-4606-aef0-43cd3a5c3395 rw rootflags=subvol=@ quiet
cryptdevice=UUID=9fb72434-ffda-483a-a5b3-1bf517fa5de2:luks-9fb72434-ffda-483a-a5b3-1bf517fa5de2
root=/dev/mapper/luks-9fb72434-ffda-483a-a5b3-1bf517fa5de2 loglevel=3 nowatchdog
Desktop: i3 4.18.2 info: i3bar dm: startx Distro: EndeavourOS
Machine:
Type: Laptop System: ASUSTeK product: ROG Zephyrus G14 GA401II v: 1.0
serial: <superuser/root required>
Mobo: ASUSTeK model: GA401II v: 1.0 serial: <superuser/root required>
UEFI: American Megatrends v: GA401II.217 date: 09/18/2020
Battery:
ID-1: BAT0 charge: 55.9 Wh condition: 69.9/76.0 Wh (92%) volts: 15.8/15.8
model: ASUSTeK ASUS Battery type: Li-ion serial: N/A status: Not charging
CPU:
Info: 8-Core model: AMD Ryzen 7 4800HS with Radeon Graphics bits: 64 type: MT MCP
arch: Zen family: 17 (23) model-id: 60 (96) stepping: 1 microcode: 8600104
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 92662
Speed: 2257 MHz min/max: 1400/2900 MHz boost: disabled Core speeds (MHz): 1: 2257
2: 2106 3: 2097 4: 1766 5: 1970 6: 1974 7: 2676 8: 2736 9: 2399 10: 2315 11: 2492
12: 2238 13: 2356 14: 2373 15: 1997 16: 1891
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, IBRS_FW, STIBP:
conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 04:00.0
chip ID: 1002:1636
Display: server: X.Org 1.20.9 driver: amdgpu unloaded: fbdev,modesetting,vesa
alternate: ati display ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x286mm (40.0x11.3")
s-diag: 1055mm (41.6")
Monitor-1: eDP res: 1920x1080 hz: 120 dpi: 158 size: 309x174mm (12.2x6.9")
diag: 355mm (14")
Monitor-2: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 93 size: 527x293mm (20.7x11.5")
diag: 603mm (23.7")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: AMD driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:1637
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: ASUSTeK
driver: snd_rn_pci_acp3x v: kernel alternate: snd_pci_acp3x bus ID: 04:00.5
chip ID: 1022:15e2
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 04:00.6 chip ID: 1022:15e3
Device-4: Focusrite-Novation Scarlett 2i2 Camera type: USB
driver: snd-usb-audio,usb-storage bus ID: 3-2:3 chip ID: 1235:8210
serial: Y8W34KH063C875
Device-5: Arturia USB2.1 Hub type: USB driver: snd-usb-audio bus ID: 3-1.1:4
chip ID: 1c75:020a serial: 7020400495031865
Device-6: Focusrite-Novation Scarlett 2i2 USB type: USB
driver: snd-usb-audio,usb-storage bus ID: 3-1.2:6 chip ID: 1235:0103
serial: AXVC3019A06DAC
Sound Server: ALSA v: k5.8.12-arch1-1-g14
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus ID: 02:00.0
chip ID: 8086:2723
IF: wlan0 state: up mac: f8:e4:e3:25:2c:59
Drives:
Local Storage: total: 2.29 TiB used: 723.81 GiB (30.9%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB block size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: BTNH002224H5512A
rev: 002C scheme: GPT
ID-2: /dev/sda type: USB model: Scarlett Welcome Disk size: 192 KiB block size:
physical: 512 B logical: 512 B serial: Y8W34KH063C875 rev: 0.10 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-3: /dev/sdb type: USB model: Novation Onboarding Drive size: 192 KiB block size:
physical: 512 B logical: 512 B serial: AXVC3019A06DAC rev: 0.01 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
ID-4: /dev/sdc type: USB vendor: Western Digital model: WD My Passport 260D
size: 1.82 TiB block size: physical: 512 B logical: 512 B
serial: 575844314538393448575A34 rev: 2003 scheme: MBR
Partition:
ID-1: / raw size: 476.44 GiB size: 476.44 GiB (100.00%) used: 126.06 GiB (26.5%)
fs: btrfs dev: /dev/dm-0
ID-2: /home raw size: 476.44 GiB size: 476.44 GiB (100.00%) used: 126.06 GiB (26.5%)
fs: btrfs dev: /dev/dm-0
Swap:
Alert: No Swap data was found.
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2800
Info:
Processes: 405 Uptime: 3h 43m Memory: 15.12 GiB used: 7.70 GiB (50.9%) Init: systemd
v: 246 Compilers: gcc: 10.2.0 Packages: pacman: 1107 lib: 393 Shell: Bash v: 5.0.18
running in: st inxi: 3.1.07

I think in this situation , the command won’t make a difference (I probably put forward a slack explanation) . The flickering is brief perhaps one to five seconds and it’s more of a off …1…2…3…on type deal …
That may happen 4 times in ten minutes … or once every two days .

it seems like it shuts itself off automatically , and then reinstates itself (which is what the command would do yeah ? ) it’s just that it does that without a command hahah .

dmesg has nothing more than journalctl -f told me when it was happening.

Thanks for having a look :slight_smile:
I appreciate it . I’m not too stressed about it , keeps me learning