Unresolved symbol _mmx_memcpy in modules

DiskDoc · Guest

Doing emerge alsa-driver I eventually get a bunch of unresolved symbol errors. depmod -e shows ten or so ALSA modules plus a couple of kernel modules that need _mmx_memcpy to work.

As far as I understand this has to to with kernel settings when compiling but I've gone trough them and recompiled the kernel a few times (yes, installed it too.. :wink:

) ..I can't seem to find what's wrong! This shouldn't be impossible to fix..any clues?

/ Carl

DiskDoc · Posted: Sun Apr 28, 2002 8:30 am Post subject: Details

Ok..I solved the problem with the two modules included in the kernel source by having them statically compiled into the kernel. However, a lot of ALSA modules still fail to compile properly:

jr linux # depmod -e
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-ac97-codec.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-card-nm256.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-card-share.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-cs461x.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-mixer.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-pcm.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-rawmidi.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-seq-midi-event.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-seq-oss.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-seq-virmidi.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-seq.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd-synth-trident.o
depmod: _mmx_memcpy
depmod: *** Unresolved symbols in /lib/modules/2.4.19-r1/misc/snd.o
depmod: _mmx_memcpy

A friend of mine claims this happens because of a bug in the kernel but if ALSA failed to compile for all of you other Gentooers as well there'd be a lot of shouting about it.
So, if I'm the only one with this problem, could it be hardware related? Or maybe have something to do with how I set up the kernel? :?:

Starborn · Guest

I had the exact same problem, after googling for an answer it seems to be a module dependency in the kernel (only seems to happen to athlon processors though) to fix it do this:

1) turn off 'Set version information on all module symbols' in loadable module support in the kernel
2) do a 'make mrproper' before compiling the kernel (before even make menuconfig or make xconfig or whatever you use)

I did both these, and they solved the problem for me

DiskDoc · Posted: Tue Apr 30, 2002 7:31 am Post subject: Good fix

Seems the fix worked for me too! Many thanks

I have a 1 GHz Duron so they are also seem to be covered by the kernel-source bug.