From owner-freebsd-current@FreeBSD.ORG Wed Apr 20 04:06:01 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D80816A4CE for ; Wed, 20 Apr 2005 04:06:01 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5254043D1D for ; Wed, 20 Apr 2005 04:06:01 +0000 (GMT) (envelope-from gartrend@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])j3K43kbM030359 for ; Tue, 19 Apr 2005 23:03:46 -0500 (CDT) (envelope-from gartrend@area51.capnet.state.tx.us) Received: from localhost (gartrend@localhost)j3K43kD4030356 for ; Tue, 19 Apr 2005 23:03:46 -0500 (CDT) Date: Tue, 19 Apr 2005 23:03:46 -0500 (CDT) From: marek gartrend To: freebsd-current@freebsd.org Message-ID: <20050419224935.G30305@area51.capnet.state.tx.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: FreeBSD 5.4 RC3 failure on Gateway ALR 7200R. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2005 04:06:01 -0000 I tried to load 5.4-RC3 (please redirect me to the correct list if this isn't the one) on a Gateway ALR 7200R, dual processor 400MHz Pentium II. The normal boot from the CD would not boot, stopping at the agp0: line. I booted to safe mode and installed from there. When I boot it stops at: agp0: at device 1.0 on pci0 in safe bood mode, the next line is: pcib1: at device 1.0 on pci0 If I boot with extra logging, it ends with: agp0: at device 1.0 on pci0 agp0: Lazy allocation of 0x4000000 bytes rid 0x10 type 3 at 0 agp0: allocating GATT for aperture size of 64M [nothing more] I tried setting ACPI off (cause it was the only thing I know how to do) with: hint.acpi.0.disabled="1" in loader.conf (I also tried putting it in device.hints) but that made no difference. Is this machine a no-go? garth