Thanks to everyone for all the replies, very useful. I was unclear about the difference between ntpdate and ntpd. Kernel version on the problematic machine was up to date. I have altered the installation source to include the nvidia drivers, checked for all updates, turned off the IPCop box announcing the time service to the network and adjusted /etc/ntp.conf accordingly, and adding in a couple of .nz time servers. I have also checked bios options re fan speeds and turned off the Cool n Quiet and Q-fan options on this Asus board.
I'll see what date shows me tomorrow. Google tells me that some people have resolved this issue by appending "noapic acpi=off" to grub. If I am still getting nowhere then I believe having cron do "service ntp stop && service ntp start" for me a few times an hour will work. Cheers, Roger Volker Kuhlmann wrote: > On Mon 17 Sep 2007 16:41:06 NZST +1200, Robert Fisher wrote: > > >> I just use the KDE setup these days and it seems to work for me. >> >> Right click the KDE clock and select "adjust date and time" >> >> Tick "set time and date automatically" and choose a server >> (I use ntp.massey.ac.nz) >> > > Hmmm. > > Ok, this method probably does the equivalent of running ntpdate at > regular intervals, and doesn't run ntpd at all. There's nothing wrong > with that if that's what you want, but it's obviously mutually exclusive > with running ntpd. ntpdate refuses to set the time while ntpd is running > btw, and for very good reason. > > If you do want to run ntpd, use your distro's provided method to set > this up. Ok if that is KDE, but on SUSE, setting up anything with KDE > that can be set up with yast is almost always a very bad idea(TM). > > Volker > >
