/[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.53
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.53 2005/06/08 19:54:07 fox2mike 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.0 -->
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.2</version>
38<date>November 23, 2003</date> 22<date>2005-06-09</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
60</p> 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<impo>
75<c>genkernel</c> users have their config built such a way that the ALSA
76sub-system in the kernel is active. Therefore <c>genkernel</c> users can
77proceed to the <uri link="#alsa-utilities">ALSA Utilities</uri> section
78directly.
79</impo>
80
81<p>
82The two options are :
83</p>
84
85<ol>
86 <li>
87 Use ALSA provided by your kernel. This is the preferred/recommended
88 method.
89 </li>
90 <li>
91 Use Gentoo's <c>media-sound/alsa-driver</c> package.
92 </li>
93</ol>
94
95<p>
96We shall take a peek into both before finally deciding on one.
97</p>
98
99<p>
100If you were to use ALSA provided by the kernel, the following are the pros and
101cons :
102</p>
103
104<table>
105<tr>
106 <th>Kernel ALSA</th>
107 <th>Pros and Cons</th>
108</tr>
109<tr>
110 <th>+</th>
111 <ti>Pretty stable as drivers are integrated into kernel.</ti>
112</tr>
113<tr>
114 <th>+</th>
115 <ti>One shot solution, no repeating emerges.</ti>
116</tr>
117<tr>
118 <th>-</th>
119 <ti>Might be a slightly older version than <c>alsa-driver</c>.</ti>
120</tr>
121</table>
122
123<p>
124And, if you were to use alsa-driver,
125</p>
126
127<table>
128<tr>
129 <th>alsa-driver</th>
130 <th>Pros and Cons</th>
131</tr>
132<tr>
133 <th>+</th>
134 <ti>Latest drivers from the ALSA Project.</ti>
135</tr>
136<tr>
137 <th>-</th>
138 <ti>Every kernel recompile requires a re-emerge of <c>alsa-driver</c>.</ti>
139</tr>
140<tr>
141 <th>-</th>
142 <ti>Needs certain kernel config options disabled to work correctly.</ti>
143</tr>
144</table>
145
146</body>
147</section>
148<section>
149<title>So...</title>
150<body>
151
152<p>
153The main difference between using <c>alsa-driver</c> and ALSA that comes with
154the kernel is that <c>alsa-driver</c> is generally more up to date than the
155version in the kernel. Since this does not make any huge difference as
156such, you are encouraged to use the ALSA provided by the kernel.
157</p>
158
159</body>
160</section>
161<section id="lspci">
162<title>Before you proceed</title>
163<body>
164
165<p>
166Whichever method of install you choose, you need to know what drivers your
167sound card uses. <c>lspci</c> will help you in digging out the required
168information. Please <c>emerge sys-apps/pciutils</c> to get <c>lspci</c>, if
169you don't have it installed already. We now proceed to find out details about
170the sound card.
171</p>
172
173<pre caption="Soundcard Details">
174# <i>lspci -v | grep -i audio</i>
1750000:00:0a.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
176</pre>
177
178<p>
179We now know that the sound card on the machine is a Sound Blaster Live! and
180the card manufacturer is Creative Labs. Head over to the
181<uri link="http://www.alsa-project.org/alsa-doc/"> ALSA Soundcard Matrix</uri>
182page and select Creative Labs from the drop down menu. You will be taken to
183the Creative Labs matrix page where you can see that the SB Live! uses the
184<c>emu10k1</c> module. That is the information we need for now. If you are
185interested in detailed information, you can click on the link next to the
186"Details" and that will take you to the <c>emu10k1</c> specific page.
187</p>
188
189</body>
190</section>
191<section id="kernel">
192<title>Using ALSA provided by your Kernel</title>
193<body>
194
195<p>
196If you're a person who likes to keep things simple like I do, then this is
197the way to go.
198</p>
199
200<note>
201Since the 2005.0 release, Gentoo Linux uses 2.6 as the default kernel. Unless
202you are specifically using the 2.4 profile, <c>gentoo-sources</c> will be a
2032.6 kernel on <e>most</e> architectures. Please check that your kernel is a
2042.6 series kernel. This method will <e>not</e> work on a 2.4 kernel.
205</note>
206
207<p>
208Let us now configure the kernel to enable ALSA.
209</p>
210
211<pre caption="Heading over to the source">
212# <i>cd /usr/src/linux</i>
213# <i>make menuconfig</i>
214</pre>
215
216<note>
217The above example assumes that <path>/usr/src/linux</path> symlink points to
218the kernel sources you want to use. Please ensure the same before proceeding.
219</note>
220
221<p>
222Now we will look at some of the options we will have to enable in the 2.6
223kernel to ensure proper ALSA support for our sound card.
224</p>
225
226<note>
227Please note that for the sake of ease, all examples show a modular kernel. It
228is advisable to follow the same. Please do <e>not</e> skip the
229<uri link="#alsa-config">Configuration</uri> section of this document. If
230you still like to have options built-in, ensure that you make changes to your
231config accordingly.
232</note>
233
234<pre caption="Kernel Options for ALSA">
235Device Drivers ---&gt;
236 Sound ---&gt;
237
238<comment>(This needs to be enabled)</comment>
239&lt;M&gt; Sound card support
240
241<comment>(Make sure OSS is disabled)</comment>
242Open Sound System ---&gt;
243 &lt; &gt; Open Sound System (DEPRECATED)
244
245<comment>(Move one step back and enter ALSA)</comment>
246Advanced Linux Sound Architecture ---&gt;
247 &lt;M&gt; Advanced Linux Sound Architecture
248 <comment>(Select this if you want MIDI sequencing and routing)</comment>
249 &lt;M&gt; Sequencer support
250 <comment>(Old style /dev/mixer* and /dev/dsp* support. Recommended.)</comment>
251 &lt;M&gt; OSS Mixer API
252 &lt;M&gt; OSS PCM (digital audio) API
253
254<comment>(You now have a choice of devices to enable support for. Generally,
255you will have one type of device and not more. If you have more than one
256sound card, please enable them all here.)</comment>
257
258<comment>(Mostly for testing and development purposes, not needed for normal
259users unless you know what you are doing.)</comment>
260Generic devices ---&gt;
261
262<comment>(For ISA Sound cards)</comment>
263ISA devices ---&gt;
264<comment>(IF you had the Gravis, you would select this option)</comment>
265 &lt;M&gt; Gravis UltraSound Extreme
266
267<comment>(Move one level back and into PCI devices. Most sound cards today are
268PCI devices)</comment>
269PCI devices ---&gt;
270 <comment>(We now select the emu10k1 driver for our card)</comment>
271 &lt;M&gt; Emu10k1 (SB Live!, Audigy, E-mu APS)
272 <comment>(Or an Intel card would be)</comment>
273 &lt;M&gt; Intel/SiS/nVidia/AMD/ALi AC97 Controller
274 <comment>(Or if you have a VIA Card)</comment>
275 &lt;M&gt; VIA 82C686A/B, 8233/8235 AC97 Controller
276
277<comment>(Move one level back and select in case you have an USB sound card)</comment>
278USB Devices ---&gt;
279</pre>
280
281<p>
282Now that your options are set, you can (re)compile the kernel and ALSA support
283for your card should be functional once you reboot into the new kernel.
284You can now proceed to <uri link="#alsa-utilities">ALSA Utilities</uri> and
285see if everything is working as it should.
286</p>
287
288</body>
289</section>
290<section id="alsa-driver">
291<title>Using the ALSA Driver package</title>
292<body>
293
294<p>
295So you've decided to go the <c>alsa-driver</c> way. Let's get started then.
296There are a few minor things to be done to ensure only the drivers for your
297sound card are compiled. Although this is not really necessary, it cuts down
298on the unnecessary drivers that will be compiled otherwise.
299</p>
300
301<p>
302If you don't have an idea of what drivers your sound card might need, please
303take a look at the <uri link="#lspci">lspci</uri> section of this guide. Once
304you have your driver name (<c>emu10k1</c> in our example), edit
305<path>/etc/make.conf</path> and add a variable, <c>ALSA_CARDS</c>.
306</p>
307
308<pre caption="Adding ALSA_CARDS to make.conf">
309<comment>(For one sound card)</comment>
310ALSA_CARDS="emu10k1"
311<comment>(For more than one, seperate names with spaces)</comment>
312ALSA_CARDS="emu10k1 via82xx"
313</pre>
314
315<p>
316If you have compiled your kernel and want to use <c>alsa-driver</c>, please
317ensure the following before proceeding, else <c>alsa-driver</c> is likely to
318fail. The next code listing gives you one way of performing the checks.
319</p>
320
321<ol>
322 <li>
323 <c>CONFIG_SOUND</c> is set. (Basic Sound support enabled)
324 </li>
325 <li>
326 <c>CONFIG_SOUND_PRIME</c> is not set. (In-built OSS support disabled)
327 </li>
328 <li>
329 <c>CONFIG_SND</c> is not set. (In-built ALSA support disabled)
330 </li>
331 <li>
332 <path>/usr/src/linux</path> points to the kernel you want ALSA working on.
333 </li>
334</ol>
335
336<pre caption=".config checks">
337<comment>(Assuming the linux symlink points to the correct kernel)</comment>
338# <i>cd /usr/src/linux</i>
339# <i>grep SOUND .config</i>
340<comment>(1. is true)</comment>
341CONFIG_SOUND=y
342<comment>(2. is true)</comment>
343CONFIG_SOUND_PRIME is not set
344# <i>grep SND .config</i>
345<comment>(and 3. is true)</comment>
346CONFIG_SND is not set
347</pre>
348
349<p>
350Now all you have to do is type the magic words...and no, its not abracadabra.
351</p>
352
353<pre caption="Installing alsa-driver">
354# <i>emerge alsa-driver</i>
355</pre>
356
357<impo>
358Please note that you will have to run <c>emerge alsa-driver</c> after every
359kernel (re)compile, as the earlier drivers are deleted.
360</impo>
361
362</body>
363</section>
364</chapter>
365
366<chapter>
367<title>Configuring/Testing ALSA</title>
368<section id="alsa-utilities">
369<title>ALSA Utilities</title>
370<body>
371
372<p>
373<c>alsa-utils</c> forms an integral part of ALSA as it has a truckload of
374programs that are highly useful, including the ALSA Initscripts. Hence we
375strongly recommend that you install <c>alsa-utils</c>
376</p>
377
378<pre caption="Install alsa-utils">
379# <i>emerge alsa-utils</i>
380</pre>
381
382<note>
383If you activated ALSA in your <uri link="#kernel">kernel</uri> <e>and</e> did
384not compile ALSA as modules, please proceed to the
385<uri link="#initscript">ALSA Initscript</uri> section. The rest of you need
386to configure ALSA. This is made very easy by the existence of the
387<c>alsaconf</c> tool provided by <c>alsa-utils</c>.
388</note>
389
390</body>
391</section>
392<section id="alsa-config">
393<title>Configuration</title>
394<body>
395
396<note>
397Please shut down any programs that <e>might</e> access the sound card while
398running <c>alsaconf</c>.
399</note>
400
401<p>
402The easiest way to configure your sound card is to run <c>alsaconf</c>. Just
403type <c>alsaconf</c> in a shell as root.
404</p>
405
406<pre caption="Invoking alsaconf">
407# <i>alsaconf</i>
408</pre>
409
410<p>
411You will now see a neat menu guided interface that will automatically probe
412your devices and try to find out your sound card. You will be asked to pick
413your sound card from a list. Once that's done, it will ask you permission to
414automatically make required changes to <path>/etc/modules.d/alsa</path>.
415It will then adjust your volume settings to optimum levels and run
416<c>modules-update</c> and starts the <path>/etc/init.d/alsasound</path>
417service. Once <c>alsaconf</c> exits, you can proceed with setting up the ALSA
418initscript.
419</p>
420
421</body>
422</section>
423<section id="initscript">
424<title>ALSA Initscript</title>
425<body>
426
427<p>
428We're now almost all setup. Whichever method you chose to install ALSA, you'll
429need to have something load your modules or initialize ALSA and restore your
430volume settings when your system comes up. The ALSA Initscript handles all of
431this for you and is called <c>alsasound</c>. Add it to the default run-level.
432</p>
433
434<pre caption="Adding ALSA to default">
435# <i>rc-update add alsasound default</i>
436 * alsasound added to runlevel default
437 * rc-update complete.
438</pre>
439
440<p>
441Next, just check the <path>/etc/conf.d/alsasound</path> file and ensure that
442SAVE_ON_STOP variable is set to yes. This saves your sound settings when you
443shutdown your system.
444</p>
445
446</body>
447</section>
448<section>
449<title>Volume Check!</title>
450<body>
451
452<p>
453We've completed all the setups and pre-requisites, so let's fire up ALSA. If
454you ran <c>alsaconf</c>, you can skip this step, since <c>alsaconf</c> already
455does this for you.
456</p>
457
458<pre caption="Start the service">
459<comment>(Modular Kernels)</comment>
460# <i>/etc/init.d/alsasound start</i>
461 * Loading ALSA modules ...
462 * Loading: snd-card-0 ... [ ok ]
463 * Loading: snd-pcm-oss ... [ ok ]
464 * Loading: snd-seq ... [ ok ]
465 * Loading: snd-emu10k1-synth ... [ ok ]
466 * Loading: snd-seq-midi ... [ ok ]
467 * Restoring Mixer Levels ... [ ok ]
468<comment>(ALSA compiled in)</comment>
469# <i>/etc/init.d/alsasound start</i>
470 * Loading ALSA modules ...
471 * Restoring Mixer Levels ... [ ok ]
472</pre>
473
474<p>
475Now that the required things have been take care of, we need to check up on
476the volume as in certain cases, it is muted. We use <c>alsamixer</c> for this purpose.
477</p>
478
479<pre caption="Starting alsamixer">
480<comment>(Opens up a console program. Only required settings are shown)</comment>
481# <i>alsamixer</i>
482</pre>
483
484<p>
485This is how the ALSA Mixer <e>might</e> look the first time you open it. Pay
486attention to the Master and PCM channels which both have an MM below them.
487That means they are muted. If you try to play anything with <c>alsamixer</c>
488in this state, you will not hear anything on your speakers.
489</p>
490
491<figure link="/images/docs/alsa-mixermuted.png" short="AlsaMixer Muted" caption="The Alsa Mixer Main Window, Muted"/>
492
493<p>
494Now, we shall unmute the channels, and set volume levels as needed.
495</p>
496
497<warn>
498Both Master <e>and</e> PCM need to be unmuted and set to audible volume levels if
499you want to hear some output on your speakers.
500</warn>
61 501
62<ul> 502<ul>
63 <li> 503 <li>
64 Efficient support for all types of audio interfaces, from consumer 504 To move between channels, use your left and right arrow keys. (&lt;-
65 soundcards to professional multichannel audio interfaces 505 &amp; -&gt;)
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> 506 </li>
73 <li> 507 <li>
74 Support for the older OSS API, providing binary compatibility for most OSS 508 To toggle mute, move to the specific channel, for example Master and press
75 programs 509 the <e>m</e> key on the keyboard.
76 </li> 510 </li>
77</ul>
78
79<p>
80There's lots more to ALSA however, like support for Full Duplex playback and
81recording, multiple soundcard support, hardware mixing of streams, extensive
82mixer capabilities (to support advanced features of new soundcards), ...
83</p>
84
85</body>
86</section>
87<section>
88<title>Why use ALSA?</title>
89<body>
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>
108</section>
109<section>
110<title>What cards does ALSA support?</title>
111<body>
112
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>
117
118<p>
119To know if your card is supported, you can find a Soundcard Matrix of supported
120and not-supported cards here: <uri>http://www.alsa-project.org/alsa-doc/</uri>.
121</p>
122
123</body>
124</section>
125</chapter>
126
127<chapter>
128<title>Installation</title>
129<section>
130<title>Gentoo USE flags</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>
141</section>
142<section>
143<title>Kernel modules</title>
144<body>
145
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>
152
153<p>
154First we'll make sure that our kernel configuration is ready for use with ALSA.
155All you need in your kernel configuration is having Sound Card Support set to
156be built as a module (M). This will build <path>soundcore.o</path>.
157</p>
158
159<note>
160Possibly, this will also work when you built Sound Card Support in the kernel
161(Y) instead of building it as a module (M). However, the official ALSA
162documentation suggests building it as a module, since ALSA will try loading it.
163</note>
164
165<p>
166If you already have a working kernel configuration, make sure you remove all
167sound drivers (except for Sound Card Support). If you wish to do this without
168having to reboot, you could do like this:
169</p>
170
171<pre caption="Kernel configuration">
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>
180Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound
181drivers. Exit and say Y to save your kernel configuration. After that, build
182the modules:
183</p>
184
185<pre caption="Kernel compilation">
186# <i>make dep clean</i>
187# <i>make modules modules_install</i>
188</pre>
189
190<p>
191Before installing your new modules, this last line will delete all your previous
192modules, even the ones from a previous ALSA installation.
193</p>
194
195<impo>
196This means, whenever you recompile your kernel later on, you MUST recompile
197<c>alsa-driver</c>.
198</impo>
199
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>
211
212<pre caption="Search for soundcard information">
213# <i>grep audio /proc/pci</i>
214</pre>
215
216<warn>
217If you had a previous sound setup and there are still non-ALSA sound modules
218loaded, unload them <e>now</e>. Check with <c>lsmod</c> and use <c>rmmod</c>
219to unload all sound-related modules on your system.
220</warn>
221
222<p>
223We could simply do an <c>emerge alsa-driver</c> now, this would compile and
224install <e>all</e> ALSA sound drivers.
225</p>
226
227<p>
228However, to save some time, lookup the <e>Module Name</e> of your soundcard(s)
229on the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard
230Matrix</uri> by following the <e>Details</e> link in the <e>Driver and Docs</e>
231column in the row of the chipset of your soundcard. Mine is <c>snd-emu10k1</c>,
232since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. We'll set
233ALSA_CARDS environment to the value of the module name before emerging (but
234without the snd prefix), so emerge will only compile the drivers we need.
235</p>
236
237<pre caption="Compile correct modules">
238# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i>
239</pre>
240
241<note>
242You can also add this value in <path>/etc/make.conf</path>, so when you have
243to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>.
244For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c>
245</note>
246
247<note>
248When you want to install ALSA drivers for more than one soundcard, you could
249set ALSA_CARDS to a space-separated list of drivers; like this: <c>env
250ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c>
251</note>
252
253<note>
254If you want to have OSS compatibility, make sure to emerge <i>alsa-oss</i>, it
255is the ALSA/OSS compatibility wrapper.
256</note>
257
258<note>
259If you plan on recompiling your kernels numerous times, it might
260be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This
261will create a binary package for it. Later, after recompiling your kernel,
262you can just do <c>emerge --usepkg alsa-driver</c> which will install the
263binary package instead of recompiling it completely.
264</note>
265
266<p>
267After this, the ALSA modules should be installed on your system.
268</p>
269
270</body>
271</section>
272<section>
273<title>Configuration of ALSA</title>
274<body>
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>
387</section>
388</chapter>
389
390<chapter>
391<title>Starting ALSA</title>
392<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>
411<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>
480</chapter>
481
482<chapter>
483<title>Final Notes</title>
484<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>
505<section>
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>
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
531<ul>
532 <li> 511 <li>
533 If you have <b>lots of noise</b> when using <b>oss</b> emulation, add 512 To increase and decrease the volume levels, use the up and down arrow keys
534 <e>options snd-pcm-oss dsp_map=1</e> to <path>/etc/modules.d/alsa</path> 513 respectively.
535 </li> 514 </li>
536</ul> 515</ul>
537 516
517<note>
518Be careful when setting your Bass and Treble values. 50 is usually a good
519number for both. Extremely high values of Bass may cause <e>jarring</e>
520on speakers that are not designed to handle them.
521</note>
522
523<p>
524After you're all done, your ALSA Mixer should look similar to the one below.
525Note the 00 instead of the MM and also the volume levels for some optimum
526settings.
527</p>
528
529<figure link="/images/docs/alsa-mixerunmuted.png" short="AlsaMixer Unmuted" caption="Alsa Mixer ready to roll"/>
530
538</body> 531</body>
539</section>
540<section> 532</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> 533<section>
534<title>Sound Check!</title>
535<body>
536
537<p>
538Finally. Some music. If everything above is perfect, you should be able to now
539listen to some good music. A quick way to test is to use a command line tool
540like <c>media-sound/madplay</c>. You could also use something more well known
541like <c>mpg123</c> or <c>xmms</c>. If you are an ogg fan, you could use
542<c>ogg123</c> provided by <c>media-sound/vorbis-tools</c>. Use any player you
543are comfortable with. As always, <c>emerge</c> what you need.
544</p>
545
546<pre caption="Getting the software">
547<comment>(Install the applications you want)</comment>
548# <i>emerge madplay mpg123 xmms</i>
549<comment>(To play .ogg files)</comment>
550# <i>emerge vorbis-tools</i>
551</pre>
552
553<p>
554And then play your favorite sound track...
555</p>
556
557<pre caption="Playing Music">
558# <i>madplay -v /mnt/shyam/Music/Paul\ Oakenfold\ -\ Dread\ Rock.mp3</i>
559MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al.
560 Title: Dread Rock
561 Artist: Paul Oakenfold
562 Album: Matrix Reloaded
563 Year: 2003
564 Genre: Soundtrack
565 Soundtrack
566 00:04:19 Layer III, 160 kbps, 44100 Hz, joint stereo (MS), no CRC
567
568# <i>ogg123 Paul\ Oakenfold\ -\ Dread\ Rock.ogg</i>
569Audio Device: Advanced Linux Sound Architecture (ALSA) output
570
571Playing: Paul Oakenfold - Dread Rock.ogg
572Ogg Vorbis stream: 2 channel, 44100 Hz
573Genre: Soundtrack
574Transcoded: mp3;160
575Title: Dread Rock
576Artist: Paul Oakenfold
577Date: 2003
578Album: Matrix Reloaded
579Time: 00:11.31 [04:28.75] of 04:40.06 (200.6 kbps) Output Buffer 96.9%
580</pre>
581
582</body>
581<section> 583</section>
582<title>More links..</title> 584<section>
585<title>Issues?</title>
586<body>
587
588<p>
589If for some reason you're unable to hear sound, the first thing to do would
590be to check your <uri link="#doc_chap3_pre5">alsamixer</uri> settings. 80% of
591the issues lie with muted channels or low volume. Also check your Window
592Manager's sound applet and verify that volumes are set to audible levels.
593</p>
594
595<p>
596<path>/proc</path> is your friend. And in this case, <path>/proc/asound</path>
597is your best friend. We shall just take a short look at how much info is made
598available to us there.
599</p>
600
601<pre caption="Fun with /proc/asound">
602<comment>(First and foremost, if /proc/asound/cards shows your card, ALSA has
603picked up your sound card fine.)</comment>
604# <i>cat /proc/asound/cards</i>
6050 [Live ]: EMU10K1 - Sound Blaster Live!
606 Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
607
608<comment>(If you run ALSA off the kernel like I do and wonder how far behind
609you are from alsa-driver, this displays current running ALSA version)</comment>
610# <i>cat /proc/asound/version</i>
611Advanced Linux Sound Architecture Driver Version 1.0.8 (Thu Jan 13 09:39:32 2005 UTC).
612
613<comment>(ALSA OSS emulation details)</comment>
614# <i>cat /proc/asound/oss/sndstat</i>
615Sound Driver:3.8.1a-980706 (ALSA v1.0.8 emulation code)
616Kernel: Linux airwolf.zion 2.6.11ac1 #2 Wed May 4 00:35:08 IST 2005 i686
617Config options: 0
618
619Installed drivers:
620Type 10: ALSA emulation
621
622Card config:
623Sound Blaster Live! (rev.6, serial:0x80271102) at 0xb800, irq 11
624
625Audio devices:
6260: EMU10K1 (DUPLEX)
627
628Synth devices: NOT ENABLED IN CONFIG
629
630Midi devices:
6310: EMU10K1 MPU-401 (UART)
632
633Timers:
6347: system timer
635
636Mixers:
6370: SigmaTel STAC9721/23
638</pre>
639
583<body> 640</body>
641</section>
642</chapter>
584 643
585<p> 644<chapter>
586You could check these for additional info: 645<title>Other things ALSA</title>
646<section>
647<title>Setting up MIDI support</title>
648<body>
649
587</p> 650<p>
651If your sound card is one of those that come with on-board MIDI synthesizers
652and you would like to listen to some .mid files, you have to install
653<c>awesfx</c> which is basically a set of utilities for controlling the AWE32
654driver. We need to install it first. If you don't have a hardware synthesizer,
655you can use a virtual one. Please see the section on
656<uri link="#vsynth">Virtual Synthesizers</uri> for more information.
657</p>
658
659<pre caption="Installing awesfx">
660# <i>emerge awesfx</i>
661</pre>
662
663<note>
664You will need to copy over SoundFont (SF2) files from your sound card's driver
665CD or a Windows installation into <path>/usr/share/sounds/sf2/</path>. For
666example a sound font file for the Creative SBLive! card would be 8MBGMSFX.SF2.
667</note>
668
669<p>
670After copying over the Soundfont files, we can then play a midi file as shown.
671You can also add the <c>asfxload</c> command to
672<path>/etc/conf.d/local.start</path>, so that the sound font is loaded
673every time the system starts up.
674</p>
675
676<note>
677<path>/mnt</path> paths mentioned in the code listing(s) below will <e>not</e>
678be the same in your machine. They are just an example. Please be careful to
679change the path to suit your machine.
680</note>
681
682<pre caption="Loading Soundfonts">
683<comment>(First, copy the Soundfont)</comment>
684# <i>cp /mnt/win2k/Program\ Files/CreativeSBLive2k/SFBank/8MBGMSFX.SF2 /usr/share/sounds/sf2/</i>
685<comment>(We load the specific Soundfont)</comment>
686# <i>asfxload /usr/share/sounds/sf2/8MBGMSFX.SF2</i>
687</pre>
688
689<p>
690You can now play midi files using a program like <c>aplaymidi</c>. Run
691<c>aplaymidi -l</c> to get a list of available ports and then pick one
692to play the file on.
693</p>
694
695<pre caption="Playing MIDI">
696<comment>(Check open ports)</comment>
697# <i>aplaymidi -l</i>
698 Port Client name Port name
699 64:0 EMU10K1 MPU-401 (UART) EMU10K1 MPU-401 (UART)
700 65:0 Emu10k1 WaveTable Emu10k1 Port 0
701 65:1 Emu10k1 WaveTable Emu10k1 Port 1
702 65:2 Emu10k1 WaveTable Emu10k1 Port 2
703 65:3 Emu10k1 WaveTable Emu10k1 Port 3
704<comment>(Pick a port, and play a mid file)</comment>
705# <i> aplaymidi --port=65:0 /mnt/shyam/music/midi/mi2.mid</i>
706</pre>
707
708</body>
709</section>
710<section id="vsynth">
711<title>Virtual Synthesizers</title>
712<body>
713
714<p>
715If your sound card lacks a hardware synthesizer, you could use a virtual one
716like <c>timidity++</c>. Installation is a breeze.
717</p>
718
719<pre caption="Installing timidity++">
720# <i>emerge timidity++</i>
721</pre>
722
723<p>
724For timidity to play sounds, it needs a sound font. If you do not have any,
725install <c>timidity-eawpatches</c> or <c>timidity-shompatches</c> which will
726give you some sound fonts. You can have multiple sound font configurations
727installed, and you can place your own in <path>/usr/share/timidity/</path>.
728To switch between different timidity configurations, you should use the
729<c>timidity-update</c> tool provided in the timidity++ package.
730</p>
731
732<pre caption="Installing sound fonts">
733# <i>emerge timidity-eawpatches</i>
734# <i>timidity-update -g -s eawpatches</i>
735
736<comment>(or)</comment>
737
738# <i>emerge timidity-shompatches</i>
739# <i>timidity-update -g -s shompatches</i>
740</pre>
741
742<p>
743Don't forget to add <c>timidity</c> to the default runlevel.
744</p>
745
746<pre caption="Adding timidity to the default runlevel">
747# <i>rc-update add timidity default</i>
748# <i>/etc/init.d/timidity start</i>
749</pre>
750
751<p>
752You can now try out <uri link="#doc_chap4_pre3">Playing MIDI</uri> files.
753</p>
754
755</body>
756</section>
757<section>
758<title>Tools and Firmware</title>
759<body>
760
761<p>
762Some specific sound cards can benefit from certain tools provided by the
763<c>alsa-tools</c> and <c>alsa-firmware</c> packages. If you need
764<c>alsa-tools</c>, be sure to define the ALSA_TOOLS variable in
765<path>/etc/make.conf</path> with the tools you require. For instance:
766</p>
767
768<pre caption="Selecting ALSA Tools in /etc/make.conf">
769ALSA_TOOLS="as10k1 ac3dec"
770</pre>
771
772<p>
773If the ALSA_TOOLS variable is not set, all available tools will be built.
774Now, install the <c>alsa-tools</c> (and/or <c>alsa-firmware</c>) package(s):
775</p>
776
777<pre caption="Installing ALSA Tools">
778# <i>emerge alsa-tools</i>
779</pre>
780
781</body>
782</section>
783<section>
784<title>A Big thank you to...</title>
785<body>
786
787<p>
788Everyone who contributed to the earlier version of the Gentoo ALSA Guide:
789Vincent Verleye, Grant Goodyear, Arcady Genkin, Jeremy Huddleston,
790John P. Davis, Sven Vermeulen, Benny Chuang, Tiemo Kieft and Erwin.
791</p>
792
793</body>
794</section>
795<section>
796<title>References</title>
797<body>
588 798
589<ul> 799<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> 800 <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> 801 <li><uri link="http://linux-sound.org">Linux Sound/MIDI Software</uri></li>
610 </li>
611</ul> 802</ul>
612 803
613</body> 804</body>
614</section> 805</section>
615</chapter> 806</chapter>

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

  ViewVC Help
Powered by ViewVC 1.1.20