From owner-freebsd-hardware@FreeBSD.ORG Fri Mar 12 05:51:32 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4588016A4CE for ; Fri, 12 Mar 2004 05:51:32 -0800 (PST) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDB5B43D4C for ; Fri, 12 Mar 2004 05:51:31 -0800 (PST) (envelope-from lgusenet@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc11) with ESMTP id <2004031213512701100ghbtme>; Fri, 12 Mar 2004 13:51:31 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 37B7C12; Fri, 12 Mar 2004 08:51:27 -0500 (EST) Sender: lowell@be-well.ilk.org To: lukas@razik.de References: <4050B593.3628.237BFC@localhost> From: Lowell Gilbert Date: 12 Mar 2004 08:51:27 -0500 In-Reply-To: <4050B593.3628.237BFC@localhost> Message-ID: <44ad2mnpgg.fsf@be-well.ilk.org> Lines: 37 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hardware@freebsd.org Subject: Re: 5.2.1-RELEASE hangs after 'agp0: mem 0-0x7ffffff at device 0.0 on pci0' X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Mar 2004 13:51:32 -0000 lukas@razik.de writes: > My system (laptop): > CPU: P4 3.06GHz (HT enabled) > Chipset: Intel 82865G/PE/P, 828485P DRAM Controller > Graphic adapter: GF FX Go5350 > > > Hi!!! > > If I try to boot from the '5.2.1-RELEASE-i386-miniinst.iso' the kernel hangs after outputting this message (with > verbose logging): > agp0: mem 0-0x7ffffff at device 0.0 on pci0 > agp0: allocating GATT for aperture of size 128M > > Is there a way to start the kernel without AGP support? No. This is something of a problem, because some AGP implementations (including the one on my laptop) will lock up or crash during the AGP probe. In my case, I confirmed that the AGP device was definitely flaky, because the CPU locked up on a simple register read. I corresponded a bit with FreeBSD's main AGP developer, but we didn't get much of anywhere. I documented the problems in my system at http://be-well.ilk.org:8088/systuff/laptop-problems.html One thing you can do is start the install from floppies, which have a more minimal kernel, without AGP. If that ever changes, some of us will have a real problem. I don't really understand why AGP should be in the GENERIC kernel, anyway, since it loads fine as a module, but I don't want to make too much of a fuss. After all, I *did* get my system going, albeit through a procedure that's clearly too much to expect of a first-time user. > I had the same problem with NetBSD 1.6.2 but after disabling APM and AGP all works fine... Try disabling ACPI on FreeBSD 5.2.1. That may leave your AGP chip a little less confused...