ASUS Laptop black screen during boot / F2 key showing why
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrading from Ubuntu 14.04.1 LTS to Ubuntu 14.04.2 LTS
Black screen during booting.
Using: Ubuntu 14.04.2 LTS / Laptop ASUS K70AC - 500Gb Hard-disc (crypted)
After started booting the screen turns to the Ubuntu colors for a second and then turns to solid black and nothing happens after that.
I noticed that, when I quickly tuned off the power (battery -by removal- and mains) and then reinstalling and pressing the power button, the system showed me the GRUB choice with different Linux versions.
Clicking the first (is newest) Linux version completed the booting.
After having done this many times (no update for this bug so far), I clicked
the F2 button (ASUS uses this key to get into the BIOS) while the screen was black, just to see what would happen.
To my surprise my screen showed the following text (white font on black screen):
Unlocking the disk /dev/disk/
Enter passphrase:
After entering my passphrase Ubuntu completed the booting in the usual way!
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 3.16.0-38-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Wed May 27 17:19:39 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-16 (10 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitec
SourcePackage: ubuntu-
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | ubuntu-release-upgrader (Ubuntu) → plymouth (Ubuntu) |
Hi,
I have amost the same problem but my laptop is a Dell Inspiron N5110 with AMD. So I noticed that when I close the screen cover and open again, it back image screen requested to enter with my log in. It's like I had let the laptop hibernate.
The workaround was close the screen cover and open again.
I still checking the bugs to see if has a upgrade ou update to fix it.
Best regards,
Daniel