Complete screen corruption on resume. Nvidia GT216GLM

Asked by Matthew J. L. Kilger on 2021-01-13

Using Nvidia-304 driver, desktop is unable to start.

When using Nouveau driver, upon resume from suspend, the entire screen is corrupted and interaction is impossible.

To work-around:
CTRL+ALT+F4 to log into terminal shell.
sudo init 3
sudo init 5 to restart the desktop.

This, of course, has the unfortunate side-effect of killing any applications on the desktop.

Any suggestion (beyond upgrading the video card, as this is a Lenovo W510 laptop, so this component is not replaceable).


Question information

English Edit question
Needs information
Ubuntu Edit question
No assignee Edit question
Last query:
Last reply:
Manfred Hampl (m-hampl) said : #1

Which Ubuntu release?
Details of your graphics card?
Please provide the output of the commands

uname -a
lsb_release -crid
sudo lshw -C display

Maybe a different version of the NVidia driver works better (the 340.* version might fit to your card)

DOH! Forgot the release info!

Here's the output that you requested:

Linux Craptop 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

       description: VGA compatible controller
       product: GT216GLM [Quadro FX 880M]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a2
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:49 memory:cc000000-ccffffff memory:d0000000-dfffffff memory:ce000000-cfffffff ioport:2000(size=128) memory:c0000-dffff

Manfred Hampl (m-hampl) said : #3

What is the output of the commands

dpkg -l | grep -E 'nvidia-[34]'
apt-cache policy nvidia-304 nvidia-340

I removed the 304 driver, so the first command returns nothing.

Second returns: nvidia-304:
  Installed: (none)
  Candidate: (none)
  Version table:
  Installed: (none)
  Candidate: 340.108-0ubuntu2
  Version table:
     340.108-0ubuntu2 500
        500 focal/restricted amd64 Packages

When attempting to install the 340 driver, it fails:

INFO:Enable nvidia-340
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
Adding system user `nvidia-persistenced' (UID 127) ...
Adding new group `nvidia-persistenced' (GID 133) ...
Adding new user `nvidia-persistenced' (UID 127) with group `nvidia-persistenced' ...
Not creating home directory `/'.
Loading new nvidia-340-340.108 DKMS files...
Building for 5.8.0-36-generic 5.8.0-38-generic
Building for architecture x86_64
Building initial module for 5.8.0-36-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-340.0.crash'
Error! Bad return status for module build on kernel: 5.8.0-36-generic (x86_64)
Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.
dpkg: error processing package nvidia-340 (--configure):
 installed nvidia-340 package post-installation script subprocess returned error exit status 10
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for initramfs-tools (0.136ubuntu6.3) ...
update-initramfs: Generating /boot/initrd.img-5.8.0-38-generic
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

Manfred Hampl (m-hampl) said : #6

Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for more information.

Which error messages are in that file?

Can you help with this problem?

Provide an answer of your own, or ask Matthew J. L. Kilger for more information if necessary.

To post a message you must log in.