/[gentoo]/xml/htdocs/doc/en/alsa-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/alsa-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.21 Revision 1.59
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.21 2003/11/23 16:30:50 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/alsa-guide.xml,v 1.59 2005/07/26 17:28:11 vanquirius Exp $ -->
3
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 5
5<guide link = "/doc/en/alsa-guide.xml"> 6<guide link="/doc/en/alsa-guide.xml">
6<title>Gentoo Linux ALSA Guide</title> 7<title>Gentoo Linux ALSA Guide</title>
8
7<author title="Author"> 9<author title="Author">
8 <mail link="zu@pandora.be">Vincent Verleye</mail> 10 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
9</author> 11</author>
10<author title="Author">
11 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
12</author>
13<author title="Author">
14 <mail link="agenkin@gentoo.org">Arcady Genkin</mail>
15</author>
16<author title="Editor"><!-- zhen@gentoo.org -->
17 John P. Davis
18</author>
19<author title="Editor">
20 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
21</author>
22<author title="Editor">
23 <mail link="bennyc@gentoo.org">Benny Chuang</mail>
24</author>
25<author title="Editor">
26 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
27</author>
28 12
13<abstract>
14This document helps a user setup ALSA on Gentoo Linux.
15</abstract>
16
17<!-- The content of this document is licensed under the CC-BY-SA license -->
18<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
29<license/> 19<license/>
30 20
31<abstract>
32This guide will show you how to set up the Advanced Linux Sound Architecture
33(ALSA) on Gentoo Linux. In addition to the Gentoo Linux Desktop Configuration
34Guide, this guide is supposed to give you more information on this subject.
35</abstract>
36
37<version>1.3.4</version> 21<version>2.7</version>
38<date>November 23, 2003</date> 22<date>2005-07-26</date>
39 23
40<chapter> 24<chapter>
41<title>Introduction</title> 25<title>Introduction</title>
42<section> 26<section>
43<title>What is ALSA?</title> 27<title>What is ALSA?</title>
44<body> 28<body>
45 29
46<p> 30<p>
47The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux 31ALSA, which stands for <e>Advanced Linux Sound Architecture</e>, provides
48sound subsystem by rewriting large chunks of it. It is anticipated that ALSA 32audio and MIDI (<e>Musical Instrument Digital Interface</e>) functionality to
49will make it into Linux kernel 2.6.x (or 3.x.x -- whichever comes first) as it 33the Linux operating system. ALSA is the default sound subsystem in the 2.6
50becomes ready. 34kernel thereby replacing OSS (<e>Open Sound System</e>), which was used in the
51</p> 352.4 kernels.
52
53<p> 36</p>
54ALSA provides audio and MIDI functionality for Linux. 37
55</p> 38<p>
56 39ALSA's main features include efficient support for all types of audio
40interfaces ranging from consumer sound cards to professional sound
41equipment, fully modularized drivers, SMP and thread safety, backward
42compatibility with OSS and a user-space library <c>alsa-lib</c> to make
43application development a breeze.
57<p> 44</p>
58Quoted from <uri>http://www.alsa-project.org</uri>, ALSA has the following 45
59features: 46</body>
47</section>
48<section>
49<title>ALSA on Gentoo</title>
50<body>
51
52<p>
53One of Gentoo's main strengths lies in giving the user maximum control over
54how a system is installed/configured. ALSA on Gentoo follows the same
55principle. There are two ways you can get ALSA support up and running on your
56system. We shall look at them in detail in the next chapter.
57</p>
58
59</body>
60</section>
61</chapter>
62
63<chapter>
64<title>Installing ALSA</title>
65<section>
66<title>Options</title>
67<body>
68
69<warn>
70The methods shown below are mutually exclusive. You cannot have ALSA compiled
71in your kernel and use <c>media-sound/alsa-driver</c>. It <e>will</e> fail.
72</warn>
73
74<p>
75The two options are :
76</p>
77
78<ol>
79 <li>
80 Use ALSA provided by your kernel. This is the preferred/recommended
81 method.
82 </li>
83 <li>
84 Use Gentoo's <c>media-sound/alsa-driver</c> package.
85 </li>
86</ol>
87
88<p>
89We shall take a peek into both before finally deciding on one.
90</p>
91
92<p>
93If you were to use ALSA provided by the kernel, the following are the pros and
94cons :
95</p>
96
97<table>
98<tr>
99 <th>Kernel ALSA</th>
100 <th>Pros and Cons</th>
101</tr>
102<tr>
103 <th>+</th>
104 <ti>Pretty stable as drivers are integrated into kernel.</ti>
105</tr>
106<tr>
107 <th>+</th>
108 <ti>One shot solution, no repeating emerges.</ti>
109</tr>
110<tr>
111 <th>-</th>
112 <ti>Might be a slightly older version than <c>alsa-driver</c>.</ti>
113</tr>
114</table>
115
116<p>
117And, if you were to use alsa-driver,
118</p>
119
120<table>
121<tr>
122 <th>alsa-driver</th>
123 <th>Pros and Cons</th>
124</tr>
125<tr>
126 <th>+</th>
127 <ti>Latest drivers from the ALSA Project.</ti>
128</tr>
129<tr>
130 <th>-</th>
131 <ti>Every kernel recompile requires a re-emerge of <c>alsa-driver</c>.</ti>
132</tr>
133<tr>
134 <th>-</th>
135 <ti>Needs certain kernel config options disabled to work correctly.</ti>
136</tr>
137</table>
138
139</body>
140</section>
141<section>
142<title>So...</title>
143<body>
144
145<p>
146The main difference between using <c>alsa-driver</c> and ALSA that comes with
147the kernel is that <c>alsa-driver</c> is generally more up to date than the
148version in the kernel. Since this does not make any huge difference as
149such, you are encouraged to use the ALSA provided by the kernel for ease of use.
150Before reporting any sound related issues to <uri
151link="https://bugs.gentoo.org">Gentoo Bugzilla</uri>, please try to reproduce
152them using <c>alsa-driver</c> and file the bug report no matter what the
153result.
154</p>
155
156</body>
157</section>
158<section id="lspci">
159<title>Before you proceed</title>
160<body>
161
162<p>
163Whichever method of install you choose, you need to know what drivers your
164sound card uses. In most cases, sound cards (onboard and otherwise) are PCI
165based and <c>lspci</c> will help you in digging out the required information.
166Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if you don't have it
167installed already. In case you have a USB sound card, <c>lsusb</c> from
168<c>sys-apps/usbutils</c> <e>might</e> be of help. For ISA cards, try using
169<c>sys-apps/isapnptools</c>. Also, the following pages <e>may</e> help users
170with ISA based sound cards.
60</p> 171</p>
61 172
62<ul> 173<ul>
63 <li> 174 <li>
64 Efficient support for all types of audio interfaces, from consumer 175 <uri link="http://www.roestock.demon.co.uk/isapnptools/">The ISAPNPTOOLS
65 soundcards to professional multichannel audio interfaces 176 Page</uri>
66 </li>
67 <li>Fully modularized sound drivers</li>
68 <li>SMP and thread-safe design</li>
69 <li>
70 User space library (alsa-lib) to simplify application programming and
71 provide higher level functionality
72 </li>
73 <li>
74 Support for the older OSS API, providing binary compatibility for most OSS
75 programs
76 </li> 177 </li>
178 <li>
179 <uri link="http://www2.linuxjournal.com/article/3269">LinuxJournal PnP
180 Article</uri>
181 </li>
182 <li>
183 <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/x320.html">TLDP Sound
184 HowTo</uri>
185 </li>
77</ul> 186</ul>
78 187
79<p> 188<note>
80There's lots more to ALSA however, like support for Full Duplex playback and 189For ease of use/explanation, we assume the user has a PCI based sound card for
81recording, multiple soundcard support, hardware mixing of streams, extensive 190the remainder of this guide.
82mixer capabilities (to support advanced features of new soundcards), ... 191</note>
192
83</p> 193<p>
194We now proceed to find out details about the sound card.
195</p>
84 196
197<pre caption="Soundcard Details">
198# <i>lspci -v | grep -i audio</i>
1990000:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
200</pre>
201
202<p>
203We now know that the sound card on the machine is a Sound Blaster Live! and
204the card manufacturer is Creative Labs. Head over to the
205<uri link="http://www.alsa-project.org/alsa-doc/"> ALSA Soundcard Matrix</uri>
206page and select Creative Labs from the drop down menu. You will be taken to
207the Creative Labs matrix page where you can see that the SB Live! uses the
208<c>emu10k1</c> module. That is the information we need for now. If you are
209interested in detailed information, you can click on the link next to the
210"Details" and that will take you to the <c>emu10k1</c> specific page.
211</p>
212
85</body> 213</body>
86</section>
87<section> 214</section>
88<title>Why use ALSA?</title> 215<section id="kernel">
89<body> 216<title>Using ALSA provided by your Kernel</title>
90
91<p>
92If your soundcard is supported by the Linux kernel sound system or the
93commercial OSS/4Front sound driver system, which can be found in all 2.4.x
94Linux kernels, you could just aswell build <e>those modules</e> for use with
95your soundcard. If you want this, just read through the <uri
96link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>.
97</p>
98
99<p>
100However, those OSS/4Front drivers have some limitations -- being commercial is
101one. ALSA is an attempt to go beyond these limitations and to do so in an open
102source fashion. ALSA is a fully GPL and LGPL'ed sound driver system, that
103provides a professional quality system for recording, playback, and MIDI
104sequencing.
105</p>
106
107</body> 217<body>
108</section> 218
219<p>
220If you're a person who likes to keep things simple like I do, then this is
221the way to go.
222</p>
223
224<note>
225Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Unless
226you are specifically using the 2.4 profile, <c>gentoo-sources</c> will be a
2272.6 kernel on <e>most</e> architectures. Please check that your kernel is a
2282.6 series kernel. This method will <e>not</e> work on a 2.4 kernel.
229</note>
230
231<p>
232Let us now configure the kernel to enable ALSA.
233</p>
234
235<impo>
236<c>genkernel</c> users should now run <c>genkernel --menuconfig</c> and then follow
237the instructions in <uri link="#doc_chap2_pre3">Kernel Options for ALSA</uri>.
238</impo>
239
240<pre caption="Heading over to the source">
241# <i>cd /usr/src/linux</i>
242# <i>make menuconfig</i>
243</pre>
244
245<note>
246The above example assumes that <path>/usr/src/linux</path> symlink points to
247the kernel sources you want to use. Please ensure the same before proceeding.
248</note>
249
250<p>
251Now we will look at some of the options we will have to enable in the 2.6
252kernel to ensure proper ALSA support for our sound card.
253</p>
254
255<p>
256Please note that for the sake of ease, all examples show ALSA built as modules.
257It is advisable to follow the same as it then allows the use of <c>alsaconf</c>
258which is a boon when you want to configure your card. Please do <e>not</e> skip the <uri
259link="#alsa-config">Configuration</uri> section of this document. If you still
260like to have options built-in, ensure that you make changes to your config
261accordingly.
262</p>
263
264<pre caption="Kernel Options for ALSA">
265Device Drivers ---&gt;
266 Sound ---&gt;
267
268<comment>(This needs to be enabled)</comment>
269&lt;M&gt; Sound card support
270
271<comment>(Make sure OSS is disabled)</comment>
272Open Sound System ---&gt;
273 &lt; &gt; Open Sound System (DEPRECATED)
274
275<comment>(Move one step back and enter ALSA)</comment>
276Advanced Linux Sound Architecture ---&gt;
277 &lt;M&gt; Advanced Linux Sound Architecture
278 <comment>(Select this if you want MIDI sequencing and routing)</comment>
279 &lt;M&gt; Sequencer support
280 <comment>(Old style /dev/mixer* and /dev/dsp* support. Recommended.)</comment>
281 &lt;M&gt; OSS Mixer API
282 &lt;M&gt; OSS PCM (digital audio) API
283
284<comment>(You now have a choice of devices to enable support for. Generally,
285you will have one type of device and not more. If you have more than one
286sound card, please enable them all here.)</comment>
287
288<comment>(Mostly for testing and development purposes, not needed for normal
289users unless you know what you are doing.)</comment>
290Generic devices ---&gt;
291
292<comment>(For ISA Sound cards)</comment>
293ISA devices ---&gt;
294<comment>(IF you had the Gravis, you would select this option)</comment>
295 &lt;M&gt; Gravis UltraSound Extreme
296
297<comment>(Move one level back and into PCI devices. Most sound cards today are
298PCI devices)</comment>
299PCI devices ---&gt;
300 <comment>(We now select the emu10k1 driver for our card)</comment>
301 &lt;M&gt; Emu10k1 (SB Live!, Audigy, E-mu APS)
302 <comment>(Or an Intel card would be)</comment>
303 &lt;M&gt; Intel/SiS/nVidia/AMD/ALi AC97 Controller
304 <comment>(Or if you have a VIA Card)</comment>
305 &lt;M&gt; VIA 82C686A/B, 8233/8235 AC97 Controller
306
307<comment>(Move one level back and select in case you have an USB sound card)</comment>
308USB Devices ---&gt;
309</pre>
310
311<p>
312Now that your options are set, you can (re)compile the kernel and ALSA support
313for your card should be functional once you reboot into the new kernel.
314You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
315see if everything is working as it should.
316</p>
317
318</body>
109<section> 319</section>
110<title>What cards does ALSA support?</title> 320<section id="alsa-driver">
321<title>Using the ALSA Driver package</title>
111<body> 322<body>
112 323
113<p>
114ALSA tries to support as many (new) cards as possible by providing open-source
115drivers. However, some vendors may provide binary-only packages.
116</p> 324<p>
117 325So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
326There are a few minor things to be done to ensure only the drivers for your
327sound card are compiled. Although this is not really necessary, it cuts down
328on the unnecessary drivers that will be compiled otherwise.
118<p> 329</p>
119To know if your card is supported, you can find a Soundcard Matrix of supported 330
120and not-supported cards here: <uri>http://www.alsa-project.org/alsa-doc/</uri>.
121</p> 331<p>
332If you don't have an idea of what drivers your sound card might need, please
333take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
334you have your driver name (<c>emu10k1</c> in our example), edit
335<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>.
336</p>
337
338<pre caption="Adding ALSA_CARDS to make.conf">
339<comment>(For one sound card)</comment>
340ALSA_CARDS="emu10k1"
341<comment>(For more than one, separate names with spaces)</comment>
342ALSA_CARDS="emu10k1 via82xx"
343</pre>
344
345<p>
346If you have compiled your kernel and want to use <c>alsa-driver</c>, please
347ensure the following before proceeding, else <c>alsa-driver</c> is likely to
348fail. The next code listing gives you one way of performing the checks.
349</p>
350
351<note>
352<c>genkernel</c> users can proceed with <uri link="#doc_chap2_pre6">Installing
353alsa-driver</uri> as their configuration is in sync with the one shown below by
354default.
355</note>
356
357<ol>
358 <li>
359 <c>CONFIG_SOUND</c> is set. (Basic Sound support enabled)
360 </li>
361 <li>
362 <c>CONFIG_SOUND_PRIME</c> is not set. (In-built OSS support disabled)
363 </li>
364 <li>
365 <c>CONFIG_SND</c> is not set. (In-built ALSA support disabled)
366 </li>
367 <li>
368 <path>/usr/src/linux</path> points to the kernel you want ALSA working on.
369 </li>
370</ol>
371
372<pre caption=".config checks">
373<comment>(Assuming the linux symlink points to the correct kernel)</comment>
374# <i>cd /usr/src/linux</i>
375# <i>grep SOUND .config</i>
376<comment>(1. is true)</comment>
377CONFIG_SOUND=y
378<comment>(2. is true)</comment>
379CONFIG_SOUND_PRIME is not set
380# <i>grep SND .config</i>
381<comment>(and 3. is true)</comment>
382CONFIG_SND is not set
383</pre>
384
385<p>
386Now all you have to do is type the magic words... and no, it's not abracadabra.
387</p>
388
389<pre caption="Installing alsa-driver">
390# <i>emerge alsa-driver</i>
391</pre>
392
393<impo>
394Please note that you will have to run <c>emerge alsa-driver</c> after every
395kernel (re)compile, as the earlier drivers are deleted.
396</impo>
122 397
123</body> 398</body>
124</section> 399</section>
125</chapter> 400</chapter>
126 401
127<chapter> 402<chapter>
128<title>Installation</title> 403<title>Configuring/Testing ALSA</title>
129<section> 404<section id="alsa-utilities">
130<title>Gentoo USE flags</title> 405<title>ALSA Utilities</title>
131<body>
132
133<p>
134To compile programs with ALSA-support, be sure to add <e>alsa</e> to
135your USE-variable. However, several tools don't support alsa yet, and
136require OSS. ALSA provides OSS-emulation if you define <e>oss</e> in your
137USE-variable before you start.
138</p>
139
140</body> 406<body>
141</section>
142<section>
143<title>Kernel modules</title>
144<body>
145 407
146<p>
147Since we're still using 2.4.x kernel sources, we'll have to compile kernel
148modules and ALSA modules separately. People who are using a 2.5.x kernel can
149do this from within their kernel configuration, since the ALSA modules are
150included in the kernel sources and should be built there.
151</p> 408<p>
152 409<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of
410programs that are highly useful, including the ALSA Initscripts. Hence we
411strongly recommend that you install <c>alsa-utils</c>
153<p> 412</p>
154First we'll make sure that our kernel configuration is ready for use with ALSA. 413
155All you need in your kernel configuration is having Sound Card Support set to 414<pre caption="Install alsa-utils">
156be built as a module (M). This will build <path>soundcore.o</path>. 415# <i>emerge alsa-utils</i>
157</p> 416</pre>
158 417
159<note> 418<note>
160Possibly, this will also work when you built Sound Card Support in the kernel 419If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
161(Y) instead of building it as a module (M). However, the official ALSA 420not compile ALSA as modules, please proceed to the
162documentation suggests building it as a module, since ALSA will try loading it. 421<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
422to configure ALSA. This is made very easy by the existence of the
423<c>alsaconf</c> tool provided by <c>alsa-utils</c>.
163</note> 424</note>
164 425
165<p> 426</body>
166If you already have a working kernel configuration, make sure you remove all 427</section>
167sound drivers (except for Sound Card Support). If you wish to do this without 428<section id="alsa-config">
168having to reboot, you could do like this: 429<title>Configuration</title>
430<body>
431
432<note>
433Please shut down any programs that <e>might</e> access the sound card while
434running <c>alsaconf</c>.
435</note>
436
169</p> 437<p>
170 438The easiest way to configure your sound card is to run <c>alsaconf</c>. Just
171<pre caption="Kernel configuration"> 439type <c>alsaconf</c> in a shell as root.
172# <i>cd /usr/src/linux</i>
173# <i>cp .config ~/</i>
174# <i>make mrproper</i>
175# <i>cp ~/.config .</i>
176# <i>make menuconfig</i>
177</pre>
178
179<p> 440</p>
180Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound 441
181drivers. Exit and say Y to save your kernel configuration. After that, build 442<pre caption="Invoking alsaconf">
182the modules: 443# <i>alsaconf</i>
444</pre>
445
183</p> 446<p>
184 447You will now see a neat menu guided interface that will automatically probe
185<pre caption="Kernel compilation"> 448your devices and try to find out your sound card. You will be asked to pick
186# <i>make dep clean</i> 449your sound card from a list. Once that's done, it will ask you permission to
187# <i>make modules modules_install</i> 450automatically make required changes to <path>/etc/modules.d/alsa</path>.
188</pre> 451It will then adjust your volume settings to optimum levels, run
189 452<c>modules-update</c> and start the <path>/etc/init.d/alsasound</path> service.
453Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA initscript.
190<p> 454</p>
191Before installing your new modules, this last line will delete all your previous 455
192modules, even the ones from a previous ALSA installation. 456</body>
457</section>
458<section id="initscript">
459<title>ALSA Initscript</title>
460<body>
461
193</p> 462<p>
463We're now almost all setup. Whichever method you chose to install ALSA, you'll
464need to have something load your modules or initialize ALSA and restore your
465volume settings when your system comes up. The ALSA Initscript handles all of
466this for you and is called <c>alsasound</c>. Add it to the boot runlevel.
467</p>
468
469<pre caption="Adding ALSA to the boot runlevel">
470# <i>rc-update add alsasound boot</i>
471 * alsasound added to runlevel boot
472 * rc-update complete.
473</pre>
474
475<p>
476Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
477SAVE_ON_STOP variable is set to yes. This saves your sound settings when you
478shutdown your system.
479</p>
480
481</body>
482</section>
483<section>
484<title>Audio Group</title>
485<body>
486
487<p>
488Before we move on to testing, there's one last <e>important</e> thing that needs
489to be setup. Rule of thumb in a *nix OS : Do not run as root unless needed.
490This applies here as well ;) How? Well, most of the times you should be logged
491in as a user and would like to listen to music or access your soundcard. For
492that to happen, you need to be in the "audio" group. At this point, we'll add
493users to the audio group, so that they won't have any issues when they want to
494access sound devices. We'll use <c>gpasswd</c> here and you need to be logged in
495as root for this to work.
496</p>
497
498<pre caption="Adding users to the audio group">
499<comment>(Substitute &lt;username&gt; with your user)</comment>
500# <i>gpasswd -a &lt;username&gt; audio </i>
501Adding user &lt;username&gt; to group audio
502</pre>
503
504</body>
505</section>
506<section>
507<title>Volume Check!</title>
508<body>
509
510<p>
511We've completed all the setups and pre-requisites, so let's fire up ALSA. If
512you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
513does this for you.
514</p>
515
516<pre caption="Start the service">
517<comment>(ALSA as modules)</comment>
518# <i>/etc/init.d/alsasound start</i>
519 * Loading ALSA modules ...
520 * Loading: snd-card-0 ... [ ok ]
521 * Loading: snd-pcm-oss ... [ ok ]
522 * Loading: snd-seq ... [ ok ]
523 * Loading: snd-emu10k1-synth ... [ ok ]
524 * Loading: snd-seq-midi ... [ ok ]
525 * Restoring Mixer Levels ... [ ok ]
526<comment>(ALSA compiled in)</comment>
527# <i>/etc/init.d/alsasound start</i>
528 * Loading ALSA modules ...
529 * Restoring Mixer Levels ... [ ok ]
530</pre>
531
532<p>
533Now that the required things have been taken care of, we need to check up on
534the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this
535purpose.
536</p>
537
538<pre caption="Starting alsamixer">
539<comment>(Opens up a console program. Only required settings are shown)</comment>
540# <i>alsamixer</i>
541</pre>
194 542
195<impo> 543<impo>
196This means, whenever you recompile your kernel later on, you MUST recompile 544If you have issues starting up <c>alsamixer</c> and get errors such as
197<c>alsa-driver</c>. 545alsamixer: function snd_ctl_open failed for default: No such file or directory,
546this is usually an issue with udev setting up the devices. Run <c>killall
547udevd; udevstart</c> to reload <path>/dev</path> entries and fire up
548<c>alsamixer</c>. It should solve the issue.
198</impo> 549</impo>
199 550
200</body>
201</section>
202<section>
203<title>ALSA modules</title>
204<body>
205
206<p>
207Now it's time to install the ALSA drivers for your soundcard(s). If your
208soundcard is PCI, you can find out the name and type of your soundcard by
209looking at the output of <path>/proc/pci</path>.
210</p> 551<p>
211 552This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
212<pre caption="Search for soundcard information"> 553attention to the Master and PCM channels which both have an MM below them.
213# <i>grep audio /proc/pci</i> 554That means they are muted. If you try to play anything with <c>alsamixer</c>
555in this state, you will not hear anything on your speakers.
214</pre> 556</p>
557
558<figure link="/images/docs/alsa-mixermuted.png" short="AlsaMixer Muted" caption="The Alsa Mixer Main Window, Muted"/>
559
560<p>
561Now, we shall unmute the channels, and set volume levels as needed.
562</p>
215 563
216<warn> 564<warn>
217If you had a previous sound setup and there are still non-ALSA sound modules 565Both Master <e>and</e> PCM need to be unmuted and set to audible volume levels
218loaded, unload them <e>now</e>. Check with <c>lsmod</c> and use <c>rmmod</c> 566if you want to hear some output on your speakers.
219to unload all sound-related modules on your system.
220</warn> 567</warn>
221 568
222<p> 569<ul>
223We could simply do an <c>emerge alsa-driver</c> now, this would compile and 570 <li>
224install <e>all</e> ALSA sound drivers. 571 To move between channels, use your left and right arrow keys. (&lt;-
225</p> 572 &amp; -&gt;)
226 573 </li>
227<p> 574 <li>
228However, to save some time, lookup the <e>Module Name</e> of your soundcard(s) 575 To toggle mute, move to the specific channel, for example Master and press
229on the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard 576 the <e>m</e> key on the keyboard.
230Matrix</uri> by following the <e>Details</e> link in the <e>Driver and Docs</e> 577 </li>
231column in the row of the chipset of your soundcard. Mine is <c>snd-emu10k1</c>, 578 <li>
232since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. We'll set 579 To increase and decrease the volume levels, use the up and down arrow keys
233ALSA_CARDS environment to the value of the module name before emerging (but 580 respectively.
234without the snd prefix), so emerge will only compile the drivers we need. 581 </li>
235</p> 582</ul>
236
237<pre caption="Compile correct modules">
238# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i>
239</pre>
240 583
241<note> 584<note>
242You can also add this value in <path>/etc/make.conf</path>, so when you have 585Be careful when setting your Bass and Treble values. 50 is usually a good
243to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>. 586number for both. Extremely high values of Bass may cause <e>jarring</e>
244For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c> 587on speakers that are not designed to handle them.
245</note> 588</note>
246 589
590<p>
591After you're all done, your ALSA Mixer should look similar to the one below.
592Note the 00 instead of the MM and also the volume levels for some optimum
593settings.
594</p>
595
596<figure link="/images/docs/alsa-mixerunmuted.png" short="AlsaMixer Unmuted" caption="Alsa Mixer ready to roll"/>
597
598</body>
599</section>
600<section>
601<title>Sound Check!</title>
602<body>
603
604<p>
605The irritating way to check your soundcard is to see if you can hear static on
606the speakers. This isn't exactly fun, but hey, it tells you the card is
607configured and working.
608</p>
609
610<pre caption="Bring on the static">
611# <i>cat /dev/urandom > /dev/dsp</i>
612</pre>
613
247<note> 614<note>
248When you want to install ALSA drivers for more than one soundcard, you could 615<path>/dev/dsp</path> is a symlink to <path>/dev/sound/dsp</path> and should be
249set ALSA_CARDS to a space-separated list of drivers; like this: <c>env 616automatically created. Try re-directing the output to
250ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c> 617<path>/dev/sound/dsp</path> in case you don't get a "No such file or directory"
618error.
251</note> 619</note>
252 620
621<p>
622You should hear static. Press <c>Ctrl + C</c> to stop. If you don't hear
623anything, now is a good time to go back and check/trace out the issue and
624rectify it.
625</p>
626
627<p>
628Finally. Some music. If everything above is perfect, you should now be able to
629listen to some good music. A quick way to test is to use a command line tool
630like <c>media-sound/madplay</c>. You could also use something more well known
631like <c>mpg123</c> or <c>xmms</c>. If you are an ogg fan, you could use
632<c>ogg123</c> provided by <c>media-sound/vorbis-tools</c>. Use any player you
633are comfortable with. As always, <c>emerge</c> what you need.
634</p>
635
636<pre caption="Getting the software">
637<comment>(Install the applications you want)</comment>
638# <i>emerge madplay mpg123 xmms</i>
639<comment>(To play .ogg files)</comment>
640# <i>emerge vorbis-tools</i>
641</pre>
642
643<p>
644And then play your favorite sound track...
645</p>
646
647<pre caption="Playing Music">
648# <i>madplay -v /mnt/shyam/Music/Paul\ Oakenfold\ -\ Dread\ Rock.mp3</i>
649MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
650 Title: Dread Rock
651 Artist: Paul Oakenfold
652 Album: Matrix Reloaded
653 Year: 2003
654 Genre: Soundtrack
655 Soundtrack
656 00:04:19 Layer III, 160 kbps, 44100 Hz, joint stereo (MS), no CRC
657
658# <i>ogg123 Paul\ Oakenfold\ -\ Dread\ Rock.ogg</i>
659Audio Device: Advanced Linux Sound Architecture (ALSA) output
660
661Playing: Paul Oakenfold - Dread Rock.ogg
662Ogg Vorbis stream: 2 channel, 44100 Hz
663Genre: Soundtrack
664Transcoded: mp3;160
665Title: Dread Rock
666Artist: Paul Oakenfold
667Date: 2003
668Album: Matrix Reloaded
669Time: 00:11.31 [04:28.75] of 04:40.06 (200.6 kbps) Output Buffer 96.9%
670</pre>
671
672</body>
673</section>
674<section>
675<title>ALSA and USE</title>
676<body>
677
678<p>
679You can now add the <c>alsa</c> use flag to <path>/etc/make.conf</path> to
680ensure that your applications that support ALSA get built with it. Some
681architectures like x86 and amd64 have the flag enabled by default.
682</p>
683
684</body>
685</section>
686<section>
687<title>Issues?</title>
688<body>
689
690<p>
691If for some reason you're unable to hear sound, the first thing to do would
692be to check your <uri link="#doc_chap3_pre6">alsamixer</uri> settings. 80% of
693the issues lie with muted channels or low volume. Also check your Window
694Manager's sound applet and verify that volumes are set to audible levels.
695</p>
696
697<p>
698<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path>
699is your best friend. We shall just take a short look at how much info is made
700available to us there.
701</p>
702
703<pre caption="Fun with /proc/asound">
704<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has
705picked up your sound card fine.)</comment>
706# <i>cat /proc/asound/cards</i>
7070 [Live ]: EMU10K1 - Sound Blaster Live!
708 Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
709
710<comment>(If you run ALSA off the kernel like I do and wonder how far behind
711you are from alsa-driver, this displays current running ALSA version)</comment>
712# <i>cat /proc/asound/version</i>
713Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 2005 UTC).
714
715<comment>(ALSA OSS emulation details)</comment>
716# <i>cat /proc/asound/oss/sndstat</i>
717Sound Driver:3.8.1a-980706 (ALSA v1.0.8 emulation code)
718Kernel: Linux airwolf.zion 2.6.11ac1 #2 Wed May 4 00:35:08 IST 2005 i686
719Config options: 0
720
721Installed drivers:
722Type 10: ALSA emulation
723
724Card config:
725Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
726
727Audio devices:
7280: EMU10K1 (DUPLEX)
729
730Synth devices: NOT ENABLED IN CONFIG
731
732Midi devices:
7330: EMU10K1 MPU-401 (UART)
734
735Timers:
7367: system timer
737
738Mixers:
7390: SigmaTel STAC9721/23
740</pre>
741
742</body>
743</section>
744</chapter>
745
746<chapter>
747<title>Other things ALSA</title>
748<section>
749<title>Setting up MIDI support</title>
750<body>
751
752<p>
753If your sound card is one of those that come with on-board MIDI synthesizers
754and you would like to listen to some .mid files, you have to install
755<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
756driver. We need to install it first. If you don't have a hardware synthesizer,
757you can use a virtual one. Please see the section on
758<uri link="#vsynth">Virtual Synthesizers</uri> for more information.
759</p>
760
761<pre caption="Installing awesfx">
762# <i>emerge awesfx</i>
763</pre>
764
253<note> 765<note>
254If you want to have OSS compatibility, make sure to emerge <i>alsa-oss</i>, it 766You will need to copy over SoundFont (SF2) files from your sound card's driver
255is the ALSA/OSS compatibility wrapper. 767CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For
768example a sound font file for the Creative SBLive! card would be 8MBGMSFX.SF2.
256</note> 769</note>
257 770
771<p>
772After copying over the Soundfont files, we can then play a midi file as shown.
773You can also add the <c>asfxload</c> command to
774<path>/etc/conf.d/local.start</path>, so that the sound font is loaded
775every time the system starts up.
776</p>
777
258<note> 778<note>
259If you plan on recompiling your kernels numerous times, it might 779<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e>
260be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This 780be the same in your machine. They are just an example. Please be careful to
261will create a binary package for it. Later, after recompiling your kernel, 781change the path to suit your machine.
262you can just do <c>emerge --usepkg alsa-driver</c> which will install the
263binary package instead of recompiling it completely.
264</note> 782</note>
265 783
266<p> 784<pre caption="Loading Soundfonts">
267After this, the ALSA modules should be installed on your system. 785<comment>(First, copy the Soundfont)</comment>
786# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
787<comment>(We load the specific Soundfont)</comment>
788# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>
789</pre>
790
268</p> 791<p>
792You can now play midi files using a program like <c>aplaymidi</c>. Run
793<c>aplaymidi -l</c> to get a list of available ports and then pick one
794to play the file on.
795</p>
269 796
797<pre caption="Playing MIDI">
798<comment>(Check open ports)</comment>
799# <i>aplaymidi -l</i>
800 Port Client name Port name
801 64:0 EMU10K1 MPU-401 (UART) EMU10K1 MPU-401 (UART)
802 65:0 Emu10k1 WaveTable Emu10k1 Port 0
803 65:1 Emu10k1 WaveTable Emu10k1 Port 1
804 65:2 Emu10k1 WaveTable Emu10k1 Port 2
805 65:3 Emu10k1 WaveTable Emu10k1 Port 3
806<comment>(Pick a port, and play a mid file)</comment>
807# <i> aplaymidi --port=65:0 /mnt/shyam/music/midi/mi2.mid</i>
808</pre>
809
270</body> 810</body>
271</section>
272<section> 811</section>
273<title>Configuration of ALSA</title> 812<section id="vsynth">
274<body> 813<title>Virtual Synthesizers</title>
275
276<p>
277Let's start configuring now to get ALSA working properly. We'll need to edit
278some files, to let our system know about the freshly installed ALSA modules.
279</p>
280
281<p>
282First, install <c>alsa-utils</c> on your system:
283</p>
284
285<pre caption = "Emerging alsa-utils">
286# <i>emerge alsa-utils</i>
287</pre>
288
289<p>
290Hereafter, we need to edit <path>/etc/modules.d/alsa</path>.
291</p>
292
293<warn>
294There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit
295files in <path>/etc/modules.d</path>.
296</warn>
297
298<p>
299Check the ALSA portion <e>at the bottom of the file</e>. By tweaking this line
300you can specify the max number of soundcards you have (generally, just one).
301</p>
302
303<pre caption="At the bottom of /etc/modules.d/alsa">
304<comment>Set this to the correct number of cards.</comment>
305options snd cards_limit=1
306</pre>
307
308<p>
309Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit
310like this:
311</p>
312
313<pre caption="In /etc/modules.d/alsa">
314## and then run `modules-update' command.
315## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
316##
317## ALSA portion
318alias snd-card-0 snd-emu10k1
319<comment>## If you have more than one, add:</comment>
320## alias snd-card-1 snd-intel8x0
321## alias snd-card-2 snd-ens1370
322## OSS/Free portion
323## alias sound-slot-0 snd-card-0
324## alias sound-slot-1 snd-card-1
325##
326</pre>
327
328<note>
329If you have more than one soundcard, adjust the <c>cards_limit</c> value and add
330more snd-card aliases to the file. I don't have experience with this, but you
331can find examples for configurations with two or more soundcards in <uri
332link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri>
333of the <uri
334link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA
335Howto</uri>.
336</note>
337
338<p>
339Last thing to do in this file, almost at the end, check if these lines are there
340and uncommented:
341</p>
342
343<pre caption="Near the end of /etc/modules.d/alsa">
344alias /dev/mixer snd-mixer-oss
345alias /dev/dsp snd-pcm-oss
346alias /dev/midi snd-seq-oss
347</pre>
348
349<p>
350Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure
351everyting is ok, run <c>modules-update</c>.
352</p>
353
354<pre caption="Running modules-update">
355# <i>modules-update</i>
356</pre>
357
358<note>
359Running <c>modules-update</c> here will insert the data from
360<path>/etc/modules.d/alsa</path> into <path>/etc/modules.conf</path>
361</note>
362
363<p>
364You should also verify that <path>/etc/devfsd.conf</path> has the alsa devices
365and permissions correctly registered.
366</p>
367
368<pre caption="/etc/devfsd.conf">
369# ALSA/OSS stuff
370# Comment/change these if you want to change the permissions on
371# the audio devices
372LOOKUP snd MODLOAD ACTION snd
373LOOKUP dsp MODLOAD
374LOOKUP mixer MODLOAD
375LOOKUP midi MODLOAD
376REGISTER sound/.* PERMISSIONS root.audio 660
377REGISTER snd/.* PERMISSIONS root.audio 660
378</pre>
379
380<note>
381Notice that devfsd.conf sets <path>/dev/sound</path> permissions to be
382root.audio. Thus, for non-root users to use audio they will have to be part of
383the audio group.
384</note>
385
386</body> 814<body>
387</section>
388</chapter>
389 815
390<chapter> 816<p>
391<title>Starting ALSA</title> 817If your sound card lacks a hardware synthesizer, you could use a virtual one
818like <c>timidity++</c>. Installation is a breeze.
819</p>
820
821<pre caption="Installing timidity++">
822# <i>emerge timidity++</i>
823</pre>
824
825<p>
826For timidity to play sounds, it needs a sound font. If you do not have any,
827install <c>timidity-eawpatches</c> or <c>timidity-shompatches</c> which will
828give you some sound fonts. You can have multiple sound font configurations
829installed, and you can place your own in <path>/usr/share/timidity/</path>.
830To switch between different timidity configurations, you should use the
831<c>timidity-update</c> tool provided in the timidity++ package.
832</p>
833
834<pre caption="Installing sound fonts">
835# <i>emerge timidity-eawpatches</i>
836# <i>timidity-update -g -s eawpatches</i>
837
838<comment>(or)</comment>
839
840# <i>emerge timidity-shompatches</i>
841# <i>timidity-update -g -s shompatches</i>
842</pre>
843
844<p>
845Don't forget to add <c>timidity</c> to the default runlevel.
846</p>
847
848<pre caption="Adding timidity to the default runlevel">
849# <i>rc-update add timidity default</i>
850# <i>/etc/init.d/timidity start</i>
851</pre>
852
853<p>
854You can now try out <uri link="#doc_chap4_pre3">Playing MIDI</uri> files.
855</p>
856
857</body>
392<section> 858</section>
393<title>Adding alsasound to a runlevel</title>
394<body>
395
396<p>
397First thing to do now, is to make ALSA startup at boottime. Like this:
398</p>
399
400<pre caption="Add ALSA to the default runlevel">
401# <i>rc-update add alsasound boot</i>
402</pre>
403
404<warn>
405Note that the alsasound script should be added to the "boot" runlevel, not the
406"default" runlevel.
407</warn>
408
409</body>
410</section> 859<section>
860<title>Tools and Firmware</title>
861<body>
862
863<p>
864Some specific sound cards can benefit from certain tools provided by the
865<c>alsa-tools</c> and <c>alsa-firmware</c> packages. If you need
866<c>alsa-tools</c>, be sure to define the ALSA_TOOLS variable in
867<path>/etc/make.conf</path> with the tools you require. For instance:
868</p>
869
870<pre caption="Selecting ALSA Tools in /etc/make.conf">
871ALSA_TOOLS="as10k1 ac3dec"
872</pre>
873
874<p>
875If the ALSA_TOOLS variable is not set, all available tools will be built.
876Now, install the <c>alsa-tools</c> (and/or <c>alsa-firmware</c>) package(s):
877</p>
878
879<pre caption="Installing ALSA Tools">
880# <i>emerge alsa-tools</i>
881</pre>
882
883</body>
411<section> 884</section>
412<title>Running and unmuting</title>
413<body>
414
415<p>
416Since we're Linux users, we don't want to reboot. So we'll start the alsasound
417script manually.
418</p>
419
420<pre caption="Starting ALSA">
421# <i>/etc/init.d/alsasound start</i>
422</pre>
423
424<p>
425ALSA is running now. If everything is ok, you should be able to see the ALSA
426modules loaded when running <c>lsmod</c>. However, sound won't work yet,
427because the channels are still muted. We need <c>amixer</c> for this.
428</p>
429
430<pre caption = "Running amixer">
431# <i>amixer</i>
432</pre>
433
434<warn>
435You shouldn't get this, but <e>if</e> you get an error about "amixer: Mixer
436attach default error: No such file or directory", you should manually modprobe
437<c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again.
438</warn>
439
440<pre caption="Only if you get an error when running amixer">
441# <i>modprobe snd-mixer-oss</i>
442# <i>modprobe snd-pcm-oss</i>
443# <i>amixer</i>
444</pre>
445
446<p>
447If you got this far, now unmute Master and PCM channels. Some hardware
448even requires you to unmute the center channel or even the surround
449channel.
450</p>
451
452<pre caption = "Unmuting channels">
453# <i>amixer set Master 100 unmute</i>
454# <i>amixer set PCM 100 unmute</i>
455<comment>Only if the above doesn't succeed on its own:</comment>
456# <i>amixer set Center 100 unmute</i>
457# <i>amixer set Surround 100 unmute</i>
458<comment>Test the sound:</comment>
459# <i>aplay $KDEDIR/share/sounds/pop.wav</i> <codenote>(pop.wav is part of KDE)</codenote>
460</pre>
461
462<p>
463We check to see if sound is working by using the aplay (alsa play) command. If
464you hear a pop, then sound is indeed working. Then, adjust the volume settings
465to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them
466"just so".
467</p>
468
469<p>
470You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for
471XMMS.
472</p>
473
474<p>
475When you reboot your system, the <c>alsasound</c> init script will properly saveand restore your volume settings.
476</p>
477
478</body>
479</section> 885<section>
480</chapter> 886<title>A Big thank you to...</title>
887<body>
481 888
482<chapter> 889<p>
483<title>Final Notes</title> 890Everyone who contributed to the earlier version of the Gentoo ALSA Guide:
891Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston,
892John P. Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin.
893</p>
894
895</body>
484<section> 896</section>
485<title>After kernel-upgrades..</title>
486<body>
487
488<p>
489When you ever rebuild your kernel, or upgrade to another kernel, you'll have to
490rebuild the ALSA modules.
491</p>
492
493<p>
494Although you might have installed <c>alsa-driver</c>, <c>alsa-libs</c> and
495<c>alsa-utils</c>, only the first will have to be installed again, since it will
496put the alsa modules in <path>/lib/modules/*/kernel/sound/pci/</path>.
497</p>
498
499<pre caption="needed after each kernel compile">
500# <i>emerge alsa-driver</i>
501</pre>
502
503</body>
504</section> 897<section>
505<section> 898<title>References</title>
506<title>/etc/modules.autoload</title>
507<body>
508
509<p>
510You won't have to edit this file for use with ALSA. After our <c>rc-update add
511alsasound boot</c>, our system will load the correct modules at startup.
512</p>
513
514<p>
515It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this
516file. Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this
517FAQ</uri> for more info.
518</p>
519
520</body> 899<body>
521</section>
522<section>
523<title>Known bugs</title>
524<body>
525
526<note>
527This guide lags behind on the alsa-development. Chances are these bugs
528are already fixed when you read this.
529</note>
530 900
531<ul> 901<ul>
532 <li>
533 If you have <b>lots of noise</b> when using <b>oss</b> emulation, add
534 <e>options snd-pcm-oss dsp_map=1</e> to <path>/etc/modules.d/alsa</path>
535 </li>
536</ul>
537
538</body>
539</section>
540<section>
541<title>Activating Joystick Support</title>
542<body>
543
544<p>
545If your soundcard has a joystick plug, you might be interested in activating
546joystick support for your soundcard. If so, start by verifying if your soundcard
547driver has a joystick parameter. You can verify this by running <c>modinfo</c>
548against your <path>snd-&lt;your chipset&gt;</path>. For instance, for the
549<c>snd-via82xx</c>:
550</p>
551
552<pre caption="Running modinfo">
553# <i>modinfo snd-via82xx</i>
554filename: /lib/modules/2.4.22-ck2/snd-via82xx.o
555description: "VIA VT82xx audio"
556author: "Jaroslav Kysela &lt;perex@suse.cz&gt;"
557license: "GPL"
558parm: index int array (min = 1, max = 8), description "Index value for VIA 82xx bridge."
559parm: id string array (min = 1, max = 8), description "ID string for VIA 82xx bridge."
560parm: enable int array (min = 1, max = 8), description "Enable audio part of VIA 82xx bridge."
561parm: mpu_port long array (min = 1, max = 8), description "MPU-401 port. (VT82C686x only)"
562<i>parm: joystick int array (min = 1, max = 8), description "Enable joystick. (VT82C686x only)"</i>
563parm: ac97_clock int array (min = 1, max = 8), description "AC'97 codec clock (default 48000Hz)."
564parm: dxs_support int array (min = 1, max = 8), description "Support for DXS channels
565 (0 = auto, 1 = enable, 2 = disable, 3 = 48k only, 4 = no VRA)"
566</pre>
567
568<p>
569If it has the <c>joystick</c> parameter, then append <c>joystick=1</c> to your
570<c>options</c> line in <path>/etc/modules.d/alsa</path>. For instance, for the
571<c>snd-via82xx</c>:
572</p>
573
574<pre caption="Adding the joystick parameter">
575alias snd-card-0 snd-via82xx
576options snd-via82xx joystick=1
577</pre>
578
579</body>
580</section>
581<section>
582<title>More links..</title>
583<body>
584
585<p>
586You could check these for additional info:
587</p>
588
589<ul>
590 <li>
591 <uri link="http://www.gentoo.org/doc/en/desktop.xml">The Gentoo Linux
592 Desktop Configuration Guide</uri>
593 </li>
594 <li>
595 <uri link="http://www.alsa-project.org">ALSA Project Homepage</uri> 902 <li><uri link="http://www.alsa-project.org/">The ALSA Project</uri></li>
596 </li>
597 <li>
598 <uri link="http://www.alsa-project.org/documentation.php3">ALSA Users
599 Documentation</uri>
600 </li>
601 <li>
602 <uri link="http://www.djcj.org">ALSA Howto's and FAQ's</uri>
603 </li>
604 <li>
605 <uri link="http://tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound
606 HOWTO</uri>
607 </li>
608 <li>
609 <uri link="http://linux-sound.org/">Sound and MIDI Software For Linux</uri> 903 <li><uri link="http://linux-sound.org">Linux Sound/MIDI Software</uri></li>
610 </li>
611</ul> 904</ul>
612 905
613</body> 906</body>
614</section> 907</section>
615</chapter> 908</chapter>

Legend:
Removed from v.1.21  
changed lines
  Added in v.1.59

  ViewVC Help
Powered by ViewVC 1.1.20