Re: alsa with 2 soundcards: emu10k1 and intel8x0

From: Andreas Janssen (andreas.janssen_at_bigfoot.com)
Date: 12/26/04 

Date: Sun, 26 Dec 2004 15:20:03 +0100

Hello

Xan (<xan2@ono.com>) wrote:

> I have two soundcards in my system:
> SoundBlaster Live (emu10k1) and SiS onboard card (intel8x0).
> I have a DVD with the cable sound connected to SBLive.
>
> I want to have the possibility of choosing the two soundcards in any
> program that supports alsa (eg xmms) and that SBLive was my default
> soundcard of my system.

The second part is easy, although there are (at least) three ways to do
it. The default device normally is the one for wich the driver is
loaded first (index 0), unless you configure your system differently.
Check /proc/asound/cards:

andreas@sirius:~$ cat /proc/asound/cards
0 [Live ]: EMU10K1 - Sound Blaster Live!
                     Sound Blaster Live! (rev.8) at 0xe400, irq 18
1 [Bt878 ]: Bt87x - Brooktree Bt878
                     Brooktree Bt878 at 0xdddff000, irq 19

You can see that on my system, the SB Live! is the default device. To
influence this, you can:

- alter the sequence in which the drivers are loaded
- use the configuration file /etc/asound.conf, and add something like
  this:

    pcm.!default {
         type hw
         card 1
    }

    ctl.!default {
         type hw
         card 1
    }

 This will make the device with index 1 the default device

- tell the driver modules which index the device should have, e.g.

      options snd_emu10k1 index=0
      options snd_intel8x0 index=1

  in your /etc/modprobe.conf or in some file in /etc/modprobe.d,
  depending on which system your distribution uses to configure modules
  for kernel 2.6. In my opinion, the last way is the most reliable one,
  because even if the way the drivers are loaded changes (e.g. you
  install hotplug), the cards still have the same index.

> Can you say me what steps I need to get it. I'm a novice. Please, put
> all steps (although these are trivial)

To change the output device in your applications, you need to configure
that programs or their output plugins. In xmms, you can select the
device by configuring the ALSA plugin.

> Now I have a 2.6.8rc2 kernel compiled with alsa support (here's my
> config file of kernel):

(please please, before posting some files, remove the parts that are not
important)

> CONFIG_SOUND=m
> CONFIG_SND=m
> [...]
> CONFIG_SND_EMU10K1=m
> CONFIG_SND_INTEL8X0=m

best regards
 Andreas Janssen 

-- 
Andreas Janssen <andreas.janssen@bigfoot.com>
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps-sarge.html

Relevant Pages

  • Re: Dreaded IRQ10 disabled nobody cares problem!
    ... I think probably boot with a grub configuration file. ... a problem caluse by a driver called intel8x0 which gets ... >>I tried reserver IRQ 10 in the bios, but this does not work, now both ...
    (alt.os.linux.suse)
  • Re: [SLE] lm_sensors Problems
    ... available so it can be accessed when mentioned in the "modprobe" command ... configuration file. ... Perhaps making the smbus-arp entry MODULE_1 instead of MODULE_4? ... >> driver? ...
    (SuSE)
  • Re: SD.conf and info on JNIC
    ... This is the configuration file for the 'sd' driver, ... That's the configuration file for one of the different JNI drivers. ... specifically used for SCSI cards purpose only? ... the sd.conf file details the devices that the 'sd' driver ...
    (comp.unix.solaris)
  • Re: STATUS_OBJECT_NAME_NOT_FOUND
    ... > settings I have in the registry instead of in a configuration file. ... > However, I'm not the only guy that looks at this file, so my driver has to ... >>> Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Multitracking with multiple interfaces
    ... > record from all inputs of two Echo Audiofire 12's and an M-Audio Audiophile ... You could try the Asio4All driver... ... It will work if your soundcards ...
    (rec.audio.pro)