[Asus ZenBook Prime UX31A] Installation, Live and Check disc do not start

Bug #1195483 reported by Pander
268
This bug affects 64 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Fix Released
High
Joseph Salisbury
Raring
Won't Fix
High
Joseph Salisbury
Saucy
Won't Fix
High
Joseph Salisbury
Trusty
Fix Released
High
Joseph Salisbury

Bug Description

When I try to install Ubuntu 13.04 on a new Asus ZenBook Prime UX31A from june 2013, grub will come up bit every option such as Installation, Live and Check disc result in a blank screen. This is possibly due to preinstalled Windows 8 and UEFI.

I did not approve/accept the Windows 8 installation and that should not matter. I want to install only Ubuntu and *no* dual boot with the preinstalled Windows 8. I want to erase the entire disc in firsts steps of installation procedure.

Screenshot illustrating the problem are:
http://i.imgur.com/94zPRh5.jpg (ASUS splash screen)
http://i.imgur.com/CKJZf6s.jpg (language selection for Windows 8)
http://i.imgur.com/2OIGnra.jpg (accept license, which I did not and rebooted with F1/F2)
http://i.imgur.com/0l3ZIme.jpg (general BIOS info, I upgrade to latest BIOS)
http://i.imgur.com/RtjRraF.jpg (used settings to boot from USB)
http://i.imgur.com/Vgb3Xju.jpg (grub which goes to black screen and systems is locked in that state)

For more information, see:
device information https://help.ubuntu.com/community/AsusZenbookPrime
similar problem http://ubuntuforums.org/showthread.php?t=2149954
UEFI and preinstalled Windwos 8 http://askubuntu.com/questions/221835/installing-ubuntu-on-a-pre-installed-uefi-supported-windows-8-system
More about EUFI https://help.ubuntu.com/community/UEFI
More on installing without WUBI http://www.omgubuntu.co.uk/2013/04/wubi-advice

Debugging attempts from https://wiki.archlinux.org/index.php/Boot_Debugging failed. Perhaps I did something wrong. What are ways to write debug to the screen in my case?

And, more importantly, how do I get it working because have the right to install whatever I want?

