HDMI works only if plugged in at boot.

doomsday.wombats · 2017-01-17 01:13:03

I've been having issues with getting HDMI on my Razer Blade Stealth (late 2016 model) to work.

If my laptop is off, I plugin HDMI, and then start my laptop, all is well.

If my laptop is on, I plugin HDMI, no HDMI is detected.

I just did a pacman -Syu and I have xf86-video-intel-1:2.99.917+747+g028c946d-1 installed.

lspci -v:

00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Razer USA Ltd. Device 6752
        Flags: bus master, fast devsel, latency 0, IRQ 281
        Memory at db000000 (64-bit, non-prefetchable) [size=16M]
        Memory at 90000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [40] Vendor Specific Information: Len=0c <?>
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [100] Process Address Space ID (PASID)
        Capabilities: [200] Address Translation Service (ATS)
        Capabilities: [300] Page Request Interface (PRI)
        Kernel driver in use: i915
        Kernel modules: i915

xrandr (with HDMI not working):

Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 280mm x 160mm
   2560x1440     59.95 +  39.97
   1920x1440     60.00
   1856x1392     60.01
   1792x1344     60.01
   2048x1152     60.00
   1920x1080     60.00*
   1600x1200     60.00
   1400x1050     59.98
   1600x900      60.00
   1280x1024     60.02
   1280x960      60.00
   1368x768      60.00
   1280x720      60.00
   1024x768      60.00
   1024x576      60.00
   960x540       60.00
   800x600       60.32    56.25
   864x486       60.00
   640x480       59.94
   720x405       60.00
   640x360       60.00
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

xrandr (with HDMI working - AKA - plugged in before boot):

Screen 0: minimum 8 x 8, current 3600 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+1680+0 (normal left inverted right x axis y axis) 280mm x 160mm
   2560x1440     59.95 +  39.97
   1920x1440     60.00
   1856x1392     60.01
   1792x1344     60.01
   2048x1152     60.00
   1920x1080     60.00*
   1600x1200     60.00
   1400x1050     59.98
   1600x900      60.00
   1280x1024     60.02
   1280x960      60.00
   1368x768      60.00
   1280x720      60.00
   1024x768      60.00
   1024x576      60.00
   960x540       60.00
   800x600       60.32    56.25
   864x486       60.00
   640x480       59.94
   720x405       60.00
   640x360       60.00
DP1 connected 1680x1050+0+8 (normal left inverted right x axis y axis) 430mm x 270mm
   1680x1050     59.95*+
   1280x1024     75.02    60.02
   1152x864      75.00
   1280x720      60.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
   720x400       70.08
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Dmesg does not show any errors in either case.

Running xrandr --auto doesn't detect new display.

Display isn't detected via gnome-control-center either.

Any ideas?

Last edited by doomsday.wombats (2017-01-18 22:27:54)

Starfish · 2017-01-17 12:40:07

To me this looks like the kernel and the drivers are all working fine, while there is just no hotplugging enabled for this particular device.
Although I have never done it myself, I would suggest you try to write your own udev rule:
https://wiki.archlinux.org/index.php/Udev

doomsday.wombats · 2017-01-17 22:57:19

I *think* I figured out the issue.

I made a xorg configuration file a while ago to disable my touchscreen. If I remove this file...it seems to work normally.

File:

Section "InputClass"
    Identifier         "Touchscreen catchall"
    MatchIsTouchscreen "on"
    Option "Ignore" "on"
EndSection

Strangely enough, if the screen was plugged in at boot, and then I unplugged it, I could plug it back in and it would work fine.

doomsday.wombats · 2017-01-18 22:42:27

Sadly, that was a false alarm for the fix (not sure why it worked for as long as it did).

I'm fairly certain it is not my hardware (faulty cable or monitor), as I have tried several different cables (with and without adapters), monitors, projectors, etc...

As far as I can see, the udev rules to do monitor hotplugging run a script that run xrandr. I can't get xrandr to do anything manually, so I'm not quite sure adding a custom udev rule will work.

I'm know very little about udev, but I don't see any events when I run the following command and plug and unplug the HDMI cable:

