Created attachment 110052 [details] dp1.2.txt The screen's native resolution is 1920x1080 I believe, and it can be seen to boot to correct resolution in bug 86733. In that bug report the screen is set to DisplayPort 1.1a setting, it takes a long time to initialise, but gets the correct screen resolution. When I set the monitor to DisplayPort 1.2 the screen initialisation is fast, however gets the wrong resolution - it doesn't look widescreen but rather something like 1024x768 This is still Intell haswell NUC. Maybe haswell NUC does not support DisplayPort 1.2, I don't know. If there is anything else that I can provide let me know.
Could you attach the EDID the monitor gives us for both modes? (the EDID is in /sys/class/drm/card0-DP-1/edid where DP-1 is the port the monitor is connected to)
[drm:drm_mode_prune_invalid] Not using 1920x1080 mode 12 12 is MODE_VIRTUAL_Y? Uh.
(In reply to Damien Lespiau from comment #2) > [drm:drm_mode_prune_invalid] Not using 1920x1080 mode 12 > > 12 is MODE_VIRTUAL_Y? Uh. It's just the drm_helper_probe_single_connector_modes() trying to select a mode on the output to fit 1024x768 because [ 0.517680] [drm:drm_setup_crtcs] picking CRTCs for 8192x8192 config [ 0.517682] [drm] Cannot find any crtc or sizes - going 1024x768
Created attachment 110061 [details] dp-ls-edid.tar.xz I'm attaching tarball of two ls listings & two edids (which look the same to me) Physically on the monitor I have: 2 hdmi ports, 1 DP in, 1 mini-DP in, 1 DP out. In 1.1a mode, from drm/kernel only a single "DP" port is detected - DP-1 is connected, which has an edid. In 1.2 mode, from drk/kernel three "DP" ports are depetected - DP-2 is connected, which has an edid. I hope the directory listings, edid filenames is clear inside the tarball.
Requested information is provided.
This is a somewhat known limitation of the current mst code apparently - since it can't work while locks are held we need to wait for async detect until screens show up. Not sure whether Dave Airlie is working on this. Just to confirm, does xrandr detect things correctly after boot, i.e. this is only fbcon which is wrong?
Timeout, closing. Please reopen if the problem persists with latest kernels.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.