Cannot boot ISO unless using nomodeset

[fossfreedom]

Booting the 32bit UB iso via legacy boot - have to use nomodeset otherwise the ISO appears to hang after the initial options screen turns to black screen and eventually no blinking cursor.

Looking at GNOME Settings - About it says llvmpipe is in operation - I was expecting intel graphics

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-video-intel-hwe-18.04 2:2.99.917+git20171229-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic i686
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: i386
CasperVersion: 1.394
CurrentDesktop: Budgie:GNOME
Date: Thu Aug 1 21:14:36 2019
LiveMediaBuild: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Beta i386 (20190801)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-intel-hwe-18.04
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

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

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1838698

[fossfreedom (fossfreedom)]

booting from the 64bit ISO works just fine i.e. doesnt need nomodeset

[fossfreedom (fossfreedom)]

After installing the 32bit ISO I could not boot into the OS.

With nomodeset I just saw the enclosed picture.

Without nomodeset I saw briefly the same picture and then just a black screen no blinking cursor.

The best logs I could find is to launch back into the livesession (with nomodeset) and navigate to the /var/log on the harddrive

I'll attach all the logs at the latest time in that folder

[Timo Aaltonen (tjaalton)]

if nomodeset doesn't work, the bug is not in the drm subsystem at least

[Timo Aaltonen (tjaalton)]

boot without nomodeset, and pull logs from that boot

[fossfreedom (fossfreedom)]

Hi

The logs attached were from a boot without nomodeset. I couldn't get to a desktop ... it got stuck as shown in the picture ... so I had to force power off, boot into a live session and navigate to /var/log on the hard drive

[Timo Aaltonen (tjaalton)]

wait, you said the picture was with nomodeset?

[Timo Aaltonen (tjaalton)]

Oh, if you install with nomodeset, it will be added to /etc/default/grub. The log is with nomodeset as witnessed by:

Aug 5 23:56:47 dad-HP-Notebook kernel: [ 0.040634] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=693f56ac-1fad-4163-be3d-6b9d7bf05d2f ro nomodeset quiet splash vt.handoff=1
Aug 5 23:56:47 dad-HP-Notebook kernel: [ 0.040785] You have booted with nomodeset. This means your GPU drivers are DISABLED

[fossfreedom (fossfreedom)]

ok - the best I could do is the following:

boot the live iso with nomodeset. chroot onto the hard-drive and install openssh-server and in /etc/modprobe.d/blacklist.conf added install i915 /bin/false and then ran update-initramfs -u

Then booted the machine without the USB stick ensuring nomodeset was removed by grub.

This booted to lightdm

ssh'd to the machine

sudo systemctl stop lightdm

edited /etc/modprobe.d/blacklist.conf and commented out the install line I added. saved and reran update-initramfs -u

This time check dmesg was ok.

Then ran sudo modprobe -v i915.

Checked dmesg again - saw the trace attached

[Timo Aaltonen (tjaalton)]

16:05 < fossfreedom> tjaalton: tried the 5.3rc3 32bit kernel - same crash when modprobe i915

maybe try 4.18.0-13-generic from bionic, does it work? if yes, install -25 and check if that one works.. kinda hoping the regression was due to the intel cpu security fixes

[Timo Aaltonen (tjaalton)]

test this build:

https://aaltoset.kapsi.fi/32bit-debug

[Po-Hsu Lin (cypressyew)]

Mark as Incomplete for request in comment #19

[Launchpad Janitor (janitor)]

[Expired for linux-hwe (Ubuntu) because there has been no activity for 60 days.]