Unresolved Symbol Errors

[Corey Vaillancourt]

Well I had been having some troubles with my sound card lately. So I figured i would reinstall some drivers. I downloaded the new ALSA and Creative drivers for my sound card. And by some luck I actually got them to install. I did an lsmod to see what modules I have installed. Then I did an insmod emu10k1 to install my sound card module and I got some unresolved symbol errors. So I did some more research and I found the help file on this website and it said to edit the Makefile before you configure it but I couldnt' for the life of me find the 2 lines of code I'm supposed to edit that would get rid of the unresolved symbol errors. I tried a modprobe emu10k1 but that didn't work either because it said no such device because the module isn't loaded... I can't think of anything else to do. So here is the error I got.


Using /lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol ac97_read_proc_Rbae4da72
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_send_sysex_Rfddcbfb3
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_set_instr_Rd85be938
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol ac97_probe_codec_R84601c2b
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_ioctl_Rb66d1f67
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_reset_R56504ca2
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol sound_unload_mididev_Ra6bb414c
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_open_Rf6b3a2fb
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_hw_control_Rb14b22cd
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_kill_note_R2aa31695
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_start_note_R9bdaf24d
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_aftertouch_Rf1ea8a20
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_setup_voice_R4ff47e9d
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_bender_Rba7dd041
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_load_patch_Rf7426da3
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_controller_R892093e0
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_devs_Rb3ae63d0
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol sequencer_init_Rf78f6363
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_panning_Rdb400afa
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol midi_synth_close_Rad45df73
/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: unresolved symbol sound_alloc_mididev_Rba413f87

[bwkaz]

Was that when you did a modprobe, or an insmod?

Running insmod doesn't load any other modules that the one you're loading may be dependent on. Running modprobe, on the other hand, does. If you were using insmod, try modprobe instead (but try /sbin/depmod -ae beforehand, to make sure the modules.dep file (which keeps track of module dependencies) is up to date).

[Corey Vaillancourt]

That command I ran was an insmod. I tried what you told me to do about the modprobe and I got the same error I have been getting that you have been trying to help me with... here it is:

/lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/misc/emu10k1.o failed
/lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
modprobe: insmod /lib/modules/2.4.21-0.13mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed
modprobe: insmod emu10k1 failed

I did an lsmod, and I didn't see any 'emu10k1' module loaded... and to test I did a rmmod and it said it wasn't loaded. So I tried the lsmod emu10k1 which was the unresolved symbol error. The error in post is from a modprobe emu10k1

[DMR]

As the errors suggest, have you checked your logs/dmesg for messages regarding the card or drivers?

[Corey Vaillancourt]

yes I have checked my errors... I posted it on another thread and I didn't get anywhere with it.. here it is again. This is from Dmesg:

devfs_register(sequencer2): could not append to parent, err: -17
Creative EMU10K1 PCI Audio Driver, version 0.20, 15:30:48 Mar 14 2003

[DMR]

devfs registers devices in a dynamic manner (as opposed to the tradition "static" entries in /dev), and what the "could not append to parent" error is telling you that a driver is trying to register a device in /dev, but that a device with the same name already exists. Since the device attempting to register is called "sequencer", you can be pretty sure that your upgraded sound drivers are the culprit.

Could you post a link to the MAKEFILE that you're referring to please?

In terms of the modprobe errors, your sound card might have a resource conflict with another device. Please post the output of the following three commands:

lspci (post the contents of the "Multimedia audio controller" section)

less /proc/ioports

less /proc/interrupts

Is PNP OS support turned off in your BIOS? If not, make it so.