I'm trying to use the latest version of the emu10k1 drivers from http://opensource.creative.com/ I'm following the directions but am having a problem which I have encoutered before... I've configured the kernel to load sound and the emu10k1 as a module (as normal, and as the documentation for these new drivers say)... I build and install boot into the kernel successfully... Then I 'make' and 'make install' the new driver's source and get the following error when tring 'modprobe emu10k1' on the new driver /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol mem_map_R57a328bf /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol register_sound_dsp_Rad151b8f /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol create_proc_entry_R0dcf6186 /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol register_sound_mixer_R4415bd01 /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol proc_mkdir_R0fac1f22 /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol do_BUG_R577f4bff /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol __pollwait_R72541149 /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol remove_proc_entry_Redb3f930 /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: unresolved symbol register_sound_midi_R42e9ca5a /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o failed /lib/modules/2.4.3/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed The errors are occuring because the new driver files are looking for these function names with the kernel or another loaded kernel module. I think that something with the way modules work, requires these functions to have these hex numbers as part of the function names... If I do a 'objdump -t' on the old driver files I see these same symbols, but with different hex number suffixes... Why are these hex numbers (suffixed on the functions that the new drivers are looking for with in the kernel) created differently than the ones for the modules that compiled with the running kernel? Thanks, -- Davy
