/[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.17 Revision 1.22
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.22 2003/12/20 18:39:29 aaby Exp $ -->
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 4
4<guide link = "/doc/en/alsa-guide.xml"> 5<guide link = "/doc/en/alsa-guide.xml">
5<title>Gentoo Linux ALSA Guide</title> 6<title>Gentoo Linux ALSA Guide</title>
6<author title="Author"><mail link="zu@pandora.be"> 7<author title="Author">
7 Vincent Verleye</mail> 8 <mail link="zu@pandora.be">Vincent Verleye</mail>
8</author> 9</author>
9<author title="Author"><mail link="g2boojum@gentoo.org"> 10<author title="Author">
10 Grant Goodyear</mail> 11 <mail link="g2boojum@gentoo.org">Grant Goodyear</mail>
11</author> 12</author>
12<author title="Author"><mail link="agenkin@gentoo.org"> 13<author title="Author">
13 Arcady Genkin</mail> 14 <mail link="agenkin@gentoo.org">Arcady Genkin</mail>
14</author> 15</author>
15<author title="Editor"><mail link="zhen@gentoo.org"> 16<author title="Editor"><!-- zhen@gentoo.org -->
16 John P. Davis</mail> 17 John P. Davis
17</author> 18</author>
18<author title="Editor"><mail link="swift@gentoo.org"> 19<author title="Editor">
19 Sven Vermeulen</mail> 20 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
20</author> 21</author>
21<author title="Editor"><mail link="bennyc@gentoo.org"> 22<author title="Editor">
22 Benny Chuang</mail> 23 <mail link="bennyc@gentoo.org">Benny Chuang</mail>
23</author> 24</author>
24<author title="Editor"><mail link="blubber@gentoo.org"> 25<author title="Editor">
25 Tiemo Kieft</mail> 26 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
26</author> 27</author>
27 28
28<license/> 29<license/>
29 30
30<abstract> 31<abstract>
31This guide will show you how to set up the Advanced Linux Sound Architecture (ALSA) on Gentoo Linux. 32This guide will show you how to set up the Advanced Linux Sound Architecture
32In addition to the Gentoo Linux Desktop Configuration Guide, this guide is supposed to give you more information on this subject. </abstract> 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>
33 36
34<version>1.3.3</version> 37<version>1.3.4</version>
35<date>October 9, 2003</date> 38<date>November 23, 2003</date>
36 39
37<chapter> 40<chapter>
38<title>Introduction</title> 41<title>Introduction</title>
39<section> 42<section>
40 <title>What is ALSA?</title> 43<title>What is ALSA?</title>
41<body> 44<body>
45
42<p> 46<p>
43The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux sound subsystem by rewriting 47The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux
44large chunks of it. 48sound subsystem by rewriting large chunks of it. It is anticipated that ALSA
45It is anticipated that ALSA will make it into Linux kernel 2.6.x (or 3.x.x -- whichever comes first) as it becomes ready. 49will make it into Linux kernel 2.6.x (or 3.x.x -- whichever comes first) as it
50becomes ready.
46</p> 51</p>
47 52
48<p> 53<p>
49ALSA provides audio and MIDI functionality for Linux. 54ALSA provides audio and MIDI functionality for Linux.
50</p> 55</p>
51 56
52<p> 57<p>
53Quoted from <uri>http://www.alsa-project.org</uri>, ALSA has the following features: 58Quoted from <uri>http://www.alsa-project.org</uri>, ALSA has the following
54<ul><li> Efficient support for all types of audio interfaces, from consumer soundcards to professional multichannel audio interfaces.</li> 59features:
60</p>
61
62<ul>
63 <li>
64 Efficient support for all types of audio interfaces, from consumer
65 soundcards to professional multichannel audio interfaces
66 </li>
55 <li> Fully modularized sound drivers.</li> 67 <li>Fully modularized sound drivers</li>
56 <li> SMP and thread-safe design.</li> 68 <li>SMP and thread-safe design</li>
69 <li>
57 <li> User space library (alsa-lib) to simplify application programming and provide higher level functionality.</li> 70 User space library (alsa-lib) to simplify application programming and
71 provide higher level functionality
72 </li>
73 <li>
58 <li> Support for the older OSS API, providing binary compatibility for most OSS programs.</li> 74 Support for the older OSS API, providing binary compatibility for most OSS
75 programs
76 </li>
59</ul> 77</ul>
60There's lots more to ALSA however, like support for Full Duplex playback and recording, multiple soundcard support, 78
61hardware mixing of streams, extensive mixer capabilities (to support advanced features of new soundcards), ...
62</p> 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
63</body> 85</body>
64</section>
65<section> 86</section>
87<section>
66 <title>Why use ALSA?</title> 88<title>Why use ALSA?</title>
67<body> 89<body>
90
68<p> 91<p>
69If your soundcard is supported by the Linux kernel sound system or the commercial OSS/4Front sound driver system, 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
70which can be found in all 2.4.x Linux kernels, you could just aswell build <e>those modules</e> for use with your soundcard. 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
71If you want this, just read through the <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>. 96link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>.
72</p> 97</p>
98
73<p> 99<p>
74However, those OSS/4Front drivers have some limitations -- being commercial is one. 100However, those OSS/4Front drivers have some limitations -- being commercial is
75ALSA is an attempt to go beyond these limitations and to do so in an open source fashion. 101one. ALSA is an attempt to go beyond these limitations and to do so in an open-source fashion. ALSA is a fully GPL and LGPL'ed sound driver system, that
76ALSA is a fully GPL and LGPL'ed sound driver system, that provides a professional quality system for recording, playback, 102provides a professional quality system for recording, playback, and MIDI
77and MIDI sequencing. 103sequencing.
78</p> 104</p>
105
79</body> 106</body>
80</section>
81<section> 107</section>
108<section>
82 <title>What cards does ALSA support?</title> 109<title>What cards does ALSA support?</title>
83<body> 110<body>
111
84<p> 112<p>
85ALSA tries to support as many (new) cards as possible by providing open-source drivers. 113ALSA tries to support as many (new) cards as possible by providing open-source
86However, some vendors may provide binary-only packages. 114drivers. However, some vendors may provide binary-only packages.
115</p>
116
87</p> 117<p>
88<p>To know if your card is supported, you can find a Soundcard Matrix of supported and not-supported cards here: 118To know if your card is supported, you can find a Soundcard Matrix of supported
89<uri>http://www.alsa-project.org/alsa-doc/</uri>. 119and not-supported cards here: <uri>http://www.alsa-project.org/alsa-doc/</uri>.
90</p> 120</p>
121
91</body> 122</body>
92</section> 123</section>
93</chapter> 124</chapter>
94 125
95<chapter> 126<chapter>
105USE-variable before you start. 136USE-variable before you start.
106</p> 137</p>
107 138
108</body> 139</body>
109</section> 140</section>
110
111<section> 141<section>
112 <title>Kernel modules</title> 142<title>Kernel modules</title>
113<body> 143<body>
114<p> 144
115Since 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.
116</p> 145<p>
146Since we're still using 2.4.x kernel sources, we'll have to compile kernel
147modules and ALSA modules separately. People who are using a 2.5.x kernel can
148do this from within their kernel configuration, since the ALSA modules are
149included in the kernel sources and should be built there.
150</p>
151
117<p> 152<p>
118First we'll make sure that our kernel configuration is ready for use with ALSA. 153First we'll make sure that our kernel configuration is ready for use with ALSA.
119All you need in your kernel configuration is having Sound Card Support set to be built as a module (M). 154All you need in your kernel configuration is having Sound Card Support set to
120This will build <c>soundcore.o</c>. 155be built as a module (M). This will build <path>soundcore.o</path>.
121</p>
122<p> 156</p>
123<note> 157
124Possibly, this will also work when you built Sound Card Support in the kernel (Y) instead of building it as a module (M).
125However, the official ALSA documentation suggests building it as a module, since ALSA will try loading it.
126</note> 158<note>
159Possibly, this will also work when you built Sound Card Support in the kernel
160(Y) instead of building it as a module (M). However, the official ALSA
161documentation suggests building it as a module, since ALSA will try loading it.
162</note>
163
127</p> 164<p>
128<p>If you already have a working kernel configuration, make sure you remove all sound drivers (except for Sound Card Support). 165If you already have a working kernel configuration, make sure you remove all
129If you wish to do this without having to reboot, you could do like this: 166sound drivers (except for Sound Card Support). If you wish to do this without
167having to reboot, you could do like this:
130</p> 168</p>
131<pre> 169
170<pre caption="Kernel configuration">
132# <i>cd /usr/src/linux</i> 171# <i>cd /usr/src/linux</i>
133# <i>cp .config ~/</i> 172# <i>cp .config ~/</i>
134# <i>make mrproper</i> 173# <i>make mrproper</i>
135# <i>cp ~/.config .</i> 174# <i>cp ~/.config .</i>
136# <i>make menuconfig</i> 175# <i>make menuconfig</i>
137</pre> 176</pre>
177
138<p> 178<p>
139Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound drivers. 179Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound
140Exit and say Y to save your kernel configuration. 180drivers. Exit and say Y to save your kernel configuration. After that, build
141After that, build the modules: 181the modules:
142</p> 182</p>
143<pre> 183
184<pre caption="Kernel compilation">
144# <i>make dep clean</i> 185# <i>make dep clean</i>
145# <i>make modules modules_install</i> 186# <i>make modules modules_install</i>
146</pre> 187</pre>
188
147<p> 189<p>
148Before installing your new modules, this last line will delete all your previous modules, 190Before installing your new modules, this last line will delete all your previous
149even the ones from a previous ALSA installation. 191modules, even the ones from a previous ALSA installation.
150</p>
151<p> 192</p>
193
152<impo> 194<impo>
153This means, whenever you recompile your kernel later on, you MUST recompile <c>alsa-driver</c>. 195This means, whenever you recompile your kernel later on, you MUST recompile
196<c>alsa-driver</c>.
154</impo> 197</impo>
155</p>
156<p>
157<note>However, there's no need to reinstall <c>nvidia-kernel</c>, the Nvidia drivers are in a separate directory
158in <path>/lib/modules/*/video</path> and won't get deleted by a <c>make modules modules_install</c>
159</note>
160</p>
161</body>
162</section>
163 198
199</body>
164<section> 200</section>
201<section>
165 <title>ALSA modules</title> 202<title>ALSA modules</title>
166<body> 203<body>
167 204
168<p>
169Now it's time to install the ALSA drivers for your soundcard(s). If your soundcard is PCI, you can find out the name
170and type of your soundcard by looking at the output of /proc/pci.
171</p> 205<p>
172<pre> 206Now it's time to install the ALSA drivers for your soundcard(s). If your
207soundcard is PCI, you can find out the name and type of your soundcard by
208looking at the output of <path>/proc/pci</path>.
209</p>
210
211<pre caption="Search for soundcard information">
173# <i>grep audio /proc/pci</i> 212# <i>grep audio /proc/pci</i>
174</pre> 213</pre>
175 214
176
177<p>
178<warn> 215<warn>
179If you had a previous sound setup and there are still non-ALSA sound modules loaded, unload them <e>now</e>. 216If you had a previous sound setup and there are still non-ALSA sound modules
180Check with <c>lsmod</c> and use <c>rmmod</c> to unload all sound-related modules on your system. 217loaded, unload them <e>now</e>. Check with <c>lsmod</c> and use <c>rmmod</c>
218to unload all sound-related modules on your system.
181</warn> 219</warn>
220
182</p> 221<p>
183 222We could simply do an <c>emerge alsa-driver</c> now, this would compile and
223install <e>all</e> ALSA sound drivers.
184<p> 224</p>
185We could simply do an <c>emerge alsa-driver</c> now, this would compile and install <e>all</e> ALSA sound drivers. 225
186</p> 226<p>
187<p>
188However, to save some time, lookup the <e>Module Name</e> of your soundcard(s) on the 227However, to save some time, lookup the <e>Module Name</e> of your soundcard(s)
189<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. 228on the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard
229Matrix</uri> by following the <e>Details</e> link in the <e>Driver and Docs</e>
230column in the row of the chipset of your soundcard. Mine is <c>snd-emu10k1</c>,
190Mine is <c>snd-emu10k1</c>, since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. 231since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. We'll set
191We'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. 232ALSA_CARDS environment to the value of the module name before emerging (but
233without the snd prefix), so emerge will only compile the drivers we need.
192</p> 234</p>
193 235
194<pre> 236<pre caption="Compile correct modules">
195# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i> 237# <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i>
196</pre> 238</pre>
239
197<note> 240<note>
198You 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>. 241You can also add this value in <path>/etc/make.conf</path>, so when you have
242to emerge the alsa-driver later on you can just run <c>emerge alsa-driver</c>.
199For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c> 243For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c>
200</note> 244</note>
201 245
202<note> 246<note>
203When you want to install ALSA drivers for more than one soundcard, you could set ALSA_CARDS to a space-separated list 247When you want to install ALSA drivers for more than one soundcard, you could
248set ALSA_CARDS to a space-separated list of drivers; like this: <c>env
204of drivers; like this: <c>env ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c> 249ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c>
250</note>
251
205</note> 252<note>
206
207<note>If you want to have OSS compatibility, make sure to emerge <i>alsa-oss</i>, it is the ALSA/OSS compatibility 253If you want to have OSS compatibility, make sure to emerge <i>alsa-oss</i>, it
208wrapper. </note> 254is the ALSA/OSS compatibility wrapper.
255</note>
209 256
257<note>
210<note>If you plan on recompiling your kernels numerous times, it might 258If you plan on recompiling your kernels numerous times, it might
211be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This 259be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This
212will create a binary package for it. Later, after recompiling your kernel, 260will create a binary package for it. Later, after recompiling your kernel,
213you can just do <c>emerge --usepkg alsa-driver</c> which will install the 261you can just do <c>emerge --usepkg alsa-driver</c> which will install the
214binary package instead of recompiling it completely.</note> 262binary package instead of recompiling it completely.
263</note>
215 264
216<p> 265<p>
217After this, the ALSA modules should be installed on your system. 266After this, the ALSA modules should be installed on your system.
218</p> 267</p>
268
219</body> 269</body>
220</section>
221<section> 270</section>
271<section>
222 <title>Configuration of ALSA</title> 272<title>Configuration of ALSA</title>
223<body> 273<body>
274
224<p> 275<p>
225Let's start configuring now to get ALSA working properly. 276Let's start configuring now to get ALSA working properly. We'll need to edit
226We'll need to edit some files, to let our system know about the freshly installed ALSA modules. 277some files, to let our system know about the freshly installed ALSA modules.
227</p> 278</p>
228 279
229<p> 280<p>
230First, install <c>alsa-utils</c> on your system: 281First, install <c>alsa-utils</c> on your system:
231</p> 282</p>
235</pre> 286</pre>
236 287
237<p> 288<p>
238Hereafter, we need to edit <path>/etc/modules.d/alsa</path>. 289Hereafter, we need to edit <path>/etc/modules.d/alsa</path>.
239</p> 290</p>
291
240<warn> 292<warn>
241There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit files in <path>/etc/modules.d</path>. 293There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit
294files in <path>/etc/modules.d</path>.
242</warn> 295</warn>
296
243<p> 297<p>
244Check the ALSA portion <e>at the bottom of the file</e>. 298Check the ALSA portion <e>at the bottom of the file</e>. By tweaking this line
245By tweaking this line you can specify the max number of soundcards you have (generally, just one). 299you can specify the max number of soundcards you have (generally, just one).
246</p> 300</p>
301
247<pre caption="At the bottom of /etc/modules.d/alsa"> 302<pre caption="At the bottom of /etc/modules.d/alsa">
248<comment>Set this to the correct number of cards.</comment> 303<comment>Set this to the correct number of cards.</comment>
249options snd cards_limit=1 304options snd cards_limit=1
250</pre> 305</pre>
306
251<p> 307<p>
252Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit like this: 308Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit
309like this:
253</p> 310</p>
311
254<pre caption="In /etc/modules.d/alsa"> 312<pre caption="In /etc/modules.d/alsa">
255## and then run `modules-update' command. 313## and then run `modules-update' command.
256## Read alsa-driver's INSTALL file in /usr/share/doc for more info. 314## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
257## 315##
258## ALSA portion 316## ALSA portion
263## OSS/Free portion 321## OSS/Free portion
264## alias sound-slot-0 snd-card-0 322## alias sound-slot-0 snd-card-0
265## alias sound-slot-1 snd-card-1 323## alias sound-slot-1 snd-card-1
266## 324##
267</pre> 325</pre>
326
268<note> 327<note>
269If you have more than one soundcard, adjust the <c>cards_limit</c> value and add more snd-card aliases to the file. 328If you have more than one soundcard, adjust the <c>cards_limit</c> value and add
270I don't have experience with this, but you can find examples for configurations with two or more soundcards in 329more snd-card aliases to the file. I don't have experience with this, but you
330can find examples for configurations with two or more soundcards in <uri
271<uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri> 331link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri>
332of the <uri
272of the <uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA Howto</uri>. 333link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA
334Howto</uri>.
273</note> 335</note>
336
274<p> 337<p>
275Last thing to do in this file, almost at the end, check if these lines are there and uncommented: 338Last thing to do in this file, almost at the end, check if these lines are there
339and uncommented:
276</p> 340</p>
341
277<pre caption="Near the end of /etc/modules.d/alsa"> 342<pre caption="Near the end of /etc/modules.d/alsa">
278alias /dev/mixer snd-mixer-oss 343alias /dev/mixer snd-mixer-oss
279alias /dev/dsp snd-pcm-oss 344alias /dev/dsp snd-pcm-oss
280alias /dev/midi snd-seq-oss 345alias /dev/midi snd-seq-oss
281</pre> 346</pre>
347
348<p>
349Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure
350everyting is ok, run <c>modules-update</c>.
282<p> 351</p>
283Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure everyting is ok, run <c>modules-update</c>. 352
284<pre> 353<pre caption="Running modules-update">
285# <i>modules-update</i> 354# <i>modules-update</i>
286</pre> 355</pre>
287</p> 356
288<note>
289Running <c>modules-update</c> here will insert the data from <path>/etc/modules.d/alsa</path> into <path>/etc/modules.conf</path>
290</note> 357<note>
291<p> 358Running <c>modules-update</c> here will insert the data from
292You should also verify that /etc/devfsd.conf has the alsa devices and permissions correctly registered. 359<path>/etc/modules.d/alsa</path> into <path>/etc/modules.conf</path>
360</note>
361
293</p> 362<p>
363You should also verify that <path>/etc/devfsd.conf</path> has the alsa devices
364and permissions correctly registered.
365</p>
366
294<pre caption="/etc/devfsd.conf"> 367<pre caption="/etc/devfsd.conf">
295# ALSA/OSS stuff 368# ALSA/OSS stuff
296# Comment/change these if you want to change the permissions on 369# Comment/change these if you want to change the permissions on
297# the audio devices 370# the audio devices
298LOOKUP snd MODLOAD ACTION snd 371LOOKUP snd MODLOAD ACTION snd
300LOOKUP mixer MODLOAD 373LOOKUP mixer MODLOAD
301LOOKUP midi MODLOAD 374LOOKUP midi MODLOAD
302REGISTER sound/.* PERMISSIONS root.audio 660 375REGISTER sound/.* PERMISSIONS root.audio 660
303REGISTER snd/.* PERMISSIONS root.audio 660 376REGISTER snd/.* PERMISSIONS root.audio 660
304</pre> 377</pre>
305<note> 378
306Notice 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.
307</note> 379<note>
380Notice that devfsd.conf sets <path>/dev/sound</path> permissions to be
381root.audio. Thus, for non-root users to use audio they will have to be part of
382the audio group.
383</note>
384
308</body> 385</body>
309</section> 386</section>
310</chapter> 387</chapter>
388
311<chapter> 389<chapter>
312<title>Starting ALSA</title> 390<title>Starting ALSA</title>
313<section> 391<section>
314 <title>Adding alsasound to a runlevel</title> 392<title>Adding alsasound to a runlevel</title>
315<body> 393<body>
394
316<p> 395<p>
317First thing to do now, is to make ALSA startup at boottime. Like this: 396First thing to do now, is to make ALSA startup at boottime. Like this:
318<pre> 397</p>
398
399<pre caption="Add ALSA to the boot runlevel">
319# <i>rc-update add alsasound boot</i> 400# <i>rc-update add alsasound boot</i>
320</pre> 401</pre>
321</p> 402
322<p> 403<warn>
323<warn>Note that the alsasound script should be added to the "boot" runlevel, not the "default" runlevel.</warn> 404Note that the alsasound script should be added to the "boot" runlevel, not the
324</p> 405"default" runlevel.
406</warn>
407
325</body> 408</body>
326</section>
327<section> 409</section>
410<section>
328 <title>Running and unmuting</title> 411<title>Running and unmuting</title>
329<body> 412<body>
413
330<p> 414<p>
331Since we're Linux users, we don't want to reboot. So we'll start the alsasound script manually. 415Since we're Linux users, we don't want to reboot. So we'll start the alsasound
416script manually.
332</p> 417</p>
333<pre> 418
419<pre caption="Starting ALSA">
334# <i>/etc/init.d/alsasound start</i> 420# <i>/etc/init.d/alsasound start</i>
335</pre> 421</pre>
336<p> 422
337ALSA is running now. If everything is ok, you should be able to see the ALSA modules loaded when running <c>lsmod</c>.
338However, sound won't work yet, because the channels are still muted. We need <c>amixer</c> for this.
339</p> 423<p>
424ALSA is running now. If everything is ok, you should be able to see the ALSA
425modules loaded when running <c>lsmod</c>. However, sound won't work yet,
426because the channels are still muted. We need <c>amixer</c> to fix this.
427</p>
428
340<pre caption = "Running amixer"> 429<pre caption = "Running amixer">
341# <i>amixer</i> 430# <i>amixer</i>
342</pre> 431</pre>
343<p> 432
344<warn> 433<warn>
345You 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 modprobe 434You shouldn't get this, but <e>if</e> you get an error about "amixer: Mixer
435attach default error: No such file or directory", you should manually modprobe
346<c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again. 436<c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again.
347</warn> 437</warn>
348</p> 438
349<pre caption="only if you get an error when running amixer"> 439<pre caption="Only if you get an error when running amixer">
350# <i>modprobe snd-mixer-oss</i> 440# <i>modprobe snd-mixer-oss</i>
351# <i>modprobe snd-pcm-oss</i> 441# <i>modprobe snd-pcm-oss</i>
352# <i>amixer</i> 442# <i>amixer</i>
353</pre> 443</pre>
444
354<p> 445<p>
355If you got this far, now unmute Master and PCM channels. Some hardware 446If you got this far, now unmute Master and PCM channels. Some hardware
356even requires you to unmute the center channel or even the surround 447even requires you to unmute the center channel or even the surround
357channel. 448channel.
358</p> 449</p>
359<p> 450
360<pre caption = "Unmuting channels"> 451<pre caption = "Unmuting channels">
361# <i>amixer set Master 100 unmute</i> 452# <i>amixer set Master 100 unmute</i>
362# <i>amixer set PCM 100 unmute</i> 453# <i>amixer set PCM 100 unmute</i>
363<comment>Only if the above doesn't succeed on its own:</comment> 454<comment>Only if the above doesn't succeed on its own:</comment>
364# <i>amixer set Center 100 unmute</i> 455# <i>amixer set Center 100 unmute</i>
365# <i>amixer set Surround 100 unmute</i> 456# <i>amixer set Surround 100 unmute</i>
366<comment>Test the sound:</comment> 457<comment>Test the sound:</comment>
367# <i>aplay $KDEDIR/share/sounds/pop.wav</i> <codenote>(pop.wav is part of KDE)</codenote> 458# <i>aplay $KDEDIR/share/sounds/pop.wav</i> <codenote>(pop.wav is part of KDE)</codenote>
368</pre> 459</pre>
460
369</p> 461<p>
370We check to see if sound is working by using the aplay (alsa play) command. If you hear a pop, then sound is indeed working. 462We check to see if sound is working by using the aplay (alsa play) command. If
463you hear a pop, then sound is indeed working. Then, adjust the volume settings
371Then, adjust the volume settings to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them "just so". 464to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them
465"just so".
372<p> 466</p>
467
468<p>
373You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for XMMS. 469You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for
470XMMS.
471</p>
472
374</p> 473<p>
375When you reboot your system, the <e>alsasound</e> init script will properly save and restore your volume settings. 474When you reboot your system, the <c>alsasound</c> init script will
475properly save and restore your volume settings.
476</p>
477
376</body> 478</body>
377</section> 479</section>
378</chapter> 480</chapter>
481
379<chapter> 482<chapter>
380<title>Final Notes</title> 483<title>Final Notes</title>
381<section> 484<section>
382 <title>After kernel-upgrades..</title> 485<title>After kernel-upgrades...</title>
383<body> 486<body>
487
488<p>
384<p>When you ever rebuild your kernel, or upgrade to another kernel, you'll have to rebuild the ALSA modules.</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>
385<p>Although you might have installed <c>alsa-driver</c>, <c>alsa-libs</c> and <c>alsa-utils</c>, only the first will 494Although you might have installed <c>alsa-driver</c>, <c>alsa-libs</c> and
386have to be installed again, since it will put the alsa modules in 495<c>alsa-utils</c>, only the first will have to be installed again, since it will
387<path>/lib/modules/*/kernel/sound/pci/</path>.</p> 496put the alsa modules in <path>/lib/modules/*/kernel/sound/pci/</path>.
497</p>
498
388<pre caption="needed after each kernel compile"> 499<pre caption="Needed after each kernel compile">
389# <i>emerge alsa-driver</i> 500# <i>emerge alsa-driver</i>
390</pre> 501</pre>
502
391</body> 503</body>
392</section>
393<section> 504</section>
505<section>
394 <title>/etc/modules.autoload</title> 506<title>/etc/modules.autoload</title>
395<body> 507<body>
508
509<p>
396<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 510You won't have to edit this file for use with ALSA. After our <c>rc-update add
397load the correct modules at startup.</p> 511alsasound boot</c>, our system will load the correct modules at startup.
512</p>
513
514<p>
398<p>It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this file. 515It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this
399Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this FAQ</uri> for more info.</p> 516file. Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this
400</body> 517FAQ</uri> for more info.
401</section> 518</p>
402 519
520</body>
521</section>
403<section> 522<section>
404<title>Known bugs</title> 523<title>Known bugs</title>
405<body> 524<body>
406 525
407<note> 526<note>
408This guide lags behind on the alsa-development. Chances are these bugs 527This guide lags behind on the alsa-development. Chances are these bugs
409are already fixed when you read this. 528are already fixed when you read this.
410</note> 529</note>
411 530
412<ul> 531<ul>
413<li> 532 <li>
414If you have <b>lots of noise</b> when using <b>oss</b> emulation, add 533 If you have <b>lots of noise</b> when using <b>oss</b> emulation, add
415<e>options snd-pcm-oss dsp_map=1</e> to 534 <e>options snd-pcm-oss dsp_map=1</e> to <path>/etc/modules.d/alsa</path>
416<path>/etc/modules.d/alsa</path>.
417</li> 535 </li>
418</ul> 536</ul>
419 537
420</body> 538</body>
421</section> 539</section>
540<section>
541<title>Activating Joystick Support</title>
542<body>
422 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>
423<section> 580</section>
581<section>
424 <title>More links..</title> 582<title>More links...</title>
425<body> 583<body>
584
426<p> 585<p>
427You could check these for additional info: 586You could check these for additional info:
428</p> 587</p>
429<p> 588
430<ul> 589<ul>
590 <li>
431<li><uri link="http://www.gentoo.org/doc/en/desktop.xml">The Gentoo Linux Desktop Configuration Guide</uri></li> 591 <uri link="http://www.gentoo.org/doc/en/desktop.xml">The Gentoo Linux
592 Desktop Configuration Guide</uri>
593 </li>
594 <li>
432<li><uri link="http://www.alsa-project.org">ALSA Project Homepage</uri></li> 595 <uri link="http://www.alsa-project.org">ALSA Project Homepage</uri>
596 </li>
597 <li>
433<li><uri link="http://www.alsa-project.org/documentation.php3">ALSA Users Documentation</uri></li> 598 <uri link="http://www.alsa-project.org/documentation.php3">ALSA Users
599 Documentation</uri>
600 </li>
601 <li>
434<li><uri link="http://www.djcj.org">ALSA Howto's and FAQ's</uri></li> 602 <uri link="http://www.djcj.org">ALSA Howto's and FAQ's</uri>
603 </li>
604 <li>
435<li><uri link="http://tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri></li> 605 <uri link="http://tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound
606 HOWTO</uri>
607 </li>
608 <li>
436<li><uri link="http://linux-sound.org/">Sound and MIDI Software For Linux</uri></li> 609 <uri link="http://linux-sound.org/">Sound and MIDI Software For Linux</uri>
610 </li>
437</ul> 611</ul>
438</p> 612
439</body> 613</body>
440</section> 614</section>
441</chapter> 615</chapter>
442</guide> 616</guide>

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.22

  ViewVC Help
Powered by ViewVC 1.1.20