Bug 465552 - With multiple monitors plugged into multiple NVIDIA GPU's, one monitor is not enabled as expected
Summary: With multiple monitors plugged into multiple NVIDIA GPU's, one monitor is not...
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.90
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-10 16:29 UTC by Sam Uhrig
Modified: 2024-02-16 03:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
kscreen-console bug output (109.48 KB, text/plain)
2023-03-31 23:15 UTC, Sam Uhrig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Uhrig 2023-02-10 16:29:42 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Have Multiple Nvida GPU's 970 and 3070
2.  Have 6+ monitors
3.  Configure layout for multiple monitors.
4.  Set kernel parameters for Nvida GPU
5.  Observed in Wayland and X
6.  Tried configuration on 5.26.5 and 5.26.90

OBSERVED RESULT

2 Monitors connected 2 2nd GPU(970) have issues. Once configuration is finally set on reboot it is lost. Next getting it back is a tiresome process. I have to enable and disable the 2 monitors back and forth and can finally get them to work. Sometimes they show as enabled but the screen is blank.  

EXPECTED RESULT

All monitors work with both GPU's and the configuration is preserved on reboot. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:  
(available in About System)
KDE Plasma Version: 5.26.90 or 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

The Display Configuration setup now with this many monitors and them mostly all being the same model make it extremely difficult to identify the one you want to make primary. In the display configuration the monitor ID is not displayed. So when I hit identify I can't easily find what that relates to in the configuration.  I have to disable each monitor and enable them one at a time to find out which is which. So not so much related to this bug but would be nice to make identifying monitors much easier as a side to this bug.
Comment 1 Nate Graham 2023-02-13 01:53:50 UTC
So you're saying there are multiple issues here? One issue is that the screens' arrangement gets lost on reboot, and the other issue is that sometimes screens show no output despite being enabled in the KScreen KCM?

Do I have that right?
Comment 2 Sam Uhrig 2023-02-13 05:14:51 UTC
Yes that is correct. I think I have narrowed the output issue and the screen going blank to a refresh rate issues of some sort. I have to change a couple of the monitors down to a lower refresh rate that is not used in windows. I have all my monitors set to 60 hz in Windows on this same machine and they work fine.
Comment 3 Nate Graham 2023-02-13 18:34:39 UTC
Ok, let's use this bug report for the "not displaying any output due to a refresh rate problem" issue. Can you open a new one for the issue about the monitors' arrangements not being remembered as expected? Thanks!
Comment 4 Sam Uhrig 2023-03-07 00:52:35 UTC
Ok I can do that. After using now for a while and being on latest version. It appears that the layouts are being saved. I don't think that seems to be a problem anymore. The problem still exists where one monitor requires me to enable and disable and sometimes requires me to change the refresh rate back and forth to finally get it working. Its odd behavior but when I first boot to fresh desktop I have to enable disable change refresh rates to get 2 of the monitors working properly. The only other problem I seem to have when I power on a 7th monitor it blows up the monitor configuration and sends it into constant blinking screens. I will add this setup works fine in Windows 10. I can power monitors off/on at will and it make adjustments as needed. Maybe this is an Nvidia driver problem more than a KDE problem as a side thought.
Comment 5 Nate Graham 2023-03-07 15:45:25 UTC
Do all monitors have the same refresh rates?

Are you running Plasma 5.27.2?
Comment 6 Sam Uhrig 2023-03-08 03:35:16 UTC
KDE: 5.27.2
Kernel: 6.2.2-1
Qt Version: 5.15.8
KDE Frameworks Version: 5.103.0

Monitors are not all the same refresh rate. I have however set them all to the same which they support and that doesn't change anything.
Comment 7 Nate Graham 2023-03-08 15:04:45 UTC
Thanks. When all monitors are plugged in and enabled as expected, can you attach a file with the output of `kscreen-console bug`?
Comment 8 Bug Janitor Service 2023-03-23 03:45:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Sam Uhrig 2023-03-31 23:15:49 UTC
Created attachment 157754 [details]
kscreen-console bug output
Comment 10 Sam Uhrig 2023-03-31 23:25:09 UTC
(In reply to Nate Graham from comment #7)
> Thanks. When all monitors are plugged in and enabled as expected, can you
> attach a file with the output of `kscreen-console bug`?

I have attached the file but downside is I will be moving away from this monitor configuration in favor of much larger monitors and less screens that hopefully KDE will support. Going to Dual 43 inches and removing 5 of the 7 monitors. So I will have 4 total which will be supported by one graphics card hopefully. I already have one of the 43's that is going up for testing so I won't have this much longer to determine if the bug is fixed. I had most of the monitors disabled is why I never finished out this report in favor of testing out the KDE Zones feature not sure what its called but is like MS Fancy Zones. I think this will allow me to use less monitors and go for larger monitors that will support my need. I am running arch and have all that latest updates installed. I noticed when I re-enabled all the monitors that the configuration of them was a breeze and feels like something improved a little more potentially. When ever I had did this in the past I would have a lot of flickering forever as each monitor was powered on and it would sometimes lock up. This felt more like what I would experience in Windows.
Comment 11 Nate Graham 2024-01-17 15:57:30 UTC
A lot of work has gone into both multimonitor support as well as NVIDIA robustness in Plasma 6. Can I ask you to test with the Plasma 6 RC to see if it's fixed now?
Comment 12 Bug Janitor Service 2024-02-01 03:45:32 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Bug Janitor Service 2024-02-16 03:46:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!