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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
