From owner-freebsd-questions Tue Mar 6 7:16: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from hytronix.com (hytronix.ne.mediaone.net [66.30.96.178]) by hub.freebsd.org (Postfix) with ESMTP id 3998837B718 for ; Tue, 6 Mar 2001 07:16:06 -0800 (PST) (envelope-from john@hytronix.com) Received: from tatewaki (tatewaki.hytronix.com [192.168.1.2]) by hytronix.com (8.11.2/8.11.2) with SMTP id f26FG5U23740 for ; Tue, 6 Mar 2001 10:16:05 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: "John E.P. Hynes" Reply-To: john@hytronix.com Organization: HyTronix To: freebsd-questions@freebsd.org Subject: Alpha PC164 Clock not Y2K Compliant? Date: Tue, 6 Mar 2001 10:16:05 -0500 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01030610160500.11112@tatewaki> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All, I'm new to the list (but I've been using FreeBSD on a number of machines for quite some time.) I recently installed FreeBSD 4.2-RELEASE on an Alpha for the first time (all my other boxes are x86) and I noticed that if I use "date" to set the clock to March 6, 2001, after the next reboot the kernel complains that the clock lost 365 days, and indeed, the time/day is correct, but the year shows up as 2000. Currently, I just run ntpdate before ntpd loads, and all is well. Is there a known Y2K issue with the clock chips on the PC164 Motherboard, or could there be an issue with the way the "date" command updates the hardware clock? -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message