I had to turn off the M/B integrated "Azalia" sound chip in the BIOS. For what it's worth, here are the automatically loaded modules for my SoundBlaster Live soundcard on Debian Lenny which is producing sound beautifully:
hend...@ivcadmin:~$ lsmod | grep snd snd_emu10k1_synth 5664 0 snd_emux_synth 27936 1 snd_emu10k1_synth snd_seq_virmidi 4896 1 snd_emux_synth snd_seq_midi_emul 5376 1 snd_emux_synth snd_emu10k1 115200 2 snd_emu10k1_synth firmware_class 6816 1 snd_emu10k1 snd_ac97_codec 88484 1 snd_emu10k1 ac97_bus 1728 1 snd_ac97_codec snd_pcm_oss 32800 0 snd_mixer_oss 12320 1 snd_pcm_oss snd_pcm 62596 3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss snd_page_alloc 7816 2 snd_emu10k1,snd_pcm snd_util_mem 4032 2 snd_emux_synth,snd_emu10k1 snd_hwdep 6212 2 snd_emux_synth,snd_emu10k1 snd_seq_dummy 2660 0 snd_seq_oss 24992 0 snd_seq_midi 5728 0 snd_rawmidi 18496 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi snd_seq_midi_event 6432 3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi snd_seq 41456 9 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event snd_timer 17800 3 snd_emu10k1,snd_pcm,snd_seq snd_seq_device 6380 8 snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq snd 45604 15 snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device soundcore 6368 1 snd The command 'lspci | grep Creative' outputs this on my Lenny machine: 05:03.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08) 05:03.1 Input device controller: Creative Labs SB Live! Game Port (rev 08) Why don't you post the output from 'lsmod | grep snd' and "lspci | grep Creative' to the list. That way we can see what's registered at the OS level. Hendrik Simon Wood wrote: > On Wed, 4 Mar 2009 09:39:22 -0700 > Rick Norman <[email protected]> wrote: > >> /etc/modules has only two entries: 'sbp2' and 'loop', but seeing as >> how there are no new sound modules in memory after running alsaconf, >> I'm at a bit of a loss as to what I might need to add there. > > If the module is loading OK on its own but there something that alsactl is > doing, then you could try saving the state of the alsa system and have that > load automatically on boot. > > You can save current settings with: > alsactl store <card #> > > > Its also possible that the module needs some parameters set, maybe alsaconf > is managing to auto configure those. If you can work out what these are (I > can't think how to at present) then they can be added to the /etc/modutils > files. _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
