Bug 1400593 - External display/projector via thunderbolt/DP not detected on MacBook Air [NEEDINFO]
Summary: External display/projector via thunderbolt/DP not detected on MacBook Air
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 25
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1386528
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 14:55 UTC by Alexander Todorov
Modified: 2019-01-09 12:54 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1386528
Environment:
Last Closed: 2017-02-23 23:01:41 UTC
Type: Bug
labbott: needinfo? (atodorov)


Attachments (Terms of Use)

Description Alexander Todorov 2016-12-01 14:55:34 UTC
+++ This bug was initially created as a clone of Bug #1386528 +++

Description of problem:

I'm using RHEL 7 on a MacBook Air (can provide more hw info if needed). With RHEL 7.1 and 7.2 kernels I was able to connect an external display via DisplayPort to VGA adapter connected to the Thunderbolt port. I've also used a DP-HDMI adapter which worked. I have verified the peripherals work fine on another computer.

The last time this was working for me was on Oct 1st 2016. Then it stopped working. ATM when I connect an external display it is not detected at all. 


Version-Release number of selected component (if applicable):
kernel-3.10.0-513.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Connect an external display/projector to a MacBook Air via DP/VGA adapter
2.
3.

Actual results:
External display not detected

Expected results:
Display is detected and I'm able to use this laptop for presentations


Additional info:

I've checked my yum.log and there are no signs of kernel upgrades between Sept and Oct.

... skip ...
Jul 23 11:42:00 Installed: qt5-qtwebkit-devel-5.6.1-3.b889f46git.el7.x86_64
Jul 29 01:44:20 Installed: dos2unix-6.0.3-4.el7.x86_64
Sep 13 00:15:11 Installed: rh-python34-runtime-2.0-5.el7.x86_64
Sep 13 00:15:12 Installed: rh-python34-python-pip-1.5.6-4.el7.noarch
Sep 13 00:15:13 Installed: rh-python34-python-setuptools-11.3.1-2.el7.noarch
Sep 13 00:15:13 Installed: rh-python34-python-3.4.2-13.el7.x86_64
Sep 13 00:15:15 Installed: rh-python34-python-libs-3.4.2-13.el7.x86_64
Sep 13 00:16:46 Installed: rh-python34-python-devel-3.4.2-13.el7.x86_64
Sep 13 00:16:46 Installed: rh-python34-python-virtualenv-1.11.6-1.el7.noarch
Sep 28 14:15:49 Installed: zoom-2.0.63547.0830-1.x86_64
Oct 17 09:26:05 Updated: mate-utils-common-1.14.1-1.el7.noarch
Oct 17 09:26:06 Updated: caja-extensions-common-1.14.1-1.el7.noarch
Oct 17 09:26:06 Updated: mate-control-center-filesystem-1.14.1-1.el7.x86_64
Oct 17 09:26:06 Updated: 32:bind-license-9.9.4-29.el7_2.4.noarch
... skip ...


A few days ago I've updated to the latest 7.3 nightly hoping to fix this or at least be able to debug it a bit more but I'm stuck.

Searching on the Internet I found this:

# cat /sys/class/drm/card0-DP-1/enabled
disabled


If I reboot and leave the external screen connected then it is detected and I'm able to use it somewhat. Both the main screen and external screen are adjusted to the same resolution by default.


The above info and the fact that I haven't changed pretty much anything before this stopped working leads me to think this may be related to some power saving features. Let me know what other information you need in order to debug this.

--- Additional comment from Alexander Todorov on 2016-10-26 11:55 EEST ---

More info I was able to dig out:

окт 26 10:43:17 aero kernel: [drm] stuck on render ring
окт 26 10:43:17 aero kernel: [drm] GPU HANG: ecode 8:0:0x85dffffb, in Xorg [1611], reason: Ring hung, action: reset
окт 26 10:43:17 aero kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
окт 26 10:43:17 aero kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
окт 26 10:43:17 aero kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
окт 26 10:43:17 aero kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
окт 26 10:43:17 aero kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
окт 26 10:43:17 aero kernel: drm/i915: Resetting chip after gpu hang

--- Additional comment from Alexander Todorov on 2016-10-26 12:06 EEST ---

# cat /etc/X11/xorg.conf.d/98-mba_bl.conf 
# as per https://bugzilla.redhat.com/show_bug.cgi?id=989555#c17
# uncomment below if brightness control still doesn't work after
# mba6x_bl is loaded

Section "Device"
    Identifier      "Intel Graphics"
    Driver          "intel"
    Option          "Backlight"     "mba6x_backlight"
EndSection


NOTE: mba6x_backlight is an out of tree driver that I compiled myself. Sources are available from
https://github.com/atodorov/mba6x_bl/commits/rhel_7.2_3.10.0-327.el7.x86_64

--- Additional comment from Hans de Goede on 2016-10-26 14:09:14 EEST ---

(In reply to Alexander Todorov from comment #2)
> NOTE: mba6x_backlight is an out of tree driver that I compiled myself.
> Sources are available from
> https://github.com/atodorov/mba6x_bl/commits/rhel_7.2_3.10.0-327.el7.x86_64

Since you've hardware to test this with, any chance you could work on upstreaming this driver ? I can help you with the kernel process if necessary.

--- Additional comment from Alexander Todorov on 2016-10-27 14:00:59 EEST ---


(In reply to Hans de Goede from comment #3)
> (In reply to Alexander Todorov from comment #2)
> > NOTE: mba6x_backlight is an out of tree driver that I compiled myself.
> > Sources are available from
> > https://github.com/atodorov/mba6x_bl/commits/rhel_7.2_3.10.0-327.el7.x86_64
> 
> Since you've hardware to test this with, any chance you could work on
> upstreaming this driver ? I can help you with the kernel process if
> necessary.

Thanks for the proposal but it would be far stretch for me to actually do this. I merely cloned the git repo and built the source for RHEL, altering some of the patches here and there. I don't have the technical knowledge to actually maintain the driver upstream. 

I've filed an issue with the original author to see what his intentions are:
https://github.com/patjak/mba6x_bl/issues/57

--- Additional comment from Alexander Todorov on 2016-12-01 16:54:59 EET ---

ping, any update here? I've tried the same hardware with Fedora25 live cd and still all of the ports are disabled.

Comment 1 Alexander Todorov 2016-12-01 14:59:47 UTC
Tested with Fedora 25 Workstation x86_64 live media. I can't get the external projector to work. The ports are still disabled. Software versions:

kernel-4.8.6-300.fc25
xorg-x11-drv-intel-2.99.917-26.20160929.fc25

when pulgging in the DP adapter into the Thunderbolt port I only saw the following in the log:

thunderbolt 0000:07:00.0: resetting error on 0:b
thunderbolt 0000:07:00.0: 0:b: got unplug event for disconnected port, ignoring

The hardware is:
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 6000 (rev 09)


Internet indicates this is not an isolated occurence. Some users report the same issue on Lenovo hardware with Intel graphics. However there's no solution I could find.

Comment 2 Laura Abbott 2017-01-17 01:11:39 UTC
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Laura Abbott 2017-02-23 23:01:41 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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