Bug 111410 - Gemini Lake - can't change refresh rate with default EDID and loading of custom EDID fails with eDP
Summary: Gemini Lake - can't change refresh rate with default EDID and loading of cust...
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: Triaged
Depends on:
Reported: 2019-08-16 09:32 UTC by tempel.julian
Modified: 2019-08-22 11:29 UTC (History)
1 user (show)

See Also:
i915 platform: GLK
i915 features: display/eDP


Note You need to log in before you can comment on or make changes to this bug.
Description tempel.julian 2019-08-16 09:32:30 UTC
Device is a Trekstor Surfbook A13B notebook with Celeron N4000 (Graphics 600) SoC. It features a 1080p eDP display (without panel self refresh feature).

The display's default EDID offers 59.9xHz and 48Hz for 1080p.
But: When switching to the 48Hz resolution via xrandr, the display continues running with 59.9xHz. Though some applications expect 48Hz then (e.g. mpv), causing bad stutter.
On Windows, changing refresh rate to 48Hz works without issues.

Also, loading a custom EDID or using custom Xorg modelines doesn't help, the display always runs with 59.9xHz and the resolutions/refresh rates of the custom EDID aren't even parsed correctly (only 59.9xHz are offered). Furthermore, the display then only runs with limited brightness level range, causing a washed out look.
On Windows, installing the very same EDID as custom monitor driver works correctly: The resolutions/refresh rates are parsed correctly, it correctly uses full range brightness levels and the display actually switches to the target refresh rates.

Not being able to use different refresh rates is quite annoying, as watching movies etc. is not optimal with 59.9xHz.
Comment 1 tempel.julian 2019-08-16 09:56:02 UTC
That's with linux 5.2.8 and xorg 1.20.5. Happens with modesetting DDX, xf86-video-intel and also on Wayland.
Comment 2 Lakshmi 2019-08-22 11:29:13 UTC
Can you please attach the dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M?

Also, Can you please try to reproduce this issue with drm-tip (https://cgit.freedesktop.org/drm-tip).

Dmesg from drmtip testing would be helpful for investigation.

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.