Bug 1044781 - Chromebook Pixel built-in display goes blank when external display connected, but is still considered active
Summary: Chromebook Pixel built-in display goes blank when external display connected,...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 00:58 UTC by Kenton Varda
Modified: 2014-06-03 06:05 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-03 06:05:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Kenton Varda 2013-12-19 00:58:40 UTC
Description of problem:

On a Chromebook Pixel, when an external DisplayPort display is connected, the built-in display goes blank.  However, the desktop environment clearly thinks the built-in display is still active:  the gnome top bar doesn't appear on the external display and I can still move my mouse off the side of the screen as if on to the other display.  I just can't see anything.

Moreover, on disconnecting the external display, the built-in display remains off, making the machine unusable until rebooted.

Work-around is to go to display settings (after connecting; possible by right-clicking on the desktop) and disable the built-in display from there (although this means only one display can be used at a time), and then reboot when disconnecting the external display later.

Version-Release number of selected component (if applicable):

Whatever shipped with Fedora 20 on release day.

How reproducible:

Always

Steps to Reproduce:
1. Boot machine into X.
2. Connect external display via DisplayPort (2560x1440 in my case).

Actual results:

Built-in display goes blank but desktop is still extended to it.  External display works but is treated as secondary.

Expected results:

Both displays live.

Additional info:

Previously had Ubuntu 13.04 on the same hardware and didn't see this problem (although it had numerous other problems...).

Please let me know what debug info would be useful.

Comment 1 Hans de Goede 2014-06-02 18:29:36 UTC
This sounds like a brightness control issue, can you please run through all the test suggestions listed here: http://hansdegoede.livejournal.com/13889.html

And gather the logs, etc. requested there and report back here with the results ? First step would be to see if backlight control works at all, if it does, first thing to try would be to see if you can get the screen to work again using the backlight buttons.

Also please please try the various suggested kernel cmdline options, and see if any of those help and please check ls /sys/class/backlight for all of them. Note I realize the pixel is not a regular notebook, but still please try this.

Comment 2 Hans de Goede 2014-06-02 18:36:08 UTC
Also can you please try the latest 3.15 kernel? With some luck this has already been fixed, you cfan find the latest 3.15 kernel build for Fedora here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=520926

Download the kernel-3.15...rpm for your architecture and then install it using:

sudo rpm -ivh kernel-3.15...rpm

Note when installing kernels it is important to rpm -i so that you keep your current kernel as a backup.

Comment 3 Kenton Varda 2014-06-03 00:39:33 UTC
Sorry, this problem eventually forced me to uninstall Fedora, so I'm no longer in a position to provide more details.

Comment 4 Hans de Goede 2014-06-03 06:05:01 UTC
Hi,

(In reply to Kenton Varda from comment #3)
> Sorry, this problem eventually forced me to uninstall Fedora, so I'm no
> longer in a position to provide more details.

Sorry for not getting around to looking into this sooner. Given the above I'm going to close this bug.

Regards,

Hans


Note You need to log in before you can comment on or make changes to this bug.