Installation Ubuntu 15.10 crash (asus GL752VW)

Bug #1529597 reported by Jérémie
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Hello

I just bought a asus laptop (GL752VW-T4005T), and I tried to install ubuntu 15.10, but the installation crashed.

I can boot correctly and choose with grud to install ubuntu or to try it. But shorter after I choose one option, the installation crash.
It's kind of random , sometime it's immediatly (black screen), sometime, some lines are displayed, sometime i can reach the selection of language, but i never could go further.

I try many different things (liveCD, usbCD, with UEFI (with secureboot or without), in legacy mod, with or wothiout fast boot, I also disabled fastboot in windows 10, i try with a minimal image disk in command line, and it also crash at the language seclection in the best case, and i also try to boot with the nomodeset option for the kernel.

However, I could install ubuntu 14.04.03 without any trouble (the only thing that I noticed is that my touchpad does not work)
I installed it in dual boot (with grub reusing the UEFI boot partition of windows 10 in the SSD). I let windows alone in my SSD and ubuntu is installed in the HDD.

You can find my boot-info here if needed: http://paste.ubuntu.com/14208400/

On the french forum, someone make me notice that a big difference between ubuntu 14.04 and ubuntu 15.10 is that ubuntu 14.04 uses systemd. Yet, I don't know if it the bug is coming from that ..

I can conduct more test if needed.

Edit: also, i tried to upgrade from an installation of ubuntu 14.04 to ubuntu 15.10, and he does the upgrade, but destroy my system (upgrade crash at the end, kernel panic after a reboot, etc...)

Also, I could boot on the live cd of mint 17.3, which is based on ubuntu 14.04
---
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jeremie 2028 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 15.10
HibernationDevice: RESUME=UUID=02daa242-0a9c-4ee6-8c30-0ec19e7f9053
InstallationDate: Installed on 2015-12-29 (6 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 04f2:b450 Chicony Electronics Co., Ltd
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL752VW
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic.efi.signed root=UUID=55064b7a-149f-4b7e-a1d6-28b74977a53e ro quiet splash idle=nomwait vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-22-generic N/A
 linux-backports-modules-4.2.0-22-generic N/A
 linux-firmware 1.149.3
Tags: wily
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
Uname: Linux 4.2.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/15/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL752VW.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL752VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL752VW.205:bd09/15/2015:svnASUSTeKCOMPUTERINC.:pnGL752VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL752VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: GL752VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Jérémie (jitsumi)
description: updated
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1529597/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Jérémie (jitsumi) wrote :

I think it's very difficult to identify the package (and i read https://wiki.ubuntu.com/Bugs/FindRightPackage)

Revision history for this message
Jérémie (jitsumi) wrote :

Ok, so I can correctly start it and install it if i use the boot option "idle=nomwait", and secure boot and the touch pad are working.
I get similar result with the option "nolapic", but only one core is working with this option.

Revision history for this message
Brian Murray (brian-murray) wrote :

If a kernel boot option modifies the behavior it seems like a kernel issue.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1529597

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jérémie (jitsumi) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected wily
description: updated
Revision history for this message
Jérémie (jitsumi) wrote : CRDA.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : IwConfig.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : JournalErrors.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : Lspci.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : ProcModules.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : PulseList.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : RfKill.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : UdevDb.txt

apport information

Revision history for this message
Jérémie (jitsumi) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Jérémie (jitsumi) wrote :

Also, my friend who have a msi laptop (i forgot which version, but a recent one, he just bought it) has the same problem than me.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

If you are experiencing the same issue as in bug #1522922, please:

1. Mark this bug as a duplicate of that.
2. In bug #1522922, into the tag list, write down "xenial".

In any case, set this bug status back to "confirmed". Thank you.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jérémie (jitsumi) wrote :

No, it's not the same issue as in bug #1522922 (in bug #1522922 ubuntu is booting and the screen is flickering, in my case, ubuntu is not booting at all)

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Does it happen if you remove the nvidia proprietary driver, or you install the intel-microcode package?

When answered, please set this bug status back to "confirmed".

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jérémie (jitsumi) wrote :

Yes it still happen without the nvidia proprietary driver (booting on liveCD with the nouveau driver does not work for example), and it still happen with the intel-microcode.

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

Jérémie, as per https://www.asus.com/us/ROG-Republic-Of-Gamers/ROG-GL752VW/HelpDesk_Download/ an update to your computer's buggy and outdated BIOS is available (210). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed. If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-210
removed: 15.10 boot installation
Changed in linux (Ubuntu):
importance: Critical → Low
status: Confirmed → Incomplete
Revision history for this message
Jérémie (jitsumi) wrote :

Hello, the bios update solve my problem.
Thanks!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
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.