Le lundi 18 avril 2005 à 23:21 +0200, Richard Fish a écrit :
> Frédéric Grosshans wrote:
>
> >I'll choose the simpler cronjob solution, thanks. Anyway, isn't that a
> >kernel bug ? How sould I report this ?
> >
> >
>
> Well, from googling around, it seems that a few seconds per day of drift
> b
Frédéric Grosshans wrote:
>I'll choose the simpler cronjob solution, thanks. Anyway, isn't that a
>kernel bug ? How sould I report this ?
>
>
Well, from googling around, it seems that a few seconds per day of drift
between the system clock and hardware clock is considered perfectly
normal, and
Le samedi 16 avril 2005 à 08:43 +0200, Dirk Raeder a écrit :
> Frédéric Grosshans wrote:
> > Le vendredi 15 avril 2005 à 13:51 +0200, Dirk Raeder a écrit :
> >>do you have a CPU that can modulate its frequency?
>
> > I don't think so (it's not a laptop). How do I check that ?
> >>In that case, a
Le vendredi 15 avril 2005 à 20:15 +0200, Richard Fish a écrit :
> F
>
> Assuming I understand the probelm correctly, that is that the bios clock
> keeps correct time, but the linux system time drifts,
Exacly,
> you could try
> using the clock= kernel parameter, which specifies what timesource t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frédéric Grosshans wrote:
> Le vendredi 15 avril 2005 à 13:51 +0200, Dirk Raeder a écrit :
>
>
>>do you have a CPU that can modulate its frequency? IE clock down if there is
>>low load and clock up if there is high load?
>
>
> I don't think so (it'
Frédéric Grosshans wrote:
>Le vendredi 15 avril 2005 à 20:16 +0800, William Kenworthy a écrit :
>
>
>>also worth trying: stop ntp or whatever time sync program you are using,
>>then delete /etc/adjtime and /etc/ntp.drift (or whatever the drift is)
>>Then run ntp, leaving it to run for a few hour
Le vendredi 15 avril 2005 à 20:16 +0800, William Kenworthy a écrit :
> also worth trying: stop ntp or whatever time sync program you are using,
> then delete /etc/adjtime and /etc/ntp.drift (or whatever the drift is)
> Then run ntp, leaving it to run for a few hours so it will write correct
> drift
Le vendredi 15 avril 2005 à 13:51 +0200, Dirk Raeder a écrit :
> do you have a CPU that can modulate its frequency? IE clock down if there is
> low load and clock up if there is high load?
I don't think so (it's not a laptop). How do I check that ?
> In that case, activate HPET (high precision t
also worth trying: stop ntp or whatever time sync program you are using,
then delete /etc/adjtime and /etc/ntp.drift (or whatever the drift is)
Then run ntp, leaving it to run for a few hours so it will write correct
drift and adjustment values.
BilkK
On Fri, 2005-04-15 at 13:51 +0200, Dirk Ra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frédéric Grosshans wrote:
> The sytem time of my computer drifts by roughly 5 min per day, while the
> hwclock stays at the correct time.
>
> Anyone knows how to avoid this ?
>
> (My kernel is a 2.6.11-r6 gentoo-sources kernel, if that can help)
>
>
The sytem time of my computer drifts by roughly 5 min per day, while the
hwclock stays at the correct time.
Anyone knows how to avoid this ?
(My kernel is a 2.6.11-r6 gentoo-sources kernel, if that can help)
Fred
--
Frédéric Grosshans <[EMAIL PROTECTED]>
--
gentoo-user@gentoo.o
11 matches
Mail list logo
