Date: Mon, 12 Jul 2004 22:34:21 +0100 From: Doug Rabson <dfr@nlsystems.com> To: freebsd-current@freebsd.org Cc: John Polstra <jdp@polstra.com> Subject: Re: kldload won't load Message-ID: <200407122234.21351.dfr@nlsystems.com> In-Reply-To: <XFMail.20040712133036.jdp@polstra.com> References: <XFMail.20040712133036.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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().
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407122234.21351.dfr>