Bug 102928 - [IGT] [KBL] Missing 3180x2160_60Hz mode
Summary: [IGT] [KBL] Missing 3180x2160_60Hz mode
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: PatchSubmitted
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-21 14:27 UTC by Wolfgang Haupt
Modified: 2018-04-20 20:16 UTC (History)
2 users (show)

See Also:
i915 platform: KBL
i915 features: display/LSPCON


Attachments
vbios.dump (64.00 KB, application/octet-stream)
2017-09-21 14:27 UTC, Wolfgang Haupt
no flags Details
dmesg.log (123.90 KB, text/plain)
2017-09-21 18:35 UTC, Wolfgang Haupt
no flags Details
dmesg drm-tip + yuv 4:2:0 patches (125.34 KB, text/plain)
2017-09-22 11:29 UTC, Wolfgang Haupt
no flags Details
dmesg after some testing (121.93 KB, text/plain)
2017-09-28 20:47 UTC, Wolfgang Haupt
no flags Details

Description Wolfgang Haupt 2017-09-21 14:27:13 UTC
Created attachment 134409 [details]
vbios.dump

With kernel 4.14rc1 I miss the 4k 60Hz resolutions.

uname -a:
Linux lrplayer 4.14.0-rc1 #1 SMP Tue Sep 19 20:16:17 CEST 2017 x86_64 GNU/Linux

Linux Distribution:
LibreELEC

Machine:
Intel NUC7i5BNK

Display Connector:
Hdmi (but it's this DP->HDMI Converter Chip afaik)

dmesg:
http://sprunge.us/TKbO
Comment 1 Jani Nikula 2017-09-21 15:14:37 UTC
(In reply to Wolfgang Haupt from comment #0)
> dmesg:
> http://sprunge.us/TKbO

Please ensure the dmesg starts at boot (use log_buf_len=4M or something if needed), and attach dmesg to the bug. Don't reference external sites that are bound to lose the data.
Comment 2 Ville Syrjala 2017-09-21 16:09:03 UTC
[    3.348528] [drm:drm_helper_probe_single_connector_modes] [CONNECTOR:58:DP-1]
[    3.348534] [drm:intel_dp_detect] [CONNECTOR:58:DP-1]
[    3.348831] [drm:lspcon_wake_native_aux_ch] Native AUX CH up, DPCD version: 1.2
[    3.348847] [drm:lspcon_resume] LSPCON recovering in PCON mode after 0 ms

It's our old friend LSPCON :(

The 4:2:0 support for that is still WIP. You may want to try the patches here:
https://patchwork.freedesktop.org/series/28536/

Assuming you would apply them on top of drm-tip you should only need the last three. Not sure if the entire series would cleanly apply against 4.14-rc.
Comment 3 Wolfgang Haupt 2017-09-21 18:35:16 UTC
Created attachment 134412 [details]
dmesg.log

Attached dmesg output beginning at boot.
Comment 4 Wolfgang Haupt 2017-09-22 11:29:22 UTC
Created attachment 134441 [details]
dmesg drm-tip + yuv 4:2:0 patches

I built the drm-tip branch and applied the 3 patches.
Now I can choose 4k@60 again.
However when I reboot, BIOS and Bootloader screen turns green.
After transition to user space it seems to go away.
Attached you can find the dmesg output.
Comment 5 Wolfgang Haupt 2017-09-28 20:47:00 UTC
I've been testing a few days now and also tried different builds.
For some reason I always have a black screen flickering like with kernel 4.13 now and can't really figure out why this happens.

I tried to diff the dmesg output and miss the line that states "YCbCr 4:2:0".
Also the screen does not turn green anymore when in bios and bootloader state.
But I see the debug outputs of the yuv 4:2:0 patches.
Current dmesg.log attached.
Any thoughts?
Comment 6 Wolfgang Haupt 2017-09-28 20:47:37 UTC
Created attachment 134557 [details]
dmesg after some testing
Comment 7 Wolfgang Haupt 2017-10-18 17:50:47 UTC
I kept testing a little bit and built the drm-tip branch occasionally.
While I now always have 3180x2160_60Hz available there's one major issue, namely black screen flickering.
Additionally I'm very interested in yuv 4:2:0 support.

How can we proceed?
The bug title has nothing to do with the mentioned problem nor with yuv 4:2:0.
Shall I close this one and open a dedicated one for the black screen flickering issue?
Comment 8 Elizabeth 2017-10-19 14:38:35 UTC
(In reply to Wolfgang Haupt from comment #7)
> I kept testing a little bit and built the drm-tip branch occasionally.
> While I now always have 3180x2160_60Hz available there's one major issue,
> namely black screen flickering.
> Additionally I'm very interested in yuv 4:2:0 support.
> 
> How can we proceed?
> The bug title has nothing to do with the mentioned problem nor with yuv
> 4:2:0.
> Shall I close this one and open a dedicated one for the black screen
> flickering issue?
Hello Wolfgang,
This bug should be closed once the patches are merged upstream. For the other issues the best will be to open a dedicated one, as you mentioned before.
Comment 9 Elizabeth 2018-03-05 19:34:49 UTC
Hi, any news on this? Thank you.
Comment 10 Jani Saarinen 2018-03-29 07:10:29 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 11 Jani Saarinen 2018-04-20 14:27:54 UTC
Closing, please re-open if still occurs.


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.