Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Jan 2003 11:20:45 -0600
From:      Patrick Hartling <patrick@137.org>
To:        freebsd-current@freebsd.org
Subject:   Time keeping problems with 5.0-RELEASE
Message-ID:  <20030123172048.28C3C25@gypsy.vrac.iastate.edu>

Next in thread | Raw E-Mail | Index | Archive | Help
I just updated a 4.7-STABLE system (last rebuilt using sources from
Jan 7, 2003) to 5.0-RELEASE, and now the system clock is going nuts.
I had the same problem when I updated from 3-STABLE to 4-STABLE quite
a while back.  To solve the problem then, I added the following to my
kernel configuration file:

   device apm0 at nexus? disable flags 0x20

For my 5.0 kernel configuration, I have:

   device apm

In /boot/device.hints, I have:

   hint.apm.0.disabled="1"
   hint.apm.0.flags="0x20"

Unfortunately, this isn't working.  Is there something different I need
to do for 5.0?  Looking in NOTES for information about APM, I see a
reference to a sysctl variable kern.timecounter.method, but that doesn't
seem to be a valid oid in 5.0.  I don't think this system (a cheap, old
Cyrix MediaGX-based computer) supports ACPI.  At the very least, ACPI
isn't enabled by default at boot time as it is on my Athlon system.

 -Patrick

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20030123172048.28C3C25>