Subject: Re: Loading LKMs at boot yields unresolved symbols, but from commandline it's OK
To: Jeff Rizzo <firstname.lastname@example.org>
From: Quentin Garnier <email@example.com>
Date: 03/04/2005 18:56:32
Content-Type: text/plain; charset=us-ascii
On Fri, Mar 04, 2005 at 09:32:02AM -0800, Jeff Rizzo wrote:
> The problem: if I load the LKMs from the commandline, it's fine.=20
> However, when I configure things in lkm.conf for boot-time load, I get
> undefined reference errors. This is *with* the -s flag.
> ... the first module loads, but the second (which requires symbols from
> the first) doesn't. Here's what /etc/lkm.conf looks like:
> # path options entry postinstall =20
> output when
> #/lkm/if_ipl.o - - - =20
> - -
> /usr/lkm/mod_zaptel.o -s - - - AFTERMOUNT
> /usr/lkm/mod_ztdummy.o -s - - - AFTERMOUNT
> ... as you can see, I _do_ have the -s flag in there. Even more
> interesting, someone else using this code (also on a 2.0 system, like
> this one) is NOT seeing this problem.
Hmm. At first I thought it was kern/29133, but I'm not that sure.
I'm wondering a bit about the part in /etc/rc.lkm where it adds
-A unconditionally (well, as long as the kernel is readable). Could
you try with that part commented out? (It begins with booted_kernel.)
Quentin Garnier - firstname.lastname@example.org - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
-----END PGP SIGNATURE-----