From owner-freebsd-alpha@FreeBSD.ORG Tue Aug 31 16:32:06 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10E2716A4CE for ; Tue, 31 Aug 2004 16:32:06 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D23A43D2D for ; Tue, 31 Aug 2004 16:32:05 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i7VGW3ss077904 for ; Tue, 31 Aug 2004 18:32:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: alpha@freebsd.org From: Poul-Henning Kamp Date: Tue, 31 Aug 2004 18:32:03 +0200 Message-ID: <77903.1093969923@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: ok, have kernel, can test. X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2004 16:32:06 -0000 Ok, my 1000 is now able to compile a -current kernel and test-boot it while running the 5.0-RC1 kernel.good I saved. First hurdle is confirmed: hw.eisa_slots must be set to something, 5 works fine. I'm compiling a kernel without fxp now to see if that is the cause of the PCI problem. Ideas and patches are welcome. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.