Ubuntu 19.04 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile

[Matthew General]

I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related.

This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed).

Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either.

lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 3e9b
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Device a353 (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1)
3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
Package: gnome-shell
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Tags: disco
Uname: Linux 5.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1821426/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Daniel van Vugt (vanvugt)]

Please run:

  apport-collect 1821426

to send us more information about the machine.

Please also try these potential workarounds and let us know which one(s) work:

(a) Edit /etc/gdm3/custom.conf and uncomment the line:

    #WaylandEnable=false

    and reboot.

(b) Disable integrated graphics/GPU in your BIOS

(c) Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run:

    sudo update-initramfs

    and reboot.

[Matthew General (mattgen88)]

apport information

[Matthew General (mattgen88)]

apport information

[Matthew General (mattgen88)]

apport information

[Matthew General (mattgen88)]

I can get to the desktop by adding nomodeset

Tried it on the latest 19.04 from 3/26
Without nomodeset it continues its flashing black screen

However it reports as "unknown display" and I can not get it to detect an external display.

Attaching the apport-collect but it is from a live disk, I'm not sure if that'll be helpful. Unfortunately I cannot install ubuntu 19.04 at this time because I need use of the computer which works fine under 18.10.

It looks like I cannot disable the GPU in BIOS on this machine.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1822026, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.