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

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

  ViewVC Help
Powered by ViewVC 1.1.20