Messages in this thread | | | Date | Fri, 4 Jan 2002 19:01:33 +0100 (CET) | From | Roy Sigurd Karlsbakk <> | Subject | Re: Error loading e1000.o - symbol not found |
| |
hm...
same problem with 2.4.18-pre1
[root@vs2 src]# modprobe e1000 /lib/modules/2.4.18-srv1/kernel/drivers/net/e1000.o: unresolved symbol _mmx_memcpy /lib/modules/2.4.18-srv1/kernel/drivers/net/e1000.o: insmod /lib/modules/2.4.18-srv1/kernel/drivers/net/e1000.o failed /lib/modules/2.4.18-srv1/kernel/drivers/net/e1000.o: insmod e1000 failed
anyone that knows why?
On 4 Jan 2002, Craig Knox wrote:
> > When trying to insmod the driver, I get the following errors: > > > > /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? > > I had the same problem (unresolved symbol _mmx_memcpy) - I think it was > with 2.4.17. > Two solutions are - > Compile your kernel as althon - compile module as something else (ie > i386). > or - > Patch your 2.4.17 kernel to 2.4.18pre1 which doesn't have the problem > and seems very stable to me. > >
-- 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/
| |