[nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

Bug #1925344 reported by Łukasz Zemczak
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Won't Fix
nvidia-graphics-drivers-460 (Ubuntu)
Won't Fix
nvidia-prime (Ubuntu)
Won't Fix
xorg-server (Ubuntu)
Won't Fix

Bug Description

After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top-left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1.

Running `prime-select query` shows `nvidia`.

Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`.

Not sure which package I should fill this under.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xserver-xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021
 GCC version:
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 21 15:20:15 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Dell UHD Graphics [1028:09e1]
 NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1]
InstallationDate: Installed on 2021-04-21 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. G3 3500
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2020
dmi.bios.release: 1.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 06ND9G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: GSeries
dmi.product.name: G3 3500
dmi.product.sku: 09E1
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
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.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

Revision history for this message
Łukasz Zemczak (sil2100) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
affects: xorg (Ubuntu) → xorg-server (Ubuntu)
tags: added: nvidia
tags: added: dualgpu hybrid
summary: - Session not started after reboot (black screen) - requires switching tty
- back and forth
+ [nvidia] Session not started after reboot (black screen) - requires
+ switching tty back and forth
Revision history for this message
Tim Crawford (crawfxrd) wrote :

I believe I am experiencing this on 20.04

> (EE) open /dev/dri/card0: No such file or directory

The problem seems to be that gdm-wait-for-drm doesn't work for (muxless) dual GPU laptops when using the dGPU.

GDM will start when only card1 is available, *both* card0 and card1 need to be available before starting X.

(As a quick hack, I am using `ExecStartPre=/bin/sleep 1` to give drm enough time before starting GDM.)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdm3 (Ubuntu):
status: New → Confirmed
Changed in nvidia-graphics-drivers-460 (Ubuntu):
status: New → Confirmed
Changed in nvidia-prime (Ubuntu):
status: New → Confirmed
Changed in xorg-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.

See this document for currently supported Ubuntu releases:

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in xorg-server (Ubuntu):
status: Confirmed → Won't Fix
Changed in nvidia-prime (Ubuntu):
status: Confirmed → Won't Fix
Changed in nvidia-graphics-drivers-460 (Ubuntu):
status: Confirmed → Won't Fix
Changed in gdm3 (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers