Dear Maintainer,

I'm having a problem that renders the nvidia driver versions 455 and 460
that have been available on Debian unusable to me. When installed, the
system usually boots up fine and appears to work until something happens
that affects the link to the monitor - this could be removing the HDMI
cable, DPMS being activated for screen blanking, or switching to a
different input on the monitor (as I have two computers connected to
it).

At that point, when the link is restored (for example by reconnecting
the HDMI cable, moving the mouse or switching back to the HDMI input for
this computer), no sync is seen again. Examining the X logs, it appears
that the monitor is seen multiple times at this point, but never gains
sync. Switching to a VC and disconnecting and reconnecting the cable has
very occasionally restored the display, but often it doesn't and a
reboot is required.

Switching back to version 450 as was in testing until a week or two ago,
none of these problems exist. Despite this, just in case, I've tried
changing the HDMI cable, and 460 still exhibits the same problems. I've
had to switch back to 450 to enable work to continue, as I have to
regularly switch inputs on this computer.

I'm unsure what information would be useful to progress, but I'm very
happy to provide any information requested or test any changes. Just let
me know and I'll get back to you as soon as possible.

I've attached an example of the Xorg.0.log after switching inputs away
and back to the computer affected as a starting point. The switch away
was the event at ~15.6s, the switch back was ~77.2s, switch to a VC was
93.5s (this did not result in any usable display) and reboot was ~159s.

I don't currently have an Xorg log from v450, but once the bug report is
accepted I'll switch back and attach it as a comparison.

Thanks very much for your time,
-Dave.

Dear Maintainer,

As a comparison, please find below logs from driver 450 which is working
fine. Here, the system was booted and displayed fine. IT was left for
some time, DPMS kicked in from the display manager timing out, and was
re-woken at around 2121s.

Display inputs on the monitor were switched at ~2168s, and reverted
soon after, with no problems at all.

All the best,
-Dave.

Hi David,

could you try nvidia-tesla-450-driver 450.102.04-1 from sid?
It is installable along the regular driver and you can switch between
the different drivers with update-glx (and then reboot to load the other
kernel module and libraries).

This is just to check whether the 450 series got "broken" too with the
latest version (which includes a CVE fix).

Thanks

Andreas

PS: If it is still working fine, we might keep the tesla-450 driver in
bullseye along tesla-460.

Hi Andreas,

Thanks very much for the quick reply. I've given this a try as
requested: nvidia-tesla-450-driver and dependencies installed, then ran
"update-glx --config nvidia" and selected /usr/lib/nvidia/tesla-450 and
rebooted after it had recreated the initrd.

On reboot, I checked the X server log to ensure it had selected the
correct version, and "450.102.04" was reported, so that looked good. At
that point, I tried switching away to a new display then switching back,
removing and re-inserting cables, and forcing a DPMS off state using
xset, and each time the display came back without any problems, so it
looks like the CVE fix isn't the cause of the problems.

Let me know if I can try anything else, and thanks again for your efforts.

All the best,
-Dave.

I've just uploaded nvidia-graphics-drivers 460.39-1 to sid, please try
that as well.

Andreas

Hi Andreas,

I was unable to find the packages at present, but I understand that they
do take a little while to filter through the system. However, the source
was available, and I had no problem using debuild to create the
(unsigned) packages locally. Installing the new version of all currently
installed packages then running update-glx to select that version and
rebooting, I'm afraid the problem comes back.

I've replied using reportbug so you can see the collected information
in case that's of use - the test case was to boot up, switch monitor
inputs, and switch back. These are the the old Xorg log fix - ~62s was
the switch away, ~73s was the attempt to switch back. No sync at all
when switching back. Tried to switch to a text console, still no
display, so rebooted.

For now, I'm going to switch back to the tesla-450 driver, but I'm very
happy to run any more tests if you'd like me to. Also, when the packages
filter through the system far enough for apt to see them, I'll re-test
with the official ones and confirm this situation.

All the best,
-Dave.

Control: tag -1 upstream

There should be no difference.

Please check whether your issue is already reported in the nvidia forums
and if it isn't please follow nvidia's instructions to do this.

https://forums.developer.nvidia.com/t/if-you-have-a-problem-please-read-this-first/27131

Thanks

Andreas

Control: forwarded -1
https://forums.developer.nvidia.com/t/fails-to-display-on-any-monitor-change-on-driver-455-and-460-reverting-to-450-things-work-again/167232/2

I couldn't find anything there, so have created and account and a thread
as suggested:
https://forums.developer.nvidia.com/t/fails-to-display-on-any-monitor-change-on-driver-455-and-460-reverting-to-450-things-work-again/167232/2

Thanks again for your help,
-Dave.

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Matthias Babisch <matthias@babisch.net>
To: Debian Bug Tracking System <981114@bugs.debian.org>
Subject: Re: nvidia-driver: Fails to display on any monitor change
Message-ID:
<161785878981.49100.8822991974104545369.reportbug@animal.smooth.local>
X-Mailer: reportbug 7.10.3
Date: Thu, 08 Apr 2021 07:13:09 +0200

Package: nvidia-driver
Version: 460.67-1
Followup-For: Bug #981114

Dear Maintainer,

I am just reporting this in case it may be helpful.

I have a similar problem. I am using a 2 Monitor setup on Debian
Bullseye. One
of said monitors is a 4k TV. That TV shuts down completely for energy saving
after a while. (I need to turn on the TV via remote to get anywhere.)

On Debian Buster (older Version of Driver, default, can't tell which
right now)
the display then came back after a few seconds. On Bullseye (460.67-1,
another
older version too) the display does not come back. The TV reports no signal.

A workaround I found is, changing some settings of the affected display
in the
display settings (using kde in my case).
I found it helps to either:

* Deactivate the display, save/activate the settings and activate it again.
* Change the framerate of the display and save/activate the settings.

For me fixing this bug is not very important, though it is annoying.

Maybe this information helps you.

Sincerely

Matthias Babisch