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
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
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…
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.
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.
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.
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 …
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 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
I appreciate it . I’m not too stressed about it , keeps me learning