udevadm monitor --environment --udev

Does this maybe indicate a driver level issue?

Is there something I'm missing on how udev and hotplugging works?

Starfish · 2017-01-19 12:55:34

Alright, lets try something different:
Unplug the device and run

lshw -short > file1.asc

Plug in the device and run

lshw -short > file2.asc

and finally

diff file1.asc file2.asc

Does it give you anything?

Last edited by Starfish (2017-01-19 12:56:25)

nartes · 2017-01-20 15:53:04

What's about suspend?

There is an issue with your driver on the kernel bugzilla.
It tells that suspend as well might affect HDMI output,
so forcing you to reboot the system.
More info here.

I still have a similar issue regarding audio over HDMI on radeon open source driver.

doomsday.wombats · 2017-01-20 21:25:39

I've been trying to reproduce this error for the last day...hasn't started doing it again.

It always seems like I have to say "It's fixed!" before it breaks again...so there.

I'll post back with the lshw info if it occurs again. I did this before and I don't recall there being any differences, but I'll post the results nonetheless.

I don't really suspend my laptops that much (I just turn them off). But I'm guessing the suspend bug is connected to ACPI, so it could be a possibility?

I'll hopefully be able to reproduce this error again so we can investigate further.

doomsday.wombats · 2017-01-21 21:33:45

Finally was able to reproduce the bug. There wasn't any difference between lshw when working vs not working:

$ lshw -short
H/W path       Device  Class          Description
=================================================
                       system         Blade Stealth (RZ09-01962E12)
/0                     bus            Razer
/0/0                   memory         64KiB BIOS
/0/25                  memory         16GiB System Memory
/0/25/0                memory         8GiB Row of chips LPDDR3 Synchronous 1867 MHz (0.5 ns)
/0/25/1                memory         8GiB Row of chips LPDDR3 Synchronous 1867 MHz (0.5 ns)
/0/29                  memory         128KiB L1 cache
/0/2a                  memory         512KiB L2 cache
/0/2b                  memory         4MiB L3 cache
/0/2c                  processor      Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
/0/100                 bridge         Intel Corporation
/0/100/2               display        Intel Corporation
/0/100/14              bus            Sunrise Point-LP USB 3.0 xHCI Controller
/0/100/14/0    usb1    bus            xHCI Host Controller
/0/100/14/0/6          communication  Bluetooth wireless interface
/0/100/14/0/7          multimedia     USB Camera
/0/100/14/0/8          input          Razer Blade Stealth
/0/100/14/0/9          input          Touchscreen
/0/100/14/1    usb2    bus            xHCI Host Controller
/0/100/14.2            generic        Sunrise Point-LP Thermal subsystem
/0/100/15              generic        Sunrise Point-LP Serial IO I2C Controller #0
/0/100/15.1            generic        Sunrise Point-LP Serial IO I2C Controller #1
/0/100/16              communication  Sunrise Point-LP CSME HECI #1
/0/100/1c              bridge         Intel Corporation
/0/100/1c/0    wlp1s0  network        QCA6174 802.11ac Wireless Network Adapter
/0/100/1c.4            bridge         Sunrise Point-LP PCI Express Root Port #5
/0/100/1d              bridge         Sunrise Point-LP PCI Express Root Port #9
/0/100/1d/0            storage        NVMe SSD Controller
/0/100/1e              generic        Sunrise Point-LP Serial IO UART Controller #0
/0/100/1f              bridge         Intel Corporation
/0/100/1f.2            memory         Memory controller
/0/100/1f.3            multimedia     Intel Corporation
/0/100/1f.4            bus            Sunrise Point-LP SMBus
/1                     power          empty (NULL)

Last edited by doomsday.wombats (2017-01-21 21:34:43)

nartes · 2017-01-22 07:57:12

I am guessing that suspend bug is related to the video driver itself. Would you try to reproduce the bug against suspend. It might be relevant to enable debug output in kernel module for the driver if there is any. If it succeeds then provide kernel logs for both boot ups.

Last edited by nartes (2017-01-22 07:57:43)

