From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 21:34:31 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 EB1CD16A4CE for ; Mon, 12 Jul 2004 21:34:31 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BEDB43D53 for ; Mon, 12 Jul 2004 21:34:31 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i6CLYQiB059086; Mon, 12 Jul 2004 22:34:26 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Mon, 12 Jul 2004 22:34:21 +0100 User-Agent: KMail/1.6.1 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407122234.21351.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: John Polstra 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 21:34:32 -0000 On Monday 12 July 2004 21:30, John Polstra wrote: > 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. Hmm. Maybe the simplest thing would be to print the link errors using uprintf() instead of printf().