sequencer problem.

Janina Sajka janina at
Tue Nov 19 18:14:00 EST 2002

Well, I'm certainly not the expert on this, but in my experience, "unresolved symbols" means your not going to work as currently compiled. Beyond that,
it's a matter of getting compatible module code appropriately compiled to your hardware and kernel.

That's about the extent of what I know on this. Perhaps others can be more helpful with the place to start, etc. I'm sure that's what you're really
after! <grin>

shaun_oliver at writes:
> From: shaun_oliver at
> hi,
> Whenever I try to modprobe snd-seq-oss,
> I get the following errors.
> Script started on Tue Nov 19 19:58:16 2002
> borg:~# modprobe snd-seq-oss
> /lib/modules/2.4.18/kernel/sound/acore/seq/oss/snd-seq-oss.o: init_module: Device or resource busy
> Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
> /lib/modules/2.4.18/kernel/sound/acore/seq/oss/snd-seq-oss.o: insmod /lib/modules/2.4.18/kernel/sound/acore/seq/oss/snd-seq-oss.o failed
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_midi_event_decode_R1ed0deb6
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_device_register_driver_R06d31dfc
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_kernel_client_enqueue_Rf0f16687
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_kernel_client_dispatch_R761cd91e
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_midi_event_encode_byte_R2479bebd
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_create_kernel_client_R85622965
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_info_create_module_entry_Rf07cfd79
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_kernel_client_write_poll_Rc021ab7a
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_midi_event_free_Re376887e
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_kernel_client_enqueue_blocking_Recc17552
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_info_unregister_Raf7b65bf
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_seq_root_Ra02ed75e
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_register_oss_device_R708f96f6
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_info_register_R2384789a
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_unregister_oss_device_R74dd7bb1
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_midi_event_new_Rcc1457c9
> /lib/modules/2.4.18/misc/snd-seq-oss.o: unresolved symbol snd_info_free_entry_R08eed1fb
> /lib/modules/2.4.18/misc/snd-seq-oss.o: insmod /lib/modules/2.4.18/misc/snd-seq-oss.o failed
> /lib/modules/2.4.18/misc/snd-seq-oss.o: insmod snd-seq-oss failed
> borg:~# 
> Script done on Tue Nov 19 19:58:34 2002
> however, when I look at the offending line in
> /usr/src/alsa-driver-0.9.0rc6/alsa-kernel/core/seq/oss/seq_oss.c, I see
> the code that prints the error message can't register device seq.
> line 223 of the affore mentioned file states thus,
> snd_printk(KERN_ERR "can't register device seq\n");
> any help would be greatly appreciated.
> I'm using the SB_Live with alsa-0.9.0rc6
> thanks in advance.
> -- 
> Shaun Oliver
>  It's multiple choice time...
>       What is FORTRAN?
>       a: Between thre and fiv tran.
>       b: What two computers engage in before they interface.
>       c: Ridiculous.
> _______________________________________________
> Speakup mailing list
> Speakup at

				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina at		Phone: (202) 408-8175

More information about the Speakup mailing list