https://bugs.kde.org/show_bug.cgi?id=513812
--- Comment #7 from [email protected] --- (In reply to Zamundaaa from comment #5) > The driver is hitting some sort of resource limits: > > [ 240.868304] amdgpu 0000:03:00.0: [drm] Adding stream 000000009e4d87f2 to > > context failed with err 2! > > [ 240.868306] amdgpu 0000:03:00.0: [drm:amdgpu_dm_atomic_check [amdgpu]] > > ENABLE: dm_update_crtc_state() failed > > [ 240.868448] amdgpu 0000:03:00.0: [drm:amdgpu_dm_atomic_check [amdgpu]] > > Atomic check failed with err: -22 > "err 2" is DC_NO_CONTROLLER_RESOURCE, I've never seen that before though. > > It also has another warning, which I'm more familiar with: > > DC global validation failure: Bandwidth validation failure (BW and > > Watermark) (13) > To reduce bandwidth requirements, you could try reducing resolution and > refresh rate on one or more screens. > Just to be certain, also check if you're using the exact same modes on Xorg. > KWin goes for the highest refresh rate by default, which can cause increased > bandwidth requirements. > > One more thing you can test: is your "color accuracy" setting on any of the > screens set to "prefer color accuracy"? In theory, KWin should be doing > automatic fallbacks, but it's worth trying with all screens set to "prefer > efficiency" anyways. > > Last but not least, the fastest way to find out what to do about this would > be a bisect. If you're sure it worked earlier in 6.5, then you could compile > KWin 6.5.0 and see if that can enable all screens with the same settings. Hi! Very sorry for the late reply, I've got around to some more testing and found the seemingly single setting that breaks it! Putting my center monitor at 165hz (well the settings says 164.99hz) is what causes the 4th plugged in monitor to not work. Even putting every other display at 60hz and just the center one at 165hz it doesn't like. 120hz is fine though for the center monitor! And I'm not gamer enough to notice a difference anyway :) I still am pretty sure it's not a hardware limitation, as I know for a fact I've always been able to have everything set to it's highest, and I've had this monitor for half a year and it wasn't an issue earlier. The colour accuracy setting was already all set to efficient, and didn't make a difference. Also worth noting I'm now on Kwin 6.5.5-1.fc43. I'm perfectly content keeping it at 120hz honestly, but if a developer wants me to do further testing please let me know and I'll gather what I can :) -- You are receiving this mail because: You are watching all bug changes.