Is the only way to get it installed to accept the Windows 8 license and install Ubuntu from Windows (and in effect making it dual boot which I don't want).

Ubuntu should fix this as it is the flagship of a major laptop manufacturer (ASUS) for which Ubuntu is no longer installable.
---
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sander 2424 F.... pulseaudio
DistroRelease: Ubuntu 13.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=24994e67-9b18-4cad-b387-788beff8b388
InstallationDate: Installed on 2013-07-06 (80 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: ASUSTeK COMPUTER INC. UX31A
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-30-generic N/A
 linux-backports-modules-3.8.0-30-generic N/A
 linux-firmware 1.106
StagingDrivers: rts5139
Tags: raring staging raring staging raring staging
Uname: Linux 3.8.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/31/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31A.218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31A
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.:bvrUX31A.218:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnUX31A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX31A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX31A
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Pander (pander)
information type: Private Security → Public Security
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in shim (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

If GRUB comes up, this is not a shim bug, but a kernel bug with the video output. Reassigning.

affects: shim (Ubuntu) → linux (Ubuntu)
information type: Public Security → Public
Revision history for this message
vgeloven (vgeloven) wrote :
Revision history for this message
vgeloven (vgeloven) wrote :

How can I debug this? What do I add exactly where when editing grub?

Revision history for this message
vgeloven (vgeloven) wrote :

Extra question, would a newer kernel be worth trying? How do I add a new kernel to an USB Live image?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to see if this issue is resolved with the latest Saucy image, which can be downloaded from:
http://cdimage.ubuntu.com/daily-live/current/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key raring
Revision history for this message
Pander (pander) wrote :
Revision history for this message
Cris Dywan (kalikiana) wrote :

Tried with today's Saucy image and got a black screen even after disabling SecureBoot; updated the BIOS and SecureBoot was silently auto-enabled, this probably leads to inconsistent experiences. I did use a Raring stick successfully after that.

Revision history for this message
Jamie (jamie-practicaluseful) wrote :

Disabled secure boot: issue persists.
Tried the latest saucy image and still get the same: blank screen after grub.
Updated to latest BIOS (218) and retried (after checking secure boot was disabled): issue persists.
Suspect it is actually booting and the screen is blank - a bit of random button pressing causes the USB access light to flash.
Is there a way to change the display settings by editing the grub entry?

Revision history for this message
Jamie (jamie-practicaluseful) wrote :

Work around that at least gets me to a command prompt (with saucy):
Press 'e' to edit grub
Append to the end of the line that starts 'linux' and ends with '--' just before the --:
    nomodeset
Press F10 to save and boot.
Get the purple splash screen.
Drops to a command prompt.

What should I check from here?

Revision history for this message
Jamie (jamie-practicaluseful) wrote :

Back to Raring and it now works fine with no modification.
Resolution for 13.04 is that you must be on the latest BIOS and Secure Boot must be off.
(should have read Christian's response more closely!)

But the current saucy image still has this issue.

Changed in linux (Ubuntu Raring):
importance: Undecided → High
status: New → Confirmed
tags: added: kernel-key
Revision history for this message
Pander (pander) wrote :

Perhaps a silly question, but with UEFI and Windows 8 and all, I can still do anything I want with the hard drive? Can I remove all Windows 8 partitions without running into troubles? Because I really do not want that on my system.

Revision history for this message
Pander (pander) wrote :

Saucy daily results in a blank screen, with nomodeset it results in a command line. startx gives information in /var/log/Xorg.0.log that "(EE) Screen(s) found, but none have a usable configuration" Please fix this.

Raring installs but results in http://askubuntu.com/questions/282856/an-error-occurred-while-mounting-boot-efi

Revision history for this message
Pander (pander) wrote :

The error about being unable to mount boot is due to "unknown filesystem type ext2". This has to do with a kernel upgrade after installation. :( Please advise on how to upgrade without running into this problem again.

Revision history for this message
Pander (pander) wrote :

(Raring works without adding nomodeset. When nomodeset is added, low resolution is being used.)

Revision history for this message
Pander (pander) wrote :

On comment number #14, could be caused by enabling Fast Boot in BIOS of by incomplete apt-get upgrade. Second complete reinstall worked fine.

Please let me know if I can do any testing for the Saucy daily live image.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Just to confirm, withi Saucy, you are getting further with nomodeset specified? Once you specify nomodeset are you able to sucessfully install Saucy? If so, do you still need to specify nomodeset to boot sucessfully?

Also, it now sounds like Raring does not exhibit this bug? If so, it would be good to have someone with a working raring install try the saucy kernel[0] (with the expectation it would need nomodeset to work). The Saucy kernel .debs can be found by selecting a specific arch under "Builds".

If the Saucy kernel does require nomodeset to boot on a Raring install, we can then perform a kernel bisect to identify the commit that introduced this regression.

[0] https://launchpad.net/ubuntu/saucy/+source/linux/3.10.0-2.10

Revision history for this message
Allan Nielsen (an-luz) wrote :

I had the exact same problem with my new ux32vd born with windows 8. After trying most of what has been suggested and failing with the black screen during boot, I found that Disable the Secure Boot Control in the bios did the trick for me, and it boots 13.04 fine
- haven't tried saucy though.

I am very releaved as I couldn't possibly live with win8...

Revision history for this message
Pander (pander) wrote :

Saucy daily didn't work for me, with or without nomodeset

penalvch (penalvch)
tags: removed: 13.04 asus eufi grub install installation shim
Changed in linux (Ubuntu Raring):
status: Confirmed → Invalid
tags: added: needs-kernel-logs saucy
removed: raring
Changed in linux (Ubuntu Saucy):
status: Confirmed → Incomplete
2 comments hidden view all 127 comments
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Pander, would it be possible for you to test the Saucy kernel on a Raring installation?

Revision history for this message
Pander (pander) wrote :

Yes. Please provide exact instruction to install it *without* it becomming my default kernel so I can simply reboot back into a working situation. And tell me what logs to send to you.

Revision history for this message
penalvch (penalvch) wrote :

Pander, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483/comments/23 :
>"Yes. Please provide exact instruction to install it *without* it becomming my default kernel so I can simply reboot back into a working situation."

Instructions may be found in https://wiki.ubuntu.com/Kernel/MainlineBuilds .

>"And tell me what logs to send to you."

The logs requested are provided via you posting in a terminal:
apport-collect 1195483

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Pander, one additional question. Does this issue not exist in Saucy if you boot with Secure Boot disabled?

tags: removed: kernel-key
Revision history for this message
Pander (pander) wrote :

Christopher, could you send me the exact commands to execute. In that way we both know how to replicate the situation later and I am testing the kernel you are intending me to test.

Revision history for this message
Helmut (helmut-lammel) wrote :

I tried the Zenbook without the secure boot.
There was no difference.
Grub came up an as soon as the Ubuntu was started i had an black screen.
So i went back to 13.04

Atom Stark (atomstark)
Changed in linux (Ubuntu Raring):
status: Invalid → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I tried with saucy desktop build 20130902 / amd64 on an Asus UX32VD-R4030P, with secure boot disabled. Live Session, installation and system boot after installation went all fine. Note that I wiped all existing data on the 2 drives that comes with this machine and installed the system on the SSD.

Revision history for this message
Timo Kluck (tkluck) wrote :

I can confirm this issue. I can get to my desktop by attaching an external monitor -- it is apparently only the internal display which doesn't work. This is on a raring -> saucy upgrade.

I also tried mainline kernel 3.11.1-031101-generic and it has the same issue.

I will gladly help getting this fixed. I'm pretty proficient with git and I did a kernel build before, so I could theoretically do a bisect. If someone 'in the know' can give me some extra starting points (do I build a .deb for each bisect step?), I can probably find the offending commit.

Thanks!

Revision history for this message
penalvch (penalvch) wrote :

Timo Kluck, could you please file a report so your hardware may be logged via a terminal:
ubuntu-bug linux

Feel free to subscribe me to it.

Revision history for this message
Timo Kluck (tkluck) wrote :

@Christopher: will do.

I'm in the process of bisecting. The problem has been introduced somewhere between v3.10-rc1 and v3.10-rc2. More precisely, it has been introduced between v3.10-rc1 and commit fea0f9f. Looking at the logs, the latter is a likely candidate:
---
Pull drm fixes from Dave Airlie:
     "Just a few straggling fixes I hoovered up, and an intel fixes pull
      from Daniel which fixes some regressions, and some mgag200 fixes from
      Matrox."
---
I'm bisecting that branch now.

Revision history for this message
Pander (pander) wrote :
Revision history for this message
Pander (pander) wrote :

I think you can also do
$ apport-collect 1195483
instead of
$ ubuntu-bug linux
correct?

Revision history for this message
Timo Kluck (tkluck) wrote :

This bug was introduced in 657445fe8660100ad174600ebfa61536392b7624
---
Author: Daniel Vetter <email address hidden>
Date: Sat May 4 10:09:18 2013 +0200

    Revert "drm/i915: revert eDP bpp clamping code changes"

    This reverts commit 57c219633275c7e7413f8bc7be250dc092887458.

    It's an ugly hack for a Haswell SDV platform where the vbt doesn't
    seem to fully agree with the panel. Since it seems to cause issues on
    real eDP platform let's just kill this hack again.

    Reported-and-tested-by: Josh Boyer <email address hidden>
    References: https://lkml.org/lkml/2013/5/3/467
    Cc: Paulo Zanoni <email address hidden>
    Signed-off-by: Daniel Vetter <email address hidden>
-----
I'll investigate a bit, but this is not exactly my expertise.

Revision history for this message
Timo Kluck (tkluck) wrote :

My very brief investigation shows that this piece of code has been applied and reverted a few times already, apparently because some hardware works with it and other hardware works without it.

I'll install the raring kernel on my own machine and use that for now; I guess it's up to the ubuntu kernel team to decide how to handle this. I'll stay available for testing!

Timo Kluck (tkluck)
Changed in linux (Ubuntu Saucy):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Pander, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483/comments/33 :
I think you can also do
$ apport-collect 1195483
instead of
$ ubuntu-bug linux
correct?

No. "Me too!" comments and attachments are largely unhelpful. Instead, it would be best for others to file a new report via:
ubuntu-bug linux

Changed in linux (Ubuntu Saucy):
status: Confirmed → Incomplete
Pander (pander)
tags: added: apport-collected raring staging
description: updated
1 comments hidden view all 127 comments
Revision history for this message
Pander (pander) wrote : AlsaInfo.txt

apport information

Revision history for this message
Pander (pander) wrote : BootDmesg.txt

apport information

Revision history for this message
Pander (pander) wrote : CRDA.txt

apport information

penalvch (penalvch)
tags: added: bios-outdated-219
Changed in linux (Ubuntu Saucy):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Raring):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Saucy):
status: Confirmed → Incomplete
Apostolos D (apdim9)
Changed in linux (Ubuntu Saucy):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu Saucy):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Raring):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Saucy):
status: Incomplete → Confirmed
tags: added: kernel-key
no longer affects: linux (Ubuntu Raring)
Changed in linux (Ubuntu Saucy):
status: Confirmed → In Progress
assignee: nobody → Joseph Salisbury (jsalisbury)
tags: removed: raring
Changed in linux (Ubuntu Saucy):
assignee: Joseph Salisbury (jsalisbury) → nobody
assignee: nobody → Joseph Salisbury (jsalisbury)
47 comments hidden view all 127 comments
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Installation, Live and Check disc do not start on Asus ZenBook Prime UX31A

