[Bug 68451] [byt dsi] Baytrail/T DSI display not supported on ASUS T100TA

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Thu Apr 17 22:35:10 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=68451

Robert R. Howell <rhowell at uwyo.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rhowell at uwyo.edu

--- Comment #38 from Robert R. Howell <rhowell at uwyo.edu> ---
I'm seeing what I believe may be a related problem with the panel display on my
ASUS T100A, running 3.15-rc1.  The system, which was working reasonably well
with 3.14, and also the partly merged 3.15 code, seemed to break with the merge
of the latest i915 code into the kernel on about April 8.  

The basic problem is that the panel display and an external HDMI display come
up properly on boot, but if I do anything to turn off the panel display, such
as "xrandr --output VGA1 --off", then nothing I do after that is able to make
the panel display visible till I reboot.

After an "xrandr --output VGA1 --auto" the system seems to THINK the panel is
active, as indicated by xrandr output and also the implied limits of the
display when moving windows and the mouse from one display to the other, but
there just isn't any visible panel output.  The HDMI is fine.  I don't see any
error messages in any of the logs I've been able to check.  The system really
acts like some part of the video output chain is being disabled, and never gets
reenabled except by a reboot.  With versions of the kernel I comiled before the
April 8 driver merge, I am able to turn off then turn on the panel.  

For your information, I am using a video=VGA-1:1368x768e parameter at boot, and
also specify an edid file I created.

This is my first attempt to report a bug on bugzilla.kernel.org, and I'm also
relatively new to compiling the kernel, so if I should post this in a different
manner, just let me know.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the intel-gfx-bugs mailing list