[Bug 1234055] New: Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Bug ID: 1234055 Summary: Unable to reach dual monitor resolution with 2x 4k UHD side by side to 7680x2160 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: otrebor@hispeed.ch QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878829 --> https://bugzilla.suse.com/attachment.cgi?id=878829&action=edit xrandr log Hi I have a recently bought Lenovo X1 Carbon Gen 12 with an Intel Core Ultra 7 Processor 165U and 64Gig Memory. This Notebook is attached to a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock via a TB4 cable. Plugged into the dock there are two EIZO FlexScan EV2740X Displays. Both attached via DisplayPort. The NB runs OpenSuse Leap 15.6 all patches applied. Also all available firmware updates have been installed via fwupdmgr. The problem is, that this setup does not run with both EIZO displays set to 4k UHD resolution side-by-side. (in 7680x2160 resolution setup). This fails with or without having the internal NB display active or not. Another NB running Win11 with an Nvidia Graphics card attached to the same dock runs both display just fine at 4k UHD resolution. So, i guess the problem lies with the Lenovo X1 Carbon and its Intel i915 graphics driver. According to the intel specs here this should work: https://www.intel.com/content/www/us/en/products/sku/237329/intel-core-ultra... The setup runs fine when i set the resolution on both EIZOS to the lower 2560x1440 and arrange them side by side. I'm a bit puzzled, as is this limited by design or is there something wrong with the drivers. In single display config both displays run fine at 4k UHD (3840x2160) mode. I have attached a number of log files. If you wouldn't mind helping me on this, I'd be grateful. I'm no hardware or kernel geek. Thanks -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c1 --- Comment #1 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878830 --> https://bugzilla.suse.com/attachment.cgi?id=878830&action=edit /etc/os-release -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c2 --- Comment #2 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878831 --> https://bugzilla.suse.com/attachment.cgi?id=878831&action=edit neofetch -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c3 --- Comment #3 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878832 --> https://bugzilla.suse.com/attachment.cgi?id=878832&action=edit modinfo i915 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c4 --- Comment #4 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878833 --> https://bugzilla.suse.com/attachment.cgi?id=878833&action=edit lshw -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c5 --- Comment #5 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878834 --> https://bugzilla.suse.com/attachment.cgi?id=878834&action=edit inxi -Gayz -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c6 --- Comment #6 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878835 --> https://bugzilla.suse.com/attachment.cgi?id=878835&action=edit inxi -FGSz -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c7 --- Comment #7 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878836 --> https://bugzilla.suse.com/attachment.cgi?id=878836&action=edit dmesg -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c8 --- Comment #8 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878837 --> https://bugzilla.suse.com/attachment.cgi?id=878837&action=edit boltctl -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878834|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878835|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878836|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878833|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878832|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878829|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #878831|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c12 --- Comment #12 from Otrebor Igorig <otrebor@hispeed.ch> --- I've tested with kernel package kernel-default-6.4.0-150600.23.25.1.x86_64 all patches applied. No, it does not work. xrandr complains with "error code 1; configure crtc 3 failed" Also, neither KDEs Desktop configuration nor ArandR works. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c14 --- Comment #14 from Otrebor Igorig <otrebor@hispeed.ch> --- (In reply to Takashi Iwai from comment #13)
Thanks, now it's interesting.
Could you boot with boot options "drm.debug=0x1e log_buf_len=16M" and get the dmesg outputs from both working and non-working cases?
done that, see attachments. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c15 --- Comment #15 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878956 --> https://bugzilla.suse.com/attachment.cgi?id=878956&action=edit dmesg non-working dmesg non-working -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c16 --- Comment #16 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878957 --> https://bugzilla.suse.com/attachment.cgi?id=878957&action=edit dmesg resolution-working dmesg resolution-working -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c18 --- Comment #18 from Otrebor Igorig <otrebor@hispeed.ch> --- (In reply to Takashi Iwai from comment #17)
Thanks.
Could you boot again the non-working kernel with the same debug boot options, and get the kernel messages that have been output during you try (and fail) xrandr manually? The log was huge, so I couldn't spot easily what was tested and failed...
ok. I did: xrandr --output eDP-1 --below DP-1-1-6 --output DP-1-2 --right-of DP-1-1-6 --output DP-1-1-6 --mode 3840x2160 --output DP-1-2 --mode 3840x2160 the error was: xrandr: Configure crtc 2 failed and the diff from dmesg during that see attachment -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c19 --- Comment #19 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 878965 --> https://bugzilla.suse.com/attachment.cgi?id=878965&action=edit dmesg kernel-6.4.0-150600.23.25.1. diff -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c21 --- Comment #21 from Otrebor Igorig <otrebor@hispeed.ch> --- No, I took a snapshot of the dmesg output before I ran the xrandr command. After that, I took a snapshot again. What I've uploaded is the diff of the two snapshots. Maybe I was renaming the first snapshot after I took it which ate some seconds, can't recall. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c22 --- Comment #22 from Otrebor Igorig <otrebor@hispeed.ch> --- Additionally, running xrandr producing the above error also eats some seconds until it decides to revert to the old working resolution. btw issuing the same xrandr command as above but setting the resolution to 2560x1440 works perfectly (but that is not part of the log entries). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c24 --- Comment #24 from Otrebor Igorig <otrebor@hispeed.ch> --- (In reply to Takashi Iwai from comment #23)
Thanks. Then it might try multiple times and that resulted in the lengthy log. It's way too long to read through, unfortunately...
What if you run xrandr for each of DPs one by one just with --output and --mode without positioning? Both calls result in errors?
good hint! xrandr --output DP-1-1-6 --mode 3840x2160 xrandr --output DP-1-2 --mode 3840x2160 Either one of them works, as long as the other monitor is in the lower resolution mode. Having both in high-res mode does not. Depending which one is set last it shows xrandr: Configure crtc 1 or 2 failed -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c25 --- Comment #25 from Otrebor Igorig <otrebor@hispeed.ch> --- I've produced the shortest log I could come up with. This covers this scenario: First, setting the right screen to 3840x2160: xrandr --output DP-1-2 --mode 3840x2160 this works Then doing the same with the left screen: xrandr --output DP-1-1-6 --mode 3840x2160 This fails: xrandr: Configure crtc 1 failed The diff log attached covers what happens when I issue the failing call only (which is still a lot). Hope this helps. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c26 --- Comment #26 from Otrebor Igorig <otrebor@hispeed.ch> --- Created attachment 879146 --> https://bugzilla.suse.com/attachment.cgi?id=879146&action=edit Kerel dmesg diff setting failing screen -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234055 https://bugzilla.suse.com/show_bug.cgi?id=1234055#c29 --- Comment #29 from Otrebor Igorig <otrebor@hispeed.ch> --- Unplugging every other device but the two monitors from the dock does not help. The effect is still the same. I'm no hardware expert, but the notebook and the dock are recent enough models that should cover the required bandwidth with ease. In fact, the dock is sold with the advertisement of being able to serve four monitors (1xHDMI, 2xDP, 1xUSB-C). And the test with another notebook showed that serving the two monitors with both in resolution 3840x2160 works. So I would exclude the dock from the problem domain. The notebook specs linked above by Intel also suggest that this should work. The notebook and the dock are linked by a Thunderbolt 4 spec cable, which also should support this setup. So, where does this bandwidth limitation come from? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com