On 2.6.35 kernels does not boot when using plymouth

Bug #612769 reported by LCID Fire
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

When I boot the kernel - I get a low res ubuntu logo and then the computer does not seem to do anything anymore (no HD activity either). ACPI works though.
When I remove the "splash" option in grub2 it boots fine.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Aug 3 00:27:56 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
MachineType: Dell Inc. Latitude E5400
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=bbfec93c-20fb-4654-b60f-b93bf5fc1b53 ro crashkernel=384M-2G:64M,2G-:128M quiet
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 11/05/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0K644C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/05/2009:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0K644C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E5400
dmi.sys.vendor: Dell Inc.

Revision history for this message
LCID Fire (lcid-fire) wrote :
Revision history for this message
LCID Fire (lcid-fire) wrote :

Works in Release Candidate - is a problem though when attempting to use Kernel 2.6.32.

Revision history for this message
dino99 (9d9) wrote :

outdated report & no more maintained distro; please send a new one if that issue still exist (using ubuntu-bug)

Changed in plymouth (Ubuntu):
status: New → 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.