Dell C640 fails normal boot with 2.6.30

Bug #391322 reported by Olof Kindgren
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading to Karmic I can no longer use "normal" boot. After selecting the default kernel in grub2, the screen goes black and scroll lock and caps lock starts blinking. To recover I have to press the power button a few seconds.

If I however select recovery mode and select resume normal boot after the kernel has finished loading, everything works fine.

In Grub I also have a manually compiled 2.6.28 kernel (basically the stock kernel without some unneeded modules). If I use that kernel I can boot normally, so I suspect this is a 2.6.30 problem.

ProblemType: Bug
Architecture: i386
Date: Tue Jun 23 22:23:23 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=03124330-9865-41c0-a9b8-3741c59906fd
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Computer Corporation Latitude C640
Package: linux-image-2.6.30-10-generic 2.6.30-10.12
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.30-10-generic root=UUID=661c4eec-257e-4603-9ab2-a863a150a769 ro single
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
RelatedPackageVersions:

SourcePackage: linux
Uname: Linux 2.6.30-10-generic i686
dmi.bios.date: 12/10/2002
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A05
dmi.board.name: Latitude C640
dmi.board.vendor: Dell Computer Corporation
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA05:bd12/10/2002:svnDellComputerCorporation:pnLatitudeC640:pvr:rvnDellComputerCorporation:rnLatitudeC640:rvr:cvnDellComputerCorporation:ct8:cvr:
dmi.product.name: Latitude C640
dmi.sys.vendor: Dell Computer Corporation

Revision history for this message
Olof Kindgren (flamingolof) wrote :
Revision history for this message
Olof Kindgren (flamingolof) wrote :

This works again after todays update. Last time I updated before that was Jun 26. There were some updates for devicekit. Could have been that.

Guess this can be closed now as I seem to be the only subscriber

Changed in linux (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.