Asus X200MA Black Screen after LTS Update (3.13.0-49-generic)

[Stilmant Michael]

related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427646

Description: Ubuntu 14.04.2 LTS
Release: 14.04
cat /proc/version_signature := Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Linux Lux1-Ops-LiloXX 3.13.0-49-generic #83-Ubuntu SMP Fri Apr 10 20:11:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-49-generic 3.13.0-49.83
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
Uname: Linux 3.13.0-49-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Tue Apr 21 09:45:44 2015
HibernationDevice: RESUME=UUID=8cfe631b-97f1-4da1-b1b2-15675c32779e
InstallationDate: Installed on 2015-01-19 (91 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
 Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 734c:5220 TBS Technologies China
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic.efi.signed root=UUID=44c3a9ad-88df-4e7e-833f-257b8e54822d ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-49-generic N/A
 linux-backports-modules-3.13.0-49-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.502
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
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.:bvrX200MA.502:bd09/11/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X200MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Stilmant Michael (michael-stilmant)]

Hello Christopher,

According to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427646/comments/7
I've created this bug report. Sorry I'm new to bug reporting but somehow this will created an duplicate isn't it?

Tell me if you need more details.

[penalvch (penalvch)]

Stilmant Michael, thank you for reporting this and helping make Ubuntu better. Could you please bring your BIOS up to parity via http://www.asus.com/Notebooks_Ultrabooks/X200MA/HelpDesk_Download/ (504) following https://help.ubuntu.com/community/BIOSUpdate ?

[Zsolt Rizsanyi (rizsanyi)]

I have upgraded my bios to version 504 and it did not help.

[penalvch (penalvch)]

Zsolt Rizsanyi, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

[Stilmant Michael (michael-stilmant)]

Hello Christopher,

if Zsolt Rizsany fill up a new report, is that report will not create a new third entry for the same issue?
For my reference and for future, how to link such kind of new report to existing bug ?

Thanks.

[Stilmant Michael (michael-stilmant)]

I have also upgraded my bios to version 504 and indeed it is not helping but there is a change in the fact that the back-light is now turning on allowing to see video artifacts.

I've succeeded to get something on screen by using 'nomodeset' kernel parameter but at the end the X session is running in some sort of low resolution (VESA?)

Maybe this would be resolved by usage of some proprietary driver but there is no "Additional Drivers" available from UI.
And proprietary was not needed in the past.

[Stilmant Michael (michael-stilmant)]

I missed that thread that is more advanced : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416849

[penalvch (penalvch)]

Stilmant Michael, could you please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Just to advise, there is nothing advanced at all about LP#1416849.

[Stilmant Michael (michael-stilmant)]

Thanks for your follow up Christopher

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
X200MA.504
11/13/2014

The advanced side of LP#1416849 is that the identification of the kernel working and new not working is done there. (thanks to exercises made on kernel-fixed-upstream tags side)

I'm not sure why you want to work on 3 bugs thread for same issue? And also I don't understand why you don't confirm that bug? There is indeed more that one person affected isn't?

Installing a fresh image of a LTS 14.04.2 is installing 3.16 kernel base and that "LTS 14.04.2 3.16" is working. no black/white screen issue.

The laptop having issue reported in this thread (and other thread) are installed from LTS 14.04.2 having kernel (point release? ) stuck to 3.13

doing an apt-get update & disp-upgrade don't update that laptop from 3.13 to 3.16.

I believe the solution for my issue is to found the best way to upgrade my laptop(s) from 3.13 to 3.16 while staying on a real LTS 14.02.x release.

doing:
sudo apt-get install --install-recommends linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic libegl1-mesa-drivers-lts-utopic
from https://wiki.ubuntu.com/Kernel/LTSEnablementStack

resolve the situation since it move to

GNU/Linux
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
Linux Lux1-Ops-LiloXX 3.16.0-36-generic #48~14.04.1-Ubuntu SMP Wed Apr 15 13:11:28 UTC 2015 x86_64 x86_64 x86_64

But I'm not sure it is what I want/ the best option.

So, so far for me, Ubuntu 14.04.2 LTS installed prior to 3.13.0-44 are working, the problem appeared with 3.13.0-45 update of that Ubuntu 14.04.2 LTS
and new installation of Ubuntu 14.04.2 LTS is based on 3.16.x that is working.

I was not aware of such variation between same LTS regarding point release. Maybe I need to understand how to move a distribution from one point release to the next one.

[Stilmant Michael (michael-stilmant)]

I believe I've a partial answer from here

"As a Long Term Support release, Ubuntu 14.04.2 includes an updated hardware enablement stack that includes the 3.16 Linux kernel and an updated version of the Xorg display server. [...] The new hardware enablement stack will be installed by default if you install from 14.04.2 installation media, but if you’re humming along nicely with the current versions of Xorg and the Linux kernel on 14.04 and 14.04.1, fear not – the new stack is not installed by default and is completely opt-in."

from here: http://www.omgubuntu.co.uk/2015/02/ubuntu-14-04-2-lts-released-includes-3-16-kernel
details of the stuf: http://askubuntu.com/questions/506956/how-can-i-install-3-16-kernel-on-ubuntu-14-04

So I believe to understand that if we want to correct the proper way LTS 14.04.2 release installed prior a fresh 14.04.2 installation media, future 3.13.x release update of LTS 14.04.2 needs to include the correction to avoid to force people to install HWE.
What you are trying to track Christopher. Right?

So my situation is to not update kernel over 3.13.0-44 for X200 laptops where LST 14.04.X is already installed.
for those laptop I would need to wait, eventually, LTS 14.04.3 around august.
on new X200 laptops laptops the LTS 14.04.2 include 3.16 by default. (what strange is that some how, update of linux-generic-lts-utopic was already held back)
And for laptop updated to 3.13.0-45, or i need to install HWE from linux-generic-lts-utopic and co, or I need to wait for 3.13.0-x providing some roll-back or some code correction.

So I understand, that next steps are really to do your advice from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416849/comments/17

But I guess 3.16 is needed and not 3.19. right?

Thanks.

[penalvch (penalvch)]

Stilmant Michael, given the issue is resolved for you in the Ubuntu kernel 3.16, did you need a backport to a kernel/release prior to this, or may this be closed as Status Invalid?

[Stilmant Michael (michael-stilmant)]

What I describe is more like a workaround.

The problem remains for users with ubuntut LTS version (installed prior 3.13.0-44 kernel) doing a 'normal' update and falling back into that black screen.

I'm in favor to close this bug entry since, I guess, you will continue to work for, eventually, a kernel back-port in LP#1416849.

Thanks for your support.

[penalvch (penalvch)]

Stilmant Michael, just to clarify, if you update to the Utopic enablement stack and the problem is gone, it's considered fixed (i.e. not a WORKAROUND). Hence, for you personally (not speculating to what other users may or may not have or do) do you need a backport regarding the scope of this bug report (not some other bug report)?

[Launchpad Janitor (janitor)]

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