Ubuntu :: Big Difference In System And Hardware Clock
Jun 23, 2010
Wrong system clock; Right hardware clock. 'date' and 'hwclock --show' show big differences in time. Hardware clock keeps the correct time, but 'date', the system clock, doesn't (often wrong in a matter of hours). So I'm sure it is the problem of the kernel. I'm tired of synching hardware clock with the system clock all the time. How do I get Ubuntu to use the hardware clock instead of its own in the first place?
I triple boot with XP on the first partition, sidux on the second and third and Ubuntu on the fourth. sidux controls grub2. When I boot into XP or Ubuntu, my clock gets set ahead 4 hours to UTC time (I'm on Eastern daylight time).
Is there a way for all three OSs to display the right time?
Try as I might I cannot seem to get the system clock to display local time. It looks like it's stuck on GMT. In the System>Administration>Time and Date I have my local time zone set correctly and also set to update automatically with an appropriate time server selected. It still displays my local time +5 hours (I'm central time, USA).
I'm completely new to Linux. I'm having the hardest time trying to do the simplest things. I'm using Kopete and I was wondering if I can put the icon on the system taskbar by the clock? I can't drag it there, won't work. I also tried to right click the taskbar and open 'add new items' but Kepete doesn't show on the list.
I restored my .kde directory after changing some stuff unrelated to my clock and now all plasma clocks are exactly 5 hours faster than my system time (the correct time).I've set the time zone for Date&Time in System Settings properly and that's working well and I've ALSO gone into the time zone settings for the plasma widgets and switched between UTC and Local manually but that doesn't do anything.
I've been frustrated with several problems I've been experiencing with Karmic Koala. The one I'll mention in this post is the fact that it randomly decides to adjust the system clock ahead 6 hours. I believe this began happening when I set the location for the system time that displays in the top panel. I'm guessing that the 6 hours is the fact that I'm in the US Central Time zone.
I've set-up dual boot on my laptop. Ubuntu installed first, then Windows 7 so it uses Grub2 to control the booting on start-up. I've noticed that my system clock goes out by an hour on both OS's, I change the clock to correct time & on reboot the time is usually (not always straight away) an hour behind. Has anyone else had this problem & know how to fix it?
While dual-booting Windows and Linux, Linux sets the system time to UTC, so Windows thinks it's midnight near mid-morning. Is there any other way to tell Windows to use UTC? I've seen the registry tweak proposed here and other places. This does not work on my computer (Windows 7 32-bit).For reference, the registry entry is this:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTimeZoneInformation]"RealTimeIsUniversal"=dword:00000001
Today I updated a bunch of packages, rebooted. I run lucid 10.04 x86_64, originally Xubuntu but now gnome since I cannot make xfce4-panel tasklist behave with compiz. Anyway, by the end of the day my clock was 10min off. If I use ntpdate at about 10min intervals I see things like:
$ sudo ntpdate time.xxx.xxx.de 1 Jun 18:37:02 ntpdate[9734]: step time server xxx.xxx.xxx.xxx offset 10.043055 sec
I have deleted /etc/adjtime and touch'd a blank file to no avail.
Is this problem serious? Is it likely software or hardware? Is running an ntp daemon the right solution or would it be masking a new software or hardware problem that appeared today?
the time on system clock given with 'date' command keeps moving forward about 1 minute for every hour of realtime. The box is up all the time so this is not an issue with motherboard battery. An equivalent box with the same hardwre/OS and applications doesn't have the same level of drift. I'm not sure what else this could be.Both boxes are Centos 5.2 64-bit.
I'm using a very simple conky script to diplay the date and time on my desktop. I've noticed that he conky clock is a few seconds early compared to the time displayed in the right hand side of the top panel (Natty). I guess both displays are based on the same "internal" time, so I'm left wondering how this could happen, and how to sync back the clocks.
It seems that Conky is in sync with the system date, while the panel clock is 2 seconds late (on my system). Checked with while true; do date; sleep 0.1; done
on the mac there is a piece of software to change the system clock so it shows the stardate instead of the month, day and year. Is there something like that for Ubuntu? I think it would be pretty cool to have a star trek themed desktop
I have Ubuntu 10.04.1 32bit installed on my flash drive so wherever I go I can have my own mini personal computer, but one problem I'm having is every computer it is run on the next time it's rebooted to the OS on the hard drive it has UTC time instead of the actual time for the timezone you're in that Windows uses. So is their a way I can make Ubuntu not automatically change the clock to what it wants?
I want to set up a web server, and I want to set up NTP so to always keep the clock in sync. I have installed a very basic system (No GUI or X components), to keep it slim and thereby a little less prone to security problems. However, does anybody know what the Synchronize system clock before starting option in system-config-date actually does in terms of changing config files or permissions? I'd like to know so I can do it manually via the commandline.
Generally you can set system clock using [URL]. However, it doesn't supply millisecond precision (it does have nanoseconds, but this isn't working on my system). Is there another way to set system clock, or will I need to write a C program to do it?
I have cron jobs running and the timing is critical, because I'm running Nessus scans on production servers. If I hit them at the wrong time, I'm toast. But when I check the cron log, I see that it is an hour off. Here is the output for the command "clock": Wed 31 Mar 2010 03:01:26 PM CDT -0.257677 seconds
And this is the tail of the cron log: Mar 31 16:00:01 nes-001 CROND[8790]: (root) CMD (/Nessus/Targets/NessusScriptDataCenterScan.test) Mar 31 16:01:02 nes-001 CROND[8822]: (root) CMD (run-parts /etc/cron.hourly) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8822]: starting 0anacron Mar 31 16:01:02 nes-001 anacron[8832]: Anacron started on 2010-03-31 Mar 31 16:01:02 nes-001 anacron[8832]: Normal exit (0 jobs run) Mar 31 16:01:02 nes-001 run-parts(/etc/cron.hourly)[8834]: finished 0anacron
Cron thinks it is 4:00 p.m., but it's really 3:00 p.m. How do I tell Cron what time it is? (Stopping and restarting the crond service did not change it.)
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
I have adjust the clock to my country current time but after a reboot,all the setting is gone. How to permanently setting the correct time?I have select my country region.
I'm setting the hardware clock on RHEL 5.1 system using /sbin/hwclock --systohc. After setting the clock I issue a date command followed by a /sbin/hwclock --show from within a script to get fast resolution and I see that the hardware clock precedes the system time on average by .5 seconds. I would think the clock should be identical after setting.
My server is a VPS which is running with CentOS. I found a wield problem that the system clock always runs faster than the hardware clock. For example, I set system clock and hardware clock both on 20:00. After about half an hour, the system clock will be 20:34/5 which is wrong while the hardware clock remains correct (20:30).
My system clock loses about 10 seconds every minute. The hwclock is fine. I've tried different kernel args (clocksource=acpi_pm, nohz=off, highres=off). None of these have any effect. I am running Fedora 11 with kernel 2.6.30-105.2.23.fc11.x86_64 on an AMD Istanbul node (Processor 2439 SE).
I installed Mythbuntu 9.04 about 9 months to a year ago and (for the most part) I haven't had any problems with mythwelcome, automatic shutdown or the system clock. The "for the most part" relates to the fact that the clock on mythbuntu has always been 4 minutes fast. Then, just last week, the system started acting up - for some reason the system clock changed to 8-10 minutes fast (6 minutes faster than it was previously). To fix this problem, I have tried manually setting the "time and date" setting, and I have also tried setting the "time and date" setting to sync with an internet server. Lastly, I tried changing the system time through the motherboard bios. In each situation, mythwelcome would initially start up with the correct time. Then, several seconds later, the time shown in mythwelcome would change to being 4 minutes fast (as I described above). The time would also be 4 minutes fast when I enter the frontend.
I was willing to live with this, but the weird part is that when I start the system now (assuming I don't have any programs scheduled to record), mythwelcome boots up fine and I see the indication that "MythTV is idel and will shutdown in XXX seconds". Then, it flashes to "MythTV is idle" - like it used to; except now, it doesn't flash back to the countdown for shutting down mythtv. One time when I started the system when I was adjusting the time as mentioned above, I noticed that mythwelcome went to the "MythTV is idle" around the same time it changed the clock to 4 minutes fast - I think there is definitely a correlation here.
I checked out all the settings and nothing else has been changed that would otherwise affect MythTV from shutting itself down. The other interesting part is that I can get the shutdown countdown back if I go to "Utilities / Setup", "Setup", and "Mythbuntu". In the popup screen I choose "MythTV Configuration" and select "Launch MythTV Setup". I get a popup box that says that the mythbackend must be closed (as expected). Then I immediately exit mythtv-setup and the system runs "mythfilldatabase". I exit the Mythbuntu Control Centre and exit the frontend. When I get back to mythwelcome, the shutdown countdown comes back.
I had cloned a centos 5.6 installation from virtualbox virtual machine to physical box. Everything work fine. However, the time showing in os using date command differs from bios time by roughly 4 hours. I am running ntp services which sync the time with another centos server on the network. It appears that some services are using virtual clock and some use physical clock. How do I get rid of virtual clock and only use physical clock?