Date: Mon, 6 Oct 2003 08:01:52 -0400 From: "Ross, Chris" <cross@wcasd.k12.pa.us> To: "Lowell Gilbert" <freebsd-questions-local@be-well.ilk.org> Cc: freebsd-questions@FreeBSD.ORG Subject: RE: Problem booting 5.1 install CD Message-ID: <42918C1908E8A44495BB9695F969ACB81F689D@sabmsx04.wcasd.k12.pa.us>
next in thread | raw e-mail | index | archive | help
Over the weekend I was working on this and found an old 4.7 release CD lying around. I figured that it couldn't hurt to give that a try and see if it would boot. Sure enough 4.7 was fine. From there, I did a cvsup for the current set of 4.8 source files. When the 4.8 kernel was built, I excluded agp and a bunch of other bits from the GENERIC make file. Can't say if the problem exists in the 4.8 tree too. =20 It was my hope that I could get my feet wet on 5.1 before going into real deployment testing. Any deployments would be on newer hardware so this problem may not be that big of an issue in the long run. I'm not happy about the idea of upgrading from 4.8 to 5.1. One of the things that I wanted to look closely at was extended ACLs on UFS2. Upgrading won't allow me to do that. From the "Release Engineering Information" section of the FreeBSD web site, it looks like 6-CURREWNT will be forked when 5.2-RELEASE is out. I would assume that this means there will be little work done on the 4 branch after 4.9 is released. =20 -----Original Message----- From: Lowell Gilbert [mailto:freebsd-questions-local@be-well.ilk.org]=20 Sent: Saturday, October 04, 2003 11:09 AM To: Ross, Chris Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problem booting 5.1 install CD "Ross, Chris" <cross@wcasd.k12.pa.us> writes: > I am having a problem booting the FreeBSD 5.1 install CD. My > machine hangs when it goes to pole agp. Is there a way to disable agp > when booting from this CD? I don't think so. On my laptop, I can't directly install *any* recent releases, since AGP was put into the default kernel. I had to install 4.4 and update to -STABLE from there. Eric Anholt was planning on taking a look at this, but I hadn't heard about any results. I had narrowed it down to something weird in the aperture probe, but I couldn't see any reason for it to actually hang at that specific point. To be honest, I had been pretty sure it was just me, and I didn't have 100% confidence in my hardware anyway.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42918C1908E8A44495BB9695F969ACB81F689D>