On Apr 8, 12:00 pm, Nigel Henry <cave.dnb2m9...@aliceadsl.fr> wrote:
Many thanks Nigel for your eply.
> On Wednesday 08 April 2009 14:56, Dancing Fingers wrote:
>
> > Hi guys,
> > I'm also having an ALSA problem. I put a SoundBlaster card in my
> > Lenny box. If I run alsaconf every time I boot and everything works
> > fine. What I don't understand is why the system resets the conf
> > files every time it boots?
> > Thanks.
> > Chris
>
> Hi Chris.
>
> I assume there is an onboard soundcard on the machine as well. What may be
> happening when you boot up is that both soundcards are being detected, and
> the onboard soundcard is being set as card0, and the audigy one as card1.
> Most audio apps use card0 as default, so you may find that plugging the
> speakers into the onboard soundcard (if there is one) produces sound.
>
> To check this out, reboot, then run the following command before running
> alsaconf, and post the results.
>
> cat /proc/asound/cards
This is what I get:
0 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with CMI9761A+ at 0xd800, irq 22
>
> Then run alsaconf, and set up the audigy card, then run the command above
> again, and post the results.
>
> If what I say above is the case, and you want the audigy soundblaster to be
> set as card0 (the default), you can add a couple of lines to the bottom of:
> to /etc/modprobe.d/alsa-base
>
> options snd-emu10k1 index=0
> options snd-???? index=1
What I tried was:
options snd-emu10k1 index=0
options snd-V8235 index=1
>
> The above is assuming that your soundblaster is using the snd-emu10k1 driver,
> but may be snd-ca0106. The snd-???? is the unknown driver for the onboard
> card (if that exists). Just change that to whatever the driver is (maybe
> snd-hda-intel, as a guess).
>
> Now reboot, and see if you have sounds on the soundblaster (without running
> alsaconf), and run cat /proc/asound/cards again, where you should see the
> soundblaster as card0, and the onboard card as card1.
>
> If you do have 2 soundcards you can open alsamixer on the CLI as below to
> access the controls for each card.
>
> alsamixer -D hw:0
> alsamixer -D hw:1
>
> Would you post the output from the following, as well please.
>
> lsmod | grep snd
deb:/home/cricky# 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 1 snd_emu10k1_synth
firmware_class 6816 1 snd_emu10k1
snd_via82xx 20664 1
snd_pcm_oss 32800 0
snd_mixer_oss 12320 1 snd_pcm_oss
snd_ac97_codec 88484 2 snd_emu10k1,snd_via82xx
ac97_bus 1728 1 snd_ac97_codec
snd_util_mem 4032 2 snd_emux_synth,snd_emu10k1
snd_pcm 62596 5
snd_emu10k1,snd_via82xx,snd_pcm_oss,snd_ac97_codec
snd_hwdep 6212 2 snd_emux_synth,snd_emu10k1
snd_seq_dummy 2660 0
snd_page_alloc 7816 3 snd_emu10k1,snd_via82xx,snd_pcm
snd_mpu401_uart 6368 1 snd_via82xx
snd_seq_oss 24992 0
snd_seq_midi 5728 0
snd_rawmidi 18496 4
snd_seq_virmidi,snd_emu10k1,snd_mpu401_uart,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 16
snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_via82xx,snd_pcm_oss,snd_mixer_oss,snd_ac97_codec,snd_pcm,snd_hwdep,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
gameport 10700 3 snd_via82xx,emu10k1_gp
soundcore 6368 1 snd
>
> All the best.
>
> Nigel.
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
No sound at boot yet.
Thanks.
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
