From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 20:30:37 2004 Return-Path: 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 A0A6116A4CE for ; Mon, 12 Jul 2004 20:30:37 +0000 (GMT) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBCF43D2D for ; Mon, 12 Jul 2004 20:30:37 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (dsl081-189-067.sea1.dsl.speakeasy.net [64.81.189.67]) by blake.polstra.com (8.12.11/8.12.11) with ESMTP id i6CKUapw079061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 12 Jul 2004 13:30:36 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.11/8.12.11/Submit) id i6CKUaG9009167 for freebsd-current@freebsd.org; Mon, 12 Jul 2004 13:30:36 -0700 (PDT) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20040712194438.B9CFB16A4D1@hub.freebsd.org> Date: Mon, 12 Jul 2004 13:30:36 -0700 (PDT) From: John Polstra To: freebsd-current@freebsd.org X-Bogosity: No, tests=bogofilter, spamicity=0.414429, version=0.14.5 Subject: Re: kldload won't load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 12 Jul 2004 20:30:37 -0000 On 12-Jul-2004 Bill Paul wrote: >> Yesterday I built the ndis module (ndis.ko) but I can't seem to load it: >> >> 5 # ls /sys/modules/ndis/ | grep 'ndis' >> kern_ndis.o >> ndis.kld >> ndis.ko >> subr_ndis.o >> 6 # kldload -v /sys/modules/ndis/ndis.ko >> kldload: can't load /sys/modules/ndis/ndis.ko: No such file or directory [...] > *sigh* > > When a kernel module doesn't load correctly, this is your cue to > run "dmesg" and look at the messages printed in the kernel message > buffer. That will tell you why it didn't load. Of course, nobody > ever remembers this, and apparently running xconsole is no longer > in vogue. > > This needs to be a FAQ. No, it needs to be fixed. It's printing a totally incorrect error message, and nobody should have to use dmesg to find out what's really happened. > Every time I have to tell someone to go back and look at what dmesg > says, god kills a kitten. Really? Maybe he's trying to tell you something. John