Second display does not show up on dock of Lenovo Helix 2

Bug #1816860 reported by udippel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

https://bugs.freedesktop.org/show_bug.cgi?id=109750

---

To me a deal-breaker: I bought the Helix 2 as machine on the dock, and I also bought the one out of the three docks that doesn't need extra driver (so it says), the 4X10H04503. I stuck the tablet into it, with Windows, and the second display came up without any additional driver.
With kubuntu 18.04 I can't make it appear. xrandr doesn't show it.
Now I wonder, where else it might pop up? I mean, the dock works, I ran a unified Logitech receiver on it, and from the first second mouse and keyboard are available to my *buntu installation, of course the grub menu.

I am quite disheartened, since I don't feel like going back to Windows after some 20 years on *nix.
I am willing to help out as much as my very limited abilities allow me to.
I can't believe that a dock which actually supplies power and keyboard and mouse data does not supply any information about the second monitor?
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
InstallationDate: Installed on 2019-02-16 (4 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 20CHS10P02
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-45-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/31/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N17ETA2W (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CHS10P02
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 11
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
dmi.product.family: ThinkPad Helix 2nd
dmi.product.name: 20CHS10P02
dmi.product.version: ThinkPad Helix 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I am keen to figure this problem out. But first please run this command to send us more information about the machine (while the dock is connected):

  apport-collect 1816860

affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
udippel (udippel) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected bionic ubuntu
description: updated
Revision history for this message
udippel (udippel) wrote : DpkgLog.txt

apport information

Revision history for this message
udippel (udippel) wrote : Lspci.txt

apport information

Revision history for this message
udippel (udippel) wrote : Lsusb.txt

apport information

Revision history for this message
udippel (udippel) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
udippel (udippel) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
udippel (udippel) wrote : ProcEnviron.txt

apport information

Revision history for this message
udippel (udippel) wrote : ProcInterrupts.txt

apport information

Revision history for this message
udippel (udippel) wrote : ProcModules.txt

apport information

Revision history for this message
udippel (udippel) wrote : UdevDb.txt

apport information

Revision history for this message
udippel (udippel) wrote : XorgLog.txt

apport information

Revision history for this message
udippel (udippel) wrote : XorgLogOld.txt

apport information

Revision history for this message
udippel (udippel) wrote : Xrandr.txt

apport information

Revision history for this message
udippel (udippel) wrote : xdpyinfo.txt

apport information

Changed in xorg-server (Ubuntu):
importance: Undecided → Low
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. It looks like an Intel-graphics-only system. So if the extra display doesn't show up in xrandr, can you please run this command to see if it's showing up in the kernel?

  grep . /sys/class/drm/*/enabled
  grep . /sys/class/drm/*/status
  grep . /sys/class/drm/*/dpms

Ideally both with and without the dock connected.

Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I mean please send us the output from all of those commands.

Revision history for this message
udippel (udippel) wrote :

udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/enabled
/sys/class/drm/card0-eDP-1/enabled:enabled
/sys/class/drm/card0-HDMI-A-1/enabled:disabled
/sys/class/drm/card0-HDMI-A-2/enabled:disabled
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/status
/sys/class/drm/card0-eDP-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
/sys/class/drm/card0-HDMI-A-2/status:disconnected
udippel@Uwe-ThinkPad-Helix-2nd:~$ grep . /sys/class/drm/*/dpms
/sys/class/drm/card0-eDP-1/dpms:On
/sys/class/drm/card0-HDMI-A-1/dpms:Off
/sys/class/drm/card0-HDMI-A-2/dpms:Off

Seriously boring, I agree. Why thrice?
Also on Windows 10 Pro it is far from flawless. When started with the tablet in the dock, the second monitor isn't recognized either. But when taken off and put back or when the power supply to the dock removed and put back, the second monitor *is* recognized and the display switches over. Therefore the three runs as above: started and plugged in, removed (just running as tablet) and put back on the top. It doesn't seem to see anything different.

I don't know if this helps, yet another bug: when in the dock, Windows 10 does a reboot. When in the dock, Kubuntu 18.04 doesn't. It shows the grub menu, it accepts keyboard input (through the Logitech receiver in the dock), it momentarily starts up X, and then the mouse cursor remains on the screen, and I can move this cursor around with the Logitech touchpad. It stays in this state however, until I switch it off. I have tried a good number of keys in this state to get it to do something, like showing the 'kubuntu' or the login screen, but it wouldn't.
So I guess that starting X, it *does* see something that makes it confused. It doesn't crash, it accepts mouse commands, but just sits there.
I do hope this is somewhat clear? It does mean, to start it in kubuntu-mode, I have to take it out of the dock in all cases, and once up, I can put it back.

Curious ... !

Uwe

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please clarify which commands above are from when the dock is connected, and which are from when the dock is not connected. If you get the same output in both scenarios then that means the kernel or hardware isn't detecting the dock.

Also, your comment about seeing the mouse but nothing else on start-up sounds like there's a secondary display connection but not working well enough to light up a screen. So that part may be bug 1760849.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please also tell us how many and what type display/HDMI ports are on the tablet and are on the dock.

Revision history for this message
udippel (udippel) wrote :

The three sets of three are: the first three on dock after start, the next three off the dock and the last three after reinsertion. It looks like no detection of any change with respect to display.

The machine is a Helix 2, Machine Type Model: 20CHS10P02 (details can be found on lenovo support website, if needed). It has a micro-HDMI-output on the tablet, but also offers video via a USB-2-video adapter (that I do not have, otherwise I could test it).
The dock is 4X10H04503, details under https://support.lenovo.com/de/en/accessories/ACC100200. It has one HDMI-plug and also some USBs that are said to allow the use of the adapter as described above.
The external monitor is a SONY Digital-TV BRAVIA, KDL-32CX525.

If it helps, I can produce a Youtube-clip showing the behaviour. Maybe that helps?

I also wonder, if it is possible one way or another to store the dmesg respectively the xorg log for those sessions that need abandoning due to only the mouse cursor being visible. Do you think those could help to identify what makes the boot-up process stop? Or do you think it goes through and simply doesn't send anything to the display?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the clarification.

I suspect the start-up problem has a chance of being a different bug, possibly related to gdm3. So if you agree then please open a bug for that by running: ubuntu-bug gdm3

Back on the main issue here, the data in comment #18 is showing that the tablet always has both HDMI ports present in software, but none are able to detect the TV which is presumably always connected to the HDMI port of the dock. The only thing that changes is whether the dock is connected to the tablet.

Basically this is a kernel problem in which the kernel never detects the TV connected to the HDMI port. So the next step is to report it to the Intel graphics kernel bug tracker, please :)
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel

affects: xorg-server (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually, maybe quick sanity check first: If you can then please try a different HDMI cable, and plug/replug it in firmly.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
udippel (udippel) wrote :

Thanks so far, Daniel! - I still encounter the strange boot problems on that dock, but sometimes it works; in W10 as well as in kubuntu.

However, the non-detection of the monitor is 100%. I tried another cable, even a proper Samsung monitor (contrary to the digital TV as before). Nothing at all. In W10 the lenovo diagnostics does correctly receive and handle the EDID-data.

Therefore I did follow your suggestions and filed bugs under gdm3 and freedesktop.

Thanks again and kind regards,

Uwe

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.