I can confirm the fix for this bug is in 3.12 final:

git describe --contains 7195a50b5c7e00cc3312934fd022c3006b533d12
v3.12~20^2~1^2~3

The fix has been cc'd to stable, but I don't see it in the stable trees as of yet.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

I built a trusty test kernel with the following commits from upstream:
c6cd2ee2d59111a07cd9199564c9bdcb2d11e5cf
7195a50b5c7e00cc3312934fd022c3006b533d12
4f56d12ebb28fceac4c6e60c8993fbfc122e1399

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1195483/

Can you test this kernel and confirm if it fixes this bug or not?

Revision history for this message
Till Kinstler (spam-kinstler) wrote :

I can confirm, that kernel 3.12.0 from #89 fixes this bug. Video output works as expected on my UX31A.

Though, installing the packages, dpkg complains about missing dependencies: linux-tools-3.12.0-1-generic misses linux-tools-3.12.0-1

Changed in linux (Ubuntu Raring):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug is now fixed in Trusty and will be fixed in the stable releases shortly.

Changed in linux (Ubuntu Trusty):
status: In Progress → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
Tim (swearingen-tim) wrote :

How long till this is released? as trusty does not yet download with do-release-upgrade -d

Revision history for this message
Amandine (z-launchpad-w) wrote :

