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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.10 - (show annotations) (download) (as text)
Fri Jun 6 01:52:02 2003 UTC (11 years, 1 month ago) by peesh
Branch: MAIN
Changes since 1.9: +7 -2 lines
File MIME type: application/xml
Added Grant Goodyear and Arcady Genkin as authors for the guide

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3
4 <guide link = "/doc/en/alsa-guide.xml">
5 <title>Gentoo Linux ALSA Guide</title>
6 <author title="Author"><mail link="zu@pandora.be">
7 Vincent Verleye</mail>
8 </author>
9 <author title="Author"><mail link="g2boojum@gentoo.org">
10 Grant Goodyear</mail>
11 </author>
12 <author title="Author"><mail link="agenkin@gentoo.org">
13 Arcady Genkin</mail>
14 </author>
15 <author title="Editor"><mail link="zhen@gentoo.org">
16 John P. Davis</mail>
17 </author>
18
19 <abstract>
20 This guide will show you how to set up the Advanced Linux Sound Architecture (ALSA) on Gentoo Linux.
21 In addition to the Gentoo Linux Desktop Configuration Guide, this guide is supposed to give you more information on this subject. </abstract>
22
23 <version>1.2</version>
24 <date>5 June 2003</date>
25
26 <chapter>
27 <title>Introduction</title>
28 <section>
29 <title>What is ALSA?</title>
30 <body>
31 <p>
32 The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux sound subsystem by rewriting
33 large chunks of it.
34 It is anticipated that ALSA will make it into Linux kernel 2.6.x (or 3.x.x -- whichever comes first) as it becomes ready.
35 </p>
36
37 <p>
38 ALSA provides audio and MIDI functionality for Linux.
39 </p>
40
41 <p>
42 Quoted from <uri>http://www.alsa-project.org</uri>, ALSA has the following features:
43 <ul><li> Efficient support for all types of audio interfaces, from consumer soundcards to professional multichannel audio interfaces.</li>
44 <li> Fully modularized sound drivers.</li>
45 <li> SMP and thread-safe design.</li>
46 <li> User space library (alsa-lib) to simplify application programming and provide higher level functionality.</li>
47 <li> Support for the older OSS API, providing binary compatibility for most OSS programs.</li>
48 </ul>
49 There's lots more to ALSA however, like support for Full Duplex playback and recording, multiple soundcard support,
50 hardware mixing of streams, extensive mixer capabilities (to support advanced features of new soundcards), ...
51 </p>
52 </body>
53 </section>
54 <section>
55 <title>Why use ALSA?</title>
56 <body>
57 <p>
58 If your soundcard is supported by the Linux kernel sound system or the commercial OSS/4Front sound driver system,
59 which can be found in all 2.4.x Linux kernels, you could just aswell build <e>those modules</e> for use with your soundcard.
60 If you want this, just read through the <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>.
61 </p>
62 <p>
63 However, those OSS/4Front drivers have some limitations -- being commercial is one.
64 ALSA is an attempt to go beyond these limitations and to do so in an open source fashion.
65 ALSA is a fully GPL and LGPL'ed sound driver system, that provides a professional quality system for recording, playback,
66 and MIDI sequencing.
67 </p>
68 </body>
69 </section>
70 <section>
71 <title>What cards does ALSA support?</title>
72 <body>
73 <p>
74 ALSA tries to support as many (new) cards as possible by providing open-source drivers.
75 However, some vendors may provide binary-only packages.
76 </p>
77 <p>To know if your card is supported, you can find a Soundcard Matrix of supported and not-supported cards here:
78 <uri>http://www.alsa-project.org/alsa-doc/</uri>.
79 </p>
80 </body>
81 </section>
82 </chapter>
83
84 <chapter>
85 <title>Installation</title>
86 <section>
87 <title>Kernel modules</title>
88 <body>
89 <p>
90 Since we're still using 2.4.x kernel sources, we'll have to compile kernel modules and ALSA modules separately. People who are using a 2.5.x kernel can do this from within their kernel configuration, since the ALSA modules are included in the kernel sources and should be built there.
91 </p>
92 <p>
93 First we'll make sure that our kernel configuration is ready for use with ALSA.
94 All you need in your kernel configuration is having Sound Card Support set to be built as a module (M).
95 This will build <c>soundcore.o</c>.
96 </p>
97 <p>
98 <note>
99 Possibly, this will also work when you built Sound Card Support in the kernel (Y) instead of building it as a module (M).
100 However, the official ALSA documentation suggests building it as a module, since ALSA will try loading it.
101 </note>
102 </p>
103 <p>If you already have a working kernel configuration, make sure you remove all sound drivers (except for Sound Card Support).
104 If you wish to do this without having to reboot, you could do like this:
105 </p>
106 <pre>
107 # <c>cd /usr/src/linux</c>
108 # <c>cp .config ~/</c>
109 # <c>make mrproper</c>
110 # <c>cp ~/.config .</c>
111 # <c>make menuconfig</c>
112 </pre>
113 <p>
114 Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound drivers.
115 Exit and say Y to save your kernel configuration.
116 After that, build the modules:
117 </p>
118 <pre>
119 # <c>make dep clean</c>
120 # <c>make modules modules_install</c>
121 </pre>
122 <p>
123 Before installing your new modules, this last line will delete all your previous modules,
124 even the ones from a previous ALSA installation.
125 </p>
126 <p>
127 <impo>
128 This means, whenever you recompile your kernel later on, you MUST recompile <c>alsa-driver</c>.
129 </impo>
130 </p>
131 <p>
132 <note>However, there's no need to reinstall <c>nvidia-kernel</c>, the Nvidia drivers are in a separate directory
133 in <path>/lib/modules/*/video</path> and won't get deleted by a <c>make modules modules_install</c>
134 </note>
135 </p>
136 </body>
137 </section>
138
139 <section>
140 <title>ALSA modules</title>
141 <body>
142
143 <p>
144 Now it's time to install the ALSA drivers for your soundcard(s). If your soundcard is PCI, you can find out the name
145 and type of your soundcard by looking at the output of /proc/pci
146 <pre># <c>grep audio /proc/pci</c></pre>
147 </p>
148
149 <p>
150 <warn>
151 If you had a previous sound setup and there are still non-ALSA sound modules loaded, unload them <e>now</e>.
152 Check with <c>lsmod</c> and use <c>rmmod</c> to unload all sound-related modules on your system.
153 </warn>
154 </p>
155
156 <p>
157 We could simply do an <c>emerge alsa-driver</c> now, this would compile and install <e>all</e> ALSA sound drivers.
158 </p>
159 <p>
160 However, to save some time, lookup the <e>Module Name</e> of your soundcard(s) on the
161 <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard Matrix</uri> by following the <e>Details</e> link in the <e>Driver and Docs</e> column in the row of the chipset of your soundcard.
162 Mine is <c>snd-emu10k1</c>, since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset.
163 We'll set ALSA_CARDS environment to the value of the module name before emerging (but without the snd prefix), so emerge will only compile the drivers we need.
164 </p>
165
166 <p>
167 <pre>
168 # <c>env ALSA_CARDS='emu10k1' emerge alsa-driver</c>
169 </pre>
170 </p>
171 <p>
172 <note>
173 You can also add this value in <path>/etc/make.conf</path>, so when you have to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>.
174 For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c>
175 </note>
176
177 <note>
178 When you want to install ALSA drivers for more than one soundcard, you could set ALSA_CARDS to a space-separated list
179 of drivers; like this: <c>env ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c>
180 </note>
181
182 <note>If you want to have OSS compatibility, make sure to emerge <i>alsa-oss</i>, it is the ALSA/OSS compatibility
183 wrapper. </note>
184
185 </p>
186 <p>
187 After this, the ALSA modules should be installed on your system.
188 </p>
189 </body>
190 </section>
191 <section>
192 <title>Configuration of ALSA</title>
193 <body>
194 <p>
195 Let's start configuring now to get ALSA working properly.
196 We'll need to edit some files, to let our system know about the freshly installed ALSA modules.
197 </p>
198 <p>
199 First file to edit is <path>/etc/modules.d/alsa</path>.
200 </p>
201 <warn>
202 There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit files in <path>/etc/modules.d</path>.
203 </warn>
204 <p>
205 Check the ALSA portion <e>at the bottom of the file</e>.
206 By tweaking this line you can specify the max number of soundcards you have (generally, just one).
207 </p>
208 <p>
209 <pre caption="At the bottom of /etc/modules.d/alsa">
210 # Set this to the correct number of cards.
211 <c>options snd cards_limit=1</c>
212 </pre>
213 </p>
214 <p>
215 Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit like this:
216 <pre caption="In /etc/modules.d/alsa">
217 ## and then run `update-modules' command.
218 ## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
219 ##
220 ## ALSA portion
221 <c>alias snd-card-0 snd-emu10k1</c>
222 <c>## If you have more than one, add:
223 ## alias snd-card-1 snd-intel8x0
224 ## alias snd-card-2 snd-ens1370</c>
225 ## OSS/Free portion
226 ## alias sound-slot-0 snd-card-0
227 ## alias sound-slot-1 snd-card-1
228 ##
229 </pre>
230 </p>
231 <p>
232 <note>
233 If you have more than one soundcard, adjust the <c>cards_limit</c> value and add more snd-card aliases to the file.
234 I don't have experience with this, but you can find examples for configurations with two or more soundcards in
235 <uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri>
236 of the <uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA Howto</uri>.
237 </note>
238 </p>
239 <p>
240 Last thing to do in this file, almost at the end, check if these lines are there and uncommented:
241 <pre caption="Near the end of /etc/modules.d/alsa">
242 alias /dev/mixer snd-mixer-oss
243 alias /dev/dsp snd-pcm-oss
244 alias /dev/midi snd-seq-oss
245 </pre>
246 </p>
247 <p>
248 Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure everyting is ok, run <c>update-modules</c>.
249 <pre>
250 # <c>update-modules</c>
251 </pre>
252 </p>
253 <note>
254 Running <c>update-modules</c> here will insert the data from <path>/etc/modules.d/alsa</path> into <path>/etc/modules.conf</path>
255 </note>
256 <p>
257 You should also verify that /etc/devfsd.conf has the alsa devices and permissions correctly registered.
258 </p>
259 <pre caption="/etc/devfsd.conf">
260 # ALSA/OSS stuff
261 # Comment/change these if you want to change the permissions on
262 # the audio devices
263 LOOKUP snd MODLOAD ACTION snd
264 LOOKUP dsp MODLOAD
265 LOOKUP mixer MODLOAD
266 LOOKUP midi MODLOAD
267 REGISTER sound/.* PERMISSIONS root.audio 660
268 REGISTER snd/.* PERMISSIONS root.audio 660
269 </pre>
270 <note>
271 Notice that devfsd.conf sets /dev/sound permissions to be root.audio. Thus, for non-root users to use audio they will have to be part of the audio group.
272 </note>
273 </body>
274 </section>
275 </chapter>
276 <chapter>
277 <title>Starting ALSA</title>
278 <section>
279 <title>Adding alsasound to a runlevel</title>
280 <body>
281 <p>
282 First thing to do now, is to make ALSA startup at boottime. Like this:
283 <pre>
284 # <c>rc-update add alsasound boot</c>
285 </pre>
286 </p>
287 <p>
288 <warn>Note that the alsasound script should be added to the "boot" runlevel, not the "default" runlevel.</warn>
289 </p>
290 </body>
291 </section>
292 <section>
293 <title>Running and unmuting</title>
294 <body>
295 <p>
296 Since we're Linux users, we don't want to reboot. So we'll start the alsasound script manually.
297 </p>
298 <pre>
299 # <c>/etc/init.d/alsasound start</c>
300 </pre>
301 <p>
302 ALSA is running now. If everything is ok, you should be able to see the ALSA modules loaded when running <c>lsmod</c>.
303 However, sound won't work yet, because the channels are still muted. We need <c>alsa-utils</c> for this.
304 </p>
305 <pre>
306 # <c>emerge alsa-utils</c>
307 # <c>amixer</c>
308 </pre>
309 <p>
310 <warn>
311 You shouldn't get this, but <e>if</e> you get an error about "amixer: Mixer attach default error: No such file or directory", you should manually insmod
312 <c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again.
313 </warn>
314 </p>
315 <pre caption="only if you get an error when running amixer">
316 # <c>insmod snd-mixer-oss</c>
317 # <c>insmod snd-pcm-oss</c>
318 # <c>amixer</c>
319 </pre>
320 <p>
321 If you got this far, now unmute both Master and PCM channels.
322 </p>
323 <p>
324 <pre>
325 # <c>amixer set Master 100 unmute</c>
326 # <c>amixer set PCM 100 unmute</c>
327 # <c>aplay $KDEDIR/share/sounds/pop.wav</c> <codenote>(pop.wav is part of KDE)</codenote>
328 </pre>
329 </p>
330 We check to see if sound is working by using the aplay (alsa play) command. If you hear a pop, then sound is indeed working.
331 Then, adjust the volume settings to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them "just so".
332 <p>
333 You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for XMMS.
334 </p>
335 When you reboot your system, the <e>alsasound</e> init script will properly save and restore your volume settings.
336 </body>
337 </section>
338 </chapter>
339 <chapter>
340 <title>Final Notes</title>
341 <section>
342 <title>After kernel-upgrades..</title>
343 <body>
344 <p>When you ever rebuild your kernel, or upgrade to another kernel, you'll have to rebuild the ALSA modules.</p>
345 <p>Although you might have installed <c>alsa-driver</c>, <c>alsa-libs</c> and <c>alsa-utils</c>, only the first will
346 have to be installed again, since it will put the alsa modules in
347 <path>/lib/modules/*/kernel/sound/pci/</path>.</p>
348 <pre caption="needed after each kernel compile">
349 # <c>emerge alsa-driver</c>
350 </pre>
351 </body>
352 </section>
353 <section>
354 <title>/etc/modules.autoload</title>
355 <body>
356 <p>You won't have to edit this file for use with ALSA. After our <c>rc-update add alsasound boot</c>, our system will
357 load the correct modules at startup.</p>
358 <p>It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this file.
359 Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this FAQ</uri> for more info.</p>
360 </body>
361 </section>
362 <section>
363 <title>More links..</title>
364 <body>
365 <p>
366 You could check these for additional info:
367 </p>
368 <p>
369 <ul>
370 <li><uri link="http://www.gentoo.org/doc/en/desktop.xml">The Gentoo Linux Desktop Configuration Guide</uri></li>
371 <li><uri link="http://www.alsa-project.org">ALSA Project Homepage</uri></li>
372 <li><uri link="http://www.alsa-project.org/documentation.php3">ALSA Users Documentation</uri></li>
373 <li><uri link="http://www.djcj.org">ALSA Howto's and FAQ's</uri></li>
374 <li><uri link="http://tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri></li>
375 <li><uri link="http://linux-sound.org/">Sound and MIDI Software For Linux</uri></li>
376 </ul>
377 </p>
378 </body>
379 </section>
380 </chapter>
381 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20