From owner-freebsd-questions Fri Jul 9 5:29:30 1999 Delivered-To: freebsd-questions@freebsd.org Received: from europe.std.com (europe-e.std.com [192.74.137.10]) by hub.freebsd.org (Postfix) with ESMTP id B4EFD14DA6 for ; Fri, 9 Jul 1999 05:29:19 -0700 (PDT) (envelope-from lowell@world.std.com) Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0) id IAA20767; Fri, 9 Jul 1999 08:29:09 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA16662; Fri, 9 Jul 1999 08:29:09 -0400 To: Tim Hirst Cc: freebsd-questions@freebsd.org Subject: Re: Kernel Compile Problems References: <37852DDA.926E4A81@hiverworld.com> From: Lowell Gilbert Date: 09 Jul 1999 08:29:09 -0400 In-Reply-To: Tim Hirst's message of Thu, 08 Jul 1999 16:01:46 -0700 Message-Id: Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Hirst writes: > I am attempting to complie a unix kernel for the first time. I have been > using BSD and Linux for almost six month, but I heard that compiling > your own kernel not only increased performance but also was a sort of > "right-of-passage" (if that were the case, I beleive I would have been "Rite" of passage. The "right" to compile a kernel you got just by installing FreeBSD. > thrown to the wolves a while ago) My new kernel seems to be dying right > when hte generic one would swich to root (after the "npx0: INT 16 > interface" line). In general, my advice is to try starting from the GENERIC kernel and making sure you can compile that first. Then you can make a few changes at a time and narrow the trouble down. In this case, a quick look showed me at least one thing that looks funny, though: you have both sc0 and vt0 enabled, which is surely one console driver too many. Be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message