I also confirm that the kernel 3.12.0 from #89 fixed the bug on my UX31A just after upgrading to 13.10.

Revision history for this message
Benjamin Gerfelder (benjamin-gerfelder) wrote :

Just upgraded 13.04 to 13.10 on the Zenbook and ran into what I believe is this problem.

In case anyone is looking for an easy solution, workaround was to go to the bios, and under "boot", set "CSM enabled" and the issue disappeared. No kernel switching was required.

penalvch (penalvch)
summary: - Installation, Live and Check disc do not start on Asus ZenBook Prime
- UX31A
+ [Asus ZenBook Prime UX31A] Installation, Live and Check disc do not
+ start
Changed in linux (Ubuntu Saucy):
status: In Progress → Fix Released
Revision history for this message
marque (vivideo) wrote :

I have the same problem on my ASUS K52J: i.e. black screen after upgrading my Ubuntu 13.04 to 13.10. The only way for me to get in my Linux enviroment is to boot with kernel 3.8 and having an external monitor connected. Then my internal screen remains black, but I can 'work' on the monitor...

I also updated the kernel to jsalisbury's 3.12 version. That seemed to help. But instead of getting a black screen, only the mouse appears on the black screen.. (without any possibility to do/access something).

So for me, my Ubuntu 13.10 is not fixed yet and I hope this issue will be solved in coming updates.

Cheers!

Revision history for this message
Pander (pander) wrote :

Same here, I need to escape the booting process and boot manually 3.8

1 comments hidden view all 127 comments
Revision history for this message
Till Kinstler (spam-kinstler) wrote :

On Saucy I just got kernel 3.11.0-14 via updates this morning. The bug is not fixed in this kernel release for Saucy. Same symptoms as described in this bug report: System boots, but internal screen stays black/blank, though external display shows Ubuntu desktop.
The bug is fixed in 3.12.0-031200 I got from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-saucy/
Setting "CSM = enabled" doesn't help either, then no kernel boots on my UX31A (BIOS version 219, latest), but hangs right after selecting it in grub.

Revision history for this message
hogart (s-ryazansky) wrote :

Yes, I can confirm the message #98 - the update to 3.11.0-14 release didn't fix the bug in Saucy.

description: updated
1 comments hidden view all 127 comments
Revision history for this message
hogart (s-ryazansky) wrote :

 Chrostopher M.Penalver, sorry, but I am really don't understand what you are mean in your answear. According to the bug description, it is related to several Ubuntu versions - 13.04. 13.10 and 14.04. The status of the bug was changed as 'fixed' to 14.04 and 13.10 ones. In my message I (and several other folks above) have reported that in the novel 3.11.0-14 kernel the bug is still present. Whats wrong in my post? Why I have to create the novel bug report with similar problem that is described here?

Revision history for this message
Eric O'Connor (oconnore) wrote :

Christopher Penalver -- the "fix released in Saucy" is clearly not correct. Creating a new bug report won't help anyone, and would correctly be marked as a duplicate of this bug.

This "fix released" tag should perhaps be changed to "in progress", since the fix is not actually available through apt-get, and is therefore not "released".

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Sorry, this should have been marked as "Fix Committed" for Saucy. The fix is in the Ubuntu-3.11.0-15.22 kernel.

Changed in linux (Ubuntu Saucy):
status: Fix Released → In Progress
status: In Progress → Fix Committed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Those interested in testing can enable the -proposed repository. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

Revision history for this message
Devon Cooke (devonavar) wrote :

I'm afraid I don't understand the versioning system for linux properly...

I got myself on -proposed, updated via apt-get, and pulled down 3.11.0.15.16. Does this version contain 3.11.0-15.22? What is the difference between the "0.15" versions that I can get from apt, and the "0-15" version that is referenced here?

If the version from -proposed does not contain the proposed fix, should I be trying to apply the .debs directly? I'd rather not mess with my kernel outside of apt, since I'm not 100% sure how it integrates back in...

If 3.11.0.15.16 DOES contain the proposed fix, it does NOT fix this problem on the ASUS UX32VD, which I had assumed it would. I have not seen a parallel bug report for my specific model — should I be creating one? Most problem fixes I've seen have directed me to this bug report or one of the duplicates.

1 comments hidden view all 127 comments
Revision history for this message
hogart (s-ryazansky) wrote :

Most likely, that '3.11.0.15.16' is the same as '3.11.0-15.16' and, so, this is not yet '3.11.0-15.22'.

Revision history for this message
Robert Bamler (robamler) wrote :

I can confirm that the kernel currently in "saucy-proposed" resolves this issue on my UX31A (Asus Zenbook Prime). The output of "uname -a" reads:
Linux zenbook 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Devon Cooke (devonavar) wrote :

Ok, now that I've figured out how to upgrade the kernel properly, I can confirm that the issue is resolved on my Asus Zenbook UX32VD for 3.11.0-15-generic

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote :

Experiencing similar behaviour from zenbook ux302lg. Pinning and upgrading to trusty kernel gives me slightly different outcomes (I get a backlight down and red streak appear) before backlights up and blank screen where I hear the Cowbell of lightdm.

I don't get the red tear at all with Saucy default kernel.

I'LLC get an apport dump and attach soon.

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : apport information

ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lightdm 1389 F.... pulseaudio
 /dev/snd/controlC0: lightdm 1389 F.... pulseaudio
CRDA:
 country SG:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5735 - 5835 @ 40), (N/A, 20)
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=808c568f-76fa-46d3-9e60-276860ebe1ec
InstallationDate: Installed on 2013-12-20 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 03eb:8a03 Atmel Corp.
 Bus 001 Device 003: ID 1bcf:2987 Sunplus Innovation Technology Inc.
 Bus 001 Device 002: ID 8087:07dc Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX302LG
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic.efi.signed root=UUID=c4550a46-5cb3-4033-ac7f-3bc9d38959f8 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
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.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic N/A
 linux-firmware 1.116
Tags: saucy saucy
Uname: Linux 3.12.0-7-generic x86_64
UpgradeStatus: Upgraded to saucy on 2013-12-20 (0 days ago)
UserGroups:

dmi.bios.date: 10/30/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX302LG.207
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX302LG
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.:bvrUX302LG.207:bd10/30/2013:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX302LG
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : AlsaInfo.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : BootDmesg.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : IwConfig.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : Lspci.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : ProcEnviron.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : ProcModules.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : RfKill.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : UdevDb.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : UdevLog.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote : WifiSyslog.txt

apport information

Revision history for this message
Joel Wirāmu Pauling (aenertia) (aenertia) wrote :

Opened a new Bug for UX302LG version of this bug - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263015

Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Saucy):
status: Fix Committed → Won't Fix
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug was nominated against a series that is no longer supported, ie raring. The bug task representing the raring nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Raring):
status: In Progress → Won't Fix
Displaying first 40 and last 40 comments. View all 127 comments or add a comment.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.