Bug 104909 - external monitor not detected (HDMI)
Summary: external monitor not detected (HDMI)
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-02 00:05 UTC by Bill Nottingham
Modified: 2018-05-01 08:42 UTC (History)
3 users (show)

See Also:
i915 platform: KBL
i915 features: display/HDMI


Attachments
dmesg (88.41 KB, application/gzip)
2018-02-02 00:05 UTC, Bill Nottingham
no flags Details
dmesg from drm-tip (of 02/18) (557.75 KB, text/plain)
2018-02-26 03:51 UTC, Bill Nottingham
no flags Details
dmesg from drm-tip (of 03/01 (524.93 KB, text/plain)
2018-03-02 00:58 UTC, Bill Nottingham
no flags Details
dmesg from drm-tip (of 03/29) (665.16 KB, text/plain)
2018-03-30 02:48 UTC, Bill Nottingham
no flags Details

Description Bill Nottingham 2018-02-02 00:05:53 UTC
Created attachment 137123 [details]
dmesg

4.14.14-300.fc27.x86_64 (Fedora 27).

Thinkpad X1 Carbon (5th gen). Using GNOME on Wayland.

When I plug in a monitor to the HDMI port... nothing happens. It does not show up in the display panel, and is not lit up.

Thunderbolt/USB-C port through USB-C->HDMI adapter also does not light up display.

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88)
05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961

There are no kernel messages on plug/unplug of HDMI cable. EDID does not change when cable is plugged in.

No GPU errors from class/drm/card0/error. Cannot dump vbios (i915 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff)
Comment 1 Elizabeth 2018-02-02 15:38:44 UTC
From dmesg:
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:70:HDMI-A-1]
[drm:intel_hdmi_detect [i915]] [CONNECTOR:70:HDMI-A-1]
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK on first message, retry
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK for addr: 0050 w(1)
[drm:drm_do_probe_ddc_edid [drm]] drm: skipping non-existent adapter i915 gmbus dpb
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK on first message, retry
[drm:gmbus_xfer [i915]] GMBUS [i915 gmbus dpb] NAK for addr: 0040 w(1)
[drm:drm_dp_dual_mode_detect [drm_kms_helper]] DP dual mode HDMI ID:  (err -6)
[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:70:HDMI-A-1] disconnected
Comment 2 Jani Nikula 2018-02-07 12:28:26 UTC
Please try drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip
Comment 3 Jani Nikula 2018-02-07 12:28:58 UTC
(In reply to Jani Nikula from comment #2)
> Please try drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip

Also, please attach dmesg running that. And don't gzip the attachments, just use plain text.
Comment 4 Bill Nottingham 2018-02-26 03:51:11 UTC
Created attachment 137600 [details]
dmesg from drm-tip (of 02/18)

Here you go.
Comment 5 Bill Nottingham 2018-03-02 00:58:39 UTC
Created attachment 137741 [details]
dmesg from drm-tip (of 03/01

... and today's, while I'm here.
Comment 6 Jani Saarinen 2018-03-29 07:11:01 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 7 Bill Nottingham 2018-03-30 02:48:44 UTC
Created attachment 138439 [details]
dmesg from drm-tip (of 03/29)

Still happens, updated dmesg here.
Comment 8 Jani Saarinen 2018-04-25 11:13:43 UTC
Jani, Ville any advice here?
Comment 9 Jani Nikula 2018-04-25 11:39:11 UTC
It's pretty tough going with nothing to work with. It's as if we didn't get any indication of HDMI being plugged in.
Comment 10 Bill Nottingham 2018-04-25 13:42:14 UTC
Chance that this is hardware failure? Or would hardware failure not present in this way?
Comment 11 Jani Nikula 2018-04-25 13:56:26 UTC
(In reply to Bill Nottingham from comment #10)
> Chance that this is hardware failure? Or would hardware failure not present
> in this way?

If you could test your display with another machine, and your machine with another display, it would of course rule that out.

It might be good to get the dmesg from the USB Type-C adaptor case too, though I've seen those be problematic too.
Comment 12 Bill Nottingham 2018-04-25 14:04:33 UTC
Have done both - it happens with all displays I've found so far with this laptop recently, and at least one other laptop (different model of both laptop and Intel graphics) works with both the display and the USB-C adapter.

Have not been able to try Windows with this laptop, as I completely wiped it beforehand.
Comment 13 Bill Nottingham 2018-04-30 20:08:33 UTC
Laptop motherboard replacement fixed it. Closing as hardware issue.
Comment 14 Jani Saarinen 2018-05-01 08:42:06 UTC
Thanks, closing.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.