mishoo · 2017-01-23 11:50:04

I got the same problem after pacman -Syu today. I have the exact same version of xf86-video-intel.

I can confirm that plugging in the HDMI cable while the laptop was powered off “fixed” the issue (doing a reboot with the HDMI already connected didn't help). The only difference here is that when it wasn't working, xrandr -q | grep HDMI did not output anything (no “HDMI1 disconnected” line).

doomsday.wombats · 2017-01-26 01:00:37

Not sure if this is relevant to this issue, but other display options do not seem to be effected (USB-C works when HDMI does not).

seth · 2017-01-26 08:47:51

Why does your working setup list DP1 being connected (but no HDMI)? Some adapter involved?
Does it fail with any output device? Can you try another monitor, Tv, etc.?

doomsday.wombats · 2017-01-26 19:30:33

I've tried a handful of monitors and projectors. Whether I use an adapter, or use straight HDMI, it shows up as DP1. I get the same bug regardless of the monitor/projector used (plugged in at boot works, not plugged in at boot fails...usually...maybe every 10 reboots it might work without being plugged in at boot).

I also thought the HDMI showing up as DP1 was curious. Since I only have 2 ports for video (USB-C and HDMI), I'm not sure what the 2 HDMI ports refer to (I have 6 monitors, 4 that I've seen in use plus the 2 HDMI entries).

Doesn't seem like they are being used by some internal HDMI montior (not sure if embedded HDMI is a thing):

$ grep HDMI /var/lib/gdm/.local/share/xorg/Xorg.0.log
[    12.339] (II) intel(0): Output HDMI1 has no monitor section
[    12.340] (II) intel(0): Enabled output HDMI1
[    12.340] (II) intel(0): Output HDMI2 has no monitor section
[    12.340] (II) intel(0): Enabled output HDMI2
[    12.605] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event15)
[    12.605] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event16)
[    12.605] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event17)

This might be a stupid question, but are they separate entries for audio/touchscreen (my knowledge of Linux device internals is pretty low)?

$ less /proc/bus/input/devices
...
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input16
U: Uniq=
H: Handlers=event15 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:1f.3/sound/card0/input17
U: Uniq=
H: Handlers=event16 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0018 Vendor=06cb Product=5f41 Version=0100
N: Name="15320205:00 06CB:5F41"
P: Phys=i2c-15320205:00
S: Sysfs=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-8/i2c-15320205:00/0018:06CB:5F41.0005/input/input18
U: Uniq=
H: Handlers=event17 mouse2 
B: PROP=5
B: EV=b
B: KEY=e520 10000 0 0 0 0
B: ABS=673800001000003

imissmymind · 2017-01-30 02:56:39

I just bought a razer blade stealth and am having this exact same problem. I am in the process of trying to figure it out so any guidance here would be appreciated

Arch Linux

#1 2017-01-17 01:13:03

HDMI works only if plugged in at boot.

#2 2017-01-17 12:40:07

Re: HDMI works only if plugged in at boot.

#3 2017-01-17 22:57:19

Re: HDMI works only if plugged in at boot.

#4 2017-01-18 22:42:27

Re: HDMI works only if plugged in at boot.

#5 2017-01-19 12:55:34

Re: HDMI works only if plugged in at boot.

#6 2017-01-20 15:53:04

Re: HDMI works only if plugged in at boot.

#7 2017-01-20 21:25:39

Re: HDMI works only if plugged in at boot.

#8 2017-01-21 21:33:45

Re: HDMI works only if plugged in at boot.

#9 2017-01-22 07:57:12

Re: HDMI works only if plugged in at boot.

#10 2017-01-23 11:50:04

Re: HDMI works only if plugged in at boot.

#11 2017-01-26 01:00:37

Re: HDMI works only if plugged in at boot.

#12 2017-01-26 08:47:51

Re: HDMI works only if plugged in at boot.

#13 2017-01-26 19:30:33

Re: HDMI works only if plugged in at boot.

#14 2017-01-30 02:56:39

Re: HDMI works only if plugged in at boot.

Board footer