Messages in this thread | | | Subject | Re: [2.4.20] e1000 as module gives unresolved symbol _mmx_memcpy | From | Alan Cox <> | Date | 10 Jan 2003 15:14:03 +0000 |
| |
On Fri, 2003-01-10 at 13:45, Jurgen Kramer wrote: > Hi, > > While trying to use the e1000 as a module with kernel 2.4.20 it gives > me a unresolved symbol while trying to insmod the module. The offending > symbol is _mmx_memcpy. When the driver is compiled into the kernel > there's no problem. > > I am running the kernel on a VIA Eden with 800MHz C3. Does this have > something to do with the fact that kernels for the VIA C3 are now > compiled with i486 optimisations (so maybe no MMX support?)?
Make sure you build from distclean if you've built for other cpu options before. (cp .config ..; make distclean; cp ../.config .config; make oldconfig..
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |