Can it really be so difficult to set the time??

  • johne53
Posted: Mon, 03/30/2009 - 09:38
Yesterday I booted into 64studio (I'm still running Version 2.2) and because daylight savings time had changed, 64studio added 1 hour to my desktop clock. Unfortunately, Windows XP (which is on a different partition) had already made the adjustment so my clock was now showing 11 o'clock when the actual time was 10 o'clock. I've tried opening 64studio's clock and resetting the time (and initially, it seems to work) but each time I reboot, the time always comes up an hour late. For whatever reason, setting the desktop clock doesn't seem to be setting the hardware clock. I don't think any external synchronisation is involved because because when I try to set my clock for automatic synchronisation it displays a message box saying that NTP support is not installed. Also, I can't find any setting to tell it to "stop adding a 'daylight savings' hour to the time". Any ideas how I can fix this problem?

Time set...

  • Quentin Harley
  • 05/24/07
  • Tue, 03/31/2009 - 17:45
It is working fine in 3.0 betas at the moment... I have yet to see any bad side effects on my systems running 3.0, but we keep testing ;-) Ho hum indeed

For a minute I thought you

  • johne53
  • 10/07/07
  • Tue, 03/31/2009 - 16:46
For a minute I thought you might be onto something Quentin. I did forget to check that both Windows installations were set to GMT but in fact, they are. I've been experimenting for most of this afternoon but AFAICT 64studio no longer has any affect on my mobo's hardware clock. It can read the time but cannot write it. I even tried logging in as root and setting the time from a command prompt (using the 'date' command). Everything works fine as long as the laptop remains powered up - but after a reboot, the time is always 1 hour fast again. There's one major difference between my dekstop and laptop PC's. Some time ago I had a problem on the laptop whereby any attempt to set the time would cause weird screen blackouts. I wrote about this here:- I ended up by updating a lot of stuff and at first it seemed as if the problem was fixed. Only now have I realised that setting the time no longer works. It gives the appearance of working but that's only a temporary effect.... :-( Ho hum....


  • Quentin Harley
  • 05/24/07
  • Tue, 03/31/2009 - 15:06
It seems that your desktop PC master clock (11:40:21) is correctly set th UTC = GMT. The laptop is not. Windows in the laptop is set to use system clock as local time in stead of calculating correct local time from UTC. I had the same on my laptop, and fixed it this way. So... Set the hardware clock to UTC, and change your windows setup to reflect the local time from UTC. 64 studio time should now be ok.

Thanks guys.First Dave, I

  • johne53
  • 10/07/07
  • Tue, 03/31/2009 - 11:52
Thanks guys. First Dave, I checked my settings and they seem to be correct. In fact, I have the same settings on my desktop PC but that isn't showing this problem (it's only happening with my laptop PC). Youki - First, I ran tzconfig on both machines which confirmed that they are both set to Europe / London. Then I ran dpkg-reconfigure tzdata on my destop PC (the one that's working fine) and it gave me this output:- Local time is now: Tue Mar 31 12:40:21 BST 2009. Universal Time is now: Tue Mar 31 11:40:21 UTC 2009. Run 'tzconfig' if you wish to change it A few seconds later I did the same thing on my laptop PC and got this output:- Local time is now: Tue Mar 31 13:41:01 BST 2009. Universal Time is now: Tue Mar 31 12:41:01 UTC 2009. Run 'tzconfig' if you wish to change it. Note that Universal Time (wherever that comes from) is an hour late. If Universal Time is simply the time of my hardware clock, then that could explain the problem. However, Windows is set up the same on both machines and is showing the correct time on both of them. Looks like I'll just have to live with this.... :-(

date & /etc/environment

  • skullnotions
  • 09/29/07
  • Tue, 03/31/2009 - 10:32
sudo date month-day-present\time e.g. I've just run: $ sudo date 03311100 or look to /etc/environment $ sudo gedit /etc/environment Add your locales e.g. LANGUAGE ="en_GB.UTF-8" LANG="en_GB.UTF-8" LC_ALL="en_GB.UTF-8" You will have to reboot for the environment setting to be accepted. Check with: $ date $ locale Cheers! Dave.

Did you try a

  • youki
  • 12/29/07
  • Tue, 03/31/2009 - 09:43
Did you try a dpkg-reconfigure tzdata ?

Groan.... why does nothing

  • johne53
  • 10/07/07
  • Tue, 03/31/2009 - 09:34
Groan.... why does nothing ever seem to work properly under Linux?? Your suggestion seemed pretty sensible Quentin so this morning, I opened 64studio and tried selecting one of the other European time zones to see if I could find a zone that is 1 hour earlier than London. No matter what I did, the time remained consistently 1 hour late. So eventually, I selected a time zone in North America (just to be certain that it would be different) but the time still showed 1 hour late. Eventually i gave up and just reset it back to london. Guess what..? The time now suddenly changed and became 3 hours late!! I then tried to set the actual time correctly - but this time it jumped again and became 3 hours early!! Fortunately (in this case) I seem to have a secondary problem which is that 64studio isn't managing to set the mobo's hardware clock - so after a reboot I was luckily back to where I started at 1 hour late. That seems to be the best I can achieve. My guess is that there's probably a config file somewhere that's telling 64studio to add an hour to the time in summer time. Do you happen to know if any such config file exists? John


  • Quentin Harley
  • 05/24/07
  • Mon, 03/30/2009 - 14:51
Set the system clock to GMT and let windows and 64 studio use your localisation to set the time correctly. I set my laptop up like this (Dayjob forces windows...)