On Thu, Feb 09, 2006 at 03:36:00PM -0500, Chris Howie wrote:
Try booting the kernel with the noapic nolapic parameters.
Thanks Chris, this worked.
I've been monitoring ntp on and off all day and noticed it was having to
step the clock about -6 seconds every 5 to 10 minutes. I also would
never
On Wed, 2006-02-08 at 21:30 -0500, Ken Wahl wrote:
On Wed, Feb 08, 2006 at 07:20:55PM -0600, Ron Johnson wrote:
Nothing hugely wrong with that... Talk to pool.ntp.org every 3 or
4 hours, at a weird odd number of minutes past the hour (since most
people tend to choose :00, :30, etc). That
On Thu, Feb 09, 2006 at 02:57:11AM -0600, Ron Johnson wrote:
Sounds like your mobo is messed up. My old mobo (a Shuttle SK41G)
drifted ~0.05 every 3 hours. My new board (an Abit KV-81), drifts
more than 1/2 a second every 3 hours.
I had considered that at first but my gut still tells me
On Thu, Feb 09, 2006 at 04:18:38AM -0500, Ken Wahl wrote:
On Thu, Feb 09, 2006 at 02:57:11AM -0600, Ron Johnson wrote:
Sounds like your mobo is messed up. My old mobo (a Shuttle SK41G)
drifted ~0.05 every 3 hours. My new board (an Abit KV-81), drifts
more than 1/2 a second every 3 hours.
hendrik writes:
[Chrony} doesn't seem to talk through IP-masquerading.
It does for me (I'm the Chrony maintainer). What is your configuration?
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Jacob S wrote:
After I did an apt-get update/upgrade Monday I've had problem keeping
the time set properly on my computer. I have both ntpdate and
ntp-server installed, running a strictly Sid machine.
Welcome to the club. #debian suggested booting with 'noacpi nolacpi' but that
does nothing.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 8 Feb 2006 19:36:54 -0500
Ken Wahl [EMAIL PROTECTED] wrote:
I've had the same problem for about 6 weeks. I'm not sure but I think
it is bug #342887. Doesn't NTP usually use the system clock as a
fallback?
On Friday 10 February 2006 01:57, Chris Howie wrote:
Jacob S wrote:
After I did an apt-get update/upgrade Monday I've had problem keeping
the time set properly on my computer. I have both ntpdate and
ntp-server installed, running a strictly Sid machine.
Welcome to the club. #debian
Ken Wahl wrote:
I've heard of it but not tried it. I did try the openntp package before
NTP but tossed it for reasons I can't remember. I'm holding out to see
if a fix for bug #342887 corrects things or not. The original bugreport
sounds exactly like the same symptoms I've been having.
Try
Chris Howie wrote:
Jacob S wrote:
After I did an apt-get update/upgrade Monday I've had problem keeping
the time set properly on my computer. I have both ntpdate and
ntp-server installed, running a strictly Sid machine.
Welcome to the club. #debian suggested booting with 'noacpi nolacpi'
On Thursday 09 February 2006 15:37, Chris Howie wrote:
Chris Howie wrote:
Jacob S wrote:
After I did an apt-get update/upgrade Monday I've had problem
keeping the time set properly on my computer. I have both ntpdate
and ntp-server installed, running a strictly Sid machine.
Welcome to the
On Thu, Feb 09, 2006 at 10:52:18AM -0600, John Hasler wrote:
hendrik writes:
[Chrony} doesn't seem to talk through IP-masquerading.
It does for me (I'm the Chrony maintainer). What is your configuration?
Dead, I'm afraid -- I was describing the state of affairs before mu
gateway was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello list,
After I did an apt-get update/upgrade Monday I've had problem keeping
the time set properly on my computer. I have both ntpdate and
ntp-server installed, running a strictly Sid machine.
Originally I thought maybe it was my motherboard
On Wednesday 08 February 2006 05:46 pm, Jacob S wrote:
Hello list,
After I did an apt-get update/upgrade Monday I've had problem keeping
the time set properly on my computer. I have both ntpdate and
ntp-server installed, running a strictly Sid machine.
Originally I thought maybe it was my
I've had the same problem for about 6 weeks. I'm not sure but I think it
is bug #342887. Doesn't NTP usually use the system clock as a fallback?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887
NTP has been pretty much useless and I've had to keep time by calling
ntpdate hourly from cron.
On Wed, 2006-02-08 at 19:36 -0500, Ken Wahl wrote:
I've had the same problem for about 6 weeks. I'm not sure but I think it
is bug #342887. Doesn't NTP usually use the system clock as a fallback?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887
NTP has been pretty much useless and
On Wed, Feb 08, 2006 at 07:20:55PM -0600, Ron Johnson wrote:
Nothing hugely wrong with that... Talk to pool.ntp.org every 3 or
4 hours, at a weird odd number of minutes past the hour (since most
people tend to choose :00, :30, etc). That shouldn't be too bad.
I'm actually pulling it at 51
17 matches
Mail list logo
