Date: Mon, 12 Jul 2004 16:38:36 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: John Polstra <jdp@polstra.com> Cc: freebsd-current@freebsd.org Subject: Re: kldload won't load Message-ID: <20040712213835.GA98593@dan.emsphone.com> In-Reply-To: <XFMail.20040712133036.jdp@polstra.com> References: <20040712194438.B9CFB16A4D1@hub.freebsd.org> <XFMail.20040712133036.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 12), John Polstra said: > On 12-Jul-2004 Bill Paul wrote: > > 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. Maybe a uprintf would be useful here? imgact_elf.c does that to add a little more info before returning ENOEXEC. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040712213835.GA98593>