From owner-freebsd-stable Fri Jul 14 7:20:39 2000 Delivered-To: freebsd-stable@freebsd.org Received: from rothko.bestweb.net (rothko.bestweb.net [209.94.100.160]) by hub.freebsd.org (Postfix) with ESMTP id 44C9137C6C1; Fri, 14 Jul 2000 07:20:33 -0700 (PDT) (envelope-from kmg@bestweb.net) Received: from Barbarossa (dialin-21.poughkeepsie.bestweb.net [216.179.15.52]) by rothko.bestweb.net (8.9.1a/8.9.3) with SMTP id KAA13970; Fri, 14 Jul 2000 10:20:12 -0400 (EDT) From: Kevin Reply-To: kmg@bestweb.net To: so@server.i-clue.de, Christoph Sold , "Daniel C. Sobral" Subject: Re: Stable does not boot after make buildworld, ... Was: HEADS UP! Always use the 'make buildkernel' target to make yerkernels Date: Fri, 14 Jul 2000 15:17:10 -0400 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: so@server.ms-agentur.de, Kris Kennaway , stable@FreeBSD.ORG References: <396C6848.A4907221@newsguy.com> <396F18CC.6EB2304D@i-clue.de> In-Reply-To: <396F18CC.6EB2304D@i-clue.de> MIME-Version: 1.0 Message-Id: <00071415190500.00593@Barbarossa> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 14 Jul 2000, Christoph Sold wrote: > A-Ha! Now we get closer to the problem... read on, suggestions follow... > > "Daniel C. Sobral" wrote: > > > > Christoph Sold wrote: > > > > > > > Summary of Officially Sanctioned Update Procedure: > > > > > > > > make buildworld > > > > make buildkernel > > > > make installkernel > > > > shutdown (drop into single-user mode) > > > > make installworld > > > > mergemaster > > > > reboot > > > > > > > > Depart from the above procedure at your own risk. Thankyou :-) > > > > > > Been there, done that, to the last letter ('kay, I didn't type the > > > "(drop into single-user..." part). Fresh install from 4.0-Release, > > > CVSup'ed after the binutils were declared clean. The system panics when > > > loading linux.ko. > > > > > > It seems to me there is something not working as intended. > > > > > > Can any helpful soul look at the stable build sequence shown and > > > determine why it crashes during loading linux.ko? > > > > Yes. After the above procedure, your new kernel will be installed under > > a different name, equal to the name of the kernel configuration file. > > When booting, the old /kernel will get loaded, and that one is > > incompatible with your newer modules. > > > > There are two ways around this: > > > > 1) Edit /boot/loader.conf and add the line kernel="XYZZY", where XYZZY > > is the name of your kernel. > > 2) See LINT (it's still LINT on -stable, right? :) for an option that > > let you override the name, so that XYZZY will install kernels named > > "kernel" again. > > As I have written: I have followed this procedure to the point. An 'lo, > there was a kernel named (SURPRISE) GENERIC shamelessly sitting around > at root. > > Can we safely > > a) assume when building the default (GENERIC) kernel it should be > installed automagically so it boots automatically, and, if possible, > move the old kernel to kernel.old automagically? > > b) make the build process so following the instructions to the point > leads to a running system, automagically, > or, alternatively > change the build instructions to show the pitfalls more prominently? > > IMHO, when big changes like aout-elf, or, recently, new tool chain tools > make changes to the build process unavoidable, /prominent/ hints for > stupid stable-only-readers like me should be placed everywhere*) -- in > case of aout->elf, I was warned, so that went through. This time I > plainly missed the warnings. > > Just my .05 Euro > -Christoph Sold Read /usr/src/UPDATING for information on how to compile and install a new kernel. -Kevin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message