Thread: [Alsa-user] modprobe snd-seq-oss hangs
Brought to you by:
perex
From: Kevin M. G. <kn...@go...> - 2005-01-30 07:43:01
|
I've been trying for a year to get midi to work under Linux, finally ditched my old Yamaha YMF-724 and put in a new SoundBlaster Audigy 2 ZS. I can now get midi to work, but after the system boots there's no /dev/sequencer, so I have to 1) modprobe snd-seq-oss (which hangs and doesn't respond to signals from the keyboard) 2) kill that process from a different window 3) sfxload the sound font files in CT4MGM.SF2 If I try to put the modprobe into rc.local so it'll happen at boot, it hangs there too and the boot process stops. Relevant system data is below. Can anyone tell my why "modprobe snd-seq-oss" would hang, or how otherwise to get /dev/sequencer up and working? $ uname -a Linux mrs.hudson.goess.org 2.6.9-1.681_FC3 #1 Thu Nov 18 15:10:10 EST 2004 i686 i686 i386 GNU/Linux /etc/modules.conf: # ALSA portion alias char-major-116 snd # module options should go here # OSS/Free portion alias char-major-14 soundcore alias sound-slot-0 snd-card-0 # card #1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias snd-card-0 snd-emu10k1 options snd-card-0 index=0 install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && /usr/sbin/alsactl restore >/dev/null 2>&1 || : remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r--ignore-remove snd-emu10k1 alias ieee1394-controller ohci1394 before forcing the modprobe: $ lsmod | grep snd snd_emu10k1 93769 1 snd_rawmidi 26725 1 snd_emu10k1 snd_pcm_oss 47608 0 snd_mixer_oss 17217 1 snd_pcm_oss snd_pcm 97993 2 snd_emu10k1,snd_pcm_oss snd_timer 29765 1 snd_pcm snd_seq_device 8137 2 snd_emu10k1,snd_rawmidi snd_ac97_codec 64401 1 snd_emu10k1 snd_page_alloc 9673 2 snd_emu10k1,snd_pcm snd_util_mem 4801 1 snd_emu10k1 snd_hwdep 9413 1 snd_emu10k1 snd 54053 11 snd_emu10k1,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_hwdep soundcore 9889 1 snd # modprobe -v snd-seq-oss insmod /lib/modules/2.6.9-1.681_FC3/kernel/sound/core/seq/snd-seq.ko insmod /lib/modules/2.6.9-1.681_FC3/kernel/sound/core/seq/snd-seq-midi-event.ko insmod /lib/modules/2.6.9-1.681_FC3/kernel/sound/core/seq/oss/snd-seq-oss.ko ...hangs there, needs to be killed from a different terminal and after forcing the modprobe: # lsmod | grep snd snd_seq_midi 8033 0 snd_emu10k1_synth 7873 0 snd_emux_synth 38977 1 snd_emu10k1_synth snd_seq_virmidi 6593 1 snd_emux_synth snd_seq_midi_emul 6593 1 snd_emux_synth snd_seq_oss 33985 0 snd_seq_midi_event 8385 3 snd_seq_midi,snd_seq_virmidi,snd_seq_oss snd_seq 56785 8 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi_event snd_emu10k1 93769 2 snd_emu10k1_synth snd_rawmidi 26725 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1 snd_pcm_oss 47608 0 snd_mixer_oss 17217 1 snd_pcm_oss snd_pcm 97993 2 snd_emu10k1,snd_pcm_oss snd_timer 29765 2 snd_seq,snd_pcm snd_seq_device 8137 7 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi snd_ac97_codec 64401 1 snd_emu10k1 snd_page_alloc 9673 2 snd_emu10k1,snd_pcm snd_util_mem 4801 2 snd_emux_synth,snd_emu10k1 snd_hwdep 9413 2 snd_emux_synth,snd_emu10k1 snd 54053 15 snd_emux_synth,snd_seq_virmidi,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_seq_device,snd_ac97_codec,snd_hwdep soundcore 9889 1 snd |
From: Clemens L. <cl...@la...> - 2005-01-31 16:37:17
|
Kevin M. Goess" wrote: > modprobe snd-seq-oss (which hangs and doesn't respond to signals from > the keyboard) > > $ uname -a > Linux mrs.hudson.goess.org 2.6.9-1.681_FC3 #1 Thu Nov 18 15:10:10 EST > 2004 i686 i686 i386 GNU/Linux Try using a newer version of ALSA (kernel 2.6.10, or compile ALSA separately). HTH Clemens |
From: Kevin M. G. <kn...@go...> - 2005-02-03 06:53:42
|
Clemens Ladisch wrote: > Kevin M. Goess" wrote: > >>modprobe snd-seq-oss (which hangs and doesn't respond to signals from >>the keyboard) >> >>$ uname -a >>Linux mrs.hudson.goess.org 2.6.9-1.681_FC3 #1 Thu Nov 18 15:10:10 EST >>2004 i686 i686 i386 GNU/Linux > > Try using a newer version of ALSA (kernel 2.6.10, or compile ALSA > separately). That seems to have done the trick. Thank you! |