AlsaProject - User contributions [en]

Matrix:Module-ice1712

2011-10-17T16:27:02Z

Dominique: /* Links for ICE1712 module - mise en page */

{| align="right"
| __TOC__
|}

{{Template:Modinfo
|module=ice1712
|description=ICEnsemble ICE1712 (Envy24)
|author=Jaroslav Kysela
|index:Index value for ICE1712 soundcard. (array of int)
|id:ID string for ICE1712 soundcard. (array of charp)
|enable:Enable ICE1712 soundcard. (array of bool)
|omni:Enable Midiman M-Audio Delta Omni I/O support. (array of bool)
|cs8427_timeout:Define reset timeout for cs8427 chip in msec resolution. (array of int)
|model:Use the given board model. (array of charp)
|dxr_enable:Enable DXR support for Terratec DMX6FIRE. (array of int)
}}

{{Matrix:Soundcard|name=ICE1712|module=ice1712}}
* KDE users may use KEnvy24 utility from [http://sourceforge.net/projects/kenvy24/ SourceForge]

Matrix:Module-ice1712

2011-10-17T16:17:28Z

Dominique: /* Added link to the KEnvy24 here */

{| align="right"
| __TOC__
|}

{{Template:Modinfo
|module=ice1712
|description=ICEnsemble ICE1712 (Envy24)
|author=Jaroslav Kysela
|index:Index value for ICE1712 soundcard. (array of int)
|id:ID string for ICE1712 soundcard. (array of charp)
|enable:Enable ICE1712 soundcard. (array of bool)
|omni:Enable Midiman M-Audio Delta Omni I/O support. (array of bool)
|cs8427_timeout:Define reset timeout for cs8427 chip in msec resolution. (array of int)
|model:Use the given board model. (array of charp)
|dxr_enable:Enable DXR support for Terratec DMX6FIRE. (array of int)
}}

{{Matrix:Soundcard|name=ICE1712|module=ice1712}}
===Links for ICE1712 module===
* KDE users may use KEnvy24 utility from [http://sourceforge.net/projects/kenvy24/ SourceForge]

Matrix:Soundcard

2011-10-17T16:13:11Z

Dominique: /* Specific Links - Removed */

<noinclude>{| align="right"
| __TOC__
|}
==Template Matrix:Soundcard==

This is the generic ALSA module template which is intended to give an overview for '''all''' sound modules.

If you want to add specific hardware information or information for a specific module, please '''DO NOT modify''' this template. Add extra information above and/or bellow to the specific Matrix:Module-* page instead. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

</noinclude>==Introduction for {{{name|unknown}}} soundcard==

There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the [http://www.tldp.org/ Kernel-HOWTO] for details of how to compile a kernel.

'''You must turn on the sound support soundcore module.''' This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.

Most modern distros come with <tt>soundcore</tt> compiled as a module. You can check this in numerous ways. The easiest way is to type:

modinfo soundcore

If this command returns that you have this module, then you don't need to recompile your kernel.

==Quick installation==

Type the following commands in the shell of your choice.

{{Note|
''If you are using Hg ([http://www.selenic.com/mercurial/ Mercurial]) then you need to type:''

<nowiki>./hgcompile "or" make build</nowiki>

''instead of:''

<nowiki>./configure</nowiki>
|NB}}

Make a directory to store the alsa source code in:

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .

Now unzip and install the <tt>alsa-driver</tt> package:

bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards={{{module|unknown}}} --with-sequencer=yes ; make ; make install

{{Note|
''If you are using drivers before 0.9.4 then you need to run:''

<nowiki>./snddevices</nowiki>
|NB}}

The <tt>snddevices</tt> script sets the permissions for the devices it creates to root. If you use <tt>devfs</tt> then you should not run the <tt>snddevices</tt> script. Otherwise run:

chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi

Now unzip and install the <tt>alsa-lib</tt> package:

cd ..
bunzip2 alsa-lib-xxx
tar -xf alsa-lib-xxx
cd alsa-lib-xxx
./configure ; make ; make install

Now unzip and install the <tt>alsa-utils</tt> package:

cd ..
bunzip2 alsa-utils-xxx
tar -xf alsa-utils-xxx
cd alsa-utils-xxx
./configure ; make ; make install

Now insert the modules into the kernel:

modprobe snd-{{{module|unknown}}} ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>modprobe snd-card-</nowiki>{{{module|unknown}}}
|NB}}

Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example <tt>alsamixer</tt> from the <tt>alsa-utils</tt> package. Note that some usb-audio devices do not have internal mixer controls. Run:

alsamixer

You can also look at the utils/alsasound file. This script is designed for the ''RedHat Linux'' distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.

===Setting up modprobe and kmod support===

Before you send a mail complaining that "I don't have <tt>/etc/modules.conf</tt>, where do I find it ……" ‒ the <tt>/etc/conf.modules</tt> has been deprecated with a few distro's, but in your case it may still be <tt>/etc/conf.modules</tt>. Basically they are both the same, but recent version of <tt>modutils</tt> use <tt>/etc/modules.conf</tt> instead. Nothing to worry about as such, optionally please update to the latest version of <tt>modutils</tt>. This should solve your problem.

Here's the example for this card. Copy and paste this to the bottom of your <tt>/etc/modules.conf</tt> file.

{{Note|'''Debian GNU/Linux users''' need to save this information into a file in the <tt>/etc/modutils/</tt> directory (eg. <tt>/etc/modutils/alsa</tt>) and run <tt>update-modules</tt>. 

Note also that the kernel module '''soundcore''' has been renamed in Debian kernels >2.6.23 into '''snd'''. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to '''snd.ko'''}}

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-{{{module|unknown}}}
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
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

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>snd-card-</nowiki>{{{module|unknown}}}
|NB}}

To copy and paste the above to your <tt>/etc/modules.conf</tt> file follow these [http://www.alsa-project.org/alsa-doc/doc-php/file-edit.php instructions].

==modules.conf==

This is a short explanation of what happens in the <tt>/etc/modules.conf</tt> file.

===Native devices===

After the main multiplexer is loaded, its code automatically requests the top level sound card module. String <tt>snd-card-''%i''</tt> is requested for native devices where ''%i'' is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String <tt>sound-slot-''%i''</tt> is requested for native devices where ''%i'' is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String <tt>id</tt> (or <tt>snd_id</tt>) lets you set the name of the card which is then returned in the <tt>/proc/asound/cards</tt> file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the <tt>INSTALL</tt> file or above.

username@hostname# pico /etc/modules.conf

# ALSA portion
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-cmipci
options snd-cmipci id="first" mpu_port=0x330

# OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1

{{Note|
''For drivers older than 0.9.0rc5 use:''

<nowiki>options snd-cmipci snd_id="first" snd_mpu_port=0x330</nowiki>
|NB}}

{{Note|The "<tt>snd_</tt>" prefix has been removed from the module options to fit with the kernel standard.|NB}}

===Autoloading OSS/free emulation===

At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: <tt>snd-pcm1-oss</tt>. String <tt>sound-service-''%i''-''%i''</tt> is required for OSS/Free service where the first ''%i'' is the slot number/sound card number and the second ''%i'' is the service number.

username@hostname# pico /etc/modules.conf

# OSS/Free portion - card #1
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

# OSS/Free portion - card #2 (cmipci)
alias sound-slot-1 snd-card-1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

The alias for <tt>snd-seq-oss</tt> is not necessary on the second device, because there is only one <tt>/dev/sequencer</tt> regardless how many devices you have.

===The .asoundrc file===

[[Asoundrc|This file]] allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The <tt>.asoundrc</tt> file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in <tt>alsa-lib</tt>. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.

Below is the most basic definition (only example - not required to define at all).

Make a file called <tt>.asoundrc</tt> in your home and/or root directory:

vi ~/.asoundrc

Copy and paste the following into the file, then save it:

pcm.{{{module|unkown}}} {
type hw
card 0
}

ctl.{{{module|uknown}}} {
type hw
card 0
}

==Links==
[[Category:Module]]
'''Generic'''

* Keep up to date with the news at [http://www.mstation.org/ M-Station]
* The most current book about Linux audio is [http://www.nostarch.com/lms.htm Linux Music and Sound] (September 2000)
* Find more applications at [http://sound.condorow.net/ Sound & MIDI Software For Linux SourceForge]
* For professional quality, low latency audio routing use [http://jackaudio.org/ JACK] ‒ the “Jack Audio Connection Kit”.

'''Specific'''
* [[Special:Whatlinkshere/Matrix:{{PAGENAME}}|Users of this module]]
* [http://www-old.alsa-project.org/alsa-doc/doc-php/template.php?module={{{module}}}#notes Old User contributed notes] at www-old.alsa-project.org (old page)<noinclude>

==Template Matrix:Soundcard – bottom notes==

If you have additional ''specific'' links, add them directly after this template to the specific Matrix:Module-* page. You can also add specific hardware notes to paragraphs below. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

'''DO NOT modify''' this template with specific module information.
</noinclude>

Matrix:Soundcard

2011-10-17T16:01:22Z

Dominique: /* Links - Removed ICE 1712 specific info */

<noinclude>{| align="right"
| __TOC__
|}
==Template Matrix:Soundcard==

This is the generic ALSA module template which is intended to give an overview for '''all''' sound modules.

If you want to add specific hardware information or information for a specific module, please '''DO NOT modify''' this template. Add extra information above and/or bellow to the specific Matrix:Module-* page instead. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

</noinclude>==Introduction for {{{name|unknown}}} soundcard==

There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the [http://www.tldp.org/ Kernel-HOWTO] for details of how to compile a kernel.

'''You must turn on the sound support soundcore module.''' This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.

Most modern distros come with <tt>soundcore</tt> compiled as a module. You can check this in numerous ways. The easiest way is to type:

modinfo soundcore

If this command returns that you have this module, then you don't need to recompile your kernel.

==Quick installation==

Type the following commands in the shell of your choice.

{{Note|
''If you are using Hg ([http://www.selenic.com/mercurial/ Mercurial]) then you need to type:''

<nowiki>./hgcompile "or" make build</nowiki>

''instead of:''

<nowiki>./configure</nowiki>
|NB}}

Make a directory to store the alsa source code in:

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .

Now unzip and install the <tt>alsa-driver</tt> package:

bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards={{{module|unknown}}} --with-sequencer=yes ; make ; make install

{{Note|
''If you are using drivers before 0.9.4 then you need to run:''

<nowiki>./snddevices</nowiki>
|NB}}

The <tt>snddevices</tt> script sets the permissions for the devices it creates to root. If you use <tt>devfs</tt> then you should not run the <tt>snddevices</tt> script. Otherwise run:

chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi

Now unzip and install the <tt>alsa-lib</tt> package:

cd ..
bunzip2 alsa-lib-xxx
tar -xf alsa-lib-xxx
cd alsa-lib-xxx
./configure ; make ; make install

Now unzip and install the <tt>alsa-utils</tt> package:

cd ..
bunzip2 alsa-utils-xxx
tar -xf alsa-utils-xxx
cd alsa-utils-xxx
./configure ; make ; make install

Now insert the modules into the kernel:

modprobe snd-{{{module|unknown}}} ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>modprobe snd-card-</nowiki>{{{module|unknown}}}
|NB}}

Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example <tt>alsamixer</tt> from the <tt>alsa-utils</tt> package. Note that some usb-audio devices do not have internal mixer controls. Run:

alsamixer

You can also look at the utils/alsasound file. This script is designed for the ''RedHat Linux'' distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.

===Setting up modprobe and kmod support===

Before you send a mail complaining that "I don't have <tt>/etc/modules.conf</tt>, where do I find it ……" ‒ the <tt>/etc/conf.modules</tt> has been deprecated with a few distro's, but in your case it may still be <tt>/etc/conf.modules</tt>. Basically they are both the same, but recent version of <tt>modutils</tt> use <tt>/etc/modules.conf</tt> instead. Nothing to worry about as such, optionally please update to the latest version of <tt>modutils</tt>. This should solve your problem.

Here's the example for this card. Copy and paste this to the bottom of your <tt>/etc/modules.conf</tt> file.

{{Note|'''Debian GNU/Linux users''' need to save this information into a file in the <tt>/etc/modutils/</tt> directory (eg. <tt>/etc/modutils/alsa</tt>) and run <tt>update-modules</tt>. 

Note also that the kernel module '''soundcore''' has been renamed in Debian kernels >2.6.23 into '''snd'''. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to '''snd.ko'''}}

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-{{{module|unknown}}}
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
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

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>snd-card-</nowiki>{{{module|unknown}}}
|NB}}

To copy and paste the above to your <tt>/etc/modules.conf</tt> file follow these [http://www.alsa-project.org/alsa-doc/doc-php/file-edit.php instructions].

==modules.conf==

This is a short explanation of what happens in the <tt>/etc/modules.conf</tt> file.

===Native devices===

After the main multiplexer is loaded, its code automatically requests the top level sound card module. String <tt>snd-card-''%i''</tt> is requested for native devices where ''%i'' is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String <tt>sound-slot-''%i''</tt> is requested for native devices where ''%i'' is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String <tt>id</tt> (or <tt>snd_id</tt>) lets you set the name of the card which is then returned in the <tt>/proc/asound/cards</tt> file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the <tt>INSTALL</tt> file or above.

username@hostname# pico /etc/modules.conf

# ALSA portion
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-cmipci
options snd-cmipci id="first" mpu_port=0x330

# OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1

{{Note|
''For drivers older than 0.9.0rc5 use:''

<nowiki>options snd-cmipci snd_id="first" snd_mpu_port=0x330</nowiki>
|NB}}

{{Note|The "<tt>snd_</tt>" prefix has been removed from the module options to fit with the kernel standard.|NB}}

===Autoloading OSS/free emulation===

At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: <tt>snd-pcm1-oss</tt>. String <tt>sound-service-''%i''-''%i''</tt> is required for OSS/Free service where the first ''%i'' is the slot number/sound card number and the second ''%i'' is the service number.

username@hostname# pico /etc/modules.conf

# OSS/Free portion - card #1
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

# OSS/Free portion - card #2 (cmipci)
alias sound-slot-1 snd-card-1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

The alias for <tt>snd-seq-oss</tt> is not necessary on the second device, because there is only one <tt>/dev/sequencer</tt> regardless how many devices you have.

===The .asoundrc file===

[[Asoundrc|This file]] allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The <tt>.asoundrc</tt> file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in <tt>alsa-lib</tt>. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.

Below is the most basic definition (only example - not required to define at all).

Make a file called <tt>.asoundrc</tt> in your home and/or root directory:

vi ~/.asoundrc

Copy and paste the following into the file, then save it:

pcm.{{{module|unkown}}} {
type hw
card 0
}

ctl.{{{module|uknown}}} {
type hw
card 0
}

===Specific Links===
* KDE users may use KEnvy24 utility from [http://sourceforge.net/projects/kenvy24/ SourceForge]

==Links==
[[Category:Module]]
'''Generic'''

* Keep up to date with the news at [http://www.mstation.org/ M-Station]
* The most current book about Linux audio is [http://www.nostarch.com/lms.htm Linux Music and Sound] (September 2000)
* Find more applications at [http://sound.condorow.net/ Sound & MIDI Software For Linux SourceForge]
* For professional quality, low latency audio routing use [http://jackaudio.org/ JACK] ‒ the “Jack Audio Connection Kit”.

'''Specific'''
* [[Special:Whatlinkshere/Matrix:{{PAGENAME}}|Users of this module]]
* [http://www-old.alsa-project.org/alsa-doc/doc-php/template.php?module={{{module}}}#notes Old User contributed notes] at www-old.alsa-project.org (old page)<noinclude>

==Template Matrix:Soundcard – bottom notes==

If you have additional ''specific'' links, add them directly after this template to the specific Matrix:Module-* page. You can also add specific hardware notes to paragraphs below. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

'''DO NOT modify''' this template with specific module information.
</noinclude>

Matrix:Soundcard

2011-10-17T16:00:34Z

Dominique: /* Added specific link from Matrix:Soundcard */

<noinclude>{| align="right"
| __TOC__
|}
==Template Matrix:Soundcard==

This is the generic ALSA module template which is intended to give an overview for '''all''' sound modules.

If you want to add specific hardware information or information for a specific module, please '''DO NOT modify''' this template. Add extra information above and/or bellow to the specific Matrix:Module-* page instead. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

</noinclude>==Introduction for {{{name|unknown}}} soundcard==

There are two ways of getting Linux drivers to work, you can either compile them into the kernel or build them separately as modules. Read the [http://www.tldp.org/ Kernel-HOWTO] for details of how to compile a kernel.

'''You must turn on the sound support soundcore module.''' This is in the kernel. Look in the sound drivers directory and it should be the first option. Most people enable the module setting. That way you can load and unload the module manually if you have multiple soundcards/devices or if you intend to debug or use cutting edge software which may cause your drivers to halt sometimes. Of course it also means you have more control of your system.

Most modern distros come with <tt>soundcore</tt> compiled as a module. You can check this in numerous ways. The easiest way is to type:

modinfo soundcore

If this command returns that you have this module, then you don't need to recompile your kernel.

==Quick installation==

Type the following commands in the shell of your choice.

{{Note|
''If you are using Hg ([http://www.selenic.com/mercurial/ Mercurial]) then you need to type:''

<nowiki>./hgcompile "or" make build</nowiki>

''instead of:''

<nowiki>./configure</nowiki>
|NB}}

Make a directory to store the alsa source code in:

cd /usr/src
mkdir alsa
cd alsa
cp /downloads/alsa-* .

Now unzip and install the <tt>alsa-driver</tt> package:

bunzip2 alsa-driver-xxx
tar -xf alsa-driver-xxx
cd alsa-driver-xxx
./configure --with-cards={{{module|unknown}}} --with-sequencer=yes ; make ; make install

{{Note|
''If you are using drivers before 0.9.4 then you need to run:''

<nowiki>./snddevices</nowiki>
|NB}}

The <tt>snddevices</tt> script sets the permissions for the devices it creates to root. If you use <tt>devfs</tt> then you should not run the <tt>snddevices</tt> script. Otherwise run:

chmod a+rw /dev/dsp /dev/mixer /dev/sequencer /dev/midi

Now unzip and install the <tt>alsa-lib</tt> package:

cd ..
bunzip2 alsa-lib-xxx
tar -xf alsa-lib-xxx
cd alsa-lib-xxx
./configure ; make ; make install

Now unzip and install the <tt>alsa-utils</tt> package:

cd ..
bunzip2 alsa-utils-xxx
tar -xf alsa-utils-xxx
cd alsa-utils-xxx
./configure ; make ; make install

Now insert the modules into the kernel:

modprobe snd-{{{module|unknown}}} ; modprobe snd-pcm-oss ; modprobe snd-mixer-oss ; modprobe snd-seq-oss

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>modprobe snd-card-</nowiki>{{{module|unknown}}}
|NB}}

Now adjust your soundcard's volume levels. All mixer channels are muted by default. You must use a native mixer program to unmute appropriate channels, for example <tt>alsamixer</tt> from the <tt>alsa-utils</tt> package. Note that some usb-audio devices do not have internal mixer controls. Run:

alsamixer

You can also look at the utils/alsasound file. This script is designed for the ''RedHat Linux'' distribution, but it can also be used with other distributions which use System V style rc init scripts. This will allow you to load your modules at boot time. If you don't want to do this you can of course compile them into the kernel instead and save yourself the hassle of coming to terms with the rc init scripts.

===Setting up modprobe and kmod support===

Before you send a mail complaining that "I don't have <tt>/etc/modules.conf</tt>, where do I find it ……" ‒ the <tt>/etc/conf.modules</tt> has been deprecated with a few distro's, but in your case it may still be <tt>/etc/conf.modules</tt>. Basically they are both the same, but recent version of <tt>modutils</tt> use <tt>/etc/modules.conf</tt> instead. Nothing to worry about as such, optionally please update to the latest version of <tt>modutils</tt>. This should solve your problem.

Here's the example for this card. Copy and paste this to the bottom of your <tt>/etc/modules.conf</tt> file.

{{Note|'''Debian GNU/Linux users''' need to save this information into a file in the <tt>/etc/modutils/</tt> directory (eg. <tt>/etc/modutils/alsa</tt>) and run <tt>update-modules</tt>. 

Note also that the kernel module '''soundcore''' has been renamed in Debian kernels >2.6.23 into '''snd'''. A workaround is to put a symlink at /lib/modules/x.x.xx/kernel/sound/soundcore.ko pointing to '''snd.ko'''}}

# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-{{{module|unknown}}}
# module options should go here

# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0

# card #1
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

{{Note|
''For drivers older than 0.9.0beta11 use:''

<nowiki>snd-card-</nowiki>{{{module|unknown}}}
|NB}}

To copy and paste the above to your <tt>/etc/modules.conf</tt> file follow these [http://www.alsa-project.org/alsa-doc/doc-php/file-edit.php instructions].

==modules.conf==

This is a short explanation of what happens in the <tt>/etc/modules.conf</tt> file.

===Native devices===

After the main multiplexer is loaded, its code automatically requests the top level sound card module. String <tt>snd-card-''%i''</tt> is requested for native devices where ''%i'' is the sound card number, counted from zero (the first sound card) to seven (the eighth sound card). String <tt>sound-slot-''%i''</tt> is requested for native devices where ''%i'' is slot number for the corresponding ALSA owner (which is basically the sound card number). The options line allows you to set various configuration options before the module is loaded. String <tt>id</tt> (or <tt>snd_id</tt>) lets you set the name of the card which is then returned in the <tt>/proc/asound/cards</tt> file, i.e. to user space applications. Other options may be available depending on the specific card. Options for these cards are found in the <tt>INSTALL</tt> file or above.

username@hostname# pico /etc/modules.conf

# ALSA portion
alias snd-card-0 snd-hda-intel
alias snd-card-1 snd-cmipci
options snd-cmipci id="first" mpu_port=0x330

# OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1

{{Note|
''For drivers older than 0.9.0rc5 use:''

<nowiki>options snd-cmipci snd_id="first" snd_mpu_port=0x330</nowiki>
|NB}}

{{Note|The "<tt>snd_</tt>" prefix has been removed from the module options to fit with the kernel standard.|NB}}

===Autoloading OSS/free emulation===

At this point we are finished with the configuration for ALSA native devices, but you may also need autoloading for the OSS/Free emulation modules, an ALSA add-on. At this time only one module does not depend on any others, thus must be loaded separately: <tt>snd-pcm1-oss</tt>. String <tt>sound-service-''%i''-''%i''</tt> is required for OSS/Free service where the first ''%i'' is the slot number/sound card number and the second ''%i'' is the service number.

username@hostname# pico /etc/modules.conf

# OSS/Free portion - card #1
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

# OSS/Free portion - card #2 (cmipci)
alias sound-slot-1 snd-card-1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-12 snd-pcm-oss

The alias for <tt>snd-seq-oss</tt> is not necessary on the second device, because there is only one <tt>/dev/sequencer</tt> regardless how many devices you have.

===The .asoundrc file===

[[Asoundrc|This file]] allows you to have more advanced control over your card/device. For most setups the default, system-wide configuration is sufficient. You may change this file only for special setup. The <tt>.asoundrc</tt> file consists of definitions for the various sound devices available in your system. It also provides access to the pcm plugins in <tt>alsa-lib</tt>. These allow you to do tricky things like combine your cards into one or access multiple I/O streams on your multi-channel card.

Below is the most basic definition (only example - not required to define at all).

Make a file called <tt>.asoundrc</tt> in your home and/or root directory:

vi ~/.asoundrc

Copy and paste the following into the file, then save it:

pcm.{{{module|unkown}}} {
type hw
card 0
}

ctl.{{{module|uknown}}} {
type hw
card 0
}

===Specific Links===
* KDE users may use KEnvy24 utility from [http://sourceforge.net/projects/kenvy24/ SourceForge]

==Links==
[[Category:Module]]
'''Generic'''

* Keep up to date with the news at [http://www.mstation.org/ M-Station]
* The most current book about Linux audio is [http://www.nostarch.com/lms.htm Linux Music and Sound] (September 2000)
* Find more applications at [http://sound.condorow.net/ Sound & MIDI Software For Linux SourceForge]
* For professional quality, low latency audio routing use [http://jackaudio.org/ JACK] ‒ the “Jack Audio Connection Kit”.
* KDE users may use KEnvy24 utility from [http://sourceforge.net/projects/kenvy24/ SourceForge]

'''Specific'''
* [[Special:Whatlinkshere/Matrix:{{PAGENAME}}|Users of this module]]
* [http://www-old.alsa-project.org/alsa-doc/doc-php/template.php?module={{{module}}}#notes Old User contributed notes] at www-old.alsa-project.org (old page)<noinclude>

==Template Matrix:Soundcard – bottom notes==

If you have additional ''specific'' links, add them directly after this template to the specific Matrix:Module-* page. You can also add specific hardware notes to paragraphs below. Please read the [[Matrix:Description|Universal Soundcard Description]] for more details.

'''DO NOT modify''' this template with specific module information.
</noinclude>

Matrix Talk:Soundcard

2010-12-29T19:00:10Z

Dominique: /* KEnvy24i */

== Wiki ==

Hi!

Maybe I'm too much used to Wikipedia, but shouldn't this be Template:Soundcard instead of [[Matrix:Soundcard]]? Otherwise one might get confused and edit this page by mistake...

Greetings, [[User:Y2kbug|Andreas]] 20:21, 24 July 2007 (CEST)

-- I tried to separate matrix pages and Matrix: is different namespace (mainly used for the search function). I don't want to change name at this moment. [[User:Perex]]

=== KEnvy24 ===
The following did appear in the link section of every sound card :

"KDE users may use KEnvy24 utility from SourceForge"

This is completely silly because KEnvy24 is a mixer for the Envy24 chip (like MAudio Audiophile 96). Even with a card like the MAudio Audiophile 192 (Envy24HT/PT), KEnvy24 will fail with an error message like what it cannot find some Envy24 sound card.

So, please remove this line from this page. --[[User:Dominique|Dominique]] 20:00, 29 December 2010 (CET)

Matrix Talk:Module-ice1724

2010-12-13T20:35:19Z

Dominique: /* envy24control and kenvy24gui */

Matrix Talk:Module-usb-audio

2009-08-10T21:45:06Z

Dominique: New page: Please, can someone explain what is "async unlink mode" intended for.

Please, can someone explain what is "async unlink mode" intended for.

Talk:Asoundrc

2009-05-23T15:58:46Z

Dominique: /* Bindings explained */

== Bindings explained ==
Hi, thanks for this useful article.
It is something that I don't get. In the asoundrc example file, I can read "They have been split into top row and bottom row with channels 0-7+16-25 on rme9652_0 and channels 8-15+26-27 on rme9652_1." But it is no channel numbered 26 or 27 into this asoudrc.

If I understand well the code into the file, both sound cards are using the same virtual stereo channels 24 and 25. And we have 27 bindings for 25 channels. --[[User:Dominique|Dominique]] 17:53, 23 May 2009 (CEST)

Talk:Asoundrc

2009-05-23T15:53:18Z

Dominique: /* Bindings explained */

== Bindings explained ==
Hi, thanks for this useful article.
It is something that I don't get. In the asoundrc example file, I can read "They have been split into top row and bottom row with channels 0-7+16-25 on rme9652_0 and channels 8-15+26-27 on rme9652_1." But it is no channel numbered 26 or 27 into this asoudrc.

If I understand well the code into the file, both sound cards are using the same stereo channels 24 and 25. And we have 27 bindings for 25 channels. --[[User:Dominique|Dominique]] 17:53, 23 May 2009 (CEST)

Talk:Asoundrc

2009-05-23T15:52:58Z

Dominique: bindings explained

== Bindings explained ==
Hi, thanks for this useful article.
It is something that I don't get. In the asoundrc example file, I can read "They have been split into top row and bottom row with channels 0-7+16-25 on rme9652_0 and channels 8-15+26-27 on rme9652_1." But it is no channel numbered 26 or 27 into this asoudrc.

If I understand well the code into the file, both sound cards are using the same stereo channels 24 and 25. And we have 27 bindings for 25 channels.

User:Dominique

2008-12-18T18:54:48Z

Dominique:

What to say?

It is several years ago that I am using GNU/linux. And very happy with it.

I was learning radio-electricity and electronics because I was and still is passionate by the sound. Later, I learned even more into electronics and processors. I learned music too, classical when I was young, some more modern style like blues and jazz some years later.

But I prefer to think about artistic or philosophical issues than about electronics, so I am working with Caterpillar like machines for living.

I do have several hobbies: I love to go for a walk and making music. They are the 2 only things that made me really happy. Well almost, I love my family too.

Electronics and computers are also 2 of my hobbies. I made some tubes guitar amps. The next step will be to put a dsp into such an amp.

I forgot almost reading. I read a lot of books, mainly comics and books about political facts, psychology and philosophy.

Oh yes! religiously speaking, I am a free thinker. As such, I don't care much about what peoples are saying but much more about what they are doing. I call this the prof by the act!

What else? Just ask!

User:Dominique

2008-12-18T18:49:28Z

Dominique: New page: What to say? It is several years ago that I am using GNU/linux. And very happy with it. I was learning radio-electricity and electronics because I was and still is passionate by the soun...

What to say?

It is several years ago that I am using GNU/linux. And very happy with it.

I was learning radio-electricity and electronics because I was and still is passionate by the sound. Later, I learned even more into electronics and processors.

But I prefer to think about artistic or philosophical issues than about electronics, so I am working with Caterpillar like machines for living.

In my spar time, I do have several hobbies: I love to go for a walk and making music. They are the 2 only things that made me really happy. Well almost, I love my family too.

Electronics and computers are also 2 of my hobbies. I made some tubes guitar amps. The next step will be to put a dsp into such an amp.

I forgot almost reading. I read a lot of books, mainly comics and books about political facts, psychology and philosophy.

Oh yes! religiously speaking, I am a free thinker.

What else? Just ask!

Matrix Talk:Module-ice1724

2008-12-18T18:24:57Z

Dominique: /* envy24control and kenvy24gui */

==envy24control and kenvy24gui==
I cannot edit the end of the page. kenvy24gui work only with ice1712 sound cards, it will not even start with an ice1724 soundcard. See http://kenvy24.wiki.sourceforge.net/kenvy24+actually+supports+these+cards

The same apply to envy24control that work only with ice1712 sound cards.

So, the statement that users of this module can use kenvy24gui into the links section is wrong.

The conclusion for me is simple. I will not waste my time anymore with this card and buy something else !

Another thing that is irritating me is M-Audio complete lack of linux support and linux understanding.

--[[User:Dominique|Dominique]] 18:27, 18 December 2008 (CET)

Matrix Talk:Module-ice1724

2008-12-18T17:41:13Z

Dominique:

==envy24control and kenvy24gui==
I cannot edit the end of the page. kenvy24gui work only with ice1712 sound cards, it will not even start with an ice1724 soundcard. See http://kenvy24.wiki.sourceforge.net/kenvy24+actually+supports+these+cards

The same apply to envy24control that work only with ice1712 sound cards.

So, the statement that users of this module can use kenvy24gui into the links section is wrong.

The conclusion for me is simple. I will not waste my time anymore with this card and buy something else !

Another thing that is irritating me is M-Audio complete lac of linux support and linux understanding.

--[[User:Dominique|Dominique]] 18:27, 18 December 2008 (CET)

Matrix Talk:Module-ice1724

2008-12-18T17:27:40Z

Dominique: New page: I cannot edit the end of the page. kenvy24gui work only with ice1712 sound cards, it will not even start with an ice1724 soundcard. See http://kenvy24.wiki.sourceforge.net/kenvy24+actually...

I cannot edit the end of the page. kenvy24gui work only with ice1712 sound cards, it will not even start with an ice1724 soundcard. See http://kenvy24.wiki.sourceforge.net/kenvy24+actually+supports+these+cards

So, the statement that users of this module can use kenvy24gui into the links section is wrong.

--[[User:Dominique|Dominique]] 18:27, 18 December 2008 (CET)