From owner-freebsd-questions@FreeBSD.ORG Thu Mar 18 22:06:55 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C44316A4CE for ; Thu, 18 Mar 2004 22:06:55 -0800 (PST) Received: from pd4mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 051A843D48 for ; Thu, 18 Mar 2004 22:06:55 -0800 (PST) (envelope-from flowers@users.sourceforge.net) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-ser.prod.shaw.ca [10.0.141.178])2003)) with ESMTP id <0HUT00G837NI6N@l-daemon> for questions@freebsd.org; Thu, 18 Mar 2004 23:06:54 -0700 (MST) Received: from pn2ml4so.prod.shaw.ca (pn2ml4so-qfe0.prod.shaw.ca [10.0.121.148]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HUT002KD7NI6L@l-daemon> for questions@freebsd.org; Thu, 18 Mar 2004 23:06:54 -0700 (MST) Received: from sirius (h68-144-47-89.cg.shawcable.net [68.144.47.89]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with SMTP id <0HUT0020G7NHBL@l-daemon> for questions@freebsd.org; Thu, 18 Mar 2004 23:06:53 -0700 (MST) Date: Thu, 18 Mar 2004 23:06:52 -0700 From: Dan MacMillan In-reply-to: <200403191246.46219.satimis@icare.com.hk> To: Stephen Liu , questions@freebsd.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Subject: RE: The clock is running too fast X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2004 06:06:55 -0000 Hola, I had a similar problem on one of the machines at work. Here is a memo I made to myself to remind me of how to fix the problem in the future: The "ACPI-safe" Timecounter does not work (it is way, WAY too fast). To get around this, add the following line to /etc/sysctl.conf: kern.timecounter.hardware=i8254 There are multiple pieces of hardware capable of supplying timing information to the OS. "dmesg | grep Timecounter" should give you a list of all such devices. I think this is an ACPI-related problem, since that is the technology I understand the least at the moment. :) -Dan -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Stephen Liu Sent: March 18, 2004 21:47 To: questions@freebsd.org Subject: The clock is running too fast Hi folks, AMD CUP FreeBSD 5.2 The clock on KDE desktop is running on double speed compelling me to adjust it periodically. Kindly advise how to fix this problem. TIA B.R. Stephen Liu _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"