Nvidia graphics -- D-U Interrupted at logind.conf dialog

[dibl]

This morning, on two desktop systems with Nvidia graphics, d-u aborted, and the video signal was killed, at the point where the dialog for updating or keeping /etc/systemd/logind.conf is presented. The screen goes black with no signal, and no further hdd activity is seen.

Fix -- wait 5 minutes to make sure all processing is completed, then either press reset or use Alt-PrtSc-RSEIUB if you have it set. On the next grub menu, press "e" to edit, add "3" to the end of your kernel boot line options, and then press Enter Ctrl-x to boot to tty1. Log in as root to tty1, and enter

Code Select Expand

dpkg --configure -a

and answer the configuration question, and d-u should complete with no further issues. Worked on two systems for me -- YMMV.

[michaa7]

Hi dibl, thanks for the heads-up.

Did you get a new nvidia driver with the d-u?

Here nvidia-tesla-470-driver is to be updated and that's why I was looking here for any warning upfront.

Still unsure whether or not I should give d-u a try hoping your fix would work. I think I wait for now.

[dibl]

Yes, a new set of nvidia-xx packages came down for those systems. I'm away from my house at this moment, but apt-policy tells me the new version must be 525.125.06-3.

EDIT: 

Code Select Expand

nvidia-driver:
  Installed: 525.125.06-3
  Candidate: 525.125.06-3
  Version table:
*** 525.125.06-3 500
        500 https://deb.debian.org/debian unstable/non-free amd64 Packages
        100 /var/lib/dpkg/status

[Pip]

I just did a du with nvidia-tesla-470 involved, no issues. But then, I don't have nvidia-driver.
inxi -G gives me

  Device-1: NVIDIA GK104 [GeForce GTX 770] driver: nvidia v: 470.199.02
  ...
  API: OpenGL v: 4.6.0 vendor: nvidia v: 470.199.02 renderer: NVIDIA GeForce GTX 770/PCIe/SSE2

apt list shows me

  nvidia-tesla-470-vdpau-driver/unstable,now 470.199.02-4

[dibl]

Here's the newer one, with dual monitors:

Code Select Expand

Graphics:
  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 525.125.06
  Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 1: 1920x1200~60Hz 2: 1920x1080~60Hz

[michaa7]

...a du with nvidia-tesla-470 involved,... don't have nvidia-driver.
...

What are you trying to say?

[Pip]

...a du with nvidia-tesla-470 involved,... don't have nvidia-driver.
...

What are you trying to say?

dibl had said he had nvidia-driver 525.125.06-3. I don't have nvidia-driver, so although I was experiencing no problems with the du, my situation is not the same as his. You said you had nvidia-tesla-470-driver which is more similar to what I have, nvidia-tesla-470-vdpau-driver, but again not exactly the same. Our experiences may vary.

[michaa7]

... ok, so "nvidia-driver" refers to the version (=525.x.x), and not to nvidia in general ... which wasn't clear to me when reading it.

Thanks for your clarification.

[ro_sid]

@dibl - original post.
Like you I had a black screen. But, after waiting, like you, to get the disc activity quiesced, for me, it was sufficient to press "ctrl-alt-F2" to get my screen back - intact. I could finish the "logind"-dialog. So it was not necessarily the nvidia-driver.

But mayhem struck afterwards. Installation of Nvidia components other than the driver did not complete. The reason was, that the access of /proc/driver/nvidia/version was no longer possible - it hangs! Now "grep"s for NVRM in the postinst installation action did/could not finish.

For the "unafraid": search for the grep process (ps ...) and kill it every time it comes up. The installation finishes (with errors). Then do the "dpkg --configure -a" and all is well.
Otherwise just reboot (forcefully) and fix things as described.

[dibl]

@dibl - original post.
Like you I had a black screen.

Did your monitor show the video signal shut off? (Maybe you have a laptop and screen is integrated ....).

That is what I had never seen before -- the video signal actually cut off in the middle of d-u. I did fiddle with the keyboard on the first system that showed the problem, but there was no video signal and no response from various key presses. However, Alt-RSEIUB did shut off the CPU so I know the keyboard was working correctly.

[terroreek]

I had the same issue with you dibl and my monitor was was saying there was no display port signal.  I had not output from my desktop,

[ro_sid]

@dibl - original post.
Like you I had a black screen.

Did your monitor show the video signal shut off? (Maybe you have a laptop and screen is integrated ....).

Your assumption is correct, it is a laptop. Nevertheless the screen went black in the middle of the update, did not 'come back' by itself and no (trivial) keypress did help. Only when I "switched" screens with the "ctrl-alt-F..."-sequence.
So a laptop may make a difference, but in what way? The video output still has to be driven. And it did not switch the graphics controller [it is an "optimus" ThinkPad]. But of course I can not (easily) test the video signal.

Me, I have also never seen this kind of behaviour before. Normally, once video is gone it is gone,

[michaa7]

Hi, my d-u now went through without any problem (except for an unrelated tex-common failure for which a bugreport exists). But in contrast to dibl's situation my nvidia ungrade relates to nvidia-470!!!