Skip to contentSkip to conversation

unresolved symbols in snd-gus-synth & snd-page-alloc on linux-2.2.27

DISCUSSION Ted 2 participants 4 messages Jun 23, 2005 – Jun 30, 2005

lore
Share & tools
lore

Ted

author
#0 lore raw

Hello,

Problem 1) I get unresolved symbols in the snd-gus-synth module of alsa-driver-1.0.9rc3 when building for the interwave pnp card using

$ ./configure --prefix=/usr --with-debug=detect --with-isapnp=yes \
		--with-sequencer=yes --with-cards=interwave
# depmod -e
depmod: *** Unresolved symbols in /lib/modules/2.2.27-pre2/misc/snd-gus-synth.o
depmod:		snd_midi_channel_free_set
depmod:		snd_midi_channel_alloc_set
#

This is because the snd-seq-midi-emul is ommitted from the build. A fix that appears to correct this is to add its dependancy to the file

alsa-kernel/core/seq/Makefile

# diff alsa-kernel/core/seq/Makefile.Orig alsa-kernel/core/seq/Makefile
41c41
< obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o
---
Quoted 1 line

obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o snd-seq-midi-emul.o

#

Problem 2) Following that fix, the snd-ainstr-simple module also fails to load because its initialisation is incorrect:

# insmod snd-ainstr-simple
Using /lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o
/lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o: init_module:
	Invalid argument Hint: insmod errors can be caused by incorrect \
	module parameters, including invalid IO or IRQ parameters

Not sure how to fix this, it looks like incomplete "work in progress". See
alsa-kernel/core/seq/instr/ainstr_simple.c

Problem 3) The cvsexport 2005-06-17 also has unresolved symbols in the snd-page-alloc module on linux-2.2.27:

# depmod -e
depmod: *** Unresolved symbols in /lib/modules/2.2.27-pre2/misc/snd-gus-synth.o
depmod:         snd_midi_channel_free_set
depmod:         snd_midi_channel_alloc_set
depmod: *** Unresolved symbols in /lib/modules/2.2.27-pre2/misc/snd-page-alloc.o
depmod:         strsep
depmod:         simple_strtol
depmod:         memparse
#

These symbols are not defined in linux-2.2.27 and need adding to alsa-driver/include/compat_22.h.

Thankyou,

Ted.

Signature · 9 lines
Ted <[email protected]>
   http://www.nowtsfree.freeserve.co.uk


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
author
#1 lore raw

Hello, I have made a little progress in this, but am still having problems loading the snd-ainstr-simple module.

Using yesterday's cvs for alsa-driver and alsa-kernel, I still need to make the following change in order to build the snd-seq-midi-emul module (Problem 1 in previous message)

$ diff alsa-kernel/core/seq/Makefile.Orig alsa-kernel/core/seq/Makefile
41c41
< obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o
---
Quoted 1 line

obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o snd-seq-midi-emul.o

The unresolved symbols in snd-page-alloc (Problem 3 in my last message) seem to have been corrected in yesterday's cvs.

I have made a little progress but still not found a fix for Problem 2 in my previous message

Quoted 5 lines
# insmod snd-ainstr-simple
Using /lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o
/lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o: init_module:
        Invalid argument Hint: insmod errors can be caused by incorrect \
        module parameters, including invalid IO or IRQ parameters

When this error occurs, dmesg also reports the following

kernel: init_module: mod->ex_table_* invalid.

Adding print statements to the sourcecode for sys_init_module() in linux-2.2.27pre, I've found that this failure arises because mod->ex_table_end == mod + mod->size. whereas the kernel expects mod->ex_table_end < mod + mod->size.

See the massive sanity checks in sys_init_module() in linux/kernel/module.c.

I'm using modutils-2.3.17, gcc-2.95.3, ld-2.10, linux-2.2.27pre2 if that helps. I'm not sure how to make further progress on this. Any help would much appreciated.

Ted.

Signature · 9 lines
Ted <[email protected]>
   http://www.nowtsfree.freeserve.co.uk


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
#2 lore raw

At Thu, 30 Jun 2005 03:47:42 +0100,

Quoted 5 lines · Ted

Hello, I have made a little progress in this, but am still having problems loading the snd-ainstr-simple module.

Quoted 9 lines

Using yesterday's cvs for alsa-driver and alsa-kernel, I still need to make the following change in order to build the snd-seq-midi-emul module (Problem 1 in previous message)

$ diff alsa-kernel/core/seq/Makefile.Orig alsa-kernel/core/seq/Makefile
41c41
< obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o
---
Quoted 1 line

obj-$(call sequencer,$(CONFIG_SND_GUS_SYNTH)) += snd-seq-instr.o snd-seq-midi-emul.o

Thanks, fixed on CVS.

Quoted 2 lines

The unresolved symbols in snd-page-alloc (Problem 3 in my last message) seem to have been corrected in yesterday's cvs.

Yes.

Quoted 9 lines

I have made a little progress but still not found a fix for Problem 2 in my previous message

Quoted 5 lines
# insmod snd-ainstr-simple
Using /lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o
/lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o: init_module:
        Invalid argument Hint: insmod errors can be caused by incorrect \
        module parameters, including invalid IO or IRQ parameters
Quoted 3 lines

When this error occurs, dmesg also reports the following

kernel: init_module: mod->ex_table_* invalid.

Sorry, no idea yet.
ainstr_simple.c has a quite simple module init, so I don't see what's going wrong, at least at module init...

Takashi

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#3 lore raw
Quoted 11 lines · Takashi

At Thu, 30 Jun 2005 03:47:42 +0100,

Quoted 9 lines · Ted

I have made a little progress but still not found a fix for Problem 2 in my previous message

Quoted 5 lines
# insmod snd-ainstr-simple
Using /lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o
/lib/modules/2.2.27-pre2/misc/snd-ainstr-simple.o: init_module:
        Invalid argument Hint: insmod errors can be caused by incorrect \
        module parameters, including invalid IO or IRQ parameters
Quoted 7 lines
Quoted 3 lines

When this error occurs, dmesg also reports the following

kernel: init_module: mod->ex_table_* invalid.

Sorry, no idea yet.
ainstr_simple.c has a quite simple module init, so I don't see what's going wrong, at least at module init...

Thanks for quick reply. I've tried comparing the build of similar small modules to snd-ainstr-simple, such as snd-ainstr-gf1, which does appear to load correctly, but I have not noticed anything yet.

Ted.

Signature · 9 lines
Ted <[email protected]>
   http://www.nowtsfree.freeserve.co.uk


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click