Screen goes blank after booting

[Manoz]

I can only use the recovery mode and not the normal mode on ubuntu. This is happening after i upgraded to Ubuntu 18.04. I have an Asus R554L model laptop and no special hardware at this time.

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
.tmp.unity_support_test.1:

ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompositorRunning: None
Date: Fri Apr 27 22:59:45 2018
DistUpgraded: 2018-04-27 22:06:39,664 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:235a]
InstallationDate: Installed on 2018-04-27 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK COMPUTER INC. TP550LAB
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c1a388d3-c492-42e1-a077-44d34cf97386 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-28 (0 days ago)
dmi.bios.date: 12/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP550LAB.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TP550LAB
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.:bvrTP550LAB.202:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnTP550LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TP
dmi.product.name: TP550LAB
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.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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: Fri Apr 27 22:43:41 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

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

What is the problem you see in normal mode? Can you take a photo?

[Iron Davey (idb151)]

I'm having the same problem too after just upgrading to 18.04 on my R554LA hardware. I've found that sometimes I actually see the login screen, but then it immediately goes blank - as if the screen was turned off using the blank display keys (Fn+F7). Once this happens, if I plug in an HDMI cable connected to my TV, the screen turns on again, and will remain on once I unplug the HDMI cable. This will survive a sleep/wakeup event but not a reboot.

In my Xorg.0.log file, I see HDMI getting enabled (not sure if this is a cause, an effect, or not relevant):

==========================
[ 2.798] (II) FBDEV: driver for framebuffer: fbdev
[ 2.798] (II) VESA: driver for VESA chipsets: vesa
[ 2.799] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151010
[ 2.799] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 (Timo Aaltonen <email address hidden>)
[ 2.799] (II) intel(0): SNA compiled for use with valgrind
[ 2.800] (WW) Falling back to old probe method for modesetting
[ 2.801] (WW) Falling back to old probe method for fbdev
[ 2.801] (II) Loading sub module "fbdevhw"
[ 2.801] (II) LoadModule: "fbdevhw"
[ 2.801] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 2.802] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 2.802] compiled for 1.18.4, module version = 0.0.2
[ 2.802] ABI class: X.Org Video Driver, version 20.0
[ 2.802] (WW) Falling back to old probe method for vesa
[ 2.803] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 5500
[ 2.803] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2; using a maximum of 2 threads
[ 2.803] (II) intel(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[ 2.803] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[ 2.803] (==) intel(0): RGB weight 888
[ 2.803] (==) intel(0): Default visual is TrueColor
[ 2.804] (II) intel(0): Output eDP1 has no monitor section
[ 2.820] (--) intel(0): Found backlight control interface intel_backlight (type 'raw') for output eDP1
[ 2.820] (II) intel(0): Enabled output eDP1
[ 2.820] (II) intel(0): Output HDMI1 has no monitor section
[ 2.820] (II) intel(0): Enabled output HDMI1
[ 2.820] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[ 2.820] (II) intel(0): Output VIRTUAL1 has no monitor section
[ 2.820] (II) intel(0): Enabled output VIRTUAL1
[ 2.820] (--) intel(0): Output eDP1 using initial mode 1366x768 on pipe 0
[ 2.820] (==) intel(0): TearFree disabled
[ 2.820] (==) intel(0): DPI set to (96, 96)
=======================================

[Daniel van Vugt (vanvugt)]

Thanks for the additional information about the Asus R554LA.

Unfortunately it appears Manoz has reported this bug from a different machine (TP550LAB) so all the attached system information is not relevant to the reported problem.

I suggest someone please open a new bug using an actual R554LA.

[Daniel van Vugt (vanvugt)]

... which does mean you will need to use a workaround to the problem first.