[Bug 96255] New: [CHV] Surface 3 does not get correct EDID from firmware

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat May 28 01:20:50 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=96255

            Bug ID: 96255
           Summary: [CHV] Surface 3 does not get correct EDID from
                    firmware
           Product: DRI
           Version: XOrg git
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: stephenjust at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

On the Surface 3 (Atom x7 X8700), the kernel is unable to get the correct EDID
data for the display. As a result, the correct display dimensions are not set,
meaning that user-space programs that depend on this info do not have it. As an
example, Gnome would kick in to Hi-DPI mode if the correct dimensions were
available.

Windows seems to be able to fetch an EDID record for the display with the
proper dimensions set, and as far as I can tell it doesn't use any mechanisms
to override the EDID using a specific driver implying that the GPU could be
accessing it somehow.

I will attach an export of the Windows Registry showing what it can see. In
this file, DISPLAY\MEI9001\4 is the Surface's screen with the correct
dimensions specified.


Work around:
1. Build a kernel with CONFIG_DRM_LOAD_EDID_FIRMWARE=Y
2. Download attached EDID record (extracted on Windows), surface3.bin, to
/lib/firmware/edid/surface3.bin
3. Add drm_kms_helper.edid_firmware=DSI-1:edid/surface3.bin to your kernel line

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160528/6dfcde2b/attachment.html>


More information about the intel-gfx-bugs mailing list