From owner-freebsd-questions@FreeBSD.ORG Tue Oct 7 07:31:50 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E4D916A4B3 for ; Tue, 7 Oct 2003 07:31:50 -0700 (PDT) Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8845F43FEC for ; Tue, 7 Oct 2003 07:31:46 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 02DA03AB7; Tue, 7 Oct 2003 10:31:46 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Ewald Jenisch References: <3F815EA2.20403@jenisch.at> From: Lowell Gilbert Date: 07 Oct 2003 10:31:45 -0400 In-Reply-To: <3F815EA2.20403@jenisch.at> Message-ID: <44llrxktke.fsf@be-well.ilk.org> Lines: 45 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-questions@freebsd.org Subject: Re: Upgrading 5.1 to latest -> crash upon starting X X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2003 14:31:50 -0000 Ewald Jenisch writes: > Seems like I'm running into a problem upgrading my 5.1 machine to the > latest level: If you're going to run -CURRENT, you really do have to follow the -CURRENT mailing list. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html > The symptoms: When I boot the new kernel everything runs straight up > to the moment when I start X-Windows. When starting X as a normal user > I end up with a "db"-prompt (debugger?); when starting X as root the > screen goes blank and after some seconds the box reboots. Yep, sounds pretty serious. > As far as building & installing is concerned I did everything as per > chapter 21 of "the handbook", including installing binaries (userland) > in single-user mode, running mergemaster etc.etc. No, you are supposed do the installworld under the *new* kernel, so that if the kernel fails to boot, you don't end up with the new binaries unless the matching kernel works as well. > BTW, when booting the old kernel (kernel.old) everything is fine again > - > so assume the problem is with the kernel itself. Right. > Has anybody else seen this? What can I do against it? I don't think I've seen anything like this on the -CURRENT list, so it doesn't seem to be a general problem. cvsup your sources again, and do another round of updates. Just make sure you save the working kernel somewhere safe (kernel.old will be overwritten next time you do an installkernel). make buildworld make buildkernel make installkernel shutdown -r now and *then* do the make installworld. And subscribe to freebsd-current@freebsd.org.