From owner-freebsd-alpha Tue Oct 12 1:37:28 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 33DDD15089 for ; Tue, 12 Oct 1999 01:37:22 -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 JAA48814; Tue, 12 Oct 1999 09:33:31 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 12 Oct 1999 09:33:31 +0100 (BST) From: Doug Rabson To: "Erik H. Bakke" Cc: Peter Wemm , freebsd-alpha@freebsd.org, Don 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 11-Oct-99 Peter Wemm wrote: > >> > >> 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. > > > I tried to configure a new kernel from a standard GENERIC config file, just > with atapi enabled, but got the same result. > > The PCI-ISA bridge is not probed, and therefore no ISA devices will be attached. > What changes has been done to this part lately, that could affect this? > And, also, is anyone else experiencing this? I haven't heard anyone. Could you boot with 'boot -flags v' so that I can see what devices pci picks up. -- 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