@fhortner
I tried to upgrade dock firmware version but it is failing on my setup. It is not able to detect dock while upgrade process though external monitors connected to display are working fine before and after suspend operation. However I believe that firmware upgrade does not plays any role here as you are seeing this issue with 2 different firmware versions.
Also I forced edid shared by you on my setup but could not reproduced issue.
Can you please help on below data points which might help us to find where issue is lying with.
Do you remember nvidia driver version where it worked fine in the past.
What is the repro frequency, do you see issue every time you suspend/resume notebook ?
Is there any specific hours to keep notebook in suspend mode?
Can you try unplug/plug display connection from dock (as WAR) when you are in repro state and see if it detects external monitor.
Can you try unplug/plug display connection from display itself ( as WAR) when you are in repro state and see if it detects external monitor.
@amrits
strange with the firmware update. But I think it could matter.
I remember I have ordered a second Thinkpad thunderbolt 3 Workstation dock which I did not update. There suspend to sleep seemed to sporadically work. But also here it used to fail after the second or third attempt.
Honestly, I was never really able to test ist, because from the beginning I had the dock, there was the issue with static noise over the Dock. Maybe you remember. So it was not really possible to use the dock.
But I could try to test with the same config as of that time, if suspend would have worked with the older drivers (with unsolved static noise at Quadro T2000 bug).
It happens every single time the notebook is suspend/resumed.
Only in case BIOS/UEFI setting “Only Descrete Graphics” is enabled it works.
Yes, when disconnecting the display from the dock when in repro state, the external monitor is detected again.
Yes, when disconnecting the display from the display when in repro state, the external monitor is also detected again.
So far point 3 and 4 and disconnecting/reconnecting the dock itself are the only “workarounds” until next suspend/resume cycle.
I have now also checked this the following way:
complete fresh install of the system:
System: Fedora 31 KDE spin. No Updates, disabled update-repo.
Kernel: 5.3.7-301
Installed earliest driver possible: Nvidia 435.21
Dock is authorised via boltctl
External Display is also NOT recognized after wake from sleep with driver 435.21
Thanks for all the isolations.
I am still trying to repro issue locally but I have a feeling this issue is with dock.
Is it possible for you to log a case with Lenovo as well , meanwhile I will try my best to replicate it ASAP .
Sorry when asking again, but is your Thinkpad P1 Gen3 set to "Hybrid Graphics"?
BIOS Option: Tab Devices → Display → “Hybrid Graphics”
I would exclude an issue with the dock, since Suspend/Wake works flawlessly under Linux using the Nouveau driver
It also works without any issue under Windows 10
It also works when having set BIOS Option Devices → Display → “Discrete Graphics” with the Nvidia driver
It only does not work with the Nvidia driver when the BIOS Option Devices → Display → “Hybrid Graphics”
So the combination of Nvidia driver + Optimus + TB Dock + Suspend/Wake from Suspend is the issue.
Nevertheless, If I get the chance I will try another dock.
May I ask, what do you think about the dock issue only with Nvidia driver in Optimus mode?
Meaning that the dock would be the issue vs a driver issue (like specific timing issue, Multi Stream Transport due to only affecting S3 with the DP hub in the dock, etc…)
Later I installed Fedora 35 matching your config, graphic settings saved as Hybrid but not observed any issue post multiple suspend/resume cycles.
ThinkPad P1 Gen 3 + Quadro T1000 with Max-Q + Driver 515.43.04 + Fedora release 35 (Thirty Five) + kernel 5.17.11-200.fc35.x86_64 + ThinkPad Thunderbolt 3 Workstation Dock Gen 2 + BenQ EL2870U
I also performed force edid which was shared by you earlier but could not repro issue after multiple suspend/resume cycles.
ThinkPad P1 Gen 3 + Quadro T1000 with Max-Q + Driver 515.43.04 + Fedora release 35 (Thirty Five) + kernel 5.17.11-200.fc35.x86_64 + ThinkPad Thunderbolt 3 Workstation Dock Gen 2 + Lenovo Group Limited LEN P27u-10
dump-dp-aux-log (7.3 KB)
Can you please follow below steps with the help of attached utility and share logs.
Enable the AUX logger in RM:
echo ‘options nvidia NVreg_RegistryDwords=“RmEnableDpAuxlogger=0x10000001”’ > /etc/modprobe.d/nvidia.conf
Reboot.
Start X and log in as usual.
In a terminal, run the attached dump-dp-aux-log program. Let it run in the background.
Reproduce the problem.
Run sudo nvidia-bug-report.sh
Send the log to us.
Don’t forget to remove /etc/modprobe.d/nvidia.conf when they’re done with it.
Steps 1, 2, and 8 might not be needed but doesn’t hurt.
Thanks for taking the time to update the dock. Loocks good.
Unfortunately I am currently running driver 510.68.02 since no newer version is available via rpmfusion so far.
I followed your instructions according to the list.
Please find the bug report attached. nvidia-bug-report.log.gz (194.3 KB)
Thanks for sharing the information.
Looks like I am able to duplicate issue now with driver 510.68.02 but as soon as I upgraded driver to 515.43.04, I do not duplicate issue.
Can you please uninstall existing driver and install the latest one using .run installer file from below location. https://us.download.nvidia.com/XFree86/Linux-x86_64/515.43.04/NVIDIA-Linux-x86_64-515.43.04.run
Finally, thank you for making the effort.
I had already doubts that my Laptop/graphics chip is somehow defect.
Could you already identify what exactly the problem is, and where it gets stuck?
I tried the Beta-Driver 515.43.04 from negativo17 and it seems that it works.
Nevertheless, I would say that it is very important to identify the problem and understand it in order to find a permanent and future-proof solution.
EDIT:
But this driver is too unstable for me. Firefox or Vivaldi often just hangs and does not load, etc.
What I said about the driver being unstable is actually not true. It is the same effect with Nouveau. I see the effect of not loading browser after resume from sleep while the dock is connected. Maybe it has something to do with the dock being connected (maybe the integrated Ethernet port)
In addition, I cannot update to 515.48.07, since Fedora 36 requires simpledrm which Nvidia driver does not support yet. The Rpmfusion driver has a patch for that, what I have read, to enable efifb. So far rpmfusion does not have the 515 in the pipeline yet.
With kernel 5.17.11 there is a patch that identifies a kernel parameter being set - nvidia-drm.modeset=1. if so it switches to old behaviour. I have just tried 515.48.07 with kernel 5.17.12 and the driver seems to work.
That sounds a great news, I was about to request you to try with out latest production release driver 515.48.07.
If I understood correctly, it solved the suspend/resume issue.
Please let me know if you think otherwise.
I experienced some glitches when going to suspend.
The System did go to sleep but woke immediately again. It only happend sporadicly, so not every time. I will check further and let you know.
By the way, do you also experience different QT scaling via the Dock compared to directly USB-C DP?
(Using F36 KDE spin). Symbols, Icons and fonts do not get scaled when having the monitor connected via the Dock. But they get scaled correctly when having the monitor directly connected via USB Type C DisplayPort.
I see this issue with almost if not all QT applications like KDE System Settings, Dolphin, Rstudio, KeePassXC, etc…
do you also experience different QT scaling via the Dock compared to directly USB-C DP?
(Using F36 KDE spin). Symbols, Icons and fonts do not get scaled when having the monitor connected via the Dock. But they get scaled correctly when having the monitor directly connected via USB Type C DisplayPort.
I see this issue with almost if not all QT applications like KDE System Settings, Dolphin, Rstudio, KeePassXC, etc…
I am not seeing such issue on my setup, tried few times lately.
Were you able to check extensively suspend/resume operation with driver 515.48.07 , if yes, please share test results.
Since the last post was modified by nvidia staff member, I repost the solution here.
From Nvidia driver version 515.48.07 the external monitor is waking after sleep, when connected via the thunderbolt docking station.
I am now using RPMfusion 515.57 driver version. No issues so far.
@amrits
Just wanted to let you know,
it looks like I could solve the issue with different scaling when using the dock. I reset the scaling, performed a reboot, reset the scaling, again reboot and now it seems to work.
In addition I think I could also solve the issue with the system not staying asleep when suspend.
Due to the issue with the external monitor not waking from sleep when using the dock, I tried to find an appropriate setting in the BIOS. Since it now works, I reset the BIOS settings to defaults and recommended Win10 settings. So far it seems to work.
