From owner-freebsd-alpha Sun Oct 10 17:38: 1 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 813581536C for ; Sun, 10 Oct 1999 17:37:51 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id CAA08772; Mon, 11 Oct 1999 02:37:34 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Oct 1999 02:37:25 +0200 (CEST) From: "Erik H. Bakke" To: Don Subject: Re: Timer problems with current on 164SX Cc: freebsd-alpha@FreeBSD.ORG Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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... :) ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message