From owner-freebsd-alpha@FreeBSD.ORG Sat Apr 2 17:49:58 2005 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD9E516A4CE for ; Sat, 2 Apr 2005 17:49:58 +0000 (GMT) Received: from alpha.prismequine.com (ns1.prismequine.com [199.120.78.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF59043D4C for ; Sat, 2 Apr 2005 17:49:57 +0000 (GMT) (envelope-from kylea@prismequine.com) Received: from [192.168.1.129] ([192.168.1.1]) (authenticated bits=0) by alpha.prismequine.com (8.12.11/8.12.6) with ESMTP id j32GT9Kl068595 for ; Sat, 2 Apr 2005 10:29:09 -0600 (CST) (envelope-from kylea@prismequine.com) User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Sat, 02 Apr 2005 11:49:54 -0600 From: "Kyle S. Allender" To: Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Subject: Digital Server 3300 hardware clock X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Apr 2005 17:49:58 -0000 I'm having a problem with FreeBSD 5.0-RELEASE on a Digital Server 3300 (or at least I think it's a 3300). I converted this from an NT 4 server machine almost 3 years ago and it's been running fine under 4.x/5.x for a very long time. However, one issue I've continually had with this machine is that the hardware clock is off by almost 2 hours. Ntpd can't keep the correct time because the hardware clock is too far off. I've tried various things, but for the life of me can't remember how to get back to the correct console to reset the clock time. Can someone out there on the list help me get this fixed? I'd like to move to 5.3 for this system, but want the clock fixed first (it's driving me batty). Any asisstance is greatly appreciated. Thanx. -- Kyle Allender