Xorg freeze (black screen after ubuntu logo during boot)

[Benjamin Li]

I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system.

So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode.

Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again!

What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you!

And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04.

What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS.

Any help is appreciated, thanks in advance!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.17.0-041700rc3-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 5 19:49:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Today
GraphicsCard:
 Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd]
InstallationDate: Installed on 2018-04-04 (215 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: ASUSTeK COMPUTER INC. T300FA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: T300FA.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: T300FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: T
dmi.product.name: T300FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Tue Nov 6 03:47:33 2018
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.6-1ubuntu4.2

[Cristian Aravena Romero (caravena)]

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19

[Cristian Aravena Romero (caravena)]

-> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1
--
Cristian

[Daniel van Vugt (vanvugt)]

The machine is stuck in recovery mode, according to the kernel command line:

[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset

To fix this, you need to reboot and then press Esc as soon as the purple screen appears. Now select the proper kernel that is not recovery mode.

[Benjamin Li (seasone-liii)]

Thanks for all you guys reply!!

And since there are two different suggestion, so I will reply respectively.

To Cristian,

Yes, the issue I am facing happens after I upgraded from Ubuntu 16.04 to 18.04.

But no, or correctly, I don't know. As I followed what you suggested and do the test with the installation of latest kernel, V4.19, I can't even get to the phase where I can see the Ubuntu logo! Only a screen filled with error messages, which I took the photo and attach it as follow.

So, let me rephrase what happened again. I headed to the kernel mainline page under V4.19. And download these three, as I followed the steps in the https://wiki.ubuntu.com/Kernel/MainlineBuilds:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901_4.19.1-041901.201811041431_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-image-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-modules-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb

and after 'wget' done in the terminal (the files have been downloaded in the folder I chose) I use the command: "sudo dpkg -i *.deb"

Then reboot.

Then what's on the screen was what you see in the attachment.

I think it might be my laptop does not support this kernel? Since my laptop is so weird, meaning the screen of my laptop is touch-screen and detachable. So, sorry for your inconvenience of making the Ubuntu be compatible with my rare device, sorry.

As for Daniel,

So thank you for your advice, however, the issue I am facing is not when I tried to get in recovery mode or I was stuck at the recovery mode. No. I am only in the recovery mode is because this is the only way I can report this bug because I can not get in when it's in the regular mode and for some reason, I am able to access the Ubuntu when I am in the recovery mode.

And this is how I get in:

When I stuck at the black screen which show up after the Ubuntu logo. I did turn off the laptop forcefully buy long press the "turn on laptop" button, then turn on again.

But this time I switch from "Ubuntu" to "Advance something something option" and get to the menu where I can chose to boot under the recovery mode.

When I selected recovery mode, press enter, after all those scripts loading finish, and press "enter" or enter "Y" for one or two times, I reach to another menu where I can see, "Resume something" (or some words else but it's the first option in the menu), then I chose it, press enter, here I am!

So... was I clear in my above description?

And thank you all so much for the help and suggestion! All your active reply is why I love Ubuntu so much, even my device is such a pain, which I am sorry!

[Benjamin Li (seasone-liii)]

I am so so so sorry for I made a mistake of selecting the wrong kernel with the wrong architecture to install, which lead to all those error messages during boot in v4.19. (My laptop should install the kernel with architecture amd64 but I installed i386, I am so sorry for making things more complicated, SORRY!!!)

Anyway, I "apt purge" the wrong kernel (4.19 with architecture i386) and just installed the proper one(architecture amd64).

However! The issue in the v4.17 remain in the 4.19! I don't see anything improve in my situation, I still can't get in the system, getting stuck in the black screen after the Ubuntu logo during the boot, I can only access the system in recovery mode; the brightness of my display can't be adjusted; the setting for my display still says "Unknown Display", and the laptop can't get back if I put the whole system into sleep mode(by turn off the display)

Any idea? Please help!!!! Thanks in advance!

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

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