From owner-freebsd-alpha Sun Oct 10 22:18:24 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 448A114D27 for ; Sun, 10 Oct 1999 22:18:17 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id C38DD1CC8; Mon, 11 Oct 1999 13:18:14 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: "Erik H. Bakke" Cc: Don , freebsd-alpha@FreeBSD.ORG Subject: Re: Timer problems with current on 164SX In-reply-to: Your message of "Mon, 11 Oct 1999 02:37:25 +0200." Date: Mon, 11 Oct 1999 13:18:14 +0800 From: Peter Wemm Message-Id: <19991011051814.C38DD1CC8@overcee.netplex.com.au> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "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 screw ed > up somewhere, but it did not help. > > I will continue to try... :) Make sure you've got the right DEC_* platform options enabled. Of course, if you have them all, then you get all the chipsets anyway. You should at least have DEC_EB164 for the PC164SX, which is what I have here. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message