[EMAIL PROTECTED], on 2006-10-09: > "lsmod |grep snd" returns > > snd_cmipci 31296 0 > gameport 14344 1 snd_cmipci > snd_pcm_oss 35968 0 > snd_mixer_oss 15872 1 snd_pcm_oss > snd_pcm 74532 2 snd_cmipci,snd_pcm_oss > snd_page_alloc 9512 1 snd_pcm > snd_opl3_lib 9824 1 snd_cmipci > snd_timer 20836 2 snd_pcm,snd_opl3_lib > snd_hwdep 8676 1 snd_opl3_lib > snd_mpu401_uart 7520 1 snd_cmipci > snd_rawmidi 22560 1 snd_mpu401_uart > snd_seq_device 7756 2 snd_opl3_lib,snd_rawmidi > snd 48100 10 > snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device > soundcore 9216 1 snd > > > which seems to indicate that the module is actually loaded.
I had the same problem a few weeks ago (after a possibly unrelated security update for kernel 2.6.8 on sarge). After a helpful remark in debian-user this solved it for me: sudo modprobe snd_seq_oss sudo modprobe snd_pcm_oss sudo modprobe snd_mixer_oss Of those three, you only miss snd_seq_oss. So a sudo modprobe snd_seq_oss /might/ do the trick. I just added these lines: # Sound snd_seq_oss snd_pcm_oss snd_mixer_oss to my /etc/modules, which should help after the next reboot; haven't tried it yet. -- Maurits van Rees | http://maurits.vanrees.org/ [NL] Work | http://zestsoftware.nl/ GnuPG key | http://maurits.vanrees.org/var/gpgkey.asc "Do only what only you can do." --- Edsger Wybe Dijkstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
