[Bug 1209441] New: Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station
https://bugzilla.suse.com/show_bug.cgi?id=1209441 Bug ID: 1209441 Summary: Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: mvetter@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Thinkpad P16 Gen 1 doesnt detect monitor when plugged into docking station. Notebook is running and attached to docking station. Only external monitor is used, internal one disabled in GNOME settings. Works fine. Occasionally screen tearing (quite unregular, every few days suddenly). I plug it out of the docking station and in again. Only the notebook montir is used and external one not properly detected. It is seen as "unknown monitor/device" but not with the actual name as usual. hwinfo file can be found in original bug report for system freeze upon connecting to docking station: https://bugzilla.suse.com/show_bug.cgi?id=1207900 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209441
https://bugzilla.suse.com/show_bug.cgi?id=1209441#c1
--- Comment #1 from Michael Vetter
https://bugzilla.suse.com/show_bug.cgi?id=1209441
https://bugzilla.suse.com/show_bug.cgi?id=1209441#c2
--- Comment #2 from Takashi Iwai
https://bugzilla.suse.com/show_bug.cgi?id=1209441
Petr Vorel
https://bugzilla.suse.com/show_bug.cgi?id=1209441
https://bugzilla.suse.com/show_bug.cgi?id=1209441#c3
--- Comment #3 from Michael Vetter
The best would be to report the issue to the upstream, gitlab.freedesktop.org Issues.
I would like to. But I'm unsure which repo exactly. And also it seems to me that I have several problems which I would like to untangle first to tackle them independant of each other so that we can have good support for this hardware. For example in dmesg (also posted in original bugreport) I see the following, that looks not normal to me, as well:
[ 1.362495] pcieport 0000:00:1c.0: pciehp: Cannot get irq -1 for the hotplug controller [ 1.362501] pcieport 0000:00:1c.0: pciehp: Notification initialization failed (-1)
[ 1.442438] blacklist: Problem blacklisting hash (-13)
[ 3.354886] nouveau 0000:01:00.0: DRM: VRAM: 4096 MiB [ 3.354887] nouveau 0000:01:00.0: DRM: GART: 536870912 MiB [ 3.354889] nouveau 0000:01:00.0: DRM: BIT table 'A' not found [ 3.354890] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
[ 4.844380] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)
[ 7.043589] ucsi_acpi USBC000:00: con3: failed to register alt modes [ 7.095557] ucsi_acpi USBC000:00: PPM init failed (-110)
[ 12.959801] spi-nor spi0.0: unrecognized JEDEC id bytes: f6 f0 30 09 03 00
[ 15.420842] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 30.470905] hid-generic 0003:17EF:30B4.0009: hiddev96,hidraw0: USB HID v1.11 Device [Lenovo ThinkPad Thunderbolt 4 Dock MCU Controller2] on usb-0000:00:14.0-6.1/input0 [ 152.804805] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:4a:04.0 [ 152.804828] pcieport 0000:4a:04.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 152.804829] pcieport 0000:4a:04.0: device [8086:0b26] error status/mask=00000040/00002000 [ 152.804831] pcieport 0000:4a:04.0: [ 6] BadTLP [ 180.804908] pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:4a:04.0 [ 180.805035] pcieport 0000:4a:04.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID) [ 180.805040] pcieport 0000:4a:04.0: device [8086:0b26] error status/mask=00000040/00002000 [ 180.805046] pcieport 0000:4a:04.0: [ 6] BadTLP [ 180.805051] pcieport 0000:4a:04.0: AER: Error of this Agent is reported first
[ 4559.852955] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for HDMI-A-1
All I can say that it seems that "something is wrong", but I don't have enough knowledge to understand what. Nor to understand which things are related. I would like to find somebody to understands these messages, can tell me what test and what information to provice. With the goal to have this hw supported well since AFAIK this is one of our new standard company laptops now. So again, I'm not even sure which components are relevant here (kernel, missing drivers, missing support, noveau..). It seems to be several problems. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209441
https://bugzilla.suse.com/show_bug.cgi?id=1209441#c4
--- Comment #4 from Michael Vetter
https://bugzilla.suse.com/show_bug.cgi?id=1209441
https://bugzilla.suse.com/show_bug.cgi?id=1209441#c5
--- Comment #5 from Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c6
--- Comment #6 from Stefan Dirsch
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c8
--- Comment #8 from Petr Vorel
Meanwhile we have a Lenovo P16 laptop available for testing in our team. I suggest to use nvidia proprietary or opengpu driver instead of nouveau driver. All external outputs are connected to nVidia GPU.
https://drewdevault.com/2017/10/26/Fuck-you-nvidia.html -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c9
--- Comment #9 from Michael Vetter
Meanwhile we have a Lenovo P16 laptop available for testing in our team.
That's great to hear :)
I suggest to use nvidia proprietary or opengpu driver instead of nouveau driver. All external outputs are connected to nVidia GPU.
I did that now as well. Thanks to your instruction on your blog! The problem I have with this setup is that once I suspend it crashes. Once I close the notebook lid (if it's not connected) it crashes. And interesting enough: When I boot I get until GDM, and the output is on the external monitor (as I configured it). But when I log in and it loads GNOME 3, then suddenly it uses the internal display only. Then I plug it out of the docking station, and in again. And it correctly uses the external display (as configured). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c10
--- Comment #10 from Petr Vorel
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c11
--- Comment #11 from Stefan Dirsch
(In reply to Stefan Dirsch from comment #6)
Meanwhile we have a Lenovo P16 laptop available for testing in our team.
That's great to hear :)
I suggest to use nvidia proprietary or opengpu driver instead of nouveau driver. All external outputs are connected to nVidia GPU.
I did that now as well. Thanks to your instruction on your blog!
The problem I have with this setup is that once I suspend it crashes. Once I close the notebook lid (if it's not connected) it crashes.
Indeed we've seen issues with S3 with at least sle15-sp5 kernels. So TW could be affected as well! For some reason S3 worked with sle15-sp4 kernels. We'll have a closer look this week.
And interesting enough: When I boot I get until GDM, and the output is on the external monitor (as I configured it). But when I log in and it loads GNOME 3, then suddenly it uses the internal display only. Then I plug it out of the docking station, and in again. And it correctly uses the external display (as configured).
Oh well. :-( -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c12
--- Comment #12 from Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c13
--- Comment #13 from Stefan Dirsch
(In reply to Stefan Dirsch from comment #6)
Meanwhile we have a Lenovo P16 laptop available for testing in our team. I suggest to use nvidia proprietary or opengpu driver instead of nouveau driver. All external outputs are connected to nVidia GPU.
nVidia supports GBM since some time. This text is from 2017. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c14
Stefan Dirsch
Do we get a crash log, if it's a kernel crash?
Also, was it tested with the SLE15-SP5-GM kernel (that is from the official SUSE/Leap repo), or is it a SLE15-SP5 KOTD (in OBS Kernel:SLE15-SP5 repo)?
Last but not least, please try with the kernel in OBS home:tiwia:bsc1206843-3 repo, too: http://download.opensuse.org/repositories/home:/tiwai:/bsc1206843-3/pool/
NEEDINFO reporter -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c15
--- Comment #15 from Petr Vorel
nVidia supports GBM since some time. This text is from 2017.
Thanks for an update. I didn't check, because sway still insists on nouveau probably due previous problems (and expecting not following future changes in mainline kernel fast enough). Generally, Nvidia proprietary is pragmatic option for KDE/GNOME (for major desktops), due good new hardware support, but as long as the HW is supported properly with nouveau (and mesa) it's IMHO better option than out-of-tree proprietary nvidia driver. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1209441
http://bugzilla.suse.com/show_bug.cgi?id=1209441#c16
--- Comment #16 from Stefan Dirsch
participants (1)
-
bugzilla_noreply@suse.com