From owner-freebsd-alpha Mon Oct 11 2:19:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 556A414C0A for ; Mon, 11 Oct 1999 02:19:43 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA20784; Mon, 11 Oct 1999 10:21:37 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 11 Oct 1999 10:21:37 +0100 (BST) From: Doug Rabson To: "Erik H. Bakke" Cc: Don , freebsd-alpha@freebsd.org Subject: Re: Timer problems with current on 164SX In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 11 Oct 1999, Erik H. Bakke wrote: > > On 10-Oct-99 Don wrote: > >> cia0: Pyxis, pass 1 > >> cia0: extended capabilities: 1 > > > >> # Platform chipsets > >> #controller cia0 > >> #controller apecs0 > >> #controller tsunami0 > >> #controller lca0 > > Dont you need to actually enable a platform chipset? (although I dont see > > why the kernel was picking it up) > > > I was under the impression (seem to recall some messages about it) that the > alpha port now figures out which chipset to use based on the system type > specified in the config file. > Actually, these are gone from the GENERIC file too... > > However, I tried to uncomment the cia0 line, just in case something was screwed > up somewhere, but it did not help. > > I will continue to try... :) It really looks as if the isa bus driver is missing. None of the isa devices are present (and as you have noticed, mcclock is critical). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message