Re: ALSA strikes again (sb16 no go)
ALSA works just fine with SB16. Try ALSA 0.9 -- it's better. Make sure you have the right module compile options.. oss-emulation, isa-pnp, etc. Then use modconf to make sure that the correct ALSA modules are indeed loaded. To make them load at boot automagically, add them to /etc/modules. Also, remember that ALSA defaults to mute everything. Use a good mixer like aumix-gtk to "unmute" the channels before you play (/etc/aumixrc will need to be edited so that it works with alsa -- you'll see what I mean when you look at the file. Just comment out the no-alsa lines)
cheers,
Matt
On Sun, 2001-12-16 at 17:22, Curtis Farnham wrote:
> Does *everybody* have problems getting ALSA to run? Has anyone got an
> ALS4000 card to work? What about SB16? I am getting frustrated and
> desparate to get sound to come out of my speakers.
>
> I was using an ALS4000 card and having no success, and I read somewhere
> that ALSA didn't fully support it anyway. So, I bought a Sound Blaster
> 16 PCI PnP card and tried again. My speakers are still sadly silent.
>
> Following are various data, outputs, and files that might be of interest
> to someone gracious enough to help me.
>
> I'm running:
> Debian Woody
> i586
>
> Sound card:
> sb16 pci pnp
> *or*
> als4000 pci (pnp?)
>
> (I only have room enough for 1 of these inside my box.)
>
> My ALSA version:
> 0.5.12a (compiled from source)
>
> The command I last used to configure alsa-driver sources before
> compiling:
> debian:/usr/src/alsa/alsa-driver-0.5.12a# ./configure
> --with-sequencer=yes --with-isapnp=no --with-cards=sb16
>
> And after compiling, here was the output from alsaconf:
>
> Loading driver:
> Starting ALSA sound driver (version 0.5.12a): (sb16)
> Setting the PCM volume to 100% and the Master output volume to 50%
> The ALSA sound driver was not detected in this system.
> Could not initialize the mixer, the card was probably not detected
> correctly.
>
> And here's the output from lsmod for sound-related modules (I *think*
> that's all that were loaded after '/etc/init.d/alsa start'):
> Module Size Used by Tainted: P
> <snip>
> snd 30848 0 (autoclean)
> soundcore 3460 0 (autoclean) [snd]
> <snip>
>
> Here's the output of 'modprobe snd-card-sb16':
> /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: init_module: No such
> device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters
> /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod
> /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o failed
> /lib/modules/2.4.14cf120901/misc/snd-card-sb16.o: insmod snd-card-sb16
> failed
>
> And here are the contents of /etc/alsa/modutils/0.5 (also occurs in
> /etc/modules.conf):
>
> # --- BEGIN: Generated by ALSACONF, do not edit. ---
> # --- ALSACONF verion 0.4.3b ---
> alias char-major-116 snd
> alias snd-card-0 snd-card-sb16
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-0
> 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
> options snd snd_major=116 snd_cards_limit=1 snd_device_mode=0660
> snd_device_gid=29 snd_device_uid=0
> options snd-card-sb16 snd_index=0 snd_id=CARD_0 snd_port=0x220
> snd_mpu_port=0x300 snd_irq=5 snd_dma8=1 snd_dma16=5 snd_mic_agc=0
> # --- END: Generated by ALSACONF, do not edit. ---
>
> Here's an additional part of /etc/modules.conf, which is seen after the
> above section
>
> # Debian ALSA modules path
> # Do not edit this unless you understand what you're doing.
> path=/lib/modules/`uname -r`/alsa
>
> Finally, here is a recent portion of /var/log/messages (similar is seen
> during boot-up):
> Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #1 not
> found at 0x220 or device busy
> Dec 16 14:28:25 debian kernel: snd: Sound Blaster 16 soundcard #2 not
> found or device busy
>
>
> Thanks, in advance, for any help you can give.
> -Curtis
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: