-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 9 Mar 2003 14:52:21 -0400, Shaw, Marco wrote:
> (My apologies, I'll be starting a new thread as I was currently off the mailing > list distrib, and just viewing the archives, but I've changed my settings.) > > >> I've installed kernel-2.4.18-18.7.xbigmem along with the > >> kernel-source-2.4.18-18.x. > >> I've compiled a few custom modules, yet I get this error for > >> 3 modules I've built: > >> > >> # insmod esm > >> Using /lib/modules/2.4.18-18.7.xbigmem/misc/esm.o > >> /lib/modules/2.4.18-18.7.xbigmem/misc/esm.o: kernel-module > >> version mismatch > >> /lib/modules/2.4.18-18.7.xbigmem/misc/esm.o was > >> compiled for kernel > >> version 2.4.18-18.7.x while this kernel is version > >> 2.4.18-18.7.xbigmem. > > > From: Michael Schwendt > > > No, but before compiling the modules, edit the Makefile in the > > top-level kernel source directory. At the top of the file, make > > sure EXTRAVERSION is the same than your running kernel: > > > EXTRAVERSION = -18.7.xbigmem > > This doesn't seem to have changed anything: I still get the same errors. If I > Try to force an insmod, I get loads of unresolved symbol errors. > > Could I be missing something else? > > Marco > > # insmod ./e1000.o > ./e1000.o: kernel-module version mismatch > ./e1000.o was compiled for kernel version 2.4.18-18.7.x > while this kernel is version 2.4.18-18.7.xbigmem. As you can see here, your module was compiled for 2.4.18-18.7.x, NOT 2.4.18-18.7.xbigmem. Whether or not you re-installed the newly built module or whether or not you didn't recompile the module for the correct kernel version, I don't want to guess. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+a5GT0iMVcrivHFQRAu70AJ0W83ZI+WIbQnXS2MI0meGxusgbRgCeOs4G hQnJEu5xv/5nZmWruB8x54s= =wgJk -----END PGP SIGNATURE----- -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list