Running 'sudo date -s @0' and then rebooting certainly seems to produce a thoroughly confused hardware clock for a couple of reboots. I wonder if this is a useful starting point.
One thought I have is that we could use /etc/adjtime very early in the boot process (although probably not in the initramfs, or we'd have to update it at every boot) to try to make sure that the hardware clock is at least somewhat sane. It might take a couple of boots to stabilise after installation, but that's better than nothing. -- Edgy Beta -- fsck on every (re)boot https://launchpad.net/bugs/63175 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
