Login screen freeze on Intel Sandy Bridge i5-2500 GPU

[Peter Bosch]

Since using Ubuntu 18.04.1 LTS on boot at the login screen the screen is frozen. I tried both gdm3 and lightdm login managers, with either I don't get into the system.

I am using Intel 2nd generation (Sandy bridge) CPU with on-board GPU: HD Graphics 2000. I have an external 24" ASUS display connected with VGA (tried HDMI as well but same problem).

UPDATE: I now use "nomodeset" since that is the only way to get into the system. However, graphics are low and there's only 1 screen resolution available (1280x1024) which does not suit my screen at all.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 16 18:16:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2018-09-15 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Gigabyte Technology Co., Ltd. H67M-UD2H
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro nomodeset quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:

dmi.bios.date: 11/12/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: H67M-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/12/2010:svnGigabyteTechnologyCo.,Ltd.:pnH67M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H67M-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.94+git1809150630.283282~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1809160730.149768~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.1.0+git1809141934.80514b~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1809061934.25c9a2~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b

[Daniel van Vugt (vanvugt)]

Please try:

1. Remove "nomodeset" from your kernel command line and `sudo update-initramfs`; then

2. Edit /etc/gdm3/custom.conf and uncomment the line:
     #WaylandEnable=false

3. Reboot

Can you log in now?

[Peter Bosch (peter.bosch)]

I'll try this first thing I get home!

Can I run the "sudo update-initramfs" during nomodeset? Or should I remove "nomodeset" first and start in recovery mode? Since otherwise, I am not able to get a command line.

[Peter Bosch (peter.bosch)]

1. $ sudo vim /etc/default/grub
2. removed "nomodeset" (leaving emptry string for GRUB_CMDLINE_LINUX
3. $ sudo update-grub
4. $ sudo update-initramfs -u
5. $ sudo vim /etc/gdm3/custom.conf
6. remove # in front of "#WaylandEnable=false", leaving "WaylandEnable=false" (under "[daemon]")
7. sudo reboot

I made sure before as well I am using gdm3 login manager by `sudo dpkg-reconfigure gdm3` and selecting "gdm3".

Unfortunately, this did not have the desired result. When the login screen pops up, the screen is frozen, and I can't login. Still the same as before.

I also installed OpenSSH before to try and connect from another computer, to get some details during the freeze. However, when the computer is frozen and I try to connect to it through SSH, it takes a while and then it says: "ssh: connect to host peter-h67m-ud2h port 22: No route to host".

[Daniel van Vugt (vanvugt)]

This is starting to sound like a kernel problem.

Are you able to log in to a VT? Instead of logging in normally try pressing Ctrl+Alt+F4 and then log into the text console.

If that worked then run:

  dmesg > dmesg.txt

and attach the resulting dmesg.txt to this bug.

[Peter Bosch (peter.bosch)]

I've tried that as well but that does not work either unfortunately. The system freezes pretty much directly after the purple screen appears. Hitting Ctrl+Alt+F4 does not do anything at that moment.

[Daniel van Vugt (vanvugt)]

Can you please try booting without the graphical splash? That way we might be able to see what's failing...

Try editing /etc/default/grub and change "splash" to "nosplash", then 'sudo update-initramfs' and reboot. You might then see errors on the next reboot and can take a photo of them.

[Peter Bosch (peter.bosch)]

I've done that now:

1. $ sudo vim /etc/default/grub
2. changed "splash" to "nosplash"
3. $ sudo update-initramfs -u
4. $ sudo update-grub
5. $ sudo reboot

Note:
* I've added the "-u" option to the update-initramfs as well (it tells me "You must specify at least one of -c, -u, or -d", so I did "-u" to update existing).
* I did a "sudo update-grub", because otherwise the changes do not have any effect when I restart.

I took some photos during start-up. I got some errors before the disk unlock (nosplash_1) and some after (nosplash_2). After that, the login page shows, and the screen is frozen again (nosplash_3).

[Peter Bosch (peter.bosch)]

I noticed that I have installed (and could only find) the amd64 image. I have a 64-bit Intel (https://ark.intel.com/products/52209/Intel-Core-i5-2500-Processor-6M-Cache-up-to-3_70-GHz) processor. Would that matter at all? (Maybe a dumb question, but throwing it out there anyway ;-))

[Daniel van Vugt (vanvugt)]

No, there are no known problems with that type of CPU/GPU...

[Peter Bosch (peter.bosch)]

Do you have any other possible solution or attempt I could do to get this solved? It's pretty annoying to have to run in nomodeset all the time. Screen res is making my eyes weird o.0 ;-)

[Peter Bosch (peter.bosch)]

I've just borrowed an external graphics card (ATI) from the office and plugged it, and then it boots without a problem.

So it definitely has to do with the GPU I mentioned. It would be too much of a coincidence if this was a hardware problem I think, since the problem appeared immediately since the upgrade to 18.04..

Anymore thoughts? Or is the only solution here buying an external graphics card?

[Daniel van Vugt (vanvugt)]

I should be able to find a similar machine to test on, but it will be a couple of weeks before I have time to do so. Please add another comment here if I forget...

[Peter Bosch (peter.bosch)]

I've solved it for me now with a new graphics card. Couldn't bare the nomodeset anymore knowing there was an alternative solution. Imagine how much I am attached to Ubuntu to rather buy a new graphics card then to switch to another OS ;-).

We can keep it open if you want further investigation and it might help with others. For me personally it is solved with the new graph card, so it can be closed as well. Up to you :-)

[Daniel van Vugt (vanvugt)]

Let's let the bug auto-expire if there are no more comments in 60 days.

[Launchpad Janitor (janitor)]

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