Ok pinned the last bit of the puzzle down my suspend.... I'm using uswsusp so in /etc/uswsusp.conf I had /dev/sda1 (as that was the correct swap drive)
so when the new kernel installed the and the devices no longer matched the initrd image no longer had uswsusp in it. Therefore correcting uswsusp (/dev/hda1) got suspending working again but of cause it wouldn't resume... Dpkg-reconfigure uswsusp fixes initrd and now only 24 hours after the latest upgrade my system is back to working. my main concern is that the Devs will now 'fix' this latest drive naming change and thus break my system yet again... at least I can fix it quickly now... -- latest kernel(2.6.20-16.28) update gives boot problems https://bugs.launchpad.net/bugs/117314 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
