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.45 2004/12/02 20:27:35 dertobi123 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> |
|
|
16 | <author title="Author"> |
|
|
17 | <mail link="eradicator@gentoo.org">Jeremy Huddleston</mail> |
|
|
18 | </author> |
15 | <author title="Editor"><mail link="zhen@gentoo.org"> |
19 | <author title="Editor"><!-- zhen@gentoo.org --> |
16 | John P. Davis</mail> |
20 | John P. Davis |
17 | </author> |
21 | </author> |
18 | <author title="Editor"><mail link="swift@gentoo.org"> |
22 | <author title="Editor"> |
19 | Sven Vermeulen</mail> |
23 | <mail link="swift@gentoo.org">Sven Vermeulen</mail> |
20 | </author> |
24 | </author> |
21 | <author title="Editor"><mail link="bennyc@gentoo.org"> |
25 | <author title="Editor"> |
22 | Benny Chuang</mail> |
26 | <mail link="bennyc@gentoo.org">Benny Chuang</mail> |
23 | </author> |
27 | </author> |
24 | <author title="Editor"><mail link="blubber@gentoo.org"> |
28 | <author title="Editor"> |
25 | Tiemo Kieft</mail> |
29 | <mail link="blubber@gentoo.org">Tiemo Kieft</mail> |
26 | </author> |
30 | </author> |
|
|
31 | <author title="Editor"> |
|
|
32 | <mail link="erwin@gentoo.org">Erwin</mail> |
|
|
33 | </author> |
|
|
34 | |
|
|
35 | <abstract> |
|
|
36 | This guide will show you how to set up the Advanced Linux Sound Architecture |
|
|
37 | (ALSA) on Gentoo Linux. In addition to the Gentoo Linux Desktop Configuration |
|
|
38 | Guide, this guide is supposed to give you more information on this subject. |
|
|
39 | </abstract> |
27 | |
40 | |
28 | <license/> |
41 | <license/> |
29 | |
42 | |
30 | <abstract> |
|
|
31 | This guide will show you how to set up the Advanced Linux Sound Architecture (ALSA) on Gentoo Linux. |
|
|
32 | In addition to the Gentoo Linux Desktop Configuration Guide, this guide is supposed to give you more information on this subject. </abstract> |
|
|
33 | |
|
|
34 | <version>1.3.3</version> |
43 | <version>1.5.7</version> |
35 | <date>October 9, 2003</date> |
44 | <date>2004-12-02</date> |
36 | |
45 | |
37 | <chapter> |
46 | <chapter> |
38 | <title>Introduction</title> |
47 | <title>The Advanced Linux Sound Architecture</title> |
39 | <section> |
48 | <section> |
40 | <title>What is ALSA?</title> |
49 | <title>What is ALSA?</title> |
41 | <body> |
|
|
42 | <p> |
|
|
43 | The Advanced Linux Sound Architecture (ALSA) is a project to improve the Linux sound subsystem by rewriting |
|
|
44 | large chunks of it. |
|
|
45 | 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. |
|
|
46 | </p> |
|
|
47 | |
|
|
48 | <p> |
|
|
49 | ALSA provides audio and MIDI functionality for Linux. |
|
|
50 | </p> |
|
|
51 | |
|
|
52 | <p> |
|
|
53 | Quoted from <uri>http://www.alsa-project.org</uri>, ALSA has the following features: |
|
|
54 | <ul><li> Efficient support for all types of audio interfaces, from consumer soundcards to professional multichannel audio interfaces.</li> |
|
|
55 | <li> Fully modularized sound drivers.</li> |
|
|
56 | <li> SMP and thread-safe design.</li> |
|
|
57 | <li> User space library (alsa-lib) to simplify application programming and provide higher level functionality.</li> |
|
|
58 | <li> Support for the older OSS API, providing binary compatibility for most OSS programs.</li> |
|
|
59 | </ul> |
|
|
60 | There's lots more to ALSA however, like support for Full Duplex playback and recording, multiple soundcard support, |
|
|
61 | hardware mixing of streams, extensive mixer capabilities (to support advanced features of new soundcards), ... |
|
|
62 | </p> |
|
|
63 | </body> |
50 | <body> |
64 | </section> |
51 | |
65 | <section> |
|
|
66 | <title>Why use ALSA?</title> |
|
|
67 | <body> |
|
|
68 | <p> |
52 | <p> |
69 | If your soundcard is supported by the Linux kernel sound system or the commercial OSS/4Front sound driver system, |
53 | ALSA is the <e>Advanced Linux Sound Architecture</e>, a project dedicated to the |
70 | 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. |
54 | development of a high-quality Linux sound subsystem. It has replaced OSS |
71 | If you want this, just read through the <uri link="http://www.tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri>. |
55 | (<e>Open Sound System</e>) as default sound subsystem in the 2.6 kernel series. |
72 | </p> |
56 | </p> |
|
|
57 | |
73 | <p> |
58 | <p> |
74 | However, those OSS/4Front drivers have some limitations -- being commercial is one. |
59 | ALSA provides efficient support for all types of audio interfaces, is fully |
75 | ALSA is an attempt to go beyond these limitations and to do so in an open source fashion. |
60 | modularized, is SMP and thread-safe and provides a high-quality user space |
76 | ALSA is a fully GPL and LGPL'ed sound driver system, that provides a professional quality system for recording, playback, |
61 | library called <e>alsa-lib</e> to simplify application programming. It also |
77 | and MIDI sequencing. |
62 | provides a backwards compatibility layer with OSS. |
78 | </p> |
63 | </p> |
79 | </body> |
64 | |
80 | </section> |
|
|
81 | <section> |
|
|
82 | <title>What cards does ALSA support?</title> |
|
|
83 | <body> |
|
|
84 | <p> |
|
|
85 | ALSA tries to support as many (new) cards as possible by providing open-source drivers. |
|
|
86 | However, some vendors may provide binary-only packages. |
|
|
87 | </p> |
|
|
88 | <p>To know if your card is supported, you can find a Soundcard Matrix of supported and not-supported cards here: |
|
|
89 | <uri>http://www.alsa-project.org/alsa-doc/</uri>. |
|
|
90 | </p> |
|
|
91 | </body> |
65 | </body> |
92 | </section> |
66 | </section> |
93 | </chapter> |
67 | </chapter> |
94 | |
|
|
95 | <chapter> |
68 | <chapter> |
96 | <title>Installation</title> |
69 | <title>Installing ALSA</title> |
97 | <section> |
|
|
98 | <title>Gentoo USE flags</title> |
|
|
99 | <body> |
|
|
100 | |
|
|
101 | <p> |
|
|
102 | To compile programs with ALSA-support, be sure to add <e>alsa</e> to |
|
|
103 | your USE-variable. However, several tools don't support alsa yet, and |
|
|
104 | require OSS. ALSA provides OSS-emulation if you define <e>oss</e> in your |
|
|
105 | USE-variable before you start. |
|
|
106 | </p> |
|
|
107 | |
|
|
108 | </body> |
|
|
109 | </section> |
70 | <section> |
|
|
71 | <title>USE Flags</title> |
|
|
72 | <body> |
110 | |
73 | |
|
|
74 | <p> |
|
|
75 | Gentoo provides an <c>alsa</c> USE flag which you should set in |
|
|
76 | <path>/etc/make.conf</path> to allow our available packages to compile with |
|
|
77 | ALSA support. If you have <c>oss</c> in your USE variable as well, ALSA will |
|
|
78 | compile with OSS backward compatibility. |
|
|
79 | </p> |
|
|
80 | |
|
|
81 | </body> |
111 | <section> |
82 | </section> |
|
|
83 | <section> |
112 | <title>Kernel modules</title> |
84 | <title>Kernel Modules</title> |
113 | <body> |
85 | <body> |
114 | <p> |
86 | |
115 | 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. |
|
|
116 | </p> |
87 | <p> |
|
|
88 | First of all, before continuing, make sure your kernel has <e>Sound Card |
|
|
89 | Support</e> enabled. If you used <c>genkernel</c> to build your kernel, then |
|
|
90 | this is automatically true. Otherwise reconfigure your kernel. |
117 | <p> |
91 | </p> |
118 | First we'll make sure that our kernel configuration is ready for use with ALSA. |
92 | |
119 | All you need in your kernel configuration is having Sound Card Support set to be built as a module (M). |
93 | <warn> |
120 | This will build <c>soundcore.o</c>. |
94 | If you use a 2.6 kernel you can skip the rest of this section and continue with |
|
|
95 | <uri link="#alsa-utils">Installing the ALSA Utils</uri> as 2.6 already has the |
|
|
96 | necessary ALSA drivers in it. Of course, don't forget to enable support for the |
|
|
97 | sound card you have when configuring your kernel. |
|
|
98 | </warn> |
|
|
99 | |
121 | </p> |
100 | <p> |
|
|
101 | Users of 2.4 kernel sources will have to install the necessary ALSA drivers for |
|
|
102 | their soundcard. First find out what soundcard you have. An easy trick is to |
|
|
103 | search for "audio" in the output of the <c>lspci</c> command. You can install |
|
|
104 | it with <c>emerge pciutils</c>. |
122 | <p> |
105 | </p> |
123 | <note> |
106 | |
124 | Possibly, this will also work when you built Sound Card Support in the kernel (Y) instead of building it as a module (M). |
107 | <pre caption="Finding out the soundcard type"> |
125 | However, the official ALSA documentation suggests building it as a module, since ALSA will try loading it. |
108 | # <i>lspci | grep -i audio</i> |
126 | </note> |
109 | Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 64). |
127 | </p> |
|
|
128 | <p>If you already have a working kernel configuration, make sure you remove all sound drivers (except for Sound Card Support). |
|
|
129 | If you wish to do this without having to reboot, you could do like this: |
|
|
130 | </p> |
|
|
131 | <pre> |
110 | </pre> |
132 | # <i>cd /usr/src/linux</i> |
111 | |
133 | # <i>cp .config ~/</i> |
|
|
134 | # <i>make mrproper</i> |
|
|
135 | # <i>cp ~/.config .</i> |
|
|
136 | # <i>make menuconfig</i> |
|
|
137 | </pre> |
|
|
138 | <p> |
|
|
139 | Now select <e>Sound Card Support</e> as Module (M) and deselect all other sound drivers. |
|
|
140 | Exit and say Y to save your kernel configuration. |
|
|
141 | After that, build the modules: |
|
|
142 | </p> |
112 | <p> |
|
|
113 | Now go to the <uri link="http://www.alsa-project.org/alsa-doc">ALSA Soundcard |
|
|
114 | Matrix</uri> and search for your soundcard. In the above example you should go |
|
|
115 | to the "VIA" manufacturer. You will receive a table with the known chipsets of |
|
|
116 | that vendor. The chipset in the above example is "via82c686"; the "Details" link |
|
|
117 | then informs me that the driver is called <path>via82xx</path>. This is all the |
|
|
118 | information you need, so you can safely discard the rest of that document. |
|
|
119 | </p> |
|
|
120 | |
|
|
121 | <p> |
|
|
122 | Based on this information we can now install the <c>alsa-driver</c> for our |
|
|
123 | soundcard. First edit <path>/etc/make.conf</path> and <e>add</e> a new option |
|
|
124 | called ALSA_CARDS to it. Inside this variable you declare the soundcard driver |
|
|
125 | you want to use: |
|
|
126 | </p> |
|
|
127 | |
|
|
128 | <pre caption="Editing /etc/make.conf for ALSA_CARDS"> |
|
|
129 | ALSA_CARDS="via82xx" |
143 | <pre> |
130 | </pre> |
144 | # <i>make dep clean</i> |
131 | |
145 | # <i>make modules modules_install</i> |
|
|
146 | </pre> |
|
|
147 | <p> |
|
|
148 | Before installing your new modules, this last line will delete all your previous modules, |
|
|
149 | even the ones from a previous ALSA installation. |
|
|
150 | </p> |
132 | <p> |
|
|
133 | Now install <c>alsa-driver</c>: |
151 | <p> |
134 | </p> |
|
|
135 | |
|
|
136 | <pre caption="Installing ALSA Drivers"> |
|
|
137 | # <i>emerge alsa-driver</i> |
|
|
138 | </pre> |
|
|
139 | |
152 | <impo> |
140 | <impo> |
153 | This means, whenever you recompile your kernel later on, you MUST recompile <c>alsa-driver</c>. |
141 | Whenever you (re)compile your kernel sources, chances are that the ALSA drivers |
|
|
142 | will be overwritten. It is therefore adviseable to rerun <c>emerge |
|
|
143 | alsa-driver</c> every time you (re)compile your kernel <e>after</e> having |
|
|
144 | rebooted into the new kernel. |
154 | </impo> |
145 | </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 |
|
|
158 | in <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 | |
146 | |
|
|
147 | </body> |
164 | <section> |
148 | </section> |
165 | <title>ALSA modules</title> |
149 | <section id="alsa-utils"> |
166 | <body> |
150 | <title>Installing the ALSA Utils</title> |
167 | |
|
|
168 | <p> |
|
|
169 | Now it's time to install the ALSA drivers for your soundcard(s). If your soundcard is PCI, you can find out the name |
|
|
170 | and type of your soundcard by looking at the output of /proc/pci. |
|
|
171 | </p> |
|
|
172 | <pre> |
|
|
173 | # <i>grep audio /proc/pci</i> |
|
|
174 | </pre> |
|
|
175 | |
|
|
176 | |
|
|
177 | <p> |
|
|
178 | <warn> |
|
|
179 | If you had a previous sound setup and there are still non-ALSA sound modules loaded, unload them <e>now</e>. |
|
|
180 | Check with <c>lsmod</c> and use <c>rmmod</c> to unload all sound-related modules on your system. |
|
|
181 | </warn> |
|
|
182 | </p> |
|
|
183 | |
|
|
184 | <p> |
|
|
185 | We could simply do an <c>emerge alsa-driver</c> now, this would compile and install <e>all</e> ALSA sound drivers. |
|
|
186 | </p> |
|
|
187 | <p> |
|
|
188 | However, to save some time, lookup the <e>Module Name</e> of your soundcard(s) on the |
|
|
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. |
|
|
190 | Mine is <c>snd-emu10k1</c>, since I have an SBlive! soundcard, with the <e>EMU10K1</e> chipset. |
|
|
191 | 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. |
|
|
192 | </p> |
|
|
193 | |
|
|
194 | <pre> |
|
|
195 | # <i>env ALSA_CARDS='emu10k1' emerge alsa-driver</i> |
|
|
196 | </pre> |
|
|
197 | <note> |
|
|
198 | 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>. |
|
|
199 | For example, like this: <c>echo 'ALSA_CARDS="emu10k1"' >> /etc/make.conf</c> |
|
|
200 | </note> |
|
|
201 | |
|
|
202 | <note> |
|
|
203 | When you want to install ALSA drivers for more than one soundcard, you could set ALSA_CARDS to a space-separated list |
|
|
204 | of drivers; like this: <c>env ALSA_CARDS='emu10k1 intel8x0 ens1370' emerge alsa-driver</c> |
|
|
205 | </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 |
|
|
208 | wrapper. </note> |
|
|
209 | |
|
|
210 | <note>If you plan on recompiling your kernels numerous times, it might |
|
|
211 | be adviseable to emerge <c>alsa-driver</c> with <c>--buildpkg</c>. This |
|
|
212 | will create a binary package for it. Later, after recompiling your kernel, |
|
|
213 | you can just do <c>emerge --usepkg alsa-driver</c> which will install the |
|
|
214 | binary package instead of recompiling it completely.</note> |
|
|
215 | |
|
|
216 | <p> |
|
|
217 | After this, the ALSA modules should be installed on your system. |
|
|
218 | </p> |
|
|
219 | </body> |
151 | <body> |
220 | </section> |
152 | |
221 | <section> |
|
|
222 | <title>Configuration of ALSA</title> |
|
|
223 | <body> |
|
|
224 | <p> |
|
|
225 | Let's start configuring now to get ALSA working properly. |
|
|
226 | We'll need to edit some files, to let our system know about the freshly installed ALSA modules. |
|
|
227 | </p> |
153 | <p> |
228 | |
154 | If you want backwards compatibility with OSS, you need to install |
|
|
155 | <c>alsa-oss</c>: |
229 | <p> |
156 | </p> |
230 | First, install <c>alsa-utils</c> on your system: |
157 | |
|
|
158 | <pre caption="Installing the ALSA OSS compatibility layer"> |
|
|
159 | # <i>emerge alsa-oss</i> |
|
|
160 | </pre> |
|
|
161 | |
231 | </p> |
162 | <p> |
|
|
163 | Now install the ALSA Utils on your system (this is mandatory): |
|
|
164 | </p> |
232 | |
165 | |
233 | <pre caption = "Emerging alsa-utils"> |
166 | <pre caption="Installing ALSA Utils"> |
234 | # <i>emerge alsa-utils</i> |
167 | # <i>emerge alsa-utils</i> |
235 | </pre> |
168 | </pre> |
236 | |
169 | |
237 | <p> |
170 | <p> |
238 | Hereafter, we need to edit <path>/etc/modules.d/alsa</path>. |
171 | Now that the utils are installed, it is time to configure ALSA... |
239 | </p> |
|
|
240 | <warn> |
|
|
241 | There is no need to edit <path>/etc/modules.conf</path>. Instead, always edit files in <path>/etc/modules.d</path>. |
|
|
242 | </warn> |
|
|
243 | <p> |
172 | </p> |
244 | Check the ALSA portion <e>at the bottom of the file</e>. |
173 | |
245 | By tweaking this line you can specify the max number of soundcards you have (generally, just one). |
174 | </body> |
|
|
175 | </section> |
|
|
176 | </chapter> |
|
|
177 | <chapter> |
|
|
178 | <title>Configuring ALSA</title> |
|
|
179 | <section> |
|
|
180 | <title>Automatically Loading the Kernel Modules</title> |
|
|
181 | <body> |
|
|
182 | |
246 | </p> |
183 | <p> |
247 | <pre caption="At the bottom of /etc/modules.d/alsa"> |
184 | If you use a modular kernel (such as when using <c>genkernel</c>) you have to |
248 | <comment>Set this to the correct number of cards.</comment> |
185 | edit <path>/etc/modules.d/alsa</path> so that it activates the necesary modules |
249 | options snd cards_limit=1 |
186 | at boot time. For the soundcard in our example: |
250 | </pre> |
|
|
251 | <p> |
187 | </p> |
252 | Now we'll specify the sounddriver(s) ALSA should use. In the same file, edit like this: |
188 | |
253 | </p> |
|
|
254 | <pre caption="In /etc/modules.d/alsa"> |
189 | <pre caption="/etc/modules.d/alsa"> |
255 | ## and then run `modules-update' command. |
|
|
256 | ## Read alsa-driver's INSTALL file in /usr/share/doc for more info. |
|
|
257 | ## |
|
|
258 | ## ALSA portion |
|
|
259 | alias snd-card-0 snd-emu10k1 |
|
|
260 | <comment>## If you have more than one, add:</comment> |
|
|
261 | ## alias snd-card-1 snd-intel8x0 |
190 | alias snd-card-0 snd-via82xx |
262 | ## alias snd-card-2 snd-ens1370 |
191 | <comment># The following is only needed when you want OSS compatibility</comment> |
263 | ## OSS/Free portion |
|
|
264 | ## alias sound-slot-0 snd-card-0 |
192 | alias sound-slot-0 snd-card-0 |
265 | ## alias sound-slot-1 snd-card-1 |
|
|
266 | ## |
|
|
267 | </pre> |
|
|
268 | <note> |
|
|
269 | If you have more than one soundcard, adjust the <c>cards_limit</c> value and add more snd-card aliases to the file. |
|
|
270 | I don't have experience with this, but you can find examples for configurations with two or more soundcards in |
|
|
271 | <uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/c1660.htm">Chapter 6</uri> |
|
|
272 | of the <uri link="http://www.alsa-project.org/alsa-doc/alsa-howto/alsa-howto.html">ALSA Howto</uri>. |
|
|
273 | </note> |
|
|
274 | <p> |
|
|
275 | Last thing to do in this file, almost at the end, check if these lines are there and uncommented: |
|
|
276 | </p> |
|
|
277 | <pre caption="Near the end of /etc/modules.d/alsa"> |
|
|
278 | alias /dev/mixer snd-mixer-oss |
193 | alias /dev/mixer snd-mixer-oss |
279 | alias /dev/dsp snd-pcm-oss |
194 | alias /dev/dsp snd-pcm-oss |
280 | alias /dev/midi snd-seq-oss |
195 | alias /dev/midi snd-seq-oss |
281 | </pre> |
196 | </pre> |
|
|
197 | |
|
|
198 | <p> |
|
|
199 | Now run <c>modules-update</c> to save the changes you made to the |
|
|
200 | <path>alsa</path> file into <path>/etc/modules.conf</path>: |
282 | <p> |
201 | </p> |
283 | Now double-check the file <path>/etc/modules.d/alsa</path> and when you're sure everyting is ok, run <c>modules-update</c>. |
202 | |
284 | <pre> |
203 | <pre caption="Running modules-update"> |
285 | # <i>modules-update</i> |
204 | # <i>modules-update</i> |
286 | </pre> |
205 | </pre> |
|
|
206 | |
|
|
207 | </body> |
|
|
208 | </section> |
|
|
209 | <section> |
|
|
210 | <title>Verifying the Device Files</title> |
|
|
211 | <body> |
|
|
212 | |
287 | </p> |
213 | <p> |
288 | <note> |
214 | If you use DevFS (which is the default for Gentoo installations) make sure that |
289 | Running <c>modules-update</c> here will insert the data from <path>/etc/modules.d/alsa</path> into <path>/etc/modules.conf</path> |
215 | <path>/etc/devfsd.conf</path> has the ALSA devices and permissions correctly |
290 | </note> |
216 | registered: |
291 | <p> |
217 | </p> |
292 | You should also verify that /etc/devfsd.conf has the alsa devices and permissions correctly registered. |
218 | |
293 | </p> |
|
|
294 | <pre caption="/etc/devfsd.conf"> |
219 | <pre caption="/etc/devfsd.conf"> |
295 | # ALSA/OSS stuff |
220 | # ALSA/OSS stuff |
296 | # Comment/change these if you want to change the permissions on |
221 | # Comment/change these if you want to change the permissions on |
297 | # the audio devices |
222 | # the audio devices |
298 | LOOKUP snd MODLOAD ACTION snd |
223 | LOOKUP snd MODLOAD ACTION snd |
… | |
… | |
300 | LOOKUP mixer MODLOAD |
225 | LOOKUP mixer MODLOAD |
301 | LOOKUP midi MODLOAD |
226 | LOOKUP midi MODLOAD |
302 | REGISTER sound/.* PERMISSIONS root.audio 660 |
227 | REGISTER sound/.* PERMISSIONS root.audio 660 |
303 | REGISTER snd/.* PERMISSIONS root.audio 660 |
228 | REGISTER snd/.* PERMISSIONS root.audio 660 |
304 | </pre> |
229 | </pre> |
305 | <note> |
230 | |
306 | 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. |
231 | </body> |
307 | </note> |
232 | </section> |
|
|
233 | <section> |
|
|
234 | <title>Having ALSA Activated at Boot</title> |
|
|
235 | <body> |
|
|
236 | |
|
|
237 | <p> |
|
|
238 | To activate ALSA support at boot, add the <c>alsasound</c> init script to the |
|
|
239 | boot runlevel: |
|
|
240 | </p> |
|
|
241 | |
|
|
242 | <pre caption="Adding alsasound to the boot runlevel"> |
|
|
243 | # <i>rc-update add alsasound boot</i> |
|
|
244 | # <i>/etc/init.d/alsasound start</i> |
|
|
245 | </pre> |
|
|
246 | |
|
|
247 | </body> |
|
|
248 | </section> |
|
|
249 | <section> |
|
|
250 | <title>Unmute the Channels</title> |
|
|
251 | <body> |
|
|
252 | |
|
|
253 | <p> |
|
|
254 | By default, all sound channels are muted. To fix this, run <c>amixer</c>: |
|
|
255 | </p> |
|
|
256 | |
|
|
257 | <pre caption="Running amixer"> |
|
|
258 | # <i>amixer</i> |
|
|
259 | </pre> |
|
|
260 | |
|
|
261 | <p> |
|
|
262 | If <c>amixer</c> produces lots of output then you're ready to unmute the |
|
|
263 | channels. If you receive an error, doublecheck that your soundcard module is |
|
|
264 | started. |
|
|
265 | </p> |
|
|
266 | |
|
|
267 | <p> |
|
|
268 | Now unmute the <e>Master</e> and <e>PCM</e> channels. If this isn't sufficient, |
|
|
269 | also unmute the <e>Center</e> and <e>Surround</e> channels. |
|
|
270 | </p> |
|
|
271 | |
|
|
272 | <pre caption="Unmuting the sound channels"> |
|
|
273 | # <i>amixer set Master 100 unmute</i> |
|
|
274 | # <i>amixer set PCM 100 unmute</i> |
|
|
275 | <comment>(Only if the above isn't sufficient:)</comment> |
|
|
276 | # <i>amixer set Center 100 unmute</i> |
|
|
277 | # <i>amixer set Surround 100 unmute</i> |
|
|
278 | # <i>amixer set Headphone 100 unmute</i> |
|
|
279 | </pre> |
|
|
280 | |
|
|
281 | <p> |
|
|
282 | To check if your sound works, play a wave file (using <c>aplay</c>), mp3 (using |
|
|
283 | <c>mpg123</c> or even <c>mplayer</c>) or any other sound file for that matter. |
|
|
284 | </p> |
|
|
285 | |
|
|
286 | <p> |
|
|
287 | To fine-tune the sound channel settings you can use the <c>alsamixer</c> |
|
|
288 | application. |
|
|
289 | </p> |
|
|
290 | |
308 | </body> |
291 | </body> |
309 | </section> |
292 | </section> |
310 | </chapter> |
293 | </chapter> |
311 | <chapter> |
294 | <chapter> |
312 | <title>Starting ALSA</title> |
295 | <title>Activating MIDI Support</title> |
313 | <section> |
|
|
314 | <title>Adding alsasound to a runlevel</title> |
|
|
315 | <body> |
|
|
316 | <p> |
|
|
317 | First thing to do now, is to make ALSA startup at boottime. Like this: |
|
|
318 | <pre> |
|
|
319 | # <i>rc-update add alsasound boot</i> |
|
|
320 | </pre> |
|
|
321 | </p> |
|
|
322 | <p> |
|
|
323 | <warn>Note that the alsasound script should be added to the "boot" runlevel, not the "default" runlevel.</warn> |
|
|
324 | </p> |
|
|
325 | </body> |
|
|
326 | </section> |
296 | <section> |
|
|
297 | <title>Installing the Necessary Packages</title> |
|
|
298 | <body> |
|
|
299 | |
|
|
300 | <p> |
|
|
301 | Some soundcards come with onboard MIDI synthesizers. To use them, you must first |
|
|
302 | install the <c>awesfx</c> package: |
|
|
303 | </p> |
|
|
304 | |
|
|
305 | <pre caption="Installing the awesfx package"> |
|
|
306 | # <i>emerge awesfx</i> |
|
|
307 | </pre> |
|
|
308 | |
|
|
309 | <p> |
|
|
310 | If you have a collection of sound fonts somewhere, place them in |
|
|
311 | <path>/usr/share/sfbank</path>. For instance, the SBLive has a sound font file |
|
|
312 | called <path>8MBGMSFX.SF2</path> or <path>CT4GMSFX.SF2</path>. |
|
|
313 | </p> |
|
|
314 | |
|
|
315 | <p> |
|
|
316 | After copying over the sound font, select them using <c>asfxload</c>: |
|
|
317 | </p> |
|
|
318 | |
|
|
319 | <pre caption="Loading the sound font"> |
|
|
320 | # <i>asfxload /usr/share/sfbank/8MBGMSFX.SF2</i> |
|
|
321 | </pre> |
|
|
322 | |
|
|
323 | <p> |
|
|
324 | You must have this command run every time you boot, so it is adviseable to add |
|
|
325 | it to <path>/etc/conf.d/local.start</path> as well. |
|
|
326 | </p> |
|
|
327 | |
|
|
328 | <p> |
|
|
329 | If you can't find soundfonts on your driver CD you can download some online from |
|
|
330 | <uri>http://www.parabola.demon.co.uk/alsa/awe64.html</uri>. |
|
|
331 | </p> |
|
|
332 | |
|
|
333 | </body> |
327 | <section> |
334 | </section> |
328 | <title>Running and unmuting</title> |
335 | <section> |
|
|
336 | <title>Timidity++ Virtual Synthesizer</title> |
|
|
337 | <body> |
|
|
338 | |
|
|
339 | <p> |
|
|
340 | If your sound card does not come with a hardware synthesizer (or you don't want |
|
|
341 | to use it), you can use <c>timidity++</c> to provide you with a virtual |
|
|
342 | synthesizer. Start by emerging this package: |
|
|
343 | </p> |
|
|
344 | |
|
|
345 | <pre caption="Installing Timidity++"> |
|
|
346 | # <i>emerge timidity++</i> |
|
|
347 | </pre> |
|
|
348 | |
|
|
349 | <p> |
|
|
350 | For timidity to play sounds, it needs a soundfont. If you do not have any, |
|
|
351 | install <c>timidity-eawpatches</c> which will give you some soundfonts. |
|
|
352 | </p> |
|
|
353 | |
|
|
354 | <pre caption="Installing timidity-eawpatches"> |
|
|
355 | # <i>emerge timidity-eawpatches</i> |
|
|
356 | </pre> |
|
|
357 | |
|
|
358 | <p> |
|
|
359 | Don't forget to add <c>timidity</c> to the default runlevel. |
|
|
360 | </p> |
|
|
361 | |
|
|
362 | <pre caption="Adding timidity to the default runlevel"> |
|
|
363 | # <i>rc-update add timidity default</i> |
|
|
364 | # <i>/etc/init.d/timidity start</i> |
|
|
365 | </pre> |
|
|
366 | |
329 | <body> |
367 | </body> |
330 | <p> |
368 | </section> |
331 | Since we're Linux users, we don't want to reboot. So we'll start the alsasound script manually. |
369 | <section> |
|
|
370 | <title>Testing MIDI Support</title> |
|
|
371 | <body> |
|
|
372 | |
332 | </p> |
373 | <p> |
|
|
374 | You can use <c>aplaymidi</c> from the ALSA Utils to test your MIDI |
|
|
375 | configuration. |
|
|
376 | </p> |
|
|
377 | |
|
|
378 | <p> |
|
|
379 | To see what MIDI output ports are available on your system, use the <c>-l</c> |
|
|
380 | option: |
|
|
381 | </p> |
|
|
382 | |
|
|
383 | <pre caption="Viewing the MIDI output ports"> |
|
|
384 | # <i>aplaymidi -l</i> |
333 | <pre> |
385 | </pre> |
334 | # <i>/etc/init.d/alsasound start</i> |
386 | |
335 | </pre> |
|
|
336 | <p> |
|
|
337 | ALSA is running now. If everything is ok, you should be able to see the ALSA modules loaded when running <c>lsmod</c>. |
|
|
338 | However, sound won't work yet, because the channels are still muted. We need <c>amixer</c> for this. |
|
|
339 | </p> |
387 | <p> |
340 | <pre caption = "Running amixer"> |
388 | If all looks fine, try playing a MIDI file to make sure everything works. With |
341 | # <i>amixer</i> |
389 | the <c>-p</c> option you define what MIDI port you want to use. |
342 | </pre> |
|
|
343 | <p> |
390 | </p> |
344 | <warn> |
391 | |
345 | 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 modprobe |
392 | <pre caption="Playing a MIDI file"> |
346 | <c>snd-mixer-oss</c> and <c>snd-pcm-oss</c> once. After that run amixer again. |
393 | # <i>aplaymidi -p 65:0 "Final Fantasy 7 - Aerith' Theme.mid"</i> |
347 | </warn> |
|
|
348 | </p> |
394 | </pre> |
349 | <pre caption="only if you get an error when running amixer"> |
395 | |
350 | # <i>modprobe snd-mixer-oss</i> |
|
|
351 | # <i>modprobe snd-pcm-oss</i> |
|
|
352 | # <i>amixer</i> |
|
|
353 | </pre> |
|
|
354 | <p> |
|
|
355 | If you got this far, now unmute Master and PCM channels. Some hardware |
|
|
356 | even requires you to unmute the center channel or even the surround |
|
|
357 | channel. |
|
|
358 | </p> |
|
|
359 | <p> |
|
|
360 | <pre caption = "Unmuting channels"> |
|
|
361 | # <i>amixer set Master 100 unmute</i> |
|
|
362 | # <i>amixer set PCM 100 unmute</i> |
|
|
363 | <comment>Only if the above doesn't succeed on its own:</comment> |
|
|
364 | # <i>amixer set Center 100 unmute</i> |
|
|
365 | # <i>amixer set Surround 100 unmute</i> |
|
|
366 | <comment>Test the sound:</comment> |
|
|
367 | # <i>aplay $KDEDIR/share/sounds/pop.wav</i> <codenote>(pop.wav is part of KDE)</codenote> |
|
|
368 | </pre> |
|
|
369 | </p> |
|
|
370 | 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. |
|
|
371 | Then, adjust the volume settings to your liking; the ncurses-based <c>alsamixer</c> is a great way to get them "just so". |
|
|
372 | <p> |
|
|
373 | You may want to emerge <c>alsa-xmms</c> as that will provide ALSA support for XMMS. |
|
|
374 | </p> |
|
|
375 | When you reboot your system, the <e>alsasound</e> init script will properly save and restore your volume settings. |
|
|
376 | </body> |
396 | </body> |
377 | </section> |
397 | </section> |
378 | </chapter> |
398 | </chapter> |
379 | <chapter> |
399 | <chapter> |
380 | <title>Final Notes</title> |
400 | <title>Final Remarks</title> |
381 | <section> |
|
|
382 | <title>After kernel-upgrades..</title> |
|
|
383 | <body> |
|
|
384 | <p>When you ever rebuild your kernel, or upgrade to another kernel, you'll have to rebuild the ALSA modules.</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 |
|
|
386 | have to be installed again, since it will put the alsa modules in |
|
|
387 | <path>/lib/modules/*/kernel/sound/pci/</path>.</p> |
|
|
388 | <pre caption="needed after each kernel compile"> |
|
|
389 | # <i>emerge alsa-driver</i> |
|
|
390 | </pre> |
|
|
391 | </body> |
|
|
392 | </section> |
401 | <section> |
|
|
402 | <title>Tools and Firmware</title> |
|
|
403 | <body> |
|
|
404 | |
|
|
405 | <p> |
|
|
406 | Some specific sound cards can benefit from certain tools provided by the |
|
|
407 | <c>alsa-tools</c> and <c>alsa-firmware</c> packages. If you need |
|
|
408 | <c>alsa-tools</c>, be sure to define the ALSA_TOOLS variable in |
|
|
409 | <path>/etc/make.conf</path> with the tools you require. For instance: |
|
|
410 | </p> |
|
|
411 | |
|
|
412 | <pre caption="Selecting ALSA Tools in /etc/make.conf"> |
|
|
413 | ALSA_TOOLS="as10k1 ac3dec" |
|
|
414 | </pre> |
|
|
415 | |
|
|
416 | <p> |
|
|
417 | Then install the <c>alsa-tools</c> (and/or <c>alsa-firmware</c>) package(s): |
|
|
418 | </p> |
|
|
419 | |
|
|
420 | <pre caption="Installing ALSA Tools"> |
|
|
421 | # <i>emerge alsa-tools</i> |
|
|
422 | </pre> |
|
|
423 | |
|
|
424 | </body> |
393 | <section> |
425 | </section> |
394 | <title>/etc/modules.autoload</title> |
|
|
395 | <body> |
|
|
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 |
|
|
397 | load the correct modules at startup.</p> |
|
|
398 | <p>It's not necessary to add <c>snd-pcm-oss</c> or <c>snd-mixer-oss</c> in this file. |
|
|
399 | Check the <uri link="http://www.djcj.org/LAU/guide/alsbook/faq1.html">this FAQ</uri> for more info.</p> |
|
|
400 | </body> |
|
|
401 | </section> |
426 | <section> |
|
|
427 | <title>Activating Joystick Support</title> |
|
|
428 | <body> |
402 | |
429 | |
|
|
430 | <p> |
|
|
431 | If your soundcard has a joystick plug, you might be interested in activating |
|
|
432 | joystick support for your soundcard. If so, start by verifying if your soundcard |
|
|
433 | driver has a joystick parameter. You can verify this by running <c>modinfo</c> |
|
|
434 | against your kernel module. For instance, for the <c>snd-via82xx</c>: |
|
|
435 | </p> |
|
|
436 | |
|
|
437 | <pre caption="Running modinfo"> |
|
|
438 | # <i>modinfo snd-via82xx</i> |
|
|
439 | filename: /lib/modules/2.4.22-ck2/snd-via82xx.o |
|
|
440 | description: "VIA VT82xx audio" |
|
|
441 | author: "Jaroslav Kysela <perex@suse.cz>" |
|
|
442 | license: "GPL" |
|
|
443 | parm: index int array (min = 1, max = 8), description "Index value for |
|
|
444 | VIA 82xx bridge." |
|
|
445 | parm: id string array (min = 1, max = 8), description "ID string for VIA |
|
|
446 | 82xx bridge." |
|
|
447 | parm: enable int array (min = 1, max = 8), description "Enable audio part |
|
|
448 | of VIA 82xx bridge." |
|
|
449 | parm: mpu_port long array (min = 1, max = 8), description "MPU-401 port. |
|
|
450 | (VT82C686x only)" |
|
|
451 | <i>parm: joystick int array (min = 1, max = 8), description "Enable |
|
|
452 | joystick. (VT82C686x only)"</i> |
|
|
453 | parm: ac97_clock int array (min = 1, max = 8), description "AC'97 codec |
|
|
454 | clock (default 48000Hz)." |
|
|
455 | parm: dxs_support int array (min = 1, max = 8), description "Support for |
|
|
456 | DXS channels (0 = auto, 1 = enable, 2 = disable, 3 = 48k only, 4 = |
|
|
457 | no VRA) |
|
|
458 | </pre> |
|
|
459 | |
|
|
460 | <p> |
|
|
461 | If it has the <c>joystick</c> parameter, append <c>joystick=1</c> to your |
|
|
462 | <c>options</c> line in <path>/etc/modules.d/alsa</path>. For instance: |
|
|
463 | </p> |
|
|
464 | |
|
|
465 | <pre caption="Adding the joystick parameter"> |
|
|
466 | alias snd-card-0 snd-via82xx |
|
|
467 | options snd-via82xx joystick=1 |
|
|
468 | </pre> |
|
|
469 | |
|
|
470 | </body> |
403 | <section> |
471 | </section> |
404 | <title>Known bugs</title> |
472 | <section> |
|
|
473 | <title>Resources</title> |
405 | <body> |
474 | <body> |
406 | |
|
|
407 | <note> |
|
|
408 | This guide lags behind on the alsa-development. Chances are these bugs |
|
|
409 | are already fixed when you read this. |
|
|
410 | </note> |
|
|
411 | |
475 | |
412 | <ul> |
476 | <ul> |
413 | <li> |
477 | <li><uri link="http://www.alsa-project.org">The ALSA Project</uri></li> |
414 | If you have <b>lots of noise</b> when using <b>oss</b> emulation, add |
478 | <li><uri link="http://www.djcj.org">ALSA Howto's and FAQs</uri></li> |
415 | <e>options snd-pcm-oss dsp_map=1</e> to |
479 | <li><uri link="http://linux-sound.org">Linux Sound/MIDI Software</uri></li> |
416 | <path>/etc/modules.d/alsa</path>. |
|
|
417 | </li> |
|
|
418 | </ul> |
480 | </ul> |
419 | |
481 | |
420 | </body> |
|
|
421 | </section> |
|
|
422 | |
|
|
423 | <section> |
|
|
424 | <title>More links..</title> |
|
|
425 | <body> |
|
|
426 | <p> |
|
|
427 | You could check these for additional info: |
|
|
428 | </p> |
|
|
429 | <p> |
|
|
430 | <ul> |
|
|
431 | <li><uri link="http://www.gentoo.org/doc/en/desktop.xml">The Gentoo Linux Desktop Configuration Guide</uri></li> |
|
|
432 | <li><uri link="http://www.alsa-project.org">ALSA Project Homepage</uri></li> |
|
|
433 | <li><uri link="http://www.alsa-project.org/documentation.php3">ALSA Users Documentation</uri></li> |
|
|
434 | <li><uri link="http://www.djcj.org">ALSA Howto's and FAQ's</uri></li> |
|
|
435 | <li><uri link="http://tldp.org/HOWTO/Sound-HOWTO/index.html">Linux Sound HOWTO</uri></li> |
|
|
436 | <li><uri link="http://linux-sound.org/">Sound and MIDI Software For Linux</uri></li> |
|
|
437 | </ul> |
|
|
438 | </p> |
|
|
439 | </body> |
482 | </body> |
440 | </section> |
483 | </section> |
441 | </chapter> |
484 | </chapter> |
442 | </guide> |
485 | </guide> |