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 21:46:14
Content-Type: text/plain; charset=us-ascii
On Fri, Mar 04, 2005 at 09:12:56PM +0100, Quentin Garnier wrote:
> On Fri, Mar 04, 2005 at 10:47:36AM -0800, Jeff Rizzo wrote:
> > >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.)
> > >
> > > =20
> > >
> > Sure enough, with that part commented out, it loads just fine. What do
> > you think the best general-purpose solution is?
> Right now, if -A is passed, ksyms is not used, so indeed the second load
> can't resolve the symbols of the first one.
On the other hand, modload(8) performs exactly what rc.lkm does, so I
think that piece of code in rc.lkm should simply be removed.
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-----