From owner-freebsd-current@FreeBSD.ORG Wed Aug 30 22:26:36 2006 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 5B86116A4DA for ; Wed, 30 Aug 2006 22:26:36 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE51C43D45 for ; Wed, 30 Aug 2006 22:26:35 +0000 (GMT) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.13.8/8.13.8) with ESMTP id k7UMQQ6Z099751 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Thu, 31 Aug 2006 00:26:27 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD90301E2F278@NT-IRVA-0750.brcm.ad.broadcom.com> References: <09BFF2FA5EAB4A45B6655E151BBDD90301E2F278@NT-IRVA-0750.brcm.ad.broadcom.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <989384AE-60BB-4A37-B240-02DE1CEE4E4C@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 31 Aug 2006 00:26:25 +0200 To: David Christensen X-Mailer: Apple Mail (2.752.2) Cc: freebsd-current@freebsd.org Subject: Re: Simplified Steps for Building a Loadable module on -CURRENT 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: Wed, 30 Aug 2006 22:26:36 -0000 Am 31.08.2006 um 00:12 schrieb David Christensen: > I've been able to successfully build drivers in the past as > loadable modules but I'm getting some kernel panics with -CURRENT > when installing a module using kldload now where things used to > work before. You did nuke /usr/obj, performed a full kernel build (cd /usr/src; make buildkernel installkernel), and the module in question that was installed alongside your new kernel is *not* panicking the system? Then what's the panic message, and how exactly are you building your module? > Assume I'm a complete FreeBSD noob for a moment > (which really isn't that far from the truth) and I want to build > a driver as a loadable module for testing. After moving to > the appropriate directory in the source tree (/usr/src/sys/dev/XXX), > what steps do I need to follow to build the driver as a module? That would be /usr/src/sys/modules/ So far, just running make there has worked for me just fine. > Assume for the moment that I have already commented the driver out > of my kernel configuration file > (/usr/src/sys//conf/GENERIC) > and rebuilt and installed that kernel. If the driver has been compiled into the kernel, kldload will error out with EEXISTS. If the system panics, you should provide specifics. Stefan -- Stefan Bethke Fon +49 170 346 0140