[nvidia] Black screen on loading latest system update

Bug #1879333 reported by mtbdrew
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-440 (Ubuntu)
New
Undecided
Unassigned
xorg-server (Ubuntu)
New
Undecided
Unassigned

Bug Description

This bug has been around since 16.04 and still occurs with 18.04 when using nvidia drivers. When update required for the OS the black screen situation happens after the required reboot. Only way to regain desktop is to login via ssh terminal and run the commands listed here:

https://askubuntu.com/questions/1129516/black-screen-at-boot-after-nvidia-driver-installation-on-ubuntu-18-04-2-lts

sudo apt-get update

sudo apt-get upgrade

sudo apt-get purge nvidia*

sudo apt autoremove

sudo apt-get install dkms build-essential linux-headers-$(uname -r)

echo "# Disable the default Nouveau kernel driver" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "# -----------------------------------------" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf

cat /etc/modprobe.d/blacklist-nouveau.conf

echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d/nouveau-kms.conf

cat /etc/modprobe.d/nouveau-kms.conf

sudo update-initramfs -u

sudo service lightdm stop

sudo apt-get install nvidia-driver-440

lsmod | grep nvidia

sudo lshw -c video | grep 'configuration'

sudo reboot

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog:

CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Mon May 18 08:44:05 2020
DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate dkms.conf file.
 File: does not exist.

 bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1]
 NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a]
InstallationDate: Installed on 2019-09-26 (234 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago)
dmi.bios.date: 02/27/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150M
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Apr 29 07:15:33 2020
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.6-1ubuntu4.4

Revision history for this message
mtbdrew (mtbdrew) wrote :
tags: added: black-screen
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Do you have automatic login enabled or do you use a password? If the former then this may be bug 1845801.

tags: added: hybrid nvidia
summary: - Black screen on loading latest system update
+ [nvidia] Black screen on loading latest system update
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
Revision history for this message
mtbdrew (mtbdrew) wrote :

I do have auto login enabled on this machine but after reading the bug report you mentioned I don't think these are the same at all. In my situation the display is completely black with no ability to to do any of this:

"I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct.

If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again."

I have to ssh in from a completely different machine and run the commands I mentioned earlier.

BR
Andrew

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

That was over a release ago. The symptoms may change but generally speaking I think the issue(s) should be discussed in a single bug until proven otherwise.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh you're using an older release than bug 1845801. Still, same statement applies.

Revision history for this message
mtbdrew (mtbdrew) wrote :

Don't see how this is the same issue I am not doing a upgrade just and update. I have been up and running on 18.04 for several months now and only see the issue if there is a an update that requires the system to be reset or sometimes when the system boots with the TV off. I do not get the GDM prompt nor can I drop into another TTY session but have to log in from another machine using ssh in order to run the commands listed here:

https://askubuntu.com/questions/1129516/black-screen-at-boot-after-nvidia-driver-installation-on-ubuntu-18-04-2-lts

Again I am not in the login loop situation but a complete black screen (no video output what so ever) situation.

Revision history for this message
mtbdrew (mtbdrew) wrote :

Issue happened again after today's system update.

The problem is causing the Nvidia device to not even been detected:

frontend@frontend:~$ lsmod | grep nvidia
frontend@frontend:~$ sudo lshw -c video | grep 'configuration'
       configuration: driver=i915 latency=0
       configuration: latency=0

After running steps listed here: https://askubuntu.com/questions/1129516/black-screen-at-boot-after-nvidia-driver-installation-on-ubuntu-18-04-2-lts

The card is correctly detected again:

frontend@frontend:~$ lsmod | grep nvidia
nvidia_uvm 937984 0
nvidia_drm 45056 3
nvidia_modeset 1110016 6 nvidia_drm
nvidia 20422656 249 nvidia_uvm,nvidia_modeset
drm_kms_helper 172032 2 nvidia_drm,i915
drm 401408 8 drm_kms_helper,nvidia_drm,i915
ipmi_msghandler 53248 2 ipmi_devintf,nvidia
frontend@frontend:~$ sudo lshw -c video | grep 'configuration'
[sudo] password for frontend:
       configuration: driver=i915 latency=0
       configuration: driver=nvidia latency=0

Revision history for this message
mtbdrew (mtbdrew) wrote :

Still did it this morning after running updates and the reset.

Revision history for this message
mtbdrew (mtbdrew) wrote :

Occurred again today after the kernel update was installed and system reset. When is this issue going to get fixed!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.