My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435

Bug #1854114 reported by Amin Sadeghi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-435 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Here's what happened: I have Ubuntu 19.10 installed + NVIDIA driver 340 + 4K screen. Everything works file. I upgraded my NVIDIA driver to 435 and then everything is still fine until the login screen. When I enter my password, the screen goes black. So, I connected my old HD monitor, rebooted, and it worked! Funny thing is that, when I'm logged in the OS, if I reconnect my 4K monitor, it works! But if I restart my system, the problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:03:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019
 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 26 19:21:07 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
 openrazer-driver, 2.6.0, 5.3.0-22-generic, x86_64: installed
 openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097]
InstallationDate: Installed on 2019-10-18 (39 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Precision Tower 5810
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=ab778d32-5ce1-4c38-a14e-2024d96eb5d3 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A32
dmi.board.name: 0K240Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA32:bd09/24/2019:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision Tower 5810
dmi.product.sku: 0617
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Amin Sadeghi (aminsadeghi) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

If updating the nvidia driver creates the issue then it seems a bug in those?

affects: xorg (Ubuntu) → nvidia-graphics-drivers-435 (Ubuntu)
Revision history for this message
Amin Sadeghi (aminsadeghi) wrote :

RE: #2
I think so, just to add: pretty much every available driver I tried that was more recent than the v340, the same thing happened. So there must be something that happens for nvidia drivers 340+.

tags: added: nvidia
Revision history for this message
Amin Sadeghi (aminsadeghi) wrote :

In case it helps debugging, I found a workaround: I enabled legacy mode in motherboard bios, and it got 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.