black screen after leaving bootsplash

Bug #1728422 reported by Karl-Philipp Richter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-384 (Ubuntu)
New
Undecided
Unassigned

Bug Description

After installing nvidia-384 the screen turns black after leaving the boot splash so that the start of the display manager can't be observed. Changing the tty isn't possible since the screen remains black after pressing Ctrl+Alt+F[X].

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-384 (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Oct 29 16:41:20 2017
InstallationDate: Installed on 2015-12-12 (687 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: nvidia-graphics-drivers-384
UpgradeStatus: Upgraded to artful on 2017-10-19 (9 days ago)
modified.conffile..etc.modprobe.d.nvidia-384_hybrid.conf: [deleted]

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :
Revision history for this message
Cedric Viou (cedric-dv) wrote :

With:
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

I use this nvidia driver:
nvidia-384 384.90-0ubuntu0.16.04.1 amd64

I can boot with:
linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 amd64

But it breaks (before I enter a passphrase to decrypt my drive) with this kernel (same as above bug description):
linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 amd64

What logs can I provide or what test can I run to help confirm this bug?

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

> What logs can I provide or what test can I run to help confirm this bug?

You can choose ~"This bug affects me", then it'll get confirmed automatically afaik.

I can't provide further information because the upgrade to 17.10 introduced severe issues in the apport tool running in recovery mode (see https://askubuntu.com/questions/975316/launchpad-doesnt-understand-the-form-data-submitted-in-this-request-when-usi for details).

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.