Problems with 2 Displays connected via DisplayPort DaisyChain / MST on Kernel 6.1

Hi,

i’ve got a Problem since Kernels newer than 6.0 with my Thunderbolt 3 Dock (CalDigit TS3 Plus).

The configuration (using kernel 6.0.7-301.fc37.x86_64) is working, but when i boot the notebook with kernel 6.1 (tried 6.1.6-200.fc37, 6.1.7-200.fc37 and 6.1.8-200.fc37 ) the two monitors (laptop lid closed) are detected in gnome, but they do not turn on.

the same issue sometimes is present after starting the notebook with kernel 6.0 but can be workarounded by disconnecting the DVI cable and reconnecting (occanionally 2 or 3 times).
my guess is that sth. in the newer kernels is taking too long or works different.

how can i get more information on the problem to better diagnose it or even better fix it?

from dmesg i have multiple entries like this on 6.1.8 kernel:
i have tried to turn monitors on/off via gnome display settings (it worked one time, one monitor had an image, the second, daisy-chained one not):

[  411.789149] [drm] DMUB HPD callback: link_index=5
[  419.528303] amdgpu 0000:33:00.0: [drm] *ERROR* Step 2 of creating MST payload for 00000000c0ac6810 failed: -5

boltctl (6.0 kernel:

# boltctl

#  ● CalDigit, Inc. TS3 Plus
   ├─ type:          peripheral
   ├─ name:          TS3 Plus
   ├─ vendor:        CalDigit, Inc.
   ├─ uuid:          cc030000-00b0-a508-a349-231808814122
   ├─ generation:    Thunderbolt 3
   ├─ status:        authorized
   │  ├─ domain:     ee263804-a005-379a-ffff-ffffffffffff
   │  ├─ rx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  ├─ tx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  └─ authflags:  boot
   ├─ authorized:    Mon 30 Jan 2023 08:50:56 AM UTC
   ├─ connected:     Mon 30 Jan 2023 08:50:56 AM UTC
   └─ stored:        Wed 28 Dec 2022 02:36:08 AM UTC
      ├─ policy:     iommu
      └─ key:        no

inxi (6.0 kernel:

# inxi -Fzx

System:
  Kernel: 6.0.7-301.fc37.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.38-24.fc37 Desktop: GNOME v: 43.2 Distro: Fedora release 37 (Thirty
    Seven)
Machine:
  Type: Convertible System: LENOVO product: 82QF v: Yoga 7 14ARB7
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
    serial: <superuser required> UEFI: LENOVO v: K5CN35WW date: 09/23/2022
Battery:
  ID-1: BAT0 charge: 70.3 Wh (100.0%) condition: 70.3/71.0 Wh (99.0%)
    volts: 17.4 min: 15.4 model: BYD L21B4PE2 status: full
  Device-1: hidpp_battery_0 model: Logitech Wireless Gaming Mouse
    charge: 55% (should be ignored) status: discharging
  Device-2: wacom_battery_0 model: Wacom HID 52D3 charge: 0% status: N/A
CPU:
  Info: 8-core model: AMD Ryzen 7 6800U with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3+ rev: 1 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 2388 high: 4741 min/max: 400/4768 boost: enabled cores:
    1: 2106 2: 2107 3: 4725 4: 4741 5: 2370 6: 2371 7: 2106 8: 2107 9: 2107
    10: 400 11: 2439 12: 4733 13: 1296 14: 400 15: 2107 16: 2106
    bogomips: 86238
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu
    v: kernel arch: RDNA-2 bus-ID: 33:00.0 temp: 45.0 C
  Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-1.1.3:9
  Device-3: Luxvisions Innotech Integrated RGB Camera type: USB
    driver: uvcvideo bus-ID: 11-1:2
  Display: wayland server: X.Org v: 22.1.7 with: Xwayland v: 22.1.7
    compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu resolution:
    1: 2560x1440~60Hz 2: 2560x1440~60Hz
  API: OpenGL v: 4.6 Mesa 22.3.3 renderer: AMD Radeon Graphics (rembrandt
    LLVM 15.0.6 DRM 3.48 6.0.7-301.fc37.x86_64) direct render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel bus-ID: 1-1.1.3:9 v: kernel bus-ID: 33:00.1
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo
    driver: snd_pci_acp6x v: kernel bus-ID: 33:00.5
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel bus-ID: 33:00.6
  Device-4: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
  Device-5: Blue Microphones Yeti Stereo Microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-1.1.4:12
  Device-6: SteelSeries ApS Arctis 9 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-1.4.1:10
  Device-7: No brand CalDigit Thunderbolt 3 Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-2:3
  Sound API: ALSA v: k6.0.7-301.fc37.x86_64 running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.64 running: yes
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel bus-ID: 01:00.0
  IF: wlp1s0 state: up mac: <filter>
  Device-2: Intel I210 Gigabit Network vendor: CalDigit driver: igb
    v: kernel port: 2000 bus-ID: 09:00.0
  IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 1-1.3:5
  Report: rfkill ID: hci1 rfk-id: 3 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
  Device-2: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 7-4:2
  Report: ID: hci0 rfk-id: 2 state: up address: N/A
Drives:
  Local Storage: total: 953.87 GiB used: 242.77 GiB (25.5%)
  ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKCD1T0TFK size: 953.87 GiB
    temp: 37.9 C
Partition:
  ID-1: / size: 952.28 GiB used: 242.41 GiB (25.5%) fs: btrfs
    dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 317.3 MiB (32.6%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 49.4 MiB (8.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 952.28 GiB used: 242.41 GiB (25.5%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 5.66 GiB (70.8%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 49.2 C mobo: N/A gpu: amdgpu temp: 45.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 612 Uptime: 9h 5m Memory: 27.1 GiB used: 12.86 GiB (47.5%)
  Init: systemd target: graphical (5) Compilers: gcc: 12.2.1 Packages: 26
  note: see --rpm Shell: Zsh v: 5.9 inxi: 3.3.24

I’m having a similar issue with a bit of different setup. I have a Lenovo laptop that connects to two monitors through a single USB-C. The second monitor is connected to the first monitor using a DisplayPort cable, and the first monitor is connected to my laptop using a USB-C cable (aka DaisyChain.)

fecb542bd4413b9f85755d875e395bd6f0ccd1b1.jpeg

It seems that I can get it to work if I reduce the resolution of the second monitor. I’d like to close the lid on my laptop and not use that display/screen and just use the two 4k monitors.

Can you share the verbose output from inxi? Mine looks like this at the moment using reduced resolution and the laptop screen is on. I see different output depending after installing wayland-info RPM. Also, consider looking at the output of your user session, or specifically at the gnome-shell logs. Mine logs report a bunch of errors…

[jcall@jcall-laptop ~]$ inxi -Gxxx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo
    driver: i915 v: kernel arch: Gen-12.1 ports: active: DP-5,DP-7,eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-6, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 3-4:3 chip-ID: 04f2:b6ea class-ID: fe01 serial: 0001
  Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 3-6.4.2:11 chip-ID: 046d:0843 class-ID: 0102 serial: 9038BE9E
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.7
    compositor: gnome-shell v: 43.2 driver: gpu: i915 display-ID: 0
  Monitor-1: DP-5 model: Dell U3223QE serial: 9LQ06H3 res: 3840x2160
    dpi: 140 size: 698x393mm (27.48x15.47") diag: 801mm (31.5") modes:
    max: 3840x2160 min: 720x400
  Monitor-2: DP-7 model: Dell U3223QE serial: 8PTWDH3 res: 3840x2160
    dpi: 140 size: 698x393mm (27.48x15.47") diag: 801mm (31.5") modes:
    max: 3840x2160 min: 720x400
  Monitor-3: eDP-1 model: BOE Display 0x094c res: 1920x1200 dpi: 161
    size: 302x188mm (11.89x7.4") diag: 356mm (14") modes: 1920x1200
  API: OpenGL v: 4.6 Mesa 22.3.4 renderer: Mesa Intel Xe Graphics (TGL GT2)
    direct render: Yes

[jcall@jcall-laptop ~]$ sudo dnf install wayland-utils
# now inxi reports that my second monitor is reduced to 2560x1440 resolution

[jcall@jcall-laptop ~]$ inxi -Gxxx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo
    driver: i915 v: kernel arch: Gen-12.1 ports: active: DP-5,DP-7,eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-6, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 3-4:3 chip-ID: 04f2:b6ea class-ID: fe01 serial: 0001
  Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 3-6.4.2:11 chip-ID: 046d:0843 class-ID: 0102 serial: 9038BE9E
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.7
    compositor: gnome-shell v: 43.2 driver: N/A d-rect: 8320x2160 display-ID: 0
  Monitor-1: DP-5 pos: primary,left res: 3840x2160 size: N/A modes: N/A
  Monitor-2: DP-7 pos: center res: 2560x1440 size: N/A modes: N/A
  Monitor-3: eDP-1 pos: right res: 1920x1200 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 22.3.4 renderer: Mesa Intel Xe Graphics (TGL GT2)
    direct render: Yes
[jcall@jcall-laptop ~]$ journalctl --no-pager -l -b0  _COMM=gnome-shell
### shows the same as below, but below also shows other processes related to my login###

[jcall@jcall-laptop ~]$ journalctl --no-pager -l -b0  -u user@$(id -u)
...
Jan 30 22:14:49 jcall-laptop gnome-shell[4406]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
Jan 30 22:14:49 jcall-laptop gnome-shell[4406]: Page flip discarded: drmModeAtomicCommit: Invalid argument
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Failed to post KMS update: drmModeAtomicCommit: No space left on device
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Page flip discarded: drmModeAtomicCommit: No space left on device
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Page flip discarded: drmModeAtomicCommit: No space left on device
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Page flip discarded: drmModeAtomicCommit: No space left on device
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument
Jan 30 22:14:56 jcall-laptop gnome-shell[4406]: Page flip discarded: drmModeAtomicCommit: Invalid argument
...

Just an update on some cable changes I made… I’ve added a Thunderbolt 3 dock to my setup. Now my laptop connects via Thunderbolt 3 to a “dock” which provides 2x DisplayPort ports. I have removed the daisychain configuration; each monitor connects directly to the Thunderbolt hub. This seems to work much better for me.

[jcall@jcall-laptop ~]$ sudo boltctl 
 ● Lenovo ThinkPad Thunderbolt 3 Dock
   ├─ type:          peripheral
   ├─ name:          ThinkPad Thunderbolt 3 Dock
   ├─ vendor:        Lenovo
   ├─ uuid:          00d74075-80fe-0801-ffff-ffffffffffff
   ├─ generation:    Thunderbolt 3
   ├─ status:        authorized
   │  ├─ domain:     2115f463-09ff-8780-ffff-ffffffffffff
   │  ├─ rx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  ├─ tx speed:   40 Gb/s = 2 lanes * 20 Gb/s
   │  └─ authflags:  none
   ├─ authorized:    Tue 31 Jan 2023 06:55:48 AM UTC
   ├─ connected:     Tue 31 Jan 2023 06:55:48 AM UTC
   └─ stored:        Tue 31 Jan 2023 06:55:48 AM UTC
      ├─ policy:     iommu
      └─ key:        no
[jcall@jcall-laptop ~]$ inxi -Gxxx
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] vendor: Lenovo
    driver: i915 v: kernel arch: Gen-12.1 ports: active: DP-7,DP-9 off: eDP-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, DP-8, HDMI-A-1, HDMI-A-2,
    HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:9a49 class-ID: 0300
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 3-4:3 chip-ID: 04f2:b6ea class-ID: fe01 serial: 0001
  Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 5-2.3:4 chip-ID: 046d:0843 class-ID: 0102 serial: 9038BE9E
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.7
    compositor: gnome-shell v: 43.2 driver: N/A d-rect: 7680x2160 display-ID: 0
  Monitor-1: DP-7 pos: primary,left res: 3840x2160 size: N/A modes: N/A
  Monitor-2: DP-9 pos: right res: 3840x2160 size: N/A modes: N/A
  API: OpenGL v: 4.6 Mesa 22.3.4 renderer: Mesa Intel Xe Graphics (TGL GT2)
    direct render: Yes

im now on 6.1.8 and with resolution changing and turning them on and off in gnome settings i’m able to get both monitors working after 5 minutes of resolution changing and turning on or off.

logs while currently running with 2 monitors via DP daisy chain over TB3 dock with current kernel:

# inxi -Gxxx
Graphics:
  Device-1: AMD Rembrandt [Radeon 680M] vendor: Lenovo driver: amdgpu
    v: kernel arch: RDNA-2 pcie: speed: 16 GT/s lanes: 16 ports:
    active: DP-7,DP-9 off: eDP-1 empty: DP-1, DP-10, DP-2, DP-3, DP-4, DP-5,
    DP-6, DP-8, HDMI-A-1 bus-ID: 33:00.0 chip-ID: 1002:1681 class-ID: 0300
    temp: 46.0 C
  Device-2: Logitech Webcam C310 type: USB driver: snd-usb-audio,uvcvideo
    bus-ID: 1-1.1.3:9 chip-ID: 046d:081b class-ID: 0102 serial: 6B1B27E0
  Device-3: Luxvisions Innotech Integrated RGB Camera type: USB
    driver: uvcvideo bus-ID: 11-1:2 chip-ID: 30c9:0057 class-ID: fe01
    serial: 01.00.00
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.7
    compositor: gnome-shell v: 43.2 driver: gpu: amdgpu display-ID: 0
  Monitor-1: DP-7 model: Dell U2721DE serial: 5CBMW13 res: 2560x1440
    dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (27") modes:
    max: 2560x1440 min: 720x400
  Monitor-2: DP-9 model: Dell U2721DE serial: DBBMW13 res: 2560x1440
    dpi: 109 size: 597x336mm (23.5x13.23") diag: 685mm (27") modes:
    max: 2560x1440 min: 720x400
  Monitor-3: eDP-1 model: Samsung 0x417a res: 2880x1800 dpi: 242
    size: 302x189mm (11.89x7.44") diag: 356mm (14") modes: max: 2880x1800
    min: 640x480
  API: OpenGL v: 4.6 Mesa 22.3.4 renderer: AMD Radeon Graphics (rembrandt
    LLVM 15.0.7 DRM 3.49 6.1.8-200.fc37.x86_64) direct render: Yes

my output of journalctl:

# journalctl --no-pager -l -b0  -u user@$(id -u)
Jan 31 14:12:20 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:12:26 nb01 gnome-shell[2039]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:12:26 nb01 gnome-shell[2039]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Jan 31 14:12:26 nb01 gnome-shell[2039]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:12:27 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:12:28 nb01 systemd[1855]: Starting tracker-extract-3.service - Tracker metadata extractor...
Jan 31 14:12:28 nb01 systemd[1855]: Started tracker-extract-3.service - Tracker metadata extractor.
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:12:33 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:12:41 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:12:52 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:12:56 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:12:58 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:13:02 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:13:08 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:13:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:13:13 nb01 gnome-shell[2039]: Update check failed: Could not connect to extensions.gnome.org: Socket I/O timed out
Jan 31 14:13:25 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:13:29 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:13:31 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:13:41 nb01 gnome-shell[2039]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:13:41 nb01 gnome-shell[2039]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Jan 31 14:13:41 nb01 gnome-shell[2039]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:13:41 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:13:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:01 nb01 gnome-control-c[3071]: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjacent
Jan 31 14:14:06 nb01 gnome-shell[2039]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:14:06 nb01 gnome-shell[2039]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Jan 31 14:14:06 nb01 gnome-shell[2039]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:07 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:14:10 nb01 gnome-shell[2039]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:14:10 nb01 gnome-shell[2039]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Jan 31 14:14:10 nb01 gnome-shell[2039]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:11 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:14:11 nb01 systemd[1855]: Starting grub-boot-success.service - Mark boot as successful...
Jan 31 14:14:11 nb01 systemd[1855]: Finished grub-boot-success.service - Mark boot as successful.
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:15 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:14:24 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:14:37 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:14:51 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:15:01 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Jan 31 14:15:07 nb01 systemd[1855]: app-gnome-gnome\x2ddisplay\x2dpanel-3071.scope: Consumed 10.020s CPU time.
Jan 31 14:15:09 nb01 gnome-shell[2039]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:15:09 nb01 gnome-shell[2039]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:15:09 nb01 gnome-shell[2039]: meta_display_get_monitor_geometry: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:15:10 nb01 gnome-shell[2039]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed
Jan 31 14:15:10 nb01 gnome-shell[2039]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Jan 31 14:15:10 nb01 gnome-shell[2039]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Jan 31 14:15:10 nb01 gnome-shell[2039]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

thanks for the advice with the resolution change @johnsimcall ! this is not an optimal solution, but for now it works.

greetings

update: since kernel 6.4 my displays are not detected anymore :frowning:

and another update from kernel 6.5.10 on fedora 39.

i tried connecting the displays directly to my notebook via a usb-c to displayport cable. the first monitor is detected, the second (connected to the first via DP daisychain) not (directly). plugging and unplugging and the workaround mentioned above works the same as if it is connected to the USB4 dock.
so i think we can rule out USB4 / TB3 Dock as the issue. interestingly i found some more messages when connecting / disconnecting my displays in journalctl / dmesg:

# connecting the displays:
[drm] DM_MST: DP12, 4-lane link detected
# a couple of these messages for some time (0-10secs)
kernel: [drm] DMUB HPD IRQ callback: link_index=5
# and if it does not show up or after it is detected but black (turn off/on in gnome settings)
[  534.807087] amdgpu 0000:33:00.0: [drm] *ERROR* Sending link address failed with -5

this keeps repeating every time i connect / disconnect my monitors until they both get detected and are black.
i then turn them off/on in gnome settings until they have a picture.

greetings

just keeping this updated. issue persists on kernel 6.6.11-200.fc39.x86_64
if anyone has some other suggestions, they are welcome :slightly_smiling_face:

Have you filed a bug anywhere?

not directly - at the beginning i had an Abrt report and created a bug, but the bug was closed because the fedora version is unsupported now.

what would be the right place to report such a bug?

i found this one: https://gitlab.freedesktop.org/drm/amd/-/issues/2035 but it had no recent activity so it was closed also…