I experienced this problem too on Ubuntu karmic installed via WUBI. Behaviour on my system is consistent with comment #47 by
Mark Abene. I was able to boot my system using these commands on the grub shell:
I installed the proposed lupin packaged on my semi-broken system, and now my system won't boot. It takes me to the grub shell like before, but the boot sequence ends with a weird Call Trace and a soft lockup (modprobe:683) after AppArmor profiles are loaded.
I experienced this problem too on Ubuntu karmic installed via WUBI. Behaviour on my system is consistent with comment #47 by
Mark Abene. I was able to boot my system using these commands on the grub shell:
sh:grub>linux /boot/vmlinuz- 2.6.31- 19-generic root=/dev/sda1 loop=/ubuntu/ disks/root. disk ro img-2.6. 31-19-generic
sh:grub>initrd /boot/initrd.
sh:grub>boot
(2.6.31-20 gave the invalid magic number error)
I installed the proposed lupin packaged on my semi-broken system, and now my system won't boot. It takes me to the grub shell like before, but the boot sequence ends with a weird Call Trace and a soft lockup (modprobe:683) after AppArmor profiles are loaded.