[HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

Bug #1768232 reported by d a i s y
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

My system stuck at ubuntu logo while booting. This issue occurred only after installing it, not when I choose 'Try without Installing'. This doesn't happen in 16.04.4.

xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
   1024x768 76.00*

Output of sudo lshw -c display

*-display UNCLAIMED
       description: VGA compatible controller
       product: 82945G/GZ Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 02
       width: 32 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:e2000000-e207ffff ioport:c000(size=8) memory:d0000000-dfffffff memory:e2080000-e20bffff memory:c0000-dffff

WORKAROUND: Using the following kernel boot parameter allows me to boot but the maximum resolution is limited to 1024x768:
nomodeset

WORKAROUND: Edit the file /etc/gdm3/custom.conf and change:
#WaylandEnable=false

to:
WaylandEnable=false

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 1 17:16:20 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:302a]
InstallationDate: Installed on 2018-05-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "AccelMethod" "uxa"
 EndSection
dmi.bios.date: 11/28/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: V1.03
dmi.board.name: 0AD8h
dmi.board.vendor: Board Manufacturer
dmi.chassis.asset.tag: INA8100LFY
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: HP dx2080 MT(KS826PA)
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
d a i s y (daisyd) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Tarik GRABA (tarikgraba) wrote :

Same thing here with a Dell Latitude E6540 (i5-4210M CPU)

`lspci -v` returns :

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
        Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at f5800000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features

and sudo lshw -c display ~
  *-display UNCLAIMED
       description: VGA compatible controller
       product: 4th Gen Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 06
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:f5800000-f5bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff

The xorg intel package is installed:

Package: xserver-xorg-video-intel
Version: 2:2.99.917+git20171229-1

Revision history for this message
Tarik GRABA (tarikgraba) wrote :

I had to use a 4.16 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline to have a working machine!

Revision history for this message
Tarik GRABA (tarikgraba) wrote :

it seems that the i915 module is missing from the Paquet linux-modules-4.15.0-20-generic package.

d a i s y (daisyd)
description: updated
description: updated
Revision history for this message
d a i s y (daisyd) wrote :

@Tarik GRABA My system stuck at ubuntu logo while booting. To resolve it, I've set nomodeset.
But now it occurs a resolution issue to 1024x768. In 'Try Ubuntu' it worked well. No such issue. I tried installing 4.16 kernel but not resolved.

I've two HDD in system. In one Ubuntu 16.04.04 installed and other 18.04. No issue with 16.04.04.

d a i s y (daisyd)
summary: - i915 driver issue in Ubuntu 18.04
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915
+ driver issue)
summary: - Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (i915
- driver issue)
+ Stuck at ubuntu logo while booting after installing Ubuntu 18.04
+ (Resolution 1024x768 after nomodeset, i915 driver issue)
Revision history for this message
Shane Semanek (ssemanek) wrote : Re: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 1024x768 after nomodeset, i915 driver issue)

I have a Dell Optiplex 330 workstation with Intel 82G33/G31 Express graphics. It ran Ubuntu 16.04, Ubuntu 17.10, and Ubuntu 18.04 beta2 without any issues. When Ubuntu 18.04 was released I did a clean install and it would boot to the Ubuntu logo screen and stop. I tried several kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline but the issue was not resolved.

To resolve the issue I had to disable Wayland in GDM3.

sudo vi /etc/gdm3/custom.conf

Change #WaylandEnable=false to WaylandEnable=false and reboot

Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable-xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux

penalvch (penalvch)
tags: added: bios-outdated-1.06 regression-release
description: updated
summary: - Stuck at ubuntu logo while booting after installing Ubuntu 18.04
- (Resolution 1024x768 after nomodeset, i915 driver issue)
+ [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
+ booting after installing
Revision history for this message
penalvch (penalvch) wrote :

d a i s y, thank you for reporting this and helping make Ubuntu better.

1) In order to root cause, could you please undo the WORKAROUND and provide the missing information from https://wiki.ubuntu.com/DebuggingKernelBoot ?

2) In order to allow additional upstream mainline kernel developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
d a i s y (daisyd) wrote :

Christopher M. Penalver

1. I've tried debugging kernel boot option other than nomodeset but it did not work, it shows started all the services and then pause there, no process after then.
2. I've installed kernel 4.16 and 4.17 but it also didn't work and I have to boot up with nomodeset option.

Revision history for this message
d a i s y (daisyd) wrote :

Shane Semanek

I've tried disabling Wayland in GDM3.

sudo vi /etc/gdm3/custom.conf

Change #WaylandEnable=false to WaylandEnable=false and reboot

It worked !

penalvch (penalvch)
description: updated
d a i s y (daisyd)
Changed in xorg (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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 1727356, 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.

affects: xorg (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: Fix Released → Confirmed
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.