[opensuse-support] Plasma5/kscreen losing primary resolution under Leap 15.1
Can anyone suggest how to debug and lock my monitor configuration? I've recently bought a great AOC Q3279VWFD8 monitor to work from home (no prizes for guessing why), which can be driven at 2580x1440 @75Hz via DisplayPort from onboard Intel graphics (Core i5-2500K) with an H67M-GE/HT motherboard. Most time the monitor sleeps it wakes up at a lower resolution (typically 1920x1080, but 1024x768 for extra annoyance). Occasionally I can reconfigure it back up with System Settings -> Display & Monitor. Often I have to repeatedly trick it by powering the monitor off and on, and sometimes it can then be stepped back up to 2580x1440. Often it gets stuck at something like 1920x1080 @ 30Hz. Options are restarting Plasma or letting it go to sleep and reconfigure (not guaranteed). Looking in the journal I can find references to: kdeinit5[6968]: kscreen: Requesting missing EDID for outputs (66, 70) org_kde_powerdevil[7047]: kscreen: Requesting missing EDID for outputs (66, 70) systemsettings5[5381]: kscreen: Requesting missing EDID for outputs (66, 70) As an aside, I have a second monitor 1920x1080 to the right, via HDMI. According to the manual my motherboard will only support two outputs (of the four). The second monitor is only needed a few times a week when puzzling over accounts/spreadsheets. I've read around and the various conflicting advice and trails for multi-monitor & Plasma issues go back years. I'm at a bit of a loss to know which bit of behind the scenes magic is going wrong, as I haven't had to concern myself with this kind of setup since the CRT days! I suspect the monitor isn't replying in time with its capabilities. Here's the xrandr output (listing modes) from it working nicely: $ xrandr Screen 0: minimum 320 x 200, current 4664 x 1588, maximum 8192 x 8192 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected 1920x1080+2744+508 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 725mm x 428mm 2560x1440 59.95 + 74.97* 1920x1080 60.00 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 1280x1440 59.91 1680x1050 59.95 1280x1024 75.02 60.02 1440x900 59.89 1280x960 60.00 1280x720 60.00 60.00 50.00 59.94 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 720x576 50.00 50.00 50.00 720x480 60.00 60.00 59.94 59.94 59.94 640x480 75.00 72.81 66.67 60.00 59.94 59.94 720x400 70.08 2560x1440_74.97 74.89 DP-3 disconnected (normal left inverted right x axis y axis) And here's xrandr output when not working nicely: $ xrandr Screen 0: minimum 320 x 200, current 4664 x 1588, maximum 8192 x 8192 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected 1920x1080+2744+508 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.00 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 59.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 725mm x 428mm 1920x1080 60.00* 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 1280x1440 59.91 1680x1050 59.95 1280x1024 75.02 60.02 1440x900 59.89 1280x960 60.00 1280x720 60.00 60.00 50.00 59.94 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 720x576 50.00 50.00 50.00 720x480 60.00 60.00 59.94 59.94 59.94 640x480 75.00 72.81 66.67 60.00 59.94 59.94 720x400 70.08 DP-3 disconnected (normal left inverted right x axis y axis) Between it being bad I tried the following (having created a modeline from cvt when it was previously good - and modelines seem odd in the days of panels/non-CRT, but I haven't been paying attention): $ xrandr --newmode "2560x1440_74.97" 397.00 2560 2760 3040 3520 1440 1443 1448 1506 -hsync +vsync $ xrandr --addmode DP-2 2560x1440_74.97 $ xrandr --output DP-2 --mode 2560x1440_74.97 xrandr: Configure crtc 0 failed # put up with it to do some critical email # made a coffee & swapped a 3D print # powered monitor up and reset several times # switched on second monitor # mashed the keyboard/wiggled mouse/switched off and on again # jumped to VT1 and got prompt mirrored on both monitors # reconfigured successfully with System Settings -> Display & Monitor I'm expecting at least another 10 weeks of working from home, and this is getting really irritating. Help! Ta. Daniel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Hi Daniel, On Tue, 07 Apr 2020, 14:14:19 +0200, Daniel Morris wrote:
Can anyone suggest how to debug and lock my monitor configuration?
I see strange behaviour of the Intel driver on a 4K@60 Hz display. Linux refuses to run at 60 Hz, while the Windows driver is capable of it, of course. I'd suggest to disconnect the second Monitor running at 1920x1080, leaving the system run into the monitor sleep mode, just to see which mode it resumes with afterwards. HTH, cheers. l8er manfred
[sorry, stuck in drafts] Hi Manfred, On Tue, Apr 07, 2020 at 03:09:32PM +0200, Manfred Hollstein wrote:
Hi Daniel,
On Tue, 07 Apr 2020, 14:14:19 +0200, Daniel Morris wrote:
Can anyone suggest how to debug and lock my monitor configuration?
I see strange behaviour of the Intel driver on a 4K@60 Hz display. Linux refuses to run at 60 Hz, while the Windows driver is capable of it, of course.
I'd suggest to disconnect the second Monitor running at 1920x1080, leaving the system run into the monitor sleep mode, just to see which mode it resumes with afterwards.
Thanks for the suggestion. It was just as random with only the AOC attached, but in the absence of logic I found a workaround, dive into the virtual console, wake and then tweak System Settigs-> Displays ;-) Curiously the AOC always runs at 75Hz when woken that way. Daniel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Daniel Morris composed on 2020-04-07 13:14 (UTC+0100):
Can anyone suggest how to debug and lock my monitor configuration?
I've recently
How recent? Is it within the no questions asked free return period? If yes, take it back. Likely its firmware is too slow to respond to when needed.
bought a great AOC Q3279VWFD8 monitor to work from home (no prizes for guessing why), which can be driven at 2580x1440 @75Hz via
https://www.anandtech.com/show/13095/aoc-launches-q3279vwfd8-inexpensive-315... says 2560x1440, which is a standard.
DisplayPort from onboard Intel graphics (Core i5-2500K) with an H67M-GE/HT motherboard.
H67 is 9 year old technology. IIRC, 2560x1440 is newer, though it shouldn't matter.
Most time the monitor sleeps it wakes up at a lower resolution (typically 1920x1080, but 1024x768 for extra annoyance). Occasionally I can reconfigure it back up with System Settings -> Display & Monitor. Often I have to repeatedly trick it by powering the monitor off and on, and sometimes it can then be stepped back up to 2580x1440. Often it gets stuck at something like 1920x1080 @ 30Hz. Options are restarting Plasma or letting it go to sleep and reconfigure (not guaranteed).
Have you ever tried a Ctrl-Alt-F3 - Alt-F7 key sequence when its stuck instead of Ctrl-Alt-F1? F1 is special compared to 2-6.
Looking in the journal I can find references to:
kdeinit5[6968]: kscreen: Requesting missing EDID for outputs (66, 70) org_kde_powerdevil[7047]: kscreen: Requesting missing EDID for outputs (66, 70) systemsettings5[5381]: kscreen: Requesting missing EDID for outputs (66, 70)
Seems like a confirmation of slow firmware.
As an aside, I have a second monitor 1920x1080 to the right, via HDMI. According to the manual my motherboard will only support two outputs (of the four). The second monitor is only needed a few times a week when puzzling over accounts/spreadsheets.
When you do need it, what is your sequence of enabling events?
I've read around and the various conflicting advice and trails for multi-monitor & Plasma issues go back years. I'm at a bit of a loss to know which bit of behind the scenes magic is going wrong, as I haven't had to concern myself with this kind of setup since the CRT days! I suspect the monitor isn't replying in time with its capabilities.
Me too.
Here's the xrandr output (listing modes) from it working nicely:
$ xrandr Screen 0: minimum 320 x 200, current 4664 x 1588, maximum 8192 x 8192 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected 1920x1080+2744+508 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.88 ... DP-2 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 725mm x 428mm 2560x1440 59.95 + 74.97* 1920x1080 60.00 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 ...
* indicates display's current mode + indicates display's native (preferred) mode
And here's xrandr output when not working nicely:
$ xrandr Screen 0: minimum 320 x 200, current 4664 x 1588, maximum 8192 x 8192 VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected 1920x1080+2744+508 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00*+ 1680x1050 59.88 ... DP-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 725mm x 428mm 1920x1080 60.00* 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 ... Between it being bad I tried the following (having created a modeline from cvt when it was previously good - and modelines seem odd in the days of panels/non-CRT, but I haven't been paying attention):
CVT/GTF generated modelines have never ever solved a problem for me. They cannot do any better than Xorg can itself, as long as it has access to valid HorizSync and VertRefresh.
# put up with it to do some critical email # made a coffee & swapped a 3D print # powered monitor up and reset several times # switched on second monitor # mashed the keyboard/wiggled mouse/switched off and on again # jumped to VT1 and got prompt mirrored on both monitors # reconfigured successfully with System Settings -> Display & Monitor
I'm expecting at least another 10 weeks of working from home, and this is getting really irritating. Help! Ta.
I would find out where in ~/.config/ Plasma stores xrandr settings and while logged out of Plasma, remove the file containing them, and delete the content of ~/.cache/. For ordinary desktop use, there's no reason to use other than 60Hz refresh. Try configuring to not use 75. Does the Q3279VWFD8 have a setting to switch DP 1.2 on or off? If it does, and it's set to 1.2, switch 1.2 off, or vice versa. 1.2 was very young when the H67 was announced. Maybe they don't play nice together. Does the H67M-GE/HT have an available BIOS upgrade? Does the Q3279VWFD8 have an available firmware upgrade? When it's in a bad mood, log out of Plasma and log into IceWM, to see what mode is selected there. Try using arandr to reconfigure while in IceWM. Maybe you could have arandr save a config script to employ when Plasma isn't getting it right. Arandr is found in repositories/X11:/Utilities IIRC. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Felix Miata composed on 2020-04-07 09:49 (UTC-0400): ...
Arandr is found in repositories/X11:/Utilities IIRC.
DP-1 in xrandr output indicates it's running on the modesetting DDX. Try running on the intel DDX, from xf86-video-intel rpm, which when in use will indicate DisplayPort-#. /etc/X11/xorg.conf.d/50-device.conf can be use to make explicit which DDX driver to use. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Felix Miata composed on 2020-04-07 09:59 (UTC-0400):
Felix Miata composed on 2020-04-07 09:49 (UTC-0400):
Another thought: Can you switch cables between displays, run the 2560x1440 on HDMI and 1920x1080 on DisplayPort? With onboard video ports, CRTC enumeration usually assigns the connector closest to the board and farthest from the last expansion slot first priority. That would make your DP connector lowest priority among the four. Changing a GPU or ACPI setting in the BIOS could conceivably have an impact on response to wakeup. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
[sorry for the lag, I'd left this in my drafts box after a few days of futzing with the setup] Hi Felix, Thanks for the suggestions, greatly appreciated and got me something that works. After lots of (literal) head-banging under my desk by swapping cables and outputs I've come up with a repeatable workaround: Power off the screen (front panel switch) Jump to virtual console one (Ctrl-Alt-F1) Power up the screen (starts at 2560x1440 @75Hz) Ctrl-Alt-F7 back to X and slide the resolution from 1920x1080 to 2560x1440 from Plasma & apply. About half the time Plasma/X wakes at 2560x1440 without needing to do this. 2560x1440 is only available on the Display Port connector, all other outputs were limited to 1920x1080. I've found with such a large monitor at hi-res that I can work effectively with just one screen, which has simplified things. I can't find any AOC firmware update and am on the lastest BIOS update. The above isn't ideal, but it works, everytime. Thanks, Daniel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, Jun 11, 2020, 08:20 Daniel Morris <danielm@ecoscentric.com> wrote:
[sorry for the lag, I'd left this in my drafts box after a few days of futzing with the setup]
Hi Felix,
Thanks for the suggestions, greatly appreciated and got me something that works. After lots of (literal) head-banging under my desk by swapping cables and outputs I've come up with a repeatable workaround:
Power off the screen (front panel switch) Jump to virtual console one (Ctrl-Alt-F1) Power up the screen (starts at 2560x1440 @75Hz) Ctrl-Alt-F7 back to X and slide the resolution from 1920x1080 to 2560x1440 from Plasma & apply.
About half the time Plasma/X wakes at 2560x1440 without needing to do this.
2560x1440 is only available on the Display Port connector, all other outputs were limited to 1920x1080. I've found with such a large monitor at hi-res that I can work effectively with just one screen, which has simplified things.
I can't find any AOC firmware update and am on the lastest BIOS update. The above isn't ideal, but it works, everytime.
Thanks, Daniel
.
What graphics and CPU are you using? Single screen via DP? Running X or Wayland? KDE or Gnome? I have 15.1 with i5-8259U (HDMI) and i5-6260U (DP) using internal graphics driving Dell display at 3840x2160 refreshing at 60Hz without doing anything special. So, depending on your graphics, the Intel driver should be able to drive your screen just fine. The problem maybe in your monitor EDID data. What does: xrandr --verbose tells you about what the monitor support? Is your desired refresh rate and resolution supported by the screen? I am no expert, perhaps comparing notes can help you get to the bottom of it. Hope it helps, Tomas
Tomas Kuchta composed on 2020-06-11 09:11 (UTC-0700):
What graphics and CPU are you using? Single screen via DP? Running X or Wayland? KDE or Gnome? https://lists.opensuse.org/opensuse-support/2020-04/msg00019.html -- Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Thu, Jun 11, 2020, 10:05 Felix Miata <mrmazda@earthlink.net> wrote:
Tomas Kuchta composed on 2020-06-11 09:11 (UTC-0700):
What graphics and CPU are you using? Single screen via DP? Running X or Wayland? KDE or Gnome? https://lists.opensuse.org/opensuse-support/2020-04/msg00019.html --
I see, thanks - you are way ahead of my basic suggestions. Tomas
participants (4)
-
Daniel Morris -
Felix Miata -
Manfred Hollstein -
Tomas Kuchta