Re: Error loading e1000.o - symbol not found
Roy Sigurd Karlsbakk (roy@karlsbakk.net)
Fri, 4 Jan 2002 17:59:32 +0100 (CET)
> > /lib/modules/2.4.17-srv3/kernel/drivers/net/e1000.o: unresolved symbol _mmx_memcpy
> > /lib/modules/2.4.17-srv3/kernel/drivers/net/e1000.o: insmod /lib/modules/2.4.17-srv3/kernel/drivers/net/e1000.o failed
> > /lib/modules/2.4.17-srv3/kernel/drivers/net/e1000.o: insmod e1000 failed
> >
> > What's this? Is _mmx_memcpy only valid on Intel architecture? Does Athlon
> > have any equivalent system call?
>
> Looks like you built the module against a different Athlon tree ?
>
What do you mean by a different Athlon tree?
I have only one kernel tree under /usr/src/, and I built the kernel and
rebooted first. I can even find _mmx_memcpy in System.map
roy
--
Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
Computers are like air conditioners.
They stop working when you open Windows.
-
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/