From owner-freebsd-questions@FreeBSD.ORG  Thu Aug  4 18:23:24 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
X-Original-To: freebsd-questions@freebsd.org
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 DC40116A41F
	for <freebsd-questions@freebsd.org>;
	Thu,  4 Aug 2005 18:23:24 +0000 (GMT)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (dc.cis.okstate.edu [139.78.100.219])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9F8B043D46
	for <freebsd-questions@freebsd.org>;
	Thu,  4 Aug 2005 18:23:24 +0000 (GMT)
	(envelope-from martin@dc.cis.okstate.edu)
Received: from dc.cis.okstate.edu (localhost.cis.okstate.edu [127.0.0.1])
	by dc.cis.okstate.edu (8.12.6/8.12.6) with ESMTP id j74INMT3015147;
	Thu, 4 Aug 2005 13:23:22 -0500 (CDT)
	(envelope-from martin@dc.cis.okstate.edu)
Message-Id: <200508041823.j74INMT3015147@dc.cis.okstate.edu>
To: "BBB" <alex.voicu@bredband.net>, freebsd-questions@freebsd.org
Date: Thu, 04 Aug 2005 13:23:22 -0500
From: Martin McCormick <martin@dc.cis.okstate.edu>
Cc: 
Subject: Re: installing kernel fails, make is ok 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2005 18:23:25 -0000

	You might first try making a generic kernel with no
customization and see if that works.  If it does, you might be
accidentally leaving out support for something vital like disk drives
or something else equally vital causing the kernel to not get along
far enough to produce error messages.

	If the generic configuration produces a working kernel, then
start pulling things off and re-making it until you kill it.  You will
then know what actually caused the problem.  If it doesn't tell you
anything at all, it must be rather early in the boot process because a
kernel can usually spit out an error or to to the screen before it
dies.

	If you get a working kernel that is not quite what you wanted,
you can at least save the dmesg output and study it to see what
devices are in your computer and make sure that your custom
configuration includes all of them.

"BBB" writes:
>Im having trouble installing my coustom kernel, config and make doesnt say any