Issues with display detection on boot in DisplayPort MST transport
hardware-compat
So, I have a very weird issue with my setup (NVidia GPU connected to the first monitor in a dual monitor setup using DisplayPort MST / Daisychaining):
During boot, both monitors just show the bios logo, plus later on the loading indicator and bazzite logo. After this, only the second monitor in the chain is detected and active (showing the login screen), with a similar behaviour when switching to another tty (only that screen is used).
When I then switch the port I use on the GPU, both monitors are detected and used without issue, with a non-graphical tty showing up on both screens, as expected. If I switch back to the first port, the issue occurs again. And it really is always the port connected to during boot, not a specific port on the GPU.
So, while I technically have a workaround, replugging the DP cable feels a bit off, and I need some help. I am generally comfortable in the terminal etc, just not used to the whole stack of things involved here (compositor etc), so I would really appreciate some pointers on how to troubleshoot this, or a solution, if anyone has seen something like this before.
During boot, both monitors just show the bios logo, plus later on the loading indicator and bazzite logo. After this, only the second monitor in the chain is detected and active (showing the login screen), with a similar behaviour when switching to another tty (only that screen is used).
When I then switch the port I use on the GPU, both monitors are detected and used without issue, with a non-graphical tty showing up on both screens, as expected. If I switch back to the first port, the issue occurs again. And it really is always the port connected to during boot, not a specific port on the GPU.
So, while I technically have a workaround, replugging the DP cable feels a bit off, and I need some help. I am generally comfortable in the terminal etc, just not used to the whole stack of things involved here (compositor etc), so I would really appreciate some pointers on how to troubleshoot this, or a solution, if anyone has seen something like this before.
