From owner-freebsd-current@FreeBSD.ORG Mon May 23 10:35:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 BF58316A41C for ; Mon, 23 May 2005 10:35:18 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id F226443D1D for ; Mon, 23 May 2005 10:35:15 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 23 May 2005 10:35:13 -0000 Received: from h081217095201.dyn.cm.kabsi.at (EHLO localhost.localdomain) [81.217.95.201] by mail.gmx.net (mp021) with SMTP; 23 May 2005 12:35:13 +0200 X-Authenticated: #16703784 From: Stefan Ehmann To: David Gurvich In-Reply-To: <200505222340.27785.david.freebsd@verizon.net> References: <20050518051111.GA33262@Athena.infor.org> <200505210727.23320.david.freebsd@verizon.net> <20050522114524.B27009@carver.gumbysoft.com> <200505222340.27785.david.freebsd@verizon.net> Content-Type: text/plain Date: Mon, 23 May 2005 12:35:13 +0200 Message-Id: <1116844513.1441.19.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org Subject: Re: Newest loader from CVS not working X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 23 May 2005 10:35:18 -0000 On Sun, 2005-05-22 at 23:40 -0400, David Gurvich wrote: > On Sunday 22 May 2005 14:45, Doug White wrote: > > On Sat, 21 May 2005, David Gurvich wrote: > > > New cvsup cycle has not fixed the problem. Might it have anything to do > > > with the fact my freebsd partition is not the first partition? > > > > Unlikely ... are you _sure_ you updated your sources correctly and you're > > booting the fixed loader? > I am sure. I had previously copied the old loader to a backup location and > then copied that to /boot/loader. Then the cvsup, buildworld kernel and > install cycle. The new loader does what all the previous loaders did that > failed to work correctly. It would get to a point where I could either > escape to the #boot prompt and have it use the older loader or go into a > reboot cycle. I am currently using the older loader. Using the older loader > I have had no problems with the system other than KWrite crashing when doing > a search. Same thing here with CPUTYPE=pentium-m on my notebook. I'm using grub as boot loader. As soon as /boot/loader is booted, the machine resets. I've also seen the kwrite search crash - but don't know if this is related. Also, I had a similar problem with grub when I installed some months ago from the ports. I downloaded a newer version from the homepage and installed it manually which just worked fine (I suppose because no cputype/optimization was set when compiling by hand). -- Stefan Ehmann