(hardy)Clock mis-set after install ?

[NoOp]

On 05/23/2008 02:45 AM, xerces8 wrote:
> "Dana J. Laude" wrote:
> 
>> xerces8 wrote:
>> > Hi!
>> > 
>> > (I'm a computer enthusiast for 20 years now, been redhat linux official beta team member for
>> years
>> > and work as a sotware engineer)
>> > 
>> > Yesterday I installed Ubuntu from the hardy-desktop-i386 CD.
>> > 
>> > After that I noticed that the system clock (HW/BIOS clock) is set wrong. It was running correct
>> for
>> > years before ...
>> > 
>> > The system is not networked, neither did I change the time. So ubuntu should have no reason to
>> > assume the BIOS clock is wrong.
>> > 
>> > Any idea what happened ?
>> > Does this sound familiar ?
>> > 
>> > I tried to reproduce this under vmware, but failed. I guess vmware synches the emulated BIOS
>> clock
>> > to the hosts system clock so it obscured the problem (if it happened at all).
>> 
>> Normally, it sets your hardware (ala BIOS) clock to UTC time and then 
>> shows your normal local time on the system clock. (like in kde or gnome)
> 
> Yes, but given this:
>  - BIOS clock has value 03:55
>  - I choose timezone UTC+2 (CET)
> 
> Why would it change the BIOS clock ?
> Why would it assume, that 3:55 is wrong and something else is right ?
> 
> (And it did not change it to 03+2 (or 03-2) but some totally off value.)
> 
> Regards,
> David
> 
> 
> 

David, did you ever figure this out?