From owner-freebsd-hackers  Fri Dec 20 12:44:59 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id MAA07462
          for hackers-outgoing; Fri, 20 Dec 1996 12:44:59 -0800 (PST)
Received: from korin.warman.org.pl (korin.warman.org.pl [148.81.160.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA07391
          for <freebsd-hackers@FreeBSD.ORG>; Fri, 20 Dec 1996 12:44:07 -0800 (PST)
Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.3/8.7.3) with SMTP id VAA09204; Fri, 20 Dec 1996 21:43:27 +0100 (MET)
Date: Fri, 20 Dec 1996 21:43:27 +0100 (MET)
From: Andrzej Bialecki <abial@korin.warman.org.pl>
To: Bruce Evans <bde@zeta.org.au>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: 2.2-ALPHA hangs while calibrating clocks...
In-Reply-To: <199612181100.WAA31169@godzilla.zeta.org.au>
Message-ID: <Pine.NEB.3.95.961220214108.9185D-100000@korin.warman.org.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 18 Dec 1996, Bruce Evans wrote:

> >I'm trying to install FreeBSD 2.2-ALPHA on my machine. Here is
> >configuration:
> >
> >* MB SOYO Intel Triton HX, Pentium 120MHz, BIOS Award
> >* 64MB RAM EDO, pipeline burst cache 512k
> >* HDD IDE WDC32100 (2.1 GB) LBA mode 4, floppy drive etc...
> >* 3c509 ISA ethernet adapter (ep0)
> >
> >The kernel is, of course, GENERIC 2.2-ALPHA.
> >
> >So, the installation itself goes well (although I used 2.1.6 install
> >floppy), and then, after rebooting with newly installed system, it hangs
> >almost forever (at least for 15 minutes :-) ) saying:
> >
> >Calibrating clock(s) relative to mc146818A clock...
> >
> >and then says it failed.
> >
> >So my question is: do I have a broken motherboard? Are there any options
> >in kernel config that I should change in order to avoid this looong
> >waiting? 
> 
> The RTC seems to be broken after the reboot.  The calibration routine
> just waits for the seconds counter to change twice.  It apparently didn't
> change for 15 minutes.  There is a generous timeout of 100 million reads
> of the seconds counter to give it a chance to change.  Change it to 1
> million (in clock.c).
> 
> Bruce
> 

Thank you for your advice - I did so, and the problem is less frustrating
- though I think I'll complain to the seller of the motherboard. Thanks.

Andy,

+-------------------------------------------------------------------------+
Andrzej Bialecki <abial@warman.org.pl>    _)    _)   _)_)   _)_)_) _)  _)
---------------------------------------   _)_)  _) _)    _) _)_)   _)_)
Research and Academic Network in Poland   _)  _)_) _)_)_)_)     _) _) _)
Bartycka 18, 00-716 Warsaw, Poland        _)    _) _)    _) _)_)_) _)  _)
+-------------------------------------------------------------------------+