Thank you Carlos. Someone could say where I could head for discussing this issue with kernel experts, please? The hardware clock works ok under MS-DOS and NT 4. hwclock always shows a compatible time; each CMOS second lasting one wall clock second. Couldn't use xntpd because it dies when the clock wents insane; wouldn't use it without a local clock (internal) anyways. Thanks, Antonio -----Mensagem original----- De: Carlos E. R. [mailto:robin1.listas@tiscali.es] Enviada em: terça-feira, 12 de novembro de 2002 22:37 Para: 'suse-linux-e@suse.com' Assunto: Re: [SLE] PC/Intel clock The 02.11.12 at 13:49, Antônio L. F. Cruz wrote:
I have a dual-Pentium II 400MHz machine that show this strange behaviour: the clock runs much faster than it should, about 3 or 4 times the real time. This happens only under Linux; under "that other OS", version 4.0 didn't happens.
I have no idea, but you could try deleting /etc/adjtime, and then set both system and hardware clocks to the same time. That would work if the system is wrongly triying to adjust the time. I also understand the ntp daemon can be used to tune the clock, making it run faster or slower: maybe it is wrong. I suppose that behaviour can be reset. -- Cheers, Carlos Robinson -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
The 02.11.13 at 11:03, Antônio L. F. Cruz wrote:
Thank you Carlos.
Welcome :-)
Someone could say where I could head for discussing this issue with kernel experts, please?
Don't look at me :-)
The hardware clock works ok under MS-DOS and NT 4.
I think there is a good discussion of that in the xntp docs, or perhaps in a howto. Windows keeps both clocks continously sinchronized, whereas linux leaves the hardware (cmos) clock alone.
hwclock always shows a compatible time; each CMOS second lasting one wall clock second.
Makes sense, it agrees with what I said above :-)
Couldn't use xntpd because it dies when the clock wents insane; wouldn't use it without a local clock (internal) anyways.
Too bad. I understand the kernel clock can be adjusted to go faster or slower and so be more precise (man adjtimex), and for that the file /etc/adjtime is used. So, if there is something wrong there, deleting it would the trick. If it something else, well... then you need help from somebody that really knows :-) Perhaps, till you find the real solution, you could use a cronjob adjusting the time from cmos to system. Also, do a search of "clock" and "time" in the sdb, there are some articles. -- Cheers, Carlos Robinson
participants (2)
-
Antônio L. F. Cruz -
Carlos E. R.