Bug#627507: Cannot access the Hardware Clock via any known method.

2011-05-21 Thread jidanni
> "JN" == Jonathan Nieder writes: JN> To be clear, does that mean you had been running 2.6.38-5 before the JN> upgrade, too? Yes. But I was forced to reboot with my backup, $ apt-show-versions|grep linux-image linux-image-2.6-686/unstable uptodate 2.6.38+34 linux-image-2.6.37-2-686 2.6.37-2 in

Bug#627507: Cannot access the Hardware Clock via any known method.

2011-05-21 Thread Jonathan Nieder
jida...@jidanni.org wrote: > Sorry. All I know is I did this upgrade, [... packages that are not linux-image-foo ...] > then rebooted and got those messages. The workaround was to reboot a > second time with 2.6.37-2-686 instead of 2.6.38-2-686, which made none > of those messages. To be clear,

Bug#627507: Cannot access the Hardware Clock via any known method.

2011-05-21 Thread jidanni
> "BB" == Bastian Blank writes: BB> Please specify your problem clearly. Sorry. All I know is I did this upgrade, [UPGRADE] acpid 1:2.0.9-1 -> 1:2.0.10-1 [UPGRADE] binutils 2.21.51.20110421-5 -> 2.21.51.20110421-6 [UPGRADE] grub-common 1.99-3 -> 1.99-4 [UPGRADE] grub-pc 1.99-3 -> 1.99-4 [UPGR

Bug#627507: Cannot access the Hardware Clock via any known method.

2011-05-21 Thread Bastian Blank
On Sat, May 21, 2011 at 06:40:38PM +0800, jida...@jidanni.org wrote: [nothing] Please specify your problem clearly. Bastian -- No one may kill a man. Not for any purpose. It cannot be condoned. -- Kirk, "Spock's Brain", stardate 5431.6 -- To UNSUBSCRIBE, email to debian-ke

Bug#627507: Cannot access the Hardware Clock via any known method.

2011-05-21 Thread jidanni
Package: linux-2.6 Version: 2.6.38-5 Setting the system clock. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Unable to set System Clock to: Sat May 21 10:29:45 UTC 2011 ... ^[[33m(warning).^[[39;49m ^[%@findfs: