boot fails after upgrade to karmic

[Michael Grunert]

was running Xubuntu 9.04 and just upgraded to Xubunut 9.10,
System is an Asus X5DI Laptop with a single disk, root filesystem is encrypted (done with the 9.04 Installeroption)

on final reboot while updating grub is starting, the screen goes blank and is expected to show the password dialog for the hdd but nothing happends.

restarting the system, enter grub menu, choose older kernel (2.6.28-16) .. bootup succeeds ..

as the workaround is not using the failing kernel, i cannot produce tool output concerning the failing package ..

ProblemType: Bug
AlsaDevices:
 total 0
 drwxr-xr-x 2 root root 60 2009-10-29 20:37 by-path
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: amd64
ArecordDevices: arecord: device_list:223: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/sequencer2', '/dev/sequencer', '/dev/seq'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Oct 29 21:03:06 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=48a7d17b-44e8-41f1-b50f-5b1d5f33b4b1
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: ASUSTeK Computer Inc. K50IJ
Package: linux-generic 2.6.31.14.27
ProcCmdLine: root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-16.55-generic
RelatedPackageVersions:
 linux-restricted-modules-2.6.28-16-generic N/A
 linux-backports-modules-2.6.28-16-generic 2.6.28-16.18
 linux-firmware 1.24
RfKill: Can't open RFKILL control device: No such file or directory
SourcePackage: linux-meta
Uname: Linux 2.6.28-16-generic x86_64
dmi.bios.date: 05/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IJ
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.:bvr206:bd05/07/2009:svnASUSTeKComputerInc.:pnK50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K50IJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Leann Ogasawara (leannogasawara)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and set the Status to Confirmed, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.

[Michael Grunert (fadingsun)]

found a fix for this ..

after installing karmic 5-6 times without any success (trying different setups regarding lvm, encryption, ubuntu, xubuntu) i stumbled upon this: http://ubuntuforums.org/showthread.php?t=1204735&page=8

apperently modesetting is not yet ready for primetime with this laptop. I am not sure if this still counts as a linux (kernel), grub2 or X bug .. but it is a serious bug as not even a clean install (instead of an dist upgrade) works ..

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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