Thanks for your reply, but I don't think anything of this explains the problem unfortunately. The main question still remains: why does gdm3 decide to launch (not working) X11 session instead of using Wayland? I've just checked on another Debian Bookworm machine and, of course, there is no X11 running at all there -- just gdm-wayland-session. Why does it try to run gdm-x-session here and how can I convince it not to?
The CPU are almost identical: I replaced i9-13900K with i9-14900K.What were the CPU models before and after replacement?
Maybe, but it did work and continues to work just fine with Wayland if I start the compositor manually (whether it's mutter or sway).You might should consider yourself lucky your three display configuration ever worked.
I had actually updated BIOS to the latest version even before replacing the CPU and while it didn't help with the hardware problem (it still froze intermittently), it didn't affect the video output. And I have the same, latest, BIOS now.It's possible you need to make a BIOS setup change. Did you reset BIOS defaults after your CPU change?
It does support 3 displays, but it has a single HDMI input and I have 2 displays with only HDMI outputs, so I connected one of them to the HDMI output on the motherboard. I guess I could buy an adapter and connect it directly to the video card but, again, this looks like a software rather than hardware problem now, isn't it?Doesn't your Radeon support three or more displays? If it does, why complicate things by using the iGPU?
Statistics: Posted by _VZ — 2024-04-05 10:00