[ThinkPad P1 Gen 4i][Nvidia T1200] External monitor does not connect on USB-C

[Stein Arne Storslett]

The external Samsung 34" monitor connects fine with HDMI, but not on USB-C.
It worked for a short amount of time at one point early after installing Ubuntu 22.04, but not since.

No difference with disconnect / reconnect, reboot, etc.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 12 10:17:49 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22e4]
 NVIDIA Corporation TU117GLM [T1200 Laptop GPU] [10de:1fbc] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:22e4]
InstallationDate: Installed on 2022-05-09 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: LENOVO 20Y3000EMX
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2022
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N40ET33W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Y3000EMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN40ET33W(1.15):bd02/24/2022:br1.15:efr1.15:svnLENOVO:pn20Y3000EMX:pvrThinkPadP1Gen4i:rvnLENOVO:rn20Y3000EMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y3_BU_Think_FM_ThinkPadP1Gen4i:
dmi.product.family: ThinkPad P1 Gen 4i
dmi.product.name: 20Y3000EMX
dmi.product.sku: LENOVO_MT_20Y3_BU_Think_FM_ThinkPad P1 Gen 4i
dmi.product.version: ThinkPad P1 Gen 4i
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[Daniel van Vugt (vanvugt)]

If you are using a USB-C dock then please see bug 1970495.

Otherwise if you think the USB-C port might be wired directly to the Nvidia GPU then please see bug 1960865.

When the bug occurs next please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

[Stein Arne Storslett (sastorsl)]

I've got it working one more time.

* Disconnected the HDMI.
* Rebooted - with USB-C to the monitor connected.
* The external monitor did not register.

In addition to the monitor a Lenovo network adapter (8P8C for CAT5/CAT6/..) is connected.

I tailed /var/log/syslog and /var/log/kern.log
I kept disconnecting / reconnecting the monitor, and _nothing_ registered in the logs.

Then I disconnected the network adapter USB-C.
Followed by disconnecting the monitor USB-C again.

Then reconnected the monitor USB-C and nothing.
I then kept the network adapter out, and turned off the power for the monitor - while connected to USB-C.

Then when I turned on the monitor power again the logs _finally_ registered the monitor, and it came to life.

I'll repeat that when connecting the same monitor with HDMI it consistently came to life.
But 1) USB-C connection should work the same, and 2) I'm usually connecting a second external monitor on HDMI.

I'll try to lock the screen / unlock, reboot, let it suspend, etc, and see what happens next.

[Stein Arne Storslett (sastorsl)]

Before reboot I had:

* Laptop internal monitor on
* Samsung 34" external monitor on, with USB-C
* Aces 24" external monitor on, with HDML

Rebooted without changing anything.

* The Samsung 34" / USB-C connected external monitor did _not_ come to life.
* The Acer 24" / HDMI second external monitor came to life

Tailed /var/log/kern.log again.
Disconnected / reconnected the USB-C monitor. Nothing in the logs.

Then:

* Disconnected the Lenovo network adapter on USB-C
* Pulled the power cord on the USB-C monitor
* Plugged in the power cord on the USB-C monitor

...and the monitor came to life.

Plugged in the network adapter on USB-C again, and everything worked still.

It would _seem_ to me that either the network adapter, or the combination is the issue.

Attaching logs from after the current boot as the "monitor issue" was present and solved within that time.

[Daniel van Vugt (vanvugt)]

Thanks. It kind of looks like the Nvidia driver is directly aware of the USB-C/Thunderbolt port. Maybe it has a hardware muxer/switch built-in? So maybe it's not surprising then that the order of connection matters.

For now that suggests the bug is somewhere between the Nvidia driver and the kernel.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.