Ubuntu fails to show splash screen after upgrade to 3.0.0-15

Bug #926325 reported by Andrew Davis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

After running some upgrades under Ubuntu 11.10, my Asus UL20FT laptop would not boot. It's a dual-boot setup, so the Grub sreen appeared automatically, but after selecting linux 3.0.0-15, it diplayed only a dark screen. I'm reporting this as a plymouth bug in accordance with the instructions here (https://wiki.ubuntu.com/Bugs/FindRightPackage), since I was able to boot in recovery mode

Strategies tried:
- Robooting with recovery mode, machine booted with some issues like low screen resolution
- Rebooting and selecting version 3.0.0-14 from previous versions, machine booted and worked properly
- Re-installed linux 3.0.0-15 packages, machine still would not boot 3.0.0-15
- Removed 3.0.0-15 packages with synaptic, now machine boots 3.0.0-14 by default and works properly

I notice that 3.0.0-15 is no longer showing up as an update for me. I'm aware of a similar thread here (http://ubuntuforums.org/showthread.php?p=11629620), although that person had some success by re-installing the package.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Fri Feb 3 15:23:09 2012
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 003: ID 064e:a136 Suyin Corp. Asus Integrated Webcam [CN031B]
MachineType: ASUSTeK Computer Inc. UL20FT
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=7c6d73e4-e301-4ad9-8509-533449b932e7 ro quiet splash vt.handoff=7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=7c6d73e4-e301-4ad9-8509-533449b932e7 ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 218
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UL20FT
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr218:bd08/12/2010:svnASUSTeKComputerInc.:pnUL20FT:pvr1.0:rvnASUSTeKComputerInc.:rnUL20FT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UL20FT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Andrew Davis (spinup) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Hi Andrew,

Sounds like a kernel regression. Reassigning to the linux package.

> I'm reporting this as a plymouth bug in accordance with
> the instructions here (https://wiki.ubuntu.com/Bugs/FindRightPackage),

Thanks for mentioning this - let me see what I can do to improve those directions :-)

affects: plymouth (Ubuntu) → linux (Ubuntu)
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Herton R. Krzesinski (herton) wrote :

Hi, can you enable -proposed and update/boot to kernel 3.0.0-16.28, and report the results here? Probably you hit a bug which is fixed there. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Revision history for this message
Andrew Davis (spinup) wrote :

I have tried updating to 3.0.0-16 from the proposed repository. Unfortunately the machine would not boot with that kernel either.

Revision history for this message
Herton R. Krzesinski (herton) wrote :

Ok, can you follow the "Boot Options" instructions from https://wiki.ubuntu.com/DebuggingKernelBoot and capture the messages? May be that will help pointing the cause of the boot failure.

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

Might be bug 925350 - could you try booting with i915.lvds_use_ssc=0 on the command line (comment #35 in that bug)?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: regression-update
Revision history for this message
Andrew Davis (spinup) wrote :

Thanks for the suggestion, Julian! The proposed kernel boots fine with the i915 parameter set. I'm seeing:

$ more /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic root=UUID=7c6d73e4-e301-4ad9-8509-533449b932e7 ro quiet splash vt.handoff=7 i915.lvds_use_ssc=0

As I understand it from that bug, this will be fixed in 3.0.0.18, then.

Revision history for this message
Herton R. Krzesinski (herton) wrote :

So this should be the same as bug 925350. The fix indeed is to be released with the 3.0.0-18.31 kernel, still in process to go to -proposed/-updates. Marking as duplicate of 925350.

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.