can I just switch suse 9.0 to stop messing my real time clock ?
Hi, I've done everything twice to reset drift files and everything else, desribed in several posts. But every now and then Suse changes my cmos real time clock to wrong time - it happens on boot procedure. I have PVR HTPC and all my recordings happen at wrong times... Can I just set Suse not to touch my real time clock ? - I will adjust it manually... Regards, Robert.
On Thursday 15 April 2004 09:36, Robert Rozman wrote:
I will adjust it manually...
~ maybe, this is what screws up /etc/adjtime . . . thus, after adjusting time manually, one should delete /etc/adjtime [ the file will be re-generated overnight, or on next boot ] -- best wishes ____________ sent on Linux ____________
On Wednesday 14 April 2004 22:36, Robert Rozman wrote:
Hi,
I've done everything twice to reset drift files and everything else, desribed in several posts. But every now and then Suse changes my cmos real time clock to wrong time - it happens on boot procedure.
I have PVR HTPC and all my recordings happen at wrong times...
Can I just set Suse not to touch my real time clock ? - I will adjust it manually...
Not much help but this happens to me from time to time as well. I have done everything what was suggested but it still happens. At start up I never know what time will come up. 9 out of 10 it is allright but then it happens. Very annoying, I agree. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
On Thursday 15 April 2004 18:39, Bill Wisse wrote:
At start up I never know what time will come up. 9 out of 10 it is allright but then it happens. Very annoying, I agree.
~ maybe, if before ShutDown one deletes /etc/adjtime then, all will be well :) -- best wishes ____________ sent on Linux ____________
On Thursday 15 April 2004 13:39, Bill Wisse wrote:
On Wednesday 14 April 2004 22:36, Robert Rozman wrote:
Hi,
I've done everything twice to reset drift files and everything else, desribed in several posts. But every now and then Suse changes my cmos real time clock to wrong time - it happens on boot procedure.
I have PVR HTPC and all my recordings happen at wrong times...
Can I just set Suse not to touch my real time clock ? - I will adjust it manually...
Not much help but this happens to me from time to time as well. I have done everything what was suggested but it still happens. At start up I never know what time will come up. 9 out of 10 it is allright but then it happens. Very annoying, I agree.
/bill at 169 west , 19 south.
How is your hardware clock set? YaST, System, Select Time Zone. Local time or UTC? IF you boot to other OS's on this machine it is strongly recommend setting it to local. OR if it is set to UTC switch it to local. I rarely boot to Win2K or Win98SE nowadays but I have to have my machine set to local time to keep it on time. UTC may be OK if all you have is Linux installed but maybe not for your system if all the other suggestions aren't working.
At start up I never know what time will come up. Exactly how my machine behaves when set to UTC.
Stan
On Thursday 15 April 2004 08:44, S.R.Glasoe wrote: Hi Stan
How is your hardware clock set? YaST, System, Select Time Zone. Local time or UTC?
It is set to Local time
IF you boot to other OS's on this machine it is strongly recommend setting it to local.
I only have SuSE.
UTC may be OK if all you have is Linux installed but maybe not for your system if all the other suggestions aren't working.
Are you suggesting I should change to UTC? -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
On Thursday 15 April 2004 16:34, Bill Wisse wrote:
On Thursday 15 April 2004 08:44, S.R.Glasoe wrote:
Hi Stan
How is your hardware clock set? YaST, System, Select Time Zone. Local time or UTC?
It is set to Local time
IF you boot to other OS's on this machine it is strongly recommend setting it to local.
I only have SuSE.
UTC may be OK if all you have is Linux installed but maybe not for your system if all the other suggestions aren't working.
Are you suggesting I should change to UTC?
--
Maybe give it a try. Can't mess up worse than it is already, right? If it still does not keep decent time than those settings are eliminated as a culprit. Remove and reinstall ntp lately? Stan
Bill Wisse wrote:
How is your hardware clock set? YaST, System, Select Time Zone. Local time or UTC?
It is set to Local time
worng
IF you boot to other OS's on this machine it is strongly recommend setting it to local.
I only have SuSE. Are you suggesting I should change to UTC?
The Right Thing (TM) would be to set it to UTC and also set the time zone corectly. Local time is for braindead OS which cannot compute, so if you would have windows and linux on the same machine you would set linux to local time in order to have a useful clock in both operating systems. So, in your case: date --set whatever or better, with an internet connection ntpdate ntp.public.server and then hwclock --systohc --utc However the fact that sometimes, at boot, your clock is way off, might be because of BIOS, motherboard, bad power, whathaveyou, but not Linux. Linux keeps two clocks system clock and hardware clock (in BIOS). At boot, the system clock is set according to the hardware clock. If the later if wrong for some reason, well...
Hi Silviu On Thursday 15 April 2004 19:15, Silviu Marin-Caea wrote:
Bill Wisse wrote:
How is your hardware clock set? YaST, System, Select Time Zone. Local time or UTC?
It is set to Local time
worng
OK. I'll changed it to UTC and see what happens when I start up the box tomorrow morning. I must also mention that this clock problem only started with SuSE 9.0.
The Right Thing (TM) would be to set it to UTC and also set the time zone corectly.
The time zone is set correctly.
date --set whatever or better, with an internet connection ntpdate ntp.public.server and then hwclock --systohc --utc
However the fact that sometimes, at boot, your clock is way off,
Not way off but 12 hours earlier.
Linux keeps two clocks system clock and hardware clock (in BIOS).
At boot, the system clock is set according to the hardware clock. If the later if wrong for some reason, well...
I know that, :-) but...........at shutdown the HW clock gets its time from the system and sometimes I get the message on the screen "Failed". -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."
Bill Wisse wrote:
Not way off but 12 hours earlier.
Would that be the difference between UTC and your local time? With system clock set to UTC, time zone set right, and with "date" showing the right time, do this now: hwclock --systohc --utc and reboot afterwards, to see what happens. If it's all right today, and tomorrow is not, the BIOS, mainboard, bad power are possible causes.
participants (5)
-
Bill Wisse -
pinto -
Robert Rozman -
S.R.Glasoe -
Silviu Marin-Caea