Re: Clock Problem?
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: Tue, 24 Apr 2007 16:06:41 GMT
Will Honea <whonea@xxxxxxxxx> writes:
I DL the ISO for OpenSuSE 10.2 AMD64 to install on a MSI MB, AMD64.
On install, the installation program ask "Date and Time? " Set to PST,
Local, <date> <Time>
O.K., so far.
Install works, a little hitch for the Libzypp problem, all is fine,
except the clock in the KDE Panel shows incorrect time.
I have updated to Linux 184.108.40.206-0.1-default #1 SMP Â x86_64 GNU/Linux
Now, still, in the KDE GUI, bottom right panel, the clock is
incorrectly set. wrong time.
Using Thunderbird to post to a NG, the post failed because "Cannot
Post to Future."
O.K., right-click the clock, > click adjust date & time
Pop up window asks for SU id <suid> [enter]
KDE Control Module opens > the analog clock displays the incorrect
Set the time to the correct time.
Now for the next few minutes the KDE panel Clock displays the correct
Open an other window, open a konsole shell type a command # uname -a
In ten minutes the Clock is off by 10 minutes. that is, I set the
clock at 18:40 (6:40pm) and at 18:50 the KDE panel clock reads 7pm
If you think information on my hardware may be of interest I will be
happy to provide.
Just for grins, go to your BIOS setup on boot and set the clock. Let it run
for 10-15 minutes just as you did here. You could have a bum clock in
hardware in which case nothing is going to help. Another real possibility
is the backup battery - if you have one on the motherboard - which will
cause all sorts of screwy things if it is really weak. Even with system
power available, I've had those things go really weird with bad batteries.
No, it SHOULD have noting to do with the battery. That will determine the
RTC which is not in use while the computer is running at all.
This is a problem with the onboard clock. It is as if the system thinks it
is running at 150Hz or 200 Hz and it is really running at 100 Hz.--
Except that 150-200 Hz is not a "usual " multipier. As I understand it, the
computer has two clocks-- the timer tick which comes off the timer chip on
the motherboard, and the CPU cycle clock. It is the time interrupt which
sets the gross clock, but the time routines in Linux use that together with
the cpu counters to give micro second accuracy to the system clock.
Now, it the kernel thought that the timer interrupts were occuring at 100Hz
and they were really occuring at 200 Hz, then at each interrupt twice as
much time would be added to the time as should be.
But 2 1/2 times would be more likely (Ie system running at 256Hz rather
than 100Hz) rather than just 1 1/2 times.
- Prev by Date: Re: Clock Problem?
- Next by Date: Re: Clock Problem?
- Previous by thread: Re: Clock Problem?
- Next by thread: Re: Clock Problem?