Re: Re: clock messed up
Giuseppe Ghibò <[email protected]> Thu, 13 Jul 2006 22:44:33 +0200
| Newsgroups | gmane.linux.mandrake.cooker.amd64 |
|---|---|
| Message-ID | <[email protected]> |
Thomas Backlund wrote: > Luiz Fernando N. Capitulino wrote: >=20 >> Hi Giuseppe, >> >> On Thu, 13 Jul 2006 12:55:44 +0200 >> Giuseppe Ghib=C3=B2 <[email protected]> wrote: >> >> | Anyone knows a way to fix clock problems which occurs into >> | kernel 2.6.12-22mdksmp (x86-64)? Basically under >> | motherboard MSI K8N Diamond, and MSI K8N Diamond plus >> | (the same happens on three different machines so sound >> | a problem of our kernel), the internal clock is not >> | going to be right (and even trying to sincronize >> | to an external source using NTP is not enough, since >> | the drift happens anyway). The >> | differences between internal clock and right clock >> | goes after one day to 8-10 hours. >> | | I tried to boot the machines specifying on both the option >> | clock=3Dtsc in lilo.conf, but it's not enough. The error >> | between internal clock and official time is always high. >> | | Is there a way to fix this? And why ntp is not enough >> | to keep the time in sync? >> >> You can try two boot options: >> >> enable_timer_pin_1=3D1 >> >> or >> >> disable_timer_pin_1=3D1 >> >> =20 >=20 >=20 >=20 > If IRC nVidia posted a fix for the timer problems they had that none of= =20 > the then known workarounds not fixed completely... > I'll try to dig it up and see... >=20 When you mention nVidia, you mean chipset (e.g. NForce4) or video card? Bye Giuseppe.