<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - NUC6i5SYB Linux screen blanks 2 seconds during use (displayport only?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99610#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - NUC6i5SYB Linux screen blanks 2 seconds during use (displayport only?)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99610">bug 99610</a> from <a class="email" href="mailto:grantgrundler@gmail.com" title="ggg <grantgrundler@gmail.com>"> ggg</a> <pre>I've switch to HDMI port and I'm getting 3840x2160 (same) resolution. But "black screen for 2 seconds" symptom is not reproducible. :/ It was very reproducible with DisplayPort. It's possible the frame rate is slower with HDMI; I don't know how to check that. The mini-to-normal DisplayPort cable is 1.8m length and not branded (AFAICT) on the connectors. The cable has : "DisplayPort cable E342987 AWM style 20276 80c 30v VW-1" printed on the cable. I don't think the DisplayPort cable is defective since I've been using the same cable all along and it's not been abused. I just want to include this info in case someone thinks it's a problem with the cable. [comments on about clock speed follows - seems like a red herring though] The Xorg.0.log (this boot) has the following info: [ 5.018] (II) modeset(0): Supported detailed timing: [ 5.018] (II) modeset(0): clock: 297.0 MHz Image Size: 608 x 345 mm [ 5.018] (II) modeset(0): h_active: 3840 h_sync: 4016 h_sync_end 4104 h_blank_end 4400 h_border: 0 [ 5.018] (II) modeset(0): v_active: 2160 v_sync: 2168 v_sync_end 2178 v_blanking: 2250 v_border: 0 [ 5.018] (II) modeset(0): Ranges: V min: 24 V max: 75 Hz, H min: 30 H max: 90 kHz, PixClock max 305 MHz [ 5.018] (II) modeset(0): Monitor name: U28D590 [ 5.018] (II) modeset(0): Serial No: HCPGxxxxxx In the previous Xorg.0.log using DisplayPort, I see the corresponding lines for the 3840x2160 output: [262565.377] (II) modeset(0): Supported detailed timing: [262565.377] (II) modeset(0): clock: 533.2 MHz Image Size: 607 x 345 mm [262565.377] (II) modeset(0): h_active: 3840 h_sync: 3888 h_sync_end 3920 h_blank_end 4000 h_border: 0 [262565.377] (II) modeset(0): v_active: 2160 v_sync: 2163 v_sync_end 2168 v_blanking: 2222 v_border: 0 So it looks like DisplayPort is running a much higher clock frequency than with HDMI. Is that expected/correct? The 2560x1440 output (openarena switches to this): [262565.377] (II) modeset(0): Supported detailed timing: [262565.377] (II) modeset(0): clock: 241.5 MHz Image Size: 607 x 345 mm [262565.377] (II) modeset(0): h_active: 2560 h_sync: 2608 h_sync_end 2640 h_blank_end 2720 h_border: 0 [262565.377] (II) modeset(0): v_active: 1440 v_sync: 1443 v_sync_end 1448 v_blanking: 1481 v_border: 0 [262565.377] (II) modeset(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 134 kHz, PixClock max 545 MHz [262565.377] (II) modeset(0): Monitor name: U28D590 So I'm not convinced this is related to cable or clock speed since the symptom was occurring with 241.5 Mhz clock speed as well. grundler@gggnuc6:~$ xdriinfo Screen 0: i965 grundler@gggnuc6:~$ xdpyinfo name of display: :0.0 version number: 11.0 vendor string: The X.Org Foundation vendor release number: 11900000 X.Org version: 1.19.0 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding: 32, LSBFirst, 32 image byte order: LSBFirst number of supported pixmap formats: 7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range: minimum 8, maximum 255 focus: window 0x380000f, revert to PointerRoot number of extensions: 29 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS DRI2 DRI3 GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM Present RANDR RECORD RENDER SECURITY SGI-GLX SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-DGA XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo default screen number: 0 number of screens: 1 screen #0: dimensions: 3840x2160 pixels (1016x571 millimeters) resolution: 96x96 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32 root window id: 0xe8 depth of root window: 24 planes number of colormaps: minimum 1, maximum 1 default colormap: 0x20 default number of colormap cells: 256 preallocated pixels: black 0, white 16777215 options: backing-store WHEN MAPPED, save-unders NO largest cursor: 256x256 current input event mask: 0xfa803f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMask EnterWindowMask LeaveWindowMask ExposureMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals: 40 default visual id: 0x21 visual: visual id: 0x21 class: TrueColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff0000, 0xff00, 0xff significant bits in color specification: 8 bits visual: visual id: 0x22 class: DirectColor depth: 24 planes available colormap entries: 256 per subfield red, green, blue masks: 0xff0000, 0xff00, 0xff significant bits in color specification: 8 bits ...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>