[Bug 104292] New: Resolution max problem since kernel 4.13

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Dec 16 17:45:55 UTC 2017


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

            Bug ID: 104292
           Summary: Resolution max problem since kernel 4.13
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: fce.valeins at libertysurf.fr
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Since upgrading kernel 4.12 to 4.13 or 4.14 I have a screen resolution problem.
My computer is a ZOTAC ZBOX CI547 nano with a graphics card Intel Corporation
HD Graphics 620 (rev 02)
With kernel 4.12 I have a maximum resolution of 1920x1080
Here is the return of the xrandr command :

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
530mm x 300mm
   1920x1080     60.00*+  50.00    59.94  
   1920x1080i    60.00    50.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      59.90  
   1280x960      60.00  
   1280x720      60.00    50.00    59.94  
   1152x720      59.97  
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       66.67    60.00    59.94  
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
but with a 4.13 or 4.14 kernel I have 1152x720

Screen 0: minimum 8 x 8, current 1152 x 720, maximum 32767 x 32767
DP1 connected primary 1152x720+0+0 (normal left inverted right x axis y axis)
530mm x 300mm
   1152x720      59.97* 
   1024x768      60.00  
   800x600       60.32    56.25  
   720x576       50.00  
   720x480       60.00    59.94  
   640x480       66.67    60.00    59.94  
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)



Here my Xorg log file for kernel 4.12.13-1-ARCH

https://pastebin.com/srjjir7R

and here Xorg log file for kernel 4.14.4-1-ARCH
https://pastebin.com/QbbHbs7C

the onlyd diffrence is

Kernel 4.14
[    13.047] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20170403
[    13.283] (II) intel(0): switch to mode 1920x1080 at 60.0 on DP1 using pipe 0,
position (0, 0), rotation normal, reflection none

Kernel 4.12
[    12.253] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20170818
[    12.632] (II) intel(0): switch to mode 1152x720 at 60.0 on DP1 using pipe 0,
position (0, 0), rotation normal, reflection none

it's the same with 4.13 kernel

I have try to set custom mode with :

cvt 1920 1080

# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088 1120
-hsync +vsync

xrandr --newmode "1920x1080_60.00"  173.00  1920 2048 2248 2576  1080 1083 1088
1120 -hsync +vsync
xrandr --addmode DP1 "1920x1080_60.00"

xrandr --output DP1 --mode "1920x1080_60.00"

xrandr: Configure crtc 0 failed

in dmesg  and journalctl I have this error

[dim. déc. 10 14:45:11 2017] [drm:intel_dp_get_link_train_fallback_values
[i915]] *ERROR* Link Training Unsuccessful

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


More information about the intel-gfx-bugs mailing list