DragonFly bugs List (threaded) for 2004-08
Re: Problems with clock on 1.1-CURRENT
Organization: Time Warner Cable
Content-Type: text/plain; charset=us-ascii
X-Trace: 1091560145 crater_reader.dragonflybsd.org 206 220.127.116.11
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:1983
Just to bring up this problem again: On my computer where the clock runs
too fast, I had this in my /boot/loader.conf:
I deleted that, and put in:
And the clock ran at a normal speed, for about half an hour. At that point,
I put the vesa_load and etc. lines back in, removed the ACPI line, and
rebooted. After about an hour and a half, the clock had skewed forward
some two (additional) hours.
I deleted the vesa_load and etc. lines again, went back to having
debug.acpi.disabled="acpi" only in loader.conf, and so far (2 hours later),
the clock is still correct.
The only other kernel module used is:
2 1 0xcc5c8000 7000 logo_saver.ko
It looks like having vesa.ko loaded or perhaps ACPI on is what causes it.
Can someone with the too-fast clock problem duplicate this?