I've been having this problem too on my Acer aoa110 (using UNR 9.10)
After a few days of using karmic and getting frustrated with the ~1:45 boot times (from grub to desktop) along with the panel configuration problems, I tried to use a PPA kernel (comment #20 in http://bugs.launchpad.net/ubuntu/karmic/+source/sreadahead/+bug/432089), which bricked my netbook. After trying unsuccessfully several times to reinstall karmic by using sysresccd for gparted (wasn't trusting karmic at this point), and doing a testdisk I noticed there was a read error at cylinder 257, along with an intermittent read-error at sector 1.
I gave up and did a wipe of the drive (not using dd. wipe. took about six hours).
Read-error went away, partitioning worked fine, karmic finally installed, but no change to boot times.
Gah!
I'm going back to jaunty until 10.04 comes out. Which is a shame, because I like the new UI in karmic, but I've decided not to risk my ssd for eye candy.
I've been having this problem too on my Acer aoa110 (using UNR 9.10) bugs.launchpad. net/ubuntu/ karmic/ +source/ sreadahead/ +bug/432089), which bricked my netbook. After trying unsuccessfully several times to reinstall karmic by using sysresccd for gparted (wasn't trusting karmic at this point), and doing a testdisk I noticed there was a read error at cylinder 257, along with an intermittent read-error at sector 1.
After a few days of using karmic and getting frustrated with the ~1:45 boot times (from grub to desktop) along with the panel configuration problems, I tried to use a PPA kernel (comment #20 in http://
I gave up and did a wipe of the drive (not using dd. wipe. took about six hours).
Read-error went away, partitioning worked fine, karmic finally installed, but no change to boot times.
Gah!
I'm going back to jaunty until 10.04 comes out. Which is a shame, because I like the new UI in karmic, but I've decided not to risk my ssd for eye candy.