Subject: Re: version of a kernel module? and modload man page
To: Rhialto <email@example.com>
From: Jeff Rizzo <riz@NetBSD.org>
Date: 03/23/2006 08:14:46
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1
> On Wed 22 Mar 2006 at 18:04:12 -0800, Jeremy C. Reed wrote:
>> LKM 'pf': kernel version mismatch - LKM 201000000, kernel 200000000
> I recently got something like that, when I tried to load an aperture lk=
> which I had compiled with pkg_comp. Strangely enough, it claimed that
> the lkm was for version 399somethign while the system was 300zeros.
> I don't quite understand where it got the 399* version number from,
> since I had compiled it under the same kernel as the one was running.
> The only thing that was 3.99+ (i.e. some -current) was the file server
> where the chroot files were actually located.
> Compiling again without pkg_comp make the issue go away. I'm puzzled
> however how it could ever occur.
If the /usr/src mounted under pkg_comp's chroot was -current, this would
have happened - it's not the version of the running kernel, it's the
version of the source tree the LKM is compiled against. (specifically,
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----