[Bug 90128] Big monitor has blank display (HDMI or DVI) in any kernel since and including 3.13 (despite earlier fixes)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 28 19:33:38 UTC 2017


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

philipmorant at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #9 from philipmorant at gmail.com ---
After
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
and
git clone  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I am unable to find commit 0a03ea9496b49746b4964d05cc1f483385d1df8a
However commit bc49a7831b1137ce1c2dda1c57e3631655f5d2ae comes a few days later
than 0a03ea, and I can see that the problematic function
hdmi_port_clock_limit() has been changed.  So I compiled it and tested.

The situation has not changed.  At boot up the WQHD monitor is switched off.  I
can call xrandr --newmode and xrandr --addmode and xrandr --output HDMI1 ...,
and xrandr (and also the ubuntu Display applet) report that they're happy, BUT
the monitor is switched to standby mode, ie not showing anything.

Neither syslog nor xorg.log show any errors.  This is all:
[  1566.989] (II) intel(0): resizing framebuffer to 4480x1440
[  1567.034] (II) intel(0): switch to mode 1920x1080 at 60.0 on VGA1 using pipe 1,
position (2560, 360), rotation normal, reflection none
[  1567.153] (II) intel(0): switch to mode 2560x1440 at 29.9 on HDMI1 using pipe
0, position (0, 0), rotation normal, reflection none

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


More information about the intel-gfx-bugs mailing list